You are here: Home > Participate > Policy Development > Policy Proposals > RIPE Resource Transfer Policies

Changes to RIPE Resource Transfer Policies

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted

Summary of Proposal

The goal of this proposal is to create a single document with all relevant information regarding the transfer of Internet number resources. delete: </p> delete: <p> Replacing resources.  insert: </p>

insert: <p>

Removing all transfer-related policy text from the allocation and assignment policies and keeping this in one document will make it easier for people to find the information they are looking for. This will also make it easier to maintain the various policies in future. All of the allocation and assignment policies will include a reference to this document.

The following policy documents currently have text relating to transfers:

insert: <span> The final transfer document will aim to generalise the policy text as much as possible. It will explain specific restrictions or exceptions relating to the various types of Internet number resources as required required. insert: </span>

The proposal extends the covers changes of holdership via transfers as well as mergers and acquisitions. Both categories will have the same 24-month transfer restriction to resources that have been transferred due to changes to an organisation’s business structure (such as a merger or acquisition). It is important to note that this restriction only prevents policy transfers – resources subject to this restriction may still be transferred due to further mergers or acquisitions within the 24-month holding period. delete: </p> delete: <p> The proposal also requires adds mergers and acquisitions to the statistics that the RIPE NCC publish information about transfers due to changes to an organisation’s business structure (such as a merger or acquisition) in the same way that it already does with general transfers. publishes.  

Policy Text

delete: <em> insert: <i> [The following policy will replace: delete: </em> delete: </p> delete: <p> delete: <em> insert: </i> insert: </p>

insert: <p>

insert: <i> - delete: </em> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-649#55" data-val="https://www.ripe.net/publications/docs/ripe-649#55" data-linktype="external"> delete: <em> insert: </i> insert: <a href="../../../../publications/docs/ripe-649#55"> insert: <i> Sections 5.5 delete: </em> delete: </a> delete: <em> insert: </i> insert: </a> insert: <i> and delete: </em> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-649#64" data-val="https://www.ripe.net/publications/docs/ripe-649#64" data-linktype="external"> delete: <em> insert: </i> insert: <a href="../../../../publications/docs/ripe-649#64"> insert: <i> 6.4 delete: </em> delete: </a> delete: <em> insert: </i> insert: </a> insert: <i> in ripe-649, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
delete: </em> delete: <em> insert: </i> insert: <i> - delete: </em> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-638#Transferring" data-val="https://www.ripe.net/publications/docs/ripe-638#Transferring" data-linktype="external"> delete: <em> insert: </i> insert: <a href="../../../../publications/docs/ripe-638#Transferring"> insert: <i> Section 4.0 delete: </em> delete: </a> delete: <em> insert: </i> insert: </a> insert: <i> in ripe-638, "Autonomous System (AS) Number Assignment Policies"
delete: </em> delete: <em> insert: </i> insert: <i> - delete: </em> delete: <a class="internal-link" title="" href="resolveuid/1a389ad7cec44e179a5532c3fdff46b9#8--transfer-of-ipv6-resources" target="_self" data-val="1a389ad7cec44e179a5532c3fdff46b9#8--transfer-of-ipv6-resources" data-linktype="internal"> delete: <em> insert: </i> insert: <a href="../../../../publications/docs/ripe-650#8--transfer-of-ipv6-resources"> insert: <i> Section 8 delete: </em> delete: </a> delete: <em> insert: </i> insert: </a> insert: <i> . in ripe-655, ripe-650, "IPv6 Address Allocation and Assignment Policy" delete: </em> delete: </p> delete: <p> delete: <em> The text in these sections will be replaced by a reference to the new RIPE Document, "RIPE Resource Transfer Policies" delete: </em> delete: </p> delete: <p> delete: <em> insert: <br />
insert: </i> insert: <i> - delete: </em> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-644" data-val="https://www.ripe.net/publications/docs/ripe-644" data-linktype="external"> delete: <em> insert: </i> insert: <a href="./resolveuid/f8180e3e9ca64c73aa5bbc7623457264" data-val="f8180e3e9ca64c73aa5bbc7623457264" data-linktype="internal"> insert: <i> ripe-644 delete: </em> delete: </a> delete: <em> insert: </i> insert: </a> insert: <i> , "Policy for Inter-RIR Transfers of Internet Resources" delete: </em> delete: </p> delete: <p> delete: <em> This insert: </i> insert: </p>

insert: <p>

insert: <i> Accordingly, these sections or policy document documents will be deleted.] delete: </em> insert: </i>

