Blame the IAB. Apparently, they were the ones who created this mess by frivolously adopting ip6.arpa as a replacement for ip6.int.
I think that's not exactly true ;-) . The reverse name tree for IPv4 is already located in the arpa. subtree. I cannot see any good reason why the same service for IPv6 should use a different TLD. (Actually I don't see a good formal reason for not using in-addr.arpa. - but I presume that there are good technical reasons...) . The mandate of the int. TLD (to support international treaty organisations) is not exactly compatible with the use for IPv6 reverse name tree delegations :-) Wilfried ( https://cert.aco.net/ ) _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber@CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~