This document provides an overview and update on various initiatives at the RIPE NCC, including: the depletion of IPv4 addresses, which is nearing exhaustion; updates to IPv6 policies and statistics showing growing IPv6 adoption; new tools like RIPEstat for analyzing registry data and RIPE Atlas for internet measurements; and changes to IPv4 and IPv6 allocation policies as resources dwindle. Key points include the RIPE NCC transitioning to allocating the final remaining /8 of IPv4 addresses and emphasizing IPv6 adoption and assignments.

1. What’s new at the
RIPE NCC?
PLNOG, Kraków, 28 September 2011
Ferenc Csorba
Trainer, RIPE NCC
ferenc@ripe.net

2. Topics - overview
• The Registry System
• IPv4 depletion
• IPv6 policy update and statistics
• RIPEstat, RIPE Atlas
2

3. The Registry System

4. The five RIRs
4

5. RIPE NCC
• Service region: Europe, Middle East and parts of
Central Asia
• Supports coordination of Internet operations
• Distributes and registers Internet resources
• Not-for-profit membership organisation
• 7,757 members
• Neutral, impartial, open and transparent
• RIPE: self regulated, open to everyone
5

6. RIPE NCC Activities
• Distributing and managing number resources
• Routing Registry
• Statistics and measurements
• Education
• K-root
• ENUM root zone
6

7. IP Address Distribution
7
IANA
7,757 LIRs
AfriNIC LACNICRIPE NCC APNICARIN
End Users

8. IPv6 Address Distribution
Allocation PA Assignment PI Assignment
IANA
End User
LIR
RIR
/3
/32
/12
/56/48 /48

9. Registration
9

10. Conservation
10

11. Aggregation
11

12. RIPE community
• Develops policies
• Open to everyone
• Communicates on Working Groups mailing lists
• Meets twice a year at RIPE Meetings.
12
• RIPE Meetings in 2011:
- RIPE 62 (Amsterdam, 2 - 6 May)
- RIPE 63 (Vienna, 31 October - 4 November)
• All new LIRs get two free tickets to attend
• Remote participation possible

13. Participate!
13

14. New RIPE policies
14
• Help make remaining IPv4 addresses last as
long as possible
• Help IPv6 deployment

15. IPv4 depletion

16. IANA IPv4 Pool
16
0%
10%
20%
30%
40%
2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011

17. IPv4 exhaustion phases
17
time
IANA pool
exhausted
IPv4 still available.
RIPE NCC continues
distributing it
Each of
the 5 RIRs
given a /8
RIPE NCC
reaches
final /8
RIPE NCC’s allocation
policy from last /8
applies
RIPE NCC
pool
exhausted
RIPE NCC can only
distribute IPv6
now
?

18. How Many Addresses Left?
18
http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph

19. Wait and See?

20. “Run Out Fairly”
• RIPE Policy Proposal 2009-03,“Run Out Fairly”
• Gradually reduced allocation / assignment periods
- 12 months (January 2010)
- 9 months (July 2010)
- 6 months (January 2011)
- 3 months (July 2011)
• 50% has to be used up by half-period
20

21. Get your IPs fast? Know how we evaluate!
• Want to know how get your resources fast?
- http://www.ripe.net/lir-services/resource-management/
contact/ipv4-evaluation-procedures
21

22. 0
64
128
192
256
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012
IPv4: allocations versus advertised
RIR Allocations Advertised
Data Projection
Today
22

23. Transfer of IPv4 allocations
• LIRs can transfer address blocks
- To another LIR
- Only when it’s empty
- Meets minimum allocation size (/21)
• Requests are evaluated by the NCC
• Registered in the RIPE database
23

24. Listing Services
• Platform to list address space you no longer
need
• For members only (LIR)
• Access via the LIR Portal
• Based on the “Transfer of Allocations Rules”
• Service included in the membership fee
24

25. Unannounced early registration addresses
• Identify legacy space which is currently not
announced on the internet
• Contact the holders about the possibility of
returning those addresses
• 400 organisations contacted
• And some blocks returned
25

26. The RIPE NCC’s last /8
26
How will distribution of the
last /8 differ?

27. The RIPE NCC’s last /8
27
• /16 reserved for unforeseen situations
• No PI assignments
• Only if LIR already has IPv6
• You must meet the criteria for an (additional)
allocation
• Each LIR can get one /22 allocation

28. How to request Independent Resources?
• Sponsoring LIR requests for End User
• Direct Assignment User request for themselves
• End User can become LIR
28

29. Charging for Resources
• 5 LIR categories: Extra Small to Extra Large
• For each category the fee is the same as in 2010
• Category determined by IPv4 and IPv6
allocations over time
• Direct assignments don’t influence category
• 50 Euro fee for every direct assignment
29

30. Have you got PI?
• Contract with End User required
- Example contract on RIPE NCC website
• Yearly charges for Independent Resources
- RIPE NCC Charging Scheme 2011
• enduser-contract@ripe.net
30

31. Don’t forget
• Reduced allocation/assignment periods
• Transfer of IPv4 address space
• Final /8
31

32. Future?
32
IPv6!

33. IPv6 ? Yes please!

34. IPv6 Ripeness
34
• Rating system:
- One star if the LIR has an IPv6 allocation
- Additional stars if:
- IPv6 Prefix is announced on router
- A route6 object is in the RIPE Database
- Reverse DNS is set up
- A list of all 4 star LIRs: http://ipv6ripeness.ripe.net/

