ripe ncc status update

39
RIPE NCC Status Update IPv4 and more Marco Hogewoning, Trainer

Upload: ripe-ncc

Post on 12-Nov-2014

1.657 views

Category:

Technology


1 download

DESCRIPTION

Presentation given by Marco Hogewoning at NETNOD

TRANSCRIPT

Page 1: RIPE NCC Status Update

RIPE NCC Status UpdateIPv4 and more

Marco Hogewoning, Trainer

Page 2: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

The five RIRs

2

Page 3: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

RIPE NCC

• Service region: Europe, Middle East and parts of Central Asia

• Supports coordination of Internet operations

• Not-for-profit membership organisation

• Over 7,000 members

• Neutral, impartial, open and transparent

• RIPE: self regulated, open to everyone

3

Page 4: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Agenda

• Resource distribution– IPv4 exhaustion and policy

– IPv6 policy change

• Statistics and measurements– IPv6 statistics

• Outreach and education– Training courses

– Meetings

• New projects

4

Page 5: RIPE NCC Status Update

IPv4 Run Out

Page 6: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv4 distribution

6

IANA

7,000 LIRs

AfriNIC LACNICRIPE NCC APNICARIN

End Users

IANA 3 February 2011

AfriNIC LACNICRIPE NCC APNICARIN ?

Page 7: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Our slice of the IPv4 pie

APNIC

ARIN

LACNIC

AfriNIC

Organisations

Other IANA

7

RIPE NCC

Page 8: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv4 exhaustion phases

8

time

IANA pool exhausted

IPv4 still available. RIPE NCC continues

normal operation

Each of the 5 RIRs received

a /8

RIPE NCC reaches final /8

Final /8 policy triggered

RIPE NCC pool

exhausted

RIPE NCC can only distribute IPv6

now

Page 9: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Business as usual

• As long as there are IPv4 addresses left, the RIPE NCC will keep on distributing them

• Same allocation and assignment policies still apply (RIPE-509)

• Until the final /8 is reached

9

Page 10: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

“Run Out Fairly”

• Gradually reduced allocation and assignment periods

• Needs for “Entire Period” of up to... – 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

10

Page 11: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Final /8 policy

• Each LIR can get one /22 allocation

• You must meet the criteria for an (additional) allocation

• Only when you already have IPv6 addresses

• A /16 is reserved for unforeseen circumstances

• No provider independent (PI) assignments

11

Page 12: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Transfer of IPv4 allocations

• LIRs can transfer IPv4 address blocks:– To another LIR

– Only when the block is not in use

– Meets minimum allocation size (/21)

• Requests are evaluated by the RIPE NCC

• Registered in the RIPE Database

12

Page 13: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

No changes yet

• Policy will only change when the RIPE NCC’s final /8 is reached

• Be aware of the shorter assignment period!

• And start deploying IPv6 now!

13

Page 14: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Registration Data Quality (RDQ) project

• Comparing various information sources:– RIPE Database

– Internal registration files

– RIS (Routing Information Service)

• Find and fix inconsistencies

• Strengthen data quality where necessary

14

Page 15: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Unannounced early registration addresses

• Builds on the RDQ project

• Identify legacy space which is currently not announced

• Contact the holders about the possibility of returning those addresses

• Over 400 organisations contacted already

• ~ 500k addresses returned over the past two months

15

Page 16: RIPE NCC Status Update

IPv6

Page 17: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Registration of IPv6 assignments

• Until now:– Assignments up to a /48 didn’t need to be registered in the RIPE Database

– Had to be registered at the LIR level

– Very ambiguous policy text

– What to register?

– What means accessible by the RIR?

17

Page 18: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Registration of IPv6 assignments (2)

• All assignments must now be registered in the RIPE Database

• This includes existing assignments

• Method introduced to minimise the number of objects you have to create and maintain

18

Page 19: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Grouping of assignments

• New status value: AGGREGATED-BY-LIR

• New attribute called assignment-size

• Create one object covering multiple assignments that share description and contacts

• Indicating the size of individual assignments

19

Page 20: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Registering all assignments

20

/56 /56/48/48/48

/48 /48 /56

/48 assignment =< /48

ALLOCATED-BY-RIR

ALLOCATED-BY-LIR ASSIGNED /44/36

Page 21: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Using AGGREGATED-BY-LIR

21

