All,
Based on the feedback in Prague and the responses to this call for
adoption, we declare the *Transaction Tokens *draft adopted as a WG
document.
Authors,
Feel free to submit a -00 version of the WG document at your convenience,
that has the same content of the latest individual document.
All,
Based on the feedback in Prague and the responses to this call for
adoption, we declare the *Identity Chaining *draft *adopted* as a WG
document.
Authors,
Feel free to submit a -00 version of the WG document at your convenience,
that has the same content of the latest individual document.
ya know - there was a time when a standard could have a conformance test
and then the implementations worked together.
Now standards are just wishful thinking. Something MIGHT work, or might
not.
interop was a feature of a standard. Now the standard is wishful thinking
and interop profile comes af
Media type parameters are useful for subtypes that add a multitude of expansion options, such as multimedia formats with a multitude of codecs, encoding options, and profiles to define feature sets. The best usages of them I’ve seen is supplemental. A baseline JWT isn’t really able to be customized
I agree with Mike. This exercise seems to add confusion rather than clarity.
thx ..Tom (mobile)
On Tue, Nov 28, 2023, 10:05 AM Michael Jones
wrote:
> Orie, you wrote:
>
>
>
> TLDR; TallTed believes that the convention in the JWT BCP is not correct:
>
> https://datatracker.ietf.org/doc/html/rfc8
Orie, you wrote:
TLDR; TallTed believes that the convention in the JWT BCP is not correct:
https://datatracker.ietf.org/doc/html/rfc8725#name-use-explicit-typing
So instead of seeing:
application/secevent+jwt
We should be seeing:
application/jwt; profile=secevent
For what it's worth, the
