>One other thing to keep in mind is that unlike an endless chain of
>glueless NS records, A6 records will, in general, chain to other records
>in the same zone and thus a significant part of the chain will be returned
>on each query. Thus, NS chains require much more work to resolve and
>should not be compared to A6 chains. It shouldn't take more than 2 or 3
>queries to resolve a full A6 chain. In all likelyhood, prefixes for
>popular providers and services will remain cached, and resolving the names
>of virtual hosts and hosts on the same network will only take a single
>query, just as they do now with A records. -Nathan
A6 chain will not stay in the same zone. it will go up from leaf site
to a small ISP, then to middle ISP, and then to large ISP. this is
the purpose of A6.
foo.itojun.org. IN A6 64 ::9876:5432:9876:5432 segment0.itojun.org.
segment0.itojun.org. IN A6 48 ::1234:0:0:0:0 ispX.net.
ispX.net. IN A6 40 0:0:0012:: ispY.net.
ispY.net. IN A6 32 0:0:2300:: ispZ.net.
ispZ.net. IN A6 16 0:9876:: ispU.net.
ispU.net. IN A6 0 1234::
itojun
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
