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

Security considerations: Point into corr-clar-future #31

Merged
merged 4 commits into from
Sep 26, 2024
Merged

Conversation

chrysn
Copy link
Member

@chrysn chrysn commented Sep 25, 2024

As per today's interim, this is all that's between this document and a WGLC.

By the time we're working in the WGLC comments, we can update the reference that now points into a PR to point to corr-clar.

draft-ietf-core-dns-over-coap.md Outdated Show resolved Hide resolved
draft-ietf-core-dns-over-coap.md Outdated Show resolved Hide resolved
Exceeding those in {{Section 11 of RFC7252}},
the request patterns of DoC make it likely that long-lived security contexts are maintained:
{{amp-0rtt}} goes into more detail on what can and needs to be done
when those are resumed from a new address.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
when those are resumed from a new address.
when those are resumed from a new source address or port.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe 'new endpoint' – source-address-and-port is a UDP/TCP thing. Thinking of OSCORE, you're also in a "new endpoint" situation if after requests over TCP from an address/port combination, all of a sudden the requests come from the same UDP address/port. (One might argue that it's very likely that this is return routable if TCP was, the same argument can also be made for same-IP-different-port, and then we'd have to think about NAT, and I don't want to think about NAT).

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated to "new endpoint" – that fine?

chrysn added a commit that referenced this pull request Sep 26, 2024
draft-ietf-core-dns-over-coap.md Outdated Show resolved Hide resolved
draft-ietf-core-dns-over-coap.md Outdated Show resolved Hide resolved
@miri64 miri64 merged commit be87b7e into main Sep 26, 2024
2 checks passed
@chrysn chrysn deleted the interim-seccons branch September 26, 2024 09:47
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