From 4984d6badb7f4ea1fc76cc3a7e0f6832f3a5a439 Mon Sep 17 00:00:00 2001 From: Martine Lenders Date: Wed, 8 Nov 2023 08:27:32 +0100 Subject: [PATCH] Address Marco's feedback --- draft-ietf-core-dns-over-coap.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/draft-ietf-core-dns-over-coap.md b/draft-ietf-core-dns-over-coap.md index c1422c2..ce2bc71 100644 --- a/draft-ietf-core-dns-over-coap.md +++ b/draft-ietf-core-dns-over-coap.md @@ -346,11 +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, consider following the guidances described in {{-cachable-oscore}}. -These have, however, implications on message sizes and security, which you will find in that 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 ------------------