You are here: Home > Publications > RIPE Document Store > IPv6 Address Allocation And Assignment Policy

Changes to IPv6 Address Allocation And Assignment Policy

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-450: ripe-707: IPv6 Address Allocation And and Assignment Policy


This document defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other organisations . organisations. It was developed through joint discussions among the APNIC, ARIN and RIPE communities.

insert: <hr />


1. Introduction
1.1. Overview
2. Definitions
2.1. Internet Registry (IR)
2.2. Regional Internet Registry (RIR)
2.3. National Internet Registry (NIR)
2.4. Local Internet Registry (LIR)
2.5. Allocate
2.6. Assign
2.7. Utilisation
2.8. HD-Ratio
2.9. End Site
3. Goals of IPv6 address space management
3.1. Goals
3.2. Uniqueness
3.3. Registration
3.4. Aggregation
3.5. Conservation
3.6. Fairness
3.7. Minimised Overhead
delete: <a href="#conflicts"> insert: <a href="#conflict"> 3.8. Conflict of goals Goals
4. IPv6 Policy Principles
4.1. Address space not to be considered property
4.2. Routability not guaranteed
4.3. Minimum Allocation
4.4. Consideration of IPv4 Infrastructure
5. Policies for allocations and assignments
5.1. Initial allocation delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.1.1. Initial allocation criteria delete: </a> delete: <br /> for LIRs insert: </a> insert: <a href=""> insert: <br />
insert: </a>
5.1.2. Initial allocation size delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.2. Subsequent allocation delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.2.1. Subsequent allocation criteria delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.2.2. Applied HD-Ratio delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.2.3. Subsequent Allocation Size delete: <br /> delete: <a href="#lir_to_isp"> insert: <a href=""> insert: <br />
insert: </a>
insert: <a class="anchor-link" href="#lir-to-isp"> 5.3. LIR-to-ISP allocation delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.4. Assignment delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.4.1. Assignment address space size delete: <br /> delete: <a href="#assignment_multiple"> insert: <a href=""> insert: <br />
insert: </a>
insert: <a href="#assignments_shorter"> 5.4.2. Assignments shorter than a /48 to a single End Site delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.4.3. Assignment to operator's infrastructure delete: <br /> delete: <a href="#registration_assignment"> insert: <a href=""> insert: <br />
insert: </a>
insert: <a class="anchor-link" href="#registration2"> 5.5. Registration delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.6. Reverse lookup delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
5.7. Existing IPv6 address space holders delete: <br /> delete: <a href="#experiment-assignments"> insert: <a href=""> insert: <br />
insert: </a>
insert: <a href="#anycasting"> 6. Assignments for Internet Experiments delete: </a> delete: <br /> delete: <a href="#defining-experiment"> 6.1. Defining the experiment delete: </a> delete: <br /> delete: <a href="#publication"> 6.2. Publication delete: </a> delete: <br /> delete: <a href="#non-commercial"> 6.3. Non-commercial basis delete: </a> delete: <br /> delete: <a href="#period-of-registration"> 6.4. Period of the temporary resource registration delete: </a> delete: <br /> delete: <a href="#experiment-registration"> 6.5. Registration delete: </a> delete: <br /> delete: <a href="#request"> 6.6. Making the request delete: </a> delete: <br /> delete: <a href="#7"> 7. Assignments for Anycasting TLD and Tier 0/1 ENUM Nameservers delete: <br /> delete: <a href="#references"> insert: <a href=""> insert: <br />
insert: </a>
insert: <a href="#IPv6_PI_Assignments"> 7. IPv6 Provider Independent (PI) Assignments insert: </a> insert: <a href=""> insert: <br />
insert: </a>
insert: <a href="#IPv6_PI_Assignments_LIR"> 7.1. IPv6 Provider Independent (PI) Assignments for LIRs insert: </a> insert: <a href=""> insert: <br />
insert: </a>
insert: <a class="anchor-link" title="" href="#8--transfer-of-ipv6-resources" target="_self"> 8. Transfer of IPv6 resources insert: </a> insert: <a href=""> insert: <br />
insert: </a>
insert: <a class="anchor-link" title="" href="#9--references" target="_self"> 9. References
delete: <a href="#appendixA"> 9. insert: <a class="anchor-link" title="" href="#10--appendix-a--hd-ratio" target="_self"> 10. Appendix A: HD-Ratio delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
10. 11. Appendix B: Background information delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
10.1. 11.1. Background delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
10.2. 11.2. Why a joint policy delete: </a> delete: <br /> policy? insert: </a> insert: <a href=""> insert: <br />
insert: </a>
10.3. 11.3. The size of IPv6's address space delete: <br /> insert: <a href=""> insert: <br />
insert: </a>
10.4. 11.4. Acknowledgment

delete: <a id="intro" name="intro"> delete: </a>  

insert: <a name="intro"> insert: </a> 1. Introduction

delete: <p> delete: <a id="overview" name="overview"> delete: </a> delete: </p>

insert: <a name="overview"> insert: </a> 1.1. Overview

This document describes policies for the allocation and assignment of globally unique Internet Protocol version 6 (IPv6) address space.

