On Wednesday 4 December 2013 at 15:01, SM wrote:
> At 09:14 04-12-2013, David Conrad wrote: > > On the minus side, management of .ARPA is a part of the IANA > > functions contract which implies changes will require US DoC NTIA > > approval, so I'd agree that there is a potential for delays and ... > > non-technical discussion. > > .arpa is an IETF matter. Per RFC 3172, changes to the ARPA zone are authorised by the IAB. Per the most recently-awarded IANA Functions Contract, changes to the ARPA zone are not authorised by NTIA. They use a similar workflow to that employed for root zone management, but not identical. Joe _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
