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

Describe how OSCORE works with non-traditional responses #3

Merged
merged 4 commits into from
Mar 2, 2024
Merged

Conversation

chrysn
Copy link
Member

@chrysn chrysn commented Mar 2, 2024

I'm tempted to CC Göran and Marco to this, but in the interest of the timeline I'd hope we can upload this, and once uploaded ask the OSCORE authors for a review.

(which without this generalized rule necessitated a "MUST" statement in the appendix).

[^maybealwaysfirst]: CA: We could also just mandate the "either the first or never" behavior.
I don't know why one would save the efficient response,
Copy link
Member

Choose a reason for hiding this comment

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

What does "save the efficient response" mean here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Clarified: The one where the OSCORE option is empty.

[^maybealwaysfirst]: CA: We could also just mandate the "either the first or never" behavior.
I don't know why one would save the efficient response,
but that may be lack of imagination.
An affine type system can make this doable in a safe way.
Copy link
Member

Choose a reason for hiding this comment

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

What does "affine type system" mean here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Made explicit: Where items are used at most once, and not generally duplicated.

Copy link
Member

Choose a reason for hiding this comment

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

I pushed the scary word into a parentheses.

@cabo cabo merged commit 108949a into master Mar 2, 2024
2 checks passed
@cabo cabo mentioned this pull request Mar 2, 2024
@chrysn chrysn deleted the oscore branch March 19, 2024 15:02
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.

2 participants