Permission to Transfer and Non-Return of Resources

This proposal corrects an inconsistency between the requirement to justify the need for IPv4 resources and the possibility of transferring such resources.

This proposal corrects a lack of clarity or inconsistency between the requirement to justify the need for IPv4 resources and the possibility of transferring such resources.

In addition, three sections included in the IPv4 portion of the Policy Manual (2.3.2.13.2. Geolocation, 2.3.2.14. Security and Confidentiality, 2.3.2.15. Equal Processing of All Applications) clearly apply to IPv4, IPv6, and even ASN resources, so the reasonable thing to do would be to move these texts to Section 1, Definitions. Because these are minor editorial changes, they can be fixed without the need to submit a separate proposa

Furthermore, if a transfer is rejected for whatever reason, there would clearly be a breach of the needs-based requirement. Current text No such text exists

f 2.3.6. Permission to Transfer and Non-Return of Resources While address allocation and assignment policies are initially based on the justification of need, in practice, the introduction of transfers means that it is no longer necessary to maintain this justification. Therefore, even in case of failed transfers, returning the resources to LACNIC will no longer be required and, instead, the resources must be transferred on successive occasion

2.3.6. Permission to Transfer and Non-Return of Resources While address allocation and assignment policies are initially based on the justification of need, the implementation of transfers eliminates the need to maintain this justification. Therefore, returning the resources to LACNIC will no longer be required in case of failed transfers or mergers and acquisitions

- Presented at: LACNIC 36 (11/10/202

Presented at: LACNIC 37 (04/05/2022