BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

LACNIC · RIR Watchdog

Authorize Recipients of Delegated Blocks to Sign ROAs

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-10
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Nov 23, 2021
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

1Total participants
UnknownDiscussion contributors
1Formal actors
UnknownDiscussion messages
UnknownEffective participants
UnknownTop-five discussion share
UnknownPeople covering 50%
UnknownPeople covering 80%

Policy evolution

2
Accepted · Implemented
Nov 23, 2021
Source facts ↗

Party identified as able to sign ROAs · The summary changes the identified signer from the receiving organization's technical contact to the recipient organization itself.

Source facts −
Once this policy is implemented, the technical contact of the organization receiving an IP prefix delegation from a provider will be able to sign the ROAs for said prefix for the duration of the delegation.
Source facts ↗
Source facts +
Una vez implementada la política, la Organización receptora de un bloque IP delegado por un proveedor será capaz de firmar los ROA para dicho prefijo mientras dure la delegación
Source facts ↗

ROA creation and management rights · The proposed text removes the receiving client's stated exclusive right, grants the recipient a right to create and manage ROAs, and removes the separate requirement that the receiving organization's technical contact manage them.

Source facts −Validated evidence is unavailable.
Source facts +
As long as the prefixes are registered in the WHOIS database, the recipient will have the right to create and manage the RPKI Route Origin Authorizations (ROAs) for said resources.
Source facts ↗

Reason for assignment registration related to routing security · The explicit reason requiring assignment registration to strengthen routing security and ensure proper RPKI implementation is removed from the proposed list.

Source facts −
o strengthen Internet routing security, ensuring the proper implementation of RPKI. Ad
Source facts ↗
Source facts +
To study IPv4 address allocation within the region. - To facilitate the geolocation of sub-assignments made by members in our region. Additional information
Source facts ↗

Presented-at event and date · The presentation metadata changes from “LACNIC35 (11/05/2021)” to “LACNIC 37 (04/05/2022).”

Source facts −
: LACNIC35 (11/05/202
Source facts ↗
Source facts +
at: LACNIC 37 (04/05/2
Source facts ↗

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗

  2. Official version

    1

    Accepted · Implemented

    Source facts ↗

  3. Official version

    2

    Accepted · Implemented

    Source facts ↗

  4. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Hernan Moguilevsky
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1

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,359
    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,115
    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,115
    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.