Agree with Mike's assessment. (One caveat to that is that I'm not close
enough to CWT to understand how scare the single byte identifiers actually
are.)
On Wed, Mar 11, 2020 at 4:39 PM Mike Jones
wrote:
> [Adding correct e-mail addresses for Chuck, who recently joined Visa]
>
>
>
> There are
On Wed, Mar 11, 2020 at 11:39:00PM +, Mike Jones wrote:
> [Adding correct e-mail addresses for Chuck, who recently joined Visa]
>
>
>
> There are two reasons that I believe not using up one of the scarce one-byte
> claim identifiers for "scope" is appropriate:
>
> 1. The claim values
[Adding correct e-mail addresses for Chuck, who recently joined Visa]
There are two reasons that I believe not using up one of the scarce one-byte
claim identifiers for "scope" is appropriate:
1. The claim values for scopes are not short themselves. They are sets of
ASCII strings
Hi Jim,
I believe you are right that the functionality is supported. In retrospect it
is good that Ludwig just imported the key transport necessary functionality
with draft-ietf-ace-oauth-params-12. Hence, you can do pretty everything
defined in draft-ietf-oauth-pop-key-distribution with the
