04:54:49 kaz has joined #auto 05:35:15 Zakim has left #auto 08:39:56 fulup-iotbzh has joined #auto 08:58:33 kaz has joined #auto 10:56:52 sam has joined #auto 13:00:16 kaz has joined #auto 17:00:38 RRSAgent has joined #auto 17:00:38 logging to http://www.w3.org/2017/02/21-auto-irc 17:00:40 RRSAgent, make logs public 17:00:40 Zakim has joined #auto 17:00:42 Zakim, this will be 17:00:42 I don't understand 'this will be', trackbot 17:00:43 Meeting: Automotive Working Group Teleconference 17:00:43 Date: 21 February 2017 17:00:45 Meeting: Auto WG 17:01:06 AdamC has joined #auto 17:01:08 Present+ Adam, Mike, Ted, Hira, Peter, Rudi, Urata 17:01:20 scribenick: ted 17:01:27 Scribe: Ted 17:01:33 Chair: Rudi 17:01:39 Chair: Rudi, Peter 17:01:59 Present+ John 17:03:04 Chair: Peter 17:03:23 Agenda+ F2F and conferene schedule 17:03:46 Agenda+ Test Suite 17:03:55 zakim, take up agendum 2 17:03:55 agendum 2. "Test Suite" taken up [from ted] 17:04:21 -> https://github.com/aShinjiroUrata/web-platform-tests/tree/dev-urata-vsss-test/vehicle-signal-server-spec Test Cases 17:05:13 Urata: we have 32 tests identified in our document 17:05:18 -> http://www.w3.org/mid/CANXs=p6Po+EQPnQF8aWbimn+F0uFaSDd6T4HtGKFTKV2S1aaYw@mail.gmail.com Urata's email 17:05:45 … I have 21 written and another dozen or so to go 17:06:12 … authentication is a bit trickier to test. I can have two tokens with different permissions 17:06:36 … we do not have enough of a description about authentication level to be able to write a test against 17:07:13 … if it is implementation dependent and will not be defined in the spec then it will be difficult for others to reuse this test suite 17:07:57 … another point is my prototype doesn't support the filter function 17:08:08 … both will take some tweaking to handle 17:09:52 Ted: I believe you are right, we left auth level to implementation and that makes it difficult to test 17:09:55 … one idea@@@ 17:10:44 Urata: there isn't a good way to test auth level 17:11:20 Adam: thank you for your work. I think the solution might be to put read/write flags in VSS data model 17:11:29 q+ 17:12:11 … we have vehicle and user level tokens. we could have a vehicle level token, user level and hybrid and different tests using the different tokens that might help 17:12:20 … I will elaborate further in github issues thread 17:12:36 Urata: do you think more needs to be added to the authentication portion of the spec? 17:12:49 Adam: there is a pull request for a more detailed example 17:13:09 … have you seen that and should we elaborate further? 17:14:08 -> https://github.com/w3c/automotive/pull/138 example pull request 17:14:39 Adam: it helps conceptualize it more 17:15:19 Urata: I will look further and comment if I think I need more 17:15:37 Peter: we are starting to look at authorization manager for our implementation here 17:15:58 … if you have different subscriptions and different tokens expiring for portions of the tree, how do you handle? 17:16:27 Adam: in the spec it says you can reset your existing authentication and build on top of it 17:17:17 John: I work for IFSF and had a similar problem years ago 17:17:35 … when you do a mobile payment for fuel there is a token generated and sent to a site 17:17:54 … we found it inadequate since it changes every time and you need to know who the person is 17:18:26 … you could use the vehicle token as a constant and use it as a means to identify the randomly generated one 17:19:08 q- 17:19:49 Adam: in section 8 of the current specification we discuss tokens for device and application 17:19:52 http://rawgit.com/w3c/automotive/gh-pages/vehicle_data/vehicle_information_service.html 17:20:09 John: can you elaborate on the device, the vehicle or a phone or? 17:20:14 Adam: the vehicle itself 17:20:34 … the infotainment unit 17:22:12 John gives some background on himself including building Shell app 17:22:28 Adam: I'm from JLR and we started using that recently 17:25:41 Ted introduces John to the WG 17:27:17 Urata: regarding the test suite topic I think I have nothing more to say at this point 17:27:52 Adam: the action will be to further discuss VSS permissions model and make sure it aligns well with section 8 of the VISS 17:29:08 -> https://github.com/w3c/automotive/issues/132 What fomat of json should be returned by getVSS()? #132 17:29:30 Ted: I closed that on a previous call when going over open issues as Urata felt his question was sufficiently answered 17:29:33 … I'll reopen 17:29:41 Adam: we did digress from the original topic 17:29:59 I have made the request to generate http://www.w3.org/2017/02/21-auto-minutes.html ted 17:30:47 Rudi: it does not make sense to expose signals that are not available 17:31:05 … not security through obscurity but trying to pair down traffic and avoid developer/app confusion 17:31:27 zakim, next agendum 17:31:27 agendum 1. "F2F and conferene schedule" taken up [from ted] 17:32:10 -> https://www.eiseverywhere.com/ehome/225965 May 9-11, 2017 Birmingham, UK 17:34:23 Ted: Thursday and Friday looks like the best but need to get confirmation still on room availability from Karin Hanson 17:35:05 … Wednesday is possible too given others' meeting schedules at AMM but would conflict with Genivi's Open day 17:35:34 … showcase is on Wednesday evening and we may get a table again but that would be disruptive to the meeting with people needing to do setup 17:35:52 Rudi: Beginning of the week I have other commitments at Genivi 17:36:24 Mike: I think Volker will represent IBM in the UK. I might be able to attend a March meeting in North America 17:37:00 Adam: I don't think that has been settled yet, leaning in the thread was 1/2 day teleconference[s] 17:37:22 Urata: Hira proposed a March F2F and people responded with teleconference idea 17:37:39 Peter: yes, limited travel budgets for two meetings so close together 17:37:57 Rudi: I started a poll to see what would work best 17:38:34 … we have had 9 responses and all have indicated that they are favorable to meet. we would need to figure out the timezones 17:38:53 Hira: what timezones are we looking at? 17:39:16 http://doodle.com/poll/yitqh6i8dq7wbrar 17:39:21 Rudi: I will quote GMT times and try to find something 17:39:49 Hira: maybe we need three times for discussion 17:39:52 pw has joined #auto 17:40:07 … for VISS, VIAS and Test Suites, one for each topic 17:40:24 mike has joined #auto 17:40:52 Rudi: I put three sessions and wanted to see based on the participants if we had any geographic/regional intersts on those topics that would help settle on times 17:41:08 … no such pattern emerged so will have to settle on arbitrary times 17:41:20 Hira: 6am in Japan is acceptable 17:41:28 Urata: that is very difficult for me 17:41:36 … 2am is in fact better 17:42:02 Peter: is a March F2F out of the question? 17:42:17 Rudi: two days plus travel time 17:46:15 teleconference +1 17:46:50 hira: f2f 17:46:52 peter: f2f 17:47:00 adam: teleconference 17:47:04 rudi: teleconference 17:47:14 urata: either ok 17:47:23 john: abstains 17:49:47 [VISS editors in Europe so should favor that timezone for that call, Powell is our VIAS editor so check with his availability, Urata has done all the Test Suite work so Asian friendly for that call] 17:50:24 Rudi: Propose week of 5 March 17:50:34 i'm open, flexible 17:50:42 Peter: regrets that week 17:50:55 Rudi: week of 12 March 17:51:25 Adam: ok for me except Friday 17:51:42 … our BG meeting is on that Tuesday 17:52:27 Ted: I was hoping to delve into payments on that BG call. if we can avoid that hour that would be my preference but otherwise alright 17:54:01 Urata: this is prepration for moving the spec to CR 17:54:14 … after these meetings can we expect to be ready for that? 17:54:21 Rudi: that is my expectation as well 17:54:43 Urata: we should work on agenda for each meeting 17:55:02 … is that clear yet? 17:56:47 Ted: I will start an agenda on a wiki. Chairs control the agenda so may revise as could people based on their specific areas who know about different issues 17:57:14 Urata: we need some prototype implementation for VIAS and test suite for it 17:57:34 … I am concerned if that spec will make that schedule 17:57:45 Hira: we have yet to publish FPWD for VIAS 17:57:53 … after we need wide review 17:59:38 https://www.w3.org/2015/Process-20150901/ 18:01:06 Ted: I share the conern about VIAS schedule. when Powell is ready and this group has reviewed it I can publish 18:01:43 … my quick read of the process document suggests we need 4 weeks at FPWD before we can go to CR 18:02:37 … I encourage people to start looking at Powell's work. there has been relatively little feedback so far 18:02:46 Peter: I have done some 18:02:52 Urata: I will as well 18:03:22 Peter: I am working on our service implementation this week and will look for a colleague to review it 18:04:47 … phone conference will be on week 11, specific times pending 18:04:59 [adjourned] 18:05:10 I have made the request to generate http://www.w3.org/2017/02/21-auto-minutes.html ted 18:05:55 s/one idea@@@/one idea is to have a known restricted signal to try to access and expect it to be refused/ 18:05:56 I have made the request to generate http://www.w3.org/2017/02/21-auto-minutes.html ted 18:06:05 leaving. As of this point the attendees have been Adam, Mike, Ted, Hira, Peter, Rudi, Urata, John 18:06:05 Zakim has left #auto 18:06:06 I see no action items