From ebded85e05905495532ec60031c4a7706a760957 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Mon, 14 Oct 2024 16:25:53 +0000
Subject: [PATCH] Script updating gh-pages from 21df35a. [ci skip]

---
 ...lar.html => draft-ietf-core-corr-clar.html | 40 ++++----
 ...-clar.txt => draft-ietf-core-corr-clar.txt | 98 +++++++++----------
 index.html                                    | 10 +-
 3 files changed, 74 insertions(+), 74 deletions(-)
 rename draft-bormann-core-corr-clar.html => draft-ietf-core-corr-clar.html (98%)
 rename draft-bormann-core-corr-clar.txt => draft-ietf-core-corr-clar.txt (93%)

diff --git a/draft-bormann-core-corr-clar.html b/draft-ietf-core-corr-clar.html
similarity index 98%
rename from draft-bormann-core-corr-clar.html
rename to draft-ietf-core-corr-clar.html
index 139ff9a..ab580c0 100644
--- a/draft-bormann-core-corr-clar.html
+++ b/draft-ietf-core-corr-clar.html
@@ -21,11 +21,11 @@
 In addition, other clarifications related to the use of CoAP in other
 specifications, including RFC 7390 and RFC 8075, are also provided. 
     " name="description">
-<meta content="xml2rfc 3.23.1" name="generator">
-<meta content="draft-bormann-core-corr-clar-latest" name="ietf.draft">
+<meta content="xml2rfc 3.23.2" name="generator">
+<meta content="draft-ietf-core-corr-clar-latest" name="ietf.draft">
 <!-- Generator version information:
-  xml2rfc 3.23.1
-    Python 3.12.6
+  xml2rfc 3.23.2
+    Python 3.12.7
     ConfigArgParse 1.7
     google-i18n-address 3.1.1
     intervaltree 3.1.0
@@ -38,7 +38,7 @@
     setuptools 70.3.0
     wcwidth 0.2.13
 -->
