+ All Categories
Home > Internet > Routing in 2016, IETF 98

Routing in 2016, IETF 98

Date post: 07-Apr-2017
Category:
Upload: apnic
View: 20 times
Download: 1 times
Share this document with a friend
56
Routing in 2016 Geoff Huston Chief Scientist, APNIC
Transcript
Page 1: Routing in 2016, IETF 98

Routing in 2016

Geoff HustonChief Scientist, APNIC

Page 2: Routing in 2016, IETF 98

Through the Routing Lens

ThereareveryfewwaystoassembleasingleviewoftheentireInternet

ThelensofroutingisoneofthewaysinwhichinformationrelatingtotheentirereachableInternetisboughttogether

Evenso,itsnotaperfectlens…

Page 3: Routing in 2016, IETF 98

1994: Introduction of CIDR

2001: The Great Internet Boom and Bust

2005: Broadband to the Masses

2009: The GFC hits the Internet

2011: Address Exhaustion

Routing the InternetThis is a view pulled together from each of the routing peers of Route-Views

Page 4: Routing in 2016, IETF 98

2015-2016 in detail

Page 5: Routing in 2016, IETF 98

2015-2016 in detail

average growth trend

Route Views Peers

RIS Peers

Page 6: Routing in 2016, IETF 98

Routing Indicators for IPv4

Routing prefixes – growing by some 54,000 prefixes per year

Page 7: Routing in 2016, IETF 98

Routing Indicators for IPv4

AS Numbers– growing by some 3,450 prefixes per year

Page 8: Routing in 2016, IETF 98

Routing Indicators for IPv4More Specifics are still taking up one half of the routing table

Page 9: Routing in 2016, IETF 98

Routing Indicators for IPv4

But the average size of a routing advertisement is getting smaller

Page 10: Routing in 2016, IETF 98

Routing Indicators for IPv4

Address Exhaustion is now visible in the extent of advertised address space

Page 11: Routing in 2016, IETF 98

Routing Indicators for IPv4The “shape” of inter-AS interconnection appears to be relatively steady, as the Average AS Path length has been steady through the year

Page 12: Routing in 2016, IETF 98

AS Adjacencies (Route-Views)

6,202AS6939HURRICANE- Hurricane Electric, Inc.,US5,069AS174COGENT-174- Cogent Communications,US4,767AS3356LEVEL3- Level 3 Communications, Inc.,US2,632AS3549LVLT-3549- Level 3 Communications, Inc.,US2,397 AS7018 ATT-INTERNET4- AT&TServices, Inc., US1,959AS209CENTURYLINK-US-LEGACY-QWEST- Qwest,US1,953AS57463NETIX,BG1,691AS37100SEACOM-AS,MU1,620AS34224 NETERRA-AS,BG

19,700outof57,064ASNshave1or2ASAdjacencies(72%)

3,062ASNshave10ormoreadjacencies

22ASNshave>1,000adjacencies

Page 13: Routing in 2016, IETF 98

What happened in 2016 in V4?

RoutingBusinessasusual– despiteIPv4addressexhaustion!

• Fromthelookofthegrowthplots,itsbusinessasusual,despitetheincreasingpressuresonIPv4addressavailability

• ThenumberofentriesintheIPv4default-freezoneisnowheadingto700,000bytheendof2017

• Thepaceofgrowthoftheroutingtableisstillrelativelyconstantat~54,000newentriesand3,400newAS’speryear• IPv4addressexhaustionisnotchangingthis!

• Instead,weareadvertisingshorterprefixesintotheroutingsystem

Page 14: Routing in 2016, IETF 98

How can the IPv4 network continue to grow when we are running out of IPv4 addresses?

WearenowrecyclingoldaddressesbackintotheroutingsystemSomeoftheseaddressesaretransferredinwaysthatarerecordedintheregistrysystem,whileothersarebeing“leased”withoutanyclearregistrationentrythatdescribesthelessee

Page 15: Routing in 2016, IETF 98

IPv4 Advertised Address “Age”

80% of all new addresses announced in 2010 were allocated or assigned within the past 12 months

2% of all new addresses announced in 2010 were >= 20 years ‘old’ (legacy)

2010

Page 16: Routing in 2016, IETF 98

IPv4 Advertised Address “Age”

24 % of all new addresses announced in 2016 were allocated or assigned within the past 12 months

39 % of all new addresses announced in 2016 were >= 20 years ‘old’(legacy)

2016

Page 17: Routing in 2016, IETF 98

IPv4: Advertised vs Unadvertised Addresses

