13:01:29 RRSAgent has joined #wot-sec 13:01:34 logging to https://www.w3.org/2024/03/11-wot-sec-irc 13:01:34 meeting: WoT Security 13:01:37 chair: McCool 13:01:45 present+ Kaz_Ashimura, Michael_McCool 13:03:47 JKRhb has joined #wot-sec 13:06:08 present+ Jan_Romann 13:07:19 McCool_ has joined #wot-sec 13:09:27 present+ Tomoaki_Mizushima 13:11:49 agenda: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#11_March_2024 13:11:55 topic: Minutes 13:12:04 -> https://www.w3.org/2024/02/26-wot-sec-minutes.html Feb-26 13:12:19 approved 13:12:58 topic: Logistics 13:13:05 mm: Apr-1 meeting will be cancelled 13:13:15 topic: Use Cases and Requirements 13:13:51 -> https://github.com/w3c/wot/tree/main/planning/Security wot/planning/Security/README.md 13:13:58 s/md/md Security planning 13:14:16 mm: tentative requirements for security above 13:16:34 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/security-categories.csv wot-usecases/USE-CASES/security-categries.csv 13:17:32 -> https://w3c.github.io/wot-usecases/#security WoT Use Cases and Reuirements ED - 4.2.6 Security 13:18:01 s/mm: tentative requirements for security above// 13:18:41 mm: some resources on work items, category table and draft requirements 13:19:13 ... (shows those three resources) 13:20:16 scribenick: JKRhb 13:21:01 mm: I guess the question is what do next here 13:21:11 ... so one option is to skip meetings to work on this 13:21:46 ... on the other hand, we have a lot to do 13:22:08 mm: Had you had a look into the security ontology issue yet, Jan? 13:22:12 jr: Not really 13:22:15 q+ 13:23:22 mm: We should to split out the security schemes that are protocol/binding specific 13:23:34 jr: I am actually very interested in that topic 13:23:43 s/should to split/should split/ 13:23:46 mm: Probably will mostly move things around 13:24:03 q+ 13:24:09 ack j 13:24:16 ... TD document will probably only contain "structural" security schemes 13:24:19 ... like oneOf 13:24:38 ... not sure if this TF has to do much in that regard then 13:24:50 mm: So what should we do with this table? 13:24:55 ... we had some updates 13:25:07 ... we could spend this meeting working through this table and finish it up 13:25:22 ... this PR has a bit more filled in 13:25:34 ... but we still have a ton of use cases to go through 13:25:43 ... we could do this offline or as part of this meeting 13:25:56 ... I think at some point, we split up who is doing what 13:26:14 ... (looks at the PR) 13:26:31 q? 13:26:33 ... oh, yeah, we assigned some to Mahda and the rest to me 13:26:45 ... let's add a comment here 13:27:18 kaz: Like in the discovery call, I suggest to wait for one or two weeks until the Use cases and Requirements discussion is finished 13:27:26 ... and we got feedback from the Japanese CG 13:27:35 mm: Was my feeling as well, that we should pause 13:27:37 s/to wait/we wait/ 13:27:51 s/one or two weeks/one week or two/ 13:27:54 ... we could end this meeting and continue offline 13:28:06 s/discussion/template discussion/ 13:28:23 ... then next week, we could continue after we got the feedback from ECHONET 13:28:31 kaz: Yeah 13:28:34 s/we got feedback/we can get feedback/ 13:28:45 mm: Well, in that case, we can close the meeting early 13:28:57 s/CG/CG's discussion on WoT Security/ 13:29:05 [adjourned] 13:29:09 rrsagent, make log public 13:29:13 rrsagent, draft minutes 13:29:15 I have made the request to generate https://www.w3.org/2024/03/11-wot-sec-minutes.html kaz 13:29:30 i|adjourned|... will take the next half an hour to work on this topic| 13:29:38 rrsagent, draft minutes 13:29:40 I have made the request to generate https://www.w3.org/2024/03/11-wot-sec-minutes.html JKRhb 13:40:03 i/Feb-26/scribenick: kaz/ 13:40:04 rrsagent, draft minutes 13:40:06 I have made the request to generate https://www.w3.org/2024/03/11-wot-sec-minutes.html kaz 15:44:12 Zakim has left #wot-sec