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> Removing resources. insert: </p>

insert: <p>

Replacing 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:

  • delete: <a class="external-link" href="../../../../publications/docs/ipv4-policies" target="_self" title=""> insert: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/ipv4-policies" data-val="https://www.ripe.net/publications/docs/ipv4-policies" data-linktype="external"> "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
  • delete: <a class="external-link" href="../../../../publications/docs/ipv6-policy" target="_self" title=""> insert: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/ipv6-policy" data-val="https://www.ripe.net/publications/docs/ipv6-policy" data-linktype="external"> "IPv6 Address Allocation and Assignment Policy"
  • delete: <a class="external-link" href="../../../../publications/docs/asn-assignment-policies" target="_self" title=""> insert: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/asn-assignment-policies" data-val="https://www.ripe.net/publications/docs/asn-assignment-policies" data-linktype="external"> "Autonomous System (AS) Number Assignment Policies"
  • delete: <a class="external-link" href="./resolveuid/2e9fa8749855424f9b5b6e0f68c4a921" target="_self" title="" data-val="2e9fa8749855424f9b5b6e0f68c4a921" data-linktype="internal"> insert: <a class="external-link" href="resolveuid/https:/www.ripe.net/publications/docs/inter-rir-transfers" data-val="https://www.ripe.net/publications/docs/inter-rir-transfers" data-linktype="external"> "Policy for Inter-RIR Transfers of Internet Resources"

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

The proposal covers extends the 24-month transfer restriction to resources that have been transferred due to changes of holdership via transfers to an organisation’s business structure (such as well as mergers and acquisitions. delete: </p> delete: <p> When scarce resources change holdership (whether by transfer, a merger or acquisition), a holding period acquisition). It is activated which important to note that this restriction only prevents them from being transferred for 24 months. A scarce resource under policy transfers – resources subject to this restriction may still change holdership at any time be transferred due to further mergers or acquisitions within the 24-month period. insert: </p>

insert: <p>

The proposal also requires that the RIPE NCC publish information about transfers due to changes to an organisation’s business structure (such as part of a merger or acquisition. delete: </p> delete: <p> The proposal also adds mergers and acquisitions to the statistics acquisition) in the same way that the RIPE NCC publishes. delete: </p> delete: <p>   it already does with general transfers.

Policy Text

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

insert: <p>

insert: <em> - delete: </i> delete: <a href="../../../../publications/docs/ripe-649#55"> delete: <i> insert: </em> insert: <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"> insert: <em> Sections 5.5 delete: </i> delete: </a> delete: <i> and delete: </i> delete: <a href="../../../../publications/docs/ripe-649#64"> delete: <i> insert: </em> insert: </a> insert: <em> and insert: </em> insert: <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"> insert: <em> 6.4 delete: </i> delete: </a> delete: <i> insert: </em> insert: </a> insert: <em> in ripe-649, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
delete: </i> delete: <i> insert: </em> insert: <em> - delete: </i> delete: <a href="../../../../publications/docs/ripe-638#Transferring"> delete: <i> insert: </em> insert: <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"> insert: <em> Section 4.0 delete: </i> delete: </a> delete: <i> insert: </em> insert: </a> insert: <em> in ripe-638, "Autonomous System (AS) Number Assignment Policies"
delete: </i> delete: <i> insert: </em> insert: <em> - delete: </i> delete: <a class="internal-link" href="resolveuid/1a389ad7cec44e179a5532c3fdff46b9#8--transfer-of-ipv6-resources" target="_self" title="" data-val="1a389ad7cec44e179a5532c3fdff46b9#8--transfer-of-ipv6-resources" data-linktype="internal"> delete: <i> insert: </em> insert: <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"> insert: <em> Section 8 delete: </i> delete: </a> delete: <i> insert: </em> insert: </a> insert: <em> . in ripe-655, "IPv6 Address Allocation and Assignment Policy" delete: <br /> delete: </i> delete: <i> insert: </em> insert: </p>

