Brian Campbell

I don't think I can do justice to (un)observability so not sure I'm going to even attempt...

#506 has some discussion of selective disclosure and unlinkability and a bit of intro context

#43 is similar/duplicative FWIW

`jti` isn't wrong exactly but not quite right either and not where one would expect to see a challenge value placed.

I think that most folks have read https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.7 (also found in the registry https://www.iana.org/assignments/jwt/jwt.xhtml) to mean that the jti value is something decided on by the issuer/sender of the JWT....

The value of explicitly typing in the context of something like DBSC isn't as clear as some other JWT usages but it's probably worth doing nonetheless. And would certainly be...

This came up, more or less, in #47 FWIW.

> Be able to do more than one registration in a response I asked about this over here https://github.com/WICG/dbsc/issues/45#issuecomment-2048193103 too but would you be able to explain more about why...

> Use structured headers Lots of different ways to encode data with Structured Fields but perhaps a [dictionary](https://www.rfc-editor.org/rfc/rfc8941.html#name-dictionaries) with an [inner list](https://www.rfc-editor.org/rfc/rfc8941.html#section-4.1.1.1) value for the algorithms and string values for...

Thanks for the update @kmonsen. And thanks @arnar for that explanation that said what I was trying to say in part of this https://github.com/WICG/dbsc/issues/45#issuecomment-2048193103 but you said it better.