RFC 8077: Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)
In plain English — editorial summary, not part of the RFC
Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode, and Ethernet) can be emulated over an MPLS backbone by encapsulating the Layer 2 Protocol Data Units (PDUs) and then transmitting them over pseudowires (PWs). It is also possible to use pseudowires to provide low-rate Time-Division Multiplexed and Synchronous Optical NETworking circuit emulation over an MPLS-enabled network. This document specifies a protocol for establishing and maintaining the pseudowires, using extensions to the Label Distribution Protocol (LDP). Procedures for encapsulating Layer 2 PDUs are specified in other documents. This document is a rewrite of RFC 4447 for publication as an Internet Standard.
Document record
- Document ID
- RFC8077
- Published
- February 2017
- Authors
- L. Martini; G. Heron
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- STD84
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 4447 (2006)
- RFC 6723 (2012)
- RFC 8077 (2017)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8092BGP Large Communities AttributeCurrent
February 2017
- RFC 8093Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243Current
February 2017
- RFC 8061Locator/ID Separation Protocol (LISP) Data-Plane ConfidentialityCurrent
February 2017
- RFC 8060LISP Canonical Address Format (LCAF)Updated
February 2017
- RFC 8059PIM Join Attributes for Locator/ID Separation Protocol (LISP) EnvironmentsUpdated
January 2017
- RFC 8097BGP Prefix Origin Validation State Extended CommunityCurrent
March 2017
- RFC 8099OSPF Topology-Transparent ZoneCurrent
February 2017
- RFC 8102Remote-LFA Node Protection and ManageabilityCurrent
March 2017
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?