13:55:21 RRSAgent has joined #wot-discovery 13:55:21 logging to https://www.w3.org/2022/10/24-wot-discovery-irc 13:57:55 McCool_ has joined #wot-discovery 14:01:24 ktoumura has joined #wot-discovery 14:03:30 Mizushima has joined #wot-discovery 14:05:45 meeting: WoT Discovery 14:05:56 chair: McCool 14:05:58 JKRhb has joined #wot-discovery 14:06:13 scribenick: JKRhb 14:06:20 present+ Kaz_Ashimura, Michael_McCool, Farshid_Tavakolizadeh, Jan_Romann, Kunihiko_Toumura, Tomoaki_Mizushima 14:06:43 topic: Next Meetings 14:06:57 mm: Next meetings are going to be cancelled 14:07:19 ... we need to get done with what is left today 14:07:27 topic: Minutes Approval 14:07:40 mm: There was a typo which is already fixed 14:07:56 ... need to discuss about IETF things today 14:08:04 ... any objections to publishing? 14:08:11 There are none, minutes are approved 14:08:19 topic: Implementation Report 14:08:27 mm: I've been working on a PR 14:08:47 ... got more test data to resolve CoAP/CoRE RD assertions 14:09:04 ... some implementation descriptions also came in 14:09:49 ... Size2 assertion has no implementations yet, but it is one we could drop 14:10:33 ... there is a missing implementation for wot.directory Resource Type with CoRE RD 14:10:55 jr: There is one pending PR for at least one implementation for this feature 14:11:15 mm: A new input for RIOT OS resolved a number of CoAP issues 14:11:56 s/we could drop/we could make informative/ 14:12:08 present+ Sebastian_Kaebisch 14:12:13 rrsagent, make log public 14:12:19 rrsagent, draft minute 14:12:19 I'm logging. I don't understand 'draft minute', kaz. Try /msg RRSAgent help 14:12:24 s/rrsagent, draft minute// 14:12:25 rrsagent, draft minutes 14:12:25 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 14:12:46 mm: (Shows current draft of the implementation report) 14:12:56 ... some boilerplate needs to be updated here 14:13:14 cris_ has joined #wot-discovery 14:13:30 ... I made these changes in the TD IR, but they are currently missing in this IR 14:13:56 ... (goes over the remaining at-risk items) 14:14:05 rrsagent, draft minutes 14:14:05 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 14:14:10 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#24_October_2022 14:14:31 present+ Cristiano_Aguzzi 14:15:10 ... there is more here than I would like, at least a quarter of assertions are still at risk 14:15:23 s/Next meetings/Next three meetings (=Oct 31, Nov 7 and Nov 14)/ 14:15:58 i|There was a typo|-> https://www.w3.org/2022/10/17-wot-discovery-minutes.html Oct-17| 14:16:07 ... people should focus on testing, we probably need to move on though anyway 14:16:08 rrsagent, draft minutes 14:16:08 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 14:16:35 mm: We are going to have a call for resolution on Wednesday 14:17:06 ... until, all remaining issues need to be resolved 14:17:27 i|working on a PR|-> https://github.com/w3c/wot-discovery/pull/430 PR 430 - CR publication prep and IR finalization| 14:17:34 ... if sections are not getting enough support, we can make them informative 14:17:53 ... if there any comments, leave them in the PR 14:17:58 i|working on a PR|-> https://cdn.statically.io/gh/w3c/wot-discovery/1a1260cf904ee31a7de4e78ec5aa194e491579da/publication/4-cr/testing/report.html Rendered version of the Implementation Report| 14:18:01 rrsagent, draft minutes 14:18:07 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 14:18:07 ... suggestions can be merged during the main call 14:18:49 topic: PRs 14:19:02 subtopic: PR #428 14:19:26 ca: This PR is probably redundant 14:19:35 mm: I will have another look into it 14:19:52 ft: I think we agreed on that we can close it 14:20:00 mm: Okay, then let's close it 14:20:27 subtopic: wot-testing PR #463 14:20:50 mm: This adds an implementation report for dart_wot 14:20:55 ... is a consumer and a discoverer 14:21:02 i|This PR is|-> https://github.com/w3c/wot-discovery/pull/428 PR 428 - Patch 8| 14:21:04 ... see no problem with merging this 14:21:05 Merged 14:21:24 subtopic: wot-testing PR #465 14:21:56 mm: Do we to have separate descriptions for linksmart and TinyIoT? 14:22:12 ft: linksmart is failing some assertions, so I think we should go with this one 14:22:16 i|This adds an|-> https://github.com/w3c/wot-testing/pull/463 wot-testing PR 463 - Add implementation description for dart_wot| 14:22:28 s/linksmart/LinkSmart/ 14:22:50 i|Do we to have|-> https://github.com/w3c/wot-testing/pull/465 wot-testing PR 465 - Add implementation description for TinyIoT| 14:23:05 mm: Is there a paragraph missing? I can add it in 14:23:11 ... (adds the paragraph) 14:23:20 ... merging 14:23:23 Merged 14:23:47 subtopic: wot-testing PR #464 14:24:01 mm: This is for Architecture, but I can merge it now 14:24:04 Merged 14:24:09 i|This is for|-> https://github.com/w3c/wot-testing/pull/464 wot-testing PR 464 - Add manual Architecture assertions for dart_wot| 14:24:30 mm: Remaining PRs will be merged in Architecture 14:24:58 topic: IANA Registration 14:25:29 mm: Our previous IANA submission was not well-structured and we got an response from them 14:25:48 ... we need to go over their email and resubmit 14:25:58 q+ 14:26:35 mm: Toumura-San, is it okay if I copy your input for the email into the issue? 14:27:00 kt: Yeah, no problem 14:27:05 mm: Here is the email 14:27:16 i|Our previous|-> https://github.com/w3c/wot-discovery/issues/403 Issue 403 - Refine DNS-SD Name Requirements and IANA Consideration| 14:27:17 ... (shows the email) 14:27:52 ... there is a separate registry for service names 14:28:19 ... we need to answer the questions they provided us 14:28:41 ... Kaz, can we name you as the contact person here? 14:30:12 kaz: Yeah, no problem. However, can we summarize what we need to do and ask IANA for help. If the upper half of the comment states what we need to do then I can work with that 14:31:23 mm: (adds in info regarding the Discovery specification to his issue comment) 14:31:39 s/adds in/adds/ 14:32:06 ... question is if we need to update the IANA Considerations section 14:32:18 ... I think it's okay but we need to check 14:33:08 mm: (Regarding the mail for IANA) What is the difference between Assignee and Contact Person? 14:33:30 kaz: Adding the chairs there is fine 14:33:54 s/Yeah, no problem. However, can we summarize what we need to do and ask IANA for help./I'm OK to be put here as the contact person. However, when I talked with Philippe, he suggested we consult with Sam, who knows more about the IANA procedure for this, so I'd like to summarize what we want to do so that I can ask Sam and the IANA contact for help./ 14:34:18 mm: I will set team-wot@w3.org as the assignee mail since affiliations may change 14:35:00 ... the mail address will be around even if the WoT WG will be closed 14:35:42 s/what we need to do then I can work with that/what we want, I can start with that./ 14:36:00 rrsagent, draft minutes 14:36:00 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 14:37:43 ... (adjusts draft IANA submission regarding the use of CoAP in the case of UDP) 14:38:58 ... there is some ambiguity regarding the use of UDP in the context of discovery, since TDs might also contain affordances that are accessed using TCP-based protocols 14:39:19 ... (clarifies this) 14:39:50 +1 14:40:01 q+ 14:40:31 kaz: Does that mean that UDP will be used to retrieve TDs via CoAP? 14:41:18 ... I am not sure if we need to mention such a low-level protocol such as UDP 14:41:34 ... see for example Google's QUIC 14:43:00 mm: Yes, we can leave it as is, however (?) 14:43:16 ack k 14:43:26 s/such as/like/ 14:43:55 mm: The text regarding Versioning is fine, however, we can add that there is no versioning mechanism 14:44:44 ... but that there could be a version field added 14:46:32 q? 14:46:52 ... (adds further clarification regarding the use of security features) 14:47:28 ... is this an acceptable clarification? 14:47:56 kaz: Yes 14:51:52 mm: (adds links to specifications) 14:52:41 ... Kaz, do you want to forward this to Sam Weiler for comment? 14:52:52 kaz: Will do 14:53:29 s/Will do/as I've already mentioned, I'll consult with Sam based on this description./ 14:53:34 mm: Should we add an Editor's Note stating that the names are subject to change? 14:53:49 q? 14:54:42 ... will add as a TODO to PR #430 14:55:18 ... my worry is that if the name changes I don't want to change the assertion 14:55:29 ... I will think about this 14:55:53 ... let's get the registration email to Sam, I will send the email right now 14:56:27 ... (starts preparing the email) 14:57:07 kaz: You can mention that we talked to PLH about this before 14:58:59 mm: I will CC Tomoura-San 14:59:06 ... (sends off the email) 15:00:35 s/email/email to Sam to get advice/ 15:00:36 mm: We made some progress. Since we will have no calls for three weeks, we will make the resolution in the main call. Please keep on testing, I will update the implementation report even though I'll be on vacation 15:00:43 [adjourned] 15:00:53 rrsagent, draft minutes 15:00:53 I have made the request to generate https://www.w3.org/2022/10/24-wot-discovery-minutes.html kaz 15:14:16 kaz has joined #wot-discovery 19:19:29 Zakim has left #wot-discovery