[RFC 4291] [ insert: <a href="#references"> RFC 4291 insert: </a> ] designates 2000::/3 to be global unicast address space that the Internet Assigned Numbers Authority (IANA) may allocate to the RIRs. In accordance with [RFC 4291], [ insert: <a class="anchor-link" href="#references"> RFC 4291 insert: </a> ], IANA allocated initial ranges of global unicast IPv6 address space from the 2000::/3 address block to the RIRs. This document concerns the initial and subsequent allocations of the 2000::/3 unicast address space, for which RIRs formulate allocation and assignment policies. All bits to the left of /64 are in scope.

delete: </p> delete: <p> This policy is subject to future review and potential revision, subject to continuing experience in the administration of IPv6.

delete: <p> delete: </p> delete: <p> delete: <a id="definitions" name="definitions"> delete: </a> delete: </p>

insert: <a name="definitions"> insert: </a> 2. Definitions

delete: <b> insert: <strong> insert: <em> [Note: some of these definitions will be replaced by definitions from other RIR documents in order to be more consistent.] delete: </b> delete: <b> delete: </b> delete: </p> delete: <p> insert: </em> insert: </strong>

The following terms and their definitions are of particular importance to the understanding of the goals, environment and policies described in this document. delete: </p> delete: <p>

Responsibility for management of IPv6 address spaces is distributed globally in accordance with the hierarchical structure shown below.

delete: <img alt="Distribution.gif" class="image-inline" height="496" name="ripe-450 chart" src="resolveuid/c60d8c3d36f6d062befd7f2f9cfc03b1" width="504" /> delete: </p> delete: <p> delete: <a id="ir" name="ir"> delete: </a>   insert: </p>

insert: <p>

insert: <img class="image-inline img-100" src="resolveuid/c60d8c3d36f6d062befd7f2f9cfc03b1" alt="Distribution.gif" name="graphics1" /> Distribution.gif insert: </p>

insert: <p>


insert: <a name="ir"> insert: </a> 2.1. Internet Registry (IR)

An Internet Registry is an organisation that is responsible for distributing IP address space to its members or customers and for registering those distributions. IRs are classified according to their primary function and territorial scope within the hierarchical structure depicted in the figure above.

delete: <p> delete: <a id="rir" name="rir"> delete: </a> delete: </p>

insert: <a name="rir"> insert: </a> 2.2. Regional Internet Registry (RIR)

Regional Internet Registries are established and authorised by respective regional communities and recognised by the IANA to serve and represent large geographical regions. The primary role of RIRs is to manage and distribute public Internet address space within their respective regions.

delete: <p> delete: <a id="nir" name="nir"> delete: </a> delete: </p>

insert: <a name="nir"> insert: </a> 2.3. National Internet Registry (NIR)

A National Internet Registry primarily allocates address space to its members or constituents, which are generally LIRs organised at a national level. NIRs exist mostly in the Asia Pacific region.

delete: <p> delete: <a id="lir" name="lir"> delete: </a> delete: </p>

insert: <a name="lir"> insert: </a> 2.4. Local Internet Registry (LIR)

A Local Internet Registry is an IR that primarily assigns address space to the users of the network services that it provides. LIRs are generally ISPs whose customers are primarily End Users and possibly other ISPs.

delete: <p> delete: <a id="allocate" name="allocate"> delete: </a> delete: </p>

insert: <a name="allocate"> insert: </a> 2.5. Allocate

To "allocate" “allocate” means to distribute address space to IRs for the purpose of subsequent distribution by them.

delete: <p> delete: <a id="assign" name="assign"> delete: </a> delete: </p>

insert: <a name="assign"> insert: </a> 2.6. Assign

To "assign" “assign” means to delegate address space to an ISP or End User for specific use within the Internet infrastructure they operate. Assignments must only be made for specific purposes documented by specific organisations and are not to be sub-assigned to other parties.

delete: <a id="utilisation" name="utilisation"> delete: </a> Providing another entity with separate addresses (not prefixes) from a subnet used on a link operated by the assignment holder is not considered a sub-assignment. This includes for example letting visitors connect to the assignment holder's network, connecting a server or appliance to an assignment holder's network and setting up point-to-point links with 3rd parties.

2.7. Utilisation

The actual usage of addresses within each assignment may be low when compared to IPv4 assignments. In IPv6, "utilisation" is only measured in terms of the bits to the left of the efficiency measurement unit (/56). In other words, "utilisation" effectively refers to the assignment of network prefixes to End Sites and not the number of addresses assigned within individual End Site assignments.

Throughout this document, the term "utilisation" refers to the assignment of network prefixes to End Sites and not the number of addresses assigned within individual subnets within those End Sites.

delete: <p> delete: <a id="hd_ratio" name="hd_ratio"> delete: </a> delete: </p>

insert: <a name="hd_ratio"> insert: </a> 2.8. HD-Ratio

The HD-Ratio is a way of measuring the efficiency of address assignment [ RFC 3194 ]. It is an adaptation of the H-Ratio originally defined in [ RFC1715 RFC 1715 ] and is expressed as follows:

 Log (number of allocated objects) ?  insert: <br /> 
HD = ---------------------------------------------- insert: <br />
Log (maximum number of allocatable objects)