insert: <p>

insert: <em> The text in these sections will be replaced by a reference to the new RIPE Document, "RIPE Resource Transfer Policies" insert: </em> insert: </p>

insert: <p>

insert: <em> - delete: </i> delete: <a href="./resolveuid/f8180e3e9ca64c73aa5bbc7623457264" data-val="f8180e3e9ca64c73aa5bbc7623457264" data-linktype="internal"> delete: <i> insert: </em> insert: <a href="resolveuid/https:/www.ripe.net/publications/docs/ripe-644" data-val="https://www.ripe.net/publications/docs/ripe-644" data-linktype="external"> insert: <em> ripe-644 delete: </i> delete: </a> delete: <i> insert: </em> insert: </a> insert: <em> , "Policy for Inter-RIR Transfers of Internet Resources" delete: </i> delete: </p> delete: <p> delete: <i> Accordingly, these sections or policy documents insert: </em> insert: </p>

insert: <p>

insert: <em> This policy document will be deleted.] delete: </i> insert: </em>

Content

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

insert: <p>

  insert: </p>

insert: <h3>

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

This policy outlines:

  • delete: <span> The rules for Internet number resource transfers within the RIPE NCC services service region delete: </span>
  • delete: <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) delete: </span>
delete: <h4> insert: <h3>


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

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> delete: <span> Resources insert: </p>

insert: <p>

Allocated resources may only be transferred to an another RIPE NCC member. Provider independent resources may be transferred to: insert: </p>

insert: <ul>
    insert: <li>
  • A RIPE NCC member; or insert: </li>
    • insert: <li>
  • An entity that has a contractual  delete: </span> delete: <span> contractual relationship with the RIPE NCC or a RIPE NCC member in accordance with a RIPE NCC member. delete: </span> delete: </p> delete: <p> delete: <span> delete: <br /> delete: </span> the RIPE Policy, “ insert: <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 insert: </a> ”. insert: </li>
    • insert: </ul>
insert: <p>

 

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 change in holdership. delete: </p> delete: <p>   transfer. 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 24 months from the date the resource was received by the resource holder. delete: </p> delete: <p>   delete: </p> delete: <h4> This restriction also applies if the resource was received due to a change in the organisation’s business (such as a merger or acquisition). insert: </p>

insert: <p>

This restriction does not prevent the resources from being transferred due to further mergers or acquisitions within the 24-month period. insert: </p>

insert: <p>

  insert: </p>

insert: <h3>

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


3.1 General

delete: <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. delete: </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. delete: <span>   delete: </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: <h4>   insert: </p>

insert: <h3>

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

The RIPE NCC will publish a list of all holdership changes. transfers. 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 changed holder in the registry. was transferred
  • Whether it was a transfer according to this policy or merger/acquisition a transfer due to changes to an organisation's business structure (such as a merger or acquisition)
 
delete: <h4> insert: <h3>

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

This document is developed by the RIPE community.

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

Erik Bais

delete: <span> Rationale delete: </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 holdership changes under the policy. transfers, including mergers and acquisitions.

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 include apply 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.

Impact Analysis

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.

A. RIPE NCC's Understanding of the Proposed Policy

