On Wed, Apr 24, 2002 at 05:59:44PM -0700, Bill Manning wrote: > While there seems to be progress on the 3ffe:: front > (wrt migrating it to ip6.arpa) we will be forever > stuck on any 2002:: or other user maintained mappings > due to RFC 3052 (I think thats the one that specifies > .arpa as the swank new anchor point) so for the > forseeable future, there will always be parts of the v6 > tree in ip6.int that will never be reflected in ip6.arpa.
While I can understand their position (or perhaps, "taking a position that does not accept 2.0.0.2.ip6.arpa", since I don't know their motivation) since there is no standard yet coming out of ngtrans wrt that zone, it is frustrating that several years after the initiative was made to move ip6.int to .arpa that there are still large obvious barriers to doing so, and more and more IPv6 code is going to have to deal with this legacy arpa/int mess. Getting it done and cleaning up later should be a reasonably high prority. No political opinion on the worth or lack thereof of ICANN is intended or implied.... -- David Terrell | "The Court understands fully why licensing has many Nebcorp Prime Minister | advantages for software publishers. However, this [EMAIL PROTECTED] | preference does not alter the Court's analysis that http://wwn.nebcorp.com/ | the substance of the transaction at issue here is a sale and not a license." - Judge Dean Pregerson, Softman v Adobe. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
