RFC1416 on Telnet Authentication Option

"Joyce K. Reynolds" <jkrey@isi.edu> Mon, 01 February 1993 23:08 UTC

Message-Id: <199302012309.AA08339@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1416 on Telnet Authentication Option
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 01 Feb 1993 15:09:22 -0800
Sender: List Manager <Postmaster@CNRI.Reston.VA.US>
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.



        RFC 1416:

        Title:      Telnet Authentication Option
        Author:     D. Borman, Editor
        Mailbox:    dab@CRAY.COM
        Pages:      7
        Characters: 13,270 
        Obsoletes:  1409


This RFC 1416 replaces RFC 1409, which has an important typographical
error in the example on page 6 (one occurance of "REPLY" should be
"IS").

One of the deficiencies of the Telnet protocol is that in order to log
into remote systems, users have to type their passwords, which are
passed in clear text through the network.  If the connections goes
through untrusted networks, there is the possibility that passwords
will be compromised by someone watching the packets as they go by.
The purpose of the AUTHENTICATION option is to provide a framework for
the passing of authentication information through the TELNET session.
This memo is the product of the Telnet Working Group of the Internet
Engineering Task Force (IETF).

This memo defines an Experimental Protocol for the Internet community.
Discussion and suggestions for improvement are requested.  Please
refer to the current edition of the "IAB Official Protocol Standards"
for the standardization state and status of this protocol.
Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://nic.ddn.mil/rfc/rfc1416.txt"><ftp://nic.ddn.mil/rfc/rfc1416.txt>

RFC1416 on Telnet Authentication Option Joyce K. Reynolds