Hello, There are 2 PRs open on this new adopted work item:
https://github.com/cose-wg/draft-ietf-cose-merkle-tree-proofs They address some migration details, and editors notes... But there is one more substantial change proposed: The goal is to allow multiple "proof values" for a given "proof type", here is a concrete example: Let's say you have a signed merkle tree root as described in RFC9162. And you want to prove that both "foo" and "bar" are included. Previously, you would have had to make 2 cose sign1 envelopes, and include a single inclusion proof in the unprotected header of each. After https://github.com/cose-wg/draft-ietf-cose-merkle-tree-proofs/pull/6 You will be able to use a single envelope with 2 inclusion proofs in the unprotected header. This requires adjusting the "value side" of "inclusion proof tag" to allow bstr or list / array of bstr. It seems like there are lots of cases where you want a single object to convey inclusion for several other objects, but there are multiple ways to accomplish this. Is this type change a good idea to make? Regards, OS -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
