ipv6: where are we in 2017? - lacnicslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... ·...

25
IPv6: Where are we in 2017? Based on Internet Society 2017 report https://www.internetsociety.org/doc/state-ipv6-deployment-2017 June 6, 2017

Upload: others

Post on 21-May-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

IPv6:Wherearewein2017?BasedonInternetSociety2017report

https://www.internetsociety.org/doc/state-ipv6-deployment-2017June6,2017

Page 2: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

HistoryofIPv6

• 1990:IETFrealizedthatIPv4addressspacewouldrunout• Tookstepstoalleviatethat

• 1993,IETFrequestedproposalsfor“nextgeneration”protocol• IPv6proposedin1994• Standardizedin1998• SupportingworkinDHCP,DNS,routingprotocols,etc

• Implementationinvariousoperatingsystems;Windowslate

• Uptakeofprefixesstarted2007• ICANNpolicyforprefixallocation2006• TokyoUniversityreportonrealityofIPv4exhaustion predictions

https://www.oecd.org/sti/ieconomy/44961688.pdf

Page 3: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Exhaustiontimeframes

• AllRIRshavenowenteredtheirrespectiveendphases• LotsofIPv6prefixestoallocate• IPv4onlyfornewentrants,andtheninsmallquantities

https://ipv4.potaroo.net/plotend.png

Page 4: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Whatdoesthatmeanforanewentrant?RelianceJIO,launchedSeptember2016• IndianISP,tryingtoreachallofIndia.

• Wirelineandmobilewireless• Secondlargestcountryintheworld• About20%ofhumanbeingsworldwide

• FirstallocationfollowedAPNICexhaustionevent• 1024IPv4addresses(/22)allocated

• AdditionalspacepurchasedinIPv4addressmarket

• MinimumIPv6allocationtoaserviceproviderisa/32:asmany/64prefixesasthereareaddressesintheIPv4addressspace

• Allocated34Baddresses(IPv6/29)plusotherallocations

https://blog.apnic.net/2017/02/07/reliance-jio-boosts-india-past-20-ipv6-capability/

• “Currently,almost90%ofourLTE4GsubscribersareusingIPv6– accountingforalmost70%ofthecountry’sIPv6traffic–whichinitselfhasequatedtoarapidriseinIndia’stotalIPv6capabilities,increasingfrom1%to16%in2016(andpassing20%inthenewyear).”

Page 5: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

GrowthinIPv6inBGP

• RIPEdocumentsthegrowthonIPv6announcements• Status:

• Allregionsseegrowth• LACNICregioncurrentlyhasabout37%ofAS’sannouncingIPv6prefixes

http://v6asns.ripe.net/v/6?s=_RIR_ARIN;s=_RIR_AfriNIC;s=_RIR_LACNIC;s=_RIR_APNIC;s=_RIR_RIPE_NCC

Page 6: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

TrafficGrowthWorldwide

• ThisgraphicasseenbyGoogle• 37countrieshave>5%trafficusingIPv6asofApril2017

• Belgiumaninterestingcase• RegulatoryrequirementtonotuseNAT

• mapaddresstoasubscriber• OperationaldecisiontodeployIPv6toresidentialnetworks

• BelgiumcurrentlyleadsIPv6trafficasseenbyGoogle,Akamai,andAPNIChttps://www.vyncke.org/ipv6status/compare.php?metric=p&countries=be,us,gr,de,ch,lu,in,gb,ca,ee,ec,br,no,jp,tt,pt,fi,fr,my,pe,cz,au,nl,nz,ie,ro,zw,hu,si,gt,pr,kr,sa,vn,at,bo,pl

Page 7: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

AworldwithoutNATs?

• NetworkAddressTranslation(NAT)wascreatedtomultiplexIPv4addressuse• Butwassold asasecuritysolution• Betteraddressedwithfirewalls

• Affectslocation-basedservices• EspeciallyifimplementedintheISP

• NotgenerallyusedwithIPv6• Norequirementtomultiplexaddresses

https://natmeter.labs.lacnic.net/charts/

Page 8: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

IPv6TrafficGrowthinLatinAmericaGooglereportonLACNICregion(searchenginerequests)

AkamaireportonLACNICRegion(TCPsessionsmovingdata)

https://www.vyncke.org/ipv6status/compare.php?metric=p&countries=ec,br,tt,pe,gt,bo

Page 9: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

IPv4AddressMarket–IPv4BGPgrowthandmarketvaluestabilizing

http://ipv4marketgroup.com/q42016-update/

Page 10: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

IPv4AddressMarket:WhatsuggestionsfromtheIPv4MarketGroup?

• “ItwouldseemthatsomesortofpricemaximizationforIPv4shouldoccurbetween[2016-08]andJanuaryof2019.Wehaveseenpricesrisefrom$5/IPto$9to$10perIPfora/16overthepast18months.”

• “Asapotentialseller,itwouldseemthatyouwouldwanttosellintothisdemandandwaitnolongerthan28monthstosell.”

• MIThasdonejustthat:solda/9toAmazontofundIPv6deployment• http://www.networkworld.com/article/3191503

/internet/mit-selling-8-million-coveted-ipv4-addresses-amazon-a-buyer.html

• https://gist.github.com/simonster/e22e50cd52b7dffcf5a4db2b8ea4cce0

http://ipv4marketgroup.com/q42016-update/

Page 11: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Markets

Page 12: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

InternetofThings(IoT)