where (in the case of this document) the objects are IPv6 site addresses assigned from an IPv6 prefix of a given size.

delete: <p> delete: <a id="end_site" name="end_site"> delete: </a> delete: </p>

insert: <a name="end_site"> insert: </a> 2.9. End Site

An End Site is defined as an End User (subscriber) who has a business or legal relationship (same or associated entities) with a service provider that involves:

  • delete: <p> that service provider assigning address space to the End User delete: </p>
  • delete: <p> that service provider providing transit service for the End User to other sites delete: </p>
  • delete: <p> that service provider carrying the End User's traffic delete: </p>
  • delete: <p> that service provider advertising an aggregate prefix route that contains the End User's assignment delete: </p>
delete: <p> delete: <a id="3" name="3"> delete: </a> delete: </p>

insert: <a name="3"> insert: </a> 3. Goals of IPv6 address space management

delete: <p> delete: <a id="goals" name="goals"> delete: </a> delete: </p>

insert: <a name="goals"> insert: </a> 3.1. Goals

IPv6 address space is a public resource that must be managed in a prudent manner with regards to the long-term interests of the Internet. Responsible address space management involves balancing a set of sometimes competing goals. The following are the goals relevant to IPv6 address policy.

delete: <p> delete: <a id="uniqueness" name="uniqueness"> delete: </a> delete: </p>

insert: <a name="uniqueness"> insert: </a> 3.2. Uniqueness

Every assignment and/or allocation of address space must guarantee uniqueness worldwide. This is an absolute requirement for ensuring that every public host on the Internet can be uniquely identified.

delete: <p> delete: <a id="registration" name="registration"> delete: </a> delete: </p>

insert: <a name="registration"> insert: </a> 3.3. Registration

Internet address space must be registered in a registry database accessible to appropriate members of the Internet community. This is necessary to ensure the uniqueness of each Internet address and to provide reference information for Internet troubleshooting at all levels, ranging from all RIRs and IRs to End Users.

The goal of registration should be applied within the context of reasonable privacy considerations and applicable laws.

delete: <p> delete: <a id="aggregation" name="aggregation"> delete: </a> delete: </p>

insert: <a name="aggregation"> insert: </a> 3.4. Aggregation

Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by ISPs and to limit the expansion of Internet routing tables.

This goal is particularly important in IPv6 addressing, where the size of the total address pool creates significant implications for both internal and external routing.

IPv6 address policies should seek to avoid fragmentation of address ranges.

Further, RIRs should apply practices that maximise the potential for subsequent allocations to be made contiguous with past allocations currently held. However, there can be no guarantee of contiguous allocation.

delete: <p> delete: <a id="conservation" name="conservation"> delete: </a> delete: </p>

insert: <a name="conservation"> insert: </a> 3.5. Conservation

Although IPv6 provides an extremely large pool of address space, address policies should avoid unnecessarily wasteful practices. Requests for address space should be supported by appropriate documentation and stockpiling of unused addresses should be avoided.

delete: <p> delete: <a id="fairness" name="fairness"> delete: </a> delete: </p>

insert: <a name="fairness"> insert: </a> 3.6. Fairness

All policies and practices relating to the use of public address space should apply fairly and equitably to all existing and potential members of the Internet community, regardless of their location, nationality, size, or any other factor.

delete: <p> delete: <a id="overhead" name="overhead"> delete: </a> delete: </p>

insert: <a name="overhead"> insert: </a> 3.7. Minimised overhead

It is desirable to minimise the overhead associated with obtaining address space. Overhead includes the need to go back to RIRs for additional space too frequently, the overhead associated with managing address space that grows through a number of small successive incremental expansions rather than through fewer, but larger, expansions.

delete: <p> delete: <a id="conflicts" name="conflicts"> delete: </a> delete: </p>

insert: <a name="conflict"> insert: </a> 3.8. Conflict of goals

The goals described above will often conflict with each other, or with the needs of individual IRs or End Users. All IRs evaluating requests for allocations and assignments must make judgments, seeking to balance the needs of the applicant with the needs of the Internet community as a whole.

In IPv6 address policy, the goal of aggregation is considered to be the most important.

delete: <p> delete: <a id="4" name="4"> delete: </a> delete: </p>

insert: <a name="4"> insert: </a> 4. IPv6 Policy Principles

To address the goals described in the previous section, the policies in this document discuss and follow the basic principles described below.

delete: <p> delete: <a id="property" name="property"> delete: </a> delete: </p>

insert: <a name="property"> insert: </a> 4.1. Address space not to be considered property

It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property.

The policies in this document are based upon the understanding that globally unique IPv6 unicast address space is licensed for use rather than owned. Specifically, IP addresses will be allocated and assigned on a license basis, with licenses subject to renewal on a periodic basis. The granting of a license is subject to specific conditions applied at the start or renewal of the license.

RIRs will generally renew licenses automatically, provided requesting organisations are making a "good faith" “good faith” effort at meeting the criteria under which they qualified for or were granted an allocation or assignment. However, in those cases where a requesting organisation is not using the address space as intended, or is showing bad faith in following through on the associated obligation, RIRs reserve the right to not renew the license.Note license. Note that when a license is renewed, the new license will be evaluated under and governed by the applicable IPv6 address policies in place at the time of renewal, which may differ from the policy in place at the time of the original allocation or assignment.

