Network Meeting
An announcement for a 1970 meeting to discuss the network protocol.
Crocker, S.D., "Network Meeting", RFC 35, DOI 10.17487/RFC0035, March 1970, <https://www.rfc-editor.org/info/rfc35>.
@misc{rfc35,
series = {Request for Comments},
number = 35,
howpublished = {RFC 35},
publisher = {RFC Editor},
doi = {10.17487/RFC0035},
url = {https://www.rfc-editor.org/info/rfc35},
author = {S.D. Crocker},
title = {{Network Meeting}},
pagetotal = 1,
year = 1970,
month = mar,
} RFC text
Network Working Group S. Crocker
Request for Comments: 35 UCLA
Category: Informational 3 March 1970
Network Meeting
I expect to have the details of the new network protocol as
outlined in NWG/RFC #33 ready in two weeks. Some interest has been
expressed in a live presentation, so we will host a network meeting on
Tuesday, March 17, at UCLA at 9:00 a.m. To facilitate interaction,
please limit attendance to one programmer from each site. It is also
wise to leave the 18th open in case discussion continues.
The subject of the meeting will be a detailed presentation of the
network protocol, suitable for implementing unless major flaws are
discovered. Documentation will be available at the meeting and if not
obsoleted by the meeting, will be sent out as NWG/RFC on March 20.
Please call Mrs. Charlotte LaRoche at (213) 825-2543 if you need
help in making arrangements.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Jochen Friedrich 4/97 ]
ISO Plain Language
On this page
§1A Meeting at UCLA
Steve Crocker expected the details of the network protocol outlined in NWG/RFC 33 to be ready within two weeks. Because people wanted a live presentation, he announced a network meeting at UCLA on Tuesday, March 17, at 9:00 a.m.
The meeting would present the protocol in enough detail to implement it unless participants found major flaws. Documentation would be available at the meeting.
The protocol authors planned an in-person presentation so network participants could hear the details and discuss problems.
§1Attendance and Follow-Up
To make discussion easier, attendees were asked to limit participation to one programmer from each site. Participants were also advised to keep March 18 open in case discussion continued.
If the meeting did not make the documentation obsolete, it would be sent out as an NWG/RFC on March 20. The memo includes a telephone contact for help with arrangements.
Each site was asked to send one programmer. If the meeting did not require changes, the document would be circulated shortly afterward.
§1A Coordination Memo
The text is limited to meeting arrangements and the planned presentation of a protocol. It does not contain the protocol details or prescribe network behavior.
Its publication as an RFC provides a dated record of how participants planned to discuss the proposal and decide whether its documentation needed revision.
This memo documents how the meeting was organized. The network rules themselves were expected in a separate document.