Page 18: Routing in 2016, IETF 98

IPv4: Unadvertised Addresses

Page 19: Routing in 2016, IETF 98

IPv4:Assigned vs Recovered

Growth in Advertised Addresses

Change in the Unadvertised Address Pool

RIR Allocations

“recovery”

“draw down”

Page 20: Routing in 2016, IETF 98

IPv4 in 2016

Theequivalentof1.8/8swasaddedtotheroutingtableacross2016• Approximately1.3/8swereassignedbyRIRsin2015• 0.7/8’sassignedbyAfrinic• 0.2/8swereassignedbyAPNIC,RIPENCC(Last/8allocations)

• 0.1/8swereassignedbyARIN,LACNIC

• Andanetof0.5/8’swererecoveredfromtheUnadvertisedPool

Page 21: Routing in 2016, IETF 98

The Route-Views view of IPv6

World IPv6 Day

IANA IPv4 Exhaustion

Page 22: Routing in 2016, IETF 98

2015-2016 in detail

Page 23: Routing in 2016, IETF 98

Routing Indicators for IPv6

Routing prefixes – growing by some 6,000 prefixes per year

Page 24: Routing in 2016, IETF 98

Routing Indicators for IPv6

AS Numbers– growing by some 1,700 prefixes per year (which is half the V4 growth)

Page 25: Routing in 2016, IETF 98

Routing Indicators for IPv6

More Specifics now take up more than one third of the routing table

Page 26: Routing in 2016, IETF 98

Routing Indicators for IPv6

The average size of a routing advertisement is getting smaller

Page 27: Routing in 2016, IETF 98

Routing Indicators for IPv6

Advertised Address span is growing at a linear rate

Page 28: Routing in 2016, IETF 98

Routing Indicators for IPv6The “shape” of inter-AS interconnection in IPv6 appears to be steady, as the Average AS Path length has been held steady

Page 29: Routing in 2016, IETF 98

AS Adjacencies (Route Views)

9,105outof13,197ASNshave1or2ASAdjacencies(69%)917ASNshave10ormoreadjacencies4ASNshave>1,000adjacencies

3,276AS6939HURRICANE- HurricaneElectric,Inc.,US1,607AS174COGENT-174- CogentCommunications,US1,310AS3356LEVEL3- Level3Communications,Inc.,US1,112AS37100SEACOM-AS,MU

Page 30: Routing in 2016, IETF 98

IPv6 in 2015

• OverallIPv6InternetgrowthintermsofBGPissteadyatsome6,000routeentriesp.a.

ThisisgrowthofBGProuteobjectsis1/9ofthegrowthrateoftheIPv4network– ascomparedtotheASgrowthratewhichis1/2oftheIPv4ASnumbergrowthrate

Page 31: Routing in 2016, IETF 98

What to expect

Page 32: Routing in 2016, IETF 98

BGP Size Projections

FortheInternetthisisatimeofextremeuncertainty• RegistryIPv4addressrunout• Uncertaintyovertheimpactsofmarket-mediatedmovementsofIPv4ontheroutingtable

• UncertaintyoverthetimingofIPv6takeup leadstoamixedresponsetoIPv6sofar,andnoclearindicatoroftriggerpointsforchangeforthoseremainingIPv4-onlynetworks

Page 33: Routing in 2016, IETF 98

V4 - Daily Growth Rates

Page 34: Routing in 2016, IETF 98

V4 - Daily Growth Rates

Page 35: Routing in 2016, IETF 98

V4 - Relative Daily Growth Rates

Page 36: Routing in 2016, IETF 98

V4 - Relative Daily Growth Rates

GrowthintheV4networkappearstobeconstantatalongtermaverageof120additionalroutesperday,orsome45,000additionalroutesperyear

GiventhattheV4addresssupplyhasrunoutthisimpliesfurtherreductionsinaddresssizeinroutes,whichinturnimpliesevergreaterrelianceonNATs

Page 37: Routing in 2016, IETF 98

IPv4 BGP Table Size Predictions

Jan2013 441,0002014 488,0002015 530,0002016 586,000 580,0002017 646,000 628,000 620,0002018 700,000 675,000 670,0002019 754,000 722,000 710,0002020 808,000 768,000 760,0002021 862,000 815,0002022 916,000

Jan2016PREDICTION

Jan2015PREDICTION

Jan2017PREDICTION

Page 38: Routing in 2016, IETF 98

V6 - Daily Growth Rates

Page 39: Routing in 2016, IETF 98

V6 - Relative Growth Rates

