14:03:44 RRSAgent has joined #wot-sec 14:03:48 logging to https://www.w3.org/2023/12/04-wot-sec-irc 14:03:54 agenda: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#4_December_2023 14:05:02 chair: McCool 14:05:15 present+ Kaz_Ashimura, Michael_McCool, Mahda_Noura 14:06:04 Mizushima has joined #wot-sec 14:06:24 rrsagent, make log public 14:06:29 rrsagent, draft minutes 14:06:30 I have made the request to generate https://www.w3.org/2023/12/04-wot-sec-minutes.html kaz 14:08:10 topic: Minutes 14:08:22 -> https://www.w3.org/2023/11/27-wot-sec-minutes.html Nov-27 14:08:23 approved 14:08:29 topic: Cancellations 14:08:58 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations Cancellations (from the main wiki) 14:09:23 mm: like the impact for Discovery, the Nordic Chapter CG will have their meeting on Dec 18 again 14:09:36 ... how to deal with the collaboration in the future? 14:09:45 q+ 14:10:11 ... regarding Dec-18, we've already made a decision to cancel our meetings, though 14:10:20 q? 14:11:17 kaz: they're a CG while we're a WG, so we should prioritize our own work 14:11:34 ... let's talk with their Chairs about the future collaboration a bit more 14:11:36 ack k 14:12:27 mm: note Jan 10 will be the first call of 2024 for WoT 14:12:31 ... not calls on Jan 8 14:12:59 topic: How to accelerate the Security discussion 14:13:14 mm: we need more people for Security/Privacy 14:13:18 ... but how to do that? 14:13:46 ... human resources for security/privacy is limited 14:14:02 ... several possibilities 14:14:09 ... search for people from Members 14:14:18 ... or from Academic 14:14:32 q+ 14:15:22 ack k 14:15:48 kaz: for that purpose, we need to clarify our "need" and "requirement" 14:15:58 ... e.g., IoT security expert 14:16:09 mh: somebody in mind 14:16:36 https://vsr.informatik.tu-chemnitz.de/about/people/siegert/ 14:16:43 q+ 14:16:59 s|https://vsr.informatik.tu-chemnitz.de/about/people/siegert/|| 14:17:55 mm: we need a security expert and also a privacy expert 14:18:54 ack k 14:18:55 q+ 14:23:17 ack k 14:25:08 kaz: btw, we need to get more participants from the Membership as well 14:25:12 mm: yeah 14:26:03 q+ 14:27:16 ack k 14:28:38 topic: PR 249 14:29:17 -> https://github.com/w3c/wot-usecases/pull/249 PR 249 - Update links in security use case categories using triple-square 14:30:33 mm: would merge this PR 14:30:48 merged 14:30:52 rrsagent, draft minutes 14:30:54 I have made the request to generate https://www.w3.org/2023/12/04-wot-sec-minutes.html kaz 14:31:23 topic: Issue 243 14:31:42 -> https://github.com/w3c/wot-usecases/issues/243 Issue 243 - Update Security Requirements #243 14:32:00 s/topic: PR/subtopic: PR/ 14:32:01 s/topic: PR/subtopic: PR/ 14:32:18 i|topic: PR 249|topic: Use Cases PRs| 14:32:20 rrsagent, draft minutes 14:32:22 I have made the request to generate https://www.w3.org/2023/12/04-wot-sec-minutes.html kaz 14:32:43 mm: (adds comments) 14:32:49 -> https://github.com/w3c/wot-usecases/issues/243#issuecomment-1838759002 McCool's comments 14:33:42 topic: Security Categories 14:33:54 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/security-categories.csv security-categories.csv 14:35:17 mm: (goes through the CSV table and the use Cases document) 14:35:48 -> https://w3c.github.io/wot-usecases/ WoT Use Cases and Requirements Editor's Draft 14:37:07 mm: (shows the example of "Smart Agriculture") 14:40:55 q+ 14:43:03 kaz: technically, date/time and location could be also privacy information 14:44:16 mm: probably should split "Private Information" category into "Private Information (for PII)" 14:44:35 ... and "Confidential Information" (e.g., business confidential) 14:45:50 kaz: in that case, "business Confidential" implies "Private Information" as an organization/entity 14:46:26 ... so thinking about level of entities, e.g., person and organization, would make sense 14:48:31 i|technically|-> https://w3c.github.io/wot-usecases/#UC-open-field-agriculture-1 WoT Use Cases and Requirements - 2.1.2 Open-field Agriculture| 14:48:59 q+ 14:52:01 ack k 14:52:38 mm: "business confidential" information would cause damage of money/cost 14:53:18 kaz: in that case, maybe it would be clearer to handle the impact and damage itself, e.g., "damage of cost", instead of "business confidential" 14:54:25 subtopic: Livestock Health Management 14:54:52 -> https://w3c.github.io/wot-usecases/#UC-livestock-health-management-1 2.1.6 Livestock Health Management 14:55:22 mm: it's an interesting use case since these days we get issues on chicken flu, etc. 14:56:24 q? 14:56:51 s/chicken flu/bird flu/ 14:57:49 subtopic: Agricultural Machinery Management 14:58:11 -> https://w3c.github.io/wot-usecases/#UC-agricultural-machinery-management-1 2.1.7 Agricultural Machinery Management 14:58:46 q+ 14:59:08 ack k 15:00:42 kaz: probably we need to think about the whole lifecycle of the machinery to discuss the potential damages 15:00:49 ... when to have what kind of damages 15:02:13 ... not only within the field but also the lifecycle, e.g., getting the machinery from the shop to the field by a truck 15:03:01 mm: we're out of time. let's continue the discussion next week. 15:03:04 [adjourned] 15:03:10 rrsagent, draft minutes 15:03:11 I have made the request to generate https://www.w3.org/2023/12/04-wot-sec-minutes.html kaz 17:15:48 Zakim has left #wot-sec