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

Define Non-equivocation #131

Merged
merged 3 commits into from
Dec 5, 2023

Conversation

aj-stein-nist
Copy link
Collaborator

Define equivocation and non-equivocation and cite the article that coined the term in analyzing Lamport. Closes #116.

SteveLasker
SteveLasker previously approved these changes Nov 27, 2023
Copy link
Collaborator

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

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

Some updated clarfiication and suggestions.

draft-ietf-scitt-architecture.md Outdated Show resolved Hide resolved
draft-ietf-scitt-architecture.md Show resolved Hide resolved
draft-ietf-scitt-architecture.md Outdated Show resolved Hide resolved
@SteveLasker SteveLasker self-requested a review November 27, 2023 23:28
draft-ietf-scitt-architecture.md Show resolved Hide resolved
draft-ietf-scitt-architecture.md Outdated Show resolved Hide resolved
@robinbryce
Copy link
Collaborator

I think this reference from the CT rfc is useful.

https://datatracker.ietf.org/doc/html/rfc6962#section-7.3

"and (2) by
violating its append-only property by presenting two different,
conflicting views of the Merkle Tree at different times and/or to
different parties."

this is equivocation. If we replace "Merkle Tree" with "collection of statements".

And that reference is also careful to cast things interms of detectability rather than prevention

@aj-stein-nist
Copy link
Collaborator Author

I think this reference from the CT rfc is useful.

https://datatracker.ietf.org/doc/html/rfc6962#section-7.3

This is very useful, thanks. I will adjust with this and your other feedback, most appreciated!

@SteveLasker SteveLasker dismissed their stale review November 29, 2023 04:51

updated PR feedback

Copy link
Collaborator

@robinbryce robinbryce left a comment

Choose a reason for hiding this comment

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

I like those changes. Reads clean to me thanks

draft-ietf-scitt-architecture.md Show resolved Hide resolved
Copy link
Collaborator

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

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

LGTM
Thanks, @aj-stein-nist for the iterations. This was a tricky one to summarize an entire paper in a few sentences

@aj-stein-nist
Copy link
Collaborator Author

LGTM Thanks, @aj-stein-nist for the iterations. This was a tricky one to summarize an entire paper in a few sentences

Who reads papers anyway? Jokes aside, thanks for the contributions and making me think about how to communicate clearly on this one.

@SteveLasker SteveLasker merged commit cd61a58 into ietf-wg-scitt:main Dec 5, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add non-equivocation to terminology
4 participants