BGP Confederations essentially allow us to create sub-autonomous-systems within an autonomous system, thus creating a hierarchical structure to a large AS. Confederations are a method of overcoming the scalability problem that the iBGP full mesh peering requirement introduces into an AS. In this video, I will describe confederations, how they function, and how they can be used to overcome the limitations of scalability inherent to iBGP peerings.
Chapter list:
============================================
00:00 Introduction
00:22 iBGP Requires a Full-Mesh Peering
01:16 What is a BGP Confederation?
03:46 Are all iBGP Routers within a sub-AS?
05:52 Confederations and AS Numbers
07:15 Summary
Other videos mentioned in this video...
===============================================
Video: BGP - Why does iBGP require full mesh peering? -
https://youtu.be/03Gl1YGeZYc
Video: BGP - Why does BGP require an IGP to function? -
https://youtu.be/SN_TDZ2eDAA
Video: BGP - AS Path Attribute -
https://youtu.be/Rw1Ps2JTtPc
Other related links and videos:
===============================================
Video: What is BGP? -
https://youtu.be/fo9YxxKNO_g
Video: eBGP vs iBGP - What's the difference? -
https://youtu.be/3x7yztGSY-g
Video: BGP - Understanding the iBGP Split Horizon Rule -
https://youtu.be/lBWXBvyr6_Y
BGP Official Definition RFC 4271 - https://datatracker.ietf.org/doc/html/rfc4271
BGP AS Confederations for BGP RFC 5065 - https://datatracker.ietf.org/doc/html/rfc5065
#BGP #iBGP #confederations #autonomoussystems #lazarusagapidis