Postponement of network graphics meeting
A scheduled meeting moves to a later date.
Vezza, A., "Postponement of network graphics meeting", RFC 232, DOI 10.17487/RFC0232, September 1971, <https://www.rfc-editor.org/info/rfc232>.
@misc{rfc232,
series = {Request for Comments},
number = 232,
howpublished = {RFC 232},
publisher = {RFC Editor},
doi = {10.17487/RFC0232},
url = {https://www.rfc-editor.org/info/rfc232},
author = {A. Vezza},
title = {{Postponement of network graphics meeting}},
pagetotal = 1,
year = 1971,
month = sep,
} RFC text
RFC #232
NIC #7649
A. Vezza
September 23, 1971
At the last Network Graphics meeting held in July at
M.I.T., we tentatively scheduled the next Network Graphics
meeting which is being hosted by Stanford AI, for October
17, 18, and 19. Because the Network Working Group meeting
is being held on October 10, 11, 12, 13, and 14 it has been
decided to postpone the Network Graphics meeting. As soon
as a new date for the meeting is established it will be
announced via an RFC. It is expected that the meeting will
be held in the San Francisco area sometime in November or
early December.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by BBN Corp. under the ]
[ direction of Alex McKenzie. 12/96 ]
AI ELI5
On this page
§1Meeting Postponement
RFC 232 is a short notice that the Network Graphics meeting, tentatively scheduled for October 17, 18, and 19, 1971 at Stanford AI, has been postponed. The reason is a scheduling conflict: the Network Working Group meeting is being held October 10-14, making back-to-back meetings impractical.
Two different meetings were planned for the same week, so one had to move.
§2New Schedule
A new date for the Network Graphics meeting will be established and announced via RFC. The meeting is expected to be held in the San Francisco area in November or early December 1971.
A new date will be picked and announced later.
§3Background
The Network Graphics meeting was tentatively scheduled following the July 1971 meeting at MIT. The decision to postpone came after the October Network Working Group meeting dates were finalized, creating a scheduling conflict.
The two communities planned meetings on the same dates without realizing it until it was too late to change.