Inter-RIR Transfer Policy

Resource scope and policy structure · The old text proposed a separate inter-RIR transfer policy covering IPv4, IPv6, and ASNs. The new text instead revises the existing IPv4 transfer section, combines intra-RIR and inter-RIR IPv4 rules there, and omits the proposed IPv6 and ASN transfer provisions.

Legacy-resource restriction for inter-RIR transfers · The old text restricted outbound IPv4 and ASN transfers from LACNIC to legacy resources while allowing inbound transfers regardless of status. The new policy text permits an inter-RIR IPv4 transfer only when the resources are legacy whenever either organization belongs to another region, while expressly excluding intra-RIR transfers from that restriction.

Receiving-organization qualification · The old text required a recipient to justify need before LACNIC or the corresponding RIR depending on transfer direction. The new text specifies that a recipient within the LACNIC region must justify its IPv4 needs before LACNIC, while a recipient in another region is governed by the corresponding RIR's criteria, verifications, and requirements.

Legal documentation for transfers · The old text required both transferring and receiving entities to submit a copy of the supporting legal document to LACNIC for inter-RIR transfers. The new text requires both organizations to submit a signed copy to LACNIC only for intra-RIR transfers and provides that documentation for inter-RIR transfers will be agreed between the two RIRs.

Transfer-log contents · The old text required the existing log to record the transaction date, transferring and receiving entities, the corresponding RIR in each case, and other relevant resource data. The new text specifies the transferred addresses and, for inter-RIR transfers, the source and destination RIRs, while retaining the transaction date and participating organizations.

Transfer waiting periods and post-transfer eligibility · The old text imposed a two-year transfer prohibition on resources associated with LACNIC IPv6 allocations or assignments and a one-year retransfer prohibition on transferred blocks and sub-blocks. The new text removes the IPv6-specific two-year rule, retains a one-year prohibition on retransferring IPv4 addresses in full or in part, applies a one-year transfer prohibition to addresses from LACNIC allocations or assignments, and makes the originating organization ineligible for LACNIC IPv4 allocations or assignments for one year.