On 2010-01-04, at 17:40, John R. Levine wrote: >> If you could me more substantive guidance as to where the documents could be improved, I'd be very happy. As things stand the best I can do is say "I'm sorry" :-) > > Well, OK. Is there a plan to move the DNS for in-addr.arpa and ip6.arpa to the new set of servers? If so, what is it? Will it need more IAB or IETF action? There is a plan being developed to re-delegate IN-ADDR.ARPA and IP6.ARPA. The plan is being developed by ICANN in conjunction with the five RIRs. Work has been going on for some time, and the specification of the naming scheme for the servers (i.e. this draft) is one of the pieces of the puzzle that needs to be in place before the plan can be finalised. I am happy to share the highlights of this plan here, since you asked, but please note that this is a draft proposal which has not yet been authorised for implementation, and hence all of this is subject to change. The draft plan is to re-delegate IN-ADDR.ARPA and IP6.ARPA to dedicated servers, named according to the text you have read. The servers are to be operated by the five RIRs plus ICANN, making six operators in total, consistent with the thinking that led to the current nameserver operators for IP6.ARPA. The plan includes a timeline for the technical operations associated with the change, as well as communications with the root server operators, the RIRs, US DoC NTIA, VeriSign and the general public through operator mailing lists. It is my understanding that re-delegation of IN-ADDR.ARPA and IP6.ARPA will follow procedures specified in the IANA functions contract, and will not require IAB or IETF action. Joe _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf