Official protocol mechanism
A six-step process for proposing and approving the official Host-Host protocol.
Crocker, S.D., "Official protocol mechanism", RFC 53, DOI 10.17487/RFC0053, June 1970, <https://www.rfc-editor.org/info/rfc53>.
@misc{rfc53,
series = {Request for Comments},
number = 53,
howpublished = {RFC 53},
publisher = {RFC Editor},
doi = {10.17487/RFC0053},
url = {https://www.rfc-editor.org/info/rfc53},
author = {S.D. Crocker},
title = {{Official protocol mechanism}},
pagetotal = 1,
year = 1970,
month = jun,
} RFC text
Network Working Group S. Crocker
Request for Comments #53 UCLA
9 June 70
An Official Protocol Mechanism
During the Spring Joint Computer Conference in Atlantic City, Larry
Roberts, Barry Wessler, Cordell Green, Jon Postel and I discussed rules
for establishing and modifying an official Host-Host protocol.
The following decisions were made:
1. A new set of documents will be created. This set of
documents will specify the official Host-Host protocol. When
it becomes appropriate, these documents will be maintained at
the Network Information Center on SRI's computer.
2. I will distribute proposals for the initial version of the
official protocol and all subsequent changes as NWG/RFC's.
These proposals will be formulated from suggestions made by
any interested parties.
3. After a proposal for a change in the official protocol
has been issued as an NWG/RFC, networkers are requested to
respond with approval, criticism, etc. A cutoff date will be
included with each protocol.
4. After the cutoff date, one of two situations will prevail.
Either the proposal will have been substantially accepted by
the network community, or substantial criticism will have been
generated. In the latter case, the process stops and no
change occurs to the official protocol.
5. If the proposal has been substantially accepted, the
proposal, together with its minor revisions will be forwarded
to the ARPA office. Barry Wessler or his successor will then
either approve or disapprove the whole proposal. His decision
will be returned to me by letter.
6. After the ARPA office approves the proposal, I will send
out the new protocol (as mentioned in item 1 above).
The first version of an official protocol will be proferred this month.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Kathy de Graaf 2/98 ]
ISO Plain Language
On this page
§1Decisions on Protocol Governance
During the Spring Joint Computer Conference in Atlantic City, Larry Roberts, Barry Wessler, Cordell Green, Jon Postel, and Steve Crocker discussed rules for establishing and modifying an official Host-Host protocol.
RFC 53 records six decisions about documentation, proposal development, community comments, and approval.
The participants agreed on a process for publishing and reviewing proposals for the official Host-Host protocol. This memo records those decisions.
§1Proposal, Review, and Approval
A new set of documents would specify the official protocol and be maintained at the Network Information Center when appropriate. Steve Crocker would distribute proposals for the initial protocol and later changes as NWG/RFCs, using suggestions from interested parties.
Each proposal would include a cutoff date for community feedback. If substantial criticism emerged, the process would stop without changing the official protocol. If the proposal was substantially accepted, it and minor revisions would go to the ARPA office for approval or disapproval.
Interested parties could suggest changes, and the community could comment by a stated deadline. Accepted proposals still needed approval from the ARPA office.
§1After Approval
After ARPA approval, Crocker would distribute the new protocol. The note states that the first version of an official protocol would be offered that month.
Once approved, the new protocol would be distributed. The note expected the first version to be proposed in June 1970.