Hmm. COSE is defined on the data model level. This new text goes down to
explain how that data model will then be serialized (encoded). We don’t do
this in other places. This might confuse. More so as this is about a byte
string that is encoding another data model (that of a header map). But we are
not talking about that encoding, but about the encoding of the byte string data
item carrying an either empty byte string or an encoded map.
I think we are better off staying at the data model level; we might want to add
something about “which is then in turn encoded as…” if that is clearly
separated from the encoding of the embedded CBOR byte string.
(None of this is “wrong"; this choice is about what might confuse new people
the least, and I’m only guessing here.)
Grüße, Carsten
On 6 August 2016 at 19:29:37, Jim Schaad ([email protected]) wrote:
Does it help if this is re-written as:
Senders SHOULD encode an empty protected map as a zero length binary (encoding
h’40’) rather than as a zero length map wrapped in a binary (encoding h’41a0’).
The zero length binary encoding is preferred because it is both shorter and is
the encoding used in the serialization structures for cryptographic computation.
This fixes my CBOR encoding error as well as presenting both of the encodings
so it is clear what is being discussed.
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
