Autonomous System Confederations for BGP
RFC 5065
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet … Received changes through RFC Editor sync (changed abstract to '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]') |
|
2017-05-16
|
(System) | Changed document authors from "John Scudder, Danny McPherson" to "John Scudder, Danny McPherson, Paul Traina" |
|
2015-10-14
|
(System) | Notify list changed from idr-chairs@ietf.org to (None) |
|
2007-08-10
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2007-08-10
|
Amy Vezza | [Note]: 'RFC 5065' added by Amy Vezza |
|
2007-08-07
|
(System) | RFC published |