00:52:14 RRSAgent has joined #did 00:52:18 logging to https://www.w3.org/2024/11/08-did-irc 00:52:20 rrsagent, draft minutes 00:52:21 I have made the request to generate https://www.w3.org/2024/11/08-did-minutes.html burn 00:52:27 rrsagent, make logs public 00:53:51 present+ 00:55:36 Meeting: DID Working Group 00:55:39 Chair: Dan Burnett 01:00:03 present+ 01:10:57 drummond has joined #did 01:11:04 present+ 01:14:36 scribe+ 01:15:14 burn: gave instructions about scribing 01:15:36 Topic: Agenda Review, Introductions 01:16:09 burn: we will focus today's meeting on DID resolution issues 01:16:57 JennieM has joined #did 01:17:00 present+ joeandrieu 01:17:01 present+ 01:19:09 burn: provided an update about Gabe's entire team being laid off at Block TBD. 01:20:21 ...That's why he's not on today's call. Gabe has already applied as an invited expert. 01:20:36 Topic: DID Resolution Issue Processing 01:21:28 https://github.com/w3c/did-resolution/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc 01:22:02 Subtopic: https://github.com/w3c/did-resolution/issues/37 01:22:22 ...that link will show issues in the proper order. 01:23:42 ...subtopics that reference issues like that will automatically post an update to that issue. 01:26:29 joeandrieu: I think we've moved on from this issue (it was posted five years ago). 01:26:38 mashbean has joined #did 01:27:14 ...it is understood that at different points in time, your keys may have rotated. So resolvers need to understand to ask for the DID document current at a particular point in time or a particular version. 01:27:52 burn: yes, that's a helpful resolution to an issue. In the WebRTC WG, they called it "overtaken by events". 01:28:14 q+ drummond 01:28:16 ...however Joe also commented that it would be helpful to make sure it was clear in the spec. 01:29:27 drummond: if the spec doesn't make Markus' point clearly, it should 01:31:29 q+ 01:32:25 ack denkeni 01:32:26 scribe+ 01:32:32 ack 01:32:39 ack drummond 01:33:28 denkeni: key rotation has always been a key part of the spec, so is this a question of whether key state should be specified by a DID method. 01:35:36 ...he mentioned that Christopher Allen said once that "everything should expire". This applies to verifiable credentials. Have we ever considered that for DIDs? How does that apply to key rotations? 01:35:50 ...this topic needs more high-level discussions. 01:36:00 burn: this is about explicit versioning? 01:36:25 denkeni: should you rotate keys or have to change the DID URL? 01:36:28 q+ 01:37:19 jennieM: from the start of this WG, this was a topic: what happens when a DID method goes away completely. 01:37:47 ...we can see that in the minutes from the meeting of Sept 23rd at TPAC. 01:38:13 https://www.w3.org/2024/09/23-did-minutes.html#t11 01:38:18 q+ joeandrieu 01:38:29 ack drummond 01:38:48 drummond: this gets deep fast. 01:39:57 ... the question of the relationship of the state of a did document to a DID (what we used to call a naked DID, without the URL bits) and potentially to a DID URL which could include identifiers of a state. Whether its a version, a time, or something else. This is a complex question. 01:40:17 ... the original spec is fairly clear about when to use each method. 01:40:22 q+ 01:40:28 ack JennieM 01:40:44 ack joeandrieu 01:40:53 s/ack JennieM// 01:41:14 joeandrieu: this expiry question is a good one. I lean against having some state indicator in the raw DID itself. 01:41:34 ...but verification properties should have an expiration. And if they don't, I'd like to understand. 01:41:36 ack burn 01:42:33 mashbean has joined #did 01:43:22 burn: there is more to this issue that was in the initial response that he had been typing in this issue. 01:44:10 joeandrieu: can anyone check to see if verification methods have an expiration property. 01:45:11 drummond: we should clarify whether verification methods have an expiration property? 01:45:16 q+ 01:46:01 joeandrieu: if so, that could resolve this issue. If not, then that may open a larger question. 01:46:25 ...it also raises the larger question of whether the root DID document might need an expiration property. 01:47:00 drummond: yes, I don't remember that ever coming up, but that could indeed make sense. 01:47:17 https://www.w3.org/TR/did-core/#key-and-signature-expiration 01:47:26 ack denkeni 01:47:58 denken: I added a link to the section about key and signature expiration in DID Core. 01:48:34 ...it raises the question of whether this is a DID Core issue, a DID Resolution issue, or a DID method issue. 01:48:56 ...this is relevant because we're going to start DID method standardization. 01:49:32 ...it could also be important for distinguishing between DID methods. 01:49:59 ...some DID methods may want to take responsibility for this control and some won't. 01:50:33 burn: I prefer this speed of conversation. Makes for better deliberation. 01:50:40 drummond: +1 01:51:09 subtopic: https://github.com/w3c/did-resolution/issues/28 01:53:06 present+ mashbean 01:54:39 burn: the real question is whether the DID Resolution spec adequately covers the question of local vs. remote resolvers. 01:55:14 ...the easiest way to resolve this issue would be to check with the submitter (Christopher Allen). 01:56:01 denkeni: This question of local vs. remote was "under the radar" when we implemented our DID Resolver because we required developers to verify the VDR. 01:56:33 ...so this question is worth investigating further, in particular when a mobile phone is running a resolver. 01:56:43 burn: could you add a comment directly? 01:56:49 denkeni: Yes. 01:57:21 burn: thanks to everyone who was able to come today. This was a good start on some very old issues. 01:58:31 rrsagent, make minutes 01:58:32 I have made the request to generate https://www.w3.org/2024/11/08-did-minutes.html burn 01:58:52 rrsagent, make logs public 01:59:40 s/denken: I added/denkeni: I added/ 02:01:11 this is junk that contains a / in it 02:01:23 s:this is junk that contains a / in it:: 02:01:31 JennieM has joined #did 02:02:12 this is even worse 02:02:23 sqthis is even worseqq 02:02:46 another example 02:03:12 sqanother exampleqyet another exampleq 02:03:31 sqyet another exampleqq 02:03:57 drummond is a jerk 02:04:03 s/drummond is a jerk// 03:16:48 TallTed has joined #did 07:26:08 brentz has joined #did 13:07:08 brent has joined #did 13:33:24 brent has joined #did 14:58:14 TallTed has joined #did 15:17:15 Zakim has left #did 23:23:58 brent has joined #did