Hi,

It looks like there’s some good stuff in this draft: 
https://www.ietf.org/archive/id/draft-mih-sokolov-cose-deterministic-encodings-00.html
 

I haven’t read it carefully yet, but see that it proposes a new IANA registry 
for CBOR serializations with section 4.2.1 of RFC 8949 as the first entry.

I’m commenting now because I think this overlaps topics with the draft 
serialization in a pretty big way. Maybe we need to pull back the serialization 
draft to address some things in this?

1) A serializations registry is a CBOR WG topic, not a COSE WG topic

2) If there is consensus on a serializations registry, we should pull back the 
serialization draft and put it there

3) The serialization draft does create identifiers for serializations:
3a) They are short strings: “prefp” and “dtrm”
3b) They are targeted at CDDL, but could be used elsewhere
3c) It requires standards action to create a new serialization identifier (and 
by implication a new serialization format)

There’s been comments that the serializations identifier should be a registry. 
At present, we have consensus on the serialization draft without a registry and 
with the requirement for standards action. 
Draft-mih-sokolov-cose-deterministic-encoding is essentially in conflict with 
that.

This is just a comment on the serialization registry part of 
raft-mih-sokolov-cose-deterministic-encoding. Seems like the rest can work 
whether there’s a registry or not as long as there’s an identifier.

There’s some urgency here because of the timing with the serialization draft.

LL



_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to