RFC 8395: Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
In plain English — editorial summary, not part of the RFC
This document defines protocol extensions required to synchronize flow label states among Provider Edges (PEs) when using the BGP-based signaling procedures. These protocol extensions are equally applicable to point-to-point Layer 2 Virtual Private Networks (L2VPNs). This document updates RFC 4761 by defining new flags in the Control Flags field of the Layer2 Info Extended Community.
Document record
- Document ID
- RFC8395
- Published
- June 2018
- Authors
- K. Patel; S. Boutros; J. Liste; B. Wen; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 4761
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8394Split Network Virtualization Edge (Split-NVE) Control-Plane RequirementsCurrent
May 2018
- RFC 8393Operating the Network Service Header (NSH) with Next Protocol "None"Current
May 2018
- RFC 8397Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique NicknamesCurrent
May 2018
- RFC 8400Extensions to RSVP-TE for Label Switched Path (LSP) Egress ProtectionCurrent
June 2018
- RFC 8390RSVP-TE Path Diversity Using Exclude RouteCurrent
July 2018
- RFC 8401Bit Index Explicit Replication (BIER) Support via IS-ISUpdated
June 2018
- RFC 8388Usage and Applicability of BGP MPLS-Based Ethernet VPNCurrent
May 2018
- RFC 8402Segment Routing ArchitectureUpdated
July 2018
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?