sra@MITRE-BEDFORD.ARPA (09/05/85)
Mitre-Bedford is about to commence and an operational experiment of interconnecting as many hosts and TCP implementations that we can gain access to in an effort to demonstrate and test vendor compatibility and performance of various implementation strageties. The interconnection will be over Ethernet (Broadband, Baseband and Fiber segments) tied together by Applitek bridges. I am soliciting suggestions as to the types of tests the TCP/IP community would like to see run as well as performance benchmark or compatibility tests that may already exist that we can have. Thanks Stan Ames sra at Mitre-Bedford
MILLS@USC-ISID.ARPA (09/05/85)
In response to the message sent Thursday, 5 Sep 1985 07:20-EDT from sra@mitre-bedford.ARPA Stan, Your tests appear similar to those within the scope of the Protocol Testing Lab at DCEC. You may also discover friends in the Testing Task Force, chaired by Ed Cain (cain@edn-unix). Compatibility tests via Ethernet and Applitek bridges may be an excellent test of Ethernet technology, but they inspire little confidence that cranky TCP implementations find joy in each other via real Internet paths. Dave -------
DCP@SCRC-QUABBIN.ARPA (David C. Plummer in disguise) (09/05/85)
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.