1 / 17

Feedback from RIPE NCC Registration Services

Feedback from RIPE NCC Registration Services. Alex Le Heux, RIPE NCC RIPE64 Ljubljana. Action points from RIPE63. Inbound transfer policy, do we need one? Why do LIRs need multiple routable IPv6 blocks?. Inbound transfer policy. History Inbound “ transfers ”

ina
Télécharger la présentation

Feedback from RIPE NCC Registration Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Feedback from RIPE NCC Registration Services • Alex Le Heux, RIPE NCC • RIPE64 Ljubljana

  2. Action points from RIPE63 • Inbound transfer policy, do we need one? • Why do LIRs need multiple routable IPv6 blocks?

  3. Inbound transfer policy • History • Inbound “transfers” • ERX Project – legacy space only • Outbound “transfers” • AfriNIC • Future • Non-legacy space transfers • Community needs to define policy

  4. Multiple routable blocks for LIRs • Reasons why LIRs want multiple blocks • Non-routed infrastructure • Non-contiguous networks • Future divestment • National governments

  5. Multiple routable blocks for LIRs • Non-routed infrastructure • IPv6 PI-for-LIRs works well in this case • Non-contiguous networks • Currently no solution • 2011-04 is one that will work for most cases • Future divestment • Also currently no solution • Perhaps 2011-04 as well, if we split up the /29

  6. Multiple routable blocks for LIRs • National governments • Unique political situation • States/provinces/… are often independent • Want separately routable blocks, just in case • Could set up their own LIR, if they wanted • Central government would like to prevent this, but can’t stop them legally • Address policy does not take this into account

  7. 2011-02 – IPv6 PI multi-homing

  8. Listing Service, unused allocations, … • Listing Service lists unused allocations that can be transferred to another LIR • Unused allocations? • Shouldn’t those be returned or deregistered?

  9. Listing Service, unused allocations, … • Relevant documents: • Listing Service Terms and Conditions • RIPE-533 – Standard Service Agreement • RIPE-530 – IPv4 Address Policy • RIPE-541– Closure and de-registration…

  10. Listing Service Terms and Conditions • Article 3.2 • “The Member may use the Listing Service as a platform for the facilitation of the Transfer of IPv4 Allocations according to the RIPE policies”

  11. RIPE-533 – Standard Service Agreement • Article 6.1 • The Member acknowledges applicability of, and adheres to, the RIPE Policies and RIPE NCC procedural documents

  12. RIPE-530 – IPv4 Address Policy (1) • Section 5.0 – Policies and guidelines for allocations • …

  13. RIPE-530 – IPv4 Address Policy (2) • Section 6.6 • “All assignments are valid as long as the original criteria on which the assignment was based are still valid …” • Assignments != Allocations

  14. RIPE-541 – Closure and de-registration • Section B.1.1.b • “When the original technical requirements or the business purpose for the use of the Internet number resources change, the allocation/assignment becomes invalid.” • “… the RIPE NCC is authorised to deregister the relevant Internet number resources.”

  15. RIPE-530 – IPv4 Address Policy (3) • Section 5.5 – Transfer of allocations • “Any LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by either the RIPE NCC or the IANA.” • “Such address space must not contain any block that is assigned…”

  16. Conclusion • RIPE-541 – Closure and deregistration… • Authorises the RIPE NCC to deregister an unused allocation” • RIPE-530 – IPv4 Address Policy • Permits transfers of allocations • Requires the allocation to be unused • Listing an allocation on the Listing Service • Declares the intent to transfer

  17. Questions?

More Related