Content

delete: <a class="anchor-link" title="" href="#scope" target="_self"> insert: <span> insert: <a class="anchor-link" href="#scope" target="_self" title=""> 1.0 Scope
delete: <a class="anchor-link" title="" href="#transferswithinripenccserviceregion" target="_self"> insert: <a class="anchor-link" href="#transferswithinripenccserviceregion" target="_self" title=""> 2.0 Transfers within the RIPE NCC Service Region
delete: <a class="anchor-link" title="" href="#transferrequirements" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#transferrequirements" target="_self" title=""> 2.1 Transfer Requirements
delete: <a class="anchor-link" title="" href="#transferrestrictions" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#transferrestrictions" target="_self" title=""> 2.2 Transfer Restrictions
delete: <a class="anchor-link" title="" href="#interrirtransfers" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#interrirtransfers" target="_self" title=""> 3.0 Inter-RIR Transfers
delete: <a class="anchor-link" title="" href="#general" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#general" target="_self" title=""> 3.1 General
delete: <a class="anchor-link" title="" href="#transferringtotheripenccregion" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#transferringtotheripenccregion" target="_self" title=""> 3.2 Transferring Internet Number Resources to the RIPE NCC Service Region
delete: <a class="anchor-link" title="" href="#transferringfromtheripenccregion" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#transferringfromtheripenccregion" target="_self" title=""> 3.3 Transferring Internet Number Resources from the RIPE NCC Service Region
delete: <a class="anchor-link" title="" href="#transferstats" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#transferstats" target="_self" title=""> 4.0 Transfer Statistics
delete: <a class="anchor-link" title="" href="#attribution" target="_self"> insert: </span> insert: <span> insert: <a class="anchor-link" href="#attribution" target="_self" title=""> 5.0 Attribution delete: </p> delete: <p>   delete: </p> delete: <h3> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <br />
insert: </span> insert: </p>

insert: <h4>

1.0 Scope delete: </h3> insert: </h4>

This policy outlines:

  • insert: <span> The rules for Internet number resource transfers within the RIPE NCC service services region delete: </li> delete: <li> insert: </span> insert: </li>
    • insert: <li>
  • insert: <span> The rules for Internet number resource transfers (including legacy resources) to and from the RIPE NCC service region (often referred to as inter-RIR transfers) insert: </span>
delete: <h3> insert: <h4>


2.0 Transfers within the RIPE NCC Service Region delete: </h3> insert: </h4>

Any legitimate resource holder is allowed to transfer complete or partial blocks of address space or number resources (IPv4, IPv6 and AS Numbers) that were previously allocated or assigned to them by the RIPE NCC or otherwise through the Regional Internet Registry (RIR) system. Resources are excluded from transfers when RIPE Policies mandate their return to the RIPE NCC. delete: </p> delete: <p> Allocated resources   insert: </p>

insert: <p>

insert: <span> Resources may only be transferred to another RIPE NCC member. Provider independent resources may be transferred to: delete: </p> delete: <ul> delete: <li> A RIPE NCC member; or delete: </li> delete: <li> An an entity that has a contractual contractual  insert: </span> insert: <span> relationship with the RIPE NCC or with a RIPE NCC member in accordance with the RIPE Policy, “ delete: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/contract-req" data-val="https://www.ripe.net/publications/docs/contract-req" data-linktype="external"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ”. delete: </li> delete: </ul> delete: <p>   member. insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <br />
insert: </span>

2.1 Transfer Requirements

Transfers must be reflected in the RIPE Database. Transfers can be on a permanent or non-permanent basis.

The original resource holder remains responsible for an Internet number resource until the transfer to the receiving party is completed. In the case of a temporary transfer, the original resource holder re-assumes responsibility when the resource is returned. The current resource holder must ensure that all relevant policies are applied.

