RFC 5668: 4-Octet AS Specific BGP Extended Community
In plain English — editorial summary, not part of the RFC
This document defines a new type of a BGP extended community, which carries a 4-octet Autonomous System (AS) number. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5668
- Published
- October 2009
- Authors
- Y. Rekhter; S. Sangli; D. Tappan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 5701IPv6 Address Specific BGP Extended Community AttributeUpdated
November 2009
- 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
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 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?