You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest set of changes have removed the serialized leaf from the RFC9162-log inclusion proof. This is problematic for SCITT because the expectation was that verification of a COSE signed Merkle Proof would be self-contained (the CCF ledger ID is forced to make the serialization explicit because the leaf carries additional metadata).
Generally, I would argue that a proof type is only well defined if all inputs required for proof verification are carried in the COMETRE CBOR definition of the proof value. Otherwise, the question of the serialization of these additional inputs becomes ambiguous and you may end up with a mix of CBOR and other formats. Furthermore, it is difficult for implementations of validation libraries to define the API if they have to consider additional inputs for some verifiable data structures or some proof types.
The text was updated successfully, but these errors were encountered:
OR13
transferred this issue from ietf-scitt/draft-steele-cose-merkle-tree-proofs
Sep 6, 2023
The latest set of changes have removed the serialized leaf from the RFC9162-log inclusion proof. This is problematic for SCITT because the expectation was that verification of a COSE signed Merkle Proof would be self-contained (the CCF ledger ID is forced to make the serialization explicit because the leaf carries additional metadata).
Generally, I would argue that a proof type is only well defined if all inputs required for proof verification are carried in the COMETRE CBOR definition of the proof value. Otherwise, the question of the serialization of these additional inputs becomes ambiguous and you may end up with a mix of CBOR and other formats. Furthermore, it is difficult for implementations of validation libraries to define the API if they have to consider additional inputs for some verifiable data structures or some proof types.
The text was updated successfully, but these errors were encountered: