The document presents an overview of obtaining IPv4 addresses and the current status of allocation and distribution policies set by the RIPE community. It discusses the final IPv4 allocation from the last /8, options for acquiring IPv6 allocations, and the process for transferring IPv4 address resources, including mergers and acquisitions. Additionally, it addresses security concerns related to hijacking of IPv4 addresses and encourages members to keep their registry data accurate and up-to-date.

1. Obtaining IPv4 Addresses
Andrew de la Haye
Chief Operations Officer
RIPE NCC Regional Meeting | Almaty – Kazakhstan | June 2014

2. The Internet Registry System 2
RIPE NCC Regional Meeting – June 2014
AFRINIC
Africa
APNIC
Asia Pacific
ARIN
North America
LACNIC
Latin America
RIPE NCC
Eurasia
Middle East

3. IPv4 Address Distribution 3
Allocation PA Assignment PI Assignment
RIPE NCC Regional Meeting – June 2014
/0
/22
/8
IANA
RIR
LIR
/23 /25 /24 End User

4. Distribution of Internet Number Resources
• Distribution of IP addresses is based on policies set by the
RIPE community
- The RIPE community is a collaborative forum open to
anyone
- The RIPE community develops and sets policies
through open, bottom-up process of discussion and
consensus-based decision making
- Policy proposals are discussed in the Address Policy
Working Group mailing list
http://www.ripe.net/ripe/mail/wg-lists
RIPE NCC Regional Meeting – June 2014
4

5. Getting an IPv4 Allocation From the Last /8 5
• Every member can get one final /22 allocation:
- Both new and existing members
- 16,000 x /22 in a /8
- About 3,700 x /22 issued so far
- Any returned address space goes into the free pool
• A /11 just received from IANA and added to the free pool
• Only applies if the member already holds an IPv6
allocation
RIPE NCC Regional Meeting – June 2014

6. RIPE NCC IPv4 Pool 6
http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph
RIPE NCC Regional Meeting – June 2014

7. Allocations From the Last /8 7
300"
250"
200"
150"
100"
50"
0"
Oct*12"
Nov*12"
Sep*12"
Feb*13"
Mar*13"
Jan*13"
Dec*12"
RIPE NCC Regional Meeting – June 2014
Jun*13"
Apr*13"
May*13"
Sep*13"
Jul*13"
Aug*13"
Oct*13"
Nov*13"
Jan*14"
Dec*13"
Apr*14"
May*14"
Feb*14"
Mar*14"
AddiAonal"
1st"

8. IPv4 Allocations by Country - Regional 8
140"
120"
100"
80"
60"
40"
20"
0"
KZ" GE" AZ" AM" KG" UZ" TJ" TM"
RIPE NCC Regional Meeting – June 2014

9. IPv4 Addresses by Country - Regional 9
3000000"
2500000"
2000000"
1500000"
1000000"
500000"
0"
KZ" GE" AZ" AM" KG" UZ" TJ" TM"
RIPE NCC Regional Meeting – June 2014

10. Getting an IPv6 Allocation 10
• To qualify, an organisation must:
- Be a member of the RIPE NCC
- Have a plan for making assignments within two years
• The minimum allocation size is a /32
- Up to a /29 without additional justification
- The initial /32 can be extended up to a /29 on request
RIPE NCC Regional Meeting – June 2014

11. Members With IPv4/IPv6 Address Space 11
RIPE NCC Regional Meeting – June 2014
0%#
10%#
20%#
30%#
40%#
50%#
60%#
70%#
80%#
90%#
100%#
2003-01#
2003-05#
2003-09#
2004-01#
2004-05#
2004-09#
2005-01#
2005-05#
2005-09#
2006-01#
2006-05#
2006-09#
2007-01#
2007-05#
2007-09#
2008-01#
2008-05#
2008-09#
2009-01#
2009-05#
2009-09#
2010-01#
2010-05#
2010-09#
2011-01#
2011-05#
2011-09#
2011-12#
2012-04#
2012-08#
2012-12#
2013-04#
2013-08#
2013-12#
2014-04#
v4&v6# v6only# v4only#

12. IPv6 Allocations by Country - Regional 12
30"
25"
20"
15"
10"
5"
0"
AZ" KZ" AM" GE" KG" UZ" TJ" TM"
RIPE NCC Regional Meeting – June 2014

13. Need More IPv4 Address Space? 13
• Two different types of transfers
- Mergers and acquisitions
- Transfers of allocations using the RIPE transfer
policy
RIPE NCC Regional Meeting – June 2014

14. Mergers and Acquisitions 14
• If an organisation (or part of it) is being sold, the Internet
number resources in use on its network can be transferred
• Documentation requested:
- Merger/purchase agreement
- Company registration papers for both parties
- New “Independent Assignment Request and Maintenance
Agreement” (only for Independent Resources)
• Based on ripe-595
RIPE NCC Regional Meeting – June 2014

15. Mergers Completed 15
60"
50"
40"
30"
20"
10"
0"
Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1" Qtr2" Qtr3" Qtr4" Qtr1"
2010" 2011" 2012" 2013" 2014"
#"Mergers"
RIPE NCC Regional Meeting – June 2014

