% >% >RFC1886: DNS Extensions for IPv6
% >% this one needs IP6.INT -> IP6.ARPA change, at least.
% > one does not change RFCs, one issues replacements.
%
% i understand that, thanks for clarification.
%
% (sorry for continuing this on ipngwg, not dnsext0
% don't we need suggestions in the document, regarding to transition
% from ip6.int to ip6.arpa? for example, i think client resolvers should
% do
%
% try blah.ip6.arpa;
% if (not found)
% try blah.ip6.int;
%
% as there are name tree populated on ip6.int.
%
% itojun
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.
ip6.arpa will remain a subset of ip6.int.
one might better optimize the loop as:
try blah.ip6.int;
if (not found)
try blah.ip6.arpa;
--
--bill
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
