The OAuth group discovered a problem with some the names of our new OAuth
fields that was caused by the fact that they have an ID that is someplace
between the IESG and the RFC Editor which introduced the concept of using a
JWT to as the transport for an OAuth request. This allows for doing
end-to
On 04/10/18 03:47, Jim Schaad wrote:
The OAuth group discovered a problem with some the names of our new OAuth
fields that was caused by the fact that they have an ID that is someplace
between the IESG and the RFC Editor which introduced the concept of using a
JWT to as the transport for an OAuth
Jim Schaad wrote:
> The OAuth group discovered a problem with some the names of our new
> OAuth fields that was caused by the fact that they have an ID that is
> someplace between the IESG and the RFC Editor which introduced the
Took a moment to realize that ID = Internet Draft, rath
> -Original Message-
> From: Michael Richardson
> Sent: Thursday, October 4, 2018 6:45 AM
> To: Jim Schaad
> Cc: ace@ietf.org
> Subject: Re: [Ace] JWT + OAuth Request
>
>
> Jim Schaad wrote:
> > The OAuth group discovered a problem with some t
