Aller au contenu principal

LACNIC · Veille des RIR

Minor revision to the PDP

Commencez ici pour consulter l’historique, proposition par proposition : ce qui a changé, pourquoi cela comptait, qui a défendu quoi, comment les positions ont évolué, ce qui a été décidé et quelles lacunes subsistent dans les preuves.

Faits sourcés

Identifiant
LAC-2018-12
RIR
LACNIC
Statut officiel
Implemented
Statut normalisé
Acceptée
Introduction
14 sept. 2018
Dernière mise à jour des sources
4 oct. 2026
Couverture
Partielle

Qui a réellement façonné le débat ?

10Total des participants
10Contributeurs à la discussion
1Acteurs formels
15Messages de discussion
6,8Entités effectives
66,7 %Part des cinq premiers
3Personnes couvrant 50 %
7Personnes couvrant 80 %

Évolution de la politique

2
Acceptée · Implemented
14 sept. 2018
Faits sourcés ↗

Rationale for the proposed modification · The new version adds that allowing discussion to continue without an artificial revision would also avoid staff overhead associated with translating such a revision.

Chair and author options after consensus is not reached · The proposed text is reframed from choosing whether to publish a new version, maintain the current version, or abandon the proposal to choosing whether to continue discussion using either the same or a new version, or abandon it. The restart requirement is correspondingly expanded: the 8-week discussion period restarts whenever discussion continues, rather than only when a new version is submitted.

Reference and presentation information · The RIPE reference title is shortened from “Policy Development Process in RIPE” to “PDP in RIPE,” and the presentation field changes from a dash to “LACNIC 30 (24/09/2018).”

Chronologie du débat

  1. Présentation

    Présentation

    Faits sourcés ↗
  2. Version officielle

    1

    Acceptée · Implemented

    Faits sourcés ↗
  3. Version officielle

    2

    Acceptée · Implemented

    Faits sourcés ↗
  4. Débat public

    [LACNIC/Politicas] Nueva propuesta LAC-2018-12 / Nova proposta LAC-2018-12 / New proposal LAC-2018-12

    10 Messages de discussion · 7 Entités

    Faits sourcés ↗
  5. Débat public

    [LACNIC/Politicas] Últimos Comentarios propuesta LAC 2018-12 v2// Ultimos comentarios proposta LAC 2018-12 v2 // Last Comments for Proposal LAC 2018-12 v2

    2 Messages de discussion · 2 Entités

    Faits sourcés ↗
  6. Décision officielle

    accepted

    accepted

    Faits sourcés ↗

Entités

