+1 for making all the CWT-like structures into real CWTs.
Grüße, Carsten
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
3.1, 3.2, and 4.1, parameter definitions: None of these parameter definitions
specify the syntax of the parameters defined, making understanding these quite
confusing. Yes, this is talked about later in the doc but there are not even
forward references to where the definitions are completed in
On 24/10/2018 03:44, Benjamin Kaduk wrote:
Just one minor note -- this is a great discussion to see happening!
On Tue, Oct 23, 2018 at 04:43:14PM +0200, Ludwig Seitz wrote:
On 22/10/2018 21:09, Jim Schaad wrote:
* Section 5.8.2 - If the RS is going to do introspection, can it send some
type
On 23/10/2018 20:44, Jim Schaad wrote:
* Section 6 - I am not sure that I agree with the SHOULD NOT in
the last paragraph. Think multicast.
Any suggestions on how to mitigate the issue then? If I issue a
token bound to a symmetric key for audience {R1, R2, R3}, as soon
as R1 got this
On 23/10/2018 21:09, Hannes Tschofenig wrote:
2) 'req_aud' parameter
At the last IETF OAuth meeting in Montreal we agreed to adopt a new
document, called resource indicators, and it can be found here:
https://tools.ietf.org/html/draft-ietf-oauth-resource-indicators-01
I believe the
On 23/10/2018 21:09, Hannes Tschofenig wrote:
Hi all,
I read through draft-ietf-ace-oauth-params-00 and have a few comments.
1) I believe the document should explain in more detail about how it
fits into the rest of the OAuth PoP token work.
Ok I can update the introduction.
The story
