The internet’s exponential growth has long stretched the limits of IPv4, making the transition to IPv6 not just an option, but a critical necessity for future-proofing networks. With IPv4 address exhaustion a persistent challenge, understanding how to secure your own IPv6 address space is paramount for organizations aiming for scalability, performance, and innovation. This comprehensive guide will walk you through the process of obtaining your own IPv6 addresses directly from the RIPE NCC (Réseaux IP Européens Network Coordination Centre), the Regional Internet Registry (RIR) responsible for Europe, the Middle East, and parts of Central Asia. We’ll cover everything from becoming a member to deploying your new address block, equipping you with the knowledge to navigate this essential transition.

The Foundation: Becoming a RIPE NCC Local Internet Registry (LIR)

To directly obtain IPv6 address space from the RIPE NCC, your organization must first become a Local Internet Registry (LIR). An LIR is an organization that receives allocations of Internet number resources (like IPv6 addresses and Autonomous System Numbers) from an RIR and then assigns or sub-allocates them to its own network infrastructure and/or its customers. This model empowers you with direct control over your address space, offering greater flexibility and independence compared to relying solely on upstream providers for assignments.

Becoming a RIPE NCC member, and thus an LIR, is a straightforward process designed for any legal entity or natural person. The benefits extend beyond just IPv6 addresses; LIRs gain access to various RIPE NCC services, training, and tools, as well as participation in the RIPE community’s policy development.

The LIR application typically involves these key steps:

1. Application Form: Complete the RIPE NCC Membership Application Form, providing details about your organization.
2. Due Diligence: The RIPE NCC will conduct checks to verify your documentation and ensure compliance with their procedures.
3. Standard Service Agreement (SSA): Upon successful verification, you will receive an SSA (or LIR Account Agreement for additional LIRs) and an invoice. This agreement outlines the terms of service.
4. Payment and Activation: Once the signed SSA and payment (a one-time sign-up fee and an annual membership fee) are received, your LIR account will be activated. You will then gain access to the secure LIR Portal.

Understanding RIPE NCC IPv6 Allocation Policies

Once your organization is a RIPE NCC LIR, you are eligible to request an IPv6 allocation. The RIPE community’s policies govern how this address space is distributed, ensuring fair and efficient use.

The minimum initial IPv6 allocation size available from the RIPE NCC is a /32. This might seem like a massive block compared to IPv4 allocations, but it’s designed to provide ample room for hierarchical addressing and future growth. Importantly, LIRs can request an initial allocation of up to a /28 without needing to provide extensive justification documentation. This simplifies the process for many organizations.

However, if your organization requires an initial allocation larger than a /28, you will need to provide additional documentation to justify the request. This justification typically includes:

• An addressing/subnetting plan detailing how the space will be used.
• A network topology diagram illustrating your infrastructure.
• The size and scope of end sites to be covered by the request.
• Statistics for past network growth (if applicable).
• A deployment plan for the IPv6 address space.

The RIPE NCC evaluates these requests based on factors like the number of users, the extent of your LIR infrastructure, hierarchical and geographical structuring, security segmentation, and planned longevity of the allocation.

It’s also worth noting that for organizations that do not wish to become a RIPE NCC member, a Provider Independent (PI) IPv6 assignment is an alternative. In this scenario, a RIPE NCC member (a sponsoring LIR) requests the PI assignment on your behalf. The minimum PI assignment size is typically a /48, and it’s intended for end-user organizations that will not further assign address space to other external entities.

The IPv6 Request Process via the LIR Portal

The LIR Portal is your central hub for managing your RIPE NCC membership and requesting Internet number resources. After your LIR account is active, you can log in to the portal to initiate your IPv6 allocation request.

The steps to request your IPv6 allocation generally involve:

1. Accessing the LIR Portal: Log in using your RIPE NCC Access account credentials.
2. Initiating a Request: Navigate to the section for requesting IPv6 resources.
3. Providing Information: You will be asked to supply specific details, including:
   • The type of request (e.g., an IPv6 allocation for providing services to your customers or for your own infrastructure).
   • Information about the people responsible for your LIR and its number resources, including a “maintainer object” to protect your registration information in the RIPE Database.
   • Confirmation that you intend to use the addresses for assignments or sub-allocations.
   • Confirmation that the addresses will be used on a network with an active presence in the RIPE NCC service region.
4. Justification (if needed): If you’re requesting an allocation larger than a /28, you’ll upload the supporting documentation as discussed previously.
5. Submission: Once you submit the request, a ticket will be opened, and the RIPE NCC staff will evaluate it against the applicable RIPE policies and procedures. They typically aim to contact you within one working day.

Upon approval, your new IPv6 allocation will be registered in the RIPE Database with a status of “ALLOCATED-BY-RIR”. You are then responsible for the correct registration of subsequent assignments and sub-allocations within your block in the RIPE Database.

