From f8104e0b98cac0bab2114b006054bf22eef8c62d Mon Sep 17 00:00:00 2001 From: Matthias Waehlisch Date: Sat, 29 Jun 2024 10:45:23 +0200 Subject: [PATCH] fix --- draft-lenders-core-dnr.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-lenders-core-dnr.md b/draft-lenders-core-dnr.md index daf3a68..069a6cc 100644 --- a/draft-lenders-core-dnr.md +++ b/draft-lenders-core-dnr.md @@ -124,11 +124,11 @@ CoAP offers three security modes: addition to transport security. OSCORE keys have a limited lifetime and need to be set up. - Keys can be received from an ACE Authorization Server (AS), as described in the ACE OSCORE profile {{-ace-oscore}}, or, alternatively to support “zero-touch", through an EDHOC key exchange {{-edhoc}}, + Keys can be received from an ACE Authorization Server (AS), as described in the ACE OSCORE profile {{-ace-oscore}}, or, alternatively to support “zero-touch”, through an EDHOC key exchange {{-edhoc}}, as described in the ACE EDHOC profile {{-ace-edhoc}}. -The SVCB-based discovery of a CoAP service in mode “no security" is covered in {{-coap-indication}}, and a CoAP service in the mode “transport security" in {{-coap-dtls-svcb}}. -The discovery of CoAP services in mode "object security" is not specified. +The SVCB-based discovery of a CoAP service in mode “no security” is covered in {{-coap-indication}}, and a CoAP service in the mode “transport security” in {{-coap-dtls-svcb}}. +The discovery of CoAP services in mode “object security” is not specified. To guide future specifications, this document clarifies aspects when using SVCB in the context of CoAP and object security. # Terminology