Changes to Policy for Inter-RIR Transfers of Internet Resources

Summary of Proposal

This RIPE Policy Proposal policy proposal describes how the transfer of Internet number resources will occur between resource holders in the RIPE NCC service region and those in other Regional Internet Registry (RIR) service regions.

The policy should be as similar as possible the same for transfers both outside and within the RIPE NCC service region. If another RIR has a different policy, the RIPE NCC should create an operational procedure, in cooperation with that RIR, to allow transfers to and outside the RIPE NCC from its service region. For transfers from regions where the RIR requires the receiving region to have needs-based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the transferred resources within five years.  In all cases, the registries of the different RIRs must be consistent.

With this policy, legacy resources can be transferred to or from the RIPE NCC service region, in spite of the fact that there is no specific transfer policy for them. delete: </p> delete: <p> Amendments to the existing policy, policy “ delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies"> insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies" target="_self" title=""> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ”, ” are also proposed proposed, to bring the policy in it into line with the new policy. 
 insert: <br />
insert: <br />

Policy Text

a. New Policy

Abstract:

This policy describes the transfer of Internet number resources between a resource holder an LIR of another Regional Internet Registry (RIR) and an entity or LIR within the RIPE NCC service region and a resource holder within the region of another another Regional Internet Registry (RIR). delete: </p> delete: <h4> region. insert: <b> insert: </b> insert: </p>

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

1.0 Introduction

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

This policy outlines the rules for Internet number resource transfers between the RIPE NCC and other RIR service regions.

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

1.1 Scope

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

The policy for transferring Internet number resources to or from the RIPE NCC service region will apply to be general for any resource. A transfer policy must exist for each type of Internet number resources for which there is a transfer policy resource within the RIPE NCC service region. delete: <i> delete: </i> With this policy, legacy resources can be transferred to or from the RIPE NCC service region, in spite of the fact there is no specific transfer policy for them. delete: </p> delete: <p> While the transfer is in process, during the time the internet number resources are registered in the RIPE NCC service region, then RIPE policies will apply.  delete: </p> delete: <h4> insert: <b> insert: </b> insert: </p>

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

2.0 Transferring Internet Resources to the RIPE NCC Service Region

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

The RIPE NCC shall accept all transfers of Internet number resources to its service region, provided that they comply with the policies relating to transfers within its service region.

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

When Internet number resources are transferred from RIR regions that require the receiving region to have needs-based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the transferred resources within 5 years. delete: </p> delete: <h4> another RIR, the RIPE NCC will work with its member LIR to fulfil any requirements of the sending RIR. insert: </p>

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

3.0 Transferring Internet Resources from the RIPE NCC Service Region

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

When transferring Internet number resources to another RIR, the RIPE NCC will follow the transfer policies that apply within its own service region. The RIPE NCC will also comply with the commitments imposed by the receiving RIR RIR, in order to facilitate the transfer.  transfer. insert: </p>

insert: <p>

 

b. Modification to Existing Policy Document ripe-623 existing policy document RIPE-606

[The following text will update section 5.5 in the RIPE Policy Document ripe-623, “ delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies"> insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies" target="_self" title=""> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ”, if the proposal reaches consensus.]

delete: <h3> insert: <h4>

insert: <b> b.a. insert: </b> insert: <b> Current Policy Text delete: </h3> delete: <h4> policy text insert: </b> insert: </h4>

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

insert: <b> 5.5 Transfers of Allocations insert: </b>

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

Any Local Internet Registry (LIR) LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them either by the RIPE NCC or otherwise through the Regional Internet Registry system. delete: </p> delete: <p> System. insert: </p>

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

Address space may only be re-allocated to another LIR that is also a member of the RIPE NCC. delete: </p> delete: <p> The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation. insert: </p>

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

Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis.

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

LIRs that receive a re-allocation from another LIR cannot re-allocate complete or partial blocks of the same address space to another LIR within 24 months of receiving the re-allocation.

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

[…]

delete: <h3> insert: <h4>

b.b. New Policy Text delete: </h3> delete: <h4> policy text insert: <b> insert: </b> insert: </h4>

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

insert: <b> 5.5 Transfers of Allocations insert: </b>

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

Any resource holder LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by the RIPE NCC or otherwise through the Regional Internet Registry (RIR) system. delete: </p> delete: <p> System. insert: </p>

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

Address space may only be re-allocated to another resource holder who LIR that is a member of an RIR that allows transfers. delete: </p> delete: <p> The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation. insert: </p>

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

Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis.

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

