W3C home > Mailing lists > Public > public-web-and-tv@w3.org > November 2011

[hntf] Summary of the joint session on Device discovery

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Mon, 14 Nov 2011 09:24:15 +0100
To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <op.v4xgapnp6ugkrk@giuseppep-x220>
Hi all,
sorry for the late report.

This is a summary of the joint session on Device discovery between Web and  
TV IG and DAP WG during TPAC 2 weeks ago.
If something is not clear, feel free to ask.

- I set the context of the home network task force, highlighting  
identified gaps that the DAP WG now needs to address:
  * discovery/advertisement to allow Web applications to be aware of  
services available on the home network, and/or to advertise themselves on  
the home network.
  * communication: need to relax same origin restrictions (when CORS is not  
supported)
See presentation at:
  http://people.opera.com/giuseppep/hntf/

- Clarke presented a demo of the CableLabs/Opera proposal
  http://www.w3.org/mid/CAE1B1EF.14108%25c.stevens@cablelabs.com

- Dave Raggett presented a demo of the Webinos proposal
  http://www.w3.org/mid/4EBCF297.8070203@w3.org

- The discussion focused on security concerns triggered by exposing the  
local network to Web applications, and on possible mechanisms to reduce  
the surface of attack. Some security policy needs to be applied between  
discovery requests and responses before attempting device pairing and  
control. Exposing service details such as its address on the local network  
or its exact identity may not be needed: the UA could perhaps rather  
expose an opaque object to the JavaScript to communicate with services  
identified by the type of service they fulfill. Concerns about the idea of  
allowing application to coomunicate with UPnP devices diretly since these  
devices may have not been designed for this scenario so probably not  
enough tested for this scenario.

- Web Intents proposal was presented
  www.weintents.org

- The Web Intents proposal seems to be going in a similar direction,  
exposing services to Web applications through a broker.

- No decision was taken to adopt/reject any of the proposals. DAP will  
work on Web Intents per its charter. It is unclear at this stage whether  
Web Intents solves discovery requirements identified in the Home  
Networking Task Force, in particular in terms of supporting the protocol  
supported by the device that exposes the service. The two efforts may not  
result in a single API in the end.

- DAP will work on Web Intents in a dedicated task force and specific  
mailing-list and, pending WebApps gets re-chartered, as a joint  
deliverable between WebApps and DAP. Discussions on device discovery  
should take place in that task force as well, unless it appears clear that  
two APIs need to be defined. On-going discussions on DAP main mailing-list  
might conclude one way or the other, or leave it up to the task force to  
solve the issue:
  http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0054.html


CONCLUSION:
Participants of the Home Network TF are encouraged to join DAP, where  
further discussions will take place. We are not going to make any work in  
this IG unless required at some point in future.
Thanks to all TF members for their contribution and looking forward to  
your contribution in DAP.


-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software
Received on Monday, 14 November 2011 08:24:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 November 2011 08:24:46 GMT