1. Rob Blokzijl, RIPE 64, 16-20 April 2012 IPv4 Maintenance Policy

2. Rob Blokzijl, RIPE 64, 16-20 April 2012 12 August 2012 + 1 year + 2 years etc …. 2

3. Rob Blokzijl, RIPE 64, 16-20 April 2012 Introduction RIPE NCC’s pool of available IPv4 addresses nearing exhaustion Still a need to maintain IPv4 address space in the RIPE Registry When IPv4 pool is exhausted, many of the existing policies will become outdated and/or irrelevant Need to consolidate and simplify into one IPv4 document 3

4. Rob Blokzijl, RIPE 64, 16-20 April 2012 Developing the Proposal Cross-departmental team from the RIPE NCC worked with RIPE Chair over the course of 2011 developing the document Key policies reviewed: – RIPE-530 IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region – RIPE-526 Temporary Internet Number Assignment Policy Also: legacy space, last /8, transfers, etc... 4

5. Rob Blokzijl, RIPE 64, 16-20 April 2012 The Registry Maintaining the Registry will be the most important IPv4 related activity for many years to come 5

6. Rob Blokzijl, RIPE 64, 16-20 April 2012 All-Inclusive IPv4 Maintenance Policy policy includes: – Contractual relationships in the RIPE NCC service region – IPv4 registration maintenance – Transfer of allocations – Allocations from the last /8 – Unforeseen circumstances – Legacy space – Temporary assignments 6

7. Rob Blokzijl, RIPE 64, 16-20 April 2012 Question… Do YOU like this approach 7

8. Rob Blokzijl, RIPE 64, 16-20 April 2012 Next Steps... Complete the document Send policy proposal to APWG mailing list Get feedback from the RIPE community 8

9. Questions?