If you ever get tired of having to dress your precious objects in base64Url/bstr, or having to dig out the type of an object in JWT/CWT headers [*], the following may be worth a look.
In particular https://www.ietf.org/archive/id/draft-rundgren-universal-cbor-03.html#name-enveloped-signatures The 03 version represents a major release. Enjoy! Anders *] All objects aren't necessarily signed, making this method very specific. -------- Forwarded Message -------- Subject: New Version Notification for draft-rundgren-universal-cbor-03.txt Date: Sun, 16 Mar 2025 01:14:01 -0700 From: [email protected] To: Anders Rundgren <[email protected]> A new version of Internet-Draft draft-rundgren-universal-cbor-03.txt has been successfully submitted by Anders Rundgren and posted to the IETF repository. Name: draft-rundgren-universal-cbor Revision: 03 Title: Universal CBOR (U-CBOR) Date: 2025-03-16 Group: Individual Submission Pages: 28 URL: https://www.ietf.org/archive/id/draft-rundgren-universal-cbor-03.txt Status: https://datatracker.ietf.org/doc/draft-rundgren-universal-cbor/ HTML: https://www.ietf.org/archive/id/draft-rundgren-universal-cbor-03.html HTMLized: https://datatracker.ietf.org/doc/html/draft-rundgren-universal-cbor Diff: https://author-tools.ietf.org/iddiff?url2=draft-rundgren-universal-cbor-03 Abstract: This document defines Universal CBOR (U-CBOR), a strict subset of CBOR (RFC 8949) intended to serve as a viable replacement for JSON in computationally advanced systems like Internet browsers, mobile phones, and Web servers. To foster interoperability, deterministic encoding is mandated. Furthermore, the document outlines how deterministic encoding combined with enhanced CBOR tools, enable cryptographic methods like signing and hashing, to optionally use "raw" (non-wrapped) CBOR data as input. This document mainly targets CBOR tool developers. The IETF Secretariat _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
