RFC 7965: LDP Extensions for Pseudowire Binding to Label Switched Path (LSP) Tunnels
In plain English — editorial summary, not part of the RFC
Many transport services require that user traffic, in the form of Pseudowires (PWs), be delivered via either a single co-routed bidirectional tunnel or two unidirectional tunnels that share the same routes. This document defines an optional extension to the Label Distribution Protocol (LDP) that enables the binding between PWs and the underlying Traffic Engineering (TE) tunnels. The extension applies to both single-segment and multi-segment PWs.
Document record
- Document ID
- RFC7965
- Published
- August 2016
- Authors
- M. Chen; W. Cao; A. Takacs; P. Pan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7964Solutions for BGP Persistent Route OscillationCurrent
September 2016
- RFC 7963RSVP-TE Extension for Additional Signal Types in G.709 Optical Transport Networks (OTNs)Current
August 2016
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7961Transparent Interconnection of Lots of Links (TRILL): Interface Addresses APPsub-TLVCurrent
August 2016
- RFC 7956Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 GatewayCurrent
September 2016
- RFC 7955Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) BlockCurrent
September 2016
- RFC 7954Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) BlockCurrent
September 2016
- RFC 7978Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header ExtensionCurrent
September 2016
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?