LACNIC · RIR Watchdog
Add IPv6 operational as a requirement for IPv4 transfers
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- LAC-2020-1
- RIR
- LACNIC
- Official status
- Abandoned
- Normalized status
- Abandoned
- Introduced
- Mar 31, 2021
- Last source update
- Oct 13, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
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.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
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.
Source facts −
In the case the receiver provides a written statement from its upstream that IPv6 connectivity is unavailable, the IPv6 requirement may be waived.Source facts ↗
Source facts +
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.Source facts ↗
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.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.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.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Debate timeline
Public discussion
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
8 Discussion messages · 1 Entities
Source facts ↗
Entities
- Discussion messages8First activityApr 11, 2021Last activityApr 14, 2021First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyConsistentOther policies5Freshness: Stale
Last research attempt: Sep 27, 2026
Identity verified: Sep 27, 2026
LACNIC · Historical CEO of LACNIC between 2002 and 2014.
www.internetsociety.orgInternet Society · Historical Raúl Echeberría will join the organization in the new position of Vice President, Global Engagement.
www.internetsociety.orgVerified public profiles
- Discussion messages
- 8
- First activity
- Apr 11, 2021
- Last activity
- Apr 14, 2021
- First explicit stance
- Oppose
- Latest explicit stance
- Oppose
- Stance changes
- 0
- Viewpoint consistency
- Consistent
- Other policies
- 5
First explicit stance: Oppose → Latest explicit stance: Oppose · Stance changes: 0
Viewpoint consistency: Consistent
Across these 23 messages on six proposals, from June 2020 to April 2021, the participant consistently tests new requirements against a demonstrated problem, community self-management and the RIR's number-resource mission. Opposition to particular procedures or an IPv6 transfer requirement coexists with support for targeted process reform and IPv6 deployment. No unexplained reversal is evident in this set; this is not a finding about the participant's entire history or the final versions of every proposal.
Assessment: Consistent · On the PDP chair election procedure, the participant maintains opposition to the more complex proposal while accepting that prior mailing-list participation could be required through a narrow amendment. That exception qualifies the objection; it does not reverse it.
Conditions: The preferred approach preserves community self-management and requires a clear reason to replace the existing procedure. · The evidence concerns these June 2020 exchanges, not approval or rejection of every later version.
Porque el mecanismo actual es mucho m?s basado en la comunidad. Es la propia comunidad que se autogestiona.
Alcanzar?a con una propuesta que solamente agregue este punto espec?fico.
Como dije antes. Bueno y simple, doblemente bueno.
Acceptable Use Policy (AUP) for the Policy List
Assessment: Consistent · Opposition to a new policy-list acceptable-use policy rests on the view that existing tools can handle the incidents described. The participant leaves room for additional tools if an unresolved gap is demonstrated, rather than denying that incidents occurred.
Conditions: The assessment of existing remedies is the participant's stated view, not an independently established measure of their effectiveness. · The objection is to adding a general policy for the cited problems under the circumstances discussed.
Mi opini?n es que no se necesita una PUA, por lo cual ni siquiera debo comentar el punto 2.
Si en alg?n momento queda evidente que existen problemas que no se pueden resolver con las herramientas disponibles (por ej. el c?digo de conducta), tendr?a sentido desde mi punto de vista, buscar nuevas herramientas, pero no creo que sea el caso en este momento.
No se puede hacer una pol?tica general para resolver temas puntuales.
Assessment: Consistent · Support for making proposals working documents concerns a way to focus discussion and address repeated, unsupported proposals. It remains support for the problem and direction, with the choice of mechanism open; the participant explicitly treats effects on participation as speculative.
Conditions: A process change must preserve the freedom to propose and discuss ideas. · These messages do not establish that the proposed mechanism improves participation or endorse every clause.
Ser? esta u otra propuesta, eso ya lo veremos, pero el concepto es muy apropiado.
Como no lo conozco, lo ?nico que puedo hacer es especular.
La propuesta de Arturo es una opci?n. Si esa opci?n no es la mejor para algunos, hay que buscar otra, pero el problema hay que resolverlo.
Assessment: Consistent · The two early responses on improving the PDP welcome combining alternative approaches and including a broad range of views. They support collaborative process design, without resolving the details of a final proposal.
Conditions: Combining ideas is not equivalent to endorsing every provision of either proposal. · Only these two early contributions support this finding.
Tal vez deber?an trabajar en una combinaci?n de ambas propuestas.
Hagamos lo posible por incluir tantas visiones como sea posible.
Add IPv6 operational as a requirement for IPv4 transfers
Assessment: Consistent · The participant supports wider IPv6 deployment but repeatedly rejects making IPv6 operation a condition of IPv4 transfers. The dispute concerns the means, expected effect and proper scope of resource policy, not the IPv6 objective or a categorical rejection of operational requirements.
Conditions: The participant accepts that policies can impose requirements and affect markets, while disputing the appropriate trade-off in this case. · Training, coordination and operator engagement are preferred approaches in these messages; their comparative effectiveness is not proven here.
comparto el esp?ritu que fundamenta la propuesta pero NO la apoyo
No apoyo esta pol?tica porque no me parece el camino adecuado
La discusi?n se basa en donde colocar el punto de equilibrio (o el trade off) y cuales requerimientos apuntan al uso eficiente del recurso que se asigna y cuales implican otro tipo de obligaciones.
Non-Competition Between Proposals
Assessment: Consistent · Opposition to non-competition between proposals remains consistent with treating policy-list contributions as freely usable community work. The participant distinguishes those contributions from separately published research whose author may retain intellectual-property rights; that distinction is not a reversal on ownership of policy proposals.
Conditions: Attribution remains appropriate even where policy contributions are freely reusable. · The distinction addresses policy contributions and separately published research, not every possible intellectual-property dispute.
Estoy totalmente en contra de esta propuesta.
Creo que las contribuciones que se hacen en esta lista en relaci?n a pol?ticas de manejo de recursos de numeraci?n de Internet, deben ser p?blicas y de uso libre de la comunidad.
El autor puede publicar el art?culo en otro lado, aplicar las reglas de propiedad intelectual que le parezcan m?s conveniente y luego hacer una referencia a esa publicaci?n desde la propuesta de pol?tica.
Acceptable Use Policy (AUP) for the Policy List · Adoption of policy proposals for discussion at the Public Policy Forum, Discussion List and call for consensus as working documents.
Assessment: Consistent · Rejecting a new acceptable-use policy while supporting discussion-process reform is a qualified distinction: the participant sees existing remedies as adequate in the former case and an unresolved agenda problem in the latter. The shared criterion is a concrete need for change, not opposition to all procedures.
Conditions: The existence and scale of each problem are the participant's assessments in these exchanges. · Support for an agenda remedy remains open to alternatives and does not establish its effect on participation.
Si en alg?n momento queda evidente que existen problemas que no se pueden resolver con las herramientas disponibles (por ej. el c?digo de conducta), tendr?a sentido desde mi punto de vista, buscar nuevas herramientas, pero no creo que sea el caso en este momento.
La propuesta de Arturo es una opci?n. Si esa opci?n no es la mejor para algunos, hay que buscar otra, pero el problema hay que resolverlo.
Modification of the PDP to improve the quality of proposals and increase participation in the policy development process · Non-Competition Between Proposals
Assessment: Consistent · Encouraging authors to combine PDP ideas fits the later rejection of exclusive control over policy-list contributions. Both positions favor collective policy development, while leaving room for attribution and rights in separately published research.
Conditions: This comparison does not treat every form of intellectual property as incompatible with open participation. · It describes the positions in the cited exchanges, not a universal rule attributed to the participant.
Tal vez deber?an trabajar en una combinaci?n de ambas propuestas.
Hagamos lo posible por incluir tantas visiones como sea posible.
Creo que las contribuciones que se hacen en esta lista en relaci?n a pol?ticas de manejo de recursos de numeraci?n de Internet, deben ser p?blicas y de uso libre de la comunidad.
- Apr 11, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
comparto el esp?ritu que fundamenta la propuesta pero NO la apoyo … no apoyo que este requerimiento se incluya en la pol?tica de transferencia tal como se propone.
Source facts ↗ - Apr 12, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
N?O apoio esta proposta. … Mas acredito que n?o ? papel da pol?tica for?ar o mercado
Source facts ↗ - Apr 12, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
esta propuesta, m?s all? que yo no la comparto, … No creo que solo cambiar las pol?ticas tenga un efecto en la realidad como el que se busca.
Source facts ↗ - Apr 12, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
est? desde mi punto de vista, m?s all? del "trade off" aceptable. … No querramos forzar la implementaci?n de buenas pr?cticas operativas a trav?s de las pol?ticas.
Source facts ↗ - Apr 12, 2021 · Procedural or neutral
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
nuestros desacuerdos han quedado clar?simos.
Source facts ↗ - Apr 12, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
No apoyo esta pol?tica porque no me parece el camino adecuado … Tu y yo estamos de acuerdo en lo importante de un despliegue m?s r?pido de IPv6.
Source facts ↗ - Apr 14, 2021 · Oppose
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
la discrepancia es con el punto central de tu propuesta … impondr?a requerimientos de operaci?n que van m?s all? de lo que debe hacer una pol?tica.
Source facts ↗ - Apr 14, 2021 · Procedural or neutral
[LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1
Todas las objeciones son v?lidas. Es la base del funcionamiento de este tipo de foros.
Source facts ↗
Per-policy stance timelines:LAC-2018-13 · Oppose · ConsistentLAC-2019-7 · Oppose · ConsistentLAC-2020-1 · Oppose · ConsistentLAC-2020-5 · Support with changes · ConsistentLAC-2020-7 · Propose alternative · ConsistentLAC-2021-2 · Oppose · ConsistentTotal policy messages: 23
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
Sources and coverage
Official policy sources
Public discussion archives
- lacnic-politicas
- Earliest captured
- Oct 21, 1999
- Latest captured
- Oct 12, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,630
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,169
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,133
- Known gaps
- 0
- lacnic-infofrida
- Earliest captured
- Aug 14, 2006
- Latest captured
- Sep 13, 2011
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 292
- Known gaps
- 0
- lacnic-iot
- Earliest captured
- Oct 6, 2015
- Latest captured
- Jul 11, 2017
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,511
- Known gaps
- 3
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,267
- Known gaps
- 0
- lacnic-seguridad
- Earliest captured
- Jan 26, 2006
- Latest captured
- Dec 28, 2007
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 14, 2026
Freshness
Known gaps
- politicas.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-politicas: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-anuncios: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-ietf-lac: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-infofrida: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-iot: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-lacnog: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-lactf: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-seguridad: Source coverage is incomplete. · The source boundary has not yet been reached.
