Re: [oauth-ext-review] [Ace] Requested review for IANA registration in draft-ietf-ace-oauth-params

[Jim Schaad <[e-mail]>]

I have managed to merge most of my code that deals with the confirmation claim and I have ended up with a single problem when dealing with confirmations.  If this is going to get fixed, it needs to get fixed in draft-ietf-ace-cwt-proof-of-possession prior to this document finishing processing the EDIT process in the RFC editor.

 

All of the items that can appear in a confirmation claim are unique except for the ‘kid’ claim method.  This field is defined as being a text field for JWT (RFC 7800), but it is defined as being a binary field for CWT.  It is a text field when defined in RFC 7800.  I do not anticipate any issues for the definition of a thumbprint as COSE is using a very different format for the definition of thumbprints which will led to a different naming convention.

 

Jim

 

 

 

From: Brian Campbell <[e-mail]> 
Sent: Monday, January 13, 2020 10:01 AM
To: Seitz Ludwig <[e-mail]>
Cc: Ludwig Seitz <[e-mail]>; Roman Danyliw <[e-mail]>; [e-mail]; Daniel Migault <[e-mail]>; Jim Schaad <[e-mail]>; Benjamin Kaduk <[e-mail]>; [e-mail]; [e-mail]
Subject: Re: [Ace] Requested review for IANA registration in draft-ietf-ace-oauth-params

 

Thanks Ludwig,

 

On Sat, Jan 11, 2020 at 8:20 AM Seitz Ludwig <[e-mail] <mailto:[e-mail]> > wrote:

[snip] 

 

From: Ace <[e-mail] <mailto:[e-mail]> > On Behalf Of Brian Campbell

 

[snip]

                   

So in -09 the "cnf" Introspection Response Parameter was the following the syntax of the "cnf" claim from PoP Key Semantics for CWTs [ID.ietf-ace-cwt-proof-of-possession] and in -10 it's following the syntax of PoP Key Semantics for JWTs [RFC7800] transitively via [I-D.ietf-oauth-mtls] reference. I think I understand that the two PoP key semantics documents are conceptually the same or similar. But I don't know that the syntax is the same? Figure 5 <https://tools.ietf.org/html/draft-ietf-ace-oauth-params-10#section-6>  is pointed to for mapping between CBOR and JSON but it only has mappings for the main top level parameters. Maybe I just don't get it or am missing something...   

 

[LS] No you are not missing something, I just got sloppy trying to do a quickfix.

 

Background: The reason for defining both JSON and CBOR-based interactions is that you might have a powerful client communicating with a constrained RS. The client does vanilla OAuth interactions with the AS via the token endpoint, but is served a CWT and associated ACE parameters (cnf, ace-profile, …) for interaction with the RS. 

The pop-key should decode to the same binary representation regardless of whether it came in a JSON or CBOR wrapper.

 

Okay, so noting that there is cnf content that doesn't decode to a key, I suppose I'll just take it on faith that all the relevant or expected usages involve a key that can be represented in both CBOR and JSON. 


CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.