InterRIR transfers: what IPv4 moves actually work

Only four RIRs currently support moving IP addresses and ASNs across regional boundaries. Inter-RIR transfers enable the specific movement of IP addresses and Autonomous System Numbers from a network in one Regional Internet Registry service region to a different RIR. This guide details the strict eligibility criteria for resource holders, the exact transferable resources allowed between RIPE NCC and other registries, and the standardized submission procedures required to execute these moves.

As of 2023, policies fully cover IPv4 transfers but only partially support ASN transfers, leaving IPv6 Inter-RIR transfers entirely unsupported across all regions. Data confirms that while ARIN, RIPE NCC, and APNIC enable ASN movement, transfers originating from LACNIC cannot include ASNs. AFRINIC has yet to implement any Inter-RIR transfer policies, creating a distinct gap in global resource management.

The process demands rigorous adherence to regional rules, such as the requirement for active network elements within the destination region. Understanding these limitations is critical for any organization attempting to restructure its global IP portfolio without triggering policy violations or operational downtime.

The Role of Inter-RIR Transfers in Global IP Resource Management

Inter-RIR Transfer Definition for IPv4 and ASN Resources

Inter-RIR transfers relocate Internet number resources, specifically IPv4 blocks and ASNs, across distinct Regional Internet Registry boundaries. This mechanism enables resource owners to move assets between service regions rather than restricting transactions to internal registry limits. Currently, only four organizations enable these cross-regional movements: RIPE NCC, APNIC, ARIN, and LACNIC. As of 2023, policies fully cover IPv4 inter-RIR transfers, partially cover ASN inter-RIR transfers, and do not cover IPv6 inter-RIR transfers.

Eligibility depends heavily on the specific resource type and originating registry pair. IPv4 addresses flow freely from RIPE NCC to ARIN, APNIC, or LACNIC. ASN transfers face stricter constraints where LACNIC blocks cannot migrate externally at all. ARIN, RIPE NCC, and APNIC do support ASN Inter-RIR transfers. Compatible policies create a closed loop of interoperability among the participating entities.

This fragmentation forces network architects to validate path continuity separately from address space availability.

Transferring IPv4 Addresses and ASNs from RIPE NCC to ARIN

Organizations moving assets from RIPE NCC to ARIN relocate IPv4 address blocks and Autonomous System Numbers under specific bilateral agreements. Both LIRs and End Users explicitly qualify to execute these inter-regional transactions, provided the destination registry accepts the resource type. IPv4 moves freely between RIPE NCC, ARIN, and APNIC. ASN portability faces tighter constraints due to partial policy coverage.

This matrix confirms that while IPv4 liquidity remains high across all four active regions, ASN mobility excludes LACNIC entirely. Operators must verify that their allocations meet the receiving region's necessity criteria before initiation. A cost exists: although policies align for IPv4, the administrative burden of validating cross-regional eligibility often delays deployment timelines compared to intra-regional moves. Successful execution depends on rigorous adherence to the originating registry's release protocols.

Provider-Independent vs Provider-Aggregatable Addresses in Cross-Region Moves

Inter-RIR mechanisms fundamentally change the holdership of Internet number resources from an offering party A to a receiving party B, yet policy constraints dictate which formats survive the transition. Current frameworks fully cover IPv4 transfers but explicitly exclude IPv6 inter-RIR moves, limiting optimization to legacy v4 assets. Organizations holding PI assignments and PA allocations can both participate in these transfers, with the status able to remain the same or be converted to another one upon transfer. APNIC restricts eligible partners for these transactions to RIPE NCC, ARIN, and LACNIC, ensuring strict policy alignment during redistribution. This limitation means transfers to unlisted regions remain impossible regardless of address type. InterLIR enables the strategic navigation of these bilateral compatibilities to maximize asset liquidity. Operators must verify that their unused IPv4 inventory meets the specific eligibility criteria of both originating and receiving registries before initiating requests. Adherence to specific registry requirements regarding active network elements in the destination region is necessary to avoid delays in the evaluation phase.

Eligibility Criteria and Policy Constraints for Resource Holders

Eligible Requestors: LIRs, Non-Members, and Legacy Holders

Three distinct entity categories may initiate an Inter-RIR transfer from the RIPE NCC region. The primary actors are LIRs registered directly with the registry, who hold full contractual standing to move resources. Non-members lacking a direct agreement must route their request through a sponsoring LIR to satisfy validation requirements. This mechanism allows organizations without regional membership to participate in the global market while maintaining registry oversight. A third group comprises legacy IPv4 holders who operate without a current contractual relationship with the RIPE NCC. These entities retain the right to transfer assets directly, provided they prove current rights ownership and confirm no active disputes exist over the block.

