17:53:48 RRSAgent has joined #auto 17:53:48 logging to https://www.w3.org/2021/02/01-auto-irc 17:53:50 RRSAgent, make logs Public 17:53:51 Meeting: Automotive Working Group Teleconference 17:53:52 scribenick: ted 17:53:55 Meeting: RPC 17:53:57 Present+ Ted 18:01:38 Present+ MagnusF, Ulf 18:01:45 Present+ Glenn 18:03:02 Present+ Gunnar 18:07:01 [Magnus discusses presentation for upcoming webinar 18 February but cannot share until approved by Toyota] 18:08:39 [Ted mentions he is encouraging Autonomic to provide service candidates for catalog] 18:08:46 Present+ Rudi 18:13:21 MagnusF: back to use cases then. assume these to be external interaction only or include internal eg hvac, seating etc? 18:13:29 Ted: don't see reason to exclude internal 18:14:14 Gunnar: question exists on whether to use VISS/VSS internal to vehicle as well 18:15:02 … seems contrary to SOME/IP but some moving more towards regular network in-vehicle 18:15:19 Rudi: having a unified method in and outside the vehicle has clear benefits 18:15:41 … people are familiar with existing use cases and advantages it could bring 18:16:19 Gunnar: back to original point, Magnus you're looking for clear scope 18:16:24 MagnusF: correct 18:17:07 Gunnar: CVII tech stack conversation it in and outside the vehicle 18:17:42 … cloud to vehicle can use this protocol (VISS) but how do you invoke AutoSAR services... 18:18:29 MagnusF: we may want to explore bring your own device. a generic interface service for a properly authenticated and authorized device 18:18:58 … and can give paired down functionality to the kids in the back seat 18:20:04 Rudi: another question is there is overlap with VSS/VISS for signals and keep VSC for functions 18:20:55 MagnusF: I can support multiple protocols and could easily intergrate others if sufficient libraries exist such as SOME/IP 18:22:26 Gunnar: we have a large number of areas under CVII, where we can provide some concrete work items helps 18:24:38 MagnusF: let's go back to the domains themselves 18:25:04 … are we coming up with explicit, complete functions or smaller functions for exposure to developers 18:25:49 Gunnar: do we go with AGL definitions for infotainment services? 18:26:27 s/AGL/specific/ 18:26:28 I have made the request to generate https://www.w3.org/2021/02/01-auto-minutes.html ted 18:27:08 MagnusF: good question, some seem appropriate while others not 18:35:03 Glenn: there are financial interests, eg on vehicle loan related use cases 18:36:02 MagnusF: such as remotely disable ignition, makes sense. if you know anyone that can provide details for such would be helpful 18:36:20 … this would be handled with PKI and need regular certificate renewals 18:37:01 Glenn: ideal would be capability at manufacturer and allow enabling per fleet 18:38:25 MagnusF: any discussion with truck guys? 18:40:20 Ted: ongoing with Daimler, Volvo trucking - could also reach out to NMFTA 18:41:01 MagnusF: difference is heavy trucks are invariably in managed fleets 18:41:47 Glenn: they also produced an API for heavy vehicles 18:42:24 … there are regulations on telematics for vehicles 18:42:56 [Discussion of presentation at webinar] 18:44:34 https://github.com/nmfta-repo/nmfta-opentelematics-api 18:51:21 I have made the request to generate https://www.w3.org/2021/02/01-auto-minutes.html ted 18:52:25 Gunnar: part of problem is there are a few of these parallel but narrowly focused efforts on eg remote unlock, such as CCC 18:52:41 … there still should be a common, multi-function capability 18:52:54 … why exclude it? 18:54:24 Ted: we might be able to do with a thin layer and should look at that 18:55:37 … also with WoT glasses 18:58:20 https://carconnectivity.org/digital-key/