DPoP mentions the **ASCII encoding** of a token value. This appears twice
in the spec:
*section 4.2. DPoP Proof JWT Syntax*...
ath: hash of the access token. The value MUST be the result of a base64url
encoding (as defined in Section 2 of [RFC7515]) the SHA-256 [SHS] hash of
the ASCII encoding of
All,
Dick, Giuseppe, and I submitted a new version of JWT Embedded Tokens
(previously known as Multi-Subject JWT).
https://www.ietf.org/archive/id/draft-yusef-oauth-nested-jwt-06.html
We would appreciate any feedback on this document.
Regards,
Rifaat (as individual)