Strategic IPv6 Deployment and Management

Receiving your IPv6 allocation is just the beginning. Effective deployment requires careful planning and adherence to best practices to maximize the benefits of the new protocol.

1. Crafting an Addressing Plan

A well-structured IPv6 addressing plan is crucial. Unlike IPv4, where addresses were a scarce resource, IPv6 offers an abundance that encourages a hierarchical and generous assignment strategy.

• Hierarchical Design: Design your address plan in a hierarchical manner to facilitate route aggregation and simplify network management.
• /48 for Sites: For enterprises and larger organizations, assigning a /48 prefix to each site is generally recommended. This provides 65,536 /64 subnets per site, offering immense flexibility for future expansion without renumbering.
• /64 for Subnets: A /64 prefix is the standard subnet size for IPv6, as it enables Stateless Address Autoconfiguration (SLAAC) and other fundamental IPv6 features.

2. Configuration Considerations

• Dual-Stack: A common strategy during the transition is dual-stack deployment, where both IPv4 and IPv6 run simultaneously on network devices. This ensures backward compatibility while gradually migrating services to IPv6.
• Router Advertisements (RA): For routers, servers, and infrastructure devices, it is often recommended to use manually configured static IPv6 addresses rather than relying on SLAAC. This provides more control and simplifies troubleshooting. Consequently, Router Advertisements (RA) for autoconfiguration should be carefully managed or disabled on internal network segments where static addressing is preferred.
• ICMPv6: Internet Control Message Protocol for IPv6 (ICMPv6) is fundamental to IPv6 operations, handling functions like Neighbor Discovery Protocol (NDP). Be cautious when filtering ICMPv6 traffic; blocking essential types can break network functionality.
• Security Policies: Implement equivalent IPv6 security policies to those you have for IPv4. IPv6 introduces new attack vectors and necessitates a thorough review of firewall rules and access controls.

3. Resource Management and Routing

• RIPE Database Registration: Continuously update the RIPE Database with your assignments and sub-allocations. This ensures accurate public records and aids in troubleshooting and coordination across the internet.
• Route Origin Authorizations (ROAs): Implement Resource Public Key Infrastructure (RPKI) and create ROAs for your IPv6 prefixes. RPKI allows you to cryptographically attest to the legitimacy of route announcements for your address space, protecting against BGP hijacking.
• Monitoring: Configure monitoring and logging for your IPv6 services to track performance, identify issues, and ensure high availability.

Related Articles

• BIMI + VMC + CMC: Boost Email Trust & Branding
• BGP (Border Gateway Protocol) Deep Dive
• Checksums Explained: Data Integrity Fundamentals
• Load Balancing Algorithms and Strategies

Conclusion

Obtaining your own IPv6 addresses from the RIPE NCC is a strategic step that provides independence, scalability, and prepares your network for the future. By becoming an LIR, understanding the allocation policies, and meticulously planning your deployment, your organization can effectively transition to the next generation of the Internet Protocol. While the process involves several administrative and technical considerations, the long-term benefits of embracing IPv6—including an expansive address space, improved efficiency, and enhanced security—far outweigh the initial effort. Embrace the future of the internet by taking control of your IPv6 destiny today.

References

1. RIPE NCC (2020). IPv6 Address Allocation and Assignment Policy.
2. The Number Resource Organization. RIPE NCC Membership.
3. RIPE NCC. Obtain and Register IPv6.
4. RIPE NCC. Become a RIPE NCC Member.
5. RIPE NCC (2012). Procedure for Becoming a Member of the RIPE NCC.
6. RIPE NCC. How to Request an IPv6 Allocation.
7. RIPE NCC. How to Become a Member.
8. RIPE NCC. Deploy IPv6 Now.
9. RIPE NCC. Assessment Criteria for IPv6 Allocations.
10. RIPE NCC (2024). IPv6 Initial Allocations /28 and extension to /28.
11. RIPE NCC. Basic Steps for RIPE NCC Members.
12. RIPE NCC. LIR Portal.
13. RIPE NCC. RIPE NCC Membership.
14. RIPE NCC. Basic IPv6 and RIPE NCC: A Comprehensive Guide.
15. Žorž, J., et al. (2017). Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose.
16. RIPE NCC. Every RIPE NCC member has an LIR Portal account.
17. RIPE NCC Forum (2024). How to Optimize IPv6 Deployment for a Medium-Sized Network?.
18. RIPE NCC. What is the LIR Portal?.
19. RIPE NCC. Configure and Deploy.
20. RIPE NCC. How to Request an IPv6 PI Assignment.
21. RIPE NCC. Basic IPv6 and RIPE NCC: A Comprehensive Guide.
22. RIPE NCC. Request IPv6.
23. RIPE NCC (2021). How to create ROAs on the RIPE NCC LIR Portal.