From 5361e4f5e7fb4431301e7072aefeec1082e33bd0 Mon Sep 17 00:00:00 2001 From: crimson Date: Sun, 8 Oct 2023 17:05:18 +0200 Subject: [PATCH] Editorial --- draft-ietf-core-groupcomm-bis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-core-groupcomm-bis.md b/draft-ietf-core-groupcomm-bis.md index cf577b7..ba9119d 100644 --- a/draft-ietf-core-groupcomm-bis.md +++ b/draft-ietf-core-groupcomm-bis.md @@ -922,7 +922,7 @@ Group OSCORE provides end-to-end application-level security. This has many desir CoAP group communication MUST be protected by using Group OSCORE as specified in {{I-D.ietf-core-oscore-groupcomm}}, with the possible exception of: applications that are proven to be neither sensitive nor critical; and specific, well-defined steps where security is not viable or is intrinsically unattainable (e.g., early discovery). -The same security considerations from {{Section 11 of I-D.ietf-core-oscore-groupcomm}} hold for this specification. +The same security considerations from {{Section 13 of I-D.ietf-core-oscore-groupcomm}} hold for this specification. ### Group Key Management ### {#chap-security-considerations-sec-mode-key-mgmt}