Pressure from the Chairman
The Network Working Group chair asks every site for a real schedule for its network software.
Crocker, S.D., "Pressure from the Chairman", RFC 111, DOI 10.17487/RFC0111, March 1971, <https://www.rfc-editor.org/info/rfc111>.
@misc{rfc111,
series = {Request for Comments},
number = 111,
howpublished = {RFC 111},
publisher = {RFC Editor},
doi = {10.17487/RFC0111},
url = {https://www.rfc-editor.org/info/rfc111},
author = {S.D. Crocker},
title = {{Pressure from the Chairman}},
pagetotal = 2,
year = 1971,
month = mar,
} RFC text
Network Working Group S. Crocker
Request for Comments #111 UCLA
NIC #5815 31 March 71
Pressure from the Chairman
[Categories: A.5;
RFC's obsoleted: none;
RFC's updated: 107]
It is time to set serious schedules for the implementation of NCP's and
Telnets. To facilitate matters, John Heafner of Rand has agreed to
monitor each site's progress and test its implementation.
Network Liaison Contacts are hereby responsible for preparing a schedule
for implementation and informing John. Such a schedule must include
dates of
(a) implementation of an NCP according to the specifications
in Document #1 as modified by RFC #107;
(b) implementation of a user-Telnet which enables local users to
login to foreign Hosts;
(c) implementation of a server-Telnet which enables foreign users to
login on your Host;
(d) documentation of the mechanism for connecting to and logging in
to your Host;
(e) documentation of the mechanism for obtaining job numbers,
passwords, etc. to your Host;
(f) documentation of the services available on your Host; and
(e) regular operation at advertised hours.
RFC 111
John is hereby responsible for prodding Host teams to prodcue the
requisite schedule, software and documentation; for testing out the
advertised implementations; and for probing and understanding the
reasons for unseemly delays. Concomitantly, John is now the right
person to complain to about ambiguities, insufficiencies and
misunderstandings of the protocols.
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 ]
AI ELI5
On this page
§1The Request for Schedules
This short memo from Steve Crocker says it is time to set serious schedules for the implementation of NCPs (Network Control Programs) and Telnets. To help, John Heafner of Rand agreed to monitor each site's progress and test its implementation.
Network Liaison Contacts are made responsible for preparing a schedule and informing John. The memo is marked as updating RFC 107.
The class leader says it is time to pick finish dates. A helper named John will keep track.
§2What a Schedule Must Cover
A schedule must include dates for implementing an NCP according to the specifications in Document #1 as modified by RFC 107, a user-Telnet that lets local users log in to foreign Hosts, and a server-Telnet that lets foreign users log in on your Host.
It must also give dates for documenting how to connect and log in to your Host, documenting how to obtain job numbers and passwords, documenting the services available on your Host, and reaching regular operation at advertised hours.
Each school must say when its mailbox will work, when visitors can come in, and when it will write down the rules for visiting.
§3John Heafner's Role
John is responsible for prodding Host teams to produce the schedule, software and documentation, for testing the advertised implementations, and for probing and understanding the reasons for unseemly delays.
The memo adds that John is now the right person to complain to about ambiguities, insufficiencies and misunderstandings of the protocols.
John nudges people who are late, checks that things work, and listens when something in the rules is confusing.