RFC 659 UNKNOWN TELNET · META

Announcing additional Telnet options

Announcing the new Telnet options from RFC 651 to 658.

On rfc-editor.org ↗
PUBLISHED
October 1974
AUTHORS
J. Postel
STREAM
Legacy
TYPE
Announcement
DOI
10.17487/RFC0659

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                          J. Postel
Request for Comments: 659                                        SRI-ARC
NIC: 31177                                               18 October 1974


                  Announcing Addtional Telnet Options

   This is to announce the set of Telnet Options defined in Request For
   Comments 651 through 658 (NIC 31154 through 31161) are part of the
   official Telnet Options and should be added to the Protocol Notebook.

   RFC 651 is a revision of the Status Option to utilize the subcommand
   feature and reduce the number of bits required to convey the status
   information.  This revised Status Option replaces the previous Status
   Option.

   The other RFCs (652 through 658) are new Options for controlling the
   behavior of the format effector characters Carriage Return,
   Horizontal Tab, Form Feed, Vertical Tab, and Line Feed.

   Your attention is also called to RFC 645 (NIC 30899) "Network
   Standard Data Specification Syntax" which was prepared some time ago
   but has not received wide circulation.

   Unfortunately the Network Information Center can not provide hardcopy
   documents.  Currently the author is responsible for distribution of
   RFCs.

   The documents are available online as:

      [ISI]<DCROCKER>STATUS-OPTION-REVISION.TXT
      [ISI]<DCROCKER>NAOCRD.TXT
      [ISI]<DCROCKER>NAOHTS.TXT
      [ISI]<DCROCKER>NAOHTD.TXT
      [ISI]<DCROCKER>NAOFFD.TXT
      [ISI]<DCROCKER>NAOVTS.TXT
      [ISI]<DCROCKER>NAOVTD.TXT
      [ISI]<DCROCKER>NAOLFD.TXT
      [SRI-ARC]<POSTEL>RFC645.TXT
      [SRI-ARC]<POSTEL>RFC659.TXT (This Announcement)
         (If these files are not found online they may have been
         archived, in this case the files should be accessable via the
         "interogate" command.)


             [This RFC was put into machine readable form for entry]
              [into the online RFC archives by Lorrie Shiota, 2/02]

AI ELI5

On this page
PROBLEMMultiple new Telnet options had been defined in RFCs 651 to 658, but there was no central announcement to notify the community and point to the official list.
MECHANISMThis is a short announcement document that lists the new options and points to where they are defined: a revised Status option (RFC 651) and seven new options for handling formatting characters like tabs, formfeeds, and line-feeds.
STATUSThe community was notified of the options and could refer to the individual RFCs for the technical specifications. These options were included in the official Telnet protocol suite.

§1The Telnet Options Announcement

RFC 659 is a short announcement document by Jon Postel at SRI-ARC, written to draw attention to a new set of Telnet options that had been defined in RFCs 651 through 658. It does not define any protocol itself; it simply announces the official adoption of these options into the Telnet protocol and directs readers to the documents where the actual specifications are found.

This is just a notice: some new Telnet options have been written down in other RFCs, and here is where to find them.

§3Where to Find the Specifications

The RFC lists online file locations where the documentation is available (from ISI and SRI-ARC systems), noting that at the time, the Network Information Center could not provide hardcopy and the author was responsible for distribution. The reference to RFC 645, "Network Standard Data Specification Syntax," notes that important document had not received wide circulation and points interested readers to it as well.

Here is where to find the actual documents: these online file names point to the full specifications for all eight new options.

§4References