Change in IP Assignments for Anycasting DNS Policy

This proposal suggested that there should no longer be a requirement to be a ccTLD or a gTLD to receive IPv4 and IPv6 assignments for anycasting DNS.

Summary of Proposal:

This proposal suggests that there should no longer be a requirement to be a ccTLD or a gTLD to receive IPv4 and IPv6 assignments for anycasting DNS. The proposal suggests new requirements that the requesting organisation must fulfil to receive assignments for anycasting DNS.

Rationale:

a. Arguments supporting the proposal

There are organisations which are running DNS but which are not holding a ccTLD or a gTLD. However, as their DNS setup is reasonably large and very important for their customers, they need to do anycasting. Although these organisations need resources for similar reasons, they cannot qualify for anycast assignments under the current Anycasting Assignments policy.

The proposal suggests that resources should be assigned to those organisations which can demonstrate a reasonable anycasting DNS setup. It proposes that details like the number of the organisation's name servers and the geographical diversity of their DNS setup should be included in the policy text so that eligible organisations can demonstrate their serious need for the address space.

b. Arguments opposing the proposal

One can argue that there will be some additional address consumption and routing table slots with this proposal as the assignment criteria will be opened to organisations that are not a ccTLD or a gTLD.