35. IPv6 RIPEness in the RIPE NCC service region
35
No IPv6
55%
4 stars
16%
3 stars
10%
2 stars
5%
1 star
13%
1 star 2 stars 3 stars 4 stars No IPv6

36. IPv6 Ripeness in Poland
36
No IPv6
47%
4 stars
26%
3 stars
13%
2 stars
6%
1 star
8%
1 star 2 stars 3 stars 4 stars No IPv6

37. Ripeness per country (Poland & region)
37
0
200
400
600
800
1,000
Germany Russia Ukraine Poland Czech Republic
1 star 2 stars 3 stars 4 stars no IPv6

38. Ripeness per country, (%, Poland & region)
38
0%
20%
40%
60%
80%
100%
Germany Russia Ukraine Poland Czech Republic All (7757)
1 star 2 stars 3 stars 4 stars no IPv6

39. IPv6 enabled networks
39
0%
5%
10%
15%
20%
25%
30%
2004 2005 2006 2007 2008 2009 2010 2011
_RIR_RIPE_NCC RU PL UA DE CZ
http://v6asns.ripe.net

40. To get an IPv6 allocation
• You must:
- Be an LIR
- Have a plan for making assignments within two years
• Minimum allocation size /32
• Allocation size is based on customer numbers
and growth, not on transition technique!
40

41. Assigning IPv6 to customers
• Give your customers enough addresses
- Up to a /48
• For more addresses, send in request form
- Alternatively, make a sub-allocation
• Every assignment must now be registered in the
RIPE database
41

42. Grouping assignments in the RIPE DB
inet6num: 2001:db8:1000::/36
netname: Bluelight
descr: We want more Bluelight B.V.
descr: Colocation services
country: NL
admin-c: BN649-RIPE
tech-c: BN649-RIPE
status: AGGREGATED-BY-LIR
assignment-size: 48
mnt-by: BLUELIGHT-MNT
notify: noc@example.net
changed: noc@example.net 20110218
source: RIPE
42

43. Using AGGREGATED-BY-LIR
43
ALLOCATED-BY-RIR
ALLOCATED-BY-LIR
AGGREGATED-BY-LIR
assignment-size: 48
/40
/48 /48/48/48/48
ASSIGNED /44/36 AGGREGATED-BY-LIR
assignment-size: 56
/34
/56 /56/56/56/56

44. Route6 object:
Aut-num object:
IPv6 in the Routing Registry
44
aut-num: AS65550
mp-import: afi ipv6.unicast from AS64496 accept ANY
mp-export: afi ipv6.unicast to AS64496 announce AS65550
route6: 2001:DB8::/32
origin: AS65550

45. Getting IPv6 PI address space
• Minimum assignment size /48
• PI space can not be used for sub-assignments
• An organisation must:
- Demonstrate it will multihome *
- LIRs must demonstrate special routing requirements
- Meet contractual requirements
45

46. Contract for independent resources
46
enduser-contract@ripe.net

47. RESTful API
• Newly developed
• Query service released September 2011
• Update service currently in beta
– Planned to be released later this year
• Uses XML or JSON
– Plain html currently available for testing, this will be
removed later on!
• Details on http://labs.ripe.net
47

48. Tools for
Measurements &
Analysis
RIPEstat
&
RIPE Atlas

49. Beta: http://stat.ripe.net
Number
Registry
(RIPE DB)
Routing
Registry
(RIPE DB)
BGP
Routing
(RIS)
Active
Measuring
(TTM,
ATLAS)
Geo-
Location
(Maxmind
, …)
You

50. RIPEstat Strategy
• Immutable, sharable URLs for each result
• Add more history
• Multiple output formats (command line tool?)
• RIPEstat regular “Public Demos” (WebEx)
– Modular design --> agile development
– We demo new functionality every 4 weeks
– we receive comments and feedback
– You get the tools you ask for: get involved!
– Next public demo: Tuesday @ 11:30, 4th October

51. RIPE Atlas
• Next generation Internet measurement network
– To scale to thousands of measurement nodes
– Potentially “be everywhere” and ready to run different
measurements
– Started last November
– We’re still building it

52. Light Map of Europe
6

53. Ambitious Community Effort
Instead of building small, separate,
individual & private infrastructures,
build a
huge common infrastructure
that serves both the private goals
and the community goals.

54. Intuition -> Plan
• For accurate maps we need more probes
• Deploying very many TTM boxes too expensive
• Smaller probes
• Easily deployable
• USB powered
• 24 x 365 capable
8

55. Probes Deployed Today
10

56. Hosting = Credits = Measurements

57. RIPE Atlas - Security aspects
• Probes have hardwired trust material
(registration server addresses / keys)
• The probes don’t have any open ports, they only
initiate connections
– This works fine with NATs too
• Probes don’t listen to local traffic, there are no
passive measurements running
– There’s no snooping around
16

58. How we see k.root-servers.net (IPv6 RTT)

59. RIPE NCC Measurement Tools
• Tools for YOU
• Please support us by
– Using the tools
– Giving us feedback and ideas
– Telling your friends about them
– Finding sponsors for RIPE Atlas

60. Questions?

61. See you at RIPE 63!
Vienna, 31Oct-4 Nov 2011