Re: [Cbor] Reviews and shepherd for draft-ietf-cbor-cddl-more-control

["lgl island-resort.com" <[e-mail]>]

On Apr 11, 2024, at 6:27 AM, Carsten Bormann <[e-mail]> wrote:

It would be nice if the cddl tool had a —version option so you could know easily what you have and put version dependency in document validation scripts. I wasn’t planning on updating the CDDL in the to-be-published EAT because you can’t error out saying “you need a new version of the cddl tool”.

I added a version number to the usage message in 0.11.3.

Thx!


I've done some work on this, mostly putting .b64u to work. Much is good and makes the CDDL neater and validation more thorough. The interesting one is validating https://github.com/ietf-rats-wg/eat/blob/master/cddl/Example-Tokens/deb.json

Ah, this is about describing the JWT by dividing it into its three parts, essentially a “split”-like usage of “.join”…

Hmm.


b64u should work on text strings, not just on byte strings.

Well, it accepts a text string as the target (left hand side), and a byte string as its controller (right hand side).
Do you have an example where you need something different?

The use case is JWT and EAT. JSON data that they sign is b64 wrapped for protection in transit.

In EAT, it’s a Claims-Set that is wrapped so it is desired that the validation descend into the Claims-Set. The Claims-Set wrapping is part of the detached claims sets and detached eat bundles.



(In a pinch, .cat can be used as a conversion operator between text and byte strings, but I’m not sure the tool is very smart about that.)

Not sure how to use .cat here. I tried a little, but couldn't’ get it to work.

LL