W3C home > Mailing lists > Public > public-wot-wg@w3.org > January 2021

[wot-security] minutes - 7 December 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Tue, 19 Jan 2021 22:21:24 +0900
Message-ID: <87r1mh3vvv.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/12/07-wot-sec-minutes.html

also as text below.

Thanks a lot for taking th minuts, Oliver!

Kazuyuki

---
   [1]W3C

      [1] http://www.w3.org/

                              WoT Security

07 Dec 2020

Attendees

   Present
          Kaz_Ashimura, Michael_McCool, Elena_Reshetova,
          Oliver_Pfaff, Tomoaki_Mizushima

   Regrets

   Chair
          McCool

   Scribe
          Oliver

Contents

     * [2]Topics
         1. [3]Prev minutes
         2. [4]Publication schedule
         3. [5]Issues
     * [6]Summary of Action Items
     * [7]Summary of Resolutions
     __________________________________________________________

   <kaz> scribenick: Oliver

Prev minutes

   <kaz> [8]Nov-30

      [8] https://www.w3.org/2020/11/30-wot-sec-minutes.html

   Review of minutes for the wot-sec call 2020-11-30

   No change requests/comments for the minutes. They can be
   published

Publication schedule

   Next are quick updates: schedule/milestones were reviewed and
   acknowledged (during other meetings before): stable drafts
   needed for May 01

   wot-wg charter has a list of items to be covered in 1.1

   <kaz> [9]WoT-WG Charter

      [9] https://www.w3.org/2020/01/wot-wg-charter.html

   However a more specific list of items would be helpful (the
   charter provides a generic/abstract perspective)

   Github-native features e.g. notifications could help to improve
   team interactions while working on issues towards an updated
   draft

Issues

   Discussion on
   [10]https://github.com/w3c/wot-thing-description/issues/998

     [10] https://github.com/w3c/wot-thing-description/issues/998

   The 'API key' approach often is vendor/supplier-specific. Can
   mean different things (encodings...) for different
   vendors/suppliers

   PSK is not necessarily equivalent to "API key"

   For PSK usage in conjunction with (D)TLS see
   [11]https://www.iana.org/assignments/tls-parameters/tls-paramet
   ers.xhtml#tls-parameters-4

     [11] https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4

   <kaz> [12]wot-thing-description issue 965

     [12] https://github.com/w3c/wot-thing-description/issues/965

   Discussion on
   [13]https://github.com/w3c/wot-thing-description/issues/965

     [13] https://github.com/w3c/wot-thing-description/issues/965

   Can be closed without actual action (overlapping, can be done
   later)

   No call 2020-12-14, next wot-sec call should be expected for
   Jan. 21

   <kaz> [adjourned]

   Meeting closed

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [14]scribe.perl version ([15]CVS log)
    $Date: 2021/01/19 13:21:01 $

     [14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [15] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 19 January 2021 13:21:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 January 2021 13:21:45 UTC