15:59:15 RRSAgent has joined #auto 15:59:15 logging to http://www.w3.org/2015/11/24-auto-irc 16:00:06 urata_access has joined #auto 16:00:36 Present: Paul_Boyes, Kaz_Ashimura, Qing_An, Shinjiro_Urata, Yingying_Chen 16:01:40 Present: Paul_Boyes, Dave_Jensen, Kaz_Ashimura, Qing_An, Shinjiro_Urata, Yingying_Chen 16:02:41 Present: Paul_Boyes, Adam_Crofts, Dave_Jensen, Kaz_Ashimura, Qing_An, Shinjiro_Urata, Yingying_Chen 16:03:11 Present: Paul_Boyes, Adam_Crofts, Dave_Jensen, Junichi_Hashimoto, Kaz_Ashimura, Qing_An, Shinjiro_Urata, Yingying_Chen 16:03:19 junichi-hashimoto has joined #auto 16:03:46 KevG has joined #auto 16:05:32 paul has joined #auto 16:06:20 topic: agenda 16:06:39 paul: spec timeline, security update, etc. 16:06:59 agenda: https://lists.w3.org/Archives/Public/public-automotive/2015Nov/0017.html 16:07:50 -> https://www.w3.org/auto/wg/wiki/Main_Page#Publication_Schedule publication schedule so far 16:07:51 AdamC has joined #auto 16:08:31 kaz: we should update the timeline 16:08:39 ... FPWD already done 16:08:43 https://www.w3.org/auto/wg/wiki/Main_Page 16:08:53 ... and we're preparing the second draft 16:09:02 paul: LC/CR should be later 16:09:44 kaz: maybe Q2 2016 16:10:02 paul: so PR and REC for Q4 2016 16:10:24 ... we'll work for the testing and implementation as well next year 16:10:45 present+ Peter_Winzell 16:11:12 ... Genivi is doing one 16:12:18 @@@: started to see how to implement on Google Chrome 16:12:39 s/@@@/peter/ 16:12:55 ... and outlook how to test it 16:13:22 ... collaboration with Genivi would be good 16:13:28 paul: right 16:13:59 ... willing to take an action to see what would happen in US and Genivi 16:14:22 ... we can get some small loop to work together 16:14:45 ... making proposal and align things 16:15:15 peter: started with Chromium 16:15:21 ... how to add interfaces 16:15:38 ... you can use the browser itself 16:16:00 ... I don't know if that is the best choice, though 16:16:21 paul: anybody who work with Chromium could use that, so that's good 16:16:50 ... for typical cars 16:16:59 peter: think so 16:17:34 ... but don't think you can do that on your PCs 16:17:57 ... could do if you have some recorder 16:18:15 paul: Kevin and Adam? 16:18:31 kevin: not typically CAN logs 16:18:35 ... but we could do 16:18:42 q+ 16:19:08 @@@: we've been testing head units 16:19:30 s/@@@/peter/ 16:19:53 dave: think ACCESS has something 16:20:10 paul: we can record data and use some simulator 16:20:37 ... JLR has some mechanism 16:21:24 ... let me sense 16:21:50 ... have to see definition 16:22:04 ... any comments from Urata-san? 16:22:05 q? 16:22:18 urata: using some property from dongle 16:22:31 ... getting CAN data from the dongle device 16:22:43 s/from/via/ 16:22:53 ... translate CAN data to JSON 16:23:11 ... could be a reference model 16:23:30 paul: Dave, do you have any experience? 16:23:50 dave: open xd has some project 16:24:01 ... hardware is open 16:24:10 ... proprietary binary format 16:24:41 ... convert the output data to JSON 16:25:05 paul: also interested in what Google is doing 16:25:18 ... how we can get/record data? 16:25:35 ... e.g., using chrome 16:26:04 ... various possibilities 16:26:32 dave: would take an action to see what would be available 16:26:51 ... not sure what the actual state 16:26:59 paul: most people should consider 16:27:10 dave: try to contact Genivi 16:27:20 paul: e.g., Gunnar? 16:27:22 dave: yes 16:27:33 ... will ask him 16:28:10 ... the best is something open 16:29:04 s/dave:/peter:/ 16:29:06 s/dave:/peter:/ 16:29:08 s/dave:/peter:/ 16:29:32 dave: would see OpenXC 16:29:39 paul: anything from JLR? 16:30:17 kevin: CAN data database 16:30:36 paul: Kevron or somebody from Poland 16:30:54 ... non-production implementation 16:31:22 ... Peter, you sent an email regarding what the test plan would be 16:31:58 peter: part of the implementation I'm doing 16:32:22 paul: would people be interested in TF work? 16:32:24 q? 16:32:28 q- 16:32:52 peter: working on that everyday 16:33:05 paul: is anybody else interested? 16:33:19 peter: interested in how ACCESS thinking about testing 16:33:24 q+ 16:33:55 dave: interested in how the other groups working on testing 16:34:39 kaz: usually groups form a TF for testing 16:34:53 ... and people work collaboratively for that purpose 16:35:05 paul: yes, that' my suggestion 16:35:31 ... urata-san, are you willing to join it? 16:35:50 urata: interested but have time restriction... 16:36:06 ... can contribute very little... 16:36:31 paul: would send out a message to ask people for participation 16:36:37 ... we can coordinate 16:37:10 ... understanding implementation, etc. 16:37:15 dave: interested 16:37:32 paul: will send an email then 16:37:50 ... peter, you can arrange the agenda 16:37:50 peter: ok 16:38:10 kevin: interested and possibly make contribution 16:39:19 kaz: we'll discuss not only implementation experience but also testing mechanism? 16:39:25 paul: yeah 16:40:08 kaz: we need to generate test assertions and test suite 16:40:16 ... also would be nicer to have testing environment 16:40:50 dave: automated tools would be helpful and worth consideration 16:41:06 q- 16:41:11 topic: Security update 16:41:57 junichi: access control 16:42:04 ... for auto makers and implementers 16:42:19 ... have been looking Web security specs 16:42:28 ... manifest is permission list 16:42:47 ... focused on icons 16:43:01 ... another one is application mechanism 16:43:12 ... controlled by implementers 16:43:26 ... difficult to use for access control by auto makers 16:43:50 ... we should consider approval of developers 16:43:59 ... approving specific URL domains 16:44:13 ... thinking of some root certificate 16:44:33 ... vehicle APIs only approved domains 16:44:50 ... would finish by the end of this month 16:44:58 ... do you like the idea? 16:45:01 paul: yeah 16:45:13 junichi: feasibility, urata-san? 16:45:28 urata: with the restricted domain list? 16:46:05 junichi: usually all APIs are openly used by any domains 16:46:28 urata: W3C widgets spec is kind of old 16:46:38 ... but handles manifest and packaged apps 16:46:49 ... maybe similar to your idea 16:47:10 junichi: currently we don't have a packaged format 16:47:25 urata: Firefox can use packaged formats 16:48:00 ... from app security perspective, that kind of packaged apps would be effective 16:48:10 ... maybe one candidate 16:48:34 ... would listen to other approaches as well 16:48:51 kevin: token? 16:49:06 ... basically have an authentication service 16:49:15 ... to authenticate and verify the app 16:49:20 ... e.g., using password 16:49:28 ... facial recognition 16:50:59 ... optionally authenticate the vehicle or infrastructure, local government, highway agency, etc. 16:51:42 ... assistance to get vehicle location, etc. 16:51:59 ... authentication token attached to the HTTP header 16:52:13 ... authorizing the access to the data 16:52:27 junichi: do we need to introduce a new HTTP header? 16:53:12 kevin: two tokens on a request 16:53:33 ... one token representing the user and another representing the vehicle or something 16:53:41 ... separate tokens are possible 16:54:12 junichi: several approaches we discussed during TPAC f2f 16:54:17 ... token was one of them 16:54:25 ... another was having a proxy 16:54:41 kevin: like having a secure proxy 16:55:07 junichi: introducing a big mechanism would cost much for implementers 16:55:17 ... so would start with light-weight approach 16:55:57 kevin: in terms of modification of spec, there would be minimum changes 16:56:04 ... not mandatory 16:56:36 kevin: happy to write an idea to access tokens 16:57:01 ... not clear how to handle that within the spec, though 16:57:16 paul: we could add that as informative notes 16:58:05 ... basically we could add that to some informative section 16:58:54 kevin: can write some wording 17:00:07 ... for an informative section 17:00:13 kaz: yes, we can do so 17:00:33 paul: makes sense 17:00:50 ... Kevin will generate some description 17:01:08 ... Hashimoto-san, are you interested in adding something? 17:01:11 junichi: yes 17:01:44 paul: Peter will work on implementation/testing TF 17:02:00 ... myself will work with Adam and Dave for Genivi 17:02:16 dave: still not much discussion on event handling 17:02:28 ... would be great to have input from Urata-san, etc. 17:02:42 s/dave:/AdamC 17:03:03 s/AdamC/AdamC: 17:04:05 adamC: vehicle enum should be changed 17:07:55 paul: Adam, you might want to summarize the discussion 17:08:16 kaz: should we ask TAG for some more help? 17:08:36 paul: Tobie made some suggestion during TPAC 17:08:52 kaz: yeah, Generic Sensor style is one possibility 17:09:09 paul: can send a message to TAG 17:09:27 ... anything else? 17:09:29 (nothing) 17:10:14 paul: will have the next call next week. 17:11:00 [ adjourned ] 17:11:05 rrsagent, make log public 17:11:10 rrsagent, draft minutes 17:11:10 I have made the request to generate http://www.w3.org/2015/11/24-auto-minutes.html kaz 17:11:38 Meeting: Automotive WG 17:11:41 Chair: Paul 17:11:43 rrsagent, draft minutes 17:11:43 I have made the request to generate http://www.w3.org/2015/11/24-auto-minutes.html kaz 17:12:23 i/we should update the/topic: Publication schedule/ 17:12:56 i/we'll work for/topic: Implementations and Testing/ 17:13:16 s/implement on Google Chrome/implement on Chromium/ 17:13:19 rrsagent, draft minutes 17:13:19 I have made the request to generate http://www.w3.org/2015/11/24-auto-minutes.html kaz 17:14:53 i/Peter will work on/topic: Wrap-up/ 17:14:56 rrsagent, draft minutes 17:14:56 I have made the request to generate http://www.w3.org/2015/11/24-auto-minutes.html kaz 19:06:10 Zakim has left #auto