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

close #9: epochs (or, more generally, match boxing) #34

Merged
merged 3 commits into from
Jul 2, 2024
Merged

close #9: epochs (or, more generally, match boxing) #34

merged 3 commits into from
Jul 2, 2024

Conversation

cabo
Copy link
Member

@cabo cabo commented Jun 19, 2024

No description provided.

@chrysn
Copy link
Member

chrysn commented Jun 19, 2024

Next step: More input from people familiar with OSCORE, KUDOS and group OSCORE solicited.

transports {{-coap-tcp}} and OSCORE {{-oscore}} create similar matching
boxes that also do not fit certain likely use cases of these additions
(e.g., with short-lived TCP connections as discussed in {{Section 4.3
of ?RFC9006}}).
Copy link

Choose a reason for hiding this comment

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

Maybe it's also worth to mention RFC 9146 - Connection Identifiers for DTLS 1.2. That keeps the session/epoch and enables to change the ip-address/port, if the matching is relaxed from the ip-endpoints.

Copy link
Member Author

Choose a reason for hiding this comment

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

I have added some text mentioning RFC 9146.

@cabo cabo merged commit 0953e9d into main Jul 2, 2024
2 checks 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.

3 participants