feedback from ripe ncc registration services · arin ripencc lacnic afrinic. alex le heux, ripe62,...

Feedback from RIPE NCC Registration ServicesAlex Le Heux - RIPE NCCRIPE62, May 2011, Amsterdam

Alex Le Heux, RIPE62, 2011-05-05

Outline

• ASN32 success, a competitive disadvantage?

• Last /8 implementation detail

• “Upgrade” of /32 IPv6 allocations

• IPv6 PI sore points and background information

2


ASN32 Update

3

0

75

150

225

300

2010-01 2010-03 2010-05 2010-07 2010-09 2010-11 2011-01 2011-03

2-btye4-byte


ASN32 Update

4

1%2%

86%

3%

8%

4-byte ASN Assignments

APNICARINRIPENCCLACNICAFRINIC


ASN32 Update

5

Returned25%

Not visble23%

Visible in BGP52%

RIPE NCC ASN32 Assignments

Competitive disadvantage?


Last /8 implementation

• Last /8 implementation:– Address space returned to the RIPE NCC after the last /8 policy comes into effect will be treated the same way as the last /8.

7


“Upgrade” of /32 allocations

• First IPv6 allocation on file: August 12, 1999

• Detailed deployment plans were rare in those days

• Years later, some holders of /32s realise they actually have a few million customers

• Solution: Return the /32 & re-evaluate

8

IPv6 PISore points and background information


IPv6 PI, Part III

• Report on Registration Services’ experience with the current policy

• Provide some background information and numbers relevant to the current IPv6 PI discussion

10


IPv6 PI, Part III

• Current IPv4 PI policy:– “PI space cannot be re-assigned or further assigned to other parties.”

– “IP addresses used solely for the connection of an End User to a service provider [...] are considered part of the service provider's infrastructure.”

11


IPv6 PI, Part III

• Current IPv6 policy:– “Assignments [...] are not to be sub-assigned to other parties.”

12


IPv6 PI, Part III

• No DSL

• No Cable

• VPN

• No co-location

• No virtual servers

• No SSL hosting

• No buts and no exceptions

13


IPv6 PI, Part III

• Sore points:– Thousands of current IPv4 PI space holders see no way to deploy IPv6

– Hard to explain why we can assign IPv4 but not IPv6

– Blurred distinction between ISP and end-user

14


IPv6 PI, Part III

• In the past, when ISPs were real ISPs and end-users were real end-users...

• The world was probably a simpler place

15

ISPPI

Customer


IPv6 PI, Part III

• In the past, when ISPs were real ISPs and end-users were real end-users...

• The world was probably a simpler place

16

ISPPI

Customer


IPv6 PI, Part III

17


IPv6 PI, Part III

18

MPLS


IPv6 PI, Part III

19

MPLS


IPv6 PI, Part III

20

MPLS


IPv6 PI, Part III

• Application Service Provider– Writes software for clients

– Then hosts the application as well

– Sets up a completely independent infrastructure for each client

– End-site? ISP?

21


IPv6 PI, Part III

• The sharp distinction between end-user and ISP is gone

• “Old-school” end-users still exist, of course

• But more and more complex services are built on top of other complex services built on top of...

22


IPv6 PI, Part III

• The complexity of deciding if something is an ISP or an end-user has increased

• If it even makes sense to make the distinction at all, in some cases

• This is hard to do in a fair and consistent manner

23


IPv6 PI, Part III

24

Background information


IPv6 PI, Part III

25Hosting

25%

Hosting & Access6%

Access36%

End-site33%

IPv4 PI Usage


IPv6 PI, Part III

26

0

75

150

225

300

2010-01 2010-03 2010-05 2010-07 2010-09 2010-11 2011-01 2011-03

IPv4 vs IPv6 PI Requests / month

IPv4 PIIPv6 PI


IPv6 PI, Part III

• Look at the IPv4 routing table to see what might happen with IPv6

– RIR delegated stats files

– Anything assigned or allocated before 1996 considered “legacy”

– RIS

– A prefix considered “in the DFZ” if seen by at least 10 RIS peers

27


IPv6 PI, Part III

28

legacy43%

assigned22%

allocated35%

Global IPv4 BGP prefixes


IPv6 PI, Part III

29

Legacy10%

PI assignments21%

LIR allocations70%

RIPE NCC Service region IPv4 BGP prefixes


IPv6 PI, Part III

• Summary, RIPE NCC service region:

30

Number given out

BGP entries in DFZ

Ratio

ALLOCATED 15417 59126 3.8

ASSIGNED 16340 17468 1.1

Questions?

feedback from ripe ncc registration services · arin ripencc lacnic afrinic. alex le heux, ripe62,...

Documents