RFC 654 HISTORIC TELNET · FORMATTING

Telnet output horizontal tab disposition option

Deciding who handles horizontal tab characters in Telnet output.

On rfc-editor.org ↗
PUBLISHED
October 1974
AUTHORS
D. Crocker
STREAM
Legacy
OPTION CODE
12
SUBNEGOTIATION CODES
DS = 1 (sender), DR = 0 (receiver)
DISPOSITION VALUE RANGE
0 to 255
DOI
10.17487/RFC0654

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION
RFC 654, NIC 31157 (Oct. 25, 1974)
D. Crocker (UCLA-NMC)
Online file: [ISI]<DCROCKER>NAOHTD.TXT

           TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION

1. Command name and code
   NAOHTD 12
      (Negotiate About Output Horizontal Tab Disposition)

2. Command meanings
   In the following, we are discussing a simplex connection, as described in
   the NAOL and NAOP Telnet options.
      IAC DO NAOHTD
         The data sender requests or agrees to negotiate about output
         horizontal tab character disposition with the data receiver.  In the
         case where agreement has been reached and in the absence of further
         subnegotiations, the data receiver is assumed to be handling output
         horizontal tab character considerations.
      IAC DON'T NAOHTD
         The data sender refuses to negotiate about output horizontal tab
         characters with the data receiver, or demands a return to the
         unnegotiated default mode.
      IAC WILL NAOHTD
         The data receiver requests or agrees to negotiate about output
         horizontal tab characters with the sender. In the case where
         agreement has been reached and in the absence of further
         subnegotiations, the data receiver alone is assumed to be handling
         output horizontal tab character considerations.
      IAC WON'T NAOHTD
         The data receiver refuses to negotiate about output horizontal tab
         characters, or demands a return to the unnegotiated default mode.
      IAC SB NAOHTD DS <8-bit value> IAC SE
         The data sender specifies, with the 8-bit value, which party should
         handle output horizontal tab characters and what their disposition
         should be.  The code for DS is 1.
      IAC SB NAOHTD DR <8-bit value> IAC SE
         The data receiver specifies, with the 8-bit value, which party
         should handle output horizontal tab characters and what their
         disposition should be.  The code for DR is 0.

3. Default
   DON'T NAOHTD/WON'T NAOHTD.
      In the default absence of negotiations concerning which party, data
      sender or data receiver, is handling output horizontal tab character
      considerations, neither party is required to handle horizontal tab
      characters and neither party is prohibited from handling them; but it
      is appropriate if at least the data receiver handles horizontal tab
      character considerations, albeit primitively.

4. Motivation for the Option
   Please refer to section 4 of the NAOL and of the NAOP Telnet option
   descriptions.