When Internet number resources are transferred to another RIR, the RIPE NCC will work with the destination RIR to allow the transfer to the receiving LIR. insert: </p>

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

When Internet number resources are transferred from RIR regions that require the receiving region to have needs-based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the another RIR, the RIPE NCC will work with its member LIR to fulfil any requirements of the sending RIR. insert: </p>

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

If resources are transferred resources within five years. delete: </p> delete: <p> While the transfer is in process, during the time the internet number resources are registered in the RIPE NCC service region, then RIPE policies as legacy resources, the RIPE NCC will apply. delete: </p> delete: <p> Resource holders apply the legacy policy when accepting these resources. insert: </p>

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

LIRs that receive a re-allocation from another resource holder LIR cannot re-allocate complete or partial blocks of the same address space to another resource holder LIR within 24 months of receiving the re-allocation.

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

[…]

Rationale

delete: <h3> insert: <h4>

a. Arguments Supporting the Proposal delete: </h3> supporting the proposal insert: <b> insert: <br />
insert: </b> insert: </h4>

• Provides a minimal framework for inter-RIR Internet number resource transfers that doesn’t set any new rules on either party or the resources involved
• Can be applied to multiple resources
insert: </ul>

insert: <ul>

• Increases the supply of IPv4 addresses available to RIPE NCC resource holders LIRs
• Maintains the integrity of the RIPE Database and ensures that the RIPE NCC is part of the approval and transfer process
insert: </ul>

insert: <ul>

• Allows resource holders in the RIPE NCC service region RIPE NCC entities to participate in a market already available to ARIN and APNIC resource holders LIRs
• Allows RIPE NCC members with excess resources to transfer to these to networks in other RIR regions

delete: <h3> insert: <h4>

b. Arguments Opposing the Proposal delete: </h3> opposing the proposal insert: </h4>

• Resource holders LIR’s with excess IPv4 addresses in the RIPE NCC service region may not wish to expand IPv4 inventories in the region delete: </li> delete: <li> It may reintroduce needs justification to the RIPE region for resources transferred from other RIRs that require needs-based, explicitly stated, policy principles. delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <hr /> delete: <p>   delete: </p> delete: <h2> delete: <a name="impact-analysis"> delete: </a> Impact Analysis delete: </h2> delete: <p> In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. This analysis is based on existing data and should be viewed as an indication only. delete: </p> delete: <h2> Executive Summary delete: </h2> delete: <ol> delete: <li> The proposed policy sets a general framework for inter-RIR resource transfers delete: </li> delete: </ol> delete: <ol> delete: <li> Executing inter-RIR transfers successfully depends on the other RIRs having compatible policies: ARIN and APNIC both see the proposal as compliant with their current policies delete: </li> delete: <li> Currently, the proposed inter-RIR transfer policy would apply to IPv4 PA allocations, IPv4 PI assignments and legacy resources delete: </li> delete: <li> Resources being transferred would remain subject to the policies of the sending RIR until the transfer is completed region.
• The RIPE NCC Registration Services Department expects a considerable increase in administrative work proposal will re-introduce operational needs justification, if the proposal is accepted delete: </li> delete: </ol> delete: <ol> delete: <li> If required by the other RIR, a receiving organisation must justify its need for the resource transfer delete: </li> delete: </ol> delete: <h2> Note: Compatibility with other RIRs delete: </h2> delete: <p> The proposed policy sets a general framework for transferring Internet number resources between the RIPE NCC service region and other Regional Internet Registry (RIR) service regions. The effectiveness and execution of the proposed policy depends not only any RIR insists on its implementation by the RIPE NCC, but also on its acceptance by the other RIRs. The RIPE NCC has therefore requested feedback from the other RIRs with inter-RIR transfer policies in place (APNIC and ARIN). delete: </p> delete: <p> Both RIRs have since confirmed that the proposed policy is compatible with their Inter-RIR transfer policies. The modified proposal meets the delete: <em> “ delete: </em> needs based” requirement that is explicitly stated in ARIN's policy. APNIC will hold a public consultation at the APNIC 39 Policy SIG, after which it will advise if there are any remaining areas of concern. delete: </p> delete: <p> The following impact analysis focuses on the interpretation and implementation details only as they relate to the RIPE NCC. It only considers situations in which the other RIR allows transfers to or from the RIPE NCC service region. Ultimately, this depends on policy development in other regions, which is an ongoing process that is difficult to predict. delete: </p> delete: <h3> A. RIPE NCC's Understanding of the Proposed Policy delete: <strong> delete: <br /> delete: </strong> delete: </h3> delete: <h4> General delete: </h4> delete: <p> The proposed policy sets a general framework for transferring Internet number resources between RIPE NCC members and resource holders in other RIR service regions. delete: </p> delete: <p> Resources may be transferred to and from the RIPE NCC service region if: delete: </p> delete: <ul> delete: <li> There is a policy allowing these resources to be transferred within the RIPE NCC service region (legacy resources can be transferred although there is no relevant transfer policy) delete: </li> delete: <li> The transfer is in accordance with the existing RIPE Policy on transfers within the RIPE NCC service region delete: </li> delete: <li> The transfer is compatible with the other RIR’s policy on inter-RIR this, in order to effect certain transfers. For transfers from RIR regions that require a needs-based policy, the recipient must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years.

