LAC-2020-1 v1 eng
8 removals
31 lines
14 additions
37 lines
2.3.2.18 - IPv4 address transfers
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.
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 both to transfers where one of the organizations involved is part of another region (inter-RIR transfers) as well as to transfers within the LACNIC region (intra-RIR transfers).
This policy applies both to transfers where one of the organizations involved is part of another region (inter-RIR transfers) as well as to transfers within the LACNIC region (intra-RIR transfers).
2.3.2.18.1. The minimum block size that may be transferred is a /24.
2.3.2.18.1. The minimum block size that may be transferred is a /24.
2.3.2.18.2. In order for an organization within the LACNIC region to qualify for receiving a transfer, it must first go through the process of justifying its IPv4 resources before LACNIC. That is to say, the organization must justify before LACNIC the initial/additional allocation/assignment, as applicable, according to the policies in force.
2.3.2.18.2. In order for an organization within the LACNIC region to qualify for receiving a transfer, it must first go through the process of justifying its IPv4 resources before LACNIC. That is to say, the organization must justify before LACNIC the initial/additional allocation/assignment, as applicable, according to the policies in force.
If the receiving organization is part of another region, it will be subject to the criteria, verifications and requirements of the corresponding RIR.
If the receiving organization is part of another region, it will be subject to the criteria, verifications and requirements of the corresponding RIR.
2.3.2.18.3. LACNIC or the corresponding RIR (depending on whether the transfer is inbound or outbound) will verify the holder of the resources to be transferred and check that they are not involved in any dispute.
2.3.2.18.3 Receiving organization must have LACNIC allocated IPv6 space and be able to prove it is being used by providing LACNIC documented network deployment details to prove IPv6 is operational in significant parts of the network.
LACNIC staff will define a minimal criteria to guarantee the information provided proves IPv6 is operational. If necessary staff may require further information to validate this requirement.
In the case the receiver provides a written statement from its upstream that IPv6 connectivity is unavailable, the IPv6 requirement may be waived.
2.3.2.18.4. LACNIC or the corresponding RIR (depending on whether the transfer is inbound or outbound) will verify the holder of the resources to be transferred and check that they are not involved in any dispute.
In the case of intra-RIR transfers, both organizations must submit to LACNIC a signed copy of the legal document supporting the transfer.
In the case of intra-RIR transfers, both organizations must submit to LACNIC a signed copy of the legal document supporting the transfer.
In the case of inter-RIR transfers, the documentation supporting the operation will be agreed between the two RIRs.
In the case of inter-RIR transfers, the documentation supporting the operation will be agreed between the two RIRs.
2.3.2.18.4. LACNIC shall maintain a publicly accessible transfer log of all IPv4 address block transfers registered before LACNIC. This log will be used to record the date on which the transaction took place, the organization that originated the transfer, the receiving organization, the transferred addresses and, in the case of inter-RIR transfers, the source and destination RIRs.
2.3.2.18.5. LACNIC shall maintain a publicly accessible transfer log of all IPv4 address block transfers registered before LACNIC. This log will be used to record the date on which the transaction took place, the organization that originated the transfer, the receiving organization, the transferred addresses and, in the case of inter-RIR transfers, the source and destination RIRs.
2.3.2.18.5. The organization that originated the transfer shall automatically be ineligible to receive IPv4 resource allocations and/or assignments from LACNIC for a period of one year as of the transaction date registered in the transfer log.
2.3.2.18.6. The organization that originated the transfer shall automatically be ineligible to receive IPv4 resource allocations and/or assignments from LACNIC for a period of one year as of the transaction date registered in the transfer log.
2.3.2.18.6. Addresses that have previously been transferred may not subsequently be transferred again (in full or in part) for a period of one year as ofthe transaction date specified in the transfer log.
2.3.2.18.7. Addresses that have previously been transferred may not subsequently be transferred again (in full or in part) for a period of one year as ofthe transaction date specified in the transfer log.
2.3.2.18.7. Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect the change of holder.
2.3.2.18.8. Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect the change of holder.
2.3.2.18.8. Both the transferring and the receiving organizations will be subject to the policies and membership terms and conditions of the corresponding RIR.
2.3.2.18.9. Both the transferring and the receiving organizations will be subject to the policies and membership terms and conditions of the corresponding RIR.
2.3.2.18.9. Addresses from allocations or assignments from LACNIC, whether initial or additional, may not be transferred (in full or in part) for a period of one year as of the allocation or assignment date.
2.3.2.18.10. Addresses from allocations or assignments from LACNIC, whether initial or additional, may not be transferred (in full or in part) for a period of one year as of the allocation or assignment date.
2.3.2.18.10. Legacy resources transferred into the LACNIC region will no longer be considered legacy resources.
2.3.2.18.11. Legacy resources transferred into the LACNIC region will no longer be considered legacy resources.