NextGenerationNetworks– AutomatedbyProVisionCompleteprovisioningfromallocationtoendpoint

APNICWorkshop– IPv6isLive!RealWorldSuccessStories

AaronHughesaaron@6connect.com+1-703-244-0427

Twiter:@6connect@aaronhaaronh

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 1

@PTCouncil#PTC17

PerspectiveonIPv6

6connectspecializesinprovisioningautomation• IPAM(IPAddressManagement)• DNS(DomainNameService)• DHCP(DynamicHostControlProtocol)• ChangeManagement• OperationsSupport(OSS/BSS)• Cloud(SDN/NFV)• AssetManagement• PeeringAutomation• StateManagement(Orchestratorsetc.)• ProvisioningAutomation(AnythingwithanAPI)

6connect– Viewofprospectsandcustomers• Earlyviewintowhatorganizationsaredoing• Earlyviewintointernalchallenges(underNDA)• Commonchallengeswithchangestoinfrastructure• Futureofarchitectures• Automation(gettingawayfromspreadsheets)• MovetoIPv6orDualStack• Movetovirtualization(orchestratorsandcontainers)• APIs(Becomingarequirement)• Longtermdiscussionswithpartners(weknowwhere

theyaregoingbeforemostorgsdo)

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 2

@PTCouncil#PTC17

CommonlyusedserviceshaveIPv6

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 3

@PTCouncil#PTC17

6connectIPv6statistics

6connectIPv6analytics:• 17%IPv6– Traffic(cloud/hosted)• 100%- IPv6trafficbetweenpartnersandservices

• RIRupdates,IRRupdates,whois,DNSintegrations

• 100%- CustomerswhoareimplementingIPv6• 100%- BackendservicesuseIPv6,manyONLYIPv6• Increasein464XLAT,NAT464,DNS64usage• WebContactFormIPv6stats:

• 2014(1.11%),2015(4.55%),2016(10.1%)

• 17%ofallcustomerassignmentsareIPv6.(IPAM)

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes4

@PTCouncil#PTC17

SupportingTools

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 5

AllinternaltoolssupportIPv6:• Authentication• Logging• Development• QA– Testingtools• Everyknownmajorbrowserbehavioremulator(QA)• RollingtoolsDev->QA->Production• Monitoring• Coderepositories• Etc..

@PTCouncil#PTC17

EmployeeswithoutIPv6cannotaccessinternaltoolsandsystems.

Enterpriselabconnectivity

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 6

• Enterpriseconnectionstoback-endoverIPv4attimeschallenging.Openingfirewalls,addingprefixestovarioussystems.Oddly,addingIPv6prefixesforaccesswefoundtobeveryeasy.Onceaprefixwasin,Development<->EnterpriseLabconsitentlyonandeasy.• InterestingcaseswherelackofIPv4addresseshasledtousingIPv6onlyforlabanddevelopment.

@PTCouncil#PTC17

Marketing

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 7

Marketing• AnIPv6sourceIPonwebformsassistedusinframing

theconversationwiththeprospect.Whilesomechallengesstillexistwithgeolocationinformation(wehadtouseadditionaltoolstoidentifythelocationoftheprospect),knowingtheyweresubmittingthewebformfromanIPv6sourcehelpsusunderstandwheretheyarewithimplementationforaninitialcall/assessmentwithWHOISlookups.

@PTCouncil#PTC17

Monitoring

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 8

Monitoring• We’veseenconsistencywithmonitoringservices

eithercompletelylackingsupportingforIPv6ortherequirementthatobjectsareduplicatedinthesystem.E.g.ipv4.foo.bar&ipv6.foo.bartomonitorfoo.bar.(sometimesresultingindoublecharges)

• Mostcustomersaremanagingthisissueontheirown.

• Therearea*few*monitoringserviceswhichhavestartedtolookathowtosolvemonitoringdualstackseriously.

@PTCouncil#PTC17

MeasuringSuccess?

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 9

Observations– Whatdefines“success”• IPv4utilizationisoftenveryhigh(70-100%)• IPv6utilizationisoftenverylow(<1%)• Thescaleissodifferent,it’schallengingtomeasure

“success”.Howdoyouquantifyit?Quantifyingtheimplementationtypicallyneedstochangetocustomers,ports,severs,interfaces,VLANs,mobiledevicesratherthannumberofaddresses(orpercentofutilization)

• FrequentlythepersonwhowrotetheplanforIPv4isnolongeratthecompany.IPv6planningrequiressignificanteducation.

• HowdoyoumeasuresuccessacrosstheEnterpriseinternally?• MostEnterprisesconsiderthe“frontend”/consumersinteractingwithsomething?Website?Service?Application?• HowmanyinternalusersareusingtoolsviaIPv6?

• ServiceProvidersmeasuredifferently• 1VLAN=/64• Morethan1VLAN=/48(or/56milagemayvary)• Consumersideagooddealof”unknowing”adopters.It’stransparentenoughthattheydonotknowtheissue.(andmaynotneedto)

@PTCouncil#PTC17

Takeaways

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 10

• ThereisasignificantgrowthinorganizationssearchingformanagementplatformswithsupportforIPv6

• IPv6ispartoftheconversationwhenlookingatupdatingarchitectures• VendorsareoftenselectedtodealwiththeIPv6“problem”whoarenotfollowingbestpractices,however,thestoriesaregettingbetter.

• Stillhear“WeshutoffIPv6andthatfixedtheproblem”,butmoreoftenareseeingcompaniesembraceIPv6aspartofthesolutionandfuture.

• TheconsumerstillthinksinIPv4andpresentingthedatainapalatablewayischallenging,however,thediscussionsarebeinghadatamorefrequentpace.

• Toolsandvendorsupportaregettingbetter.• WhileitmaynotallbevisibleontheInternet,wecontinuetoworkwithorganizationswhoareimplementingIPv6fromtheinsideout.

• “CleaningupIPv4”hascometomeantwothings.MoreefficientuseofIPv4resourcesandit’stimetoimplementIPv6.

• SomeportionofourcustomershavestartedtoworkonplansforanIPv6onlyworld

• ManycustomersarestartingtoimplementIPv6onlyonmanagementandinternalinfrastructure

• Upandtotheright!

@PTCouncil#PTC17

NextGenerationNetworks– AutomatedbyProVisionCompleteprovisioningfromallocationtoendpoint

APNICWorkshop– IPv6isLive!RealWorldSuccessStories

AaronHughesaaron@6connect.com+1-703-244-0427

1/15/17 6connect,Inc.- APNICWorkshop@PTC17- AaronHughes 11

@PTCouncil#PTC17