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

Update the definition of Receipts #308

Merged
merged 4 commits into from
Oct 15, 2024
Merged

Update the definition of Receipts #308

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5988859
Update the definition of Receipts
Oct 15, 2024
ad998d2
respond to review feedback by reducing the change to
Oct 15, 2024
b9382f3
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 15, 2024
ae24c9b
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 15, 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
5 changes: 2 additions & 3 deletions draft-ietf-scitt-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,9 +228,8 @@ Over time, an Issuer may register new Signed Statements about an Artifact in a T
Receipt:

: a cryptographic proof that a Signed Statement is included in the Append-only Log.
Receipts are based on Signed Inclusion Proofs, such as those as described in COSE Signed Merkle Tree Proofs {{-COMETRE}};
they can be built on different verifiable data structures, not just binary merkle trees.
A Receipt consists of a Transparency Service-specific inclusion proof for the Signed Statement, a signature by the Transparency Service of the state of the Append-only Log after the inclusion, and additional metadata (contained in the signature's protected headers) to assist in auditing.
Receipts are signed proofs of verifiable data-structure properties.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By removing the reference to the draft-ietf-cose-merkle-tree definition of receipti, are we separating the definition in SCITT as unique? If so, for what purpose?

The types of Receipts MUST support inclusion proofs and MAY support other proof types, such as consistency proofs.

Registration:

Expand Down
Loading