Skip to main content

LACNIC · RIR Watchdog

Inter-RIR Transfer Policy

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-2018-14
RIR
LACNIC
Official status
Abandoned
Normalized status
Abandoned
Introduced
Oct 30, 2018
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

9Total participants
6Discussion contributors
3Formal actors
8Discussion messages
5.3Effective participants
87.5%Top-five discussion share
2People covering 50%
5People covering 80%

BTW Analysis

BTW Analysis

What changed

The recorded lifecycle moved from introduction on 30 October 2018, through two version labels—both dated 30 October 2018 and marked abandoned—to a final recorded decision of abandonment on 13 May 2019. The supplied facts do not establish any substantive change between versions 1 and 2, and no adopted policy change resulted from this proposal.

What the debate was really about

The subject of any substantive debate cannot be determined from the supplied evidence. There are no discussion messages, participant stance timelines, proposal texts, version differences, or documented arguments from which to identify the contested policy objectives, rights, implementation mechanisms, or distributional effects.

Decision vs debate

The decision outcome is clear: the proposal was abandoned on 13 May 2019. The discussion record is empty in the measured dataset: zero messages, zero discussion participants, zero active days, and no stance participants or transitions. The abandonment therefore cannot be attributed to support, opposition, persuasion, consensus failure, withdrawal, or any other discussion dynamic on the supplied facts.

Participation concentration

Message-based participation concentration is not meaningfully measurable because the corpus contains zero messages. The zero top-one, top-five, and top-ten shares, zero HHI, and zero effective participant count do not indicate broad, equal, or dispersed participation. Three formal actors are counted, but they are not identified and no message or stance activity is attributed to them.

Chokepoint analysis

The only observable outcome chokepoint is the process ending in abandonment rather than adoption. The supplied record does not identify who controlled that chokepoint, what procedural threshold applied, whether the proposal was withdrawn, whether support was insufficient, or whether another substantive or procedural mechanism caused termination. No linkage between the three formal actors, the absence of measured messages, and the final decision is established.

Uncertainties

  • The substantive text and differences between versions 1 and 2 are not supplied.
  • Both version records share the introduction date, leaving their actual sequence and timing unresolved beyond their labels.
  • The reason for abandonment and the identity and authority of the decision-maker are not supplied.
  • Zero recorded messages establish only the contents of this measured snapshot and do not prove that no meeting, private, off-list, or omitted discussion occurred.
  • The identities, roles, positions, and influence of the three formal actors are unknown.
  • There is no evidence of support, opposition, consensus assessment, withdrawal, replacement, procedural failure, or stance change.
  • The participation metrics are bound to the identified source revision and computation snapshot and do not establish that the historical record is complete.
  • The Doctrine package does not establish a complete official company position on the proposal's merits.

Policy evolution

2
Abandoned · Abandoned
Oct 30, 2018
Source facts ↗

Resource scope and policy structure · The old text proposed a separate inter-RIR transfer policy covering IPv4, IPv6, and ASNs. The new text instead revises the existing IPv4 transfer section, combines intra-RIR and inter-RIR IPv4 rules there, and omits the proposed IPv6 and ASN transfer provisions.

Legacy-resource restriction for inter-RIR transfers · The old text restricted outbound IPv4 and ASN transfers from LACNIC to legacy resources while allowing inbound transfers regardless of status. The new policy text permits an inter-RIR IPv4 transfer only when the resources are legacy whenever either organization belongs to another region, while expressly excluding intra-RIR transfers from that restriction.

Receiving-organization qualification · The old text required a recipient to justify need before LACNIC or the corresponding RIR depending on transfer direction. The new text specifies that a recipient within the LACNIC region must justify its IPv4 needs before LACNIC, while a recipient in another region is governed by the corresponding RIR's criteria, verifications, and requirements.

Legal documentation for transfers · The old text required both transferring and receiving entities to submit a copy of the supporting legal document to LACNIC for inter-RIR transfers. The new text requires both organizations to submit a signed copy to LACNIC only for intra-RIR transfers and provides that documentation for inter-RIR transfers will be agreed between the two RIRs.

Transfer-log contents · The old text required the existing log to record the transaction date, transferring and receiving entities, the corresponding RIR in each case, and other relevant resource data. The new text specifies the transferred addresses and, for inter-RIR transfers, the source and destination RIRs, while retaining the transaction date and participating organizations.

Transfer waiting periods and post-transfer eligibility · The old text imposed a two-year transfer prohibition on resources associated with LACNIC IPv6 allocations or assignments and a one-year retransfer prohibition on transferred blocks and sub-blocks. The new text removes the IPv6-specific two-year rule, retains a one-year prohibition on retransferring IPv4 addresses in full or in part, applies a one-year transfer prohibition to addresses from LACNIC allocations or assignments, and makes the originating organization ineligible for LACNIC IPv4 allocations or assignments for one year.

Debate timeline

  1. Public discussion

    [LACNIC/Politicas] New Proposal / Nueva Propuesta / Nova Proposta - LAC-2012-08

    5 Discussion messages · 4 Entities

    Source facts ↗
  2. Introduced

    Introduced

    Source facts ↗
  3. Official version

    1

    Abandoned · Abandoned

    Source facts ↗
  4. Official version

    2

    Abandoned · Abandoned

    Source facts ↗
  5. Public discussion

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

    3 Discussion messages · 2 Entities

    Source facts ↗
  6. Official decision

    abandoned

    abandoned

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages2
    First activityJul 25, 2012
    Last activityJul 30, 2012
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  2. Juan Alejo Peirano · Identity unresolved
    Discussion messages2
    First activityNov 1, 2018
    Last activityNov 1, 2018
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies23
  3. Scott Leibrand · Identity unresolved
    Discussion messages1
    First activityJul 24, 2012
    Last activityJul 24, 2012
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  4. Unknown · Identity unresolved
    Discussion messages1
    First activityJul 30, 2012
    Last activityJul 30, 2012
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  5. Discussion messages1
    First activityNov 1, 2018
    Last activityNov 1, 2018
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies24
  6. Unknown · Identity unresolved
    Discussion messages1
    First activityJul 25, 2012
    Last activityJul 25, 2012
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  7. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies33
  8. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies5
  9. 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 8, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,331
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,110
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 10, 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 10, 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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    373
    Known gaps
    0
  • lacnic-lacnog
    Earliest captured
    Aug 1, 2026
    Latest captured
    Oct 8, 2026
    Last refresh
    Oct 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,066
    Known gaps
    0
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 29, 2006
    Last refresh
    Oct 10, 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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,356
    Known gaps
    0

Coverage

Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 10, 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.