• Systemsnotnecessarilyservingahumanbeing• Oftensensors,actuators,cameras

• Like?• Doorbells• Homesurveillance• Thermostats• SmartGrid• HomeHealthCare

Page 13: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

BluetoothLowEnergy4.2or5.0

Containedenclave• UseBluetoothforcommunication

• Noexternalcommunication• ApplicationonLinklayer…

Enclavecommunicatingwithupstreamservice• ConnecttoanIP-capablegateway

• Enablesoftwaredownload• TranslateIP<->Bluetooth

Page 14: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Ethernet/WiFiorBluetooth5.0

Containedenclave• IndustrialAutomation,IEC61850

• EthernetorWiFi• Others:UseIPv4orIPv6forcommunication• Noexternalcommunication

• EndpointSecurityviaencryptionand/ormutualauthentication

Enclavecommunicatingwithupstreamservice• Router,firewall,orgateway

• Enablesoftwaredownload• ExternalService• Security?• UpstreamservicecoulduseMQTT/MQTT-S

Page 15: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

http://w

ww3.nd

.edu

/~hfergus2/p/w

ireless.pdf

Page 16: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

ZigBeeSecureEnergyProfile2.0OpenThreads Enclavecommunicatingwith

upstreamservice• Definedgateway(UDP/IPv6<->6LowPAN)

• Securitymanagedbyarchitecture• 6LowPANwithin802.15.4 network• COaP Management

https://docs.mbed.com/docs/arm-ipv66lowpan-stack/en/latest/thread_overview/

Page 17: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

OpenConnectivityFoundationTenants

IPV6CBORCoAP

Corearchitectureresources

Currentarchitecture(OIC1.1):• hierarchyofresources• ResourcesaredefinedbyRestfull APIModellingLanguage(RAML)• PayloadsdefinedinJSON(Draft-04schema)• CommunicationviaIPV6andCoAP,payloadonthewireconvertedinCBOR• Alldataconnectionsaresecure

Applicationlevelresources

https://workspa

ce.ope

ncon

nectivity.org/app

s/org/workgroup

/techn

ology_sc_o

pen/

downloa

d.ph

p/89

50/Techn

olog

y-Discussio

n-v3.pptx

Page 18: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Thelaggard:EnterpriseNetworks

• PerHurricaneElectric• 1/8ofAlexa-Top-MillionnamesareIPv6-reachable

• 28,000ofthoseareonly reachableusingIPv6

• 23%ofAS’sadvertiseIPv6prefixes• 325AS’sareIPv6-only

• Thatleaves77%ofAS’sIPv4-only• Inmostcases,enterprise

• Usuallylookingfor• Additionalrevenue,or• “KillerApplication”

Page 19: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Whatisthefuture?

• IPv4addressesareaspeculativeasset• Inotherwords,theyareworthsomethingifsold,butonlyforalimitedperiodoftime

• WealreadyseeservicesthatallocateIPv6forfreeandchargeforIPv4• Anddarepeopletothinkdifferently

https://www.mythic-beasts.com/

Page 20: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

• “Butforus,movingtoIPv6-onlyassoonaspossiblesolvesourproblemswithIPv4depletionandaddressoversubscription.Butitalsomovesustoasimplerworldofnetworkoperationswherewecanconcentrateoninnovationandprovidingnetworkservices,insteadofwastingenergybattlingwithsuchafundamentalresourceasaddressing.”

IPv6-onlyatMicrosoft

https://blog.apnic.net/2017/01/19/ipv6-only-at-microsoft/

Page 21: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

ISP,Content,andResidential?• CanIcountIPv6accessestocontent?• Implication:IhaveanIPv6-capableapplicationonanIPv6-capabledevice onanIPv6-capablenetwork connectingacrossmultipleISPstoIPv6-accessiblecontent

• Statisticslikethesetellanendtoendstory

https://stats.labs.apnic.net/ipv6/

Page 22: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Andthenthere’smobilewireless

• IfthereisonenetworkinwhichIPv6isdominant,itis4G/LTE• VerizonWireless:84%• T-MobileUSA:81%• RelianceJio:90%ofsubscribers,80%oftraffic

• AT&T:54%• Andsoon…

http://www.worldipv6launch.org/measurements/

Page 23: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

So…

• Inthereport,wewalkedthroughIPv6deploymentandmarketimpact.• Lookingforalogisticcurve,andthehockeystick“upandtotheright”

• Thenewnewsis:• Itlookslikewehaveone–

• ThereasonIPv4pricesareexpectedtofallin2019isbecause• Supplywillbemoreconstrained(lessaddresses,smallerblocks)• DemandwillfallasIPv6deploymentpasses50%

Page 24: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Awordtothewise

• IfyouwanttosellIPv4addressesintothecurrentmarket,• YouneedtohavemovedyournetworkandapplicationstoIPv6

• MovingtoIPv6-dominantdatacenters• WillyoupayforIPv4ifIPv6worksforfree?

• IPv6deploymentisnottrivial• Doyourequipmentandapplicationssupportit?• Ifnot,whatisyourbudgettimeframe?• Haveyoutestedit?Isitoperational?

• OnlythencanyousellyourIPv4addressspace…• Whichcouldhaveenoughvaluetopartiallyfundthedeployment

Page 25: IPv6: Where are we in 2017? - LACNICslides.lacnic.net/wp-content/uploads/2017/06/ipv6-where... · 2017-06-08 · History of IPv6 •1990: IETF realized that IPv4 address space would

Yo hablo geek