Top Banner
Tracking the Internet’s BGP Table Geoff Huston Telstra December 2000
21

Tracking the Internet’s BGP Table

Mar 15, 2016

Download

Documents

nichelle-brown

Tracking the Internet’s BGP Table. Geoff Huston Telstra December 2000. Methodology. The BGP table monitor uses a router at the boundary of AS1221 which has a default-free eBGP routing table Capture the output from “show ip bgp” every hour Perform analysis of the data - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Tracking the Internet’s BGP Table

Tracking the Internet’s BGP Table

Geoff HustonTelstra

December 2000

Page 2: Tracking the Internet’s BGP Table

Methodology The BGP table monitor uses a router

at the boundary of AS1221 which has a default-free eBGP routing table

1. Capture the output from “show ip bgp” every hour

2. Perform analysis of the data(and then discard the raw dump!)

3. Update reports at www.telstra.net/ops/bgp

Page 3: Tracking the Internet’s BGP Table

The BGP Table

Page 4: Tracking the Internet’s BGP Table

Phases of Growth

Exponential growth CIDR Deployment CIDR-based Growth Post-CIDRExponential Growth

Page 5: Tracking the Internet’s BGP Table

Growth Characteristics Short term route fluctuation is an

absolute value (not a % of total routes) of 1,000 – 2,000 routes

Page 6: Tracking the Internet’s BGP Table

Routed Address Space

Fluctuation is due to announcement / withdrawals of /8 prefixes11 months of data does not provide clear longer growth characteristic

Page 7: Tracking the Internet’s BGP Table

Routed Address Space (/8 Corrected)

y = 1E-10x2.1176

R2 = 0.9923

1000000000

1020000000

1040000000

1060000000

1080000000

1100000000

1120000000

1140000000

942000000 947000000 952000000 95700 0000 962000000 967000000 972000000

Annual compound growth rate is 7% p.a.Most address comsumption today appears to beocurring behind NATs

/8 Corrected Data

Page 8: Tracking the Internet’s BGP Table

Average size of a routing table entry

The BGP routing tale is growing at a faster rate than the rate of growth of announced address space

/18.1

/18.5

Page 9: Tracking the Internet’s BGP Table

Number of AS’s in the table

Exponential growth is evident in a longer term view of the AS deployment rate

Page 10: Tracking the Internet’s BGP Table

AS Number Trend Models

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

10000

15-May-96 1-Dec-96 19-Jun-97 5-Jan-98 24-Jul-98 9-Feb-99 28-Aug-99 15-Mar-00 1-Oct-00 19-Apr-01

Value

Model 1

Model 2

Model 3

Best fit model is an exponential model using 12 months of data

Page 11: Tracking the Internet’s BGP Table

AS Number Use - Extrapolation

0

10000

20000

30000

40000

50000

60000

70000

28-Oct-95 11-Mar-97 24-Jul-98 6-Dec-99 19-Apr-01 1-Sep-02 14-Jan-04 28-May-05 10-Oct-06

Model 1

Model 2

Model 3

Values

Continued exponential growth implies AS number exhaustion in 2005

Page 12: Tracking the Internet’s BGP Table

Number of distinct AS Paths

Page 13: Tracking the Internet’s BGP Table

Observations for 99/00 Low growth in the number of routed addresses

0.6% growth / month (7% / year)

High growth in number of route advertisements3% growth / month (42% / year)

High growth in number of AS’s3.5% growth / month (51% / year)

Page 14: Tracking the Internet’s BGP Table

Multi-homing on the rise? Track rate of CIDR “holes” – currently 40% of

all route advertisements are routing ‘holes”

This graph tracks the number of address prefix advertisements which are part of an advertised larger address prefix

Page 15: Tracking the Internet’s BGP Table

Prefix Growth – Aug 00 to Oct 00/16 6553 -> 6670 absolute growth = 117, relative = 1.79%/17 889 -> 936 absolute growth = 47, relative = 5.29%/18 1763 -> 1884 absolute growth = 121, relative = 6.86%/19 5704 -> 5984 absolute growth = 280, relative = 4.91%/20 3423 -> 3854 absolute growth = 431, relative = 12.59%/21 3621 -> 3856 absolute growth = 235, relative = 6.49%/22 5415 -> 5870 absolute growth = 455, relative = 8.40%/23 7298 -> 7788 absolute growth = 490, relative = 6.71%/24 49169 -> 52449 absolute growth = 3280, relative = 6.67%/25 208 -> 436 absolute growth = 228, relative = 109.62%/26 334 -> 606 absolute growth = 272, relative = 81.44%/27 469 -> 667 absolute growth = 198, relative = 42.22%/28 357 -> 452 absolute growth = 95, relative = 26.61%/29 579 -> 764 absolute growth = 185, relative = 31.95%/30 746 -> 1026 absolute growth = 280, relative = 37.53%

The largest significant relative growth in recent times is /20, tracking the allocation policy change in the RIRs

While the absolute number is low, the largest relative growth is in /25 prefixes, and /25 to /30 represent the greatest area of prefix growth in relative terms

Page 16: Tracking the Internet’s BGP Table
Page 17: Tracking the Internet’s BGP Table
Page 18: Tracking the Internet’s BGP Table

Conjectures….BGP table size will continue to rise exponentially Multi-homing at the edge of the Internet is on

the increase The interconnectivity mesh is getting denser

The number of AS paths is increasing faster than the number of AS’s

Average AS path length remains constant AS number deployment growth will exhaust

64K AS number space in August 2005 if current growth trends continue

Page 19: Tracking the Internet’s BGP Table

More conjecturing…. Inter-AS Traffic Engineering is being

undertaken through routing discrete prefixes along different paths -- globally (the routing mallet!)

RIR allocation policy (/19, /20) is driving one area of per-prefix length growth in the aggregated prefix area of the table

BUT - NAT is a very common deployment tool

NAT, multihoming and TE is driving even larger growth in the /24 prefix area

Page 20: Tracking the Internet’s BGP Table

And while we are having such a good time conjecturing… Over 12 months average prefix length in

the table has shifted from /18.1 to /18.5 More noise (/25 and greater) in the table,

but the absolute level of noise is low (so far) Most routing table flux is in the /24 to /32

prefix space – as this space gets relatively larger so will total routing table flux levels

“Flux” here is used to describe the cumulative result of the withdrawals and announcements

Page 21: Tracking the Internet’s BGP Table

This is fun – lets have even more conjectures… CIDR worked effectively for four years, but

its effective leverage has now finished Provider-based service aggregation

hierarchies as a model of Internet deployment structure is more theoretic than real these days

i.e. provider based route aggregation is leaking like a sieve!

-