Pressure from the Chairman
The Network Working Group chair asks sites to schedule and test their software implementations.
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 ]
ISO Plain Language
On this page
§1A Request for Firm Schedules
Steve Crocker says it is time to set serious schedules for implementing NCPs and Telnets. John Heafner of Rand agrees to monitor each site's progress and test its implementation.
Each Network Liaison Contact is responsible for preparing a schedule and sending it to Heafner.
Each site must prepare a schedule for its network software. John Heafner will track progress and test what each site builds.
§2What Each Schedule Must Include
The schedule must give dates for implementing an NCP under Document 1 as modified by RFC 107, a user-Telnet for logging in to other hosts, and a server-Telnet for allowing remote users to log in.
It must also give dates for documenting how to connect and log in, how to obtain job numbers and passwords, what services the host offers, and when it will operate regularly during advertised hours.
The schedule covers software, instructions for users and regular service hours. It must include dates for each of these items.
§3Monitoring and Protocol Questions
Heafner is responsible for prompting host teams to produce schedules, software and documentation. He will test advertised implementations and investigate reasons for delays.
The memo also names him as the person to contact about ambiguities, gaps and misunderstandings in the protocols.
Heafner will check that sites meet their schedules and test their software. Sites can also report unclear or insufficient protocol rules to him.