>>>>> "Evan" == Evan Hunt <[email protected]> writes: Evan> On Mon, Aug 06, 2012 at 10:17:34AM -0400, Ted Lemon wrote: >> Here you are definitely arguing about the wrong problem. At the >> presentation layer, both are equivalent, and both are wrong. What we >> want is not fridge-1.local and fridge-2.local, but fridge (here) and >> fridge (there).
Evan> If you want access to fridge (there), then fridge (there) has
Evan> to have a
Evan> globally-addressable domain name. If it doesn't have one,
Evan> then there's
Evan> no way for you to reach it, and I can't think of any reason for a
Evan> well-designed UI to display it. If "fridge.local" is available, then
Evan> it must be fridge (here).
No, the fridge must have a globally reachable address (GUA) to be reachable.
The name does not need to be globally addressable, but if it is, that
certainly helps in solving the problem.
What we are discussing, is how my (mobile) device can retrieve/discover
a pointer to a name that can be easily translated into an address.
We want this pointer rather than just having my device cache the GUA that it
got from mDNS: caching the GUA from mDNS works in the short term, but
fails after a renumber.
Tunnels are okay, but to use them, but has to get the DNS search order
and the DNS server list right, and that's walled garden territory.
*If* we are going to turn each home into a walled garden, then let's be
aware that we are doing that.
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpGRcgpuGseJ.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
