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.

Sign up for GitHub

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

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

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c948478
Security considerations: Point into corr-clar-future
chrysn Sep 25, 2024
0df9671
seccons: Simplify
chrysn Sep 26, 2024
30f29a0
seccons: s/address/endpoint/
chrysn Sep 26, 2024
0c41739
seccons: "General CoAP apply" to the top
chrysn Sep 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions draft-ietf-core-dns-over-coap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,15 @@ informative:
I-D.lenders-core-dnr: core-dnr
I-D.amsuess-core-cachable-oscore: cachable-oscore
DoC-paper: DOI.10.1145/3609423

amp-0rtt:
title: 'PR #40 "Amplification and 0-RTT" on "CoAP: Corrections and Clarifications"'
date: 2024-09-25
format:
HTML: https://github.com/core-wg/corrclar/pull/40
ann: |
Note: It is expected that that PR will be merged way ahead of this document's publication;
at the next revision, this reference will be replaced with a reference to what will by then most likely be
I-D.ietf-core-corr-clar-00 (now bormann-core-clar-05).

--- abstract

Expand Down Expand Up @@ -488,6 +496,12 @@ Last update of this information:
Security Considerations
=======================

General CoAP security considerations apply.
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 needs to be done
when those are resumed from a new endpoint.

When using unencrypted CoAP (see {{sec:unencrypted-coap}}), setting the ID of a DNS message to 0 as
specified in {{sec:req-caching}} opens the DNS cache of a DoC client to cache poisoning attacks
via response spoofing.
Expand All @@ -499,7 +513,6 @@ harden against injecting spoofed responses.
Consequently, it is of little concern to leverage the benefits of CoAP caching by setting the ID to
0.


IANA Considerations
===================

Expand Down
Loading