Browse Prior Art Database

Telnet byte macro option (RFC0729)

IP.com Disclosure Number: IPCOM000003775D
Original Publication Date: 1977-May-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 4 page(s) / 5K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Crocker: AUTHOR

Related Documents

10.17487/RFC0729: DOI

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Network Working Group Dave Crocker, Rand-ISD Request for Comments: 729 (Dcrocker at Rand-Unix) NlC: 40306 13 May l977

TELNET Byte Macro Option

1. Command name and code:

BM 19

2. Command Meanings:

IAC WILL BM

The sender of this command REQUESTS or AGREES to use the BM option, and will send sing1e data characters which are to be interpreted as if longer data strings had been sent.

IAC WON’T BM

The sender of this option REFUSES to send single data characters which are to be interpreted as if longer data strings had been sent.

IAC DO BM

The sender REQUESTS or AGREES to have the other side (send of WILL BM) issue send single data characters which are to be interpreted as if longer data strings had been sent.

IAC DON’T BM

The sender REFUSES to allow the other side to send single data characters which are to be interpreted as if longer data strings had been sent.

IAC SB BM <DEFINE> <macro byte> <count> <expansion string> IAC SE where:

<macro byte> is the data byte actually to be sent across the network; it may NOT be Telnet IAC (decimal 255).

RFC #729 Telnet Byte Macro Option Page 2

<count> is a one-byte binary number, indicating how many <expansion string> characters follow, up to the ending IAC SE, but not including it.

<expansion string> is a string of one or more Telnet ASCII characters and/or commands, which the <macro byte> is to represent; any character may occur within an <expansion string>.

The indicated <macro byte> will be sent instead of the indicated <expansion string>. The receiver of the <macro byte> (the sender of the DO BM) is to behave EXACTLY as if the <expansion string> of bytes had instead been received from the network. This interpretation is to occur before any other Telnet interpretations, unless the <macro byte> occurs as part of a BM subcommand; in this case no special interpretation is to be made.

Note that the effect of a particular <macro byte> may be negated by reseting it to "expand" into itself.

<DEFINE> is decimal 01.

IAC SB BM <ACCEPT> <macro byte> IAC SE

The receiver of the <DEFINE> for <macro byte> accepts the requested definition and will perform the indicating expansion whenever a <macro byte> is received and is not part of a BM subcommand.

<ACCEPT> is decimal 02.

IAC SB BM <REFUSE> <macro byte> <REASON> IAC SE

The receive of the <DEFINE> for <macro byte> refuses to perform the indicated translation from <macro byte> to <expansion string> either because the particular <macro byte> is not an acceptable choice or because the length of the <expansion string> exceeds available storage.

<REFUSE> is decimal 03.

<REASON> may be

<BAD CHOICE> which is decimal 01; or

<TOO LONG> which is decimal 02.

RFC #729 Telnet Byte Macro Option Page 3

IAC SB BM <LITERAL> <macro byte> IAC SE

The <macro byte> is to be treated as real data, rather than as representative of the <expansion string>

<LITERAL> is decimal 03.

3. Default:

WON’T BM -- DON’T BM

No reinterpretation of data is allowed.

4. Motivation for the option:

Subcommands for...

Processing...
Loading...