From reviewing comments from Thomas, I noticed UCCS is missing some parts.
The UCCS draft doesn’t define the CDDL for the $EAT-CBOR-Tagged-Token,
$JSON-Selector-Type and $JSON-Selector-Value sockets for inclusion of a UCCS in
EAT.
The EAT document goes as far as it can to set up for UCCS, but can’t go all the
way without normative reference. It leaves it up to the definer of other token
formats (which UCCS is) to define how they plug into EAT as a nested token and
into a detached EAT bundle.
This is primarily an issue for JSON-encoded EATs as CBOR-encoded EATs use the
CBOR tag mechanism. JSON doesn’t haven an equivalent.
What’s needed is something like this:
$JSON-Selector-Type /= “UCCS"
$JSON-Selector-Value /= UCCS
$EAT-CBOR-Tagged-Token = UCCS
But, there’s a further problem.
The UCCS draft defines:
UCCS = #6.601(Claims-Set)
It should be:
UCCS = UCCS-Tagged / UCCS-UnTagged
UCCS-Tagged = #6.601(Claims-Set)
UCCS-UnTagged = Claims-Set
Then the CDDL to connect up to EAT is:
$JSON-Selector-Type /= “UCCS"
$JSON-Selector-Value /= UCCS-UnTagged
$EAT-CBOR-Tagged-Token = UCCS-Tagged
This also makes the UCCS reference to EAT normative, but that is OK since EAT
is ahead of UCCS.
I believe this very much needs to be fixed.
LL
> On Aug 26, 2023, at 4:43 AM, Kathleen Moriarty
> <[email protected]> wrote:
>
> Greetings!
>
> The working group last call for
> https://datatracker.ietf.org/doc/draft-ietf-rats-uccs/
> begins now and will run for 4 weeks per discussion at the IETF 117 meeting.
> Review requests are also requested from COSE working group members. Last call
> ends 9/23/2023.
>
> There are a few remaining questions that I need assistance from authors on
> prior to IETF last call. Could each author and others with knowledge of IPR
> please disclose any at this time as well.
>
> Thank you!
>
> --
>
> Best regards,
> Kathleen
> _______________________________________________
> RATS mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/rats
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
