Skip to main content

Anycasting Assignments for TLDs and Tier 0/1 ENUM

This policy proposal has been accepted

The new RIPE Documents are: ripe-481 , ripe-484

You're looking at an older version: 1

The current (published) version is 4
2008-05
State:
Accepted
Publication date
Affects
Draft document
Draft
Author(s)
  • Brett Carr [Nominet]
  • Ondřej Surý [CZ.NIC]
  • Brett Carr [Nominet]
  • Ondřej Surý [CZ.NIC]
Proposal Version
4.0 - 27 Apr 2009
All Versions
Accepted
09 Jun 2009
Working Group
Address Policy Working Group
Proposal type
  • Modify
Policy term
Permanent
New RIPE Document(s)

Summary of Proposal:

The proposal is to allow Tier 0/1 ENUM operators to receive IPv4 and IPv6 anycasting assignments.

Policy text

a. Current (if modify):

From RIPE-424

6.9 Anycasting TLD Nameservers

If the name server set of a ccTLD or a gTLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD administrator may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The prefix will be assigned by the RIPE NCC directly to the TLD, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.

b. New:

6.9 Anycasting TLD and Tier 0/1 ENUM Nameservers

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 administrator may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

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' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.

For the purposes of this policy the following definitions are made:

Tier0 Enum: User enum top level domain intended to store user enum country code delegations.

Tier0 Enum operator: The organisation that has been delegated the responsibility of operating the nameservers for e164.arpa by the IAB/ITU

Tier1 Enum: User enum second level domains intended to store enum user data within a specific geographical region.

Tier1 Enum operator: The organisation that has been delegated the responsibility of operating the nameserver for a specfic geographic region by the Tier0 Enum operator.

This policy only applies to those networks fitting within the definitions above. In other words, this policy does not apply to infrastructure or inter-operator ENUM networks. 

a. Current (if modify):

From RIPE-421

7. Assignments for Anycasting TLD Nameservers

If the name server set of a ccTLD or a gTLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD or ENUM administrator may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The prefix will be assigned by the RIPE NCC directly to the TLD, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.

a. New

7. Assignments for Anycasting TLD Nameservers

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 administrator may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

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' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.

For the purposes of this policy the following definitions are made:

Tier0 Enum: User enum top level domain intended to store user enum country code delegations.

Tier0 Enum operator: The organisation that has been delegated the responsibility of operating the nameservers for e164.arpa by the IAB/ITU

Tier1 Enum: User enum second level domains intended to store enum user data within a specific geographical region.

Tier1 Enum operator: The organisation that has been delegated the responsibility of operating the nameserver for a specfic geographic region by the Tier0 Enum operator.

This policy only applies to those networks fitting within the definitions above. In other words, this policy does not apply to infrastructure or inter-operator ENUM networks.

The text of this version of the proposal was recovered from the slides presented at RIPE 57.

It was not possible to retrieve the following details from the archive:

Rationale:

  1. Arguments supporting the proposal
  2. Arguments opposing the proposal