[{"author": "Robert Moskowitz", "text": "<p>I thought I saw daylight through the window.</p>", "time": "2026-03-18T03:30:14.000Z"}, {"author": "Martin Thomson", "text": "<p>ekrbot will take notes for us</p>", "time": "2026-03-18T03:31:39.000Z"}, {"author": "Sean Turner", "text": "<p>Remote Room2 - is the Taki room in Japan. There's Martin, Rohan, Joe, Wes, and myself currently present.</p>", "time": "2026-03-18T03:31:56.000Z"}, {"author": "Martin Thomson", "text": "<p>absolutely, ekrbot is not trustworthy</p>", "time": "2026-03-18T03:32:01.000Z"}, {"author": "David Waite", "text": "<p>how many of the no votes were no I hadn't read the charter additions?</p>", "time": "2026-03-18T03:36:28.000Z"}, {"author": "Christopher Inacio", "text": "<p>the way the question was worded could be that \"no\" could mean the list message wasn't read</p>", "time": "2026-03-18T03:36:29.000Z"}, {"author": "Carsten Bormann", "text": "<p>Yes</p>", "time": "2026-03-18T03:36:51.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention silent\" data-user-id=\"1195\">Christopher Inacio</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/209974\">said</a>:</p>\n<blockquote>\n<p>the way the question was worded could be that \"no\" could mean the list message wasn't read</p>\n</blockquote>\n<p>OOps, yes, that's a problem.  But I assumed that people could read the slide</p>", "time": "2026-03-18T03:36:53.000Z"}, {"author": "Nathanael Ritz", "text": "<p>But I really wanna.</p>", "time": "2026-03-18T03:37:14.000Z"}, {"author": "Brent Zundel", "text": "<p>I\u2019m hoping folks who didn\u2019t read it indicated no opinion</p>", "time": "2026-03-18T03:37:15.000Z"}, {"author": "Martin Thomson", "text": "<p>Obviously, if we don't get negative feedback, that's information.</p>", "time": "2026-03-18T03:37:35.000Z"}, {"author": "Carsten Bormann", "text": "<p>We'll get the input from the real no people</p>", "time": "2026-03-18T03:37:42.000Z"}, {"author": "David Waite", "text": "<p>I'm vibe coding a cryptography library but I only recommend production usage by AI agents</p>", "time": "2026-03-18T03:37:48.000Z"}, {"author": "Pieter Kasselman", "text": "<p>You think your joking David..</p>", "time": "2026-03-18T03:38:08.000Z"}, {"author": "Nathanael Ritz", "text": "<p>IETFMolt</p>", "time": "2026-03-18T03:38:41.000Z"}, {"author": "Richard Barnes", "text": "<p>DID is not a certificate</p>", "time": "2026-03-18T03:38:59.000Z"}, {"author": "Richard Barnes", "text": "<p>Even a DID document is not a certificate</p>", "time": "2026-03-18T03:39:08.000Z"}, {"author": "Justin Richer", "text": "<p>DIDdoc is a certificate :P</p>", "time": "2026-03-18T03:39:14.000Z"}, {"author": "Richard Barnes", "text": "<p>At most it is a self-signed certificate</p>", "time": "2026-03-18T03:39:17.000Z"}, {"author": "Orie Steele", "text": "<p>Oh no heck DIDnt</p>", "time": "2026-03-18T03:39:18.000Z"}, {"author": "Orie Steele", "text": "<p>Henk*</p>", "time": "2026-03-18T03:39:29.000Z"}, {"author": "Richard Barnes", "text": "<p>wait what?</p>", "time": "2026-03-18T03:46:44.000Z"}, {"author": "Martin Thomson", "text": "<p>My view on THAT is that we can define claims in support of advancing this work without a recharter.</p>", "time": "2026-03-18T03:46:47.000Z"}, {"author": "Richard Barnes", "text": "<p>why would you need a separate work item?</p>", "time": "2026-03-18T03:46:50.000Z"}, {"author": "Martin Thomson", "text": "<p>So yes, what Richard said.</p>", "time": "2026-03-18T03:47:00.000Z"}, {"author": "Richard Barnes", "text": "<p><span class=\"user-mention\" data-user-id=\"26\">@Martin Thomson</span> seems like chairs prerogative to clarify that</p>", "time": "2026-03-18T03:47:15.000Z"}, {"author": "Martin Thomson", "text": "<p>I did.  But we're short on time and I want to give Rohan as much of it as possible.</p>", "time": "2026-03-18T03:47:39.000Z"}, {"author": "Richard Barnes", "text": "<p>+1 for redact/disclose.  blind/unblind is a term of art in cryptography, e.g., \"blinded signatures\"</p>", "time": "2026-03-18T03:47:44.000Z"}, {"author": "Martin Thomson", "text": "<p>That point is a distraction.</p>", "time": "2026-03-18T03:47:44.000Z"}, {"author": "Martin Thomson", "text": "<p>Hide/reveal ?</p>", "time": "2026-03-18T03:48:02.000Z"}, {"author": "Richard Barnes", "text": "<p>\"unredact\" is the word for \"unredact\"</p>", "time": "2026-03-18T03:48:04.000Z"}, {"author": "Nathanael Ritz", "text": "<p>leak</p>", "time": "2026-03-18T03:48:04.000Z"}, {"author": "Orie Steele", "text": "<p>+1 Richard</p>", "time": "2026-03-18T03:48:05.000Z"}, {"author": "Justin Richer", "text": "<p>isn't unredact the word for unredact?</p>", "time": "2026-03-18T03:48:09.000Z"}, {"author": "Martin Thomson", "text": "<p>Isn't redaction irreversible?</p>", "time": "2026-03-18T03:48:21.000Z"}, {"author": "Martin Thomson", "text": "<p>The black highlighter doesn't come off.</p>", "time": "2026-03-18T03:48:28.000Z"}, {"author": "Sean Turner", "text": "<p>\"blot out\"</p>", "time": "2026-03-18T03:48:30.000Z"}, {"author": "Justin Richer", "text": "<p>@martin depends on how you do it</p>", "time": "2026-03-18T03:48:35.000Z"}, {"author": "Richard Barnes", "text": "<p><a href=\"https://theonion.com/cia-realizes-its-been-using-black-highlighters-all-thes-1819568147/\">https://theonion.com/cia-realizes-its-been-using-black-highlighters-all-thes-1819568147/</a></p>", "time": "2026-03-18T03:48:37.000Z"}, {"author": "Orie Steele", "text": "<p>Depends on how good you are with PDFs</p>", "time": "2026-03-18T03:48:40.000Z"}, {"author": "Nathanael Ritz", "text": "<p>@Martin not if you are Adobe PDF</p>", "time": "2026-03-18T03:48:43.000Z"}, {"author": "Nathanael Ritz", "text": "<p>lol same</p>", "time": "2026-03-18T03:48:47.000Z"}, {"author": "Richard Barnes", "text": "<p>also, why are we not just doing whatever SD-JWT does</p>", "time": "2026-03-18T03:48:49.000Z"}, {"author": "Carsten Bormann", "text": "<p>I think we can still get \"unredact\" for $0.50.</p>", "time": "2026-03-18T03:48:51.000Z"}, {"author": "Brian Campbell", "text": "<p>FWIW, vct is hopefully <em>going</em> to be registered by SD-JWT VC not SD-JWT</p>", "time": "2026-03-18T03:48:53.000Z"}, {"author": "Nathanael Ritz", "text": "<p>Redact/Bare?</p>", "time": "2026-03-18T03:50:04.000Z"}, {"author": "Brian Campbell", "text": "<p>we did have words</p>", "time": "2026-03-18T03:50:31.000Z"}, {"author": "Brian Campbell", "text": "<p>not sure they are consistent</p>", "time": "2026-03-18T03:50:41.000Z"}, {"author": "Justin Richer", "text": "<p>they were redacted</p>", "time": "2026-03-18T03:50:41.000Z"}, {"author": "Richard Barnes", "text": "<p>i mean, even if they were not consistent</p>", "time": "2026-03-18T03:50:45.000Z"}, {"author": "Richard Barnes", "text": "<p>that's my answer for basically every question here. \"Why not just do what SD-JWT did\"</p>", "time": "2026-03-18T03:51:21.000Z"}, {"author": "Richard Barnes", "text": "<p>this is just a re-encoding, not a re-imagining</p>", "time": "2026-03-18T03:51:30.000Z"}, {"author": "Brian Campbell", "text": "<p>is it though?</p>", "time": "2026-03-18T03:51:47.000Z"}, {"author": "Richard Barnes", "text": "<p>well it ought to be</p>", "time": "2026-03-18T03:51:53.000Z"}, {"author": "Richard Barnes", "text": "<p>if i were writing it, i would have literally taken the SD-JWT spec and had Claude change JSON to CBOR</p>", "time": "2026-03-18T03:52:07.000Z"}, {"author": "Orie Steele", "text": "<p>There are a few \u201cnew things\u201d\u2026. Encrypted disclosures, and presentation format does not need the \u201c~\u201d + hash thing that so-just has</p>", "time": "2026-03-18T03:52:33.000Z"}, {"author": "Brian Campbell", "text": "<p>you might need to underedact that</p>", "time": "2026-03-18T03:52:38.000Z"}, {"author": "Brian Campbell", "text": "<p>there's a whole encryption thing too</p>", "time": "2026-03-18T03:53:10.000Z"}, {"author": "Orie Steele", "text": "<p>Yeah, what Brian said.</p>", "time": "2026-03-18T03:53:26.000Z"}, {"author": "Henk Birkholz", "text": "<p>Timers hel</p>", "time": "2026-03-18T03:53:56.000Z"}, {"author": "Henk Birkholz", "text": "<p>P</p>", "time": "2026-03-18T03:54:00.000Z"}, {"author": "Heather Flanagan", "text": "<p>Yes, I know. Had one going, too.</p>", "time": "2026-03-18T03:54:15.000Z"}, {"author": "Brian Campbell", "text": "<p>SD-JWT did not have encryption</p>", "time": "2026-03-18T03:54:38.000Z"}, {"author": "Brian Campbell", "text": "<p>on purpose</p>", "time": "2026-03-18T03:54:46.000Z"}, {"author": "Richard Barnes", "text": "<p>for goodness sake, non-AEAD is dead in the modern world</p>", "time": "2026-03-18T03:54:49.000Z"}, {"author": "Martin Thomson", "text": "<p>The data is authenticated.  Via a hash.</p>", "time": "2026-03-18T03:54:54.000Z"}, {"author": "Richard Barnes", "text": "<p>still</p>", "time": "2026-03-18T03:55:17.000Z"}, {"author": "Martin Thomson", "text": "<p>The problem with AEAD is that there are many potential ciphertexts that are valid according to the key. There is only one plaintext that hashes to the provided value.</p>", "time": "2026-03-18T03:55:31.000Z"}, {"author": "Richard Barnes", "text": "<p><span class=\"user-mention\" data-user-id=\"26\">@Martin Thomson</span> that doesn't sound like a problem.  just use the right ciphertext.</p>", "time": "2026-03-18T03:56:09.000Z"}, {"author": "Nathanael Ritz", "text": "<p>So basically why not HKDF all the things?</p>", "time": "2026-03-18T03:56:19.000Z"}, {"author": "Richard Barnes", "text": "<p>i already issued my threat</p>", "time": "2026-03-18T03:56:55.000Z"}, {"author": "Richard Barnes", "text": "<p>:)</p>", "time": "2026-03-18T03:56:57.000Z"}, {"author": "Brent Zundel", "text": "<p>Two buttons meme:</p>", "time": "2026-03-18T03:57:41.000Z"}, {"author": "Brent Zundel", "text": "<p>use AEAD in sd-cwt vs Richard Barnes as Sec AD</p>", "time": "2026-03-18T03:58:23.000Z"}, {"author": "Martin Thomson", "text": "<p>(4/3)^6 FTW</p>", "time": "2026-03-18T03:58:26.000Z"}, {"author": "Brian Campbell", "text": "<p>i am admittedly not very smart but still don't understand why encrypt anything in this</p>", "time": "2026-03-18T03:58:29.000Z"}, {"author": "Martin Thomson", "text": "<p>Selective disclosure on SPEED!</p>", "time": "2026-03-18T03:58:45.000Z"}, {"author": "Martin Thomson", "text": "<p>Encryption gives you more power over who gets to see what..</p>", "time": "2026-03-18T03:59:01.000Z"}, {"author": "Richard Barnes", "text": "<p><span class=\"user-mention silent\" data-user-id=\"7517\">Brian Campbell</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210118\">said</a>:</p>\n<blockquote>\n<p>i am admittedly not very smart but still don't understand why encrypt anything in this</p>\n</blockquote>\n<p>i am also confused by this</p>", "time": "2026-03-18T03:59:04.000Z"}, {"author": "Richard Barnes", "text": "<p><span class=\"user-mention silent\" data-user-id=\"26\">Martin Thomson</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210122\">said</a>:</p>\n<blockquote>\n<p>Encryption gives you more power over who gets to see what..</p>\n</blockquote>\n<p>seems like layer confusion</p>", "time": "2026-03-18T03:59:14.000Z"}, {"author": "Orie Steele", "text": "<p>@brian the use case is for tunneling som disclosures to an inner verifier.. basically not all audiences need to see all claims</p>", "time": "2026-03-18T03:59:27.000Z"}, {"author": "Richard Barnes", "text": "<p>don't send the disclosures to the verifiers that don't need them</p>", "time": "2026-03-18T03:59:45.000Z"}, {"author": "Richard Barnes", "text": "<p>??</p>", "time": "2026-03-18T03:59:50.000Z"}, {"author": "Brian Campbell", "text": "<p>@orie I stand by my comment</p>", "time": "2026-03-18T04:00:01.000Z"}, {"author": "Robert Moskowitz", "text": "<p>Wow, a human in the room.</p>", "time": "2026-03-18T04:00:01.000Z"}, {"author": "Martin Thomson", "text": "<p>I do wonder whether encrypted disclosures could be an extension...</p>", "time": "2026-03-18T04:00:03.000Z"}, {"author": "Martin Thomson", "text": "<p>(For clarity, none of my comments on this encryption piece should be construed as chair positions.)</p>", "time": "2026-03-18T04:00:25.000Z"}, {"author": "Richard Barnes", "text": "<p>it definitely seems like you could do a post-hoc transform that just encrypts the disclosures, though see my earlier \"why???\"</p>", "time": "2026-03-18T04:00:36.000Z"}, {"author": "Brian Campbell", "text": "<p>mine either</p>", "time": "2026-03-18T04:00:36.000Z"}, {"author": "Henk Birkholz", "text": "<p>Possibly, but they fit fine in the id currently</p>", "time": "2026-03-18T04:00:40.000Z"}, {"author": "Rohan Mahy", "text": "<p><span class=\"user-mention silent\" data-user-id=\"26\">Martin Thomson</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210038\">said</a>:</p>\n<blockquote>\n<p>Isn't redaction irreversible?</p>\n</blockquote>\n<p>hence \"unblind\" or \"disclose\"</p>", "time": "2026-03-18T04:00:42.000Z"}, {"author": "Martin Thomson", "text": "<p>I like hide/reveal or conceal/reveal.  But the \"what did SD-JWT do\" argument is pretty strong.</p>", "time": "2026-03-18T04:01:21.000Z"}, {"author": "Josh G", "text": "<p>redaction would seem to be revert-able but not reversible</p>", "time": "2026-03-18T04:01:37.000Z"}, {"author": "Nathanael Ritz", "text": "<p>Is \"Holder\" akin to \"Bearer\" a la OAuth?</p>", "time": "2026-03-18T04:01:53.000Z"}, {"author": "Richard Barnes", "text": "<p>\"blind\" does not appear in the SD-JWT RFC</p>", "time": "2026-03-18T04:01:54.000Z"}, {"author": "Brian Campbell", "text": "<p>per Orie, we also apparently need an inner verifier</p>", "time": "2026-03-18T04:01:58.000Z"}, {"author": "Robert Moskowitz", "text": "<p>IMO it is always at least a 3-party model.  I don't think there is any 2-party model for these things.  n-party messes do exist.  So expressing the 3-party seems reasonable.</p>", "time": "2026-03-18T04:02:05.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"4175\">@Josh G</span> only if you accept a world where the arrow of time can be reversed.</p>", "time": "2026-03-18T04:02:16.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"3598\">@Brent Zundel</span> are you serious about that flow diagram?  because that diagram won't fit in 72 columns.</p>", "time": "2026-03-18T04:03:05.000Z"}, {"author": "Richard Barnes", "text": "<p>somehow PKIX has gotten by with the subject/CA/RP trichotomy just fine for decades</p>", "time": "2026-03-18T04:03:09.000Z"}, {"author": "Josh G", "text": "<p>I'm not sure such deep consideration went into SD-JWT</p>", "time": "2026-03-18T04:03:14.000Z"}, {"author": "Rohan Mahy", "text": "<p><span class=\"user-mention silent\" data-user-id=\"115\">Carsten Bormann</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210051\">said</a>:</p>\n<blockquote>\n<p>I think we can still get \"unredact\" for $0.50.</p>\n</blockquote>\n<p>Pat, I'd like to buy a vowel please</p>", "time": "2026-03-18T04:03:18.000Z"}, {"author": "Nathanael Ritz", "text": "<p>Not with that attitude</p>", "time": "2026-03-18T04:03:20.000Z"}, {"author": "Carsten Bormann", "text": "<p>What is RFC track?</p>", "time": "2026-03-18T04:04:01.000Z"}, {"author": "Brian Campbell", "text": "<p>i suspect 'blind' is one of the words would be considered problematic in that document that isn't available on us gov related websites</p>", "time": "2026-03-18T04:04:14.000Z"}, {"author": "David Waite", "text": "<p>FWIW Credential Management API now defines what a Credential Manager is. <a href=\"https://w3c.github.io/webappsec-credential-management/#credential-manager\">https://w3c.github.io/webappsec-credential-management/#credential-manager</a></p>", "time": "2026-03-18T04:04:47.000Z"}, {"author": "Nathanael Ritz", "text": "<p>The bait worked.</p>", "time": "2026-03-18T04:07:37.000Z"}, {"author": "Martin Thomson", "text": "<p>It sounds like Brian has WGLC comments on SD-CWT.</p>", "time": "2026-03-18T04:07:41.000Z"}, {"author": "Orie Steele", "text": "<p>RATs has \u201cVerifier\u201d as a separate thing from RP \u201cRelying party\u201d</p>", "time": "2026-03-18T04:08:37.000Z"}, {"author": "Brian Campbell", "text": "<p>my inner voice has comments apparently</p>", "time": "2026-03-18T04:08:49.000Z"}, {"author": "Brian Campbell", "text": "<p>that came out</p>", "time": "2026-03-18T04:08:53.000Z"}, {"author": "Justin Richer", "text": "<p>proud of you, heather</p>", "time": "2026-03-18T04:08:59.000Z"}, {"author": "Orie Steele", "text": "<p>I was sorta joking, but sorta not\u2026. The use case for the encrypted disclosure should probably be put in context of those, to avoid further confusion</p>", "time": "2026-03-18T04:09:14.000Z"}, {"author": "Orie Steele", "text": "<p>So basically I agree with Brian\u2019s bait.</p>", "time": "2026-03-18T04:09:49.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention silent\" data-user-id=\"7517\">Brian Campbell</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210201\">said</a>:</p>\n<blockquote>\n<p>my inner voice has comments apparently</p>\n</blockquote>\n<p>Happy to hear those translated into email form.  Maybe this will be RATS-baiting only and this is already resolved over there, but still worth having it expressed.</p>", "time": "2026-03-18T04:10:17.000Z"}, {"author": "Brian Campbell", "text": "<p>i was sorta joking and sorta not too. I agree with that, if the WG really wants to keep that stuff.</p>", "time": "2026-03-18T04:10:27.000Z"}, {"author": "Heather Flanagan", "text": "<p>@justin #winning</p>", "time": "2026-03-18T04:10:27.000Z"}, {"author": "Carsten Bormann", "text": "<p>Is this SCITT or SPICE?</p>", "time": "2026-03-18T04:11:40.000Z"}, {"author": "Brent Zundel", "text": "<p>SPICE</p>", "time": "2026-03-18T04:11:58.000Z"}, {"author": "Martin Thomson", "text": "<p>\"multiple implementations\" == necessary but not sufficient.</p>", "time": "2026-03-18T04:12:01.000Z"}, {"author": "Carsten Bormann", "text": "<p>Why are we discussing something that looks like SCITT?</p>", "time": "2026-03-18T04:12:16.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"115\">@Carsten Bormann</span> you know where the queue button is.</p>", "time": "2026-03-18T04:12:44.000Z"}, {"author": "Orie Steele", "text": "<p>We did a draft that adjusted claims from JWT / CWT regarding OIDC\u2026 I see this as sorta like that\u2026 but more domain specific\u2026 but Carsten raises a great point.</p>", "time": "2026-03-18T04:13:02.000Z"}, {"author": "Carsten Bormann", "text": "<p>I didn't want to waste time if I'm just not updated.</p>", "time": "2026-03-18T04:13:04.000Z"}, {"author": "Brian Campbell", "text": "<p>\"RATS-baiting\" is wonderful btw</p>", "time": "2026-03-18T04:13:23.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention silent\" data-user-id=\"115\">Carsten Bormann</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210230\">said</a>:</p>\n<blockquote>\n<p>I didn't want to waste time if I'm just not updated.</p>\n</blockquote>\n<p>I don't know if we've really gotten to the bottom of this.</p>", "time": "2026-03-18T04:13:35.000Z"}, {"author": "Carsten Bormann", "text": "<p>Thanks.</p>", "time": "2026-03-18T04:13:43.000Z"}, {"author": "Martin Thomson", "text": "<p>If we have participation, perhaps those participants can help us set some scope bounds.  The set of claims they collectively want.  The challenge here, as Mike articulated is that there is a piece of string that you could pull on almost indefinitely.</p>", "time": "2026-03-18T04:15:14.000Z"}, {"author": "Brian Campbell", "text": "<p>but I've not looked at RATS nor do I anticipate finding the appetite to do so anytime in the foreseeable future</p>", "time": "2026-03-18T04:15:50.000Z"}, {"author": "Martin Thomson", "text": "<p>Forum shopping is not the answer to the question. We can coordinate amongst different groups to find the right venue.</p>", "time": "2026-03-18T04:16:41.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"4268\">@Wes Hardaker</span> <a href=\"https://datatracker.ietf.org/doc/draft-prorock-spice-cwt-traceability-claims/\">https://datatracker.ietf.org/doc/draft-prorock-spice-cwt-traceability-claims/</a></p>", "time": "2026-03-18T04:17:35.000Z"}, {"author": "Brian Campbell", "text": "<p>something about key discovery and scope?</p>", "time": "2026-03-18T04:18:53.000Z"}, {"author": "Heather Flanagan", "text": "<p>Thanks, @Carsten</p>", "time": "2026-03-18T04:19:09.000Z"}, {"author": "Brian Campbell", "text": "<p>or am I out of touch? (again)</p>", "time": "2026-03-18T04:19:11.000Z"}, {"author": "Heather Flanagan", "text": "<p>Missed that feature</p>", "time": "2026-03-18T04:19:14.000Z"}, {"author": "Martin Thomson", "text": "<p>We've used that feature in meetings in the past, though I realize that maybe it was the case that <em>I</em> used that feature.</p>", "time": "2026-03-18T04:19:37.000Z"}, {"author": "Heather Flanagan", "text": "<p>I expect we have. My memory can't be trusted for something I use only 3 times a year. :-)</p>", "time": "2026-03-18T04:20:10.000Z"}, {"author": "Martin Thomson", "text": "<p>It isn't exactly intuitive, definitely.</p>", "time": "2026-03-18T04:20:31.000Z"}, {"author": "Paul Wouters", "text": "<p>heather: so do more interims :)</p>", "time": "2026-03-18T04:20:38.000Z"}, {"author": "Carsten Bormann", "text": "<p>bi-weekly works wonders</p>", "time": "2026-03-18T04:20:54.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"43\">@Paul Wouters</span> the answer is almost never \"more meetings\"</p>", "time": "2026-03-18T04:20:56.000Z"}, {"author": "Orie Steele", "text": "<p>Is a DID Method a specific type of PKSP?</p>", "time": "2026-03-18T04:21:06.000Z"}, {"author": "Heather Flanagan", "text": "<p>@Paul I was rather thinking we needed to do that, but not so I can get more familiar with the tools. That would be mean of me. Fun, but mean.</p>", "time": "2026-03-18T04:21:13.000Z"}, {"author": "Michael StJohns", "text": "<p>I hate to say this but PKSP ~= single point of failure??</p>", "time": "2026-03-18T04:21:42.000Z"}, {"author": "Martin Thomson", "text": "<p>did:plc: ftw!</p>", "time": "2026-03-18T04:22:01.000Z"}, {"author": "Carsten Bormann", "text": "<p>Will this work as well as the PGP keyservers?</p>", "time": "2026-03-18T04:22:10.000Z"}, {"author": "Martin Thomson", "text": "<p><span class=\"user-mention\" data-user-id=\"435\">@Michael StJohns</span> SPOF can be addressed within the architecture of the single point of failure, right?</p>", "time": "2026-03-18T04:22:33.000Z"}, {"author": "Michael StJohns", "text": "<p>I'm looking at the document and this looks monolithic...</p>", "time": "2026-03-18T04:22:59.000Z"}, {"author": "Martin Thomson", "text": "<p>This could also be a PKI.</p>", "time": "2026-03-18T04:23:05.000Z"}, {"author": "Orie Steele", "text": "<p>hmm, watching verifiers pull issuer keys is a nice control point\u2026 but limits applicability</p>", "time": "2026-03-18T04:23:20.000Z"}, {"author": "Michael StJohns", "text": "<p>And I'm not sure about the \"authenticates the verifier\" thing...</p>", "time": "2026-03-18T04:23:42.000Z"}, {"author": "Nathanael Ritz", "text": "<p>I'm anxious about the PKSP being a big shiny treasure trove</p>", "time": "2026-03-18T04:24:59.000Z"}, {"author": "Martin Thomson", "text": "<p>Isn't it the case that there is a need for trust between the verifiers and PKSP?  I mean, there is a lightweight trust requirement on issuers to trust that the PKSP presents their keys faithfully.</p>", "time": "2026-03-18T04:26:49.000Z"}, {"author": "Jonathan Hammell", "text": "<p>keytrans is meeting in parallel to this session</p>", "time": "2026-03-18T04:27:37.000Z"}, {"author": "Martin Thomson", "text": "<p>is there some sort of AGC on this meeting?  because MSJ was VERY loud here relative to all other speakers.</p>", "time": "2026-03-18T04:27:53.000Z"}, {"author": "Michael StJohns", "text": "<p>@martin - sorry about that</p>", "time": "2026-03-18T04:28:09.000Z"}, {"author": "Martin Thomson", "text": "<p>Totally not your fault</p>", "time": "2026-03-18T04:28:19.000Z"}, {"author": "Martin Thomson", "text": "<p>VIdeoconferencing systems generally have automatic gain control to manage that.</p>", "time": "2026-03-18T04:28:47.000Z"}, {"author": "Carsten Bormann", "text": "<p>Which doesn't help if the source is clippping</p>", "time": "2026-03-18T04:29:04.000Z"}, {"author": "Brian Campbell", "text": "<p><span class=\"user-mention silent\" data-user-id=\"26\">Martin Thomson</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210213\">said</a>:</p>\n<blockquote>\n<p><span class=\"user-mention silent\" data-user-id=\"7517\">Brian Campbell</span> <a href=\"#narrow/channel/379-spice/topic/ietf-125/near/210201\">said</a>:</p>\n<blockquote>\n<p>my inner voice has comments apparently</p>\n</blockquote>\n<p>Happy to hear those translated into email form.  Maybe this will be RATS-baiting only and this is already resolved over there, but still worth having it expressed.</p>\n</blockquote>\n<p>I am not allowed to use my work email here so honestly unlikely this will ever be translated into email form. TBH the work email is just a convenient excuse. My feedback is mostly just don't do confusing things that aren't explained for reasons you probably don't have.</p>", "time": "2026-03-18T04:29:18.000Z"}, {"author": "Justin Richer", "text": "<p>this sounds like it should be in WIMSE not SPICE?</p>", "time": "2026-03-18T04:29:56.000Z"}, {"author": "Rohan Mahy", "text": "<p><span class=\"user-mention\" data-user-id=\"7526\">@A. Prasad</span>  out of curiosity, did you bring this to OAUTH already? <br>\nIs it only for JWTs or for both CWTs and JWTs?</p>", "time": "2026-03-18T04:30:06.000Z"}, {"author": "Nathanael Ritz", "text": "<p>OAuth has Identity Chaining too</p>", "time": "2026-03-18T04:30:32.000Z"}, {"author": "Carsten Bormann", "text": "<p>(Heather: just go on as a hallway meeting for a couple more minutes)</p>", "time": "2026-03-18T04:30:44.000Z"}, {"author": "Heather Flanagan", "text": "<p>How does one do that?</p>", "time": "2026-03-18T04:31:06.000Z"}, {"author": "Carsten Bormann", "text": "<p>Just ignore the clock, and maybe say this is no longer a WG meeting</p>", "time": "2026-03-18T04:31:22.000Z"}, {"author": "Martin Thomson", "text": "<p>THIS IS NO LONGER A WG MEETING!</p>", "time": "2026-03-18T04:31:37.000Z"}, {"author": "Brian Campbell", "text": "<p>It seems I am in the rough, as the grey beards and golfers of my skill level say, however, and have no interest in discussing more</p>", "time": "2026-03-18T04:31:40.000Z"}, {"author": "Carsten Bormann", "text": "<p>Thanks, Martin</p>", "time": "2026-03-18T04:31:49.000Z"}, {"author": "Lorenzo Miniero", "text": "<p>We never close meetings abruptly, no worries</p>", "time": "2026-03-18T04:31:59.000Z"}, {"author": "Martin Thomson", "text": "<p>We are done with formal proceedings.  Stick around a short time if you want to hear more from our presenter.</p>", "time": "2026-03-18T04:32:00.000Z"}, {"author": "Martin Thomson", "text": "<p>But we won't be here much longer.  Some of us have things to do.</p>", "time": "2026-03-18T04:32:14.000Z"}, {"author": "Justin Richer", "text": "<p>is there a signature on top of the achd?</p>", "time": "2026-03-18T04:32:43.000Z"}, {"author": "Henk Birkholz", "text": "<p>Thanks all!</p>", "time": "2026-03-18T04:33:26.000Z"}]