> But, do you agree that publishing your home lighting controller to the DNS is > how you manage to control your lights from your phone when you are out of > wifi distance,
Yes, I didn't mean we should disallow this. If the user wants to publish his lightbulbs under .com, it's not our job to tell him he shouldn't. What I was worried about was that Ted's original proposal was that he was attempting to solve two independent and fairly doable problems with one overly general solution that would take years to specify and implement. I've said that before, so sorry for repeating myself: publishing a name in the global DNS is an end-to-end application-layer issue. If it involves the Homenet routers or the CPEs in any way, we're doing it wrong. The device that wishes to be publicly named should directly contact a DNS provider and get a lease on a suitable DNS name. It's not rocket science, and people like Dyn have been doing it for ages. (By the way -- I'm not particularly recommending Dyn's protocol, which doesn't do expiry times.) -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