Transferred resources are no different from allocations or assignments made directly by the RIPE NCC and so must be used by the receiving party in accordance with the respective policy documents.

To complete the transfer, the RIPE NCC will update the registration records of the Internet number resource to reflect the transfer. delete: </p> delete: <p>   change in holdership. insert: </p>

insert: <p>

 

2.2 Transfer Restrictions

Scarce resources, which are understood as those resources that are allocated or assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs), cannot be transferred for by the resource holder within 24 months from the date the resource was received by the resource holder. This restriction also applies if the resource was received due to a change in the organisation’s business (such as a merger or acquisition). delete: </p> delete: <p> This restriction does not prevent the resources from being transferred due to further mergers or acquisitions within the 24-month period. delete: </p> delete: <p>   delete: </p> delete: <h3> received. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

3.0 Inter-RIR Transfers delete: </h3> insert: </h4>


3.1 General

insert: <span> Any type of Internet number resource can be transferred to or from the RIPE NCC service region. This includes legacy resources, in spite of the fact there are no specific rules for legacy resource transfers within the RIPE NCC service region. insert: </span>

Resources are excluded from transfers when RIPE Policies mandate their return to the RIPE NCC.

RIPE Policies will apply while the transfer is in process, for as long as the Internet number resources are registered within the RIPE NCC service region.

   

3.2 Transferring Internet Number Resources to the RIPE NCC Service Region

The RIPE NCC shall accept all transfers of Internet number resources to its service region, provided they comply with the policies relating to transfers within its service region. insert: <span>   insert: </span>

For transfers from RIR service 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 five years.

   

3.3 Transferring Internet Number Resources from the RIPE NCC Service Region

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 any commitments imposed by the receiving RIR in order to facilitate the transfer.

  delete: </p> delete: <h3>   insert: </p>

insert: <h4>

4.0 Transfer Statistics delete: </h3> insert: </h4>

The RIPE NCC will publish a list of all transfers. holdership changes. This publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses.

This list will contain information about approved changes. The following information will be published:

  • The name of the offering party
  • The resource originally held by the offering party
  • The name(s) of the receiving party or parties
  • Each subdivided prefix (each partial block derived from that original block) or resource received
  • The date each resource was transferred changed holder in the registry.
  • Whether it was a transfer according to this policy or a transfer due to changes to an organisation's business structure (such as a merger or acquisition) or merger/acquisition
 
delete: <h3> insert: <h4>

5.0 Attribution delete: </h3> insert: </h4>

This document is developed by the RIPE community.

The following people actively contributed by making proposals through the RIPE Policy Development Process:

Erik Bais

insert: <span> Rationale insert: </span>

a. Arguments supporting the proposal

  • The goal of this proposal is to reduce the amount of documents where various parts of a transfer policy can be found, based on the type of number resource. resource.  When the initial transfer policies were written, it was already intended to move the new policy text to a dedicated transfer policy document.
  • To improve transparency, the transfer statistics now include insight into all transfers, including mergers and acquisitions. holdership changes under the policy.

b. Arguments opposing the proposal

  • The document implements a couple of slight wording changes into the documents to make the writing more generic.
  • The document proposes to apply include the transfer restrictions to mergers and acquisitions. This is done to make the policy more in line with the intention of the transfer policy restrictions when proposed. proposed. 
