RIPE Policy Proposal 2008-05

Summary of Proposal:

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.

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.

b. 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 the 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.

Rationale:

a. Arguments supporting the proposal

Tier 0/1 ENUM operators have similar addressing needs in anycasting as ccTLDs or gTLDs as part of Internet DNS operators. Therefore the anycasting policies should be extended to cover them too.

b. Arguments opposing the proposal

Some may argue this will cause some waste of address space and additional entries in routing tables but the number of ENUM operators are limited so such impact should be very limited.