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.

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

Receipts #276

Closed
hannestschofenig opened this issue Jul 20, 2024 · 6 comments · Fixed by #308
Closed

Receipts #276

hannestschofenig opened this issue Jul 20, 2024 · 6 comments · Fixed by #308
Assignees
Labels
pending-close Pending closure with no recent activity ready-for-pr

Comments

@hannestschofenig
Copy link
Collaborator

When the draft talks about receipts does it refers only to inclusion proofs. Can we still talk about receipts, if other proof types are supported by an implementation that those are still called Receipts?

@robinbryce
Copy link
Collaborator

I think it is meant to refer to this: https://datatracker.ietf.org/doc/draft-ietf-cose-merkle-tree-proofs/ at least as an example. And this defines receipts of inclusion and receipts of consistency

@SteveLasker
Copy link
Collaborator

Can we get a suggestion or PR for next steps?

@SteveLasker SteveLasker added ready-for-pr pending-close Pending closure with no recent activity labels Oct 1, 2024
@robinbryce
Copy link
Collaborator

I'm inclined to reduce the entry in Definitions to just the head line from "Definition of transparency" which says just - "Receipts demonstrate inclusion of Signed Statements in the Append-only Log of a Transparency Service". The particulars of how "inclusion is demonstrated" is very log specific. I'll put together a small diff and see how that looks

@robinbryce
Copy link
Collaborator

ah also, quite far down, where the draft describes "append only", it does introduce

"In addition to Receipts, some verifiable data structures might support additional proof types, such as proofs of consistency, or proofs of non inclusion"

I think a small amount of fore shadowing or re-arangement will do the trick

@SteveLasker
Copy link
Collaborator

Thanks, @robinbryce
A PR would be great to review to formalize the discussion

@robinbryce
Copy link
Collaborator

PR added, but I think it warants some discussion regarding possible tension with the hard requirement for COSE-Receipts

robinbryce pushed a commit to robinbryce/draft-ietf-scitt-architecture that referenced this issue Oct 15, 2024
1. align Receipt definition with definition of transparency
2. Explicitly acknowlege other signed proof types, but make it clear
   they are "not receipts", per the issue ietf-wg-scitt#276 's query
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-close Pending closure with no recent activity ready-for-pr
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants