[rfc-dist] RFC 4618 on Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Sat Sep 30 14:24:57 PDT 2006

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

        RFC 4618

        Title:      Encapsulation Methods for Transport of 
                    PPP/High-Level Data Link Control (HDLC) over 
                    MPLS Networks 
        Author:     L. Martini, E. Rosen,
                    G. Heron, A. Malis
        Status:     Standards Track
        Date:       September 2006
        Mailbox:    lmartini at cisco.com, 
                    erosen at cisco.com, 
                    giles.heron at tellabs.com,  Andy.Malis at tellabs.com
        Pages:      16
        Characters: 33141
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-hdlc-ppp-encap-mpls-09.txt

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

A pseudowire (PW) can be used to carry Point to Point Protocol (PPP)
or High-Level Data Link Control (HDLC) Protocol Data Units over a
Multiprotocol Label Switching (MPLS) network without terminating the
PPP/HDLC protocol.  This enables service providers to offer "emulated"
HDLC, or PPP link services over existing MPLS networks.  This document
specifies the encapsulation of PPP/HDLC Packet Data Units (PDUs)
within a pseudowire.  [STANDARDS TRACK]

This document is a product of the Pseudo Wire Emulation Edge to Edge
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 

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

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

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