delete: <h4> Applicable Types of Internet Resources delete: </h4> delete: <p> Currently, the RIPE NCC service region has a transfer policy for IPv4 Provider Aggregatable (PA) allocations and IPv4 Provider Independent (PI) assignments. If this proposal is accepted, it will be possible to transfer these resources to and from the RIPE NCC service region. IPv4 PA allocations and IPv4 PI assignments transferred to the RIPE NCC service region will be considered as registrations made directly by the RIPE NCC and existing RIPE Policies will be applied. delete: <br /> delete: <br /> Other internet resources such as IPv6 and ASNs will become available for inter-RIR transfers if the relevant transfer policies are accepted by the RIPE community. delete: </p> delete: <p> The RIPE NCC will only register resources if the network that will be using them has at least one active element located in the RIPE NCC service region. This is in line with the current practice of only allocating or assigning resources for use in our service region. delete: <br /> delete: <br /> Legacy resources that are transferred to the RIPE NCC service region, and have not had their legacy status revoked by the transferring RIR, will be treated as legacy according to RIPE Policy. If they have lost their legacy status, they will be handled in accordance with their new status. delete: </p> delete: <p> IPv4 PA allocations, IPv4 PI assignments and legacy resources transferred from the RIPE NCC service region to another RIR will receive the status defined by the policies and contracts of the receiving RIR. delete: </p> delete: <h4> Applicable Policy delete: </h4> delete: <p> The proposed policy states that "while the transfer is in process, during the time the internet number resources are registered in the RIPE NCC service region, then RIPE policies will apply." For transfers to other regions, the resources will remain registered in the RIPE Registry until the transfer is completed. For transfers to the RIPE NCC service region, the resources will only be registered in the RIPE Registry when the transfer is completed. delete: </p> delete: <p class="p2"> It is the RIPE NCC’s understanding that resources being transferred are subject to the policies of an RIR as long their are registered in its registry.  delete: </p> delete: <p class="p2"> For transfers from the RIPE NCC service region to another RIR, “The RIPE NCC will also comply with the commitments imposed by the receiving RIR in order to facilitate the transfer.” It is the RIPE NCC’s understanding that the other RIR might need the RIPE NCC’s support to ensure their policies can be followed to complete the transfer. For example, the other RIR might request documentation from the resource holder in the RIPE NCC service region.  delete: </p> delete: <p class="p2"> In addition, for transfers to the RIPE NCC service region from RIRs that require needs-based policies, recipients must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years. delete: </p> delete: <p class="p2"> The proposed policy can only apply to RIRs with compatible inter-RIR transfer policies. delete: </p> delete: <p class="p2"> The RIPE NCC cannot guarantee that the other RIR will agree to a resource transfer, even if it is approved by the RIPE NCC. The requirement to ensure consistency between RIRs means that both registries have to be in agreement to execute a transfer. The RIPE NCC can not, on its own, ensure that the policy requirements of the other RIR are met. Failure to comply with any RIR policy in such cases could lead to a difference of opinion on whether a transfer is acceptable between the transferring and receiving RIRs. delete: </p> delete: <h4> Transfer Period delete: </h4> delete: <p> It is the RIPE NCC’s understanding that a resource transfer can be on a permanent or non-permanent basis. Temporary transfers will be moved back from the RIPE Registry to the transferring RIR once the transfer period has ended or vice versa. delete: <br /> delete: <strong> delete: </strong> delete: </p> delete: <h4> Deregistration delete: </h4> delete: <p> Resources that are permanently transferred to the RIPE NCC service region, and are later deregistered (for any reason), will be added to the RIPE NCC’s pool of available resources. delete: </p> delete: <h4> Documentation and Holding Period delete: </h4> delete: <p> The RIPE NCC will publish a list of transferred resources between RIRs if this is required in the applicable transfer policy for the RIPE NCC service region. Similarly, if the applicable transfer policy contains a holding period for received resources, then this will also apply to resources received from other RIR service regions. delete: </p> delete: <h4> Arbitration delete: </h4> delete: <p> The potential for disagreement between RIRs on policy compliance could require cross-registry arbitration to resolve such conflicts (for example, if a member of the RIPE NCC disagrees with the decision of another RIR). The RIPE NCC Conflict Arbitration procedure does not include appeals of this nature and can only settle disputes between members and the RIPE NCC, between members, and between legacy Internet resource holders and the RIPE NCC. delete: </p> delete: <h3> B. Impact of Policy on Registry and Addressing System delete: </h3> delete: <h4> Address/Internet Number Resource Consumption: delete: </h4> delete: <p> After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented. delete: </p> delete: <h4> Fragmentation/Aggregation: delete: </h4> delete: <p> If it is accepted, the proposal would likely result in increased deaggregation, as existing IP ranges could be split and transferred in parts. The RIPE NCC has no historical data to estimate the likely amount of deaggregation.  delete: </p> delete: <h3> C. Impact of Policy on RIPE NCC Operations/Services delete: <br /> delete: <strong> delete: </strong> delete: </h3> delete: <h3> Registration Services:  delete: </h3> delete: <h4> Amount of Requests delete: </h4> delete: <p> In the RIPE NCC service region, there are more than 23,000 PA allocations, more than 22,000 PI assignments, and more than 5,000 legacy resources that can potentially be transferred (either in their entirety, or further broken up into smaller blocks). This is in addition to all of the eligible prefixes registered in other RIR service regions that could be transferred. delete: </p> delete: <p> The RIPE NCC has seen a considerable increase in transfer activity since 2012. In 2014, more than 900 PA allocation transfers were completed within the RIPE NCC service region. A similar number of inter-RIR transfers will likely result if the proposal is accepted, though the RIPE NCC is unable to provide an actual estimate. delete: </p> delete: <h4> Inter-RIR Coordination and Evaluation of Requests  delete: </h4> delete: <p class="p1"> If this proposal reaches consensus and is deemed compatible by other RIRs, the RIPE NCC will process requests to transfer resources to or from its service region:   delete: </p> delete: <ul> delete: <li> For transfers from RIR service regions that require needs-based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the transferred resources within five years. The RIPE NCC will evaluate the provided addressing plan and will only approve the transfer if this requirement is met. delete: </li> delete: <li> For transfers to other RIR service regions, the RIPE NCC will apply the transfer policies of its region along with “the commitments imposed by the receiving RIR”. This means that the RIPE NCC might need to support the other RIR to ensure that the transfer is compliant with their policies. For example, if the other RIR requires documentation from a resource holder in the RIPE NCC service region, the RIPE NCC would support this process. delete: </li> delete: </ul> delete: <p class="p1"> In this context, it is important to highlight that maintaining the inter-RIR transfer framework is expected to require considerably more work than transfers within the RIPE NCC service region. Inter-RIR coordination is necessary to ensure that the transfer is in accordance with the related policies in both regions. The update in the RIR registries must be synchronised to ensure correct registration. As RIRs operate in different time zones the processing of inter-RIR transfers is expected to take longer than intra-RIR transfers. delete: </p> delete: <h4> Billing/Finance Department: delete: </h4> delete: <p> After analysing the data that is currently available, the RIPE NCC does not anticipate any significant impact if this proposal is implemented. delete: <b> delete: <br /> delete: <strong> delete: </strong> delete: </b> delete: </p> delete: <h4> RIPE Database and DNS: delete: </h4> delete: <p> The RIPE Database will reflect inter-RIR transfers. delete: <br /> For prefixes transferred to the RIPE NCC service region, resource holders will be able to set up reverse DNS in the RIPE Database based on the existing inter-RIR DNS information exchange. delete: <b> delete: <br /> delete: <strong> delete: </strong> delete: </b> delete: </p> delete: <h4> Software Engineering: delete: </h4> delete: <p class=" "> Software development will be needed to process inter-RIR transfers. Given the information that is currently available, a medium impact is expected, with between two and three months needed to develop the necessary software tools. delete: </p> delete: <h3> D. Legal Impact of Policy delete: </h3> delete: <h4> Contractual Relationship delete: </h4> delete: <p> The RIPE NCC can only evaluate a transfer request for resources that are subject to a contract, except in the case of legacy resources. However, while the RIPE NCC can evaluate legacy transfer requests without a contract, the other RIR may have concrete contractual requirements that cannot be avoided. The RIPE NCC will also perform due diligence checks to ensure that the offering part is the legitimate holder of any resources being transferred. delete: </p> delete: <h4> Transfer Procedure and Due Diligence delete: </h4> delete: <p> A procedural document will need to be drafted that outlines the transfer procedure and due diligence checks of all the RIRs involved in inter-RIR transfers. delete: </p> delete: <h4> Shift of Responsibility – Updates on Contracts delete: </h4> delete: <p> Until the transfer is completed, the transferring party is responsible for complying with the transferring RIR’s policies and any relevant contractual and legal obligations with regards to the resources to be transferred. delete: <br /> After the transfer is completed, the transferring party may need to update its contract so that the transferred resources are no longer subject to it anymore. The receiving party is responsible for complying with the receiving RIR’s policies. The existing contractual obligations of the receiving party will have to extend to the transferred resources. A new contract may therefore need to be signed or the existing contract may need to be updated in order to include the transferred resources (e.g. if legacy resources are transferred to or from the RIPE NCC service region, the existing contract with the RIPE NCC or a RIPE NCC member will need to be updated accordingly). The receiving party will also be responsible for any other legal obligations regarding the transferred resources. delete: </p> delete: <h4> Responsibility for the Evaluation delete: </h4> delete: <p> The requirements for a transfer to be approved by the RIPE NCC may be different from those of other RIRs. According to the proposal: delete: </p> delete: <ul> delete: <li> For transfers to the RIPE NCC service region, the RIPE NCC will evaluate requests in the same manner it would evaluate a request for a transfer within its service region. If the request comes from an RIR service region that requires a needs-based policy, the RIPE NCC will evaluate “a plan for the use of at least 50% of the transferred resources within 5 years” that is provided by the recipient. delete: </li> delete: <li> For transfers from the RIPE NCC service region, the RIPE NCC will evaluate the request in the same manner it would evaluate a request for transfer within its service region and “will comply with the commitments imposed by the receiving RIR” in order to facilitate the transfer. delete: </li> delete: </ul> delete: <p> When the other RIR has additional requirements, the RIPE NCC will work with the resource holder to comply with these. This will require the RIPE NCC to share confidential information about the resource holder with the other RIR, though it will only do so if it has the resource holder’s approval. The RIPE NCC will also need to draft and sign an NDA with the other RIR regarding the third party information shared.   delete: </p> delete: <h4> E. Implementation delete: </h4> delete: <p> With the information currently available, it is expected that implementation of the proposal would have a medium impact in terms of the software development needed to facilitate inter-RIR transfers in internal RIPE NCC systems. The RIPE Registry will document transfers and received resources. New processes and documentation will also need to be created in coordination with other RIRs. delete: </p> delete: <p> It is important to note that the implementation will only establish the framework for the RIPE NCC to process inter-RIR transfers. The actual execution will be dependent on matching policies and procedures between the RIRs involved. delete: </p> delete: <p>   delete: </p> delete: <p>   delete: </p>

