Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!A.ISI.EDU!PADLIPSKY
From: PADLIPSKY@A.ISI.EDU (Michael Padlipsky)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RCTE
Message-ID: <8709291511.AA18314@ucbvax.Berkeley.EDU>
Date: Tue, 29-Sep-87 10:55:38 EDT
Article-I.D.: ucbvax.8709291511.AA18314
Posted: Tue Sep 29 10:55:38 1987
Date-Received: Wed, 30-Sep-87 07:18:55 EDT
References: <870928095131.6.DCP@KOYAANISQATSI.S4CC.Symbolics.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13

Never having been at all fond of reinventing wheels, I hastened to
FTP the SUPDUP RFC and print it out at my terminal.  When I got to
"Due to the highly interactive characteristics of both the SUPDUP
protocol and the ITS system [which was the original Server for which
the protocol was developed], all transactions are strictly character
at a time and all echoing is remote" I aborted the printing.  Am I
misunderstanding something--the context is, as far as I know, avoiding
"unnecessary" transmissions--or have you misremembered SUPDUP?
(If the latter, let me be the first to welcome you to Early Middle Age.)
As things stand, I have to deem SUPDUP a reinvention of the travois,
in context; please correct me if I'm wrong.
   cheers, map
-------