RFC 7447: Deprecation of BGP Entropy Label Capability Attribute
In plain English — editorial summary, not part of the RFC
The BGP Entropy Label Capability attribute is defined in RFC 6790. Regrettably, it has a bug: although RFC 6790 mandates that routers incapable of processing Entropy Labels must remove the attribute, fulfillment of this requirement cannot be guaranteed in practice. This specification deprecates the attribute. A forthcoming document will propose a replacement.
Document record
- Document ID
- RFC7447
- Published
- February 2015
- Authors
- J. Scudder; K. Kompella
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 6790
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7446Routing and Wavelength Assignment Information Model for Wavelength Switched Optical NetworksCurrent
February 2015
- RFC 7449Path Computation Element Communication Protocol (PCEP) Requirements for Wavelength Switched Optical Network (WSON) Routing and Wavelength AssignmentCurrent
February 2015
- RFC 7442Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)Current
February 2015
- RFC 7453MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)Current
February 2015
- RFC 7441Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN RoutesCurrent
January 2015
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 7455Transparent Interconnection of Lots of Links (TRILL): Fault ManagementCurrent
March 2015
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
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?