BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

LACNIC · RIR Watchdog

Inclusion of ASN in the whois when available

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-2010-03
RIR
LACNIC
Official status
Consensus
Normalized status
Accepted
Introduced
Aug 13, 2010
Last source update
Oct 25, 2026
Coverage
Partial

Who actually shaped the debate?

2Total participants
2Discussion contributors
UnknownFormal actors
4Discussion messages
1.6Effective participants
100%Top-five discussion share
1People covering 50%
2People covering 80%

Policy evolution

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗

  2. Public discussion

    [LACNIC/Politicas] LAC-2010-03 actualizado/atualizado/updated

    3 Discussion messages · 2 Entities

    Source facts ↗

  3. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Christian O'Flaherty Only for Strategic Circle
    Discussion messages3
    First activityAug 9, 2010
    Last activityNov 30, 2010
    First explicit stanceSupport with changes
    Latest explicit stancePropose alternative
    Stance changes1
    Viewpoint consistencyConsistent
    Other policies3
    Freshness: Stale

    Last research attempt: Oct 18, 2026

    Identity verified: Oct 18, 2026

    Internet Society · Current
    Regional Vice President - Latin America and The Caribbean
    www.internetsociety.org
    Discussion messages
    3
    First activity
    Aug 9, 2010
    Last activity
    Nov 30, 2010
    First explicit stance
    Support with changes
    Latest explicit stance
    Propose alternative
    Stance changes
    1
    Viewpoint consistency
    Consistent
    Other policies
    3

    First explicit stance: Support with changes → Latest explicit stance: Propose alternative · Stance changes: 1

    Viewpoint consistency: Consistent

    He supports adding origin-AS information to WHOIS, initially allowing optional provision. His later preference for AS originador concerns Spanish wording, and he explicitly accepts the alternative wording if participants regard the terms as equivalent; neither message withdraws the earlier qualified support.

    Inclusion of ASN in the whois when available

    Assessment: Consistent · He supports adding origin-AS information to WHOIS, initially allowing optional provision. His later preference for AS originador concerns Spanish wording, and he explicitly accepts the alternative wording if participants regard the terms as equivalent; neither message withdraws the earlier qualified support.

    Conditions: These are discussions of the 2010 proposal, including its informal development before formal submission, not the 2021 replacement.

    La propuesta es muy buena y sirve para conocer el dato mas importante que buscamos en un routing registry sin tener la complejidad del RR. Tal vez al comienzo puede ser opcional poner esta informaci?n, pero en el futuro seria bueno que todos los bloques entregados por Lacnic tengan en whois el AS que debe originarlos. Creo que deberias mandar la propuesta formal. 2010/8/6 Flavio Marcelo <fmca at yahoo-inc.com>:

    Gracias Sofia, Tengo una duda con la traducci?n de "origin AS". Creo que es mejor decir: AS originador que "AS de origen" como dice el texto actual. Christian

    Hola Carlos, El texto sobre el que no tenemos duda es el ingl?s "origin AS". La propuesta fue de Flavio en portugu?s que puso "AS de origen". Si AS originador y AS de origen para todos es lo mismo entonces podemos dejarlo como AS de origen. En espa?ol a mi me gusta mas AS originador. 2010/11/30 Carlos Martinez-Cagnazzo <carlosm3011 at gmail.com>:

    1. Aug 9, 2010 · Support with changes

      [LACNIC/Politicas] proposta de politica: inclusao de ASN no whois

      La propuesta es muy buena y sirve para conocer el dato mas importante que buscamos en un routing registry sin tener la complejidad del RR. Tal vez al comienzo puede ser opcional poner esta informaci?n, pero en el futuro seria bueno que todos los bloques entregados por Lacnic tengan en whois el AS que debe originarlos. Creo que deberias mandar la propuesta formal. 2010/8/6 Flavio Marcelo <fmca at yahoo-inc.com>:

      Source facts ↗
    2. Nov 30, 2010 · Question or clarify

      [LACNIC/Politicas] LAC-2010-03 actualizado/atualizado/updated

      Gracias Sofia, Tengo una duda con la traducci?n de "origin AS". Creo que es mejor decir: AS originador que "AS de origen" como dice el texto actual. Christian

      Source facts ↗
    3. Nov 30, 2010 · Propose alternative

      [LACNIC/Politicas] LAC-2010-03 actualizado/atualizado/updated

      Hola Carlos, El texto sobre el que no tenemos duda es el ingl?s "origin AS". La propuesta fue de Flavio en portugu?s que puso "AS de origen". Si AS originador y AS de origen para todos es lo mismo entonces podemos dejarlo como AS de origen. En espa?ol a mi me gusta mas AS originador. 2010/11/30 Carlos Martinez-Cagnazzo <carlosm3011 at gmail.com>:

      Source facts ↗
    Per-policy stance timelines:LAC-2010-03 · Propose alternative · ConsistentLAC-2012-8 · Oppose · ConsistentLAC-2013-3 · Support · Insufficient evidence to assess consistencyLAC-2014-2 · Propose alternative · Consistent

    Total policy messages: 10

  2. Carlos Martínez-Cagnazzo Only for Strategic Circle
    Discussion messages1
    First activityNov 30, 2010
    Last activityNov 30, 2010
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies3

Sources and coverage

Official policy sources

Public discussion archives

  • lacnic-politicas
    Earliest captured
    Oct 21, 1999
    Latest captured
    Oct 21, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,704
    Known gaps
    28
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Mar 15, 2002
    Latest captured
    Oct 16, 2026
    Last refresh
    Oct 25, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,620
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 25, 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 25, 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 25, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    373
    Known gaps
    0
  • lacnic-lacnog
    Earliest captured
    Aug 1, 2026
    Latest captured
    Oct 16, 2026
    Last refresh
    Oct 25, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    7,770
    Known gaps
    4
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 30, 2013
    Last refresh
    Oct 25, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,257
    Known gaps
    0
  • lacnic-seguridad
    Earliest captured
    Jan 26, 2006
    Latest captured
    Dec 28, 2007
    Last refresh
    Oct 25, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,356
    Known gaps
    0

Coverage

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