💾 Archived View for gmi.noulin.net › rfc › rfc779.gmi captured on 2022-04-28 at 22:36:58. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-12-05)

➡️ Next capture (2023-01-29)

-=-=-=-=-=-=-

Keywords: [TOPT-SNDL|p]








Network Working Group                                         E. Killian
Request for Comments: 779                                            LLL
                                                              April 1981



                      TELNET SEND-LOCATION Option




1.  Command name and code.

   SEND-LOCATION   23

2.  Command meanings.

   IAC WILL SEND-LOCATION

      The sender REQUESTS or AGREES to use the SEND-LOCATION option to
      send the user's location.

   IAC WON'T SEND-LOCATION

      The sender REFUSES to use the SEND-LOCATION option.

   IAC DO SEND-LOCATION

      The sender REQUESTS that, or AGREES to have, the other side use
      SEND-LOCATION commands send the user's location.

   IAC DON'T SEND-LOCATION

      The sender DEMANDS the other side not use the SEND-LOCATION
      option.

   IAC SB SEND-LOCATION <location> IAC SE

      The sender specifies the user's location to the other side via a
      SEND-LOCATION subnegotiation.  <location> is a sequence of ASCII
      printable characters; it is terminated by the IAC SE.

3.  Default.

   WON'T SEND-LOCATION

   DON'T SEND-LOCATION



Killian                                                         [page 1]


RFC 779                                                       April 1981
TELNET SEND-LOCATION Option



4.  Motivation for the option.

   Many network sites now provide a listing of the users currently
   logged in giving their names and locations (see the NAME/FINGER
   protocol, RFC 742).  The location is useful for physically locating
   the user if he or she is nearby, or for calling them (a nearby phone
   number is often included). However, for users logged in via the
   network, the location printed is often no more than the originating
   site name. This TELNET option allows the user's TELNET program to
   send the user's location to the server TELNET so that it can be
   displayed in addition to the site name.  This functionality is
   already present in the SUPDUP protocol (RFC 734).

5.  Description of the option.

   When the user TELNET program knows the user's location, it should
   offer to transmit this information to the server TELNET by sending
   IAC WILL SEND-LOCATION.  If the server's system is able to make use
   of this information (as can the ITS sites), then the server will
   reply with IAC DO SEND-LOCATION.  The user TELNET is then free to
   send the location in a subnegotiation at any time.





























Killian                                                         [page 2]