RFC 111

Pressure from the Chairman

📅 published March 1971, from ietf

RFC 111: Pressure from the Chairman 💅

  • Network Working Group 🫶
  • Request for Comments: #111
  • NIC: #5815
  • Author: S. Crocker, UCLA ✨
  • Date: 31 March 71 📅
  • Categories: A.5 🎀
  • RFC's obsoleted: none
  • RFC's updated: 107 🦋

Okay bestie, this one is giving serious chairman energy 💀. It's time to lock in real schedules for implementing NCP's and Telnets, no more vibes-based planning 🔥. To keep things moving, John Heafner of Rand has agreed to keep tabs on every site's progress and test their implementations 🧚.

Network Liaison Contacts are officially responsible for making a schedule for implementation and telling John about it 📋. That schedule has to include the dates of:

  • (a) implementing an NCP following the specifications in Document #1 as modified by RFC #107 💻;
  • (b) implementing a user-Telnet that lets local users log in to foreign Hosts 🌸;
  • (c) implementing a server-Telnet that lets foreign users log in to your Host 🌈;
  • (d) documenting the mechanism for connecting to and logging in to your Host 📖;
  • (e) documenting the mechanism for obtaining job numbers, passwords, etc. to your Host 🔑;
  • (f) documenting the services available on your Host; and
  • (e) regular operation at advertised hours ⏰.

John is now officially in charge of prodding Host teams to produce the requisite schedule, software, and documentation 👑. He's also testing the advertised implementations 🧪 and probing the reasons behind any unseemly delays 🙈. Concomitantly, John is the right person to complain to about ambiguities, insufficiencies, and misunderstandings of the protocols 💜. Iykyk 😭.

Thank you for your cooperation 🫶✨.

Steve Crocker 💖

[ This RFC was put into machine readable form for entry into the online RFC archives by Josh Elliott 1/98 ]

📦 where this page comes from