-<link href="draft-bormann-core-corr-clar.xml" rel="alternate" type="application/rfc+xml">
+<link href="draft-ietf-core-corr-clar.xml" rel="alternate" type="application/rfc+xml">
 <link href="#copyright" rel="license">
 <style type="text/css">@font-face {
   font-family: 'Lora';
@@ -1035,11 +1035,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">Corrections and Clarifications to CoAP</td>
-<td class="right">September 2024</td>
+<td class="right">October 2024</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">Bormann</td>
-<td class="center">Expires 28 March 2025</td>
+<td class="center">Expires 17 April 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1049,18 +1049,18 @@
 <dt class="label-workgroup">Workgroup:</dt>
 <dd class="workgroup">Network Working Group</dd>
 <dt class="label-internet-draft">Internet-Draft:</dt>
-<dd class="internet-draft">draft-bormann-core-corr-clar-latest</dd>
+<dd class="internet-draft">draft-ietf-core-corr-clar-latest</dd>
 <dt class="label-updates">Updates:</dt>
 <dd class="updates">
 <a href="https://www.rfc-editor.org/rfc/rfc6690" class="eref">6690</a>, <a href="https://www.rfc-editor.org/rfc/rfc7252" class="eref">7252</a>, <a href="https://www.rfc-editor.org/rfc/rfc7641" class="eref">7641</a>, <a href="https://www.rfc-editor.org/rfc/rfc7959" class="eref">7959</a>, <a href="https://www.rfc-editor.org/rfc/rfc8132" class="eref">8132</a>, <a href="https://www.rfc-editor.org/rfc/rfc8323" class="eref">8323</a> (if approved)</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-09-24" class="published">24 September 2024</time>
+<time datetime="2024-10-14" class="published">14 October 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-03-28">28 March 2025</time></dd>
+<dd class="expires"><time datetime="2025-04-17">17 April 2025</time></dd>
 <dt class="label-authors">Author:</dt>
 <dd class="authors">
 <div class="author">
@@ -1093,7 +1093,7 @@ <h2 id="name-about-this-document">
       </h2>
 <p id="section-note.1-1">This note is to be removed before publishing as an RFC.<a href="#section-note.1-1" class="pilcrow">¶</a></p>
 <p id="section-note.1-2">
-        Status information for this document may be found at <span><a href="https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/">https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/</a></span>.<a href="#section-note.1-2" class="pilcrow">¶</a></p>
+        Status information for this document may be found at <span><a href="https://datatracker.ietf.org/doc/draft-ietf-core-corr-clar/">https://datatracker.ietf.org/doc/draft-ietf-core-corr-clar/</a></span>.<a href="#section-note.1-2" class="pilcrow">¶</a></p>
 <p id="section-note.1-3">
         Discussion of this document takes place on the
         core Working Group mailing list (<span><a href="mailto:core@ietf.org">mailto:core@ietf.org</a></span>),
@@ -1121,7 +1121,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 28 March 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 17 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1486,7 +1486,7 @@ <h3 id="name-rfc7252-64-decomposing-uris">
 <span><a href="https://rfc-editor.org/rfc/rfc7252#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>.
 A slightly updated version of the proposed note might be:<a href="#section-2.3-3" class="pilcrow">¶</a></p>
 <span class="break"></span><dl class="dlNewline" id="section-2.3-4">
-          <dt id="section-2.3-4.1">INCOMPLETE; FORMAL ADDITION at the end of <span><a href="https://rfc-editor.org/rfc/rfc7252#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>:</dt>
+          <dt id="section-2.3-4.1">FORMAL ADDITION at the end of <span><a href="https://rfc-editor.org/rfc/rfc7252#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>:</dt>
           <dd style="margin-left: 1.5em" id="section-2.3-4.2">
             <p id="section-2.3-4.2.1">Also note that a trailing slash character in the &lt;path&gt; component
 represents a separate, zero-character path segment (see the ABNF in
@@ -1612,7 +1612,7 @@ <h4 id="name-oscore-kudos-and-group-osco">
           </h4>
 <p id="section-2.5.2-1">The security protocol Object Security for Constrained RESTful Environments (OSCORE) defined in <span>[<a href="#RFC8613" class="cite xref">RFC8613</a>]</span> provides end-to-end security for CoAP messages at the application level, by using CBOR Object Signing and Encryption (COSE) <span>[<a href="#RFC9052" class="cite xref">RFC9052</a>]</span>. In order to protect their communications, two peers need to have already established an OSCORE Security Context.<a href="#section-2.5.2-1" class="pilcrow">¶</a></p>
 <p id="section-2.5.2-2"><span><a href="https://rfc-editor.org/rfc/rfc8613#appendix-B.2" class="relref">Appendix B.2</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span> provides an example for a key update procedure, which two OSCORE peers can run for establishing a new shared OSCORE Security Context that replaces their old one. The recent key update protocol KUDOS <span>[<a href="#I-D.ietf-core-oscore-key-update" class="cite xref">I-D.ietf-core-oscore-key-update</a>]</span> specifies how two OSCORE peers can establish a new shared OSCORE Security Context that replaces their old one, with a number of advantages compared to the method defined in <span><a href="https://rfc-editor.org/rfc/rfc8613#appendix-B.2" class="relref">Appendix B.2</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span>.<a href="#section-2.5.2-2" class="pilcrow">¶</a></p>
-<p id="section-2.5.2-3">The security protocol Group Object Security for Constrained RESTful Environments (Group OSCORE) defined in <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span> builds on OSCORE and protects group communication for CoAP <span>[<a href="#I-D.ietf-core-groupcomm-bis" class="cite xref">I-D.ietf-core-groupcomm-bis</a>]</span>. The management of the group keying material is entrusted to a Group Manager (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-3" class="relref">Section 3</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>), which provides the latest group keying material to a new group member upon its group joining, and can update the group keying material by performing a group rekeying.<a href="#section-2.5.2-3" class="pilcrow">¶</a></p>
+<p id="section-2.5.2-3">The security protocol Group Object Security for Constrained RESTful Environments (Group OSCORE) defined in <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span> builds on OSCORE and protects group communication for CoAP <span>[<a href="#I-D.ietf-core-groupcomm-bis" class="cite xref">I-D.ietf-core-groupcomm-bis</a>]</span>. The management of the group keying material is entrusted to a Group Manager (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-3" class="relref">Section 3</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>), which provides the latest group keying material to a new group member upon its group joining, and can update the group keying material by performing a group rekeying.<a href="#section-2.5.2-3" class="pilcrow">¶</a></p>
 <p id="section-2.5.2-4">The following discusses how OSCORE, KUDOS, and Group OSCORE position themselves with respect to the match boxing, the transport used underlying CoAP, and the renewal of the keying material.<a href="#section-2.5.2-4" class="pilcrow">¶</a></p>
 <div id="match-boxing">
 <section id="section-2.5.2.1">
@@ -1628,8 +1628,8 @@ <h5 id="name-match-boxing">
 (Master Secret, Master Salt, ID Context, Sender ID) must be unique. As
 per <span><a href="https://rfc-editor.org/rfc/rfc8613#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span>, this is a hard requirement and
 guarantees unique (key, nonce) pairs for the AEAD algorithm used.<a href="#section-2.5.2.1-4" class="pilcrow">¶</a></p>
-<p id="section-2.5.2.1-5">In Group OSCORE, the Security Context extends that of OSCORE, and the same as above holds  (see Sections <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-2" class="relref">2</a>, <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-2.2" class="relref">2.2</a>, and <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-13.11" class="relref">13.11</a> of <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.1-5" class="pilcrow">¶</a></p>
-<p id="section-2.5.2.1-6">Finally, (Group) OSCORE performs a separate secure match boxing under its own control, by cryptographically binding each protected request with all the corresponding protected responses. This is achieved by means of the COSE external_aad involved during the security processing of protected messages (see <span><a href="https://rfc-editor.org/rfc/rfc8613#section-5.4" class="relref">Section 5.4</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span> and <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-4.4" class="relref">Section 4.4</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.1-6" class="pilcrow">¶</a></p>
+<p id="section-2.5.2.1-5">In Group OSCORE, the Security Context extends that of OSCORE, and the same as above holds  (see Sections <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-2" class="relref">2</a>, <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-2.2" class="relref">2.2</a>, and <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-13.11" class="relref">13.11</a> of <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.1-5" class="pilcrow">¶</a></p>
+<p id="section-2.5.2.1-6">Finally, (Group) OSCORE performs a separate secure match boxing under its own control, by cryptographically binding each protected request with all the corresponding protected responses. This is achieved by means of the COSE external_aad involved during the security processing of protected messages (see <span><a href="https://rfc-editor.org/rfc/rfc8613#section-5.4" class="relref">Section 5.4</a> of [<a href="#RFC8613" class="cite xref">RFC8613</a>]</span> and <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-4.4" class="relref">Section 4.4</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.1-6" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="underlying-transport">
@@ -1645,7 +1645,7 @@ <h5 id="name-underlying-transport">
 <p id="section-2.5.2.2-5">Upon receiving a protected message, the recipient endpoint retrieves the OSCORE Security Context to use for decryption based on key identifier information specified in the CoAP OSCORE Option of protected requests, and on the value of the CoAP Token of protected responses.<a href="#section-2.5.2.2-5" class="pilcrow">¶</a></p>
 <p id="section-2.5.2.2-6">In OSCORE, the key identifier information in request messages is
 typically limited to a "kid", with a value the OSCORE Sender ID associated with the message sender. In case Sender IDs are not unique among different OSCORE Security Contexts stored by the same peer, it is possible to disambiguate by additionally using a "kid context" identifying the OSCORE Security Context as a whole. Instead, response messages are not required to convey key identifier information, as the client can rely on the Token conveyed in the response for retrieving the Security Context to use (see above).<a href="#section-2.5.2.2-6" class="pilcrow">¶</a></p>
-<p id="section-2.5.2.2-7">In Group OSCORE, the key identifier information in request messages always includes also a "kid context", whose value is used as identifier of the OSCORE group associated with the Security Context to use for security processing of the exchanged message. Response messages are also required to convey a "kid" as key identifier information (i.e., the OSCORE Sender ID associated with the message sender), if the corresponding request was protected with the group mode of Group OSCORE (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-8" class="relref">Section 8</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>) .<a href="#section-2.5.2.2-7" class="pilcrow">¶</a></p>
+<p id="section-2.5.2.2-7">In Group OSCORE, the key identifier information in request messages always includes also a "kid context", whose value is used as identifier of the OSCORE group associated with the Security Context to use for security processing of the exchanged message. Response messages are also required to convey a "kid" as key identifier information (i.e., the OSCORE Sender ID associated with the message sender), if the corresponding request was protected with the group mode of Group OSCORE (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-8" class="relref">Section 8</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>) .<a href="#section-2.5.2.2-7" class="pilcrow">¶</a></p>
 <p id="section-2.5.2.2-8">Some particular uses of (Group) OSCORE enable to build OSCORE-based tunneling <span>[<a href="#I-D.ietf-core-oscore-capable-proxies" class="cite xref">I-D.ietf-core-oscore-capable-proxies</a>]</span>. In such a case, a CoAP server might have to enforce that some OSCORE Security Contexts are not just looked up by a "kid" and similar key identifier information from the CoAP OSCORE Option in the incoming request to decrypt. Such a lookup should also rely on the alleged client's address, or on an alternative identifier of the tunnel from which the request came from.<a href="#section-2.5.2.2-8" class="pilcrow">¶</a></p>
 </section>
 </div>
@@ -1674,11 +1674,11 @@ <h5 id="name-key-update">
                 <p id="section-2.5.2.3-3.3.1">Group OSCORE: The Group Manager can distribute new group keying material to the members of an OSCORE group, by performing a group rekeying. When receiving updated group keying material from the Group Manager, either upon joining the group or by participating in a group rekeying, a group member uses that material to install a new, commonly shared Group OSCORE Security Context, which replaces the old one (if any is stored).<a href="#section-2.5.2.3-3.3.1" class="pilcrow">¶</a></p>
 <p id="section-2.5.2.3-3.3.2">
 Also, Group OSCORE makes it possible for group members to safely
-preserve their ongoing active requests (e.g., CoAP Observations), also across the establishment of new Group OSCORE Security Contexts. This is achieved by virtue of how the Group Manager assigns and maintains the identifiers of OSCORE groups (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-3.2.1.1" class="relref">Section 3.2.1.1</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.3-3.3.2" class="pilcrow">¶</a></p>
+preserve their ongoing active requests (e.g., CoAP Observations), also across the establishment of new Group OSCORE Security Contexts. This is achieved by virtue of how the Group Manager assigns and maintains the identifiers of OSCORE groups (see <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-3.2.1.1" class="relref">Section 3.2.1.1</a> of [<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.3-3.3.2" class="pilcrow">¶</a></p>
 <p id="section-2.5.2.3-3.3.3">
 Furthermore, analogous to the update that <span>[<a href="#I-D.ietf-core-oscore-key-update" class="cite xref">I-D.ietf-core-oscore-key-update</a>]</span> makes on the OSCORE protocol with respect to protecting responses, Group OSCORE prevents security issues that can arise from misbinding a request and a response, when those are protected with two different Group OSCORE Security Contexts.<a href="#section-2.5.2.3-3.3.3" class="pilcrow">¶</a></p>
 <p id="section-2.5.2.3-3.3.4">
-In the same way specified in <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-key-update-08#section-3" class="relref">Section 3</a> of [<a href="#I-D.ietf-core-oscore-key-update" class="cite xref">I-D.ietf-core-oscore-key-update</a>]</span> for OSCORE, Group OSCORE requires a server to include its own Sender Sequence Number as Partial IV of an outgoing response, when protecting it with a Security Context different from the one used to protect the corresponding request (see Sections <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-8.3" class="relref">8.3</a> and <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22#section-9.5" class="relref">9.5</a> of <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.3-3.3.4" class="pilcrow">¶</a></p>
+In the same way specified in <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-key-update-08#section-3" class="relref">Section 3</a> of [<a href="#I-D.ietf-core-oscore-key-update" class="cite xref">I-D.ietf-core-oscore-key-update</a>]</span> for OSCORE, Group OSCORE requires a server to include its own Sender Sequence Number as Partial IV of an outgoing response, when protecting it with a Security Context different from the one used to protect the corresponding request (see Sections <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-8.3" class="relref">8.3</a> and <a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23#section-9.5" class="relref">9.5</a> of <span>[<a href="#I-D.ietf-core-oscore-groupcomm" class="cite xref">I-D.ietf-core-oscore-groupcomm</a>]</span>).<a href="#section-2.5.2.3-3.3.4" class="pilcrow">¶</a></p>
 </li>
             </ul>
 </section>
@@ -1881,7 +1881,7 @@ <h3 id="name-informative-references">
 <dd class="break"></dd>
 <dt id="I-D.ietf-core-oscore-groupcomm">[I-D.ietf-core-oscore-groupcomm]</dt>
         <dd>
-<span class="refAuthor">Tiloca, M.</span>, <span class="refAuthor">Selander, G.</span>, <span class="refAuthor">Palombini, F.</span>, <span class="refAuthor">Mattsson, J. P.</span>, and <span class="refAuthor">R. Höglund</span>, <span class="refTitle">"Group Object Security for Constrained RESTful Environments (Group OSCORE)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-core-oscore-groupcomm-22</span>, <time datetime="2024-08-28" class="refDate">28 August 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22">https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-22</a>&gt;</span>. </dd>
+<span class="refAuthor">Tiloca, M.</span>, <span class="refAuthor">Selander, G.</span>, <span class="refAuthor">Palombini, F.</span>, <span class="refAuthor">Mattsson, J. P.</span>, and <span class="refAuthor">R. Höglund</span>, <span class="refTitle">"Group Object Security for Constrained RESTful Environments (Group OSCORE)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-core-oscore-groupcomm-23</span>, <time datetime="2024-09-26" class="refDate">26 September 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23">https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-groupcomm-23</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="I-D.ietf-core-oscore-key-update">[I-D.ietf-core-oscore-key-update]</dt>
         <dd>
diff --git a/draft-bormann-core-corr-clar.txt b/draft-ietf-core-corr-clar.txt
similarity index 93%
rename from draft-bormann-core-corr-clar.txt
rename to draft-ietf-core-corr-clar.txt
index 22a174c..17491f2 100644
--- a/draft-bormann-core-corr-clar.txt
+++ b/draft-ietf-core-corr-clar.txt
@@ -4,14 +4,14 @@
 
 Network Working Group                                         C. Bormann
 Internet-Draft                                    Universität Bremen TZI
-Updates: 6690, 7252, 7641, 7959, 8132, 8323 (if        24 September 2024
+Updates: 6690, 7252, 7641, 7959, 8132, 8323 (if          14 October 2024
          approved)                                                      
 Intended status: Standards Track                                        
-Expires: 28 March 2025
+Expires: 17 April 2025
 
 
 Constrained Application Protocol (CoAP): Corrections and Clarifications
-                  draft-bormann-core-corr-clar-latest
+                    draft-ietf-core-corr-clar-latest
 
 Abstract
 
@@ -33,7 +33,7 @@ About This Document
    This note is to be removed before publishing as an RFC.
 
    Status information for this document may be found at
-   https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar/.
+   https://datatracker.ietf.org/doc/draft-ietf-core-corr-clar/.
 
    Discussion of this document takes place on the core Working Group
    mailing list (mailto:core@ietf.org), which is archived at
@@ -53,9 +53,9 @@ Status of This Memo
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 1]
+Bormann                   Expires 17 April 2025                 [Page 1]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    Internet-Drafts are working documents of the Internet Engineering
@@ -68,7 +68,7 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on 28 March 2025.
+   This Internet-Draft will expire on 17 April 2025.
 
 Copyright Notice
 
@@ -109,9 +109,9 @@ Table of Contents
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 2]
+Bormann                   Expires 17 April 2025                 [Page 2]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
      5.2.  Informative References  . . . . . . . . . . . . . . . . .  17
@@ -165,9 +165,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 3]
+Bormann                   Expires 17 April 2025                 [Page 3]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
 1.1.2.  Proposed text based on IETF 117 and 2023-08-30 CoRE WG interim
@@ -221,9 +221,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 4]
+Bormann                   Expires 17 April 2025                 [Page 4]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    4.  Reshape the -corr-clar document in order to reflect a sequence of
@@ -277,9 +277,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 5]
+Bormann                   Expires 17 April 2025                 [Page 5]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
       Request URI:  The URI that identifies a resource on a server
@@ -333,9 +333,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 6]
+Bormann                   Expires 17 April 2025                 [Page 6]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    reference the Max-Age to the time of reception.  This in effect
@@ -368,8 +368,7 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
    Section 6.4 of [RFC7252].  A slightly updated version of the proposed
    note might be:
 
-   INCOMPLETE; FORMAL ADDITION at the end of Section 6.4 of
-   [RFC7252]:
+   FORMAL ADDITION at the end of Section 6.4 of [RFC7252]:
       Also note that a trailing slash character in the <path> component
       represents a separate, zero-character path segment (see the ABNF
       in Section 3.3 of [RFC3986]).  This is encoded using a Uri-Path
@@ -389,9 +388,10 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 7]
+
+Bormann                   Expires 17 April 2025                 [Page 7]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
          |  Note that the exception at the start of step 8 does not mean
@@ -445,9 +445,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 8]
+Bormann                   Expires 17 April 2025                 [Page 8]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
       The Content-Format code attribute MUST NOT appear more than once
@@ -501,9 +501,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                 [Page 9]
+Bormann                   Expires 17 April 2025                 [Page 9]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
 2.5.2.  OSCORE, KUDOS, and Group OSCORE
@@ -557,9 +557,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 10]
+Bormann                   Expires 17 April 2025                [Page 10]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    Even in case the Token value in a CoAP response is manipulated to
@@ -613,9 +613,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 11]
+Bormann                   Expires 17 April 2025                [Page 11]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    Practically, (Group) OSCORE relies on the underlying CoAP
@@ -669,9 +669,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 12]
+Bormann                   Expires 17 April 2025                [Page 12]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    The following provides more details about key update, separately for
@@ -725,9 +725,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 13]
+Bormann                   Expires 17 April 2025                [Page 13]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
       Also, Group OSCORE makes it possible for group members to safely
@@ -781,9 +781,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 14]
+Bormann                   Expires 17 April 2025                [Page 14]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    *  https://mailarchive.ietf.org/arch/msg/core/
@@ -837,9 +837,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 15]
+Bormann                   Expires 17 April 2025                [Page 15]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
       The VERIFIED Errata Report [Err4954] corrects the usage of
