Browse Prior Art Database

Telnet Suppress Go Ahead Option (RFC0858)

IP.com Disclosure Number: IPCOM000003905D
Original Publication Date: 1983-May-01
Included in the Prior Art Database: 2019-Feb-14
Document File: 2 page(s) / 3K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR [+1]

Related Documents

10.17487/RFC0858: DOI

Abstract

This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15392.

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

Network Working Group J. Postel Request for Comments: 858 J. Reynolds ISI Obsoletes: NIC 15392 May 1983

TELNET SUPPRESS GO AHEAD OPTION

This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard.

1. Command Name and Code

SUPPRESS-GO-AHEAD 3

2. Command Meanings

IAC WILL SUPPRESS-GO-AHEAD

The sender of this command requests permission to begin suppressing transmission of the TELNET GO AHEAD (GA) character when transmitting data characters, or the sender of this command confirms it will now begin suppressing transmission of GAs with transmitted data characters.

IAC WON’T SUPPRESS-GO-AHEAD

The sender of this command demands to begin transmitting, or to continue transmitting, the GA character when transmitting data characters.

IAC DO SUPPRESS-GO-AHEAD

The sender of this commannd requests that the sender of data start suppressing GA when transmitting data, or the sender of this command confirms that the sender of data is expected to suppress transmission of GAs.

IAC DON’T SUPPRESSS-GO-AHEAD

The sender of this command demands that the receiver of the command start or continue transmitting GAs when transmitting data.

3. Default

WON’T SUPPRESS-GO-AHEAD

DON’T SUPPRESS-GO-AHEAD

Go aheads are transmitted.

Postel & Reynolds [Page 1]

RFC 858 May 1983

4. Motivation for the Option

While the NVT nominally follows a half duplex protocol complete with a GO AHEAD signal, there is no reason why a full duplex connection between a full duplex terminal and a host optimized to handle full duplex terminals should be burdened with the GO AHEAD signal. Therefore, it is desirable to have a TELNET option with which parties involved can agree that one or the other or both should suppress transmission of GO AHEADS.

5. Description of the Option

When the SUPPRESS-GO-AHEAD option is in effect on the connection between a s...

Processing...
Loading...