| 1 |
<pre>Network Working Group R. Nedved |
| 2 |
Request for Comments: 946 Carnegie-Mellon University |
| 3 |
May 1985 |
| 4 |
|
| 5 |
<span class="h1">TELNET TERMINAL LOCATION NUMBER OPTION</span> |
| 6 |
|
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This RFC proposes a new option for Telnet for the ARPA-Internet |
| 11 |
community, and requests discussion and suggestions for improvements. |
| 12 |
Distribution of this memo is unlimited. |
| 13 |
|
| 14 |
Overview |
| 15 |
|
| 16 |
In a community of users that share a large degree of common |
| 17 |
facilities, it is often advantageous to use some common feature to |
| 18 |
improve software performance and reduce initial implementation costs. |
| 19 |
|
| 20 |
In March of 1982, CMU designed and implemented based on the growing |
| 21 |
CMU PUP-based network a terminal location database and modified |
| 22 |
existing network software to handle a 64-bit number which some call |
| 23 |
the Terminal Location Number or TTYLOC for short. The number can be |
| 24 |
efficiently stored in operating systems tables and can be passed |
| 25 |
between various levels of operating system and network layering with |
| 26 |
minimum modifications to existing software. An initial evaluation of |
| 27 |
changing software to communicate an unfixed or reasonable length |
| 28 |
terminal location string indicated it would be expensive. |
| 29 |
|
| 30 |
CMU now wishes to extend this mechanism into the TCP-based networking |
| 31 |
support that is replacing the existing PUP-based software. The |
| 32 |
mechanism is not viewed as a replacement for the Telnet Terminal |
| 33 |
Location (SEND-LOCATION) Option but as a shorthand mechansim for |
| 34 |
communicating hosts in the same community. |
| 35 |
|
| 36 |
TTYLOC Number |
| 37 |
|
| 38 |
The TTYLOC number is a 64-bit number composed of two (2) 32-bit |
| 39 |
numbers: The 32-bit official ARPA Internet host address (may be any |
| 40 |
one of the addresses for multi-homed hosts) and a 32-bit number |
| 41 |
representing the terminal on the specified host. The host address of |
| 42 |
[0.0.0.0] is defined to be "unknown", the terminal number of FFFFFFFF |
| 43 |
(hex, r or-1 in decimal) is defined to be "unknown" and the terminal |
| 44 |
number of FFFFFFFE (hex, or -2 in decimal) is defined to be |
| 45 |
"detached" for processes that are not attached to a terminal. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
|
| 53 |
|
| 54 |
<span class="grey">Nedved [Page 1]</span></pre> |
| 55 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 56 |
<span class="grey"><a href="./rfc946">RFC 946</a> May 1985</span> |
| 57 |
Telnet Terminal Location Number Option |
| 58 |
|
| 59 |
|
| 60 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Command Name and Option Code</span> |
| 61 |
|
| 62 |
TTYLOC 28 |
| 63 |
|
| 64 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Command Meanings</span> |
| 65 |
|
| 66 |
IAC WILL TTYLOC |
| 67 |
|
| 68 |
The sender offers to send the TTYLOC information or confirms that |
| 69 |
it can send the TTYLOC information. |
| 70 |
|
| 71 |
IAC WON'T TTYLOC |
| 72 |
|
| 73 |
The sender refuses to send the TTYLOC information. |
| 74 |
|
| 75 |
IAC DO TTYLOC |
| 76 |
|
| 77 |
The sender requests to receive the TTYLOC information or confirms |
| 78 |
that it will receive the TTYLOC information. |
| 79 |
|
| 80 |
IAC DON'T TTYLOC |
| 81 |
|
| 82 |
The sender refuses to receive the TTYLOC information. |
| 83 |
|
| 84 |
IAC SB TTYLOC <format> <TTYLOC number with IAC doubling> IAC SE |
| 85 |
|
| 86 |
The sender is transmitting the TTYLOC information. The 64-bit |
| 87 |
TTYLOC number has format 0. The first 32-bits is the Internet host |
| 88 |
number and the second 32-bits is the line on the specified |
| 89 |
Internet host. The bytes are in most significant 8-bit byte to |
| 90 |
least significant byte order. |
| 91 |
|
| 92 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Default Specification</span> |
| 93 |
|
| 94 |
WON'T TTYLOC |
| 95 |
|
| 96 |
TTYLOC information will not be sent. |
| 97 |
|
| 98 |
DON'T TTYLOC |
| 99 |
|
| 100 |
TTYLOC information will not be received. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
|
| 109 |
<span class="grey">Nedved [Page 2]</span></pre> |
| 110 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 111 |
<span class="grey"><a href="./rfc946">RFC 946</a> May 1985</span> |
| 112 |
Telnet Terminal Location Number Option |
| 113 |
|
| 114 |
|
| 115 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Motivation</span> |
| 116 |
|
| 117 |
Many systems provide a mechanism for finding out where a user is |
| 118 |
logged in from usually including information about telephone |
| 119 |
extension and office occupants names. The information is useful for |
| 120 |
physically locating people and/or calling them on the phone. |
| 121 |
|
| 122 |
For incoming network connections to a host, only the remote host's |
| 123 |
name is available. This option and the Telnet Terminal Location |
| 124 |
option (<a href="./rfc779">RFC-779</a>) provide the information to the system so it in turn |
| 125 |
can provide the information to the various mechanisms (FINGER, WHOIS, |
| 126 |
etc.). |
| 127 |
|
| 128 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Description of the Option</span> |
| 129 |
|
| 130 |
When the user Telnet connects to a remote host, it can attempt to |
| 131 |
send the terminal location number information by doing a |
| 132 |
IAC WILL TTYLOC command. If the Telnet server can use the |
| 133 |
information, it replies with a IAC DO TTYLOC command. The user Telnet |
| 134 |
then sends the TTYLOC number in the subnegotiation. |
| 135 |
|
| 136 |
It is recommended that if sending the TTYLOC number is refused then |
| 137 |
the Telnet Terminal Location (SEND-LOCATION in <a href="./rfc779">RFC-779</a>) should be |
| 138 |
attempted. |
| 139 |
|
| 140 |
The following are two example usage scenarios: |
| 141 |
|
| 142 |
User Side First: |
| 143 |
|
| 144 |
(User) Host1: IAC WILL TTYLOC |
| 145 |
|
| 146 |
Host1 is asking if it can send the 64-bit terminal location |
| 147 |
number (I will send...). |
| 148 |
|
| 149 |
(Server) Host2: IAC DO TTYLOC |
| 150 |
|
| 151 |
Host2 indicates to Host1 that it will accept the 64-bit |
| 152 |
terminal location number in a subnegotiation (You please do |
| 153 |
...). |
| 154 |
|
| 155 |
(User) Host1: IAC SB TTYLOC 0 <64-bit number> IAC SE |
| 156 |
|
| 157 |
Host1 is sending the location number to Host2 which can |
| 158 |
communicate the number to the operating system or other |
| 159 |
system components. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Nedved [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc946">RFC 946</a> May 1985</span> |
| 167 |
Telnet Terminal Location Number Option |
| 168 |
|
| 169 |
|
| 170 |
Server Side First: |
| 171 |
|
| 172 |
(Server) HostA: IAC DO TTYLOC |
| 173 |
|
| 174 |
HostA indicates to HostB that it would like to know the |
| 175 |
64-bit terminal location number (You please do ...). |
| 176 |
|
| 177 |
(User) HostB: IAC WILL TTYLOC |
| 178 |
|
| 179 |
HostB agrees to send the 64-bit terminal location number to |
| 180 |
HostA in a subnegotiation (I will send...). |
| 181 |
|
| 182 |
(User) HostB: IAC SB TTYLOC 0 <64-bit number> IAC SE |
| 183 |
|
| 184 |
HostB is sending the location number to HostA which can |
| 185 |
communicate the number to the operating system or other |
| 186 |
system components. |
| 187 |
|
| 188 |
|
| 189 |
|
| 190 |
|
| 191 |
|
| 192 |
|
| 193 |
|
| 194 |
|
| 195 |
|
| 196 |
|
| 197 |
|
| 198 |
|
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
Nedved [Page 4] |
| 220 |
</pre> |