Saltar al contenido principal

RIPE NCC · Vigilancia de RIR

Anycasting Assignments for TLDs and Tier 0/1 ENUM

Consulta aquí el historial de cada propuesta: qué cambió, por qué fue relevante, quién defendió cada postura, cómo evolucionaron las posiciones, qué se decidió y dónde persisten las lagunas en la evidencia.

Hechos con fuentes

ID de política
2008-05
RIR
RIPE NCC
Estado oficial
Accepted
Presentada
14 feb 2022
Última actualización de fuentes
11 nov 2026

¿Quiénes marcaron realmente el debate?

16Participantes totales
14Participantes del debate
2Actores formales
18Mensajes de discusión
10,1Participantes efectivos
50 %Cuota de los cinco principales
5Personas que cubren el 50 %
11Personas que cubren el 80 %

Evolución de la política

2.0
Aceptada · Accepted
27 abr 2009
Hechos con fuentes ↗

IPv4 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

IPv4 anycast assignment limit · The proposed IPv4 entitlement increases from one dedicated /24 to up to four /24 prefixes per TLD or ENUM.

IPv4 assignment conditions · The proposed IPv4 text removes the explicit direct-assignment-through-an-existing-LIR procedure and instead makes critical-DNS assignments subject to the general Provider Independent number-resource policies and the stated contractual requirements.

IPv6 anycast eligibility · Eligibility is changed from a test based on whether a ccTLD, gTLD or Tier 0/1 ENUM name-server set would fail the cited IANA procedure to a category-based rule covering TLD operators defined by IANA and ENUM operators defined by the ITU as critical DNS infrastructure.

IPv6 anycast assignment limit · The proposed IPv6 entitlement increases from one dedicated /48 to up to four /48 prefixes per TLD or ENUM.

IPv6 assignment procedure and contractual conditions · The request path is broadened from submission through an existing LIR to submission either directly to the RIPE NCC or through a sponsoring LIR, and the revised text adds the stated contractual requirements for critical-DNS assignments.

3.0
Aceptada · Accepted
27 abr 2009
Hechos con fuentes ↗

Existing IPv4 policy baseline · The document refreshes the quoted existing IPv4 rule from RIPE-424 to ripe-449. The newer baseline replaces the explicit direct-assignment-via-existing-LIR wording with applicability of Provider Independent number-resource policies and the contractual requirements. This is a change to the comparison baseline, not the proposal's new entitlement.

Proposed IPv4 policy dependencies · The proposed IPv4 text drops the explicit statement that critical-DNS assignments are subject to the general Provider Independent number-resource policies, while retaining the contractual-requirements reference.

Existing IPv6 policy baseline · The quoted existing IPv6 rule is refreshed from RIPE-421 to ripe-466: the baseline now names only the TLD administrator, allows a request either directly or through a sponsoring LIR, and adds the contractual-requirements condition. This is a baseline update rather than a new proposal entitlement.

Proposed IPv6 assignment procedure · The revised proposed IPv6 text removes the sentence explicitly assigning the prefix directly to the organisation and allowing requests either directly or through a sponsoring LIR; it proceeds instead from the anycast-use rule to the contractual-requirements condition.

4.0
Aceptada · Accepted
27 abr 2009
Hechos con fuentes ↗

IPv4 eligible operator definition · The IPv4 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

IPv4 assignment-cap wording · The cap is made explicit as up to four /24 prefixes per TLD and up to four /24 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

IPv4 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

IPv6 eligible operator definition · The IPv6 text replaces the generic critical-DNS definition and TLD/ENUM operators defined by IANA or ITU with TLD managers recorded in IANA's Root Zone Database and ENUM administrators assigned by the ITU.

IPv6 assignment-cap wording · The cap is made explicit as up to four /48 prefixes per TLD and up to four /48 prefixes per ENUM, replacing the shorter 'per TLD/ENUM' formulation.

IPv6 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.

Cronología del debate

  1. Debate público

    Re: [address-policy-wg] 2005-02 Last Call for Comments (IP Assignments for Anycasting DNS)

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  2. Debate público

    Re: [address-policy-wg] PI for Not-DNS Anycast.

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  3. Debate público

    [address-policy-wg] 2008-05 New Policy Proposal (Anycasting Tier 0/1 ENUM)

    2 Mensajes de discusión · 2 Entidades

    Hechos con fuentes ↗
  4. Debate público

    [address-policy-wg] comments on 2008-05 Anycasting Tier 0/1 ENUM

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  5. Debate público

    [address-policy-wg] 2008-05 Discussion Phase extended until 12 November 2008 (Anycasting Tier 0/1 ENUM)

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  6. Debate público

    [address-policy-wg] DRAFT agenda for RIPE address policy WG in Dubai

    2 Mensajes de discusión · 2 Entidades

    Hechos con fuentes ↗
  7. Debate público

    Re: [address-policy-wg] Re: Assignments for Critical Infrastruction

    3 Mensajes de discusión · 3 Entidades

    Hechos con fuentes ↗
  8. Debate público

    [address-policy-wg] Assignments for Critical Infrastruction

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  9. Debate público

    Re: [address-policy-wg] IPv6 assignment for the RIPE meeting network

    3 Mensajes de discusión · 3 Entidades

    Hechos con fuentes ↗
  10. Debate público

    [address-policy-wg] (Draft) Agenda for RIPE 58

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  11. Versión oficial

    1.0

    Aceptada · Accepted

    Hechos con fuentes ↗
  12. Versión oficial

    2.0

    Aceptada · Accepted

    Hechos con fuentes ↗
  13. Versión oficial

    3.0

    Aceptada · Accepted

    Hechos con fuentes ↗
  14. Versión oficial

    4.0

    Aceptada · Accepted

    Hechos con fuentes ↗
  15. Decisión oficial

    accepted

    accepted

    Hechos con fuentes ↗
  16. Debate público

    [address-policy-wg] Anycasting Assignments for TLDs and Tier 0/1 ENUM Implemented

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  17. Debate público

    [address-policy-wg] agenda for upcoming APWG meeting

    1 Mensajes de discusión · 1 Entidades

    Hechos con fuentes ↗
  18. Presentación

    Presentación

    Hechos con fuentes ↗

Entidades

Última actualización:

Cargando

Fuentes y cobertura

Archivos de debates públicos

Cobertura

Primera captura: 30 jun 1992
Última captura: 14 nov 2026