RFC 7153: IANA Registries for BGP Extended Communities
In plain English — editorial summary, not part of the RFC
This document reorganizes the IANA registries for the type values and sub-type values of the BGP Extended Communities attribute and the BGP IPv6-Address-Specific Extended Communities attribute. This is done in order to remove interdependencies among the registries, thus making it easier for IANA to determine which codepoints are available for assignment in which registries. This document also clarifies the information that must be provided to IANA when requesting an allocation from one or more of these registries. These changes are compatible with the existing allocations and thus do not affect protocol implementations. The changes will, however, impact the "IANA Considerations" sections of future protocol specifications. This document updates RFC 4360 and RFC 5701.
Document record
- Document ID
- RFC7153
- Published
- March 2014
- Authors
- E. Rosen; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 9184
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 7313Enhanced Route Refresh Capability for BGP-4Current
July 2014
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 56684-Octet AS Specific BGP Extended CommunityCurrent
October 2009
- RFC 8654Extended Message Support for BGPCurrent
October 2019
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
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?