Andrzej Wolski – I am trainer at RIPE NCC where I develop, manage and deliver trainings mostly about Internet Governance, RIR/LIR aspects of numeric resource distribution and best practices in IP assignment and Internet Routing with focus on RPKI in general. You can find my speaker profile at RIPE NCC website
Topic of Presentation: IPv4 Transfers
Language: Polish
Abstract: On 14 September 2012, the RIPE NCC reached its Last /8. Since then, the supply of unallocated IPv4 space has been limited to a single /22 for each Local Internet Registry. Since then there has been a growing interest in transfers of IPv4 allocations under the RIPE Transfer Policy. In this presentation I will describe the transfer process, policies and procedures in the RIPE NCC service region as well as provide the background information on how we got to this point in time and a glimpse of what will come in the future, such as inter-RIR transfers.
2. Internet Registry System 2
PLNOG 13 - September 2014
IANA
AFRINIC
Africa
APNIC
Asia Pacific
ARIN
North America
LACNIC
Latin America
RIPE NCC
Eurasia
Middle East
3. Who are we? 3
PLNOG 13 - September 2014
• RIPE NCC
• Located in Amsterdam
• Not for profit membership
organisation
• One of five RIRs
• RIPE Community
• Open community
• Develops policies
• Organised in Working Groups
4. What do we do? 4
• Distribute IP addresses and AS numbers
• Support RIPE community
• RIPE Database
• Reverse DNS and K-root server
• Resource Certification (RPKI)
• Training
• Research and Statistics
• Tools and measurements
• RIPE Atlas, RIPEstat
PLNOG 13 - September 2014
5. IPv4 Distribution 5
Allocation PA Assignment PI Assignment
PLNOG 13 - September 2014
IANA
RIR
End User
/0
/21
/8
/23 /25 /24
LIR
7. RIPE NCC IPv4 Pool 7
“On 14 September 2012, the RIPE NCC
ran out of their regular pool of IPv4”
PLNOG 13 - September 2014
8. IPv4 Distribution Post Exhaustion 8
Allocation PA Assignment PI Assignment
PLNOG 13 - September 2014
/0
/22
/8
IANA
RIR
LIR
/23 /25 /24 End User
9. Allocations From the Last /8
PLNOG 13 - September 2014
9
• LIR can receive one /22 (1,024 IPv4 addresses),
even if they can justify a larger allocation
• Both new and existing LIRs
• LIRs must already have an IPv6 allocation from an
upstream LIR or the RIPE NCC
• over 4,400 /22 issued so far
!
• No new IPv4 Provider Independent (PI) address
space
13. Need More IPv4 Address Space?
PLNOG 13 - September 2014
13
• Three different types of Intra-RIR
transfers:
• Mergers and acquisitions
• Transfers of allocations
• Legacy space transfers
14. Mergers and Acquisitions
PLNOG 13 - September 2014
14
• If an organisation (or part of it) is being sold, the
Internet number resources in use by 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 Provider Independent resources)
• Based on procedural document ripe-595
15. Transfers of Allocations
PLNOG 13 - September 2014
15
• Policy requirements
• Only between LIRs
• 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 procedural document ripe-622, section 5.5
16. IPv4 Transfer Listing Service
PLNOG 13 - September 2014
16
• Member only service through the LIR Portal
• Enables LIRs to:
• Offer address space
• Request address space
• Currently:
• 874,496 IPs offered
• 14,265,088 IPs requested
• The RIPE NCC has no interest in financial
transactions
20. Legacy Space Transfers
PLNOG 13 - September 2014
20
• IPv4 address space that was distributed prior
to the formation of the Regional Internet
Registry system
• The RIPE NCC is able to support transfers of legacy space
with or without contractual relationship (Service agreement,
Sponsoring LIR)
!
!
Any questions?
Contact: legacy@ripe.net
21. Brokers
PLNOG 13 - September 2014
21
• Some members may decide to use a broker to
facilitate the transfer process
! • Listing of “Recognised IPv4 Transfer Brokers”
• Brokers who have signed an agreement to follow
• RIPE policies
• RIPE NCC procedures
• These brokers are not endorsed by the RIPE NCC and
do not act on behalf of the RIPE NCC
!
http://www.ripe.net/lir-services/resource-management/ipv4-transfers/brokers
22. Where Does the RIPE NCC Stand?
PLNOG 13 - September 2014
22
• Ensuring that transfers follow RIPE policy
!
• Supporting our members through the
transfer process
!
• Support you in protecting your resources!
23. Where Does the RIPE NCC Stand?
PLNOG 13 - September 2014
23
Our ultimate priority
is keeping the
registry up-to-date!
24. Increased Risk for Hijacks
PLNOG 13 - September 2014
24
• IPv4 addresses are becoming more valuable
• Criminals will try any methods to obtain control over
address blocks:
• Faking registration and identity papers
• Forged stamps and signatures
• Faking entire websites and domains
• RIPE NCC has to do more thorough checks:
• Extra time to process requests
• Please cooperate in supplying the required documents
25. Acquiring Resources
PLNOG 13 - September 2014
25
If acquiring resources, ensure you are in contact
with the legitimate holder or representative
!
!
Need help?
Contact: reg-review@ripe.net
26. Policy Proposals and Transfers
PLNOG 13 - September 2014
26
• 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
! • Policy proposal 2014-02 - ‘Allow IPv4 PI transfer’
• Policy proposal would allow holders of Provider Independent (PI) IPv4
addresses to transfer those to other organisations
27. Participate in discussions
PLNOG 13 - September 2014
27
• The RIPE Policy Development 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