Re: [homenet] About Ted's naming architecture presentation and document

[james woodyatt <[e-mail]>]

Hi Mike,

Yeah, you have to dog-leg through a provider that you don’t trust. Because the providers you don’t trust are the only things that home automation device manufacturers are assured by the actual existing Internet will be reachable from arbitrarily located remote mobile handsets. 

Home automation controllers and similar servers on home networks will not generally be reachable from arbitrarily located remote mobile handsets without some kind of standard solution to the problem described in section 3.4, Passive Listeners of RFC 6092, which is widely deployed now in most residential IPv6 gateways. Note also that REC-49 of that document is also widely ignored in most implementations, certainly enough implementations that it cannot serve as a dependable mechanism. It’s also important that REC-48 has mostly gone without further attention since, and that certainly adds additional complications.

Look on the bright side! Consider the possibilities that open before you when there is a 3rd-party provider that everyone can trust!

> On Nov 21, 2016, at 11:46, Michael Thomas <[e-mail]> wrote:
> 
> You mean i have to dogleg through a provider who i don't trust? For whom I'm the product? yuck.
> 
> Mike
> 
> On 11/21/2016 11:34 AM, james woodyatt wrote:
>> On Nov 16, 2016, at 17:31, Michael Richardson < <mailto:[e-mail]>[e-mail] <mailto:[e-mail]>> wrote:
>>> 
>>> 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, as you roam to 3G. (I switch to 3G when I get to the front of
>>> my rather modest driveway, as the AP is in the back of the basement)?
>> 
>> If anybody is currently shipping, or has announced plans to ship, any kind of home automation device that does this, please speak up on the mailing list. I’d like to calibrate my perhaps mistaken apprehension that nobody would seriously consider doing this. Everyone I know in this field plans to do this by providing a single public rendezvous point with high availability servers that communicate in turn to home automation controllers acting as private clients.


--james woodyatt <[e-mail] <mailto:[e-mail]>>