IP Assignments for Anycasting DNS
This policy proposal has been accepted
- State:
- Accepted
- Publication date
- Affects
- Draft document
- IP Assignments for Anycasting DNS
- Author
- Proposal Version
- 1.0 - 02 Nov 2005
- All Versions
-
- Accepted
- 10 Sep 2006
- Working Group
- Address Policy Working Group
- Proposal type
-
- New
- Policy term
- Renewable
To enable country code Top Level Domain (ccTLD) and global Top Level Domain (gTLD) name server operators to provide their DNS service using shared unicast technology, RIPE NCC may assign one IPv4 and/or one IPv6 prefix to each TLD operator.
a. Current: N/A
b. New: "If the name server set of a TLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Name Server Delegation and Glue Data' the TLD administrator may receive dedicated network prefixes for the sole purpose of anycasting name servers, as described in RFC 3258. These shall be:
-
One /24 IPv4 prefix and/or
-
One /48 IPv6 prefix per operator.
The prefixes shall be tagged as 'ASSIGNED ANYCAST' in the RIPE Database and MUST be returned to the RIPE NCC if not in use for anycast DNS any longer."
Appendix A. APNIC Policy
11.3 Critical infrastructure
The following critical infrastructure networks, if operating in the Asia Pacific region, are eligible to receive a portable assignment:
-
root domain name system (DNS) server;
-
global top level domain (gTLD) nameservers;
-
country code TLD (ccTLDs) nameservers;
-
IANA;
-
Regional Internet Registry (RIRs); and
-
National Internet Registry (NIRs).
Assignments to critical infrastructure are available only to the actual operators of the network infrastructure performing such functions. Registrar organisations which do not actually host the network housing the registry infrastructure, will not be eligible for an assignment under this policy.
The minimum assignment made under these terms is /24.
Appendix B. ARIN Policy
4.4. Micro-allocation - ARIN will make micro-allocations to critical infrastructure providers of the Internet, including public exchange points, core DNS service providers (e.g. ICANN-sanctioned root, gTLD, and ccTLD operators) as well as the RIRs and IANA. These allocations will be no longer than a /24 using IPv4 or a /48 using IPv6. Multiple allocations may be granted in certain situations.
Appendix C. LACNIC Policy
3.3.3 Micro Allocations
Micro allocation is the name given to those allocations that imply blocks smaller than /20 but always larger than or equal to /24.
LACNIC can grant this type of allocation in case of projects and infrastructure for networks that are key or critical for the region, such as IXPs (Internet Exchange Points), NAPs (Network Access Points), RIRs, ccTLDs, among others.
In the case of IXPs or NAPs, in order to be able to apply for this type of allocation, organizations shall meet the following requirements:
1. Duly document the following aspects:
1. 1 Prove by means of their bylaws their capacity of IXP or NAP. The organization shall have at least three members and an open policy in relation to the association of new members.
1. 2 Submit a company structure organizational diagram.
1. 3 Document the numbering plan to be implemented.
2. Provide a usage plan for the following three and six months.
The rest of the applications shall be studied based on the analysis of the documentation justifying the critical and/or key aspects of the project. Organizations receiving micro allocations are not authorized to suballocate these addresses.