delete: <hr /> delete: <p> delete: <a name="impact-analysis"> delete: </a> delete: </p> delete: <h2> Impact Analysis delete: </h2> delete: <p> Note: In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. The projections presented in this analysis are based on existing data and should be viewed only as an indication of the possible impact that the policy might have if the proposal is accepted and implemented. delete: </p> delete: <h3> A. RIPE NCC's Understanding of the Proposed Policy delete: </h3> delete: <p> It is the RIPE NCC’s understanding that this proposal will replace all transfer-related text in the various resource policy documents (for IPv4 Provider Aggregatable (PA) and Provider Independent (PI), IPv6 PA and PI, Autonomous System (AS) Numbers) and combine this into one document. The text of the transfer sections in the various resource policy documents will be replaced with references to the new policy document “RIPE Resource Transfer Policies”. delete: </p> delete: <p> The document “Policy for Inter-RIR Transfers of Internet Resources” will be replaced completely by the new policy document. delete: </p> delete: <p> Most of the requirements for transfers will remain the same as they are in the current transfer policies, as will the related delete: <a class="internal-link" title="" href="resolveuid/ebbf338ea6044af6a9c815727d8eef0d" target="_self" data-val="ebbf338ea6044af6a9c815727d8eef0d" data-linktype="internal"> procedures delete: </a> . delete: </p> delete: <p> delete: <span lang="EN-GB"> This analysis will focus on the changes that this proposal introduces. delete: </span> delete: </p> delete: <h4> Entities That Can Receive a Transfer delete: </h4> delete: <p> The proposed policy says: delete: <br /> “Allocated resources may only be transferred to another RIPE NCC member. Provider Independent resources may be transferred to: delete: </p> delete: <ul> delete: <li> A RIPE NCC member; or delete: </li> delete: <li> An entity that has a contractual relationship with a RIPE NCC member delete: </li> delete: </ul> delete: <p> in accordance with the RIPE Policy, “ delete: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/contract-req" data-val="https://www.ripe.net/publications/docs/contract-req" data-linktype="external"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ”. delete: </p> delete: <p> It is the RIPE NCC’s understanding that allocations of IPv4 and IPv6 can only be transferred to organisations that are members of the RIPE NCC (i.e. have a Local Internet Registry (LIR) account). Independent resources (such as IPv4 PI, IPv6 PI and AS Numbers) can be transferred to organisations that are members of the RIPE NCC or have a contractual relationship with a sponsoring LIR as per RIPE Policy, “ delete: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/contract-req" data-val="https://www.ripe.net/publications/docs/contract-req" data-linktype="external"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ”. delete: </p> delete: <h4> Resources Excluded from Transfers delete: </h4> delete: <p> delete: <span lang="EN-GB"> The proposed policy change excludes resources that are required to be returned to the RIPE NCC by the policies governing their issue. Currently this would apply to the following resources: delete: </span> delete: </p> delete: <ul> delete: <li> IPv4 Internet Exchange Point (IXP) - "This space will be used to run an IXP peering LAN; other uses are forbidden. [...] New IXPs will be assigned a /24. Should they require a larger assignment, they must return their current assignment (or existing PI used as an IXP peering LAN) ..." delete: <br /> delete: <a class="internal-link" title="" href="resolveuid/b97600388f9d485e87f0c532030f31b3#61" target="_self" data-val="b97600388f9d485e87f0c532030f31b3#61" data-linktype="internal"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region - Section 6.1 delete: </a> delete: <br /> While the policy specifies the return requirement for the situation where an IXP needs a larger assignment, it is the RIPE NCC's established understanding that this requirement also applies to situations where the IXP is not in need of the assignment anymore. delete: </li> delete: <li> IPv6 Anycast - "Anycasting assignments are registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for infrastructure providing authoritative TLD or ENUM Tier 0/1 DNS lookup services any longer." delete: <br /> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-655#anycasting" data-val="https://www.ripe.net/publications/docs/ripe-655#anycasting" data-linktype="external"> IPv6 Address Allocation and Assignment Policy - Section 6 delete: </a> delete: </li> delete: <li> IPv6 for Internet Root Servers - "If a root server stops operating within the RIPE region, the address space will be returned to the RIPE NCC and marked as "reserved" for a suitably long period of time."  delete: <br /> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-636" data-val="https://www.ripe.net/publications/docs/ripe-636" data-linktype="external"> IPv6 Addresses for Internet Root Servers in the RIPE Region delete: </a> delete: </li> delete: <li> Temporary Assignments - "The RIPE NCC may assign number resources to End Users on a temporary deployment basis for a specific time-limited purpose. [...] The number resources will be automatically de-registered and returned to the appropriate reservation pool at the end of the approved assignment period." delete: <br /> delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-587#procedures" data-val="https://www.ripe.net/publications/docs/ripe-587#procedures" data-linktype="external"> Temporary Internet Number Assignment Policies - Section 2.1 delete: </a> delete: </li> delete: </ul> delete: <p> N.B. IPv6 IXP assignments are not excluded from transfer because the associated policy does not specify a return requirement. The receiving party would, however, need to meet the policy requirements defined in the IPv6 Address Space Policy For Internet Exchange Points Points ( delete: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-451" data-val="https://www.ripe.net/publications/docs/ripe-451" data-linktype="external"> https://www.ripe.net/publications/docs/ripe-451 delete: </a> ) before the transfer could be completed. If this is not the intention of the community it may be necessary to make some policy development to ripe-451.   delete: </p> delete: <p> If a policy change removes or adds a return requirement for an Internet resource, the list of resources excluded from transfers will be adjusted accordingly. delete: <br /> The RIPE community is currently discussing the policy proposal 2016-03, " delete: <a href="../../../../../resolveuid/7f5aaf4e3996415b8b01ff377a6827e3" data-val="7f5aaf4e3996415b8b01ff377a6827e3" data-linktype="internal"> Locking Down the Final /8 Policy delete: </a> ". If this proposal reaches consensus in the current version, all IPv4 allocations provided by the RIPE NCC after 14 September 2012 would be excluded from transfers. delete: </p> delete: <h4> Holding Period for Scarce Resources delete: </h4> delete: <p> The proposed policy in its latest version says: delete: <br /> “Scarce resources, which are understood as those resources that are allocated or assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs), cannot be transferred for 24 months from the date the resource was received by the resource holder. This restriction also applies if the resource was received due to a change in the organisation’s business (such as a merger or acquisition). This restriction does not prevent the resources from changing holdership due to further merger or acquisition within the 24-month period.” delete: </p> delete: <p> delete: <span lang="EN-GB"> The RIPE NCC understands “scarce resources” to include IPv4 PA, IPv4 PI and 16-bit AS Numbers. If the community declares other resources to be scarce, the list of resources for which the holding period will apply will be adjusted accordingly.   delete: </span> delete: </p> delete: <p> The proposal introduces a 24-month holding period from the moment an Internet resource has been registered by the RIPE NCC to a resource holder. Within this period, it will not be possible to transfer the resource under RIPE Policies. delete: </p> delete: <p> Company mergers and network acquisitions that include Internet resources are possible at any time as they are not regulated by RIPE Policies. The proposed policy text underlines this. delete: </p> delete: <p> The holding period of 24 months will start from the moment the RIPE NCC registers the resource to the holder in the RIPE Database. This applies whether the resource was received: delete: <br /> - Directly from the RIPE NCC delete: <br /> - Via a policy transfer delete: <br /> - Through an organisation merger, acquisition, bankruptcy or liquidation delete: </p> delete: <p> Holdership changes during a temporary resource transfer will not re-start the 24-month holding period for the original resource holder. While in a strict sense the return of the resource to the original holder could be seen as “receiving back”, the Address Policy Working Group decided during RIPE 69 that the 24-month holding period should not apply to such delete: <a href="resolveuid/0ffcedc9e2e249b8b0073d22bd43e24b" data-val="0ffcedc9e2e249b8b0073d22bd43e24b" data-linktype="internal"> temporary holdership changes delete: </a> .  delete: <br /> The temporary resource holder will not be able to transfer the resource further during the period in which the resource is registered to them. delete: </p> delete: <p> Any other change to an Internet resource that is not related to a holdership change (for example, a company name change or converting address space to another resource type) has no influence on the holding period. delete: </p> delete: <h4> Publishing Transfer Statistics delete: </h4> delete: <p> The proposal extends the publication of transfer-related information to include transfers completed as a result of mergers and acquisitions. This information would only be published for mergers and acquisitions completed after the implementation of the policy, not for those approved previously. delete: </p> delete: <p> The proposed policy change excludes the publication of aggregate statistics for non-approved holdership changes. Since the adoption of the policy proposal delete: <a class="internal-link" title="" href="resolveuid/8f0a965d-1993-4c26-b707-578d22162b38" target="_self" data-val="8f0a965d-1993-4c26-b707-578d22162b38" data-linktype="internal"> 2013-03 delete: </a> , delete: <span lang="EN-GB"> “Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text”, the RIPE NCC no longer performs needs-based evaluation of transfers. Publication of statistics for non-approved IPv4 transfer requests is therefore no longer relevant.   delete: </span> delete: </p> delete: <p> delete: <span lang="EN-GB"> There is an important distinction between “non-approved” requests and “invalid/incomplete” requests. If a request is received which cannot be completed due to a policy restriction (for example IPv6 allocations smaller than the minimum /32 or IPv4 allocations which have already changed holdership within the previous 24 months), it is considered to be invalid. If a request is received with inadequate supporting documentation (for example missing the signed transfer agreement), it is considered to be incomplete. In both of these scenarios, the RIPE NCC is unable to complete the evaluation of the request and therefore it cannot be considered to be either approved or non-approved.   delete: </span> delete: </p> delete: <h3> B. Impact of Policy on Registry and Addressing System delete: </h3> delete: <p> delete: <strong> Address/Internet Number Resource Consumption: delete: <br /> delete: </strong> delete: <span lang="EN-GB"> 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: </span> delete: </p> delete: <p> delete: <strong> Fragmentation/Aggregation: delete: </strong> delete: <br /> delete: <span lang="EN-GB"> 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: </span> delete: </p> delete: <h3> C. Impact of Policy on RIPE NCC Operations/Services delete: </h3> delete: <p> delete: <strong> Software Engineering: delete: </strong> delete: <br /> Software development will be needed to: delete: </p> delete: <ul> delete: <li> Update the transfer statistics to differentiate between policy transfers and mergers/acquisitions delete: </li> delete: <li> Prevent transfer of scarce resources for 24 months after any ownership change delete: </li> delete: </ul> delete: <p> delete: <strong> Registration Services: delete: </strong> delete: <br /> Some manual intervention will be required from Registration Services to support Software Engineering with identifying and excluding LIR account consolidations from the existing list of mergers/acquisitions. delete: </p> delete: <p> delete: <strong> External Relations: delete: </strong> delete: <br /> This proposal continues a trend towards defining policies according to the action being performed (in this case the transfer of resources between holders), rather than according to the type of resource (such as a policy for allocation and assignment of IPv6 address space). The community has identified this approach as producing more straightforward policy, and the RIPE NCC agrees with this assessment. In the short term it is expected that we need to increase outreach to raise awareness of these changes within the broader Internet community. delete: </p> delete: <p> delete: <strong> Billing/Finance Department: delete: <br /> delete: </strong> delete: <span lang="EN-GB"> 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: </span> delete: </p> delete: <p> delete: <strong> RIPE Database: delete: </strong> delete: <br /> 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: <h3> D. Legal Impact of Policy delete: </h3> delete: <p> delete: <span class="internal-link"> If this proposal becomes policy, the RIPE NCC may need to update the relevant procedural documents, including the RIPE NCC procedural document “ delete: </span> delete: <a class="internal-link" title="" href="resolveuid/e47b56840d8e4e4091decb3751de9179" target="_self" data-val="e47b56840d8e4e4091decb3751de9179" data-linktype="internal"> Transfer of Internet Number Resources and Change of a Member’s Official Legal Name delete: </a> ”. delete: </p> delete: <h3> E. Implementation delete: </h3> delete: <p> delete: <span lang="EN-GB"> 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 the policy changes in internal RIPE NCC systems. Internal and external processes and documentation would also need to be updated. delete: </span> delete: </p> insert: <p>

  insert: </p>

