LACNIC · Vigilancia de RIR
Consulta aquí el historial de cada propuesta: qué cambió, por qué fue relevante, quién defendió cada postura, cómo evolucionaron las posiciones, qué se decidió y dónde persisten las lagunas en la evidencia.
Hechos con fuentes
¿Quiénes marcaron realmente el debate?
Análisis de BTW
LAC-2017-5 pasó de su introducción registrada el 25 de abril de 2017 a una decisión de aceptación el 16 de agosto de 2017. El expediente también registra dos versiones, ambas fechadas el 25 de abril de 2017 y marcadas como “Implemented”, normalizado como “accepted”. Sin los textos de esas versiones, no puede determinarse qué cambió sustantivamente entre ellas ni qué derechos, obligaciones o facultades fueron modificados.
Los hechos suministrados no permiten identificar el contenido real del debate. No hay mensajes, participantes de discusión, posturas, transiciones ni argumentos minoritarios o no resueltos. Solo puede afirmarse que existió una propuesta que llegó a ser aceptada; no puede reconstruirse qué cuestiones sustantivas, incentivos o desacuerdos condujeron al resultado.
La decisión está documentada: la política fue aceptada el 16 de agosto de 2017. La discusión no está documentada en el conjunto suministrado: hay cero mensajes, cero participantes de discusión, cero participantes con postura y cero transiciones. Por ello, la aceptación acredita un resultado procedimental, pero no demuestra por sí sola consenso comunitario amplio ni permite conocer la justificación o el umbral aplicado.
No es posible interpretar la concentración de participación. Las cuotas top-1, top-5 y top-10, el HHI, el número efectivo de participantes y los núcleos del 50 % y 80 % son cero porque no existen mensajes de discusión. Estos valores no indican una deliberación equilibrada o desconcentrada. La única participación contabilizada corresponde a un actor formal, cuya identidad y función no fueron suministradas.
El único punto de cierre verificable es la decisión formal de aceptación del 16 de agosto de 2017. No hay evidencia para identificar quién controló ese punto, qué criterios se aplicaron, si hubo votación o determinación de consenso, ni cómo las versiones registradas llegaron a la decisión. En consecuencia, puede localizarse el chokepoint procedimental, pero no atribuirse su control o influencia sustantiva.
Circumstances permitting extension of the resource revocation period · The proposed rule changes from allowing an extension when revocation involves essential strategic infrastructure and an extraordinary situation requires it to allowing an extension either for essential strategic infrastructure or for exceptional situations, with natural disasters and political instability given as examples.
Where the revocation of resources involves essential strategic infrastructure needed for operating the Internet in our region, the LACNIC Board of Directors may extend the resource revocation period should an extraordinary situation so require.Hechos con fuentes ↗
In those cases where the revocation of resources involves essential strategic infrastructure that is necessary for operating the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extraordinary situation is detected.Hechos con fuentes ↗
Staff assessment and extension trigger · The new proposed rule expressly requires a prior Staff assessment after an extraordinary situation is detected; the old proposed rule contained no Staff-assessment requirement and instead stated that an extension could occur should an extraordinary situation so require.
Where the revocation of resources involves essential strategic infrastructure needed for operating the Internet in our region, the LACNIC Board of Directors may extend the resource revocation period should an extraordinary situation so require.Hechos con fuentes ↗
In those cases where the revocation of resources involves essential strategic infrastructure that is necessary for operating the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extraordinary situation is detected.Hechos con fuentes ↗
Rationale description of version-specific modifications · The new version adds a rationale statement that its modifications introduce additional possibilities for exceptional cases and specifications concerning a Staff Assessment; the old rationale ends without this version-specific statement.
This proposal seeks to provide the community with another tool that will ensure resource availability for essential, strategic infrastructure, so as to not run any risks in exceptional cases. Consequently, we propose that the power and ability to interpret which infrastructure can be considered essential and which cases are exceptional and merit invoking this possibility lie with the LACNIC Board of Directors.Hechos con fuentes ↗
The modifications to version 2 of the proposal add additional possibilities to take into account exceptional cases and introduce specifications regarding a Staff Assessment.Hechos con fuentes ↗
Presented-at metadata · The presentation metadata changes from an unspecified dash to “LACNIC 27 (22/05/2017).”
Debate público
4 Mensajes de discusión · 4 Entidades
Hechos con fuentes ↗Último intento de investigación: 18 sept 2026
Identidad verificada: 25 sept 2026
Nicolas Antoniellolacnic.net
Nicolás Antoniello - Version [1]politicas.lacnic.net
Nicolas Antoniello co-Chairs of Public Policy Forum - LACNICmail.lacnic.net
Perfiles públicos verificados
Primera postura explícita: Propone alternativa → Última postura explícita: Propone alternativa · Cambios de postura: 0
Coherencia del punto de vista: Coherente
The substantive comparisons show consistent concern for reliable registry records, meaningful community deliberation and the boundary between registration policy and operational policing. Two real changes are explained: moving from a formal GIR proposal to wider exploratory discussion, and from an inbound-only transfer proposal to a bidirectional IPv4 proposal. Joint moderator reports do not establish personal votes, and isolated comments remain insufficient for a longitudinal finding.
Management of Returned Internet Resources
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The joint co-chair notice reports board ratification of the returned-resources proposal. It does not establish Nicolas's personal position or a sequence of such positions.
Condiciones: A reported board decision is distinguished from the messenger's individual vote.
The proposal was ratified and has entered the implementation stage.
Creation of an IPv4 reserve exclusively for IPv6 deployment
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The co-chair notice reports non-ratification of the IPv6-deployment reserve and the board's participation and implementation concerns. Those institutional reasons are not personal opposition by the sender.
Condiciones: The technical and participation statements are historical reported reasons, not independent verification of current routing behavior or registry capabilities. · The different outcomes for two proposals in one notice do not establish inconsistent personal treatment.
The proposal was not ratified by LACNIC?s board and it has returned to the Policy List.
Modification to the text describing ASN distribution requirements
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The jointly signed status summary places the ASN-requirements proposal under board analysis. Summarizing proposed changes is not authoring or endorsing them, and no personal vote is supplied.
Condiciones: A mistaken heading in the English summary must not be used to infer a new personal position.
Proposals on analysis by the board LAC-2014-2: "Modification to the text describing ASN distribution requirements".
Update to the Policy Development Process
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The January status report and May report of community approval describe successive procedural stages. They do not establish that Nicolas personally supported or changed his position on the PDP update.
Condiciones: The reports are jointly signed by the moderators. · Community approval and subsequent procedural reporting are not the same as a personal vote.
Proposals in discussion: LAC-2014-3: "Update to the Policy Development Process".
The proposal was approved by LACNIC community.
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The May joint report that the proposal returned to discussion is followed in September by explicit personal support based on keeping transfer records accurate. The earlier report is not a personal opposing position, so this is not evidence of a reversal.
Condiciones: The May language versions disagree on favorable votes and abstentions; the disputed figures are not treated as authoritative. · The detailed transfer provisions quoted in September are existing text being explained, not a new list of conditions authored by the sender. · Only the September contribution supplies an explicit personal vote.
thus the proposal returns to the discussion list.
Por todo ello, en este caso yo estoy a favor de esta propuesta
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The joint moderator report describes broad community interest in inter-RIR transfers and continued discussion of this particular proposal. It supplies no individual vote from Nicolas.
Condiciones: Community-level support must not be reassigned to each person signing a procedural report.
while the majority of the community agrees that there should be a policy of Inter-RIR transfer, it shall continue the discussion.
Settling IPv4-IPv6 connectivity disputes when only one of the protocols is supported
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author opposes the proposed connectivity-dispute mechanism because he doubts both the RIR's role and its ability to compel technical choices. One message establishes this scoped objection, not persistence or reversal over time.
Condiciones: Acknowledging a good intention is not support for the proposal as written. · The mandate and enforcement assessment is the author's reasoning.
No estoy a favor de esta pol?tica tal cual est? planteada.
dificilmente Lacnic pueda "obligar" a alguien a adoptar ciertas medidas
Modify the size of initial IPv6 allocations
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author asks that internal delegation by noncommercial organizations be considered when assessing IPv6 utilization requirements. This single contribution identifies an operational case and suggests examination, without establishing a final vote or longitudinal consistency.
Condiciones: The Uruguay university example is the author's account. · An expectation of less frequent IPv6 reassignment is a forecast, not a demonstrated outcome.
Tal vez debemos tener en cuenta esta situaci?n y analizar el nivel porcentual de exigencia de argumentaci?n de uso de las direcciones adapt?ndonos a estos casos que antes no hab?amos considerado.
One-way interregional transfers to LACNIC
Evaluación: Coherente · The April questions about source regions, contracts and reciprocity develop into explicit support for inbound transfer registration. Throughout, the author distinguishes ethical discomfort with transfers from the practical need to record transactions that occur. Those two views are not contradictory.
Condiciones: The proposed inter-RIR workflow and recollection of ARIN discussions are questions and attributed understandings, not verified legal or procedural conclusions. · Supporting accurate registration does not imply approval of every commercial transfer.
mantener un registro confiable por parte del RIR
deber?amos aclarar bien ese punto con ARIN
a fin de mantener los registros fiables tenemos que atender dicha realidad.
apoyo enf?ticamente esta pol?tica LAC-2017-2.
Modify the minimum size of IPv4 assignments to Internet Service Providers
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author requests differences between the two IPv4-size proposals, then expresses tentative agreement in principle while reserving a choice until exact changes are explained. These messages do not establish a final vote or a reversal.
Condiciones: A preference for merging proposals is a process suggestion, not a decision on their exact substantive wording.
hagan alguna aclaraci?n ya que al menos a mi me parecen similares
poder definirme por una de las propuestas o por ninguna.
Modify the minimum size of initial allocations to ISPs
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The same comparative discussion asks for each proposal's exact changes and objective before choosing either or neither. Tentative agreement with the direction does not establish endorsement of this particular text.
Condiciones: The two quoted proposal summaries are context for the question, not separately authored positions by Nicolas.
por lo menos el t?tulo es pr?cticamente el mismo
me gustar?a conocer a fondo las diferencias explicadas por los autores.
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author proposes staff technical evaluation of essential resources followed by board ratification, with exceptional board discretion. This is a specific alternative division of responsibilities, but there is no second substantive contribution for comparison.
Condiciones: Calling the proposal interesting does not establish unconditional support. · The asserted limits of the board's technical role are the author's view.
la evaluaci?n deber?a ser del staff de LACNIC el cual elevar?a una propuesta al directorio
Reducing the last-call-for-comments period in LACNIC's Policy Development Process.
Evaluación: Coherente · Across the June discussion the author defends time for normal community review, rejects a period below thirty days and points urgent cases toward the expedited process. A possible thirty-day compromise does not retract that position or amount to firm support for shortening the period.
Condiciones: He acknowledges arbitrariness in the exact number of days. · Rare use of a review stage is not accepted by the author as proof that the stage is unnecessary. · His historical timing description is not a statement of today's PDP rules.
no creo que dicho per?odo deba ser menor a 30 d?as.
es una garant?a adicional a la comunidad
para esos casos "urgentes" est? el proceso expeditivo.
no veo positivo que se reduzca a menos de 30 d?as.
Si se quiere llevar a 30 dias
Proposal to create a Global Internet Registry (GIR)
Evaluación: Coherente · The author initially advocates a virtual global registry operated by the existing RIRs, defends its administrative purpose, and later proposes withdrawing the formal proposal while continuing wider discussion and seeking a clearer process. That is an explicit change in procedural strategy and urgency, while the possible value of a GIR remains under consideration.
Condiciones: The June withdrawal proposal must not be hidden or treated as continued pursuit of the same formal draft. · The later acknowledgement that a GIR may not yet be necessary qualifies urgency without becoming opposition to examining the concept. · Reports of circulation to other bodies are not evidence of their acceptance. · ICP-2 interpretations, cost expectations, operator recollections and future off-Earth scenarios remain the author's historical arguments, not independently verified present facts.
no puede ser expeditivo en este caso porque no tendr?a sentido ?apresurar? una pol?tica global de este tipo
Nuevamente todo est? abierto a discusi?n.
un registro virtual operado por los mismos 5 RIRs
los registros y el tratamiento de los recursos reflejen la realidad.
No son t?cnicas. Son administrativas, pol?ticas y econ?micas
El feedback de la idea es, como mencionas, lo m?s importante
Puede que hoy no sea a?n tan necesario disponer de un GIR
lo mejor es bajarla como propuesta y eventualmente platear la discusi?n en las listas de los diferentes RIR
Evaluación: Coherente · Support in principle develops into a repeated request for version-neutral wording about continuing discussion or abandoning a proposal. The author separately accepts restarting the discussion period. The shift from support to alternative-wording labels reflects specification of the same position, not withdrawal.
Condiciones: The final message calls the timing issue secondary to his wording suggestion; it does not oppose resetting the period. · No adoption of the proposed wording is established.
En principio estoy de acuerdo con la modificacion que se propone.
De esa forma queda libre lo de las versiones.
Y luego habr?a que agregar en todo caso lo del reset de los meses.
estoy de acuerdo en que se reinicie
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author supports a transfer policy for registry accuracy, but requests an IPv4-only, bidirectional proposal. This single contribution establishes those conditions; earlier transfer proposals provide cross-policy context rather than another vote on this same proposal.
Condiciones: Deferring IPv6 transfer rules is not permanent opposition to them. · The description of other RIR practices is the author's historical assertion.
propongo que la propuesta sea sobre IPv4 estrictamente y por supuesto que trate las transferencias en forma bidireccional
Registration and validation of abuse contact
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author accepts the idea of registering an abuse contact with changed wording, while preferring best-practice guidance to binding operational abuse-handling rules. Partial agreement and rejection of an enforcement role concern different provisions, not opposing votes on the same provision.
Condiciones: This does not establish support for the entire proposal as written. · His mandate and capacity concerns are assessments, not legal determinations.
En principio estar?a de acuerdo con el primer punto de tu propuesta
un manual de BCPs m?s que en una pol?tica.
Evaluación: Coherente · A request for marked changes is followed by opposition to broad simplification and a defense of cumulative list-and-forum consensus. Interest in selected individual elements does not withdraw opposition to the package or to reducing the forum's role without a demonstrated need.
Condiciones: The initial request for review material is not an earlier supporting vote. · The author's participation, historical-frequency and legitimacy claims are arguments, not verified statistics or proof of equal access.
un texto con control de cambios
por ahora creo que el proceso es el adecuado para nuestra regi?n.
no veo una urgencia para nuestra regi?n, que amerite quitarle importancia al lugar que ocupa el foro en el proceso.
Clarifications of Sub-Assignments
Evaluación: No hay pruebas suficientes para evaluar la coherencia · The author tentatively prefers the option allowing a data centre to assign multiple addresses to customers. This one clarification does not establish a sequence of positions or endorsement of every sub-assignment clause.
Condiciones: References to other participants' clarifications are context, not additional positions independently expressed by Nicolas.
me inclino m?s por la opci?n 2 que menciona Jordi, que permite asignar direcciones a los clientes (y no solo una).
Update to the Policy on IPv4 Assignments to End Users
Evaluación: Coherente · The May request to clarify a scenario is followed in November by support for advancing the proposal because the author considers material objections addressed. Seeking clarification and later accepting the discussion's outcome are compatible; the earlier message did not oppose the proposal.
Condiciones: The later statement describes his assessment of resolved objections, not a formal declaration of community consensus.
creo que Jordi debe aclararlo nuevamente en todo caso.
no veo en este momento, en lo personal, nada que impida avanzar con esta propuesta.
Trigger 2.3.2.18 when a justified request larger than /22 is received which can not be allocated from any remaining pool of addresses at LACNIC. · One-way interregional transfers to LACNIC
Evaluación: Coherente · Personal support for registering intra-regional transfers and later support for inbound inter-RIR transfers share the same reason: the registry should reflect actual resource use. The earlier moderator report of a failed forum outcome is not personal opposition.
Condiciones: Intra-regional and interregional mechanisms have different procedural requirements.
los registros de LACNIC contin?en siendo vigentes y manteni?ndose actualizados.
confianza y fiabilidad en los registros.
One-way interregional transfers to LACNIC · Inter-RIR Transfer Policy
Evaluación: Coherente · The move from supporting inbound-only transfers in 2017 to requesting bidirectional IPv4 transfers in 2018 is an acknowledged design change. The author explicitly connects it to objections encountered by the earlier proposal, while retaining registry accuracy as his objective.
Condiciones: This is not an unchanged preference about directionality; it is an explained adaptation. · His account of why the earlier proposal was discarded remains attributed to him.
apoyo enf?ticamente esta pol?tica LAC-2017-2.
trate las transferencias en forma bidireccional ya que ese fue uno de los argumentos que se manejaron cuando se descart? la propuesta de transferencias unidireccionales anterior.
Settling IPv4-IPv6 connectivity disputes when only one of the protocols is supported · Registration and validation of abuse contact
Evaluación: Coherente · The connectivity-dispute objection and the abuse-handling alternative both distinguish registration responsibilities from compelling particular network operations. Accepting contact information while preferring guidance for operational behavior does not contradict the earlier boundary concern.
Condiciones: The comparison describes the author's view of the RIR role, not an authoritative definition of that role.
menos cuando se tratan de soluciones t?cnicas
no creo que LACNIC deba tener el rol de polic?a de Internet regional.
Reducing the last-call-for-comments period in LACNIC's Policy Development Process. · Simplification of the PDP
Evaluación: Coherente · Opposition to shortening ordinary last call and opposition to broad PDP simplification share a concern for deliberative safeguards and an existing expedited exception. Neither contribution treats faster processing alone as sufficient justification.
Condiciones: The comparison does not imply opposition to every procedural improvement.
para esos casos "urgentes" est? el proceso expeditivo.
apurar estos procesos o simplificarlos no siempre los vuelve m?s leg?timos
Simplification of the PDP · Minor revision to the PDP
Evaluación: Coherente · Rejecting a broad PDP overhaul is compatible with later supporting a narrower amendment using clearer, version-neutral wording. The later proposal preserves continued discussion and a reset period rather than establishing a general preference for removing deliberative stages.
Condiciones: The author had expressly left room for considering useful individual changes in the broader discussion.
algunas cosas de las que propones son muy interesantes
De esa forma queda libre lo de las versiones.
Modify the minimum size of IPv4 assignments to Internet Service Providers · Modify the minimum size of initial allocations to ISPs
Evaluación: Coherente · Across both IPv4-size proposals the author requests comparable exact changes and reserves a choice. Tentative agreement with the general direction is compatible with asking the authors to distinguish or combine their proposals.
Condiciones: This comparison concerns his decision process; it does not establish a final substantive vote on either draft.
Consulto por las dos propuestas
poder definirme por una de las propuestas o por ninguna.
Proposal to create a Global Internet Registry (GIR) · Registration and validation of abuse contact
Evaluación: Coherente · Advocating a global administrative registration mechanism is compatible with rejecting an operational policing role for LACNIC. The GIR argument explicitly describes administrative, political and economic aims, while the abuse-policy objection concerns prescribing and supervising network conduct.
Condiciones: Support for changing registry administration is not support for every expansion of enforcement authority. · The comparison does not validate the proposed GIR's feasibility or recognition requirements.
No son t?cnicas. Son administrativas, pol?ticas y econ?micas
un rol de fiscalizaci?n para el cual no est? ni mandatado ni tendr?a la capacidad de hacerlo
[LACNIC/Politicas] Nueva propuesta LAC-2017-5 / Nova proposta LAC-2017-5 / New proposal LAC-2017-5
creo que la evaluaci?n deber?a ser del staff de LACNIC el cual elevar?a una propuesta al directorio
Hechos con fuentes ↗Mensajes de políticas: 54
Parcial
Primera captura: 21 oct 1999
Última captura: 12 oct 2026