From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001
From: Thomas Voss <mail@thomasvoss.com>
Date: Wed, 27 Nov 2024 20:54:24 +0100
Subject: doc: Add RFC documents

---
 doc/rfc/rfc779.txt | 117 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 117 insertions(+)
 create mode 100644 doc/rfc/rfc779.txt

(limited to 'doc/rfc/rfc779.txt')

diff --git a/doc/rfc/rfc779.txt b/doc/rfc/rfc779.txt
new file mode 100644
index 0000000..85884b7
--- /dev/null
+++ b/doc/rfc/rfc779.txt
@@ -0,0 +1,117 @@
+
+
+
+
+
+
+
+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]
+
\ No newline at end of file
-- 
cgit v1.2.3