In message <[email protected]> Michael Richardson writes: > >>>>> "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 > Kerry> ".homenet" > Kerry> to work by comparison, I'm not sure I completely understand > Kerry> 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.
Regular DNS can do that too. :-) [btw - this wasn't dyndns] host fridge fridge.ipv6.occnc.com has IPv6 address 2001:470:1f07:1545::4:f00d That only works because ipv6.occnc.com is in my search path. In the prior example I gave if sitelocal was in my search path and there was no DNS name given to my zone, then I'd get fridge.sitelocal. If OTOH a provider gave me curtis.site.myprovider.evil then I'd get fridge.curtis.site.myprovider.evil in response to a "host fridge" command. That is because the provider would put curtis.site.myprovider.evil in the domain and search response in DHCP and the router would pass it along. [btw- I don't have a ISP provided email (that I know of) and I doubt "curtis" is not taken, however the contact email for them is [email protected].] > Kerry> If you are remotely accessing resources in your home, you > Kerry> 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? Exactly. > 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. The dyndns would be localized to the site. The provider just delegates a name to use that is a subdomain of their own, or as I suggested in an earlier email, perhaps of the form <customer-email>.site.<provider-fqdn>. That would be completely static and set up at customer service setup and never changed. At worst, the customer could opt not to use it or have equipment that can't make use of it. A provider run DNS secondary would similarly just be statically configured. Today the customer is given a dynamic address (unless explicitly asking for and paying for a single static address). That is because IPv4 addresses are in short supply. IPv6 /64 prefixes are not is short supply, therefore a provider supporting IPv6 native (or tunnels) could easily offer a static /64 reserved when the customer service is initially setup and never changed until the customer leaves. This is two things configured on the provider side when the customer is setup and never touched until the customer leaves. That is not a large burden on the provider dns ops staff. > Kerry> I think defining new "zones" under .arpa. may have merit in > Kerry> 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. The homenet.arpa subdomain adds nothing IMHO. If the provider is completely non-cooperative in all ways except basic IPv6 connectivity and granting a /64 via DHCP or statically configured on provider owned CPE, then the customer simply gets fridge.sitelocal and can't access his own fridge from the neighbor's house. > I understand that my idea is hard to evaluate without a document. > Should I write one then? Could you summarize in an outline what you would put in that document? Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