delete: <p> delete: <a id="routability" name="routability"> delete: </a> delete: </p>

insert: <a name="routability"> insert: </a> 4.2. Routability not guaranteed

There is no guarantee that any address allocation or assignment will be globally routable.

However, RIRs must apply procedures that reduce the possibility of fragmented address space which may lead to a loss of routability.

delete: <p> delete: <a id="minimum_allocation" name="minimum_allocation"> delete: </a> delete: </p>

insert: <a name="minimum_allocation"> insert: </a> 4.3. Minimum allocation

RIRs will apply a minimum size for IPv6 allocations to facilitate prefix-based filtering. delete: </p> delete: <p> The minimum allocation size for IPv6 address space is /32.

delete: <p> delete: <a id="ipv4_infrastructure" name="ipv4_infrastructure"> delete: </a> delete: </p>

insert: <a name="infrastructure"> insert: </a> 4.4. Consideration of IPv4 infrastructure

Where an existing IPv4 service provider requests IPv6 space for eventual transition of existing services to IPv6, the number of present IPv4 customers may be used to justify a larger request than would be justified if based solely on the IPv6 infrastructure.

delete: <p> delete: <a id="5" name="5"> delete: </a> delete: </p>

insert: <a name="5"> insert: </a> 5. Policies for Allocations and Assignments

delete: <p> delete: <a id="initial_allocation" name="initial_allocation"> delete: </a> delete: </p> delete: <h3> insert: <h4>

insert: <a name="initial_allocation"> insert: </a> 5.1. Initial allocation delete: </h3> delete: <p> delete: <a id="initial_criteria" name="initial_criteria"> delete: </a> delete: </p> insert: </h4>

insert: <a name="initial_criteria"> insert: </a> 5.1.1. Initial allocation criteria for LIRs

To qualify for an initial allocation of IPv6 address space, an organisation must: delete: </p> delete: <ul> delete: <li> delete: <p> a) be an LIR; delete: </p> delete: </li> delete: <li> delete: <p> b) advertise the allocation that they will receive as a single prefix if the prefix is to be used on the Internet; delete: </p> delete: </li> delete: <li> delete: <p> c) LIR must have a plan for making sub-allocations to other organisations and/or End Site assignments within two years.

delete: </li> delete: </ul> delete: <p> delete: <a id="initial_size" name="initial_size"> delete: </a> delete: </p>

insert: <a name="initial_size"> insert: </a> 5.1.2. Initial allocation size

Organisations LIRs that meet the initial allocation criteria are eligible to receive a minimum an initial allocation of /32. delete: </p> delete: <p> Organisations /32 up to /29 without needing to supply any additional information. insert: </p>

insert: <p>

LIRs may qualify for an initial allocation greater than /32 /29 by submitting documentation that reasonably justifies the request. If so, the allocation size will be based on the number of existing users and users, the extent of the organisation's infrastructure. delete: </p> delete: <p> delete: <a id="subsequent_allocation" name="subsequent_allocation"> delete: </a> LIR infrastructure, the hierarchical and geographical structuring of the LIR, the segmentation of infrastructure for security and the planned longevity of the allocation.

insert: <a name="subsequent_allocation"> insert: </a> 5.2. Subsequent allocation

Organisations LIRs that hold have received an existing IPv6 allocation may receive a subsequent allocation in accordance with the following policies.

delete: <p> delete: <a id="subsequent_criteria" name="subsequent_criteria"> delete: </a> delete: </p>

insert: <a name="subsequent_criteria"> insert: </a> 5.2.1. Subsequent allocation criteria

Subsequent allocation will be provided when an organisation (i.e. ISP/LIR) satisfies LIR: insert: </p>

insert: <p style="padding-left: 30px;">

a) Satisfies the evaluation threshold of past address utilisation in terms of the number of sites in units of /56 assignments. The /56. To this end, the HD-Ratio [ RFC 3194 ] is used to determine the utilisation thresholds that thresholds. insert: <br />
insert: <br />
or insert: </p>

insert: <p style="padding-left: 30px;">

