Operational Activities and DevelopmentsAndrew de la Haye RIPE NCC COORIPE 66

Operational overview• Continuation and extension of Webinars• RIPE database improvements• Implementation of IP analyser and next steps• Certification enhancements• Implemented Live-chat

Most changes in Registration Services after IPv4 run-out

2

RS Activities

3

Maintaining a strong Registry

Registration Services Consolidation

Strong Registry

• 2007-01 Phase 3• Resource Quality Assistance• Legacy resource DB updates• RPKI support• Abuse reports investigations• Assisted Registry Checks

Resource Lifecycle

• IPv4 (last /8)• IPv6• ASNs• ENUM• End User contract transfers• Transfers• Resource de-registrations

Stakeholder Services

• LIR and IPv6 training courses• IPv6 Roadshows• NOG and RIPE Meeting support• RIPE Policy implementations

Registration Services ticket volume

4

0"

1000"

2000"

3000"

4000"

5000"

6000"

7000"

8000"

9000"

10000"

Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1"

2009" 2010" 2011" 2012" 2013"

#"Tickets"

2007601" AS"Number" Audit" IPv4"1st"Alloc" IPv4"Add"Alloc" IPv6" PA"Request" PI"Request" Registry"Issues"

Registration Services, May 2013

Last /8 IPv4 Allocation Policy• The RIPE NCC reached the last /8 on 14 September

2012• LIRs can receive one /22 (1,024 IPv4

addresses), even if they can justify a larger allocation– LIRs must already have an IPv6 allocation from an upstream LIR or the RIPE NCC

– 1553 /22s issued so far

5

Allocations from the last /8

6

0"

50"

100"

150"

200"

250"

Sep)12" Oct)12" Nov)12" Dec)12" Jan)13" Feb)13" Mar)13" Apr)13"

"#"/2

2"Alloca=o

ns"

ISPs" non)ISPs"

IPv4 Allocation Trend

7

0"

200"

400"

600"

800"

1000"

1200"

1400"

1600"

1800"

2009""""""" 2010""""""" 2011""""""" 2012""""""" 2013"""""""

#"Alloca0o

ns"

#"IPv4"First"Alloca0ons" #"IPv4"Addi0onal"Alloca0ons"

IPv4 Allocation Transfers

8

0"

10000"

20000"

30000"

40000"

50000"

60000"

70000"

80000"

90000"

100000"

0"

1"

2"

3"

4"

5"

6"

7"

8"

Oct/12" Nov/12" Dec/12" Jan/13" Feb/13" Mar/13" Apr/13"

Size"of"T

ransfers"

#"Transfers"

Permanent" Temporary" Permanent"Size" Temporary"Size"

Mergers Completed

9

0"

10"

20"

30"

40"

50"

60"

Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1"

2010" 2011" 2012" 2013"

#"Mergers"

IPv6 Allocation

10

0"

50"

100"

150"

200"

250"

Jan)09"

Apr)09"

Jul)09"

Oct)09"

Jan)10"

Apr)10"

Jul)10"

Oct)10"

Jan)11"

Apr)11"

Jul)11"

Oct)11"

Jan)12"

Apr)12"

Jul)12"

Oct)12"

Jan)13"

Apr)13"

IPv6"Alloca9ons"

IANA IPv4 depletion

APNIC IPv4 depletion

RIPE NCC IPv4 depletion

IPv6 Allocation Extensions

11

0"

5"

10"

15"

20"

25"

30"

35"

40"

45"

Jul+12" Aug+12" Sep+12" Oct+12" Nov+12" Dec+12" Jan+13" Feb+13" Mar+13" Apr+13"

#""IPv6"AllocaBo

n"Extensions"

/29" /30" /31"

2007-01 Update• Currently in Phase 3: Contacting End User directly

Challenges: – Lack of familiarity with RIPE Policy and the RIPE NCC– Identifying legitimate resource holder– Ensuring continuity of active networks

12

2007-01 Update

13

0"

5000"

10000"

15000"

20000"

25000"

30000"

35000"

40000"

Apr+09"

Jul+0

9"

Oct+09"

Jan+10"

Apr+10"

Jul+1

0"

Oct+10"

Jan+11"

Apr+11"

Jul+1

1"

Oct+11"

Jan+12"

Apr+12"

Jul+1

2"

Oct+12"

Jan+13"

Apr+13"

2007$01&$&Phase&2&&&3&

Resources"Resolved" Target"

2960%77%%

614%16%%

292%7%%

Results'(previous'6'mths)'

Approved%Docs%

Infra%

Returned%

24212$ 3326$ 6462$

0%$ 20%$ 40%$ 60%$ 80%$ 100%$

Contacted)Resource)Holders)

Resolved$ Contacted$ To$be$contacted$

Independent Resources: Maintenance

14

0"

500"

1000"

1500"

2000"

2500"

Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1"

2011" 2012" 2013"

#"Ch

anges"

RegID"&"Status"Change" RegID"Change" Status"Change" Other"Change" Return"

Abuse Report Handling

15

224#45%#

152#31%#

115#23%#

7#1%#

Breakdown*by*Catagory*

Handled#by#CS#(Spam/Hacking)#

Incorrect#Data#

Policy#ViolaCons#

Other#

116#76%#

36#24%#

Outcomes:*Incorrect*Data*

Inves.gated#3#no#problems#found#

Inves.gated#3#problems#resolved#

66"57%"19"

17%"

30"26%"

Outcomes:*Policy*Viola1ons*

Not"Policy"Viola5ons"

Insufficient"Informa5on"

Further"inquiries"

Registration Services, May 2013

Membership and Community Feedback (1)• Members and stakeholders survey 2011 has shown

demand for means of communication that are alternative to email

– Improved communication with Customer Services– Live chat

– Improved communication in Registration Services– Phone call to every new LIR explaining the process– RS deploying live chat for LIRs

– Policy and resource related questions

16

Registration Services, May 2013

Membership and Community Feedback (2)• High quality RIPE Registry

- Members and stakeholders survey 2011 the RIPE NCC to “improve the quality and usefulness of data in the RIPE Database”

- Resource Date Quality (RDQ) project; Inter RIR consistency project; 2007-01; Abuse-c

- Exhaustion of the RIPE NCC regular IPv4 pool- Number of contact moments between LIRs and the RIPE NCC

will diminish (e.g. additional allocation requests), therefore potential for the registry data quality to deteriorate

17

Assisted Registry Check• The existing Audit procedure is seen as ‘cumbersome’ and time

consuming for the LIR• In order to maintain a strong registry and align with the members

feedback, we are evolving our services• Assisted Registry Check

– Maintain the periodic contact moments between LIRs and the RIPE NCC– Reduce workload for LIRs– RIPE NCC provides a report highlighting our observations and recommendations

– Overview of registered information (e.g. contact details) – Overview of Internet Number Resource consistency (e.g. overlapping

assignments)– Overview of rDNS and route-objects consistency (e.g check lame reverse

delegations and routing registry vs BGP announcements)– Assist LIRs with improving the data accuracy

18

Questions?