Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc214.txt.pdf Дата изменения: Wed Mar 27 23:23:26 2002 Дата индексирования: Tue Oct 2 16:20:43 2012 Кодировка:

Network Working Group Request for Comments 214 NIC 7195 Category: F Obsoletes: 193, 198

21 August 1971 E. Harslem-Rand

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 NCP-107 ICP-156 Telnet x x x x x x x x x x x x x x x x x ? x x x x x x x x x TENEX being installed Server Telnet x x ? x x x x x x Access Service x x ? x x na x x

UCLA Sigma7 UCLA /91 SRI NIC UCSB BBN A10 BBN TIP MIT Multics MIT DMCG SDC LINCOLN /67 UTAH

Logger x na ? na x

x ? x

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. RFC will be updated in about one month.

This

[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Brian Court 6/97 ]

[Page 2]