Add IPv6 operational as a requirement for IPv4 transfers

Qualifying IPv6 resources for transfer recipients · The IPv6 prerequisite was broadened from an operational IPv6 allocation issued by LACNIC to an operational IPv6 allocation or assignment issued by either LACNIC or a provider.

IPv6-requirement waiver when IPv4 cannot be supplied · A new waiver was added allowing a transfer of up to a /22 without satisfying the IPv6 requirement when LACNIC cannot meet a new entrant's IPv4 request.

IPv6-connectivity waiver for IPv4 transfer recipients · The old text required both a written statement from the recipient's upstream provider or providers that IPv6 connectivity was unavailable and justification that other means were not technically acceptable. The new text removes the latter justification requirement, leaving the written upstream statement as the stated basis for potentially waiving the IPv6 requirement.

Removal from an IPv4 waiting list after a successful transfer · The old text required an organization on any LACNIC IPv4-resource waiting list to be removed from that list upon a successful transfer. The new text omits this requirement.

IPv6 waiver extends to organizations with no IPv4 space · Version 4 adds a second basis for the up-to-/22 transfer exception: the receiving organization holds no IPv4 space. Previously this exception depended on LACNIC being unable to meet a request from the reserved pool under section 11.1. The IPv6 waiver remains discretionary, and the separate upstream-unavailability exception remains.

Meaning of operational IPv6 deployment clarified · Version 4’s additional information clarifies significant parts of the network as segments delivering IPv6 to end users or downstream networks, not merely core or border equipment without that delivery role. The operative requirement to document deployed IPv6 remains; this adds guidance on the proof expected, rather than changing every IPv4 transfer condition.