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 within and outside the RIPE NCC 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. If another RIR has a different policy, the RIPE NCC should create an operational procedure that satisfies the requirements of both RIRs in order to allow transfers to and from its service region. 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 there is no specific transfer policy for them.
Amendments to the existing policy, “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”, are also proposed to bring the policy it in line with the new policy.
This policy describes the transfer of Internet number resources between a resource holder within the RIPE NCC service region and a resource holder within the region of another of another Regional Internet Registry (RIR).
This policy outlines the rules for Internet number resource transfers between the RIPE NCC and other RIR service regions.
1.1 Scope
The policy for transferring Internet number resources to or from the RIPE NCC service region will apply to any type of Internet number resources for which there is a transfer policy within the RIPE NCC service region.With be general for any resource. A transfer policy must exist for each type of Internet number resource within the RIPE NCC service region. With this policy, legacy resources can be transferred to or from the RIPE NCC service region, in spite of the fact there is there is no specific transfer policy for them.
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.
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.
For transfers 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.
When Internet number resources are transferred from another RIR, the RIPE NCC will work with the resource holder to fulfil any requirements of the sending RIR.
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.
[The following text will update section 5.5 in the RIPE Document ripe-623, “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”, if the proposal reaches consensus.]
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. System.
Address space may only be re-allocated to another LIR that is also a member of the RIPE NCC.
Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis.
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.
[…]
Any resource holder 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. System.
Address space may only be re-allocated to another resource holder who is a member of an RIR that allows transfers.
Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis.
For transfers 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 five years.
While the transfer is in process, during the time the internetWhen Internet number resources are transferred from another RIR, the RIPE NCC will work with the resource holder to fulfil any requirements of the sending RIR.
Resource holders that receive a re-allocation from another resource holder cannot re-allocate complete or partial blocks of the same address space to another resource holder within 24 months of receiving the re-allocation.
[…]
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 only as an indication only. of the possible impact that the proposal might have if it is accepted and implemented.
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 on its implementation by the RIPE NCC, but also on its acceptance by the other RIRs. The RIPE NCC has therefore requested feedback from contacted the other RIRs with inter-RIR transfer policies in place (APNIC and
ARIN).Both RIRs have since confirmed that the proposed policy is compatible with their Inter-RIR transfer policies. The modified proposal meets the “needs based” requirement that is ARIN) for feedback.
The following statement has been received from APNIC and ARIN:
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.The its policy document. RIPE policy document ripe-622 (paragraph 5.1, sub 3), addresses a needs base in an implicit manner. It is therefore not possible for the APNIC secretariat to interpret this and take a position. The APNIC secretariat indicates that it will consult their community in order to get guidance on how to proceed. ARIN staff notes that the lack of a specific needs-based requirement in the RIPE policy document will prevent the policy from being deemed compatible with ARIN's Inter-RIR transfer policy requirements to the RIPE region (although its adoption will have no effect on Inter-RIR transfers between ARIN and the APNIC region.)”It is therefore important to note that the
The proposed policy sets a general framework for transferring Internet number resources between RIPE NCC members and resource holders in other RIR Regional Internet Registry (RIR) service regions.
Resources may be transferred to and from the RIPE NCC service region if:
The proposed policy asks the RIPE NCC to define the communication and operational procedure with the RIR involved in the transfer.
Currently, 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 NCC. Existing RIPE Policies will be applied.
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. applied to IPv4 resources.
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.
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 the RIPE Policies corresponding to their new status.
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. Currently no other Internet number resources can be transferred.
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.
It is the RIPE NCC’s understanding that resources being transferred are the resources to be transferred would remain subject to the policies of an RIR as long their are registered in its registry.
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.
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.
The proposed policy can only apply to RIRs with between Regional Internet Registries (RIR) with a compatible inter-RIR transfer policies.
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. In situations where a transfer is not accepted by one of the involved registries, it can not be completed. 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.
The proposed policy text has no defined limit on the desired level of policy compliance towards the RIRs involved and suggests that the RIPE NCC adopts procedures and coordinates with the other registry in fulfilling requirements for the transfer to succeed.
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. ended.
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.
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.
The potential for disagreement between RIRs on policy compliance could require cross-registry arbitration to resolve such conflicts (for example, conflicts, for example if a member of the RIPE NCC disagrees with the decision of another RIR). 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.
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.
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.
In the RIPE NCC service region, 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). transferred. This is in addition to all of the eligible prefixes registered in other RIR service regions that could be transferred.
The RIPE NCC has seen a considerable increase in transfer activity since 2012. In 2014, more than 900 At least 800 PA allocation transfers were completed are expected to be processed within the RIPE NCC service region. region by the end of 2014. The RIPE NCC has seen a considerable increase in transfer activity since 2012. 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.
If this proposal reaches consensus and is deemed compatible by other RIRs, the RIPE NCC Registration Services Department will process requests to transfer resources to or from its service region:
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. transfers would require the RIPE NCC to evaluate transfer requests according to the policies and procedures of multiple RIRs. Each RIR might have different requirements. In order to create and maintain this knowledge base, the RIPE NCC will have to increase its coordination effort with the other RIRs. Furthermore, it is expected that a mechanism would need to be established to allow other RIRs to review whether the RIPE NCC’s evaluation of their requirements matches their expectations. This work is expected to require a considerable amount of time and resources.
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.
The RIPE Database will reflect inter-RIR transfers.
For prefixes transferred to the RIPE NCC service region, resource holders will be able to set up setup reverse DNS in the RIPE Database based on the existing inter-RIR DNS information exchange. exchange.
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.
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 Requests to transfer legacy resources can be evaluated without a contract, though 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. in these cases.
A procedural document procedure will need to be drafted that outlines the transfer procedure and due diligence checks of all the RIRs involved in inter-RIR transfers.
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.
After the transfer is completed, the transferring party may need to update its their 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 to the transferred resources.
The requirements for a transfer to be approved by the RIPE NCC may be different from those of other RIRs. According to the
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.
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.
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 dependant on matching policies and procedures between the RIRs involved.