RFC 214

NETWORK CHECKOUT 💖

Okay bestie, here's the title block tea 🫶

• Network Working Group 🌸
• RFC number: 214 (also NIC 7195) ✨
• Title: NETWORK CHECKOUT
• Author: E. Harslem-Rand 💅
• Date: 21 August 1971 🦋
• Category: F
• Obsoletes: RFCs 193 and 198 👑
• Updates: nothing is listed in the title block 🙈

The Big Checkup 🔥

Okay so, as of August 21 we had run the following verifications with the sites listed below. These were done on an arranged basis, so they don't mean any site is continuously available 💜

What "NCP-107" Really Means 🙈

Ngl, the heading for this category is a little misleading 💀 It does NOT mean we did a thorough checkout of all the NCP functions described in Document 1 and RFC-107. What it actually means is that the NCP in question worked well enough to respond to a RESET (which the Rand NCP needs before it will consider the remote host "up") and that it performed the functions needed for an ICP. So this column really only shows a small amount of NCP completeness 🥺

Functions like ECHO, Give Back, and error message generation weren't checked. We did check some of them with UCSB and SDC, but not exhaustively, mostly because it's so tedious 😭 BBN is currently writing a protocol certifier for their DDP-516 host that will do all of this automatically. Iconic, honestly 🧚

The Table 🎀

Here's the whole vibe check:

                               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

The Legend 🌈

Here's how to read the symbols, no cap:

LEGEND:

 --- the function has not been verified for the host

x--- the function has been verified for the host
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 From the Hosts 💖

• SRI NIC: both a server telnet and a logger exist, but they don't process the telnet messages correctly 😭
• MIT Multics: we could only connect to an interim logger, and it sent a ts message ✨
• SDC: the logger makes the system crash right after login 💀

Last Words 🦋

If you spot any discrepancies, let us know by phone call 📞 This RFC will be updated in about one month, so stay tuned, bestie 🫶

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