Summary

The goal is to introduce a minor yet important adjustment to the current text that preserves the proposal's original spirit: allowing the use of idle IPv4 addresses in networks that need them.
This seeks to ensure that the recipient has justified need for the resources.

Rationale (Describe the problem you intend to solve)

Policies allowing the transfer of IPv4 addresses have been in effect since regional IPv4 address pools were exhausted.
The primary objective of these policies is to meet IPv4 needs during the transition to IPv6, which is why they must be based on justified need.
For inter-RIR transfers, there is currently no explicit requirement for reciprocity in validating the need.
This proposal seeks to adjust the rules to ensure that the recipient of IPv4 addresses justifies their need.
This requirement is already applied in intra-RIR processes, as well as in inter-RIR processes where the recipient is located within the LACNIC region.

Current text

2.3.2.18. IPv4 Address Transfers

IPv4 block transfers shall be allowed between LIRs and/or End Users (hereinafter organizations) in accordance with the conditions set forth in this section.

This policy applies to transfers where one of the entities involved is part of another region (inter-RIR transfers) as well as to transfers within the LACNIC region (intra-RIR transfers).

New text
Analyze diff

2.3.2.18. IPv4 Address Transfers

IPv4 block transfers shall be allowed between LIRs and/or End Users (hereinafter organizations) in accordance with the conditions set forth in this section.

This policy applies to transfers where one of the entities involved is part of another region (inter-RIR transfers) as well as to transfers within the LACNIC region (intra-RIR transfers).

Inter-RIR transfers under this section will only be permitted between RIRs that share reciprocal and compatible policies based on justified need.

Additional information

RIRs in other regions already include the requirement for a justified need. At RIPE, however, this applies provided the request originates from the RIR of the entity originating the transfer.

Timetable

-

References

-

Presented at:

-