Applying the Two-Year Lock-Up Rule to Recent Allocations

IPv4 subnets allocated by RIPE NCC cannot be transferred within the next 2 years after the last transfer or allocation date. This temporal restriction acts as a hard barrier for organizations attempting to relocate ALLOCATED PA or ASSIGNED PI blocks shortly after receipt. Operators must calculate their eligibility window precisely by identifying the specific date of their most recent resource event. Attempting an inter-RIR move before this period expires results in immediate rejection by the registry validation team. The rule applies uniformly regardless of whether the destination region is ARIN, APNIC, or LACNIC.

A critical complication arises when legal disputes overlap with timing restrictions. A company may find its assets frozen not by the clock, but because the resources are currently involved in a legal or administrative dispute. This dual-layer blocking mechanism means that even expired lock-up periods do not guarantee transfer readiness if ownership is contested. Organizations holding LEGACY resources face no such timing delays, provided they maintain clear title. Miscalculating this window wastes administrative effort and delays network expansion projects. Strategic patience is required when recent allocations form the basis of global routing plans.

Policy Compatibility Risks and the APNIC Coalition Limit

Global interoperability for IP resource transfers relies entirely on bilateral policy alignment rather than universal recognition. APNIC explicitly recognizes only ARIN, RIPE NCC, and LACNIC as eligible partners, creating a restricted coalition for address movement. This regulatory framework implicitly excludes regions like AfriNIC due to a lack of compatible transfer policies, effectively blocking transactions with those jurisdictions. Operators attempting to move provider-independent blocks to non-aligned regions face immediate administrative rejection regardless of technical readiness. The dual-policy requirement means a transaction must satisfy the regulatory conditions of both the source and recipient registries simultaneously.

This fragmentation forces network architects to verify regional eligibility before initiating any legacy IPv4 relocation project. A critical oversight involves assuming that market demand overrides regional policy; in reality, registry rules supersede commercial agreements. The cost of ignoring these boundaries is a stalled transaction and locked capital. Strategic navigation of these bilateral constraints remains necessary for optimizing existing IPv4 resources across global borders.

Executing Inter-RIR Transfers Through Standardized Submission Procedures

Inter-RIR Transfer Submission Template and Email Protocol

Submit the completed inter-RIR transfer template alongside all supporting documentation to [email protected] to initiate resource relocation. This action starts the validation sequence required for moving Internet number resources across regional boundaries. Proofs of ownership must accompany the request because Inter-RIR transfers fundamentally shift asset holdership from an offering party to a receiving party. Strict adherence to these submission protocols prevents immediate workflow halts caused by incomplete packets. Unlike intra-regional updates, this procedure demands dual-policy satisfaction, meaning the request must align with regulations in both the source and destination regions. Providers verifying that allocations meet the destination RIR's eligibility rules before transmission avoid significant delays. Using an incorrect or incomplete template extends the timeline for securing necessary IPv4 capacity. The constraint of matching bilateral policies creates a narrow window for successful execution, demanding precise documentation.

1. Attach proof of rights for the IPv4 blocks or ASNs in question.
2. Send the completed request.

Executing RIPE to ARIN Transfers for Non-Member Recipients

Nonmember recipients transferring IPv4 blocks from RIPE NCC to ARIN must resolve contractual status before technical evaluation begins. The receiving entity lacks automatic standing within the registry system and must bridge this gap to proceed. Operators face a binary choice: establish a direct contractual relationship with the RIPE NCC or engage a sponsoring LIR to act as an intermediary for ASSIGNED PI resources. This prerequisite ensures that the party accepting the Internet number resources accepts full liability for their future management. The registry will not process the transfer request without this legal framework in place, regardless of the buyer's readiness in the destination region.

Compliance with sponsorship requirements is mandatory; attempts to proceed without establishing the necessary contractual relationship or sponsoring LIR arrangement will prevent the registry from processing the request. ARIN provides granular reporting on transferred assets, yet the source registry strictly enforces these entry barriers to maintain database integrity. Providers should verify all sponsorship agreements are finalized before initiating the email submission to prevent administrative loops.

Legacy Status Exemptions and Contractual Validation Checklist

Determine legacy classification immediately, as LEGACY status resources bypass standard contractual renewal mandates during cross-regional moves. Operators must verify specific exemptions before submitting documentation to avoid processing rejections based on missing agreements.

