Autonomous System Confederations for BGP
RFC 5065, “Autonomous System Confederations for BGP”, is a Draft Standard document published in August 2007 by P. Traina, D. McPherson, J. Scudder. It obsoletes RFC 3065. It has since been updated by RFC 9774. The canonical text is published by the RFC Editor.
Abstract
The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP speakers within a single autonomous system (AS) must be fully meshed. This represents a serious scaling problem that has been well documented in a number of proposals.
This document describes an extension to BGP that may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the "full mesh" requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system.
This document obsoletes RFC 3065. [STANDARDS-TRACK]
What “Draft Standard” means
A historical maturity level (retired in 2011) that sat between Proposed Standard and Internet Standard and required multiple interoperable implementations.
The canonical text of RFC 5065 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5064 The Archived-At Message Header Field
- RFC 5066 Ethernet in the First Mile Copper Interfaces MIB
- RFC 5063 Extensions to GMPLS Resource Reservation Protocol Graceful Restart
- RFC 5067 Infrastructure ENUM Requirements
- RFC 5062 Security Attacks Found Against the Stream Control Transmission Protocol and Current Countermeasures
- RFC 5068 Email Submission Operations: Access and Accountability Requirements
- RFC 5061 Stream Control Transmission Protocol Dynamic Address Reconfiguration
- RFC 5070 The Incident Object Description Exchange Format