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

Add note on cachable OSCORE #26

Merged
merged 2 commits into from
Nov 8, 2023
Merged
Changes from all commits
Commits
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
10 changes: 8 additions & 2 deletions draft-ietf-core-dns-over-coap.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ informative:
RFC7942: impl-status-section
I-D.ietf-add-dnr: dnr
I-D.ietf-core-href: cri
I-D.amsuess-core-cachable-oscore: cachable-oscore
DoC-paper: DOI.10.1145/3609423


Expand Down Expand Up @@ -345,8 +346,13 @@ resource record as well.

OSCORE
------
It is RECOMMENDED to carry DNS messages encrypted using OSCORE {{-oscore}} between the DoC client and the DoC server.
The exchange of the security context is out of scope of this document.
It is RECOMMENDED to carry DNS messages encrypted using OSCORE {{-oscore}} between the DoC client
and the DoC server. The establishment and maintenance of the OSCORE Security Context is out of the
scope of this document.

If cache retrieval of OSCORE responses is desired, it can be achieved, for instance, by using the
method defined in {{-cachable-oscore}}. This has, however, implications on message sizes and
security properties, which are compiled in that document.

Mapping DoC to DoH
------------------
Expand Down
Loading