Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Revised Telnet status option (RFC0651)

IP.com Disclosure Number: IPCOM000003716D
Original Publication Date: 1974-Oct-25
Included in the Prior Art Database: 2000-Sep-13
Document File: 2 page(s) / 4K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Crocker: AUTHOR

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 68% of the total text.

Revised Telnet Status Option

NIC 31154 (25 Oct. 74)

Request for Comments: 651

D. Crocker (UCLA-NMC) 25 Oct. 74

RFC# 651

Online file: <[ISI]STATUS-OPTION-REVISION.RNO

Revised Telnet Status Option

1. Command name and code

STATUS 5

2. Command meanings

As described in the NAOL and NAOP option specifications, this option applies

to a simplex connection.

IAC DO STATUS

Sender of DO wishes to be able to send requests for status-of-options

information, or confirms that he is willing to send such requests.

IAC WILL STATUS

Sender of WILL wishes or agrees to send status information,

spontaneously or in response to future requests.

IAC DON'T STATUS

Sender refuses to carry on any further discussion of the current

status of options.

IAC WON'T STATUS

Sender refuses to carry on any further discussion of the current

status of options.

IAC SB STATUS SEND IAC SE

Sender requests receiver to transmit his (the receiver's) perception

of the current status of Telnet options. The code for SEND is 1. (See

below.)

IAC SB STATUS IS ... IAC SE

Sender is stating his perception of the current status of Telnet

options. The code for IS is 0. (See below.)

3. Default

DON'T STATUS/WON'T STATUS. That is, the current status of options will not

be discussed.

4. Motivation for the option

This option allows a user/process to verify the current status of Telnet

options (e.g., echoing) as viewed by the person/process on the other end of

the Telnet connection. Simply renegotiating options could lead to the

nonterminating request loop problem discussed in (NIC #16237). The changes

to the option, described in this paper, allow STATUS to fit into the normal

structure of Telnet options, by deferring the actual transfer of status

information to the SB command. Additionally, the numbers of bytes that must

be sent to describe the state of the options has been considerably reduced.

5. Description of the option

WILL/DO are now used only to obtain and grant permission for future

discussion. The actual exchange of status information occurs within option

subcommands (IAC SB STATUS...).

Once the two hosts have exchanged a WILL and a DO, the sender of the WILL

STATUS is free to transmit status information, spontaneously or in response

to a request from the sender of the DO. At worst, this may lead to

transmitting the information twice. Only the sender of the DO may send

requests (IAC SB STATUS SEND IAC SE) and only the sender of the WILL may

transmit actual status information (within an IAC SB STATUS IS ... IAC SE

command).

IS has the subcommands WILL, DO and SB. They are used EXACTLY as used during

the actual negotiation of Telnet options, except that SB is terminated with

SE, rather than IAC SE. Transmission of SE, as a regular data byte, is

accomplished by doubling t...