15:23:51 RRSAgent has joined #did 15:23:51 logging to https://www.w3.org/2021/01/12-did-irc 15:23:53 RRSAgent, make logs Public 15:23:54 please title this meeting ("meeting: ..."), ivan 15:24:13 Meeting: DID WG Telco 15:24:13 Chair: ivan 15:24:13 Date: 2021-01-12 15:24:13 Agenda: https://www.w3.org/mid/000000000000aa249905b8a26c1b@google.com 15:24:13 ivan has changed the topic to: Meeting Agenda 2021-01-12: https://www.w3.org/mid/000000000000aa249905b8a26c1b@google.com 15:24:14 Regrets+ burn, brent 15:38:42 TallTed has joined #did 15:41:09 TallTed has changed the topic to: Meeting Agenda 2021-01-12: https://lists.w3.org/Archives/Public/public-did-wg/2021Jan/0013.html 15:56:52 present+ 16:00:50 markus_sabadello has joined #did 16:01:08 present+ 16:01:26 present+ 16:01:34 justin_r has joined #did 16:01:42 present+ 16:02:00 present+ 16:02:05 present+ 16:02:22 present+ adrian 16:02:30 present+ identitywoman 16:02:39 agropper has joined #did 16:02:47 Orie has joined #did 16:02:53 present+ 16:03:07 scribe+ markus_sabadello 16:03:11 phila has joined #did 16:03:24 present+ 16:03:28 present+ 16:03:28 present+ 16:04:12 ivan: Dan and Brent sent their regrets, I will take over today. 16:04:22 ivan: We will mostly look at issues today. 16:04:38 ivan: There is no need for introductions today. Anybody wants to re-introduce? 16:05:03 ivan: Next topic is re-joining the Working Group. 16:05:15 drummond has joined #did 16:05:20 ivan: I looked at the list of organizations, I think almost all active members are okay. 16:05:58 JoeAndrieu has joined #did 16:06:01 ivan: Sovrin Foundation has not re-joined. Among invited experts, I haven't seen Yancy in a long time, he should re-join. 16:06:07 present+ 16:06:08 manu: I will ping Yancy. 16:06:32 ivan: Let's move to the real discussion. Let's look at priority 1 issues. 16:06:35 present+ 16:06:41 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+label%3Apre-cr-p1+sort%3Aupdated-asc 16:07:05 jonathan_holt has joined #did 16:07:15 present+ jonathan_holt 16:07:26 Topic: Priority 1 issues 16:07:32 manu: Before going to issues, we should explain something. I sent an email today. We will process issues differently. 16:07:56 manu: We are in the final stretch to get into the Candidate Recommendation stage. To do so, we like to ensure that all issues have been processed. 16:08:22 manu: I.e. we have either addressed all issues, stated that we will not address them, or stated that we will defer them to version 2.0. 16:08:31 dbuc has joined #did 16:08:35 present+ 16:09:01 manu: The chairs sent to the mailing list that very soon we will go into a mode where we will ask individuals to volunteer to close our issues (reviewing, writing PR, ..). 16:09:24 manu: If the assigned person doesn't do that by the time the group wants to move to CR, then the issue will be deferred. 16:09:42 manu: It will then be deferred to the next group working on the next version. 16:10:06 manu: Today we will do a dry-run of this. We will go over the issues. If there are no volunteers, we will mark issues "potentially deferred". 16:10:10 q? 16:10:59 manu: We will go over priority 1, 2, 3 issues 16:11:07 issue 118 https://github.com/w3c/did-core/issues/118 16:11:43 issue 292 https://github.com/w3c/did-core/issues/292 16:11:51 present+ 16:11:56 isseu 291 https://github.com/w3c/did-core/issues/291 16:12:08 manu: 118 is editorial. Amy is assigned to it, I expect she will work on it. 16:12:23 119 https://github.com/w3c/did-core/issues/119 16:13:07 manu: 119 is assigned to Dan, we may want to assign it to someone else due to availability. 16:13:23 199 https://github.com/w3c/did-core/issues/199 16:13:49 199, Brent has written a PR. Is this for Drummond? 16:13:57 manu: 16:14:11 drummond: If you want to move it to me, that's fine. 16:14:24 manu: My understanding is you wrote the appendix that will address this issue. 16:14:32 drummond: There is a separate issue also for the appendix itself. 16:15:00 manu: You are assigned. If you are not able to get the PR through, it will probably be deferred. 16:15:01 issue 170 https://github.com/w3c/did-core/issues/170 16:16:22 529 https://github.com/w3c/did-core/issues/529 16:16:22 justin_r: The sort order of dispayed issues changes as we comment on them and go through them. 16:16:27 q+ 16:17:19 495 https://github.com/w3c/did-core/issues/495 16:17:36 manu: 495, shigeya what is the status? 16:17:45 shigeya: I raised a PR, but something looks strange. 16:17:57 manu: Do you want to be assigned? 16:17:59 shigeya: Yes 16:18:18 issue 170 https://github.com/w3c/did-core/issues/170 16:18:44 manu: 170, Mike is assigned to this. 16:18:58 q+ to propose closing 16:19:06 ack Orie 16:19:06 Orie, you wanted to propose closing 16:19:09 ack ivan 16:19:23 Orie: As I said many times on this issue, I think it should be closed. I will probably reject any PR that removes duplication. 16:19:36 q+ 16:19:36 q+ 16:19:45 Orie: We've looked at this several time before. This is fundamental to the spec, changing it will break things. 16:20:05 manu: The default is, if there is not a PR, or the PR doesn't go through, it will be closed. 16:20:19 ack dbuc 16:20:26 dbuc: Our implementation doesn't use the JWK members. I'd be happy to let this issue expire. 16:20:52 jonathan_holt: Can I have a short summary of this issue? 16:20:53 ack jonathan_holt 16:21:18 Orie: There are two supported key material representations: publicKeyBase58, publicKeyJwk. If you aren't using publicKeyJwk, you need "id" or "type". 16:21:56 Orie: I had a conversation with Mike about it.. What about the values in the JWK? Should be say "kid" is forbidden? Or optional? What additional restrictions would be put on top of the JWK? 16:22:08 Orie: If you want to know what publicKeyJwk supports, you just read the JWK spec. 16:22:23 jonathan_holt: Is there any inheritance from JWK? 16:22:38 manu: There is nothing imposed in what you can put in JWK by the verification method. 16:22:52 jonathan_holt: If it is a verificiation method, are properites inherited? 16:23:16 manu: Someone would have to raise a PR if they wanted to clarify inheritance. 16:23:41 manu: Without a PR, there's not much to do here. 16:23:56 Topic: Priority 2 issues 16:23:57 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+label%3Apre-cr-p2+sort%3Aupdated-asc 16:24:12 https://github.com/w3c/did-core/issues/163 16:24:29 manu, I plan to take this when it's time 16:24:36 manu: 163, rhiaro would you take this? 16:24:57 manu: rhiaro is assigned 16:25:10 https://github.com/w3c/did-core/issues/425 16:25:32 https://github.com/w3c/did-core/issues/468 16:26:39 markus_sabadello: 468, I'm not planning to raise a PR. Maybe others? 16:26:48 manu: This is an example of something that will potentially be deferred 16:26:54 https://github.com/w3c/did-core/issues/463 16:27:11 manu: 463, more people should comment to it 16:27:37 markus_sabadello: It can stay assigned to me 16:27:40 https://github.com/w3c/did-core/issues/538 16:27:52 q+ 16:28:40 manu: 538, markus_sabadello created a PR, will assign this to him 16:28:53 https://github.com/w3c/did-core/issues/539 16:29:04 manu: 539, drummond and JoeAndrieu contributed to this, who will create the PR? 16:29:15 JoeAndrieu: We don't know yet what the PR will be, we first need to get to consensus. 16:29:30 manu: We will try to get clear responsibility. 16:29:40 https://github.com/w3c/did-core/issues/404 16:29:40 manu: JoeAndrieu are you fine with taking this 16:29:42 JoeAndrieu: yes 16:30:02 manu: 404, ivan has PRs pending for this. ivan are you okay with being responsible for this? 16:30:03 ivan: yes 16:31:14 manu: I think you're right we don't need a special topic call anymore 16:31:42 ivan: But I raised two issues on the registry. I have created the JSON Schema that I proposed to be part of the spec. Independently of that, I proposed an RDF vocabulary and SHACL. 16:32:04 ivan: I think we should discuss those two. But they are not normative, so I'm fine if they are not finalized before CR. 16:32:17 ivan: The important one is the PR on the core document. 16:32:41 manu: This is a sizable chunk of work, and it's important. Please everyone take a close look. 16:33:10 manu: Now priority 3 issues 16:33:11 Topic: Priority 3 issues 16:33:12 https://github.com/w3c/did-core/issues?q=is%3Aissue+is%3Aopen+label%3Apre-cr-p3+sort%3Aupdated-asc 16:33:28 https://github.com/w3c/did-core/issues/324 16:33:47 manu: 324, Adrian unless you plan to raise a PR, maybe we assign this to someone else? 16:34:08 agropper: I also could 16:34:14 agropper: I'm fine what whatever is most efficient to address this. I'd rather not do the PR, others may be more efficient. Does JoeAndrieu want to help me? 16:34:17 JoeAndrieu: Happy to help 16:34:28 manu: Assigned to JoeAndrieu to work with agropper 16:34:30 agropper: Fine with me 16:34:47 manu: jonathan_holt should this stay on you? 16:34:51 https://github.com/w3c/did-core/issues/340 16:35:33 jonathan_holt: I'd love to hear other people's opinions on it. 16:35:55 manu: We could mark as pending close, and give others a chance to still work on it. Anyone opposed to closing it? 16:35:56 no objection here 16:36:01 manu: Marked a pending close. 16:36:07 s/a/as/ 16:37:00 https://github.com/w3c/did-core/issues/380 16:37:18 q+ 16:37:22 manu: We warned this would be closed and there was no activity 16:37:35 ack markus_sabadello 16:37:39 ack justin_r 16:38:12 q+ 16:38:28 q+ 16:38:37 justin_r: I don't think there is interest in removing this functionality. 16:38:41 justin_r: I'm in favor of closing. 16:38:53 q+ 16:38:59 ack markus_sabadello 16:40:01 q- 16:40:06 ack jonathan_holt 16:40:09 markus_sabadello: The issue is partially obsolete, since "resolveStream" has already been renamed. The issues also discusses the relationship between the two resolution functions. In my opinion, there is no need to change anything 16:40:16 q? 16:40:37 jonathan_holt: This came up in the CBOR section. There is a vulnerability with an unknown length of arrays. It's hard to prevent buffer overflows. 16:40:50 manu: Do you support closing this? 16:40:56 jonathan_holt: I'm agnostic to that 16:41:07 https://github.com/w3c/did-core/issues/399 16:41:10 manu: Marked as pending close 16:41:57 https://github.com/w3c/did-core/issues/452 16:42:00 markus_sabadello: 399, I agree with ivan we could add some clarification for this 16:42:09 q+ 16:42:20 manu: 452 jonathan_holt or Orie do you want to address this? 16:42:33 jonathan_holt: I'll do a PR 16:43:04 https://github.com/w3c/did-core/issues/447 16:43:13 yep yep 16:43:19 manu: 447 rhiaro are you okay with continuing this 16:43:22 rhiaro: ye 16:43:24 https://github.com/w3c/did-core/issues/370 16:43:53 manu: 370, agropper you're assigned, can we find someone to help you do a PR, what are your thought? 16:44:20 agropper: Haven't looked at it in a long time. I think we're dealing with this in the Special Topic Call. 16:44:35 manu: Do you feel addressing the other issue will address this issue? 16:44:52 agropper: I contacted EFF recently to work on getting their objections clarified. 16:45:11 JoeAndrieu: I agree the "herd privacy" issue touches on this. 16:45:26 agropper: Leave it assigned to me, I'm trying to get EFF's attention. 16:45:58 agropper: If there is going to be a PR, I will write it 16:45:58 https://github.com/w3c/did-core/issues/391 16:46:53 q+ 16:46:58 markus_sabadello: 391, I raised this hoping to find someone who would write a PR. I'm not planning to write a PR. 16:47:02 q- 16:47:03 ack jonathan_holt 16:47:05 manu: Anyone willing to write a PR for it? 16:47:19 ivan: Is this section normative? 16:47:28 manu: No, it would be in Security Considerations. 16:47:29 ack ivan 16:47:44 ivan: This may mean it doesn't necessarily have to be addressed before CR. 16:48:07 manu: Marking as potentially-defer-v2. Seems nobody is interested in writing a PR 16:48:07 https://github.com/w3c/did-core/issues/504 16:48:23 manu: 504, shigeya do you want to give us an update on your concerncs? 16:48:37 shigeya: Should be closed once 457 is merged. 16:49:08 504, assigned to drummond 16:49:16 https://github.com/w3c/did-core/issues/72 16:49:24 manu: 72, drummond do you want to continue to be assigned, to do a PR? 16:49:25 drummond: yes 16:49:41 https://github.com/w3c/did-core/issues/373 16:49:41 manu: 373 drummond you have a PR open for this 16:49:54 drummond: That's correct. Waiting for the Special Topic Call. 16:51:08 https://github.com/w3c/did-core/issues/386 16:51:36 manu: 386, this is assigned to Daniel Hardman. Someone needs to write a PR. Does anyone feel strongly about this? 16:51:39 I can 16:51:40 try 16:51:58 manu: Assigned to Orie 16:52:28 ivan: We need a few min for the Special Topic Call 16:52:33 https://github.com/w3c/did-core/issues/453 16:52:48 I'm looking at that one 16:52:56 manu: 453, I'm assigned, but I don't think I'm the right person to do the PR. 16:53:16 shigeya: I think I could do something. 16:53:22 manu: Assigned to rhiaro 16:53:30 https://github.com/w3c/did-core/issues/337 16:53:41 manu: 337 dbuc are you going to write a PR for this, or should someone else? 16:53:41 q+ 16:53:48 please assign me 16:53:54 dbuc: I'm a bit out of the loop how DID parameters have evolved. 16:54:02 dbuc: It seems there's complexity I'm unaware of 16:54:19 manu: Assigned to Orie 16:54:49 527 is a dup really 16:55:07 manu: 527, 530, 532, 523 can probably stay the way they are 16:55:17 I commented. Sure 16:55:31 Topic: next topic call 16:55:57 manu: We're through. We marked almost none as potentially defer. If the assigned people don't do a PR, they will either be deferred or closed. 16:56:47 ivan: The agenda that was sent out had a mistake. It said DID Core vocabularies. Instead there was a separate email by Brent. The call will be about herd privacy and drummond's appendix. It will be on Thursday at the usual time. 16:56:49 q+ 16:57:05 q- 16:57:06 ack Orie 16:57:41 drummond: I want to encourage folks to come to that call. I prepared a short deck for the Special Topic Call, I'll post the link. 16:57:51 drummond: I'm hoping this will be a very productive call. 16:58:08 Link to a backgrounder deck on the herd privacy issue: https://docs.google.com/presentation/d/1z7Ml8KI1-A5tGW6pxfIqgGkdP0w0qwlsRXXk2v8Tl00/edit?usp=sharing 16:58:22 I will also post that to relevant issues and PRs. 16:58:40 ivan: Goodbye, thank you. 16:58:53 rrsagent, draft minutes 16:58:53 I have made the request to generate https://www.w3.org/2021/01/12-did-minutes.html ivan 16:59:04 zakim, end meeting 16:59:05 As of this point the attendees have been ivan, markus_sabadello, shigeya, justin_r, TallTed, manu, adrian, identitywoman, Orie, agropper, phila, dlongley, JoeAndrieu, drummond, 16:59:05 ... jonathan_holt, dbuc, rhiaro 16:59:05 RRSAgent, please draft minutes 16:59:05 I have made the request to generate https://www.w3.org/2021/01/12-did-minutes.html Zakim 16:59:10 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:59:14 Zakim has left #did 16:59:28 identitywoman has joined #did 16:59:35 present+ 16:59:48 (i was in the meeting the whole time today just got on IRC now) 17:00:26 I have actually put you on the list, Kaliya 17:10:24 ivan has joined #did