IPv6 Developments IPv6 Developments in AARNet " APAN 32 2011 3 0 New Delhi 23 rd August 2011 23 rd August, 2011
B By way of Introduction f I t d ti • This is not a technical talk about IPv6 • IPv6 is ready for the most part to deploy now especially in IPv6 is ready, for the most part, to deploy now, especially in a dual stack environment • Q it Quite a lot of content is readily available l t f t t i dil il bl • I would like to share some experiences of I would like to share some experiences of • Where we are in Australia with IPv6 • Our measurements of IPv6 traffic
IP 6 i IPv6 in AARNet AARN t • AARNet has operated a native dual stack IPv4/Ipv6 Network since 2003 • Core Network is DWDM with 10G diverse redundant backbone design for IPv4/IPv6 • Tunnels have been phased out except for the IPv6 Broker service to the Australian public and 6to4 etc • National footprint covering Australia • International footprint covering 5 PoPs in the US and Singapore 3
P Peer/Transit connections /T it ti • IPv6 peering connectivity to international R&E organisations in both US and Singapore. TEIN, Pacific Wave • IPv6 international peering • SIX, PAIX, Any2, Coresite, LAIIX exchanges • IPv6 international transit • Available and used NTT, HE • IPv6 domestic peering • Equinix Sydney, WAIX, Pipe, ACTIX exchanges and PNNI peerings etc No IPv6 domestic transit � • • transit provider should enable IPv6 this year • Still need to extend reach on IPv6 peers and connections
C Customer Connections t C ti • Most large customers have plenty of IPv4 space • They are taking up IPv6 space but still relatively slowly They are taking up IPv6 space but still relatively slowly • AARNet encourages dual stacked connections – the default • AARNet is adding more schools and other bodies to the network • We are now certified by the NBN – the National Broadband Network – and this will lead to a broader customer base • Running out of IPv4 address space for newer customers • Not crisis level yet
C Customers t • Only a small group of customers have extended IPv6 into their network Only a small group of customers have extended IPv6 into their network on a full production basis – Monash University has been an exemplar in that. • A number of institutions still see IPv6 as a testbed • Sometimes only used by specific researchers • Sometimes only extended to the IT department of a university Sometimes only extended to the IT department of a university • IPv4 address space is still reasonably plentiful at a major institutional level level • Consequently IPv6 traffic is ~1% of total traffic • It is increasing – but slowly
C Content t t • We host a number of archives available through IPv6 on mirror.aarnet.edu.au • We are Google white-listed and so both Google and YouTube resolve to an AAAA records • We host Akamai caches with IPv6 network connectivity • However very little traffic • Continuing to work with and encourage content delivery over IPv6 for CDN and peer networks
Th The optimistic view ti i ti i • • Unfortunately the values are for maximum bps through the period Unfortunately the values are for maximum bps through the period
Values are average bps through the period The realistic view i li ti Th •
Th The research view h i • Most of the IPv6 R&E traffic is through TEIN. • • An inverse reflection on available IPv4 address space? An inverse reflection on available IPv4 address space? • R&E traffic is not leading the way anymore by volumes
2011 D 2011 Developments l t • World IPv6 Day! June 8 th 2011, organised by ISOC • • • A trial of IPv6 A trial of IPv6 • Google, Facebook, Akamai, Yahoo, Limelight and others giving AAAA records to the world • Only Google (whitelist) and Limelight now provide AAAA records Only Google (whitelist) and Limelight now provide AAAA records • It was boring and that was good! • • No major issues seem to have happened No major issues seem to have happened. • Did it make an impression?
The IPv6 Day Quiz Spot IPv6 Day on the following graphs Spot IPv6 Day on the following graphs • AARNet 6to4 traffic AARNet all IPv6 traffic AARNet External IPv6 traffic
B Boring but m ore colourful than usual i b t l f l th l Using Netflowv9 Using Netflowv9 non-sampled by AS June 7 th 2011 June 8 th 2011 More sources but traffic levels only slightly increased
IP 6 d IPv6 day • • IPv6 day had little impression on general traffic patterns IPv6 day had little impression on general traffic patterns • A flurry of IPv6 peering requests the few days prior. • Most participants turned on AAAA records for the day only • It was turned off when the day ended • Akamai IPv6 traffic was minimal but ongoing g g • Limelight have continued • No discernable effect on Google/YouTube traffic as whitelisted already • There was a certain amount of tokenism • Many sites had IPv6 enabled only for their front pages. • Any navigation beyond that went to IPv4 only sites • Images and other content were often still IPv4 only
IPv6 day IP 6 d • Encouraged my large number of small content providers in Australia that turned on IPv6. • Sneaking suspicion that some customers actually turned off using IPv6 so as to prevent perceived issues on that day • Hard to prove as traffic levels to these customers was low anyway • CAIDA ARK machine on the AARNet network running IPv6 provided information on Australian paths/connectivity for RIPE. i f ti A t li th / ti it f RIPE • http://v6day.ripe.net/cgi-bin/index.cgi Only IPv6 measurement points in AU were on AARNet � AARN t � • O l IP 6 t i t i AU
Continuing issues within AARNet C ti i i ithi AARN t • We have our final APNIC IPv4 allocations. AARNet as an organisation is not IPv4 rich. No real historic address space available to us. Our bigger institutions are however IPv4 rich. • Our growth into schools, medical institutions and other research and education areas is likely to face IPv4 addressing allocation issues. • Our larger customer base still has plenty of IPv4 space available • Encourage IPv6 take up to provide global connectivity • E Encourage university content to be available over IPv6 i it t t t b il bl IP 6 • Dual stack environment is default for all customer connections • Overall we are in a healthy state compared to many ISPs in Australia Overall we are in a healthy state compared to many ISPs in Australia
Slow progress Sl • Issues with deployment of RPSLng for IPv6 • Basic functionality available • S ill Still not fully supported in irrtoolset v5 eg network ranges f ll d i i l k • RPSL itself has policy definition issues eg static IPv6 routes • Advanced functionality difficult • M Managed to script around it to provide congruent IPv4/IPv6 d t i t d it t id t IP 4/IP 6 policy • • IPv6 used for management, content and backups within AARNet IPv6 used for management content and backups within AARNet • Substantial traffic in those areas • • IPv6 Netflow using Netflow 9 is now deployed across AARNet IPv6 Netflow using Netflow 9 is now deployed across AARNet providing insight into traffic flows. Currently monitoring at 1:1 sampling as traffic levels low.
W h W here from here? The short term … f h ? Th h t t • Maintenance of full connectivity is prime concern • D Dual stack IPv4 NAT/native IPv6 seems inevitable in short run for l k IP 4 NAT/ i IP 6 i i bl i h f newer customers. ( Those customers currently NAT anyway) • No IPv4 allocations available in short/medium term – IPv4 link N IP 4 ll ti il bl i h t/ di t IP 4 li k addresses must be used sparingly. • • Continue to push for IPv6 adoption at both a services and client Continue to push for IPv6 adoption at both a services and client level • • It’s all becoming rather messy after 12 or so years of denial It s all becoming rather messy after 12 or so years of denial
Thank You
Recommend
More recommend
