Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.mail.uucp
Subject: Re: uucp through Bridge CS/100
Message-ID: <15805@sun.uucp>
Date: Sat, 28-Mar-87 22:54:35 EST
Article-I.D.: sun.15805
Posted: Sat Mar 28 22:54:35 1987
Date-Received: Sun, 29-Mar-87 17:51:02 EST
References: <463@umnd-cs.D.UMN.EDU> <5817@bu-cs.BU.EDU>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 12

>The PAD protocol exists for connections on X.25 PAD lines that are
>"mostly" reliable and flow controlled.  Checksumming is done on a
>per-file basis.  The SYSVR2 'x' protocol does NOT appear to be
>compatible (does no checksumming?)

They aren't *supposed* to be compatible.  The 'f' protocol is for use
over PADs; it assumes a 7-bit non-transparent data path, and does not
assume that the link level is completely reliable.  The 'x' protocol
is for use over a more direct X.25 connection; it assumes an 8-bit
transparent data path and *does* assume that the link level will do
the checksumming and flow control.  (Sort of like the 'e' or 't'
protocols.)