Aller au contenu principal

RIPE NCC · Veille des RIR

Anycasting Assignments for TLDs and Tier 0/1 ENUM

Commencez ici pour consulter l’historique, proposition par proposition : ce qui a changé, pourquoi cela comptait, qui a défendu quoi, comment les positions ont évolué, ce qui a été décidé et quelles lacunes subsistent dans les preuves.

Faits sourcés

Identifiant
2008-05
RIR
RIPE NCC
Statut officiel
Accepted
Introduction
14 févr. 2022
Dernière mise à jour des sources
11 nov. 2026

Qui a réellement façonné le débat ?

16Total des participants
14Contributeurs à la discussion
2Acteurs formels
18Messages de discussion
10,1Entités effectives
50 %Part des cinq premiers
5Personnes couvrant 50 %
11Personnes couvrant 80 %

Évolution de la politique

2.0
Acceptée · Accepted
27 avr. 2009
Faits sourcés ↗

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
Acceptée · Accepted
27 avr. 2009
Faits sourcés ↗

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
Acceptée · Accepted
27 avr. 2009
Faits sourcés ↗

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.

Chronologie du débat

  1. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  2. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  3. Débat public

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

    2 Messages de discussion · 2 Entités

    Faits sourcés ↗
  4. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  5. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  6. Débat public

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

    2 Messages de discussion · 2 Entités

    Faits sourcés ↗
  7. Débat public

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

    3 Messages de discussion · 3 Entités

    Faits sourcés ↗
  8. Débat public

    [address-policy-wg] Assignments for Critical Infrastruction

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  9. Débat public

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

    3 Messages de discussion · 3 Entités

    Faits sourcés ↗
  10. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  11. Version officielle

    1.0

    Acceptée · Accepted

    Faits sourcés ↗
  12. Version officielle

    2.0

    Acceptée · Accepted

    Faits sourcés ↗
  13. Version officielle

    3.0

    Acceptée · Accepted

    Faits sourcés ↗
  14. Version officielle

    4.0

    Acceptée · Accepted

    Faits sourcés ↗
  15. Décision officielle

    accepted

    accepted

    Faits sourcés ↗
  16. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  17. Débat public

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

    1 Messages de discussion · 1 Entités

    Faits sourcés ↗
  18. Présentation

    Présentation

    Faits sourcés ↗

Entités

Dernière mise à jour:

Chargement

Sources et couverture

Archives des discussions publiques

Couverture

Première capture: 30 juin 1992
Dernière capture: 14 nov. 2026