Network Working Group 21 August 1971 Request for Comments 214 E. Harslem-Rand NIC 7195 Category: F Obsoletes: 193, 198 NETWORK CHECKOUT As of August 21 we had performed the following verifications with the sites listed below. These verifications were done on an arranged basis and do not indicate any degree of continuous availability. In the category "NCP-107" the heading is somewhat misleading. It does not indicate a thorough checkout of all the NCP functions described in Document 1 and RFC-107. It only indicates that the NCP in question functioned to the extent required to respond to a RESET (a necessary condition for the Rand NCP to consider the remote host "up") and that the NCP performed the functions necessary for an ICP. Thus, this column really indicates only a small degree of NCP completeness. Such function as ECHO, Give Back, error message generation and so on were not checked. We have checked some of these functions with UCSB and SDC but not exhaustively. This is mainly due to the tedium of such a process. BBN is currently writing a protocol certifier for their DDP-516 host that will do this automatically. User Server Access NCP-107 ICP-156 Telnet Telnet Logger Service UCLA Sigma7 x x x x x x UCLA /91 x x x x na x SRI NIC x x ? ? ? UCSB x x x x na x BBN A10 x x x x x BBN TIP x x x x na MIT Multics x ? MIT DMCG x x x x x x SDC x x x x ? LINCOLN /67 x x x x x x UTAH TENEX being installed LEGEND: --- the function has not been verified for the host x--- the function has been verified for the host [Page 1] 21 Auguest 1971 RFC 214 na-- the function is not applicable to the host due to its operating system or intended network use ?--- a comment follows for that function in that host COMMENTS: SRI NIC -- both a server telnet and logger exist; however, they do not process the telnet messages correctly MIT Multics -- we were only able to connect to an interim logger that sent a 'ts' message SDC -- the logger causes the system to crash following login Any discrepancies should be noted via phone call. This RFC will be updated in about one month. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Brian Court 6/97 ] [Page 2] ------------------------------------------------------------------------ Network Working Group 14 July 1971 Request for Comments: 193 E. Harslem - Rand NIC 7138 J. Heafner - Rand NETWORK CHECKOUT As of 15 July we had contacted or been contacted by the sites listed below. The matrix indicates the elements of Network software we have verified at each site. Telnet- NCP- ICP User Server like Log-on Accessed NCP-1 107 80 Telnet Telnet Protocol Procedure Services ----------------------------------------------------------------- SDC | x | | | | | | | | ----------------------------------------------------------------- UCLA-91 | | x | | x | x | | | | ----------------------------------------------------------------- UCLA-S7 | x | x | x | x | x | | x | x | ----------------------------------------------------------------- SRI-10 | | x | | | | x | x | | ----------------------------------------------------------------- UCSB | x | x | x | | | | x | x | ----------------------------------------------------------------- MIT-10 | | x | | x | | | | | ----------------------------------------------------------------- MIT-645 | |par-| | | | | | | | |tial| | | | | | | ----------------------------------------------------------------- LL-67 | x | | x | | x | | | | ----------------------------------------------------------------- BBN-10 | | x | | | | x | x | x | ----------------------------------------------------------------- UTAH | x | x | x | | | x | | | ----------------------------------------------------------------- Notes SRI-10: The Telnet-like protocol differs from Telnet in that lines are terminated by X'OD' rather than X'ODOA'. John Melvin will have it fixed by the time you read this. [Page 1] RFC 193 LL-67: Joel Winett telles me NCP, ICP, EBCDIC, Telnet and access to a virtual 360 are working. Due to hard- ware difficulties we have not verified this. BBN-10: Same difference as SRI with respect to Telnet. Under certain conditions, the ICP generates a zero byte size. Ray Tomlinson tells me these idiosyncracies will be taken care of in about a week. Three sites have commented that TENEX assigns the same local socket to multiple connec- tions, when acting as a server. Ray says that this is the design -- not an error. BBN TENEX is currently being used productively via the Net, for some non-Network related problems. UTAH: Our tests with UTAH were pre-TENEX. TENEX is currently being installed at UTAH. MIT-645: Our understanding is that most software is working; we have not verified this. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Paul Williams 6/97 ] [Page 2] ------------------------------------------------------------------------ Network Working Group J. Heafner - Rand Request for Comments #198 20 July 1971 NIC #7149 Categories: D.4 Updates: RFC #193 Obsoletes: None SITE CERTIFICATION - LINCOLN LABS 360/67 We have exercised Lincoln Labs Network software as follows: NCP, ICP, ASCII Telnet (user and server), login procedure, access to CMS, and operator and console communication. All behave according to current specifications. Multiple message responses, such as listing users, were very smooth under moderate to heavy load of the /67. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Josh Elliott 1/98 ] [Page 1]