delete: <ul> delete: <li> delete: <a class="internal-link" title="" href="resolveuid/92036e9d9f654c39afdbf78b03d65e1b" target="_self" data-val="92036e9d9f654c39afdbf78b03d65e1b" data-linktype="internal"> New insert: <h2>

How to read this draft document: insert: </h2>

insert: <p>

This document relates to the policy delete: </a> delete: </li> delete: <li> delete: <a class="internal-link" title="" href="resolveuid/c3252cbf68de44f592345ff46f377c5d" target="_self" data-val="c3252cbf68de44f592345ff46f377c5d" data-linktype="internal"> Amendments to existing proposal 2015-04, “RIPE Resource Transfer Policies”. If approved, it will create a new policy document “RIPE Resource Transfer Policies”. insert: <br />
It will also delete the following sections or policy documents: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <a href="../../../../publications/docs/ripe-649#55"> Sections 5.5 insert: </a> insert: <span> and insert: </span> insert: <a href="../../../../publications/docs/ripe-649#64"> 6.4 insert: </a> insert: <span> in ripe-649, "IPv4 “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" delete: </a> delete: </li> delete: <li> delete: <a class="internal-link" title="" href="resolveuid/208f044c19f44a359774691082a30e84" target="_self" data-val="208f044c19f44a359774691082a30e84" data-linktype="internal"> Amendments to existing policy document Region” insert: </span> insert: </li>
    • insert: <li>
  • insert: <a href="../../../../publications/docs/ripe-638#Transferring"> Section 4.0 insert: </a> insert: <span> in ripe-638, "Autonomous “Autonomous System (AS) Number Assignment Policies" delete: </a> delete: </li> delete: <li> delete: <a class="internal-link" title="" href="resolveuid/172bfc12399d480e9c8386515fbff010" target="_self" data-val="172bfc12399d480e9c8386515fbff010" data-linktype="internal"> Amendments to existing policy document ripe-655, "IPv6 Policies” insert: </span> insert: </li>
    • insert: <li>
  • insert: <a href="../../../../publications/docs/ripe-650#8--transfer-of-ipv6-resources"> Section 8 insert: </a> insert: <span> . in ripe-650, “IPv6 Address Allocation and Assignment Policy" delete: </a> delete: </li> delete: <li> delete: <a class="internal-link" title="" href="resolveuid/86b69ec995874a8683bccf4709b3c149" target="_self" data-val="86b69ec995874a8683bccf4709b3c149" data-linktype="internal"> Amendments to existing policy document ripe-644, "Policy Policy” insert: </span> insert: </li>
    • insert: <li>
  • insert: <a href="./resolveuid/f8180e3e9ca64c73aa5bbc7623457264" data-val="f8180e3e9ca64c73aa5bbc7623457264" data-linktype="internal"> ripe-644 insert: </a> insert: <span> , “Policy for Inter-RIR Transfers of Internet Resources" delete: </a> Resources”  insert: </span>
