The process will dedicate new hostnames to the servers that are authoritative for the "arpa" zone, but it will initially serve the "arpa" zone from the same hosts.
Once completed, subsequent transitional phases could include using new hosts to replace or augment the existing root nameserver hosts and separating the editing and distribution of the "arpa" zone from necessarily being connected to the root zone. Any future management considerations regarding how such changes may be performed are beyond the scope of this document.
Consistent with the use of the "arpa" namespace itself to host nameservers for other delegations in the "arpa" zone [RFC 5855
], this document specifies a new namespace of "ns.arpa", with the nameserver set for the "arpa" zone to be initially labeled as follows:
Dedicated hostnames eliminate a logical dependency that requires the coordinated editing of the nameservers for the "arpa" zone and the root zone. This component of this transition does not require that the underlying hosts that provide "arpa" name service (that is, the root nameservers) be altered. The "arpa" zone will initially map the new hostnames to the same IP addresses that already provide service under the respective hostnames within "root-servers.net".
Because these nameservers are completely within the "arpa" zone, they will require glue records in the root zone. This is consistent with current practice and requires no operational changes to the root zone.
After initially migrating the "arpa" zone to use hostnames that are not shared with the root zone, the underlying name service is expected to evolve such that it no longer directly aligns with a subset of root nameserver instances. With no shared infrastructure between the root nameservers and the "arpa" nameservers, future novel applications for the "arpa" zone may be possible.
Any subsequent change to the parties providing name service for the zone is considered a normal management responsibility and would be performed in accordance with [RFC 3172
Publication of the "arpa" zone file to the authoritative "arpa" nameservers is currently undertaken alongside the root zone maintenance functions. Upon the separation of the "arpa" infrastructure from the root nameserver infrastructure, publication of the "arpa" zone no longer necessarily needs to be technically linked or interrelated to the root zone publication mechanisms.
Full technical separation of operations of the "arpa" zone and root zone minimally requires the following to be satisfied:
The "arpa" zone no longer shares any hostnames in its nameserver set with the root zone.
The hosts that provide authoritative name service are not the same hosts as the root nameservers, do not share any IPv4 or IPv6 addresses with the root servers, and are sufficiently provisioned separately such that any unique "arpa" zone requirements can be deployed without affecting how root zone service is provided.
The editorial and publication process for the "arpa" zone removes any common dependencies with the root zone process so that the "arpa" zone can be managed, edited, and provisioned wholly independently of the root zone.
Such separation is ultimately sought to allow for novel uses of the "arpa" zone without the risk of inadvertently impacting root zone and root server operations. It is recognized that achieving this state requires a deliberative process involving significant coordination to ensure impacts are minimized.