- From: Pfaff, Oliver <oliver.pfaff@siemens.com>
- Date: Tue, 12 Jan 2016 15:12:06 +0000
- To: "public-wot-ig@w3.org" <public-wot-ig@w3.org>
- Message-ID: <B842481327FC5344B501EC1921E8538E01411109@DEFTHW99EL2MSX.ww902.siemens.net>
I posted the following proposal (see https://www.w3.org/WoT/IG/wiki/F2F_meeting_2016,_January,_26th_-_28th,_France,_Nice): IG SP Topics Following topics shall be considered/discussed (in an SP breakout and/or joined sessions with the breakouts of other TFs). The listing does not present any particular order * Plugfest wrap-up (SP-related findings and next steps) * Finalizing the SP tech landscape<https://github.com/w3c/wot/blob/master/IG-SP/SecurityPrivacyLandscape.md> * Next step/procedure with respect to SP requirements identification<https://github.com/w3c/wot/blob/master/IG-SP/SecurityPrivacyRequirements.md> * SP integration for scripting API and protocol mappings (liaison with TF-AP) including: * How to tell the runtime (representing the callee) to enforce the presence of security credentials? * How to tell the caller to present security credentials? * How to organize that on client-side (library feature vs. application-code)? * SP integration with thing descriptions and metadata (liaison with TF-TD) including: * Whether to announce something and what (if yes) about required security credentials@TD * SP integration with thing discovery and provisioning (liaison with TF-DI) including: * Next step/procedure with respect to authorization for thing discovery * Clarification/formulation of WG items related to SP * "Friends and family" watch (IETF ACE/IRTF T2TRG, IIC, vendor initiatives...) Suggestions for addition are welcome Best regards, Oliver
Received on Tuesday, 12 January 2016 15:12:35 UTC