It would be great to see this on the agenda, there's no explicit way to signal deterministic encoding of COSE payloads when they are captured by digest at the moment. For applications where the data is already available in other formats and can be materialised quickly, it would be useful!
Amaury ________________________________ From: Steven Mih <[email protected]> Sent: 29 October 2026 07:03 To: [email protected] <[email protected]> Cc: [email protected] <[email protected]>; Anton Sokolov <[email protected]>; Amaury Chamayou <[email protected]>; Henk Birkholz <[email protected]>; Dick Brooks <[email protected]> Subject: [EXTERNAL] Agenda request for IETF 127: draft-mih-sokolov-cose-deterministic-encodings-00 Mike, Ivo, all, We posted draft-mih-sokolov-cose-deterministic-encodings-00: https://datatracker.ietf.org/doc/draft-mih-sokolov-cose-deterministic-encodings/ A COSE Hash Envelope (RFC 9995) signs the digest of a preimage, so a verifier that holds the value but not the bytes that were hashed has to re-encode it exactly as the producer did. RFC 8949 describes more than one deterministic encoding (Sections 4.2.1 and 4.2.3), and the preimage content type (259) does not say which one was applied. The draft adds a protected-header parameter, deterministic-encodings, that identifies the encoding, and an IANA registry whose first entry is RFC 8949 Core Deterministic Encoding Requirements (core-deterministic). Agenda request for IETF 127: - Presenters: Steven Mih & Anton Sokolov (both in-person) - Topic: Deterministic Encodings for COSE - Draft: draft-mih-sokolov-cose-deterministic-encodings-00 - Time: 10 minutes Comments on the list are welcome before then. Steven Mih
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
