W3C home > Mailing lists > Public > public-wot-wg@w3.org > February 2020

[wot-security] minutes - 13 January 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Tue, 11 Feb 2020 17:26:32 +0900
Message-ID: <871rr1v8av.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/01/13-wot-sec-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                              WoT-Security

13 Jan 2020

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#13_Jan_2020

Attendees

   Present
          Kaz_Ashimura, Michael_McCool, Elena_Reshetova,
          Tomoaki_Mizushima, Zoltan_Kis

   Regrets

   Chair
          McCool

   Scribe
          kaz

Contents

     * [3]Topics
         1. [4]Review minutes
         2. [5]Lifecycle
         3. [6]Discovery
         4. [7]PRs
         5. [8]Issues
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

Review minutes

   McCool: given we're making all the TF minutes public and some
   of the TFs would like to have some review periods, we should be
   consistent
   ... e.g., two-day review period like the Scripting TF
   ... (going through the previous minutes)

   [11]Previous minutes

     [11] https://www.w3.org/2019/12/16-wot-sec-minutes.html

   McCool: bunch of stuff for todo list
   ... should clarify that we still need to discuss IETF Anima
   ... other than that, OK to accept the minutes?

   (no objections)

   McCool: the minutes accepted

Lifecycle

   Elena: to have discussion with Zoltan

   McCool: are we ready to delete lifecycle portion from the
   Security note?

   Elena: still need to have some more discussion
   ... some discussion done during the Architecture call last
   week, though

   McCool: can join the Architecture first call this week?

   Elena: trying to provide input

   McCool: please input our proposal
   ... and wait until the Architecture draft is done

Discovery

   McCool: next item is discovery
   ... privacy and security considerations

   <McCool>
   [12]https://github.com/w3c/wot/blob/master/proposals/wot-discov
   ery.md

     [12] https://github.com/w3c/wot/blob/master/proposals/wot-discovery.md

   McCool: the above is the draft Discovery considerations
   ... use cases to be added
   ... number of things to be done
   ... probably need to discuss guidelines first
   ... that is a heads-up
   ... need to go back to GoDaddy guys and IETF guys
   ... also need to see IETF Anima
   ... by the end of March, would have clearer view
   ... questions?

   (none)

PRs

   [13]PR 150

     [13] https://github.com/w3c/wot-security/pull/150

   McCool: still leave it out

Issues

   [14]Issue 151

     [14] https://github.com/w3c/wot-security/issues/151

   McCool: Elena is working on this
   ... could you make a comment here?
   ... or a pointer to another issue?

   Elena: ok

   [15]Issue 149

     [15] https://github.com/w3c/wot-security/issues/149

   McCool: still pending

   [16]Issue 147

     [16] https://github.com/w3c/wot-security/issues/147

   McCool: covered by a PR (150)

   [17]Issue 148

     [17] https://github.com/w3c/wot-security/issues/148

   McCool: need to sort out terminology
   ... wondering about the profile discussion
   ... still done within the Architecture call?

   Kaz: yes

   McCool: it seems we have security roles, and other roles to be
   defined within the Architecture
   ... mapping with specific protocols as well
   ... still pending

   [18]Issue 142

     [18] https://github.com/w3c/wot-security/issues/142

   McCool: syntactic change
   ... "HTTP over TLS" and "CoAP over DTLS"
   ... "HTTPS" => "HTTP-over-TLS"
   ... "CoAPS" => "CoAP-over-DTLS"

   [19]Issue 143

     [19] https://github.com/w3c/wot-security/issues/143

   McCool: assigned myself to this issue
   ... should ask the PING for a definition or a reference

   [20]Issue 125

     [20] https://github.com/w3c/wot-security/issues/125

   Elena: can close it

   McCool: has been done and the Architecture doc has been
   published
   ... consider this closed

   [21]CR2 version of WoT Architecture

     [21] https://www.w3.org/TR/2019/CR-wot-architecture-20191106/

   McCool: close Issue 125

   [22]Issue 136

     [22] https://github.com/w3c/wot-security/issues/136

   McCool: issue of lifecycle is included in the new WoT WG
   Charter
   ... security and privacy sections of the TD and Architecture
   documents were updated as part of the CR2/PR review cycle
   ... information lifecycle (and the device lifecycle) are now
   part of the WoT WG Charter renewal and are being discussed in
   Architecture
   ... so this can be closed for now
   ... questions?

   (none)

   McCool: closes Issue 136
   ... AOB for today?

   (none)

   McCool: let's think about the other issues next week

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [23]scribe.perl version 1.154 ([24]CVS log)
    $Date: 2020/01/15 11:42:16 $

     [23] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [24] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 11 February 2020 08:26:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 11 February 2020 08:26:42 UTC