Telnet Protocol meeting announcement
A call for a working meeting to discuss an official TELNET protocol.
McKenzie, A.M., "Telnet Protocol meeting announcement", RFC 461, DOI 10.17487/RFC0461, February 1973, <https://www.rfc-editor.org/info/rfc461>.
@misc{rfc461,
series = {Request for Comments},
number = 461,
howpublished = {RFC 461},
publisher = {RFC Editor},
doi = {10.17487/RFC0461},
url = {https://www.rfc-editor.org/info/rfc461},
author = {A.M. McKenzie},
title = {{Telnet Protocol meeting announcement}},
pagetotal = 1,
year = 1973,
month = feb,
} RFC text
Network Working Group A. McKenzie
RFC # 461 BBN-NET
NIC # 14416 February 14, 1973
TELNET Protocol Meeting Announcement
Since the publication of RFC #318 there have been a great number of
proposals for changes and/or extensions to the (still unofficial) TELNET
Protocol. It now seems appropriate to have a meeting of concerned
parties to try, once again, to reach a consensus position and define an
"official" protocol (with perhaps, some room for optional expansion).
Accordingly, I hereby announce a TELNET Protocol meeting to be held at
UCLA on Monday, March 5. I expect this to be a working meeting (rather
than a tutorial to bring new members of the network community up-to-
speed) and therefore wish to invite the attendance of only those
individuals prepared to discuss at LEAST those issues which have already
been raised. At a minimum, attendees should be familiar with the
following:
RFC 318
RFC 328
RFC 340
RFC 357
RFC 393
RFC 426
RFC 435
A familiarity with deliberations of the TELNET Committee prior to RFC
318 would probably also be helpful. Finally, attendees should be aware
that there are few (no?) Hosts which follow the echo-control conventions
described in RFC 318.
Anyone wishing to attend this meeting should contact Alex McKenzie at
BBN (NIC ident aam) 50 Moulton Street, Cambridge, Mass. 02l38. My
telephone number is
(617) 491-1850 ext. 441
When there is some indication of the number of individuals planning to
attend, a meeting room will be selected, a time announced, etc.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 9/99 ]
ISO Plain Language
On this page
§1Why a TELNET Meeting Was Proposed
Since RFC 318, the TELNET protocol had drawn many proposals for changes and extensions. The RFC calls it still unofficial and says it seemed appropriate to meet again to seek consensus.
Many people had proposed changes to TELNET, which was still unofficial. The author calls for a meeting to try to reach agreement.
§2A Working Meeting at UCLA
The meeting was announced for Monday, March 5, at UCLA. It was intended as a working meeting for people prepared to discuss issues already raised, rather than a tutorial for newcomers.
The notice lists RFCs 318, 328, 340, 357, 393, 426, and 435 as background reading.
The meeting was for people already familiar with the TELNET proposals. The announcement lists earlier RFCs for attendees to read.
§3The Goal: An Official Protocol
The meeting's stated purpose was to reach a consensus position and define an official TELNET protocol, perhaps with some room for optional expansion. The RFC does not report whether the meeting took place or what it decided.
The author also notes that few, if any, Hosts followed the echo-control conventions described in RFC 318.
The group hoped to agree on common TELNET rules while allowing some optional features. This notice does not give the meeting's results.