Dismiss
IP.com applications will be updated on Sunday, March 5, from 11 am to 2 pm ET, to add new functionality and content. You may experience brief service interruptions during this period. We apologize for any inconvenience.
Browse Prior Art Database

Telnet X.3 PAD option (RFC1053)

IP.com Disclosure Number: IPCOM000001860D
Original Publication Date: 1988-Apr-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 18 page(s) / 45K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Levy: AUTHOR [+2]

Abstract

Status of this Memo

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

Network Working Group S. Levy

Request for Comments: 1053 T. Jacobson

Minnesota Supercomputer Center

April 1988

Telnet X.3 PAD Option

Status of this Memo

This RFC proposes a new option to Telnet for the Internet community,

and requests discussion and suggestions for improvements.

Distribution of this memo is unlimited.

1. Command name and code

X.3-PAD 30

2. Command meanings

IAC DO X.3-PAD

The issuing telnet requests that its peer perform X.3-PAD

functions, or accepts an offer to do so.

IAC DON'T X.3-PAD

The issuing telnet demands that its peer not perform or cease

performing X.3-PAD functions.

IAC WILL X.3-PAD

The issuing telnet offers to perform X.3-PAD functions or confirms

that it will do so.

IAC WON'T X.3-PAD

The issuing telnet refuses to perform X.3-PAD functions or

indicates that it is ceasing to handle them.

Typically a server (host) telnet will use DO and DON'T, while a

client (user) telnet will use WILL and WON'T. For convenience, in

the rest of this RFC 'host' and 'user' telnets refer to those saying

'DO X.3-PAD' or 'WILL X.3-PAD' respectively.

Both telnet peers may use this option without confusion, as all

messages unambiguously identify whether they come from the host

("DO") or the user ("WILL") side.

Once DO and WILL have been exchanged, the host ("DO") telnet may

send the following messages:

IAC SB X.3-PAD SET ... IAC SE

IAC SB X.3-PAD RESPONSE-SET ... IAC SE

IAC SB X.3-PAD SEND IAC SE

while the user ("WILL") telnet may send the following messages:

IAC SB X.3-PAD IS ... IAC SE

IAC SB X.3-PAD RESPONSE-IS ... IAC SE

The code for SET is 0

The code for RESPONSE-SET is 1

The code for IS is 2

The code for RESPONSE-IS is 3

The code for SEND is 4

Messages listing parameter-value pairs may contain any number of

such pairs, including zero. Each parameter and each value

occupies one octet, except that 255 (IAC) is doubled wherever it

appears.

3. Default conditions

The initial state is DON'T X.3-PAD, WON'T X.3-PAD. This RFC does not

specify default values for most X.3 parameters. If the host telnet

wishes a particular initial state (as it normally will), it should

negotiate for it after exchange of DO/WILL messages.

X.3-PAD parameter values need not be preserved except when DO/WILL

X.3-PAD is in effect. Thus if a host enables ("DO") X.3-PAD,

negotiates about some parameters, then for some reason disables

("DONT") and later re-enables X.3-PAD, it must renegotiate any

parameters it cares about.

Keeping in mind that the host telnet m...