Skip to content

Commit

Permalink
fix
Browse files Browse the repository at this point in the history
  • Loading branch information
waehlisch committed Jun 29, 2024
1 parent b154136 commit 2a07454
Showing 1 changed file with 3 additions and 5 deletions.
8 changes: 3 additions & 5 deletions draft-lenders-core-dnr.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,6 @@ informative:
RFC8323: coap-tcp
RFC8484: doh
RFC8613: oscore
RFC9176: core-rd
RFC9250: doq
RFC9203: ace-oscore
RFC9528: edhoc
Expand Down Expand Up @@ -124,11 +123,10 @@ 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}},
as described in the ACE EDHOC profile {{-ace-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
Expand Down

0 comments on commit 2a07454

Please sign in to comment.