Draft documents relating to "Policy for Inter-RIR Transfers of Internet Resources":

1. delete: <a class="internal-link" href="resolveuid/93ca40eb82d54fb2ac47d93567809128" target="_self" title="" data-val="93ca40eb82d54fb2ac47d93567809128" data-linktype="internal"> delete: <span class="internal-link"> delete: <span class="internal-link"> delete: <span class="internal-link"> insert: <a class="internal-link" href="resolveuid/f659ab4db90d4c03885a68970895aff4" target="_self" title="2014-05:Draft: Policy for Inter-RIR Transfers of Internet Resources - New Policy Text" data-val="f659ab4db90d4c03885a68970895aff4" data-linktype="internal"> New policy delete: </span> delete: </span> delete: </span>
2. delete: <a class="internal-link" href="resolveuid/1e78dfb4336040a38b57af1d94b08040" target="_self" title="" data-val="1e78dfb4336040a38b57af1d94b08040" data-linktype="internal"> delete: <span class="internal-link"> delete: <span class="internal-link"> insert: <a class="internal-link" href="resolveuid/710d99d9022742f4b8893b132189a7ba" target="_self" title="" data-val="710d99d9022742f4b8893b132189a7ba" data-linktype="internal"> Amendments to existing policy document ripe-623 delete: </span> delete: </span> ripe-606

insert: <p>

  insert: </p>