Hi all,
I do not believe there is a need to reference draft-ietf-cbor-cde or
Section 4.2.3 of RFC 8949 since the relevant key-related parameters are
not expressed via floating point data types.
Ciao
Hannes
Am 07.07.2024 um 13:17 schrieb Anders Rundgren:
Carsten, I stand corrected. Sometimes the sheer size of RFC 8949 puts
me on the wrong track :(
Referring to draft-ietf-cbor-cde seems like an excellent idea.
Cheers,
Anders
On 2024-07-07 08:40, Carsten Bormann wrote:
On 7. Jul 2024, at 06:21, Anders Rundgren
<[email protected]> wrote:
- Referring to 4.2.1 is insufficient, you need 4.2.3 as well.
Related: https://datatracker.ietf.org/doc/draft-ietf-cbor-cde/
Section 4.2.3 of RFC 8949 describes a legacy format that should not
be used for new protocols.
Section 4.2.1 is the one we want to reference here.
If the structures can contain floating point values (e.g., via a new
registry entry), some of 4.2.2 may be needed.
(If deterministic serialization for general data structures is needed
it would be best to normatively reference draft-ietf-cbor-cde. Do
not restate or second-guess.)
Grüße, Carsten
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
