- From: Ted Guild <ted@w3.org>
- Date: Mon, 11 Sep 2017 16:20:15 -0400
- To: www-tag@w3.org
- Message-ID: <1505161215.2752.148.camel@w3.org>
On Mon, 2017-09-11 at 15:51 -0400, Ted Guild wrote: > TAG, > > I am asking for your guidance on something that has been awkward and > unresolved for some time. > > For Automotive we are defining a service that will reside on a > vehicle's local network. This service is not meant to be addressed > publicly, ever, out of privacy and security considerations. > > In the present spec draft we have a hard-coded hostname, wwwivi. It > will be used in wss:// and potentially later https:// URIs. > > Appending .localhost or .localdomain will add some clarity. The local > network should be able to handle resolution of any hostname. I meant to give the GH issue link instead. https://github.com/w3c/automotive/issues/223 > https://lists.w3.org/Archives/Team/team-auto/2017Sep/0011.html > > I would suspect there may be similar concerns for Web of Things, > Second > Screen and other activities. They may be more suitable to network > discovery protocols due to adhoc nature of things and screen services > becoming available on a network. We feel it would be preferable to be > rigidly defined to prevent eg an impersonating service or introducing > latency. > -- Ted Guild <ted@w3.org> W3C Systems Team http://www.w3.org
Received on Monday, 11 September 2017 20:20:17 UTC