RFC 4385: Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN
In plain English — editorial summary, not part of the RFC
This document describes the preferred design of a Pseudowire Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS packet switched network, and the Pseudowire Associated Channel Header. The design of these fields is chosen so that an MPLS Label Switching Router performing MPLS payload inspection will not confuse a PWE3 payload with an IP payload. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4385
- Published
- February 2006
- Authors
- S. Bryant; G. Swallow; L. Martini; D. McPherson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 5586
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4382MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information BaseCurrent
February 2006
- RFC 4461Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)Current
April 2006
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4182Removing a Restriction on the use of MPLS Explicit NULLUpdated
September 2005
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?