Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

re issue#20 encourage use of detached payloads for proof formats #28

Merged
merged 2 commits into from
Aug 6, 2024
Merged

re issue#20 encourage use of detached payloads for proof formats #28

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f7726fa
re issue#20 encourage use of detached payloads for proof formats
robinbryce Aug 6, 2024
98957d3
Update draft-ietf-cose-merkle-tree-proofs.md
OR13 Aug 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions draft-ietf-cose-merkle-tree-proofs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,6 +271,7 @@ See {{-certificate-transparency-v2}}, 2.1.1. Definition of the Merkle Tree, for
## Inclusion Proof {#sec-rfc9162-sha256-inclusion-proof}

See {{-certificate-transparency-v2}}, 2.1.3.1. Generating an Inclusion Proof, for a complete description of this verifiable data structure proof type.

The CBOR representation of an inclusion proof for RFC9162_SHA256 is:

~~~~ cddl
Expand All @@ -291,6 +292,7 @@ inclusion-proof = bstr .cbor [
### Receipt of Inclusion

In a signed inclusion proof, the previous merkle tree root, maps to tree-size-1, and is a detached payload.
Specifications are encouraged to make payloads detached when possible, forcing validation-time comparison.
Profiles of proof signatures are encouraged to make additional protected header parameters mandatory, to ensure that claims are processed with their intended semantics.
One way to include this information in the COSE structure is use of the typ (type) Header Parameter, see {{-cose-typ}} and the similar guidance provided in {{-cwt-header-claims}}.
The protected header for an RFC9162_SHA256 inclusion proof signature is:
Expand Down
Loading