Skip to main content

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?

2Total participants
1Discussion contributors
1Formal actors
8Discussion messages
1Effective participants
100%Top-five discussion share
1People covering 50%
1People covering 80%

Policy evolution

2
Abandoned · Abandoned
Mar 31, 2021
Source facts ↗

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.

3
Abandoned · Abandoned
Mar 31, 2021
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.

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.

4
Abandoned · Abandoned
Mar 31, 2021
Source facts ↗

Policy text · Astra identified a substantive wording change in this retained policy section.

Policy text · Astra identified a substantive wording change in this retained policy section.

Policy text · Astra identified a substantive wording change in this retained policy section.

Policy text · Astra identified a substantive wording change in this retained policy section.

Policy text · Astra identified a substantive wording change in this retained policy section.

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Abandoned · Abandoned

    Source facts ↗
  3. Official version

    2

    Abandoned · Abandoned

    Source facts ↗
  4. Official version

    3

    Abandoned · Abandoned

    Source facts ↗
  5. Official version

    4

    Abandoned · Abandoned

    Source facts ↗
  6. Public discussion

    [LACNIC/Politicas] Nueva versión de la propuesta LAC-2020-1

    8 Discussion messages · 1 Entities

    Source facts ↗
  7. Official decision

    abandoned

    abandoned

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages8
    First activityApr 11, 2021
    Last activityApr 14, 2021
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies5
    Freshness: Stale

    Last research attempt: Sep 27, 2026

    Identity verified: Sep 27, 2026

    LACNIC · Historical
    CEO of LACNIC between 2002 and 2014.
    www.internetsociety.org
    Internet Society · Historical
    Raúl Echeberría will join the organization in the new position of Vice President, Global Engagement.
    www.internetsociety.org

    Verified 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.

    PDP Chair Election Procedure

    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.

    Adoption of policy proposals for discussion at the Public Policy Forum, Discussion List and call for consensus as working documents.

    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.

    Modification of the PDP to improve the quality of proposals and increase participation in the policy development process

    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.

    1. 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 ↗
    2. 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 ↗
    3. 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 ↗
    4. 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 ↗
    5. 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 ↗
    6. 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 ↗
    7. 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 ↗
    8. 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 ↗

    Total policy messages: 23

  2. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other 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

Freshness: Stale · Last refresh:

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.