@@ -893,9 +893,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 16]
+Bormann                   Expires 17 April 2025                [Page 16]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    [RFC7641]  Hartke, K., "Observing Resources in the Constrained
@@ -949,9 +949,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 17]
+Bormann                   Expires 17 April 2025                [Page 17]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    [Err5078]  RFC Errata Report 5078, RFC 7252,
@@ -982,9 +982,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
               Tiloca, M., Selander, G., Palombini, F., Mattsson, J. P.,
               and R. Höglund, "Group Object Security for Constrained
               RESTful Environments (Group OSCORE)", Work in Progress,
-              Internet-Draft, draft-ietf-core-oscore-groupcomm-22, 28
-              August 2024, <https://datatracker.ietf.org/doc/html/draft-
-              ietf-core-oscore-groupcomm-22>.
+              Internet-Draft, draft-ietf-core-oscore-groupcomm-23, 26
+              September 2024, <https://datatracker.ietf.org/doc/html/
+              draft-ietf-core-oscore-groupcomm-23>.
 
    [I-D.ietf-core-oscore-key-update]
               Höglund, R. and M. Tiloca, "Key Update for OSCORE
@@ -1005,9 +1005,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 18]
+Bormann                   Expires 17 April 2025                [Page 18]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
    [RFC6838]  Freed, N., Klensin, J., and T. Hansen, "Media Type
