Open nedmsmith opened 3 years ago
Should payload: bstr .cbor unsigned-corim-map in COSE-Sign1-corim us the global code point for unsigned-corim-map?
Why? I don't see any ambiguity that would justify the extra tagging.
Can a parser that only understands 506 take a hand off from a signed-corim parser that can't parse 506 or unsigned-corim?
Can a parser that only understands 506 take a hand off from a signed-corim parser that can't parse 506 or unsigned-corim?
yes, I think so: an hypothetical CoRIMParser goes through unsigned-corim-map and finds out 506 in one of the comid.tags. It starts CoMIDParser feeding it with the decap buffer and waits until the result are ready.
Should payload: bstr .cbor unsigned-corim-map in COSE-Sign1-corim us the global code point for unsigned-corim-map?
E.g., payload: bstr .cbor #6.501(unsigned-corim-map)