ALLOCATED-BY-RIR

ALLOCATED-BY-LIR

/48 /48/48/48/48

AGGREGATED-BY-LIRassignment-size: 48 /40

hint :)

ASSIGNED AGGREGATED-BY-LIRassignment-size: 56 /34/44/36

Page 22: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

AGGREGATED-BY-LIR

22

inet6num:        2001:db8:1000::/36netname:         Bluelightdescr:           We want more Bluelight B.V.descr:      Colocation servicescountry:          NLadmin-c:         BN649-RIPEtech-c:          BN649-RIPEmnt-by:          BLUELIGHT-MNTnotify:          [email protected]:        [email protected] 20110218source:         RIPE

Page 23: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

AGGREGATED-BY-LIR

23

inet6num:        2001:db8:1000::/36netname:         Bluelightdescr:           We want more Bluelight B.V.descr:      Colocation servicescountry:          NLadmin-c:         BN649-RIPEtech-c:          BN649-RIPE

mnt-by:          BLUELIGHT-MNTnotify:          [email protected]:        [email protected] 20110218source:         RIPE

status:          AGGREGATED-BY-LIR

assignment-size: 48

Page 24: RIPE NCC Status Update

IPv6 Statistics

Page 25: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 allocations and announcements

25

0

1000

2000

3000

4000

5000

6000

2004 2005 2006 2007 2008 2009 2010 2011

RIPE NCC AllocationsTotal Worldwide AllocationsTotal Worldwide Announcements

Page 26: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 statistics

• RIPEness rating system. Stars awarded for:– Requesting an allocation

– Creating a route object

– Announcing your space

– Setting up reverse DNS

• Free t-shirt if you make it to 4 stars :)

26

Page 27: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 RIPEness: total (7,350 LIRs)

27

4 stars13%

3 stars9%

2 stars5%

1 star12%

No IPv662%

Page 28: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 RIPEness: Sweden ( 251 LIRs)

28

4 stars18%

3 stars8%

2 stars2%

1 star14%

No IPv658%

Page 29: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 RIPEness: region

29

0

100

200

300

400

Sweden Norway Finland Denmark Netherlands France Spain Switzerland

No IPv6 1 star 2 star 3 star 4 star

Page 30: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

IPv6 RIPEness: region

30

0%

25%

50%

75%

100%

Sweden Norway Finland Denmark Netherlands France Spain Switzerland

No IPv6 1 star 2 star 3 star 4 star

Page 31: RIPE NCC Status Update

Outreach

Page 32: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Training courses

• LIR, IPv6 and Routing Registry courses

• Locations throughout the RIPE NCC service region

• ‘Standalone’ but also in conjunction with other events, like NOG meetings

• 33 courses now scheduled until end Q2 2011

• See https://lirportal.ripe.net/training/courses

32

Page 33: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Meetings

• RIPE 62 in Amsterdam, 2 - 6 May 2011

• Regional meetings 2011:– Damascus, Syria (14 - 15 May date changed)

– Moscow, Russia (6 - 8 June)

– Dubrovnik, Croatia (7 - 9 September TBC)

– Muscat, Oman ( 27 - 28 September)

• RIPE 63 in Vienna, Austria ( 31 October - 4 November 2011)

33

Page 34: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

Other events

• MENOG IPv6 Roadshows (dates tbc)– 5 day technical workshops

– Amman (JO), Riyadh (SA), Dubai (AE) and others

• Roundtable Meetings– Next one coming up 4 April 2011, Amsterdam (NL)

– Invite only

34

Page 35: RIPE NCC Status Update

Projects

Page 36: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

RIPE Database API

• RESTful web interface

• Data returned in XML

• API documentation on RIPE Labs

• For a demo visit http://lab.db.ripe.net/portal/

36

Page 37: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

RIPEstat

• Toolbox to access the various datasets the RIPE NCC publishes:– Resource registration details

– Routing Information Service (RIS)

– Test Traffic Measurements (TTM)

• Public demo sessions every four weeks using webex, see http://labs.ripe.net/ripestat

37

Page 38: RIPE NCC Status Update

Marco Hogewoning, 10 March 2011

More information

• http://ripe.net/v4exhaustion

• http://www.ipv6actnow.org

• http://ripeness.ripe.net

• http://labs.ripe.net

38

Page 39: RIPE NCC Status Update

Questions?