10:00:37 RRSAgent has joined #wot-arch 10:00:37 logging to https://www.w3.org/2022/05/12-wot-arch-irc 10:02:06 ktoumura has joined #wot-arch 10:02:23 mlagally has joined #wot-arch 10:02:41 McCool has joined #wot-arch 10:03:18 meeting: WoT Architecture 10:03:23 chair: Lagally 10:04:49 present+ Kaz_Ashimura, Michael_Lagally, Kunihiko_Toumura, Meiyu_Hao, Michael_McCool 10:05:04 topic: Welcome Meiyu! 10:05:13 mh: (introduces herself) 10:05:35 Mizushima has joined #wot-arch 10:05:56 present+ Tomoaki_Mizushima 10:06:13 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_12th.2C_2022 10:09:09 topic: Agenda 10:09:25 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_12th.2C_2022agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_12th.2C_2022 agenda for today 10:09:32 ml: (goes through the agenda) 10:10:33 ... anything to be added? 10:10:36 (none) 10:10:41 topic: Minutes 10:10:49 -> https://www.w3.org/2022/05/05-wot-arch-minutes.html May-5 10:11:00 ml: (goes throught the minutes 10:11:33 ... anything to be changed? 10:11:35 (none) 10:11:37 approved 10:11:53 topic: Schedule 10:12:04 -> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md publication schedule 10:12:31 ml: normative feature freeze expected by May 6 10:13:18 ... wondering if anything to be added to Issue 681? 10:13:35 mm: not aware of any additional terminology changes 10:14:03 ... OK with closing this issue 10:14:26 i/wondering/subtopic: Issue 681/ 10:14:39 i|wondering|-> https://github.com/w3c/wot-architecture/issues/681 Review architecture document consistency| 10:14:42 closed 10:15:11 q+ 10:15:45 ack k 10:16:18 kaz: regarding the schedule, do we need to extend the deadline given the original deadline was May 6? 10:16:27 mm: maybe we can extend it till today 10:16:40 ml: ok 10:17:08 ... let's see the whole schedule to make sure 10:17:12 q? 10:17:24 topic: Explainer 10:17:47 -> https://github.com/w3c/wot-architecture/pull/745 PR 745 - Explainer Updates 10:18:04 ml: McCool, you've implemented all the expected updates. right? 10:18:06 mm: yes 10:18:13 ml: let's merge this then 10:19:06 merged 10:19:32 mm: can add additional edits, e.g., line 16 10:19:53 topic: Contributions 10:20:22 ml: let's start with the one on TLS 10:20:37 subtopic: PR 747 10:20:48 -> https://github.com/w3c/wot-architecture/pull/747 PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII 10:21:00 mm: this is a mistake 10:21:16 ... with branch handling 10:21:30 ml: let's merge another one first then 10:21:37 subtopic: PR 746 10:22:02 -> https://github.com/w3c/wot-architecture/pull/746 PR 746 - Update Discoverer, add Registrant Definitions 10:22:18 mm: explain what a discovery service should be 10:22:41 ... directory service is just for directory 10:22:58 ... discovery service is the whole mechanism 10:23:21 ... one way for discovery is searching for directory 10:23:59 ... the Discovery spec describes what discovery is like 10:24:09 ... Architecture should be consistent with that 10:25:31 ml: in general, if somebody requests some changes, should provide reasonable reasons 10:26:04 ... (goes through the changes) 10:26:10 ... let's merge this then 10:27:01 merged 10:27:14 subtopic: PR 747 - revisited 10:28:26 -> https://github.com/w3c/wot-architecture/pull/747 PR - Additional Security/Privacy Considerations around TLS, access controls for PII 10:28:40 mm: we definitely need TLS for public networks 10:28:55 ... summarized the mechanism within TD 10:30:40 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/747/7c02a1a...mmccool:839347c.html#sec-security-consideration-secure-transport 10.5 Secure Transport 10:31:11 mm: should use proxy approach for public network without TLS 10:31:25 ml: basically fine with the text 10:31:46 mm: asking object security as well 10:31:58 ... but what query is making? 10:32:27 ml: great piece of clarification 10:33:12 ... some minor typos, e.g., Unforunately instead of Unfortunately. 10:33:43 ... maybe HTML section structure should be also checked again 10:35:20 mm: (asks Lagally for clarification about the issues) 10:35:32 ... maybe missing a close tag? 10:35:38 ml: think so 10:36:36 subtopic: PR 749 10:37:09 -> https://github.com/w3c/wot-architecture/pull/749 PR 749 - Remove abnf validation from rel and op 10:37:17 ml: fine with merging this 10:37:38 merged 10:37:56 subtopic: PR 750 10:38:13 -> https://github.com/w3c/wot-architecture/pull/750 PR 750 - adding orchestration section 10:38:55 ml: generated actual text for Orchestration 10:39:03 ... (goes through the diff) 10:39:42 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/750/7be810a...9521b03.html#orchestration Diff - 5.7.2 Orchestration 10:39:47 mm: OK with the text itself 10:40:02 ... but kind of concerned with the definition of "Orchestration" 10:40:17 ... already meant as "automation" from my viewpoint 10:40:29 q+ 10:41:13 kaz: +1 10:41:23 ... need a clear definition 10:42:10 ... from my viewpoint, orchestration should include mashing up multiple devices, applications and entities, and there should be some meta control model as well 10:43:08 mm: maybe we can add an Editor's note and think about the concrete text later 10:44:06 ml: let's one merge this PR itself 10:44:17 mm: note that we need to modify the Editor's note 10:44:20 merged 10:44:37 subtopic: PR 751 10:45:00 -> https://github.com/w3c/wot-architecture/pull/751 PR 751 - improving profile description 10:45:35 mm: "We" as the subject is usually not used 10:45:42 ... passive voice to be used here 10:45:56 ... like "something is defined" 10:45:58 mm: ok 10:47:26 merged 10:47:48 subtopic: PR 747 - revisited 10:48:00 -> https://github.com/w3c/wot-architecture/pull/747 PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII 10:48:11 mm: this is addressing PING issues 10:49:34 ... mutable IDs to be used for healthcare purposes 10:50:07 ml: should define "PII" as well? 10:50:11 mm: that's right 10:50:54 ... previous section 11.1.1 has the definition 10:51:30 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/747/7c02a1a...mmccool:5fcffb6.html#sec-security-consideration-td-pii diff - 11.1.1 Thing Description Personally Identifiable Information Risk 10:52:15 mm: (works on the problem to update the PR) 10:52:20 subtopic: PR 737 10:52:32 -> https://github.com/w3c/wot-architecture/pull/737 PR 737 - Align binding related information 10:52:58 ml: normative feature fix was expected by May 6 10:53:04 ... but Ege is not here today 10:53:26 ... so we need to discuss this next week on May 19 10:54:05 mm: do we want to delay the CR candidate day by one week? 10:54:09 ml: yes 10:54:25 s/by one week// 10:54:40 ... (updates the schedule) 10:55:30 mm: if we make the decision for CR candidate next week on May 19 10:55:46 ... we still have two weeks for review 10:56:03 q+ 10:56:51 ack k 10:57:02 kaz: what would be the concrete procedure here? 10:57:11 ... please note the main call is held on Wednesday 10:57:22 ... while this Architecture call is held on Thursday 10:57:45 ... maybe we would make a preliminary decision by email? 10:58:07 mm: CR candidate my thought was we have one more week for decision 10:58:19 ... then ask the whole group for 2-week review 10:58:59 ml: please add this to the main call agenda for May 18 10:59:01 mm: ok 10:59:36 subtopic: PR 747 - revisited 10:59:47 mm: updated the PR 747 based on the discussion today 11:00:25 -> https://github.com/w3c/wot-architecture/pull/747 PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII 11:00:31 [adjourned] 11:00:38 rrsagent, make log public 11:00:42 rrsagent, draft minutes 11:00:42 I have made the request to generate https://www.w3.org/2022/05/12-wot-arch-minutes.html kaz 13:07:04 Zakim has left #wot-arch