| 1 |
<pre>Network Working Group C. Hedrick |
| 2 |
Request for Comments: 1079 Rutgers University |
| 3 |
December 1988 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Telnet Terminal Speed Option</span> |
| 7 |
|
| 8 |
Status of This Memo |
| 9 |
|
| 10 |
This RFC specifies a standard for the Internet community. Hosts on |
| 11 |
the Internet that exchange terminal speed information within the |
| 12 |
Telnet protocol are expected to adopt and implement this standard. |
| 13 |
Distribution of this memo is unlimited. |
| 14 |
|
| 15 |
This standard is modelled on <a href="./rfc930">RFC 930</a> [<a href="#ref-1" title=""Telnet Terminal Type Option"">1</a>], the telnet terminal type |
| 16 |
option. Much of the text of this document is copied from that RFC. |
| 17 |
|
| 18 |
Motivation |
| 19 |
|
| 20 |
Most operating systems have provisions to keep track of the speed |
| 21 |
(bit rate) of directly attached terminals and modems. This |
| 22 |
information is used to control various timing-dependent display |
| 23 |
processes, e.g., the number of padding characters used for delay. |
| 24 |
Some software also has user interfaces that are tuned differently for |
| 25 |
fast and slow terminals. The purpose of this option is to provide |
| 26 |
similar information for telnet connections. |
| 27 |
|
| 28 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Command Name and Code</span> |
| 29 |
|
| 30 |
TERMINAL-SPEED |
| 31 |
|
| 32 |
Code = 32 |
| 33 |
|
| 34 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Command Meanings</span> |
| 35 |
|
| 36 |
IAC WILL TERMINAL-SPEED |
| 37 |
|
| 38 |
Sender is willing to send terminal speed information in a |
| 39 |
subsequent sub-negotiation. |
| 40 |
|
| 41 |
IAC WON'T TERMINAL-SPEED |
| 42 |
|
| 43 |
Sender refuses to send terminal speed information. |
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
<span class="grey">Hedrick [Page 1]</span></pre> |
| 51 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 52 |
<span class="grey"><a href="./rfc1079">RFC 1079</a> Telnet Terminal Speed Option December 1988</span> |
| 53 |
|
| 54 |
|
| 55 |
IAC DO TERMINAL-SPEED |
| 56 |
|
| 57 |
Sender is willing to receive terminal speed information in a |
| 58 |
subsequent sub-negotiation. |
| 59 |
|
| 60 |
IAC DON'T TERMINAL-SPEED |
| 61 |
|
| 62 |
Sender refuses to accept terminal speed information. |
| 63 |
|
| 64 |
IAC SB TERMINAL-SPEED SEND IAC SE |
| 65 |
|
| 66 |
Sender requests receiver to transmit his (the receiver's) |
| 67 |
terminal speed. The code for SEND is 1. (See below.) |
| 68 |
|
| 69 |
IAC SB TERMINAL-SPEED IS ... IAC SE |
| 70 |
|
| 71 |
Sender is stating his terminal speed. The code for IS is 0. |
| 72 |
(See below.) |
| 73 |
|
| 74 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Default</span> |
| 75 |
|
| 76 |
WON'T TERMINAL-SPEED |
| 77 |
|
| 78 |
Terminal speed information will not be exchanged. |
| 79 |
|
| 80 |
DON'T TERMINAL-SPEED |
| 81 |
|
| 82 |
Terminal speed information will not be exchanged. |
| 83 |
|
| 84 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Description of the Option</span> |
| 85 |
|
| 86 |
WILL and DO are used only to obtain and grant permission for future |
| 87 |
discussion. The actual exchange of status information occurs within |
| 88 |
option subcommands (IAC SB TERMINAL-SPEED...). |
| 89 |
|
| 90 |
Once the two hosts have exchanged a WILL and a DO, the sender of the |
| 91 |
DO TERMINAL-SPEED is free to request speed information. Only the |
| 92 |
sender of the DO may send requests (IAC SB TERMINAL-SPEED SEND IAC |
| 93 |
SE) and only the sender of the WILL may transmit actual speed |
| 94 |
information (within an IAC SB TERMINAL-SPEED IS ... IAC SE command). |
| 95 |
Terminal speed information may not be sent spontaneously, but only in |
| 96 |
response to a request. |
| 97 |
|
| 98 |
The terminal speed information is an NVT ASCII string. This string |
| 99 |
contains the decimal representation of the transmit and receive |
| 100 |
speeds of the terminal, separated by a comma, e.g., |
| 101 |
|
| 102 |
9600,100 |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
<span class="grey">Hedrick [Page 2]</span></pre> |
| 107 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 108 |
<span class="grey"><a href="./rfc1079">RFC 1079</a> Telnet Terminal Speed Option December 1988</span> |
| 109 |
|
| 110 |
|
| 111 |
No leading zeros may be included. No extraneous characters such as |
| 112 |
spaces may be included. |
| 113 |
|
| 114 |
The following is an example of use of the option: |
| 115 |
|
| 116 |
Host1: IAC DO TERMINAL-SPEED |
| 117 |
|
| 118 |
Host2: IAC WILL TERMINAL-SPEED |
| 119 |
|
| 120 |
(Host1 is now free to request status information at any time.) |
| 121 |
|
| 122 |
Host1: IAC SB TERMINAL-SPEED SEND IAC SE |
| 123 |
|
| 124 |
Host2: IAC SB TERMINAL-SPEED IS "1200,1200" IAC SE |
| 125 |
|
| 126 |
(This command is 15 octets.) |
| 127 |
|
| 128 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Suggestions</span> |
| 129 |
|
| 130 |
Many systems allow only certain discrete terminal speeds. In such |
| 131 |
cases it is possible that a speed may be received that does not match |
| 132 |
one of the allowed values. We suggest that you pick the nearest |
| 133 |
speed that is allowed, rounding in a "safe" direction. Safety will |
| 134 |
depend upon the use of the speed information. If it is being used |
| 135 |
for padding, it is best to round up, since too much padding is better |
| 136 |
than too little. |
| 137 |
|
| 138 |
Reference |
| 139 |
|
| 140 |
[<a id="ref-1">1</a>] Solomon, M., and Wimmers, E., "Telnet Terminal Type Option", |
| 141 |
<a href="./rfc930">RFC 930</a>, January, 1985 |
| 142 |
|
| 143 |
[AAuthor's Address: |
| 144 |
|
| 145 |
Charles Hedrick |
| 146 |
Rutgers University |
| 147 |
Center for Computer and Information Services |
| 148 |
Hill Center, Busch Campus |
| 149 |
P.O. Box 879 |
| 150 |
Piscataway, NJ 08855-0879 |
| 151 |
|
| 152 |
Phone: (201) 932-3088 |
| 153 |
|
| 154 |
Email: [email protected] |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
Hedrick [Page 3] |
| 163 |
</pre> |