>>>>> "Kerry" == Kerry Lynn <[email protected]> writes: >> When I'm at your house, and I visit "fridge.local", do I get your >> fridge, or mine?
Kerry> Mine, by definition. Given that I'm not sure how you mean ".homenet"
Kerry> to work by comparison, I'm not sure I completely understand the rest
Kerry> of the discussion.
Yes, I agree that when I lookup "fridge.local", I'll get yours.
*unless* the mapping to a GUA is still in my browser's cache...
(I deleted a realistic situation for my smartphone talking to my stove
to find out when the roast is done)
So what I'm after is a way for the fridge to say, when I lookup
"fridge.local" that it's GUA is 2001::F001 (mDNS can already do this),
but also that it's unicast DNS name is fridge.kerlyn.com.
Kerry> If you are remotely accessing resources in your home, you are
probably
Kerry> more advanced than 99% of all home network users. Why wouldn't the
Kerry> solution you use on the road apply equally well at your
Kerry> neighbor's house?
Kerry, the point of end-to-end connectivity into the home is to permit
the things that us "1%" do, to be doable by everyone... Right?
So, yes, dyndns is *a* solution, but I don't know how to automate it in
a scalable way. I'm concerned that for the homenet protocols to be
incrementally deployable ("create value") that we can not rely too much
on the ISPs doing the right thing for forward DNS delegation.
Kerry> I think defining new "zones" under .arpa. may have merit in the
following
Kerry> respect: ICANN is now in the business of selling dotless
Kerry> domain names.
Just to be clear: my idea isn't that IETF run a dyndns under arpa, but
that we have a WKN under arpa which is treated specially.
I understand that my idea is hard to evaluate without a document.
Should I write one then?
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpyqY8CKLb0c.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
