From 93ede0941e0be18fb45b13af3897ebd73f68433e Mon Sep 17 00:00:00 2001 From: crimson Date: Sun, 28 Jul 2024 12:42:19 +0200 Subject: [PATCH] Added IANA consideration on the "CoAP Option Numbers" registry. --- draft-ietf-core-oscore-groupcomm.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/draft-ietf-core-oscore-groupcomm.md b/draft-ietf-core-oscore-groupcomm.md index 43a32cd..730f04e 100644 --- a/draft-ietf-core-oscore-groupcomm.md +++ b/draft-ietf-core-oscore-groupcomm.md @@ -1881,6 +1881,10 @@ IANA is asked to add the following entry to the "OSCORE Flag Bits" registry with | 2 | Group Flag | For using a Group OSCORE Security Context, set to 1 if the message is protected with the group mode | {{&SELF}} | {: #table-iana-oscore-flag-bits title="Registrations in the OSCORE Flag Bits Registry" align="center"} +## CoAP Option Numbers Registry {#iana-cons-oscore-option-numbers} + +IANA is asked to add this document as a reference for the OSCORE Option in the "CoAP Option Numbers" registry within the "Constrained RESTful Environments (CoRE) Parameters" registry group. + ## Target Attributes Registry ## {#iana-target-attributes} IANA is asked to add the following entry to the "Target Attributes" registry within the "Constrained RESTful Environments (CoRE) Parameters" registry group. @@ -1978,6 +1982,8 @@ As discussed in {{ssec-gid-collision}}, if endpoints are deployed in multiple gr ## Version -21 to -22 ## {#sec-21-22} +* Added IANA consideration on the "CoAP Option Numbers" registry. + * Updated references. * Editorial improvements.