insert: <h2>

Contents insert: </h2>

insert: <p>

insert: <a class="anchor-link" href="#scope" target="_self" title=""> 1.0 Scope insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferswithinripenccregion" target="_self" title=""> 2.0 Transfers within the RIPE NCC Service Region insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferrequirements" target="_self" title=""> 2.1 Transfer Requirements insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferrestrictions" target="_self" title=""> 2.2 Transfer Restrictions insert: <br />
insert: </a> insert: <a class="anchor-link" href="#interrirtransfers" target="_self" title=""> 3.0 Inter-RIR Transfers insert: <br />
insert: </a> insert: <a class="anchor-link" href="#general" target="_self" title=""> 3.1 General insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferringtotheripenccregion" target="_self" title=""> 3.2 Transferring Internet Number Resources to the RIPE NCC Service Region insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferringfromtheripenccregion" target="_self" title=""> 3.3 Transferring Internet Number Resources from the RIPE NCC Service Region insert: <br />
insert: </a> insert: <a class="anchor-link" href="#transferstatistics" target="_self" title=""> 4.0 Transfer Statistics insert: <br />
insert: </a> insert: <a class="anchor-link" href="#attribution" target="_self" title=""> 5.0 Attribution insert: </a> insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="scope"> insert: </a> 1.0 Scope insert: </h4>