Actualité: Périmé · Dernière actualisation: · La dernière actualisation a échoué. Le dernier résultat obtenu avec succès est affiché.
  1. Messages de discussion4
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteSoutien
    Dernière position expliciteProposition alternative
    Changements de position2
    Cohérence du point de vueCohérent
    Autres politiques25
    Actualité: Périmé · Dernière actualisation: · La dernière actualisation a échoué. Le dernier résultat obtenu avec succès est affiché.

    Dernière tentative de recherche: 18 sept. 2026

    Identité vérifiée: 25 sept. 2026

    · Historique
    Nicolas Antoniello
    lacnic.net
    · Historique
    Nicolás Antoniello - Version [1]
    politicas.lacnic.net
    LACNIC · Historique
    Nicolas Antoniello co-Chairs of Public Policy Forum - LACNIC
    mail.lacnic.net
    Messages de discussion
    4
    Première activité
    14 sept. 2018
    Dernière activité
    14 sept. 2018
    Première position explicite
    Soutien
    Dernière position explicite
    Proposition alternative
    Changements de position
    2
    Cohérence du point de vue
    Cohérent
    Autres politiques
    25

    Première position explicite: Soutien → Dernière position explicite: Proposition alternative · Changements de position: 2

    Cohérence du point de vue: Cohérent

    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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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.

    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.

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Inter-RIR Transfers

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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.

    Addenda − Resource revocation

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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.

    Évaluation: Cohérent · 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.

    Réserves: 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)

    Évaluation: Cohérent · 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.

    Réserves: 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

    Minor revision to the PDP

    Évaluation: Cohérent · 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.

    Réserves: 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

    Inter-RIR Transfer Policy

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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.

    Simplification of the PDP

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Éléments insuffisants pour évaluer la cohérence · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    Évaluation: Cohérent · 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.

    Réserves: 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

    1. 14 sept. 2018 · Soutien

      [LACNIC/Politicas] Nueva propuesta LAC-2018-12 / Nova proposta LAC-2018-12 / New proposal LAC-2018-12

      En principio estoy de acuerdo con la modificacion que se propone.

      Faits sourcés ↗
    2. 14 sept. 2018 · Soutien avec modifications

      [LACNIC/Politicas] Nueva propuesta LAC-2018-12 / Nova proposta LAC-2018-12 / New proposal LAC-2018-12

      ?decidir con el autor si desea(n) continuar la discusi?n en el foro o abandonar la propuesta?. … Tambien, como dice Ricardo habr?a que resetrar el tiempo de 8 semanas.

      Faits sourcés ↗
    3. 14 sept. 2018 · Proposition alternative

      [LACNIC/Politicas] Nueva propuesta LAC-2018-12 / Nova proposta LAC-2018-12 / New proposal LAC-2018-12

      Vuelvo a plantearles una redacci?n alternativa para el texto que ser?a la siguiente: … ?decidir con el autor si desea(n) continuar la discusi?n en el foro o abandonar la propuesta?. … Y luego habr?a que agregar en todo caso lo del reset de los meses.

      Faits sourcés ↗
    4. 14 sept. 2018 · Proposition alternative

      [LACNIC/Politicas] Nueva propuesta LAC-2018-12 / Nova proposta LAC-2018-12 / New proposal LAC-2018-12

      lo que yo digo no es sobre el tema del plazo o del reset del plazo (en lo que estoy de acuerdo en que se reinicie y que es un tanto irrelevante) … y por eso te propon?a la redactarlo as?: *?decidir con el autor si desea(n) continuar la discusi?n en el foro o abandonar la propuesta?*.

      Faits sourcés ↗

    Messages de politique: 54

  2. Paola Perez · Identité non résolue
    Messages de discussion3
    Première activité14 déc. 2018
    Dernière activité29 déc. 2018
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques17
  3. Eduardo Cota · Identité non résolue
    Messages de discussion1
    Première activité14 déc. 2018
    Dernière activité14 déc. 2018
    Première position expliciteSoutien
    Dernière position expliciteSoutien
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques0
  4. Messages de discussion1
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteSoutien avec modifications
    Dernière position expliciteSoutien avec modifications
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques39
  5. Juan Alejo Peirano · Identité non résolue
    Messages de discussion1
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteSoutien avec modifications
    Dernière position expliciteSoutien avec modifications
    Changements de position0
    Cohérence du point de vueCohérent
    Autres politiques23
  6. Messages de discussion1
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteSoutien avec modifications
    Dernière position expliciteSoutien avec modifications
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques25
  7. Alejandro Guzman · Identité non résolue
    Messages de discussion1
    Première activité16 sept. 2018
    Dernière activité16 sept. 2018
    Première position expliciteSoutien
    Dernière position expliciteSoutien
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques9
  8. Messages de discussion1
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteOpposition
    Dernière position expliciteOpposition
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques3
  9. Ariel Weher · Identité non résolue
    Messages de discussion1
    Première activité20 déc. 2018
    Dernière activité20 déc. 2018
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques5
  10. Edmundo Cázarez · Identité non résolue
    Messages de discussion1
    Première activité14 sept. 2018
    Dernière activité14 sept. 2018
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques6

Sources et couverture

Archives des discussions publiques

  • lacnic-politicas
    Première capture
    21 oct. 1999
    Dernière capture
    2 oct. 2026
    Dernière actualisation
    13 août 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    4 856
    Lacunes connues
    26
  • www.lacnic.net
  • lacnic-anuncios
    Première capture
    13 août 2026
    Dernière capture
    23 sept. 2026
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    2 038
    Lacunes connues
    0
  • lacnic-ietf-lac
    Première capture
    30 mai 2013
    Dernière capture
    30 déc. 2015
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    1 133
    Lacunes connues
    0
  • lacnic-infofrida
    Première capture
    14 août 2006
    Dernière capture
    13 sept. 2011
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    287
    Lacunes connues
    0
  • lacnic-iot
    Première capture
    6 oct. 2015
    Dernière capture
    11 juil. 2017
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    373
    Lacunes connues
    0
  • lacnic-lacnog
    Première capture
    1 août 2026
    Dernière capture
    2 oct. 2026
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    5 304
    Lacunes connues
    0
  • lacnic-lactf
    Première capture
    13 avr. 2004
    Dernière capture
    29 déc. 2005
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    2 105
    Lacunes connues
    0
  • lacnic-seguridad
    Première capture
    26 janv. 2006
    Dernière capture
    28 déc. 2007
    Dernière actualisation
    5 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    1 356
    Lacunes connues
    0

Couverture

Partielle
Première capture: 21 oct. 1999
Dernière capture: 5 oct. 2026

Actualité

Actualité: Périmé · Dernière actualisation: · La dernière actualisation a échoué. Le dernier résultat obtenu avec succès est affiché.

Lacunes connues

  • politicas.lacnic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • www.lacnic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-politicas: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • www.lacnic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-anuncios: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-ietf-lac: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-infofrida: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-iot: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-lacnog: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-lactf: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • lacnic-seguridad: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.