https://datatracker.ietf.org/doc/pdf/draft-ietf-cbor-cddl-control-07
Sent from mobile, sorry for terse
> On 18. Jul 2023, at 17:38, Michael Richardson <mcr+i...@sandelman.ca> wrote:
>
>
> In the JWS I-D, we have some JSON that is an example.
> And the content within is BASE64URL encoded.
> We could, I think, describe this in CDDL, but we aren't trying to be
> authoritative. (It's a JOSE example)
>
> We are struggling with quoting. We could write:
>
> "payload": "BASE64URL(ietf-voucher:voucher)",
>
> which would make it valid JSON, with the literal contents.
> Or we could write:
>
> "payload": BASE64URL(ietf-voucher:voucher),
>
> which sorta makes it valid Javascript, assuming such a function existed.
>
>
> here is an example with both variations:
>
> {
> "payload": BASE64URL(ietf-voucher:voucher),
> "signatures": [
> {
> "protected": "BASE64URL(UTF8(JWS Protected Header))",
> "signature": "base64encodedvalue=="
> }
> ]
> }
>
>
>
> --
> Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
> Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
