[rfc-dist] RFC 3301 on Layer Two Tunnelling Protocol (L2TP): ATM access network extensions

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Wed, 19 Jun 2002 10:17:37 -0700


--NextPart


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


        RFC 3301

        Title:	    Layer Two Tunnelling Protocol (L2TP): 
                    ATM access network extensions
        Author(s):  Y. T'Joens, P. Crivellari, B. Sales
        Status:	    Standards Track
	Date:       June 2002
        Mailbox:    yves.tjoens@alcatel.be,
                    paolo.crivellari@alcatel.be,
                    bernard.sales@alcatel.be 
        Pages:      19
        Characters: 42756
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-l2tpext-atmext-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3301.txt


This document augments the procedures described in RFC 2661 to further
support ATM SVC (Switched Virtual Circuits) or PVC (Permanent Virtual
Circuits) based access networks.  L2TP (Layer 2 Tunneling Protocol)
specifies a protocol for tunnelling PPP packets over packet based
networks and over IP networks in particular.  L2TP supports remote
access by ISDN and PSTN networks.  The extensions defined within this
document allow for asymmetric bi-directional call establishment and
service selection in the ATM access network.  

This document is a product of the Layer Two Tunneling Protocol
Extensions Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
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.

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

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <020619101511.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3301

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3301.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <020619101511.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--