in AARNet" APAN New Delhi 23 rd August, 2011

Transcription

1 IPv6 Developments in AARNet" APAN New Delhi 23 rd August, 2011

2 By way of Introduction ti This is not a technical talk about IPv6 IPv6 is ready, for the most part, to deploy now, especially in a dual stack environment Quite a lot of content t is readily available I would like to share some experiences of Where we are in Australia with IPv6 Our measurements of IPv6 traffic

3 IPv6 in AARNet 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

4 Peer/Transit connections 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

5 Customer Connections Most large customers have plenty of IPv4 space 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

6 Customers 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 IPv4 address space is still reasonably plentiful at a major institutional level Consequently IPv6 traffic is ~1% of total traffic It is increasing but slowly

7 Content 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

8 The optimistic i view Unfortunately the values are for maximum bps through the period

9 The realistic view Values are average bps through the period

10 The research view Most of the IPv6 R&E traffic is through TEIN. An inverse reflection on available IPv4 address space? R&E traffic is not leading the way anymore by volumes

11 2011 Developments World IPv6 Day! June 8 th 2011, organised by ISOC 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 It was boring and that was good! No major issues seem to have happened. Did it make an impression?

12 The IPv6 Day Quiz Spot IPv6 Day on the following graphs AARNet External IPv6 traffic AARNet all IPv6 traffic AARNet 6to4 traffic

13 Boring but more colourful l than usual Using Netflowv9 non-sampled by AS June 7 th 2011 June 8 th 2011 More sources but traffic levels only slightly increased

14 IPv6 day 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 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

15 IPv6 day 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 ti it for RIPE. Only IPv6 measurement points in AU were on AARNet

16 Continuing i issues within AARNet 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 Encourage university it content t to be available over IPv6 Dual stack environment is default for all customer connections Overall we are in a healthy state compared to many ISPs in Australia

17 Slow progress Issues with deployment of RPSLng for IPv6 Basic functionality available Still not fully supported in irrtoolset v5 eg network ranges RPSL itself has policy definition issues eg static IPv6 routes Advanced functionality difficult Managed to script around it to provide congruent IPv4/IPv6 policy 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.

18 Where from here? The short term Maintenance of full connectivity is prime concern Dual stack kip4nat/ IPv4 NAT/native IP6 IPv6 seems inevitable i in short run for newer customers. ( Those customers currently NAT anyway) No IPv4 allocations available in short/medium term IPv4 link addresses must be used sparingly. 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

19

20 Thank You