Border Gateway Protocol

1883

IPv6 BGP was first defined in RFC 1883 in 1995, and it was improved to RFC 2283 in 1998. The current version of BGP is version 4 (BGP4), which was published as RFC 4271 in 2006.

1989

In contrast, the Internet application of the protocol is called Exterior Border Gateway Protocol, External BGP (eBGP). == History == The Border Gateway Protocol was first described in 1989 in RFC 1105, and has been in use on the Internet since 1994.

1994

In contrast, the Internet application of the protocol is called Exterior Border Gateway Protocol, External BGP (eBGP). == History == The Border Gateway Protocol was first described in 1989 in RFC 1105, and has been in use on the Internet since 1994.

1995

IPv6 BGP was first defined in RFC 1883 in 1995, and it was improved to RFC 2283 in 1998. The current version of BGP is version 4 (BGP4), which was published as RFC 4271 in 2006.

1997

RFC 1997 also defines three well-known communities that have global significance; NO_EXPORT, NO_ADVERTISE and NO_EXPORT_SUBCONFED.

1998

IPv6 BGP was first defined in RFC 1883 in 1995, and it was improved to RFC 2283 in 1998. The current version of BGP is version 4 (BGP4), which was published as RFC 4271 in 2006.

2001

In addition, and perhaps even more importantly, larger routing tables take longer to stabilize (see above) after a major connectivity change, leaving network service unreliable, or even unavailable, in the interim. Until late 2001, the global routing table was growing exponentially, threatening an eventual widespread breakdown of connectivity.

2004

While this slowed the growth of the routing table to a linear process for several years, with the expanded demand for multihoming by end user networks the growth was once again superlinear by the middle of 2004. ===512k day=== A Y2K-like overflow triggered in 2014 for those models that were not appropriately updated. While a full IPv4 BGP table (512k day) was in excess of 512,000 prefixes, many older routers had a limit of 512k (512,000–524,288) routing table entries.

2006

IPv6 BGP was first defined in RFC 1883 in 1995, and it was improved to RFC 2283 in 1998. The current version of BGP is version 4 (BGP4), which was published as RFC 4271 in 2006.

Not all ISPs give out their communities to the public, while some others do. The BGP Extended Community Attribute was added in 2006, in order to extend the range of such attributes and to provide a community attribute structuring by means of a type field.

2007

An additional private AS range is also defined in RFC 6996 (from 4200000000 to 4294967294, 4294967295 being forbidden by RFC 7300). To allow the traversal of router groups not able to manage those new ASNs, the new attribute OT AS4_PATH is used. 32-bit ASN assignments started in 2007. == Load balancing == Another factor causing this growth of the routing table is the need for load balancing of multi-homed networks.

2011

In 2011, only 15000 AS numbers were still available, and projections were envisioning a complete depletion of available AS numbers in September 2013. RFC 6793 extends AS coding from 16 to 32 bits (keeping the 16 bits AS range 0 to 65535, and its reserved AS numbers), which now allows up to 4 billion available AS.

2013

In 2011, only 15000 AS numbers were still available, and projections were envisioning a complete depletion of available AS numbers in September 2013. RFC 6793 extends AS coding from 16 to 32 bits (keeping the 16 bits AS range 0 to 65535, and its reserved AS numbers), which now allows up to 4 billion available AS.

2014

While this slowed the growth of the routing table to a linear process for several years, with the expanded demand for multihoming by end user networks the growth was once again superlinear by the middle of 2004. ===512k day=== A Y2K-like overflow triggered in 2014 for those models that were not appropriately updated. While a full IPv4 BGP table (512k day) was in excess of 512,000 prefixes, many older routers had a limit of 512k (512,000–524,288) routing table entries.

On August 12, 2014, outages resulting from full tables hit eBay, LastPass and Microsoft Azure among others.




All text is taken from Wikipedia. Text is available under the Creative Commons Attribution-ShareAlike License .

Page generated on 2021-08-05