@@ -1061,9 +1061,9 @@ Internet-Draft   Corrections and Clarifications to CoAP   September 2024
 
 
 
-Bormann                   Expires 28 March 2025                [Page 19]
+Bormann                   Expires 17 April 2025                [Page 19]
 
-Internet-Draft   Corrections and Clarifications to CoAP   September 2024
+Internet-Draft   Corrections and Clarifications to CoAP     October 2024
 
 
 Acknowledgements
@@ -1117,4 +1117,4 @@ Author's Address
 
 
 
-Bormann                   Expires 28 March 2025                [Page 20]
+Bormann                   Expires 17 April 2025                [Page 20]
diff --git a/index.html b/index.html
index 84e810b..db408b5 100644
--- a/index.html
+++ b/index.html
@@ -17,10 +17,10 @@ <h1>Editor's drafts for main branch of <a href="https://github.com/core-wg/corrc
     <p>View <a href="issues.html">saved issues</a>, or the latest GitHub <a href="https://github.com/core-wg/corrclar/issues">issues</a> and <a href="https://github.com/core-wg/corrclar/pulls">pull requests</a> in the <a href="https://github.com/core-wg/corrclar">repo</a>.</p>
     <table id="branch-main">
       <tr>
-        <td><a href="./draft-bormann-core-corr-clar.html" class="html draft-bormann-core-corr-clar" title=" (HTML)"></a></td>
-        <td><a href="./draft-bormann-core-corr-clar.txt" class="txt draft-bormann-core-corr-clar" title=" (Text)">plain text</a></td>
-        <td><a href="https://datatracker.ietf.org/doc/draft-bormann-core-corr-clar" class="dt draft-bormann-core-corr-clar" title="Datatracker for draft-bormann-core-corr-clar">datatracker</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?doc_1=draft-bormann-core-corr-clar&amp;url_2=https://core-wg.github.io/corrclar/draft-bormann-core-corr-clar.txt" class="diff draft-bormann-core-corr-clar">diff with last submission</a></td>
+        <td><a href="./draft-ietf-core-corr-clar.html" class="html draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (HTML)">Corrections and Clarifications to CoAP</a></td>
+        <td><a href="./draft-ietf-core-corr-clar.txt" class="txt draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (Text)">plain text</a></td>
+        <td><a href="https://datatracker.ietf.org/doc/draft-ietf-core-corr-clar" class="dt draft-ietf-core-corr-clar" title="Datatracker for draft-ietf-core-corr-clar">datatracker</a></td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-core-corr-clar&amp;url_2=https://core-wg.github.io/corrclar/draft-ietf-core-corr-clar.txt" class="diff draft-ietf-core-corr-clar">diff with last submission</a></td>
         <td></td>
       </tr>
     </table>
@@ -29,7 +29,7 @@ <h2>Preview for branch <a href="interim-2024-09-25">interim-2024-09-25</a></h2>
       <tr>
         <td><a href="interim-2024-09-25/draft-ietf-core-corr-clar.html" class="html draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (HTML)">Corrections and Clarifications to CoAP</a></td>
         <td><a href="interim-2024-09-25/draft-ietf-core-corr-clar.txt" class="txt draft-ietf-core-corr-clar" title="Constrained Application Protocol (CoAP): Corrections and Clarifications (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://core-wg.github.io/corrclar/draft-ietf-core-corr-clar.txt&amp;url_2=https://core-wg.github.io/corrclar/interim-2024-09-25/draft-ietf-core-corr-clar.txt" class="diff draft-ietf-core-corr-clar">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <h2>Preview for branch <a href="address-9-oscore">address-9-oscore</a></h2>