12:02:55 RRSAgent has joined #wot-sec 12:02:55 logging to https://www.w3.org/2022/04/04-wot-sec-irc 12:03:07 JKRhb has joined #wot-sec 12:04:28 meeting: WoT Security 12:04:53 present+ Kaz_Ashimura, Michael_McCool, Jan_Romann, Jiye_Park, Philipp_Blum 12:04:57 jiye has joined #wot-sec 12:06:01 McCool has joined #wot-sec 12:07:01 agenda: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#4_April_2022 12:07:41 scribenick: jiye 12:07:47 rrsagent, make log public 12:07:51 rrsagent, draft minutes 12:07:53 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 12:08:11 topic: Minutes 12:08:15 -> https://www.w3.org/2022/03/28-wot-sec-minutes.html Mar-28 12:09:05 mm: looking at the PR 1421 again 12:13:32 we also need to look at this issue: https://github.com/w3c/wot-architecture/issues/726 12:14:49 https://github.com/w3c/wot-thing-description/pull/1452 12:19:22 topic: PR #1452 fix: allow uri value only for in field of APIKeySecurityScheme 12:19:45 https://github.com/w3c/wot-thing-description/pull/1452 12:20:15 related PR #1440 https://github.com/w3c/wot-thing-description/issues/1440 12:20:33 s/related PR/related Issue/ 12:23:15 mm: check the spec actually what it's written 12:23:46 JP: problem is, there is one definition 'in' 12:24:05 s/JP/JR/ 12:25:32 mm: how we do handle case right now does not make senese 12:26:03 JR: wouldn't it make sense to separate? 12:27:01 mm: one suggestion is using different name for 'in' ex) in_xx, and use the same label "in" 12:27:16 JR: might cause confusion 12:28:59 mm: let's think about it and the worst case just leave as it is now. we can write validation in json schema 12:30:21 mm: we need to consider compatability 12:30:47 mm: URI is not a problem for compatability 12:31:42 topic: Make Security and Privacy Considerations Normative PR #295 12:31:55 https://github.com/w3c/wot-discovery/pull/295 12:32:59 mm: made a normative section and RFC keywords. Now it has assertions and new wordings. 12:34:20 s/section/sections/ 12:43:58 s/related PR/related Issue/ 12:44:17 rrsagent, draft minutes 12:44:17 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 12:44:24 rrsagent, make log public 12:44:26 rrsagent, draft minutes 12:44:26 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 12:46:53 JP: why 3x? is there any reference? 12:46:59 mm:it's from QUIC/HTTP3. 12:47:03 PB: it makes sense when service accepts HTTP3 12:49:07 PB: you might want to add periodically chainging IP address? 12:49:33 mm: good point, I will add it to the note. 12:49:59 mm: do you know related RFC number? 12:50:08 PB: I will have a look 12:51:53 mm: will not push to merge this right away, but will wait one week for a review 12:52:48 topic: Review and Update Security and Privacy Considerations #726 12:52:54 https://github.com/w3c/wot-architecture/issues/726 12:55:05 mm: need to read through the document, and see what we can do 12:55:46 present+ Philipp_Blum 12:55:51 rrsagent, draft minutes 12:55:51 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 12:56:17 present+ Tomoaki_Mizushima 12:56:19 rrsagent, draft minutes 12:56:19 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 12:56:26 chair: McCool 12:56:28 rrsagent, draft minutes 12:56:28 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 13:01:41 rrsagent, draft minutes 13:01:41 I have made the request to generate https://www.w3.org/2022/04/04-wot-sec-minutes.html kaz 14:57:31 Mizushima has left #wot-sec 15:14:39 Zakim has left #wot-sec 17:07:02 JKRhb has joined #wot-sec 19:30:49 JKRhb has joined #wot-sec 19:46:27 JKRhb has joined #wot-sec 23:12:56 JKRhb has joined #wot-sec