1. Confirm the resource holds LEGACY status within the registry database to waive new contract requirements.
2. Validate that the target network maintains an active element inside the destination service region.
3. Ensure assets remain dispute-free, satisfying the mandatory current rights holder criteria for both jurisdictions.
4. Ensure the transfer request originates in the originating service region by following the specific FAQ instructions for that RIR.

Non-legacy transfers require the recipient to establish the relationship prior to evaluation. The following table contrasts validation paths based on resource type:

Strict adherence to these distinctions helps prevent bilateral policy failures. Assuming regional approval guarantees global acceptance is a common error; incompatible policies in the destination region can halt execution even with valid source documentation. 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 logical branching ensures operators do not waste cycles on ineligible submission paths.

Strategic Implications of Cross-Regional IP Asset Mobility

Regulatory Classification of Section 8.4 Transfers

ARIN formally classifies cross-regional movement of Internet number resources under Section 8.4 of its Number Resource Policy Manual, a designation that strictly governs eligibility for network operators moving assets from North America. This regulatory framework defines Inter-RIR transfers as the movement of IP addresses and Autonomous System Numbers (ASNs) from a network in one Regional Internet Registry service region to a network in another. Unlike intra-regional transactions, these movements require simultaneous compliance with the policies of both the source and destination registries, creating a dual-approval dependency. Operators must recognize that dual policy adherence requires satisfying the regulatory frameworks of both regions, demanding verification that resources are free of legal disputes before initiation. The existence of reports on number resources transferred confirms that ARIN tracks these specific NRPM Section 8.4 transactions separately from domestic transfers, highlighting their distinct operational status. A limitation often overlooked is that while IPv4 transfers are fully supported, ASN mobility remains partially restricted depending on the specific RIR pair involved, such as the inability to move ASNs from LACNIC. InterLIR assists organizations in navigating these complex bilateral compatibilities to ensure successful resource redistribution without policy violations.

Executing LACNIC to RIPE NCC Asset Relocation

Moving IPv4 blocks from LACNIC to RIPE NCC begins only after the recipient establishes a valid contractual relationship with the destination registry. If the receiving party does not have a contractual relationship with the RIPE NCC, it shall establish one prior to the evaluation of the transfer request. Operators must verify that the specific IPv4 address space is free from legal disputes before initiating the workflow. The process requires strict adherence to dual-policy compliance, satisfying both the source and destination regulatory frameworks simultaneously.

• Confirm the receiving network holds an active contractual relationship with RIPE NCC prior to submission.
• Validate that resources are not involved in ongoing administrative or legal conflicts.
• Submit the inter-RIR transfer template with full justification for intended resource utilization.
• Review current ASN inter-rir policy execution rules, as LACNIC does not permit ASN exports to other regions.

A critical limitation exists for Independent System Numbers; current policies do not permit ASN inter-rir policy execution from LACNIC to other regions. While IPv4 mobility is fully supported, ASN transfers from this specific region remain restricted, unlike movements originating from ARIN or APNIC. This reality creates a strategic constraint where holding legacy ASNs in LACNIC limits transfer options to regions that do not support ASN imports from LACNIC. Network planners must prioritize IPv4 optimization while recognizing that ASN portability requires alternative regional positioning. InterLIR enables this complex navigation by managing the documentation and policy alignment required for successful asset relocation. The inability to transfer certain resource types shows the need for precise initial allocation planning.

Application: Operational Risks of the APNIC Coalition Limit

APNIC explicitly recognizes only ARIN, RIPE NCC, and LACNIC as eligible partners, implicitly excluding regions like AfriNIC due to a lack of compatible transfer agreements. This policy harmonization requirement forces operators targeting African markets to seek alternative acquisition strategies. The lack of universal interoperability means IPv4 market liquidity is fragmented, preventing direct asset mobility between specific global zones.

• Operators cannot execute direct Inter-RIR transfers from AfriNIC to APNIC due to missing bilateral agreements.
• Resources involved in legal or administrative disputes face a universal barrier, as both ARIN and APNIC prohibit moving contested assets.
• Strategic planning must account for excluded regions where demand outpaces local supply.
• Audit geographic expansion plans against rigid policy boundaries before committing capital.

The strategic risk involves potential isolation from emerging markets where demand outpaces local supply. While the ASN inter-rir policy enables movement between substantial economies, the exclusion of specific registries creates a tiered global infrastructure. InterLIR advises clients to audit their geographic expansion plans against these rigid policy boundaries before committing capital. Failure to account for these coalition dynamics can prevent direct resource acquisition from excluded regions. Network operators must treat policy compatibility as a primary constraint in their global architecture design. Direct acquisition from excluded regions remains impossible without policy changes.

References

• RIPE IPv4 Transfer Process: How to Buy, Sell, and