insert: <p>

This policy outlines: insert: </p>

insert: <ul>
    insert: <li>
  • insert: <span> The rules for Internet number resource transfers within the RIPE NCC services region insert: </span> insert: </li>
    • insert: <li>
  • insert: <span> The rules for Internet number resource transfers (including legacy resources) to and from the RIPE NCC service region (often referred to as inter-RIR transfers) insert: </span> insert: </li>
    • insert: </ul>
insert: <h4>

insert: <br />
insert: <a name="transferswithinripenccregion"> insert: </a> 2.0 Transfers within the RIPE NCC Service Region insert: </h4>

insert: <p>

Any legitimate resource holder is allowed to transfer complete or partial blocks of address space or number resources (IPv4, IPv6 and AS Numbers) that were previously allocated or assigned to them by the RIPE NCC or otherwise through the Regional Internet Registry (RIR) system. Resources are excluded from transfers when RIPE Policies mandate their return to the RIPE NCC.  insert: </p>

insert: <p>

insert: <span> Resources may only be transferred to an entity that has a contractual  insert: </span> insert: <span> relationship with the RIPE NCC or with a RIPE NCC member. insert: </span> insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="transferrequirements"> insert: </a> 2.1 Transfer Requirements insert: </h4>

insert: <p>

Transfers must be reflected in the RIPE Database. Transfers can be on a permanent or non-permanent basis. insert: </p>

