Anycasting Assignments for TLDs and Tier 0/1 ENUM

Summary of Proposal:

The proposal is to allow Tier 0/1 ENUM operators to receive IPv4 and IPv6 anycasting assignments and extend the number of anycasting prefixes that can be assigned to an operator from one to up to four assignments.

Policy text

a. Current (if modify):

From ripe-449

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.

Anycasting assignments 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”.

Anycasting assignments are 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:

[Following text is to appear in the RIPE Document, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region, if the proposal reaches consensus. Please review this change that the proposal is bringing within the drafted policy document from the link above in Draft RIPE Documents]

6.9 Anycasting TLD and Tier 0/1 ENUM Nameservers

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. The organisation may receive up to four /24 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.

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".

Anycasting assignments are registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for Critical DNS infrastructure any longer. 

a. Current (if modify):

From ripe-466

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 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 properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. TLD anycasting address assignments 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".

Anycasting assignments are 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

[Following text is to appear in the RIPE Document, IPv6 Address Allocation and Assignment Policy for the RIPE NCC Service Region, if the proposal reaches consensus. Please review this change that the proposal is bringing within the drafted policy document from the link above in Draft RIPE Documents]

7. Anycasting TLD and Tier 0/1 ENUM Nameservers

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. The organisation may receive up to four /48 prefixes per TLD/ENUM. These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in RFC 3258.

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".

Anycasting assignments are registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for Critical DNS infrastructure any longer.