Skip to main content

LACNIC · RIR Watchdog

Addenda − Resource revocation

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-2017-5
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Apr 25, 2017
Last source update
Oct 14, 2026
Coverage
Partial

Who actually shaped the debate?

8Total participants
7Discussion contributors
1Formal actors
17Discussion messages
5.5Effective participants
88.2%Top-five discussion share
3People covering 50%
4People covering 80%

BTW Analysis

BTW Analysis

What changed

The policy was introduced on 25 April 2017, with versions 1 and 2 both recorded on that date as “Implemented” and normalized as accepted. A later decision on 16 August 2017 records the policy as accepted. The supplied evidence does not include the version texts, so no substantive change between versions can be identified.

What the debate was really about

The subject of any underlying debate cannot be determined from the supplied record. No messages, stance timelines, arguments, motivations, or policy text were provided. The evidence establishes an accepted policy lifecycle but not the substantive issue contested or the reasons for acceptance.

Decision vs debate

The decision outcome is clear: the policy was accepted on 16 August 2017 and its two recorded versions are marked implemented/accepted. Discussion evidence is absent: zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions were captured. Acceptance therefore must not be equated with demonstrated community agreement, documented persuasion, or an uncontested process.

Participation concentration

The extract records one formal actor and one total participant but no discussion activity. The zero top-message shares, zero HHI, zero effective participant count, and zero core counts arise from having no captured messages; they do not demonstrate broad, balanced, or unconcentrated participation. They also do not establish speaker domination because there were no messages over which dominance could be measured.

Chokepoint analysis

The only visible procedural chokepoint is the formal acceptance decision recorded on 16 August 2017. The single formal actor indicates a formal-process presence in this extract, but the evidence does not identify that actor, the decision mechanism, or whether substantive power was concentrated there. Without discussion records, voting or consensus evidence, decision rationale, and version text, no stronger institutional or substantive chokepoint finding is supported.

Uncertainties

  • The substantive text and differences between versions 1 and 2 are not supplied.
  • Versions 1 and 2 have identical recorded timestamps, leaving their intraday ordering and duration unknown.
  • No discussion messages, participant stances, minority arguments, or unresolved arguments are available.
  • No decision rationale, vote tally, consensus assessment, decision-maker identity, or implementation details are supplied.
  • The zero concentration metrics reflect the absence of captured messages and cannot establish either distributed participation or domination.
  • The record does not explain why both versions share the introduction date or how they connect procedurally to the later acceptance decision.
  • The Doctrine package does not establish a complete official company position on the policy's merits, legitimacy, or desirability.

Policy evolution

2
Accepted · Implemented
Apr 25, 2017
Source facts ↗

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.

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.

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.

Presented-at metadata · The presentation metadata changes from an unspecified dash to “LACNIC 27 (22/05/2017).”

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Accepted · Implemented

    Source facts ↗
  3. Official version

    2

    Accepted · Implemented

    Source facts ↗
  4. Public discussion

    [LACNIC/Politicas] Nueva propuesta LAC-2017-5 / Nova proposta LAC-2017-5 / New proposal LAC-2017-5

    4 Discussion messages · 4 Entities

    Source facts ↗
  5. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
  1. Gianina Pensky · Identity unresolved
    Discussion messages4
    First activityMay 2, 2017
    Last activityMay 10, 2017
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies23
  2. Juan Alejo Peirano · Identity unresolved
    Discussion messages4
    First activityMay 9, 2017
    Last activityJul 7, 2017
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies23
  3. Paola Perez · Identity unresolved
    Discussion messages3
    First activityMay 29, 2017
    Last activityAug 16, 2017
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies17
  4. Unknown · Public sources found; identity verification pending
    Discussion messages3
    First activityApr 25, 2017
    Last activityMay 24, 2017
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies20
  5. Discussion messages1
    First activityApr 26, 2017
    Last activityApr 26, 2017
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies25
  6. Discussion messages1
    First activityApr 26, 2017
    Last activityApr 26, 2017
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies27
    Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.

    Last research attempt: Sep 17, 2026

    Identity verified: Oct 14, 2026

    LACNIC · Historical
    Ricardo Patara (*) - Registration Service Manager.
    www.lacnic.net
    NIC.BR · Current
    Actualmente se desempeña como gerente de Recursos de Numeración de Internet en NIC.BR
    blog.lacnic.net

    Verified public profiles

    Discussion messages
    1
    First activity
    Apr 26, 2017
    Last activity
    Apr 26, 2017
    First explicit stance
    Oppose
    Latest explicit stance
    Oppose
    Stance changes
    0
    Viewpoint consistency
    No validated consistency assessment
    Other policies
    27

    First explicit stance: Oppose → Latest explicit stance: Oppose · Stance changes: 0

    Viewpoint consistency: No validated consistency assessment

    1. Apr 26, 2017 · Oppose

      [LACNIC/Politicas] Nueva propuesta LAC-2017-5 / Nova proposta LAC-2017-5 / New proposal LAC-2017-5

      no veo (desde mi humilde punto de vista), la necesidad de se incluir eso en el texto de pol?ticas.

      Source facts ↗

    Total policy messages: 69

  7. Andres Piazza · Identity unresolved
    Discussion messages1
    First activityApr 26, 2017
    Last activityApr 26, 2017
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies0
  8. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0

Sources and coverage

Official policy sources

Public discussion archives

  • lacnic-politicas
    Earliest captured
    Oct 21, 1999
    Latest captured
    Oct 14, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,687
    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,189
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 14, 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 14, 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 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    373
    Known gaps
    0
  • lacnic-lacnog
    Earliest captured
    Aug 1, 2026
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,555
    Known gaps
    3
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 29, 2006
    Last refresh
    Oct 14, 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 14, 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.