On Mon, Oct 10, 2011 at 01:06:23PM -0400, Michael Richardson wrote: > 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
it works, but nowhere near perfectly. Whenever a querying system changes its intended name space (resolution context) from $local to the global one, resolution of names in garden.example.com will just time out. Encoding this user experience in the design looks like a suboptimal choice to me. For resolution from the inside, you'd likely be dependent on access to the external delegation, which may not be feasible, either. > 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). While ULAs would "reduce" collisions, the general issues would be the same as with RFC1918 space. A single "local" context won't be enough. -Peter _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
