RFC 6793: BGP Support for Four-Octet Autonomous System (AS) Number Space

The Autonomous System number is encoded as a two-octet entity in the base BGP specification. This document describes extensions to BGP to carry the Autonomous…

Read RFC 6793 on the RFC Editor

Outgoing relationships (10 related RFCs)

Updates, Normative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Obsoletes — RFC 4893: BGP Support for Four-octet AS Number Space
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 1997: BGP Communities Attribute
Normative reference — RFC 5065: Autonomous System Confederations for BGP
Normative reference — RFC 5492: Capabilities Advertisement with BGP-4
Normative reference — RFC 5668: 4-Octet AS Specific BGP Extended Community
Informative reference — RFC 4001: Textual Conventions for Internet Network Addresses
Informative reference — RFC 5101: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information
Informative reference — RFC 4273: Definitions of Managed Objects for BGP-4

Incoming relationships (20 related RFCs)

Normatively referenced by — RFC 7606: Revised Error Handling for BGP UPDATE Messages
Normatively referenced by — RFC 6811: BGP Prefix Origin Validation
Normatively referenced by — RFC 8205: BGPsec Protocol Specification
Normatively referenced by — RFC 7115: Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)
Normatively referenced by — RFC 6996: Autonomous System (AS) Reservation for Private Use
Normatively referenced by — RFC 7854: BGP Monitoring Protocol (BMP)
Normatively referenced by — RFC 9241: Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
Normatively referenced by — RFC 7300: Reservation of Last Autonomous System (AS) Numbers
Normatively referenced by — RFC 9703: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane
Normatively referenced by — RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP
Normatively referenced by — RFC 10005: BGP Link Bandwidth Extended Community
Informatively referenced by — RFC 6991: Common YANG Data Types
Informatively referenced by — RFC 9911: Common YANG Data Types
Informatively referenced by — RFC 7249: Internet Numbers Registries
Informatively referenced by — RFC 7705: Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH Attribute
Informatively referenced by — RFC 7897: Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)
Informatively referenced by — RFC 8092: BGP Large Communities Attribute
Informatively referenced by — RFC 8670: BGP Prefix Segment in Large-Scale Data Centers
Informatively referenced by — RFC 7898: Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 8921: Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)