HTTP/1.1 200 OK
Date: Tue, 09 Apr 2002 06:43:25 GMT
Server: Apache/1.3.20 (Unix)
Last-Modified: Tue, 08 Dec 1992 23:00:00 GMT
ETag: "304e2a-adc-2b2528f0"
Accept-Ranges: bytes
Content-Length: 2780
Connection: close
Content-Type: text/plain

--NextPart


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


        RFC 1377:

        Title:      The PPP OSI Network Layer Control Protocol
                    (OSINLCP)
        Author:     D. Katz
        Mailbox:    dkatz@cisco.com
        Pages:      10
        Characters: 22,109
        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, and
proposes a family of Network Control Protocols (NCPs) for establishing
and configuring different network-layer protocols.

This document defines the NCP for establishing and configuring OSI
Network Layer Protocols.  This memo is the product of the
Point-to-Point Protocol Working Group of the Internet Engineering Task
Force (IETF).

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 RFCs.

--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 rfc1377.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1377.txt";
        site="nic.ddn.mil";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain


--OtherAccess--
--NextPart--