Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!scrc-quabbin.arpa!DCP
From: DCP@SCRC-QUABBIN.ARPA (David C. Plummer in disguise)
Newsgroups: fa.tcp-ip
Subject: TCP Performance and Compatibility
Message-ID: <850905154233.2.NFEP@NEPONSET.SCRC.Symbolics.COM>
Date: Thu, 5-Sep-85 15:42:00 EDT
Article-I.D.: NEPONSET.850905154233.2.NFEP
Posted: Thu Sep  5 15:42:00 1985
Date-Received: Sat, 7-Sep-85 04:17:58 EDT
Sender: daemon@ucbvax.ARPA
Reply-To: tcp-ip@ucb-vax.berkeley.edu
Organization: The ARPA Internet
Lines: 9

For performance, I suggest not using many of the standard protocols.
This is because most of them have to do character set translation or at
least double scanning.  TELNET is one example, and I think ASCII mode of
TCP/FTP is another.  Specifically, it has to scan the data making sure
the whatever the system's newline sequence is gets converted into or
out-of NVT-NEWLINE and that raw CRs get NULLs appended to them.  TCP/FTP
binary mode would probably be OK.  For raw performance, SINK, ECHO and
SOURCE servers would be best, though I don't know off hand if they are a
standard port that people are expected to implement.