12:01:09 <RRSAgent> RRSAgent has joined #wot-sec
12:01:09 <RRSAgent> logging to https://www.w3.org/2019/09/02-wot-sec-irc
12:01:13 <kaz> Meeting: WoT Security
12:01:29 <kaz> present+ Kaz_Ashimura, Elena_Reshetova, Michael_McCool
12:07:41 <McCool> McCool has joined #wot-sec
12:08:33 <kaz> scribenick: kaz
12:09:09 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#Agenda
12:09:17 <kaz> topic: Review minutes
12:09:33 <kaz> -> https://www.w3.org/2019/08/26-wot-sec-minutes.html Aug-26 minutes
12:09:42 <kaz> mm: don't see any problems
12:09:51 <kaz> ... objections to accept the minutes?
12:09:54 <kaz> (no objections)
12:09:57 <kaz> mm: accepted
12:10:16 <kaz> topic: Rescheduling the security call
12:10:29 <kaz> -> https://doodle.com/poll/uygq7wtn75syw8h2 Doodle
12:10:54 <kaz> mm: Taki can't make Monday
12:11:11 <kaz> ... any preference on the slots on Monday?
12:11:16 <kaz> er: no preference
12:11:31 <kaz> mm: prefer the later time
12:11:33 <kaz> kaz: me too
12:11:48 <kaz> mm: so let's go with 7am JST
12:12:30 <kaz> action: kaz to allocate a new webex and distribute it for the next week
12:12:38 <kaz> kaz: will do
12:12:58 <kaz> mm: after talking with Taki, we might be going to change the slot again
12:13:05 <kaz> (Zoltan joins)
12:13:17 <kaz> mm: Zoltan, we were talking about the new slot for the Security call
12:13:22 <kaz> ... (explains the situation)
12:13:58 <kaz> er: it's 1pm in Finland
12:14:02 <kaz> zk: ok
12:14:37 <kaz> ... fine by me though might be a bit late
12:15:17 <kaz> topic: WG Charter draft
12:16:01 <kaz> -> https://github.com/w3c/wot/pull/856 PR 856
12:16:02 <McCool> https://github.com/w3c/wot/blob/master/charters/wot-wg-charter-draft-2019.html
12:16:12 <kaz> mm: the initial PR (PR 856) has been merged
12:17:16 <kaz> http://w3c.github.io/wot/charters/wot-wg-charter-draft-2019.html
12:17:44 <kaz> mm: rendered version above
12:17:50 <kaz> ... as far as security goes
12:18:04 <kaz> ... topics on security within "2. Scope"
12:18:24 <kaz> ... also Interoperability Profiles
12:18:29 <kaz> ... Discovery
12:18:40 <kaz> ... need to work with the Privacy group
12:18:55 <kaz> ... security aspects for Implementation View Spec as well
12:19:42 <kaz> ... 2.6 Discovery
12:20:02 <kaz> ... we have to define deliverables
12:20:19 <kaz> ... possibly break out into 2 pieces
12:20:42 <kaz> ... introduction and exploration
12:21:12 <kaz> ... peer-to-peer discovery could be supported as a special case
12:21:24 <kaz> ... have to coordinate with IETF, etc.
12:21:35 <kaz> ... need more general context here
12:21:43 <kaz> ... 2.7 Identity Management
12:22:04 <kaz> ... Kaz mentioned there is a proposed WG named the Decentralized ID WG
12:22:10 <kaz> ... should collaborate with them
12:22:37 <kaz> ... kind of like ID management lifecycle
12:22:56 <kaz> ... e.g., please notify me when the ID management changes
12:23:08 <kaz> ... device with right access to be handled
12:23:33 <kaz> ... we have a deliverable down here ("3. Deliverables")
12:23:51 <kaz> ... we need to create repos for those deliverables
12:24:01 <kaz> ... would like to start soon
12:24:10 <kaz> ... Michael Lagally is generating draft as well
12:24:43 <kaz> ... any comments?
12:24:51 <kaz> zk: discovery for WoT?
12:25:04 <kaz> ... do we want to define ourselves?
12:25:05 <kaz> mm: good point
12:25:15 <kaz> ... have predescribed script
12:25:32 <kaz> ... in fact we're doing how to distribute things
12:25:44 <kaz> ... because existing devices don't distribute TDs
12:26:04 <kaz> zk: distributing script as well?
12:26:04 <kaz> mm: maybe
12:26:10 <kaz> s/maybe/may be/
12:26:20 <kaz> zk: some king of manifest of something
12:26:30 <kaz> ... some kind of package
12:26:32 <kaz> s/king/kind/
12:26:48 <kaz> mm: bunch of things that are listed as "Notes"
12:27:15 <kaz> ... normative deliverables are extracted from the powerpoint we discussed in Munich
12:27:40 <kaz> zk: was there any deliverable which can be included as Note?
12:27:44 <kaz> mm: hold on...
12:28:17 <kaz> ... (shares the powerpoint slide from Munich)
12:28:44 <kaz> ... other things used to on the REC track
12:29:05 <kaz> ... essentially deployment model and packaging
12:29:13 <kaz> ... WG Charter can be changed later
12:29:23 <kaz> ... what we should do is
12:29:45 <kaz> ... if you think deployment/packaging mechanism for Scripting would be useful, you can create a PR for that proposal
12:29:56 <kaz> ... the current list is generated from the powerpoint in Munich
12:30:04 <kaz> zk: ok
12:30:08 <kaz> ... some provisions to associate things
12:30:23 <kaz> ... should be contained to Scripting distribution mechanism
12:30:33 <kaz> mm: 2 kinds of dependency
12:30:42 <kaz> ... MPM kind of packaging
12:30:48 <kaz> ... and function
12:31:36 <kaz> ... query mechanism and installation mechanism
12:31:53 <kaz> zk: we don't have to re-invent generic distribution mechanism
12:32:09 <kaz> mm: packaging of script
12:32:14 <kaz> ... there is dependency
12:32:18 <kaz> ... 2 parts of manifest
12:32:26 <kaz> s/MPM/NPM/
12:32:34 <kaz> ... very interesting
12:33:04 <kaz> zk: let's say I discover things and would know about the capability of scripts
12:33:09 <kaz> ... up to the clients
12:33:52 <kaz> mm: please review this draft Charter
12:34:04 <kaz> ... and also proposals from Michael Lagally
12:34:36 <kaz> -> https://w3c.github.io/wot-profile/ wot-profile proposal
12:35:00 <kaz> (Elena leaves)
12:35:38 <kaz> mm: what is the right context to handle the context?
12:35:47 <kaz> ... have been talking about the orchestrator
12:36:06 <kaz> ... e.g., Panasonic, etc., use node-red
12:36:41 <kaz> q+
12:38:04 <kaz> mm: we could add another deliverable for management script
12:38:16 <kaz> ... need context for interoperability
12:38:42 <kaz> ... just like profile, we need draft text which describes the context and the basic architecture
12:38:47 <kaz> ... would be useful to do
12:39:37 <kaz> ... personally started to think Scripting API could be a Note by the IG
12:39:54 <kaz> ... IG should be incubating the requirements
12:40:24 <kaz> zk: it's specific to node-wot and typescript
12:40:36 <kaz> mm: we could add management API
12:40:46 <kaz> ... with packaging capability
12:41:05 <kaz> zk: JS is the language supported by Web browsers
12:41:25 <kaz> ... that might be one way to go for something like Web Assembly
12:41:46 <kaz> mm: what to be contained for packaging?
12:42:06 <kaz> ... those things could be interesting
12:42:23 <kaz> zk: right now we have JS runtime
12:42:35 <kaz> ... there are some issues to tackle
12:42:46 <kaz> ... it's something would make sense
12:42:56 <kaz> ... but not directly related to WoT
12:43:32 <kaz> mm: if we go for more general mechanism for packaging
12:44:08 <kaz> ... need a draft text to be included in the draft Charter
12:44:27 <kaz> ... need same thing for packaging and/or management API
12:45:40 <kaz> kaz: it sounds like object-oriented programming
12:45:57 <kaz> ... how to combine the TD model and Scripting API as a possible method for the data model
12:46:24 <kaz> mm: would create an issue about this point
12:51:20 <McCool> https://github.com/w3c/wot/issues/861
12:52:39 <kaz> mm: WG Charter issue above
12:52:56 <kaz> ... also it would be nice to have a specific repo for the wot-discovery discussion
12:53:17 <kaz> ... will generate a draft first
12:53:26 <kaz> ... and let's have discussion during the main call
12:54:45 <kaz> zk: regarding the above Issue 861
12:55:11 <kaz> ... we need use cases to motivate it
12:55:14 <kaz> mm: ok
12:55:19 <kaz> ... (adds comment on that point)
12:55:31 <kaz> ... why don't you add your comments to this thread?
12:55:32 <kaz> zk: ok
12:56:00 <kaz> [adjourned]
12:56:03 <kaz> rrsagent, make log public
12:56:13 <kaz> rrsagent, draft minutes
12:56:13 <RRSAgent> I have made the request to generate https://www.w3.org/2019/09/02-wot-sec-minutes.html kaz
16:09:26 <zkis> zkis has joined #wot-sec
17:23:49 <zkis> zkis has joined #wot-sec