>>>>> "Peter" == Peter Koch <[email protected]> writes: >> example.com NS reachable by the world. >> garden.example.com NS pointing to AAAA record, where IPv6 >> address is only reachable from garden. >> television.garden.example.com AAAA returned from >> garden.example.com name server (above) >> >> This solution works perfectly in IPv4 land, but due to lack of IPv4
Peter> it works, but nowhere near perfectly. Whenever a querying system
Peter> changes its intended name space (resolution context) from $local
Peter> to the global one, resolution of names in garden.example.com
Peter> will just time out. Encoding this user experience in the design looks
Peter> like a suboptimal choice to me.
yes, but what is being asked for now, is that the host equivalent of
/etc/resolv.conf be extended with a list of suffixes. We are told that
mobile operators (who still think they own the handsets) will be
deploying various application layer systems whereby the application will
always do some DNS requests over 4G, and some content will only be
available that way.
So, this failure you describe will still occur, but instead of "timeout"
the user will get "host not found"
>> It seems to me that we just don't need anything else in IPv6, except
>> easily *available* non-connected PI address space (whether it's ULA-C,
>> some recognized part of 2000::/3, or an entirely new space).
Peter> While ULAs would "reduce" collisions, the general issues would be
the same
Peter> as with RFC1918 space.
Thus why I said ULA-C.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
pgpnZBbKxosgF.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