It is the RIPE NCC’s NCC’s understanding that this proposal will remove replace all transfer-related text from in the various resource policy documents (for IPv4 PA and PI, Provider Aggregatable (PA) and Provider Independent (PI), IPv6 PA and PI, AS 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”. insert: </p>

insert: <p>

The document “Policy for Inter-RIR Transfers of Internet Resources” will be replaced completely by the new policy document.

Most of the requirements for transfers will remain the same as they are in the current transfer policies and accordingly policies, as will the related delete: <a class="internal-link" href="resolveuid/ebbf338ea6044af6a9c815727d8eef0d" target="_self" title="" data-val="ebbf338ea6044af6a9c815727d8eef0d" data-linktype="internal"> insert: <a class="internal-link" title="" href="resolveuid/ebbf338ea6044af6a9c815727d8eef0d" target="_self" data-val="ebbf338ea6044af6a9c815727d8eef0d" data-linktype="internal"> procedures will also remain the same. delete: </p> delete: <p> . insert: </p>

insert: <p>

insert: <span lang="EN-GB"> This analysis will focus on the changes that this proposal introduces. insert: </span>

Entities That Can Receive a Transfer

The proposal text includes the following sentence: proposed policy says:
“Resources “Allocated resources may only be transferred to an another RIPE NCC member. Provider Independent resources may be transferred to: insert: </p>

insert: <ul>
    insert: <li>
  • A RIPE NCC member; or insert: </li>
    • insert: <li>
  • An entity that has a contractual relationship contractual relationship with the RIPE NCC or a RIPE NCC member insert: </li>
    • insert: </ul>
insert: <p>

in accordance with a RIPE NCC member.” delete: </p> delete: <p> As this the RIPE Policy, “ insert: <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 insert: </a> ”. insert: </p>

insert: <p>

It is currently written, it could be interpreted as making it possible for allocated resources to the RIPE NCC’s understanding that allocations of IPv4 and IPv6 can only be transferred to End User organisations that are not members of the RIPE NCC, but do 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 member of the RIPE NCC. Since the RIPE NCC would no longer have a direct contractual relationship with the new holder of the allocation, this could represent a significant risk to the integrity of the RIR system. delete: </p> delete: <p> If this is not the proposer’s intention, we would recommend that they clearly differentiate the requirements sponsoring LIR as per RIPE Policy, “ insert: <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 allocated and independent resources.  Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ”.

Resources Excluded from Transfers

insert: <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: insert: </span>

  • IPv4 IXP Internet Exchange Point (IXP) - "This space will be used to run an IXP peering LAN; other uses are forbidden. [...] New [...] 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: <a class="internal-link" href="resolveuid/b97600388f9d485e87f0c532030f31b3#61" target="_self" title="" data-val="b97600388f9d485e87f0c532030f31b3#61" data-linktype="internal"> insert: <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: <span>
    delete: </span> 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: <span> delete: <br /> delete: <br /> delete: </span>
  • 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."  longer."
    delete: <a href="../../../../publications/docs/ripe-655#anycasting"> insert: <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: <br /> delete: <br />
  • IPv6 for Internet 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."  time." 
    delete: <a href="./resolveuid/417ec4378ad4403fb07330a75e961b9f" data-val="417ec4378ad4403fb07330a75e961b9f" data-linktype="internal"> insert: <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: <br /> delete: <br />
  • Temporary Assignments - "The RIPE NCC may assign number resources to End Users on a temporary deployment basis for a specific time-limited purpose. [...] The [...] The number resources will be automatically de-registered and returned to the appropriate reservation pool at the end of the approved assignment period."  period."
    delete: <a href="../../../../publications/docs/ripe-587#procedures"> insert: <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 Section 2.1
insert: <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 ( insert: <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 insert: </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.   insert: </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. insert: <br />
The RIPE community is currently discussing the policy proposal 2016-03, " insert: <a href="../../../../../resolveuid/7f5aaf4e3996415b8b01ff377a6827e3" data-val="7f5aaf4e3996415b8b01ff377a6827e3" data-linktype="internal"> Locking Down the Final /8 Policy insert: </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.

Holding Period for Scarce Resources

The proposed policy in its latest version says: insert: <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.” insert: </p>

insert: <p>

insert: <span lang="EN-GB"> The RIPE NCC understands “scarce resources” “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.     insert: </span>

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.

Company mergers and network acquisitions 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.

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:
- Directly from the RIPE NCC
- Via a policy transfer
- Via a company merger/takeover delete: <br /> - Via a network acquisition delete: <br /> delete: <br /> If a legal entity has multiple LIRs and decides to consolidate these accounts Through an organisation merger, acquisition, bankruptcy or to move resources from one LIR account to another of its LIR accounts, this move of resources into a single account would liquidation insert: </p>

insert: <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 there “receiving back”, the Address Policy Working Group decided during RIPE 69 that the 24-month holding period should not apply to such insert: <a href="resolveuid/0ffcedc9e2e249b8b0073d22bd43e24b" data-val="0ffcedc9e2e249b8b0073d22bd43e24b" data-linktype="internal"> temporary holdership changes insert: </a> .  insert: <br />
The temporary resource holder will not be able to transfer the resource further during the period in which the resource is no change of the registered resource holder. to them.

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.

Publishing Transfer Statistics

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.

The consolidation of multiple LIR accounts belonging to the same legal entity or the move of resources from one LIR account to another LIR account belonging to the same legal entity will not be published, as there is no change of holdership involved. 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" href="resolveuid/8f0a965d-1993-4c26-b707-578d22162b38" target="_self" title="" data-val="8f0a965d-1993-4c26-b707-578d22162b38" data-linktype="internal"> insert: <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 , “Post insert: <span lang="EN-GB"> “Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text”, Text”, the RIPE NCC no longer performs needs-based evaluation of transfers; publication transfers. Publication of statistics for non-approved IPv4 transfer requests is therefore no longer relevant.   delete: </p> delete: <p>   insert: </span> insert: </p>

insert: <p>

insert: <span lang="EN-GB"> There is an important distinction between “non-approved” “non-approved” requests and “invalid/incomplete” “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: <strong> delete: </strong> non-approved.   insert: </span>

B. Impact of Policy on Registry and Addressing System

Address/Internet Number Resource Consumption: insert: <br />
delete: <br /> insert: <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. insert: </span>

Fragmentation/Aggregation:
insert: <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. insert: </span>

C. Impact of Policy on RIPE NCC Operations/Services

Software Engineering:
Software development will be needed to:

  • Update the transfer statistics to differentiate between policy transfers and mergers/acquisitions
  • Prevent transfer of scarce resources for 24 months after any ownership change
    • delete: <li> Exclude LIR Account consolidations from the 24-month restriction delete: </li>

Registration Services:
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.  

External Relations:
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. The trade-off, however, is that there co-exist certain policies based on specific operations and others based on specific types of resources. This has the potential to complicate future policy development activity, and In the short term it is expected that increased efforts will be needed to explain to the RIPE NCC membership and other stakeholders which policy document applies in which situations, especially during the implementation period. We recognise that the RIPE NCC has a primary role in making this information available, but hope the RIPE community can assist and support us in we need to increase outreach to raise awareness of these efforts. changes within the broader Internet community.

Billing/Finance Department: insert: <br />
delete: <br /> insert: <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. insert: </span>

RIPE Database:
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: <h4> insert: <h3>

D. RIPE NCC Executive Board delete: </h4> delete: <p> The Executive board has examined both the proposal and the RIPE NCC impact analysis for this proposal. delete: </p> delete: <p> They make the following two comments: delete: <br /> delete: <br /> 1) The RIPE NCC impact analysis notes that acceptance of this proposal could significantly affect the stability of the RIR system as a whole by allowing transfer of any resource (including assigned PA space) to any entity including one that is not a member of the RIPE NCC (or any other RIR). delete: <br /> delete: <br /> 2) The Board also notes that the following wording delete: </p> delete: <p style="padding-left: 30px; "> "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> reinforces this. delete: </p> delete: <p> We would respectfully suggest that this policy proposal be returned to the community for further work. delete: </p> delete: <h3> E. Legal Legal Impact of Policy

insert: <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: <a class="internal-link" href="resolveuid/e47b56840d8e4e4091decb3751de9179" target="_self" title="" data-val="e47b56840d8e4e4091decb3751de9179" data-linktype="internal"> “Transfer “ insert: </span> insert: <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 Member’s Official Legal Name ”. ”.

F. Implementation E. Implementation

insert: <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: </p> insert: </span> insert: </p>

Draft documents relating to "RIPE Resource Transfer Policies"
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