> register it as a domain name with a specially-designated suffix. Let's
> say the suffix is -site-ipv6.net, and let's say they chose the nice random
> number 0x0012345678, so they would register the domain
> "x0012345678-site-ipv6.net". If somebody else was using that unique
> prefix, company.foo would find this out when they went to register it, and
> would be forced to choose a different number. This guarantees uniqueness.
>
That is certainly an interesting idea.
The obvious negatives:
1. Extra load on core DNS, mainly I suppose for just storing the
things---presumably not too many of the actual queries would work thier way
to the core (though some necessarily would).
2. Extra overhead and delay of the additional query. For popular sites,
which typically have a very short TTL, the extra query would happen often,
leading to increased load on local DNS server blah blah blah
3. Having to change the DNS client...buy-in from the DNS community might be
tough.
4. The weirdness of requesting query x from DNS, and DNS going off and
actually making query y. Does this actually happen in any other context
today? Sounds like a major architectural change for DNS...(ah, but then
again it wouldn't be the first time for IPv6....)
5. Presumably sites that prefered two-faced over this would not want thier
hosts making this extra xxx-site-ipv6.net query. So there would have to be
some way of switching the behaviour on and off.
I don't know...other reactions?
PF
--------------------------------------------------------------------
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]
--------------------------------------------------------------------