Brian Campbell

Also HTTP/3 ietf-quic-http -> RFC9114 QPACK ietf-quic-qpack -> RFC9204

While acknowledging that [impedance mismatch](https://lists.w3.org/Archives/Public/ietf-http-wg/2020AprJun/0059.html) and associated issues, the scope of the draft is only about conveying the client cert info and not any new error signaling or attempts at...

PR #2257 basically adds this sentence, "Access control decisions based on the client certificate (or lack thereof) can be conveyed by selecting response content as appropriate or with an HTTP...

Makes sense. Will look at adjusting the text accordingly.

In [this conversation](https://github.com/httpwg/http-extensions/pull/1874#pullrequestreview-841081689) on the PR that introduced the chain I was aiming for 2. But eventually relented to MT. Some additional considerations about the security implications are likely warranted...

At the last virtual interim (in May/June yikes!) Martin kindly suggested that I was making this too complicated and to just make the change (paraphrasing). I've tried to do that...

> It seems like it could be helpful to implementors, allowing them to quickly validate whether what they have is syntactically an SD-JWT or an SD-JWT with key binding. Something...

That's a good improvement, thanks!

maybe add a KB-JWT line to be even more better? a la: ``` ALPHA = %x41-5A / %x61-7A ; A-Z / a-z DIGIT = %x30-39 ; 0-9 base64url = 1*(ALPHA...

> > @Sakurann - Changed to `SD-JWT-KB`, since the `SD-JWT/KB` looked weird to me (division seemed like the wrong metaphor) and `SD-JWT~KB` seemed a little too cute. Also merged `master`...