IPv6 Developments IPv6 Developments in AARNet " APAN 32 2011 - - PowerPoint PPT Presentation

IPv6 Developments IPv6 Developments in AARNet"

APAN 32 2011 3 New Delhi 23rd August 2011 23rd August, 2011

B f I t d ti By way of Introduction

• 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 l t f t t i dil il bl

• Quite a lot of content is readily available
• 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 AARN t 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

P /T it ti 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

C t C ti Customer Connections

• 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 t Customers

Only a small group of customers have extended IPv6 into their network

• Only a small group of customers have extended IPv6 into their network
• n 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 t t Content

• 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 ti i ti i The optimistic view

• Unfortunately the values are for maximum bps through the period
• Unfortunately the values are for maximum bps through the period

Th li ti i The realistic view

• Values are average bps through the period

Th h i The research view

• 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 l t 2011 Developments

• World IPv6 Day!
• June 8th 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 External IPv6 traffic AARNet all IPv6 traffic AARNet 6to4 traffic

B i b t l f l th l Boring but m ore colourful than usual

Using Netflowv9 Using Netflowv9 non-sampled by AS June 7th 2011 June 8th 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

IP 6 d 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

i f ti A t li th / ti it f RIPE information on Australian paths/connectivity for RIPE.

• http://v6day.ripe.net/cgi-bin/index.cgi

O l IP 6 t i t i AU AARN t

• Only IPv6 measurement points in AU were on AARNet

C ti i i ithi AARN t Continuing 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

E i it t t t b il bl IP 6

• Encourage university content 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

• Overall we are in a healthy state compared to many ISPs in Australia

Sl Slow progress

• Issues with deployment of RPSLng for IPv6
• Basic functionality available

S ill f ll d i i l k

• Still not fully supported in irrtoolset v5 eg network ranges
• RPSL itself has policy definition issues eg static IPv6 routes
• Advanced functionality difficult

M d t i t d it t id t IP 4/IP 6

• Managed to script around it to provide congruent IPv4/IPv6

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 f h ? Th h t t W here from here? The short term …

• Maintenance of full connectivity is prime concern

D l k IP 4 NAT/ i IP 6 i i bl i h f

• Dual stack IPv4 NAT/native IPv6 seems inevitable in short run for

newer customers. ( Those customers currently NAT anyway) N IP 4 ll ti il bl i h t/ di t IP 4 li k

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