Page 40: Routing in 2016, IETF 98

V6 - Relative Growth RatesGrowthintheV6networkappearstobeincreasing,butinrelativetermsthisisslowingdown.

Earlyadopters,whohavetendedtobetheV4transitproviders,havealreadyreceivedIPv6allocationandareroutingthem.ThetrailingedgeofIPv6adoptionaregenerallycomposedofstubedgenetworksinIPv4.ManyofthesenetworksappearnottohavemadeanyvisiblemovesinIPv6asyet.

Ifweseeachangeinthispicturethegrowthtrendwilllikelybeexponential.Butitsnotclearwhensuchatippingpointwilloccur

Page 41: Routing in 2016, IETF 98

IPv6 BGP Table Size predictions

Jan2014 16,1002015 21,2002016 27,0002017 35,0002018 50,000 43,0002019 65,000 51,0002020 86,000 59,0002021 113,000 67,0002022150,000 75,000

ExponentialModelLinearModel

Range of potential outcomes

Page 42: Routing in 2016, IETF 98

BGP Table Growth

Nothinginthesefiguressuggeststhatthereiscauseforurgentalarm-- atpresent

• TheoveralleBGP growthratesforIPv4areholdingatamodestlevel,andtheIPv6table,althoughitisgrowingatafasterrelativerate,isstillsmallinsizeinabsoluteterms

• Aslongaswearepreparedtolivewithinthetechnicalconstraintsofthecurrentroutingparadigm,theInternet’suseofBGPwillcontinuetobeviableforsometimeyet

• Nothingismeltingintermsofthesizeoftheroutingtableasyet

Page 43: Routing in 2016, IETF 98

BGP Updates

• WhataboutthelevelofupdatesinBGP?• Let’slookattheupdateloadfromasingleeBGPfeedinaDFZcontext

Page 44: Routing in 2016, IETF 98

IPv4 Announcements and Withdrawals

Page 45: Routing in 2016, IETF 98

IPv4 Convergence Performance

Page 46: Routing in 2016, IETF 98

Updates in IPv4 BGP

Thenumberofupdatesperinstabilityeventhasbeenrelativelyconstant

Whichisgood,butwhyisthishappening?

LikelycontributorstothisoutcomearethedampingeffectofwidespreaduseoftheMRAIintervalbyeBGPspeakers,andthetopologyfactors,asseenintherelativelyconstantV4ASPathLength

Page 47: Routing in 2016, IETF 98

V6 Announcements and Withdrawals

Page 48: Routing in 2016, IETF 98

V6 Convergence Performance

High noise components in IPv6

Page 49: Routing in 2016, IETF 98

V6 Updated prefixes per day

Page 50: Routing in 2016, IETF 98

V6 Updates per event

Page 51: Routing in 2016, IETF 98

Updates in IPv6

BGPRouteUpdatesareveryunequallydistributedacrosstheprefixset– theyappeartoaffectaverysmallnumberofprefixeswhichstandoutwellabovetheaverage

Page 52: Routing in 2016, IETF 98

Updates in IPv6

Thebusiest50IPv6prefixesaccountedfor1/2ofallBGPIPv6prefixupdates

http://bgpupdates.potaroo.net/instability/v6-bgpupd.html

Page 53: Routing in 2016, IETF 98

Compared to IPv4

IPv6 IPv4

http://bgpupdates.potaroo.net/instability/bgpupd.htmlhttp://bgpupdates.potaroo.net/instability/v6-bgpupd.html

Page 54: Routing in 2016, IETF 98

Updates in IPv6 BGP

IPv6routingbehaviour issimilartoIPv4behaviour:

Mostannouncedprefixesarestableallofthetime

Andasmoreprefixesareannounced,mostoftheseannouncedprefixesarehighlystable.

Butforasmallnumberofprefixesweobservehighlyunstablebehaviours thatdominateIPv6BGPupdateswhichappeartobemoreunstable(relatively)thanIPv4

Page 55: Routing in 2016, IETF 98

Today’s State of Routing

“MostlyHarmless”

Thelevelsofgrowthofthetables,andthelevelsofgrowthofupdatesinBGPdonotposeanyimmediateconcerns

Thetrendsarepredictableandsteady,sonetworkoperatorscanplanwellinadvanceforthecapacityofroutingequipmenttomeettheirfutureneeds

But:

Theadvancedlevelsofinstabilitybyasmallnumberofnetworksarealwaysannoying!Howcanwepreventthesehighlyunstableprefixes?

Page 56: Routing in 2016, IETF 98

That’s it!


Recommended