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?
Evolución de la política
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.
Hechos con fuentes −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administratorHechos con fuentes ↗
Hechos con fuentes +
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.Hechos con fuentes ↗
IPv4 anycast assignment limit · The proposed IPv4 entitlement increases from one dedicated /24 to up to four /24 prefixes per TLD or ENUM.
Hechos con fuentes −
may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.Hechos con fuentes ↗
Hechos con fuentes +
The organisation may receive up to four /24 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.Hechos con fuentes ↗
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.
Hechos con fuentes −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'Hechos con fuentes ↗
Hechos con fuentes +
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".Hechos con fuentes ↗
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.
Hechos con fuentes −
If the name server set of a ccTLD, gTLD or a Tier 0/1 ENUM without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or the ENUM administratorHechos con fuentes ↗
Hechos con fuentes +
Critical DNS infrastructure is defined as infrastructure providing Authoratitve TLD or ENUM Tier 0/1 DNS lookup services. The organisation(s) applicable under this policy are TLDs operators as defined by IANA and ENUM operators as defined by the ITU.Hechos con fuentes ↗
IPv6 anycast assignment limit · The proposed IPv6 entitlement increases from one dedicated /48 to up to four /48 prefixes per TLD or ENUM.
Hechos con fuentes −
may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.Hechos con fuentes ↗
Hechos con fuentes +
The organisation may receive up to four /48 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoratitve DNS servers for the stated TLD/ENUM, as described in RFC 3258.Hechos con fuentes ↗
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.
Hechos con fuentes −
The prefix will be assigned by the RIPE NCC directly to the TLD or ENUM operator, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST'Hechos con fuentes ↗
Hechos con fuentes +
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".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.
Hechos con fuentes −
La evidencia validada no está disponible.Hechos con fuentes +
La evidencia validada no está disponible.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.
Hechos con fuentes −
Assignments for Critical DNS infrastructure are subject to Provider Independent (PI) number resource policies as described in this document and also to the policies described in the RIPE NCC document entitled "Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region".Hechos con fuentes ↗
Hechos con fuentes +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".Hechos con fuentes ↗
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.
Hechos con fuentes −
La evidencia validada no está disponible.Hechos con fuentes +
La evidencia validada no está disponible.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.
Hechos con fuentes −
The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR.Hechos con fuentes ↗
Hechos con fuentes +
Assignments for Critical DNS infrastructure are subject to the policies described in the RIPE document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".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.
Hechos con fuentes −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.Hechos con fuentes ↗
Hechos con fuentes +
The organisations applicable under this policy are TLD managers, as recorded in the IANA's Root Zone Database and ENUM administrators, as assigned by the ITU.Hechos con fuentes ↗
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.
Hechos con fuentes −
The organisation may receive up to four /24 prefixes per TLD/ENUM.Hechos con fuentes ↗
Hechos con fuentes +
The organisation may receive up to four /24 prefixes per TLD and four /24 prefixes per ENUM.Hechos con fuentes ↗
IPv4 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.
Hechos con fuentes −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.Hechos con fuentes ↗
Hechos con fuentes +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786.Hechos con fuentes ↗
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.
Hechos con fuentes −
Critical DNS infrastructure is defined as infrastructure providing Authoritative TLD or ENUM Tier 0/1 DNS lookup services. The organisations applicable under this policy are TLD operators as defined by IANA and ENUM operators as defined by the ITU.Hechos con fuentes ↗
Hechos con fuentes +
The organisations applicable under this policy are TLD managers as, recorded in the IANA's Root Zone Database and ENUM administrators, as assigned by the ITU.Hechos con fuentes ↗
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.
Hechos con fuentes −
The organisation may receive up to four /48 prefixes per TLD/ENUM.Hechos con fuentes ↗
Hechos con fuentes +
The organisation may receive up to four /48 prefixes per TLD and four /48 prefixes per ENUM.Hechos con fuentes ↗
IPv6 anycast technical standard · The cited technical basis for use of the prefixes changes from RFC 3258 to BCP126/RFC4786.
Hechos con fuentes −
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.Hechos con fuentes ↗
Hechos con fuentes +
These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786Hechos con fuentes ↗
Cronología del debate
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 ↗Debate público
Re: [address-policy-wg] PI for Not-DNS Anycast.
1 Mensajes de discusión · 1 Entidades
Hechos con fuentes ↗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 ↗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 ↗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 ↗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 ↗Debate público
Re: [address-policy-wg] Re: Assignments for Critical Infrastruction
3 Mensajes de discusión · 3 Entidades
Hechos con fuentes ↗Debate público
[address-policy-wg] Assignments for Critical Infrastruction
1 Mensajes de discusión · 1 Entidades
Hechos con fuentes ↗Debate público
Re: [address-policy-wg] IPv6 assignment for the RIPE meeting network
3 Mensajes de discusión · 3 Entidades
Hechos con fuentes ↗Debate público
[address-policy-wg] (Draft) Agenda for RIPE 58
1 Mensajes de discusión · 1 Entidades
Hechos con fuentes ↗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 ↗Debate público
[address-policy-wg] agenda for upcoming APWG meeting
1 Mensajes de discusión · 1 Entidades
Hechos con fuentes ↗
Entidades
Cargando
Fuentes y cobertura
Fuentes oficiales
Archivos de debates públicos
- ripencc-address-policy-wg –
- ripencc-accountability-tf-ripe.net –
- ripencc-agm-nominations-ripe.net –
- ripencc-all-anchors-ripe.net –
- ripencc-anti-abuse-wg-ripe.net –
- ripencc-atlas-sponsors-ripe.net –
- ripencc-atlas-sw-probes-ripe.net –
- ripencc-bcop-ripe.net –
- ripencc-coc-tf-ripe.net –
- ripencc-connect-bof-ripe.net –
- ripencc-connect-wg-ripe.net –
- ripencc-cooperation-wg-ripe.net –
- ripencc-db-help-ripe.net –
- ripencc-db-wg-ripe.net –
- ripencc-diversity-ripe.net –
- ripencc-dns-resolver-tf-ripe.net –
- ripencc-dns-wg-ripe.net –
- ripencc-dp-tf-ripe.net –
- ripencc-eb-candidates-ripe.net –
- ripencc-eix-wg-ripe.net –
- ripencc-election-cc-team-ripe.net –
- ripencc-enum-announce-ripe.net –
- ripencc-enum-wg-ripe.net –
- ripencc-hackathon-list-ripe.net –
- ripencc-icann-plan-ripe.net –
- ripencc-iot-wg-ripe.net –
- ripencc-ipmap-ripe.net –
- ripencc-ipmt-dev-ripe.net –
- ripencc-ipv6-wg-ripe.net –
- ripencc-irrtoolset-ripe.net –
- ripencc-lir-wg-ripe.net –
- ripencc-mat-wg-ripe.net –
- ripencc-measure-voip-ripe.net –
- ripencc-members-discuss-unmoderated-ripe.net –
- ripencc-members-discuss-ripe.net –
- ripencc-myasntesting-ripe.net –
- ripencc-ncc-announce-ripe.net –
- ripencc-ncc-services-wg-ripe.net –
- ripencc-opensource-wg-ripe.net –
- ripencc-persian-lir-ripe.net –
- ripencc-policy-announce-ripe.net –
- ripencc-raci-list-ripe.net –
- ripencc-regional-russia-ripe.net –
- ripencc-regional-ukraine-ripe.net –
- ripencc-ripe-atlas-ambassadors-ripe.net –
- ripencc-ripe-atlas-tools-maintainers-ripe.net –
- ripencc-ripe-atlas-ripe.net –
- ripencc-ripe-chair-discuss-ripe.net –
- ripencc-ripe-db-requirements-tf-ripe.net –
- ripencc-ripe-forum-test-ripe.net –
- ripencc-ripe-list-unmoderated-ripe.net –
- ripencc-ripe-list-ripe.net –
- ripencc-ripe-parents-ripe.net –
- ripencc-ripecast-ripe.net –
- ripencc-rirs-lea-ripe.net –
- ripencc-ris-int-ripe.net –
- ripencc-ris-users-ripe.net –
- ripencc-routing-wg-ripe.net –
- ripencc-rpslng-ripe.net –
- ripencc-security-wg-ripe.net –
- ripencc-see-regional-ripe.net –
- ripencc-techsec-wg-ripe.net –
- ripencc-tld-wg-ripe.net –
- ripencc-tt-tf-ripe.net –
- www.ripe.net/community/wg/active-wg/ap/minutes
- ripencc-green-tech-hackathon-orga-ripe.net
- ripencc-nccdays-pc-ripe.net
Cobertura
Primera captura: 30 jun 1992
Última captura: 14 nov 2026
