16:05:48 RRSAgent has joined #auto 16:05:48 logging to http://www.w3.org/2016/07/19-auto-irc 16:06:04 agenda+ F2F logistics 16:06:07 agenda+ Spec 16:06:19 agenda+ Security TF report 16:06:22 scribenick: ted 16:06:43 present: Adam, Powell, Ted, Kaz 16:12:13 zakim, pick up agendum 1 16:12:13 I don't understand 'pick up agendum 1', kaz 16:12:21 zakim, pick agendum 1 16:12:21 I don't understand 'pick agendum 1', kaz 16:12:21 zakim, next agendum 16:12:22 agendum 1. "WG Charter Extension" taken up [from kaz] 16:12:26 zakim, close this agendum 16:12:26 I see a speaker queue remaining and respectfully decline to close this agendum, ted 16:12:28 zakim, next agendum 16:12:29 I see a speaker queue remaining and respectfully decline to close this agendum, ted 16:12:33 zakim, next agendum 16:12:33 agendum 1 was just opened, ted 16:12:35 zakim, close this agendum 16:12:35 agendum 1 closed 16:12:36 zakim, next agendum 16:12:37 I see 3 items remaining on the agenda; the next one is 16:12:37 2. F2F logistics [from ted] 16:12:37 agendum 2. "F2F logistics" taken up [from ted] 16:12:57 -> https://www.w3.org/auto/wg/wiki/Main_Page#July_26-28.2C_2016_in_Portland.2C_OR Portland f2f wiki 16:16:00 zakim, take up agendum 3 16:16:00 agendum 3. "Spec" taken up [from ted] 16:16:04 zakim, take up agendum 4 16:16:05 agendum 4. "Security TF report" taken up [from ted] 16:16:07 -> https://lists.w3.org/Archives/Public/public-automotive/2016Jul/0011.html security call minutes 16:16:32 kaz: I was not able to attend the call either as I was at a F2F in China 16:16:44 ted was in F2F meetings at MIT 16:17:39 Adam: we started with draft report. Hashimoto plans on taking use cases, proposed architecture and strategy for security and privacy 16:17:49 - https://www.w3.org/auto/security/wiki/images/b/b4/201510_26ASPTF-Sapporo.pdf 16:18:02 s/- https/-> https/ 16:18:04 -> https://www.w3.org/auto/security/wiki/Consideration_Draft Security Consideration draft 16:18:53 s/Sapporo.pdf/Sapporo.pdf Hashimoto-san's slides on Security&Privacy/ 16:19:04 Adam: on slide 8 there are groups of use cases we collected in Google docs 16:19:37 … they are protecting communication, access control, intrusion protection, devices... 16:20:32 … also goes into multiple driver perspective - able to delegate to other drivers or their devices 16:21:08 … in the current api specification we are starting to cover layered security in the web sockets approach 16:21:47 q+ 16:23:09 Kaz: I responded to Hashimoto regarding liaison with other groups at W3C like hardware security and WoT 16:23:42 … hardware security Working Group charter was not approved so they are going to be a Community Group instead 16:25:30 Ted: basically not enough momentum yet to justify a WG but there is interest in hardware security, U2F and FIDO alliance work 16:25:42 … I'll try to find out more before our F2F 16:25:54 Kaz: Payments WG is taking that up in the meantime 16:27:50 … I have had some inquiries from other standards groups on security in automotive and will present a report next week 16:29:44 Topic: Update on Web Socket API 16:30:21 Adam: we had set bounds and signal descriptions, clarifying some earlier contention 16:30:28 … we'll go into more detail at the F2F 16:31:49 -> https://github.com/w3c/automotive/issues/85 github issue on service interface 16:34:20 -> https://www.w3.org/auto/wg/wiki/Vehicle_Information_Service_Specification vehicle information service spec draft (wiki) 16:36:49 Ted: along with sending minutes, I'll start thread on recommended readings for next week and encourage people to respond with more 16:38:01 I have made the request to generate http://www.w3.org/2016/07/19-auto-minutes.html ted 16:38:09 rrsagent, bye 16:38:16 rrsagent, bye 16:38:16 I see no action items