Anycasting Assignments for TLDs and Tier 0/1 ENUM

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

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.

may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

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.

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'

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

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

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.

may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

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.

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'

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

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

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

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 document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".

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

The organisation may receive up to four /24 prefixes per TLD/ENUM.

The organisation may receive up to four /24 prefixes per TLD and four /24 prefixes per 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.

These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786.

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

The organisation may receive up to four /48 prefixes per TLD/ENUM.

The organisation may receive up to four /48 prefixes per TLD and four /48 prefixes per 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.

These prefixes must be used for the sole purpose of anycasting authoritative DNS servers for the stated TLD/ENUM, as described in BCP126/RFC4786