Meeting logistics

junichi: would like to hold this call monthly
... so the next call will be 21 of June

kaz: June 21 is the 3rd Tuesday

junichi: in that case, let's have the next call on the 28th of June
... we'll have our next f2f meeting in Portland in July
... would like to suggest the TF note by that meeting
... and at the Portland meeting, would like to ask the WG for comments
... and we can revise that Note
... and during the TPAC 2016 in Lisbon, we can ask other groups, e.g., Web App Security WG, for comments

Note: There was some more discussion about the next call time at the end of the call again, and the conclusion was "Junichi's generating another Doodle poll and ask people preference. See also the "Next call" section.

Security consideration note

<junichi-hashimoto> https://www.w3.org/auto/security/wiki/Consideration_Draft

junichi: put ideas on the above wiki page

magnaus: can't access the wiki...

<junichi-hashimoto> https://w3c.github.io/automotive/vehicle_data/security/

junichi: the content is almost same with the above GitHub repo
... would like to ask you all to update the content of the Note
... so have copied the content to the wiki space

kaz: if needed we can create a public wiki for this purpose

magnus: currently I don't have permission

kaz: will send a request to the AC Rep. CCing you

junichi: the current Note, there are 5 sections
... section 1 is introduction, and section 2 is architecture
... would like to ask Adam and Kevin to review and revise the architecture section

adam: can take Kevin's architecture

kevin: we can adapt

kaz: Junichi, do you want Kevin and Adam to merge their architecture with this section?

junichi: at this moment, not sure if we can describe whole the JLR architecture, though

<junichi-hashimoto> https://www.w3.org/2016/04/auto-f2f/28/DSC_0073.JPG

kaz: so your intention is not putting the JLR architecture diagram itself into this document
... but rather asking them for review?

junichi: yes
... puts the URL of Paul's diagram from the Paris meeting

kaz: in that case, you can put this picture itself into the wiki and the GitHub

junichi: ok
... by the next call, I'll update the Note
... if you have any idea to be added, please make your contribution directly on the wiki

kaz: when the section 2 will be fixed for the review?

junichi: section 2 is already fixed

volker: would be better to have the picture as well

kaz: +1

junichi: will do it later
... would like to confirm the timeline
... finish this document (Security Consideration) by TPAC 2016
... not sure we can/should include security consideration into the Vehicle Service Spec
... probably based on another timeline

kaz: we need more discussion with the main WG about that

junichi: ok
... from my side, that's all for today

Next call

volker: have a question
... relationship between the wiki and the GitHub repo

junichi: will put the materials from the GitHub to the wiki so that people can edit it easily
... and later will bring the materials back to GitHub

volker: ok

kaz: sounds good

volker: do we have a US-friendly call and a JP/EU-friendly call alternatively?

junichi: given the participation so far, JP/EU-friendly call would make sense
... the next call will be held on June 28th

volker: will have a full-day workshop and can't make it
... Monday would be better

(some more discussion)

junichi: will send another doodle then :)
... see you next month!

[ adjourned ]