BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
RFC 4456
Revision differences
Document history
Date | By | Action |
---|---|---|
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 TCP/IP internets. Typically, … Received changes through RFC Editor sync (changed abstract to 'The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP). This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]') |
2015-10-14
|
(System) | Notify list changed from skh@nexthop.com, yakov@juniper.net to yakov@juniper.net |
2006-05-02
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2006-05-02
|
Amy Vezza | [Note]: 'RFC 4456' added by Amy Vezza |
2006-04-27
|
(System) | RFC published |