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

  
        RFC 1334:


        Title:      PPP Authentication Protocols
        Author:     Lloyd & Simpson
        Mailbox:    brian@lloyd.com, Bill.Simpson@um.cc.umich.edu
        Pages:      16
        Characters: 33,248
        Updates/Obsoletes:  none


The Point-to-Point Protocol (PPP) provides a standard method of
encapsulating Network Layer protocol information over point-to-point
links.  PPP also defines an extensible Link Control Protocol, which
allows negotiation of an Authentication Protocol for authenticating
its peer before allowing Network Layer protocols to transmit over the
link.

This document defines two protocols for Authentication: the Password
Authentication Protocol and the Challenge-Handshake Authentication
Protocol.  This memo is the product of the Point-to-Point Protocol
Working Group of the Internet Engineering Task Force (IETF).

This is now a Proposed Standard Protocol.

This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
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@NRI.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 retreive the ASCII version
of the Internet Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mail-server@nisc.sri.com"

Content-Type: text/plain

SEND rfc1334.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1334.txt";
        site="nnsc.nsf.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain

--OtherAccess--
--NextPart--