b) Can justify the new needs (which can't be satisfied within the previous allocation), according to the initial allocation of additional address size criteria as described below. delete: </p> delete: <p> delete: <a id="applied_hd_ratio" name="applied_hd_ratio"> delete: </a> in section 5.1.2.

insert: <a name="applied_hd_ratio"> insert: </a> 5.2.2. Applied HD-Ratio

The HD-Ratio value of 0.94 is adopted as indicating an acceptable address utilisation for justifying the allocation of additional address space. Appendix A provides a table showing the number of assignments that are necessary to achieve an acceptable utilisation value for a given address block size.

delete: <p> delete: <a id="subsequent_size" name="subsequent_size"> delete: </a> delete: </p>

insert: <a name="subsequent_size"> insert: </a> 5.2.3. Subsequent allocation size

When an organisation has achieved an acceptable utilisation for its allocated address space, LIR meets the subsequent allocation criteria, it is immediately eligible to obtain an additional allocation that results in a doubling of the address space allocated to it. Where possible, the allocation will be made from an adjacent address block, meaning that its existing allocation is extended by one bit to the left.

If an organisation LIR needs more address space, it must provide documentation justifying its requirements for a two-year period. new requirements, as described in section 5.1.2. The allocation made will be based on this requirement. delete: </p> delete: <p> delete: <a id="lir_to_isp" name="lir_to_isp"> delete: </a> the relevant documentation.

insert: <a name="lir-to-isp"> insert: </a> 5.3. LIR-to-ISP allocation

There is no specific policy for an organisation (LIR) LIR to allocate address space to subordinate ISPs. Each LIR organisation may develop its own policy for subordinate ISPs to encourage optimum utilisation of the total address block allocated to the LIR. However, all /48 assignments to End Sites are required to be registered either by the LIR or its subordinate ISPs in such a way that the RIR/NIR can properly evaluate the HD-Ratio when a subsequent allocation becomes necessary.

delete: <p> delete: <a id="assignment" name="assignment"> delete: </a> delete: </p>

insert: <a name="assignment"> insert: </a> 5.4. Assignment

LIRs must make IPv6 assignments in accordance with the following provisions.

delete: <p> delete: <a id="assignment_size" name="assignment_size"> delete: </a> delete: </p>

insert: <a name="assignment_size"> insert: </a> 5.4.1. Assignment address space size

End Users are assigned an End Site assignment from their LIR or ISP. The size of the assignment is a local decision for the LIR or ISP to make, using a minimum value of a /64 (only one subnet is anticipated for the End Site).

delete: <p> delete: <a id="assignment_multiple" name="assignment_multiple"> delete: </a> delete: </p>

insert: <a name="assignments_shorter"> insert: </a> 5.4.2. Assignment of multiple /48s Assignments shorter than a /48 to a single End Site

When a single End Site requires an assignment shorter than a /48, it must request the assignment with documentation or materials that justify the request. Requests for multiple or additional prefixes exceeding a /48 assignment for a single End Site will be processed and reviewed (i.e., evaluation of justification) at the RIR/NIR level.

Note: There is no experience at the present time with the assignment of multiple network prefixes to the same End Site. Having the RIR review all such assignments is intended to be a temporary measure until some experience has been gained and some common policies can be developed. In addition, additional work at defining policies in this space will likely be carried out in the near future.

delete: <p> delete: <a id="assignment_infra" name="assignment_infra"> delete: </a> delete: </p>

insert: <a name="assignment_infra"> insert: </a> 5.4.3. Assignment to operator's infrastructure

An organisation (i.e. ISP/LIR) LIR may assign a network prefix per PoP as the service infrastructure of an IPv6 service operator. Each assignment to a PoP is regarded as one assignment regardless of the number of users using the PoP. A separate assignment can be obtained for the in-house operations of the operator.

delete: <p> delete: <a id="registration_assignment" name="registration_assignment"> delete: </a> delete: </p>

5.5. insert: <a name="registration2"> insert: </a> 5.5 Registration

When an organisation LIR holding an IPv6 address allocation makes IPv6 address assignments, it must register assignment information in a database, accessible these assignments in the appropriate RIR database. insert: </p>

insert: <p>

These registrations can either be made as individual assignments or by RIRs as appropriate. (Information registered by inserting an RIR/NIR may be replaced by a distributed database for registering address management information in future). Information is registered at the granularity of object with a status value of 'AGGREGATED-BY-LIR' where the assignment-size attribute contains the size of the individual assignments made to End Site assignments. Users. When more than a /48 is assigned to an organisation, the assigning organisation it must be registered in the database as a separate object with status 'ASSIGNED'. insert: </p>

insert: <p>

In case of an audit or when making a request for a subsequent allocation, the LIR must be able to present statistics showing the number of individual assignments made in all objects with a status of 'AGGREGATED-BY-LIR' in such a way the RIR is responsible for ensuring that the address space is registered in an RIR/NIR database. delete: </p> delete: <p> RIR/NIRs will use registered data able to calculate the HD-Ratio at the time of application for subsequent allocation and to check for changes in assignments over time. delete: </p> delete: <p> IRs shall maintain systems and practices that protect the security of personal and commercial information that is used in request evaluation, but which is not required for public registration. delete: </p> delete: <p> delete: <a id="reverse" name="reverse"> delete: </a> and verify the actual HD-ratio.

insert: <a name="reverse"> insert: </a> 5.6. Reverse lookup

When an RIR/NIR delegates IPv6 address space to an organisation, LIR, it also delegates the responsibility to manage the reverse lookup zone that corresponds to the allocated IPv6 address space. Each organisation LIR should properly manage its reverse lookup zone. When making an address assignment, the organisation LIR must delegate to an assignee organisation, upon request, the responsibility to manage the reverse lookup zone that corresponds to the assigned address.

delete: <p> delete: <a id="existing" name="existing"> delete: </a> delete: </p>

insert: <a name="existing"> insert: </a> 5.7. Existing Ipv6 IPv6 address space holders

Organisations LIRs that received /35 hold one or more IPv6 allocations are able to request extension of each of these allocations up to a /29 without providing further documentation. insert: </p>

insert: <p>

The RIPE NCC should allocate the new address space contiguously with the LIRs' existing allocations and avoid allocating non-contiguous space under the previous IPv6 address this policy section. insert: </p>

insert: <h2>

insert: <a name="anycasting"> insert: </a> 6. Anycasting TLD and Tier 0/1 ENUM Nameservers insert: </h2>

insert: <p>

The organisations applicable under this policy are immediately entitled to have their allocation expanded to a /32 address block without providing justification so long TLD managers, as they satisfy the criteria in Section 5.1.1. delete: </p> delete: <p> recorded in the IANA's Root Zone Database and ENUM administrators, as assigned by the ITU. The /32 address block will contain the already allocated smaller address block (one or multiple /35 address blocks in many cases) that was already reserved by the RIR for a subsequent allocation to the organisation. Requests for additional space beyond the minimum /32 size will be evaluated as discussed elsewhere in the document. delete: </p> delete: <p> delete: <a id="experiment-assignments" name="experiment-assignments"> delete: </a> delete: </p> delete: <h2> 6.0 Assignments for Internet Experiments delete: </h2> delete: <p> Organisations often require deployment tests for new Internet services and technologies. organisation may receive up to four /48 prefixes per TLD and four /48 prefixes per ENUM. These require numbering resources for the duration of the test. delete: </p> delete: <p> The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. delete: </p> delete: <p> delete: <a id="defining-experiment" name="defining-experiment"> delete: </a> delete: </p> delete: <h3> 6.1 Defining the experiment delete: </h3> delete: <p> An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC ( delete: <a href="#references"> see Sec. 4.2.1 delete: </a> ) or an "experiment proposal" detailing the resources required and the activities to be carried out. delete: </p> delete: <p> delete: <a id="publication" name="publication"> delete: </a> delete: </p> delete: <h3> 6.2 Publication delete: </h3> delete: <p> The experiment proposal prefixes must be made public (e.g. published on web site), upon registration of the resources by used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/ insert: <a href="#references"> RFC 4786 insert: </a> . insert: </p>

insert: <p>

Assignments for authoritative TLD or ENUM Tier 0/1 DNS lookup services are subject to the policies described in the RIPE NCC. Following the conclusion of the experiment the results Document entitled " insert: <a href=""> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ". insert: </p>

insert: <p>

Anycasting assignments are registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be published free of charge and free from disclosure constraints. delete: </p> delete: <p> delete: <a id="non-commercial" name="non-commercial"> delete: </a> delete: </p> delete: <h3> 6.3 Non-commercial basis delete: </h3> delete: <p> returned to the RIPE NCC if not in use for infrastructure providing authoritative TLD or ENUM Tier 0/1 DNS lookup services any longer. insert: </p>

insert: <h2>

insert: <a name="IPv6_PI_Assignments"> insert: </a> 7. IPv6 Provider Independent (PI) Assignments insert: </h2>

insert: <p>

To qualify for IPv6 PI address space, an organisation must meet the requirements of the policies described in the RIPE NCC document entitled “ insert: <a href=""> Contractual Requirements for Provider Independent Resources issued for an experiment must not be used for commercial purposes. delete: </p> delete: <p> delete: <a id="period-of-registration" name="period-of-registration"> delete: </a> delete: </p> delete: <h3> 6.4 Period of the Temporary Resource Registration delete: </h3> delete: <p> The resources will be issued on a temporary basis for a period of one year. Renewal of the resource's registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. delete: </p> delete: <p> The resources issued cannot be used for a commercial service following the conclusion of the experiment. delete: </p> delete: <p> delete: <a id="experiment-registration" name="experiment-registration"> delete: </a> delete: </p> delete: <h3> 6.5 Registration delete: </h3> Holders in the RIPE NCC Service Region insert: </a> ”. insert: </p>

The RIPE NCC will register the resources issued in the RIPE Whois Database. delete: </p> delete: <p> delete: <a id="request" name="request"> delete: </a> delete: </p> delete: <h3> 6.6 Making the request delete: </h3> delete: <p> The request must be made by a Local Internet Registry (LIR) using the appropriate request form for the resource found at: delete: </p> delete: <p> delete: <a href=""> delete: </a> delete: </p> delete: <p> delete: <a id="7" name="7"> delete: </a> delete: </p> delete: <h2> 7. Assignments for Anycasting TLD Nameservers delete: </h2> delete: <p> If the name server set of a ccTLD or a gTLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD administrator may receive a single dedicated /48 network assign the prefix for the sole purpose of anycasting name servers, as described in RFC 3258. delete: </p> delete: <p> The prefix will be assigned by the RIPE NCC directly to the TLD, End User organisations upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. TLD anycasting address insert: </p>

insert: <p>

The minimum size of the assignment is a /48. Organisations requesting a larger assignment (shorter prefix) must provide documentation justifying the need for additional subnets. insert: </p>

insert: <p>

Additional assignments are subject to the policies described in the RIPE NCC document entitled "Contractual Requirements for may also be made when the need is demonstrated and documented based on address usage, or because different routing requirements exist for additional assignments. When possible, these further assignments will be made from an adjacent address block. insert: </p>

insert: <p>

Assignments will be made from a separate 'designated block' to facilitate filtering practices. insert: </p>

insert: <p>

The PI assignment cannot be further sub-assigned to other organisations. insert: </p>

insert: <h3>

insert: <a name="IPv6_PI_Assignments_LIR"> insert: </a> 7.1 IPv6 Provider Independent Resources Holders in (PI) Assignments for LIRs insert: </h3>

insert: <p>

LIRs can qualify for an IPv6 PI assignment for parts of their own infrastructure that are not used for customer end sites. Where an LIR has an IPv6 allocation, the LIR must demonstrate the unique routing requirements for the PI assignment. insert: </p>

insert: <p>

The LIR should return the IPv6 PI assignment within a period of six months if the original criteria on which the assignment was based are no longer valid. insert: </p>

insert: <h2>

insert: <a name="8--transfer-of-ipv6-resources"> insert: </a> insert: <a name="transfer"> insert: </a> 8. Transfer of IPv6 resources insert: </h2>

insert: <p>

The transfer of Internet number resources is governed by the RIPE NCC Service Region". delete: </p> delete: <p> Anycasting assignments are registered with a status of 'ASSIGNED ANYCAST' in the Document, " insert: <a href="" data-val="" data-linktype="external"> RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer. delete: </p> delete: <p> delete: <a id="references" name="references"> delete: </a> Resource Transfer Policies insert: </a> ".

8. insert: <a name="9--references"> insert: </a> insert: <a name="references"> insert: </a> 9. References

[RFC1715] [RFC 1715] "The H Ratio for Address Assignment Efficiency", C. Huitema. November 1994, delete: <a href=""> insert: <a class="external-link" href=""> . delete: </p> delete: <p> [RFC2026] insert: </p>

insert: <p>

[RFC 2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC delete: <a href=""> insert: <a class="external-link" href=""> see Sec. 4.2.1

[RFC2462] [RFC 2462] "IPv6 Stateless Address Autoconfiguration", S. Thomson, T. Narten, 1998, delete: <a href=""> insert: <a class="external-link" href="">

[RFC 4291] "IP Version 6 Addressing Architecture", R. Hinden, S. Deering. February 2006, delete: <a href=""> insert: <a class="external-link" href="">

[RFC2928] [RFC 2928] "Initial IPv6 Sub-TLA ID Assignments", R. Hinden, S. Deering, R. Fink, T. Hain. September 2000 delete: <a href=""> insert: <a class="external-link" href="">

[RFC3194] [RFC 3194] "The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio", A. Durand, C. Huitema. November 2001, delete: <a href=""> insert: <a class="external-link" href="">

delete: <a id="appendixA" name="appendixA"> [RFC 4291] "IP Version 6 Addressing Architecture", R. Hinden, S. Deering. February 2006, insert: <a class="external-link" href=""> insert: </a> insert: </p>

insert: <p>

[RFC 4786] "Operation of Anycast Services", J. Abley, K. Lindqvist. December 2006, insert: <a class="external-link" href="">

9. insert: <a name="10--appendix-a--hd-ratio"> insert: </a> insert: <a name="appendixA"> insert: </a> 10. Appendix A: HD-Ratio

The utilisation threshold T, expressed as a number of individual /56 prefixes to be allocated from IPv6 prefix P, can be calculated as:

delete: <dl> delete: <dd> delete: <table> delete: <colgroup> delete: <col width="35"> delete: <col width="128"> delete: </colgroup> delete: <tbody> delete: <tr> delete: <td> delete: <p> delete: </p> delete: </td> delete: <td> delete: <p> ((56-P)*HD) delete: </p> delete: </td> delete: </tr> delete: <tr> delete: <td> delete: <p> insert: <p class="ListContents">

T = 2 delete: </p> delete: </td> delete: <td> delete: <p> delete: </p> delete: </td> delete: </tr> delete: </tbody> delete: </table> delete: </dd> delete: </dl> insert: <sup> ((56-P)*HD) insert: </sup> insert: </p>

Thus, the utilisation threshold for an organisation LIR requesting subsequent allocation of IPv6 address block is specified as a function of the prefix size and target HD ratio. This utilisation refers to the use of /56s as an efficiency measurement unit, and does not refer to to the the utilisation of addresses within those End Sites. It is an address allocation utilisation ratio and not an address assignment utilisation ratio.

In accordance with the recommendations of [ RFC 3194 ], this document adopts an HD-Ratio of 0.94 as the utilisation threshold for IPv6 address space allocations.

The following table provides equivalent absolute and percentage address utilisation figures for IPv6 prefixes, corresponding to an HD-Ratio of 0.94.

delete: <table class="appendix"> insert: <p>

  insert: </p>

insert: <table class="plain"> delete: <col width="73">delete: <col width="150">delete: <col width="150">delete: <col width="125">insert: <col width="15%">insert: <col width="30%">insert: <col width="30%">insert: <col width="15%">insert: <td>insert: <td>insert: <td>
delete: <p align="CENTER"> delete: <b> insert: <p align="center">

insert: <strong> Prefix delete: </b> delete: </p> delete: </td> delete: <td> delete: <p align="CENTER"> delete: <b> insert: </strong> insert: </p>

insert: </td>
insert: <p align="center">

insert: <strong> Total /56s delete: </b> delete: </p> delete: </td> delete: <td> delete: <p align="CENTER"> delete: <b> insert: </strong> insert: </p>

insert: </td>
insert: <p align="center">

insert: <strong> /56s HD 0.94 delete: </b> delete: </p> delete: </td> delete: <td> delete: <p align="CENTER"> delete: <b> insert: </strong> insert: </p>

insert: </td>
insert: <p align="center">

insert: <strong> Util % delete: </b> insert: </strong>

delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p align="RIGHT"> insert: <p align="right">


delete: <p> delete: <a id="appendixB" name="appendixB"> delete: </a> delete: </p>

10. insert: <a name="appendixB"> insert: </a> 11. Appendix B: Background information

delete: <p> delete: <a id="background" name="background"> delete: </a> delete: </p>

10.1. insert: <a name="background"> insert: </a> 11.1. Background

The impetus for revising the 1999 provisional IPv6 policy started with the APNIC meeting held in Taiwan in August 2001. Follow-on discussions were held at the October 2001 RIPE and ARIN meetings. During these meetings, the participants recognised an urgent need for more detailed, complete policies. One result of the meetings was the establishment of a single mailing list to discuss a revised policy together with a desire to develop a general policy that all RIRs could use. This document does not provide details of individual discussions that lead to policies described in this document; detailed information can be found in the individual meeting minutes at the,, and web sites.

In September 2002 at the RIPE 43 Meeting in Rhodes, Greece, the RIPE community approved the policy allowing Internet experiments to receive temporary assignments. As a result, Section 6 was added to this document in January 2003.

delete: <p> delete: <a id="why_joint_policy" name="why_joint_policy"> delete: </a> delete: </p>

10.2. insert: <a name="why_joint_policy"> insert: </a> 11.2. Why a joint policy policy?

IPv6 addresses are a public resource that must be managed with consideration to the long-term interests of the Internet community. Although regional registries adopt allocation policies according to their own internal processes, address policies should largely be uniform across registries. Having significantly varying policies in different regions is undesirable because it can lead to situations where "registry shopping" can occur as requesting organisations request addresses from the registry that has the most favorable policy for their particular desires. This can lead to the policies in one region undermining the efforts of registries in other regions with regards to prudent stewardship of the address space. In cases where regional variations from the policy are deemed necessary, the preferred approach is to raise the issue in the other regional registries in order to develop a consensus approach that all registries can support.

delete: <p> delete: <a id="size_ipv6_space" name="size_ipv6_space"> delete: </a> delete: </p>

10.3. insert: <a name="size_ipv6_space"> insert: </a> 11.3. The size of IPv6's address space

Compared to IPv4, IPv6 has a seemingly endless amount of address space. While superficially true, short-sighted and wasteful allocation policies could also result in the adoption of practices that lead to premature exhaustion of the address space.

It should be noted that the 128-bit address space is divided into three logical parts, with the usage of each component managed differently. The rightmost 64 bits, the Interface Identifier [RFC4291], [RFC 4291], will often be a globally unique IEEE identifier (e.g., mac address). Although an "inefficient" way to use the Interface Identifier field from the perspective of maximizing the number of addressable nodes, the numbering scheme was explicitly chosen to simplify Stateless Address Autoconfiguration [ RFC2462 RFC 2462 ].

The middle bits of an address indicate the subnet ID. This field may often be inefficiently utilised, but the operational benefits of a consistent width subnet field were deemed to be outweigh the drawbacks. This is a variable length field, determined by each LIR's local assignment policy.

delete: <p> delete: <a id="ack" name="ack" data-val="c60d8c3d36f6d062befd7f2f9cfc03b1" data-linktype="internal"> delete: </a> delete: </p>

10.4. insert: <a name="ack"> insert: </a> 11.4. Acknowledgment

The initial version of this document was produced by the JPNIC IPv6 policy drafting team consisting of Akihiro Inomata, Akinori Maemura, Kosuke Ito, Kuniaki Kondo, Takashi Arano, Tomohiro Fujisaki, and Toshiyuki Yamasaki. Special thanks goes out to this team, who worked over a holiday in order to produce an initial document quickly.

An editing team was then organised by representatives from each of the three RIRs (Takashi Arano, Chair of APNIC's Policy SIG, Thomas Narten, Chair of ARIN's IPv6 WG, and David Kessens, Chair of the RIPE IPv6 Working Group).

The editing team would like to acknowledge the contributions to this document of Takashi Arano, John Crain, Steve Deering, Gert Doering, Kosuke Ito, Richard Jimmerson, David Kessens, Mirjam Kuehne, Anne Lord, Jun Murai, Paul Mylotte, Thomas Narten, Ray Plzak, Dave Pratt, Stuart Prevost, Barbara Roseman, Gerard Ross, Paul Wilson, Cathy Wittbrodt and Wilfried Woeber.

The final editing of the initial version of this document was done by Thomas Narten.

IPv6 Address Allocation And and Assignment Policy