Re: Network Service Discovery API

Dear Alexander

Le 12/2/14 12:33 , Alexander Adolf a écrit :
> (1) Obscure all information about the device*except*  the friendlyName by replacing it with a per-session hash value before exposing it to the web app. That way it will not be possible to infer information that would potentially help in figuring out exploits (IP address, model, make, etc.), but if anything were to go back to the device, the NSD APU implementation would still be able to map it back to the actual values before sending to the device or searching the data. friendlyName is required, because the web app should be able to present the user a choice of devices to use (e.g. to select on which printer to print).
>
JCD: This was discussed, and here is one exchange: my proposal (with 
elements similar to yours) and Rich's response
http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0062.html
http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0065.html

How would the rest of the web app work in your case ?
I advocate the extension of NSD to include messaging, but how would you 
handle messaging ?

Best regards
JC
-- 
Télécom ParisTech <http://www.telecom-paristech.fr> 	*Jean-Claude 
DUFOURD <http://jcdufourd.wp.mines-telecom.fr>*
Directeur d'études
Tél. : +33 1 45 81 77 33 	37-39 rue Dareau
75014 Paris, France

Site web <http://www.telecom-paristech.fr>Twitter 
<https://twitter.com/TelecomPTech>Facebook 
<https://www.facebook.com/TelecomParisTech>Google+ 
<https://plus.google.com/111525064771175271294>Blog 
<http://jcdufourd.wp.mines-telecom.fr>