Hi all,

I noticed that both the RFC8152 countersignature header (label 7) and the V2 
countersignature header (label TBD10, draft-ietf-cose-countersign-05) have a 
union type that is either a single (counter)signature or an array of those:

[COSE_Signature] / [+ COSE_Signature]

Since those are not bstr-wrapped and a COSE_Signature is an array itself, I'm 
wondering how an implementation would be able to handle both cases generically 
(without having to explicitly constrain the problem from an upper level) since 
is_array(header_val) would be true in all cases.

Cheers
Maik
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose

Reply via email to