Add IPv6 operational as a requirement for IPv4 transfers

The objective of this proposal is to add as a requirement for organizations in process of receiving transferred IPv4 space under 2.3.2.18 to show they have an IPv6 allocation by LACNIC operational on their networks.

The objective of this proposal is to add as a requirement for organizations in process of receiving transferred IPv4 space under 2.3.2.18 to show they have an IPv6 allocation/assignment by LACNIC or a provider and that is operational on their networks.

In the case the receiver provides a written statement from its upstream that IPv6 connectivity is unavailable, the IPv6 requirement may be waived.

In the case LACNIC is not able to meet a new entrant request for IPv4 space the IPv6 requirement may be waived for a transfer up to a /22.

In the case LACNIC is not able to meet a new entrant request for IPv4 space the IPv6 requirement may be waived for a transfer up to a /22.

In the case LACNIC is not able to meet a new entrant request for IPv4 space, or the organization does not hold any IPv4 space the IPv6 requirement may be waived for a transfer up to a /22.

If LACNIC is not able to meet a request using the reserved pool under 11.1 conditions the requesting organization will be permitted to transfer an IPv4 space equivalent of maximum of /22 and the IPv6 requirement may be waived.

If LACNIC is not able to meet a request using the reserved pool under 11.1 conditions, or the organization does not hold any IPv4 space the requesting organization will be permitted to transfer an IPv4 space equivalent of maximum of /22 and the IPv6 requirement may be waived.

Timetable - References A similar proposal has been presented in ARIN: • https://www.arin.net/participate/policy/drafts/2019_19/ Work is been done in regards to this proposal in other RIRs to present equivalent proposals there.

The term “significant parts of the network” refers to the segments of the network which are responsible for delivering IPv6 connectivity to the end-user or a downstream and not only to core or border equipment which do not have a direct relationship in providing IPv6 connectivity to end-user or downstream.

Presented at: LACNIC 33 y 1/3 (20/08/2020)

Presented at: LACNIC35 (11/05/2021)