On 11 Feb 2010, at 22:27, B C wrote:
"Today, delegations under in-addr.arpa are served by servers operated by ARIN and its contractors"
Seems incorrect to me, I think the other RIR's might be surprised to find they are contractors to ARIN.
Brett, IMO it would have been better if ARIN had used the word "partners" instead of "contractors". I'm fairly sure that's what ARIN meant even if it wasn't what they said in the statement you quoted. ARIN will know that the other RIRs are not contractors to ARIN when it comes to reverse DNS space. As do the other RIRs. Who will presumably be happy to remind their cousins at ARIN of that fact. The situation with DNS service for in-addr.arpa doesn't lend itself to soundbites. So I wouldn't worry too much about soundbites on a web page which by definition won't tell the whole story in painstaking detail. As I'm sure you know, some parts of the tree are managed by the other RIRs (who then have mutual arrangements for DNS service for "their" domains). [As an example, 195.in-addr.arpa is managed by the NCC and the zone's NSRRset includes name servers operated by APNIC and ARIN.] Other parts are handled by ARIN's name servers and its contractors (Neustar/Ultra IIRC). Then there's the AS112 project for RFC1918 space. And the unallocated or reserved space, etc, etc. Now someone could explain all of this in fine detail. But would it help or hinder understanding of whar ARIN's doing wrt DNSSEC?