insert: <p>

The original resource holder remains responsible for an Internet number resource until the transfer to the receiving party is completed. In the case of a temporary transfer, the original resource holder re-assumes responsibility when the resource is returned. The current resource holder must ensure that all relevant policies are applied.  insert: </p>

insert: <p>

Transferred resources are no different from allocations or assignments made directly by the RIPE NCC and so must be used by the receiving party in accordance with the respective policy documents. insert: </p>

insert: <p>

To complete the transfer, the RIPE NCC will update the registration records of the Internet number resource to reflect the change in holdership. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="transferrestrictions"> insert: </a> 2.2 Transfer Restrictions insert: </h4>

insert: <p>

Scarce resources, which are understood as those resources that are allocated or assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs), cannot be transferred by the resource holder within 24 months from the date the resource was received. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="interrirtransfers"> insert: </a> 3.0 Inter-RIR Transfers insert: </h4>

insert: <h4>

insert: <br />
insert: <a name="general"> insert: </a> 3.1 General insert: </h4>

insert: <p>

Any type of Internet number resource can be transferred to or from the RIPE NCC service region. This includes legacy resources, in spite of the fact there are no specific rules for legacy resource transfers within the RIPE NCC service region. insert: </p>

insert: <p>

Resources are excluded from transfers when RIPE Policies mandate their return to the RIPE NCC. insert: </p>

insert: <p>

RIPE Policies will apply while the transfer is in process, for as long as the Internet number resources are registered within the RIPE NCC service region. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="transferringtotheripenccregion"> insert: </a> 3.2 Transferring Internet Number Resources to the RIPE NCC Service Region insert: </h4>

insert: <p>

The RIPE NCC shall accept all transfers of Internet number resources to its service region, provided they comply with the policies relating to transfers within its service region. insert: </p>

insert: <p>

For transfers from RIR service 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 five years. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="transferringfromtheripenccregion"> insert: </a> 3.3 Transferring Internet Number Resources from the RIPE NCC Service Region insert: </h4>

insert: <p>

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 any commitments imposed by the receiving RIR in order to facilitate the transfer. insert: </p>

insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="transferstatistics"> insert: </a> 4.0 Transfer Statistics insert: </h4>

insert: <p>

The RIPE NCC will publish a list of all holdership changes. This publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses. insert: </p>

insert: <p>

This list will contain information about approved changes. The following information will be published: insert: </p>

insert: <ul>
    insert: <li>
  • The name of the offering party insert: </li>
    • insert: <li>
  • The resource originally held by the offering party insert: </li>
    • insert: <li>
  • The name(s) of the receiving party or parties insert: </li>
    • insert: <li>
  • Each subdivided prefix (each partial block derived from that original block) or resource received insert: </li>
    • insert: <li>
  • The date each resource changed holder in the registry. insert: </li>
    • insert: <li>
  • Whether it was a transfer or merger/acquisition insert: <span>   insert: </span> insert: </li>
    • insert: </ul>
insert: <p>

  insert: </p>

insert: <h4>

insert: <a name="attribution"> insert: </a> 5.0 Attribution insert: </h4>

insert: <p>

This document is developed by the RIPE community. insert: <span>   insert: </span> insert: </p>

insert: <p>

The following people actively contributed by making proposals through the RIPE Policy Development Process: insert: </p>

insert: <p>

Erik Bais  insert: </p>

Get Involved

The Address Policy Working Group develops policies relating to the allocation and registration of Internet number resources (IPv4 and IPv6 addresses and ASNs) by the RIPE NCC and its members. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. To post a message to the list, send an email to address-policy-w[email protected]. Please note that only subscribers can post messages.

Subscribe Archives