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

[wot-security] minutes - 7 January 2019

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 21 Jan 2019 21:50:54 +0900
Message-ID: <CAJ8iq9UDEUqeuDH=DwLi727vYbQDEjxu2ULifqp+7kfOhXjAAQ@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:

also as text below.





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

                               - DRAFT -

                              WoT Security

07 Jan 2019


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


          Kaz_Ashimura, Michael_McCool, Elena_Reshetova,
          Tomoaki_Mizushima, Yosuke_Nakamura





     * [3]Topics
         1. [4]Agenda
         2. [5]F2F planning
         3. [6]GitHub repos for additional security documents
         4. [7]PRs
     * [8]Summary of Action Items
     * [9]Summary of Resolutions


   [10]prev minutes

     [10] https://www.w3.org/2018/12/17-wot-sec-minutes.html

   McCool: shows the TestFest result page on his PC
   ... will defer minutes review due to lack of people

F2F planning

   [11]f2f wiki

     [11] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_28_January-2_February_2019,_Princeton,_NJ,_USA

   McCool: we have security and privacy
   ... might have a Note for Security Testing Plan and Security
   Best Practices
   ... also Implementation Report
   ... and then add edits to "Rechartering" and "Administration"
   ... next f2f, workshop planning, smart cities BG coordination,
   other liaisons
   ... also adds some more edits
   ... other testing: security testing results, interoperability
   ... rechartering: IG, WG
   ... functional testing, adversarial testing

   Elena: maybe I can create some guidance?

   McCool: we need to get some examples
   ... simple demonstrations would be OK

GitHub repos for additional security documents

   [12]security bp repo

     [12] https://github.com/w3c/wot-security-best-practices

   [13]security test plan repo

     [13] https://github.com/w3c/wot-security-testing-plan

   Kaz: regarding the above repos
   ... I've just created them
   ... sorry for the delay

   McCool: ok, great
   ... nest to do is starting what to do
   ... functional testing, adversarial testing, etc.
   ... also tool section
   ... I can outline what to do
   ... will work on that


   Elena: anyone can accelerate the architecture work?

   McCool: would like to join the editors and accelerate the work

   Kaz: let me check with Matsukura-san

   McCool: ok
   ... let's close the meeting
   ... will work on the repos for security testing plan
   ... (checks if he has write permission for the repos)


Summary of Action Items

   See [14]the Action wiki.

     [14] https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#Actions

Summary of Resolutions

   [End of minutes]

    Minutes manually created (not a transcript), formatted by
    David Booth's [15]scribe.perl version 1.154 ([16]CVS log)
    $Date: 2019/01/21 12:45:53 $

     [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [16] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 21 January 2019 12:51:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:52 UTC