[rfc-dist] RFC 4349 on High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 17 11:33:02 PST 2006


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

        
        RFC 4349

        Title:      High-Level Data Link Control (HDLC) 
                    Frames over Layer 2 Tunneling Protocol, 
                    Version 3 (L2TPv3) 
        Author:     C. Pignataro,  M. Townsley
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    cpignata at cisco.com, 
                    mark at townsley.net
        Pages:      11
        Characters: 22888
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2tpext-pwe3-hdlc-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4349.txt

The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a protocol 
for tunneling a variety of data link protocols over IP networks.  This 
document describes the specifics of how to tunnel High-Level Data 
Link Control (HDLC) frames over L2TPv3.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distributon.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...


--2c6d9d5a3b46efdcec93056ec4e4b744


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

        
        RFC 4349

        Title:      High-Level Data Link Control (HDLC) 
                    Frames over Layer 2 Tunneling Protocol, 
                    Version 3 (L2TPv3) 
        Author:     C. Pignataro,  M. Townsley
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    cpignata at cisco.com, 
                    mark at townsley.net
        Pages:      11
        Characters: 22888
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2tpext-pwe3-hdlc-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4349.txt

The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a protocol 
for tunneling a variety of data link protocols over IP networks.  This 
document describes the specifics of how to tunnel High-Level Data 
Link Control (HDLC) frames over L2TPv3.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distributon.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list