Mirjam Kühne | March 2016 | Netnod Spring Meeting

“Lost Stars” Why Operators Switch

Off IPv6

CreditsNathalie Trenaman

Arne KiesslingEmile Aben

Rene Wilhelm

IPv6All going well?

Mirjam Kühne | Netnod Spring Meeting | March 2016 4

Enabling IPv6

• Get IPv6 address space

• Get it routed

• Get it used

Mirjam Kühne | Netnod Spring Meeting | March 2016 5

10,000 LIRs now have IPv6 Addresses

• Recently published on RIPE Labshttps://labs.ripe.net/Members/nathalie_nathalie/10-000-lirs-with-ipv6-resources

LIRs without IPv6

LIRs with IPv6

Mirjam Kühne | Netnod Spring Meeting | March 2016 6

IPv6 Enabled Networks (1)

Mirjam Kühne | Netnod Spring Meeting | March 2016 7

IPv6 Enabled Networks (2)

Sweden:51.64%

267 out of 517 ASes

Mirjam Kühne | Netnod Spring Meeting | March 2016 8

IPv6 RIPEness

• Rating system to measure early signs of IPv6 deployment

• 1 star if LIRs has an IPv6 allocation

• 3 more stars possible if- Prefix is announced (visible in RIS)

- Prefix is registered in routing registry (route6 object)

- Reverse DNS is set up

http://ipv6ripeness.ripe.net/

Mirjam Kühne | Netnod Spring Meeting | March 2016 9

IPv6 RIPEness - 4 Stars

24%

30% 10%

15%

21%

4

321

0

19%

17%

12% 17%

36%0 4

321

All (13,277 LIRs) Sweden (369 LIRs)

Mirjam Kühne | Netnod Spring Meeting | March 2016 10

IPv6 RIPEness “5th star”

• Measuring actual IPv6 deployment- Content networks: Percentage of IPv6 enabled Alexa1M

listed sites in that network, weighed by Alexa ranking

- Access networks: Percentage of IPv6-enabled users from APNIC ads-measurements

- Threshold for “5th star” has been doubled every year (now 16%)

Fifth Star in Sweden:

Mirjam Kühne | Netnog Spring Meeting | March 2016 11

IPv6 in Europe

• Belgium 49%

• Switzerland 29%

• Portugal 28%

• Greece 25%

• Germany 18%

• Finland 12%

• Norway 12%IPv6 usage per country

(source: APNIC)

IPv6Things not going so well

Mirjam Kühne | Netnod Spring Meeting | March 2016 13

Enabling IPv6

• Get IPv6 address space

• Get it routed

• Get it used

???

Mirjam Kühne | Netnod Spring Meeting | March 2016 14

False Starts?

• We found that 462 Local Internet Registries (LIRs) stopped announcing IPv6

• We contacted them all to find out why

• Within 2 weeks we received 69 survey responses- And a lot of e-mails directly sent to us

Mirjam Kühne | Netnod Spring Meeting | March 2016 15

Where are these LIRs?

0

15

30

45

60

AT BE BG CH CZ DE DK ES EU FR HU IR IT NL NO PL RU SE TR UA UK

Mirjam Kühne | Netnod Spring Meeting | March 2016 16

Awareness

• Are you aware you previously announced your IPv6 allocation to the global routing table?

0 10 20 30 40 50 60 70

yes

no

Mirjam Kühne | Netnod Spring Meeting | March 2016 17

Purpose

• What was the purpose of the announcement?

0 10 20 30 40 50

testproductiondon’t know

Mirjam Kühne | Netnod Spring Meeting | March 2016 18

Experiences

• What were your experiences during the announcement?

0 10 20 30 40 50

no problems

software issues

hardware issues

routing issues

security issues

customer complaints

Mirjam Kühne | Netnod Spring Meeting | March 2016 19

Experiences - Details (1)

• It was only a test- Announced IPv6 just for testing

- “Test customer hadn’t set up test-scenario yet”

• Hardware or software issues- New router and new set-up needed

- Need to re-configure firewall policy for core routers

- Documentation tools needed to keep records clean

Mirjam Kühne | Netnod Spring Meeting | March 2016 20

Experiences - Details (2)

• Lack of acceptance by other aspects of the business

• IPv6 not supported in my country

• Main engineer left- Are a lot of IPv6 deployments driven by a single person?

Mirjam Kühne | Netnod Spring Meeting | March 2016 21

Reasons

• Why did you disable your IPv6 announcement?

0 5 10 15 20 25

test

restructuring network

hardware issues

change of ISPno customer demand

political issues

bankruptcy

Mirjam Kühne | Netnod Spring Meeting | March 2016 22

Reasons - Details (1)

• No interest from customers

• Just testing- Wanted to get ready

- Switched it off until needed

• Network infrastructure changed- We changed something, didn’t re-enable IPv6 again (core

routers, data centre, …)

- Traffic moved to different IPv6 range

Mirjam Kühne | Netnod Spring Meeting | March 2016 23

Reasons - Details (2)

• Hardware or security issues- “Compatibility issues with old Cisco and new Juniper

equipment related to deployment of 6PE MPLS”

- “We were under a huge DDoS attack all the time”

- Routers didn’t survive stress testing over IPv6

• Service provider issues or issues with tunnel broker

• Didn’t realise that announcement stopped- Need for better monitoring tools?

Mirjam Kühne | Netnod Spring Meeting | March 2016 24

IPv4?

• Did you also stop your IPv4 announcements?

0 10 20 30 40 50 60 70

yes

no

Mirjam Kühne | Netnod Spring Meeting | March 2016 25

Plans

• When will you announce your IPv6 prefix again?

0 6 12 18 24 30

don’t know

in a few weeks

in a year

in 3 months

in 2 years

never

Mirjam Kühne | Netnod Spring Meeting | March 2016 26

Plans - Details

• Sorry - Fixed!

• Will return resources

• When customers want it

• Depends on upstream provider

Mirjam Kühne | Netnod Spring Meeting | March 2016 27

How Can the RIPE NCC Help?

• Provide more training

• Tips for addressing plans

• Pointers for best practices

• Discuss IPv6 with governments

https://ipv6actnow.org/

Mirjam Kühne | Netnod Spring Meeting | March 2016 28

Summary

• People appreciated us asking

• Still various issues- Hardware, software, upstream

• Lack of customer demand- Will customer demand for IPv6 ever exist?

• Monitoring tools missing

Questionsnathalie@ripe.net

mir@ripe.net