Internet DRAFT - draft-ietf-l2tpext-rfc2661-iana

draft-ietf-l2tpext-rfc2661-iana



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


        BCP 68
        RFC 3438

        Title:      Layer Two Tunneling Protocol (L2TP) Internet
                    Assigned Numbers Authority (IANA) Considerations
                    Update
        Author(s):  W. Townsley
        Status:     Best Current Practice
        Date:       December 2002
        Mailbox:    mark@townsley.net
        Pages:      5
        Characters: 9135
        SeeAlso:    BCP 68

        I-D Tag:    draft-ietf-l2tpext-rfc2661-iana-01.txt

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


This document describes updates to the Internet Assigned Numbers
Authority (IANA) considerations for the Layer Two Tunneling Protocol
(L2TP).

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

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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.