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

Privacy Considerations: Editorial Improvements #286

Merged
merged 17 commits into from
Sep 3, 2024

Conversation

hannestschofenig
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@roywill roywill left a comment

Choose a reason for hiding this comment

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

See comment above.

This does not make the comment any less useful, I would rather keep this.

Co-authored-by: Steve Lasker <[email protected]>
Copy link
Collaborator

@OR13 OR13 left a comment

Choose a reason for hiding this comment

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

Lets not assert properties of verifiable data structures beyond append only and inclusion proofs

Copy link
Member

@henkbirkholz henkbirkholz left a comment

Choose a reason for hiding this comment

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

Orie's suggestion makes sense

Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>

Co-authored-by: Orie Steele <[email protected]>
henkbirkholz and others added 3 commits July 22, 2024 01:25
Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>

Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>

Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>

Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>

Co-authored-by: Orie Steele <[email protected]>
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.

Suggestion to leave this section and close.

draft-ietf-scitt-architecture.md Outdated Show resolved Hide resolved
Co-authored-by: Henk Birkholz <[email protected]>
Co-authored-by: Hannes Tschofenig <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>
Co-authored-by: Hannes Tschofenig <[email protected]>
Copy link
Collaborator

@OR13 OR13 left a comment

Choose a reason for hiding this comment

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

Lets merge #294 first, and then address conflicts and see if anything remains

Copy link
Collaborator

@aj-stein-nist aj-stein-nist left a comment

Choose a reason for hiding this comment

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

I see this change as constructive, I asked Steve for clarification on his comments too.

this is okay, but maybe other parts in the pr will keep it from being merged

Co-authored-by: Hannes Tschofenig <[email protected]>
Copy link
Collaborator

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

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

Suggest we incorporate Option 1 suggestion from Steve!

@SteveLasker
Copy link
Collaborator

@OR13, @henkbirkholz, PTAL at the latest if they resolve your requested changes.

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.

Changes as of cdd13a4 improve the previous text.
LGTM

Transparency Services MAY support anonymous access.
Issuers SHOULD ensure Signed Statements submitted to public access services are acceptable for public disclosure.
In this case, Signed Statements MUST NOT carry confidential information.
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is a strange way to say that Log integrity is tamper protected.

Transparency Services MAY support anonymous access.
Issuers SHOULD ensure Signed Statements submitted to public access services are acceptable for public disclosure.
Publicly accessible Signed Statements MUST NOT carry confidential information.
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log.
Copy link
Member

@henkbirkholz henkbirkholz Sep 3, 2024

Choose a reason for hiding this comment

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

Suggested change
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log.
Once a Signed Statement is registered it cannot be removed from the Log.

Optional brevity

@SteveLasker SteveLasker merged commit c7982b6 into main Sep 3, 2024
2 checks passed
@SteveLasker SteveLasker deleted the hannestschofenig-patch-19 branch October 15, 2024 16:04
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.

8 participants