Browse Prior Art Database

Output marking Telnet option (RFC0933)

IP.com Disclosure Number: IPCOM000004349D
Original Publication Date: 1985-Jan-01
Included in the Prior Art Database: 2000-Oct-11
Document File: 4 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Silverman: AUTHOR

Abstract

Status of this Memo

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

Network Working Group S. Silverman

Request for Comments: 933 MITRE-Washington

January 1985

OUTPUT MARKING TELNET OPTION

Status of this Memo

This RFC proposes a new option for Telnet for the ARPA-Internet

community, and requests discussion and suggestions for improvements.

Distribution of this memo is unlimited.

Overview

This proposed option would allow a Server-Telnet to send a banner to

a User-Telnet so that this banner would be displayed on the

workstation screen independently of the application software running

in the Server-Telnet.

1. Command Name and Code

OUTMRK 27

2. Command Meanings

IAC WILL OUTMRK

Sender is willing to send output marking information in a

subsequent sub-negotiation.

IAC WON'T OUTMRK

Sender refuses to send output marking information.

IAC DO OUTMRK

Sender is willing to receive output marking information in a

subsequent sub-negotiation.

IAC DON'T OUTMRK

Sender refuses to accept output marking information.

IAC SB OUTMRK CNTL data IAC SE

The sender requests receiver to use the data in this

subnegotiation as a marking for the normally transmitted Telnet

data until further notice. The CNTL octet indicates the position

of the marking (see below).

RFC 933 January 1985

Output Marking Telnet Option

IAC SB OUTMRK ACK IAC SE

The sender acknowledges the data and agrees to use it to perform

output marking (see below).

IAC SB OUTMRK NAK IAC SE

The sender objects to using the data to perform output marking

(see below).

3. Default

WON'T OUTMRK

Output marking information will not be exchanged.

DON'T OUTMRK

Output marking information will not be exchanged.

4. Motivation for the Option

The security architecture of some military systems identifies a

security level with each Telnet connection. There is a corresponding

need to display a security banner on visual display devices.

(Reference: Department of Defense Trusted Computer System Evaluation

Criteria, Section 3.1.1.3.2.3, Labeling Human-Readable Output.)

The output marking is currently done by transmitting the banner as

data within each screen of data. It would be more efficient to

transmit the data once with instructions and have User-Telnet

maintain the banner automatically without any additional

Server-Telnet action. This frees Server-Telnet from ne...