16. Transfer of Allocations Using the Transfer Policy 16
• Policy requirements
- Transfers between LIRs only
- The LIR must confirm it will make assignment(s) from the
allocation
- Transfer can be permanent or temporary
- List of transferred allocations is published
• Documentation requested
- Signed RIPE NCC Transfer Agreement
- Company registration papers for both parties
• Based on ripe-606
RIPE NCC Regional Meeting – June 2014

17. Transfers Completed 17
60"
50"
40"
30"
20"
10"
Feb/13"
RIPE NCC Regional Meeting – June 2014
1000000"
900000"
800000"
700000"
600000"
500000"
400000"
300000"
200000"
100000"
0"
0"
Jan/13"
Mar/13"
Apr/13"
May/13"
Jun/13"
Aug/13"
Jul/13"
Sep/13"
Oct/13"
Nov/13"
Dec/13"
Feb/14"
Jan/14"
Mar/14"
Apr/14"
May/14"
Size%of%Transfers%
#%of%Transfers%
Number"of"Transfers" Size"of"Transfers"

18. IPv4 Transfer Listing Service 18
• Enables LIRs looking to transfer allocations to find receiving
parties
• LIRs can also publish that they need resources
• Member-only service through the LIR Portal
• The RIPE NCC has no interest in financial transactions
• Transfers must follow transfer the policy in ripe-606
RIPE NCC Regional Meeting – June 2014

19. 19
RIPE NCC Regional Meeting – June 2014

20. 20
RIPE NCC Regional Meeting – June 2014

21. Brokers 21
• Some members may decide to use a broker to facilitate the
transfer process
• Listing of “recognised brokers” on the website
- Brokers who have signed an agreement to follow
• RIPE policies
• RIPE NCC procedures
http://www.ripe.net/lir-services/resource-management/ipv4-transfers/brokers
RIPE NCC Regional Meeting – June 2014

22. Where Does the RIPE NCC Stand? 22
• Ensuring that transfers follow RIPE policy
• Supporting our members through the transfer process
• The RIPE NCC has no interest in financial transactions
• Our ultimate priority is keeping the registry up-to-date
• Support you in protecting your resources!
RIPE NCC Regional Meeting – June 2014

23. Increased Risk for Hijacks
• IPv4 addresses are becoming more valuable
• Criminals try very sophisticated methods to obtain control
over (apparently) unused address blocks:
- Faking registration and identity papers
- Faking entire websites and domains
• RIPE NCC has to do more thorough checks:
- Unfortunately, it can take extra time to process requests
- Please cooperate in supplying the required documents
RIPE NCC Regional Meeting – June 2014
23

24. Help Us Protect Your Resources
• Hijacks often target address blocks with outdated contact
details
• Make sure your contact persons and company details are
up-to-date
- Check the LIR Portal and update contacts
- Verify all entries in RIPE Database are correct
- Process any changes right away
RIPE NCC Regional Meeting – June 2014
24

25. Help Us Protect Your Resources
• If acquiring resources, ensure you are in contact with the
legitimate holder or representative
• If you need help, or think your resources may have been
hijacked, contact: reg-review@ripe.net
https://www.ripe.net/lir-services/resource-management/address-hijacking-in-the-ripe-ncc-service-region
RIPE NCC Regional Meeting – June 2014
25

26. Assisted Registry Check (ARC)
https://labs.ripe.net/Members/matt_parker/assisted-registry-check-first-results
RIPE NCC Regional Meeting – June 2014
26
• Need for current and accurate registry data
• Previous audit activities considered “time-consuming
and disruptive” by members
- Provide a more efficient, less time-consuming experience for
the member

27. Policy Proposals and Transfers 27
There are a number of policy proposals aimed at facilitating
transfer of IPv4 addresses between organisations
• Policy proposal 2014-04 - ‘Allow IPv4 PI transfer’
- Policy proposal would allow holders of Provider Independent
(PI) IPv4 addresses to transfer those to other organisations
RIPE NCC Regional Meeting – June 2014

28. Policy Proposals and Transfers (2) 28
• Policy proposal 2014-01 - ‘Abandoning the Minimum
Allocation Size for IPv4’
- Policy proposal would remove the /22 minimum allocation
size. This would allow LIRs to transfer even small blocks of
IPv4 addresses to other LIRs
• Policy proposal 2014-05 - ‘Policy for Inter-RIR Transfers of
Internet Resources’
- Policy proposal would allow the transfer of Internet number
resources from an LIR of another Regional Internet Registry
(RIR) to an entity or LIR within the RIPE NCC service region
RIPE NCC Regional Meeting – June 2014

29. Policy Proposals 29
• The RIPE Policy Development Process process is open to
everyone
• Participate and let your voice be heard
• If you would like support in order to propose a new policy,
contact us at pdo@ripe.net
• http://www.ripe.net/ripe/policies/current-proposals/current-policy-
proposals
RIPE NCC Regional Meeting – June 2014

30. Questions? 26
RIPE NCC Regional Meeting – June 2014