5. Description of the Option
   The data sender and the data receiver use the 8-bit value along with the
   DS and DR SB commands as follows:

      8-bit value                      Meaning

      0            Command sender suggests that he alone will handle
                   horizontal tab characters, for the connection.
      1 to 250     Command sender suggests that the other party alone
                   should handle horizontal tab characters, but
                   suggests that a delay of the indicated value be
                   used. The value is the number of character-times
                   to wait or number of NULs to insert in the data
                   stream before sending the next data character.
      251          Command sender suggests that the other party alone
                   handle horizontal tabs, but suggests that each
                   occurrence of the character be replaced by a space.
      252          Command sender suggests that the other party alone
                   handle horizontal tabs, but suggests that they be
                   discarded.
      253          Command sender suggests that the other party alone
                   should handle horizontal tab characters, but
                   suggests that tabbing be simulated.
      254          Command sender suggests that the other party alone
                   should handle horizontal tab characters, but
                   suggests that waiting for a character to be
                   transmitted (on the other simplex connection)
                   before sending more data. Note that, due to the
                   assynchrony of the two simplex connections, phase
                   problems can occur with this option.
      255          Command sender suggests that the other party alone
                   should handle output horizontal tabs and suggests
                   nothing about how it should be done.

   The guiding rules are that:

      1) if neither data receiver nor data sender wants to handle output
      horizontal tab characters, the data receiver must do it, and
      2) if both data receiver and data sender wants to handle output
      horizontal tab characters, the data sender gets to do it.

   The reasoning for the former rule is that if neither wants to do it, then
   the default in the NAOHTD option dominates.  If both want to do it, the
   sender, who is presumed to have special knowledge about the data, should
   be allowed to do it, taking into account any suggestions the receiver may
   make.  Simulation is defined as the replacement of the horizontal tab
   character by enough spaces to move the printer head (or line-pointer) to
   the next horizontal tab stop.
   Note that delays, controlled by the data sender, must consist of NUL
   characters inserted immediately after the horizontal tab character.  This
   is necessary due to the assynchrony of network transmissions.  As with
   all option negotiations, neither party should suggest a state already in
   effect except to refuse to negotiate; changes should be acknowledged; and
   once refused, an option should not be resuggested until "something
   changes" (e.g., another process starts).  At any time, either party can
   disable further negotiation by giving the appropriate WON'T NAOHTD or
   DON'T NAOHTD command.

AI ELI5

On this page
PROBLEMWhen a tab character is sent over Telnet, the receiving system must decide what to do with it: pass it through, replace it with spaces or a delay, or discard it. The two sides need to agree on the handling.
MECHANISMThe option lets the sender and receiver negotiate via Telnet commands. Each side proposes how it wants to handle tabs—ignore them, simulate them with spaces, discard them, delay after them, or wait for a response from the other direction. Values 0 to 255 encode the different strategies.
HISTORICBoth sides know how incoming tab characters will be processed. The RFC is Historic and no longer widely used in practice.

§1The Telnet Tab Character Disposition Option

RFC 654 defines the NAOHTD option (Negotiate About Output Horizontal Tab Disposition), a Telnet option for handling the horizontal tab character (ASCII 9) when it appears in output. Unlike RFC 653, which specifies where tabs land, this RFC specifies what happens to a tab character: whether it is sent as-is, replaced with spaces, discarded, or treated some other way. Different terminals and systems handle tabs differently, so negotiation is needed.

Computers need to agree: when a Tab character arrives, what should happen—send it to the printer, turn it into spaces, skip it, or pause after it?

§2Tab Disposition Strategies

The option defines eight strategies, encoded as values 0 to 255 in subnegotiation messages. A value of 0 means the sender will handle the tab (process it itself). Values 1 to 250 mean the receiver should handle it, with a delay (the value is the number of NUL characters to insert after the tab to slow output). Value 251 means replace the tab with a space. Value 252 means discard the tab entirely. Value 253 means simulate the tab by calculating the next tab stop and inserting spaces to reach it. Value 254 means wait for a character on the opposite connection before continuing (a flow-control technique). Value 255 means the receiver should handle it but with no specific instruction.

The key rule: if both sides want to handle tabs, the sender wins. If neither wants to, the receiver must.

The option has eight choices: 0 means I will handle it; 1-250 means handle it and wait that long; 251 means turn it into a space; 252 means delete it; 253 means simulate it with spaces; 254 means wait for a reply first; 255 means you handle it your way.

§3Choosing and Applying the Disposition

The negotiation process mirrors RFC 653: both sides exchange DO, WILL, DON'T, and WON'T commands, then use subnegotiation (IAC SB) to propose a value. The sender uses code DS (1) and the receiver uses code DR (0). Once agreement is reached on a disposition, all tab characters are handled that way until one side requests a change or refuses negotiation. The RFC notes that for delay-based methods, the delay is implemented by inserting NUL bytes (null characters) immediately after the tab to slow the network transmission.

Both sides negotiate using the standard Telnet commands, agree on a disposition value, and then apply it to every Tab that arrives until they negotiate again.

§4References