Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit TrailBlazer
Message-ID: <9103@mimsy.UUCP>
Date: Mon, 26-Oct-87 02:00:24 EST
Article-I.D.: mimsy.9103
Posted: Mon Oct 26 02:00:24 1987
Date-Received: Wed, 28-Oct-87 02:54:15 EST
References: <2451@umix.cc.umich.edu> <54@stsci>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 19

>in article <2451@umix.cc.umich.edu> honey@umix.cc.umich.edu (Peter
>Honeyman) says:
>>the trailblazer requires no modifications to uucp.

In article <54@stsci> butler@stsci.EDU (Lee A. Butler) writes:
>But if you want to take advantage of the trailblazer's added speed, you want
>to use a transfer protocol that will allow large (1K-2K) data packets and a
>sliding-window ack scheme.

That is so.  Yet peter (that is the way he spells it) is correct.
Somehow the Trailblazer manages to use large data packets and sliding
window acks, even while uucp is talking to it using small data packets
and sliding window acks.  The trick is called `g protocol spoofing':
The modem pretends to be the other computer, and acks UUCP's small
packets before it has sent its own big packets.  It may sound horrid,
but it works well.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris