Best Laid Plans
A revised agenda and reading correction for an NWG meeting.
Crocker, S.D., "Best Laid Plans", RFC 149, DOI 10.17487/RFC0149, May 1971, <https://www.rfc-editor.org/info/rfc149>.
@misc{rfc149,
series = {Request for Comments},
number = 149,
howpublished = {RFC 149},
publisher = {RFC Editor},
doi = {10.17487/RFC0149},
url = {https://www.rfc-editor.org/info/rfc149},
author = {S.D. Crocker},
title = {{Best Laid Plans}},
pagetotal = 1,
year = 1971,
month = may,
} RFC text
Network Working Group S. Crocker
Request for Comments # 149 UCLA
NIC # 6752 10 May 1971
Categories: A.2
Updates: #140
Obsoletes: None
The Best Laid Plans . . .
Dr. Roberts informs me that it is now unlikely that he will be
able to attend the Monday afternoon session of the NWG meeting,
but that he will be able to attend the Tuesday evening session.
Accordingly, the topics of "Network Planning" and "other ARPA
Projects" are moved to Tuesday evening, and on Monday afternoon,
we will take up as many of the items originally scheduled for
Tuesday evening as we can.
The relevant reading for Wednesday evening is RFC #131, not #113.
In general attendees should read all of the RFC's since the last
NWG meeting.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by C. Harald Koch 05/97 ]
ISO Plain Language
On this page
§1The Meeting Schedule
Dr. Roberts was unlikely to attend the Monday afternoon session, but could attend Tuesday evening. The note therefore moves the topics Network Planning and other ARPA Projects to Tuesday evening.
On Monday afternoon, attendees will cover as many items originally planned for Tuesday evening as they can.
Two topics move to Tuesday evening because Dr. Roberts can attend then. The group will use Monday afternoon for as many of Tuesday's other topics as time allows.
§2The Correct Reading
The relevant reading for Wednesday evening is RFC 131, not RFC 113. The note also says attendees should read all RFCs issued since the previous Network Working Group meeting.
Attendees should read RFC 131 for Wednesday, not RFC 113. They should also catch up on RFCs issued since the previous meeting.
§3Scope of the Note
This one-page RFC records meeting logistics and a reading correction. It does not specify a network protocol. The unit metadata says it updates RFC 140 and lists its status as Unknown.
This RFC is a meeting notice, not a technical protocol. Its metadata says it updates RFC 140.