Make authentication stance consistent in the document #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Proposed resolution for ietf-wg-scitt#14 and ietf-wg-scitt#46, as discussed with @SteveLasker, @OR13 and @henkbirkholz.
OR13
approved these changes
Dec 4, 2024
|
@OR13 to your point about interoperability, the document is normative to a limited extent about authentication where present. |
|
If we have a lot of "MAY be authenticated" we can consolidate it into a single paragraph, and improve the reading experience for each resource. |
That's what this PR does, I believe, but happy to fix anything I have missed. |
SteveLasker
reviewed
Dec 4, 2024
SteveLasker
approved these changes
Dec 4, 2024
achamayou
added a commit
to achamayou/draft-ietf-scitt-scrapi
that referenced
this pull request
Dec 6, 2024
An 'Issue Statement' endpoint is not necessary, nor helpful to implement a transparency service, and it is unclear why it has been added as an optional endpoint. SCITT services should be able to compose with arbitrary signing services that produce signed statements in the correct format. Aside from separating concerns and making the document more concise, this helps make the authentication posture consistent (see ietf-wg-scitt#52).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed resolution for #14 and #46, as discussed with @SteveLasker, @OR13 and @henkbirkholz.
Will PR the removal of issue statement (the sole endpoint demanding authentication) separately.