diff --git a/marco-wglc-review/draft-ietf-tls-dtls-rrc.html b/marco-wglc-review/draft-ietf-tls-dtls-rrc.html
index 35c0879..3fb59d5 100644
--- a/marco-wglc-review/draft-ietf-tls-dtls-rrc.html
+++ b/marco-wglc-review/draft-ietf-tls-dtls-rrc.html
@@ -1033,7 +1033,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Tschofenig, et al.</td>
-<td class="center">Expires 8 April 2024</td>
+<td class="center">Expires 11 April 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1049,12 +1049,12 @@
 <a href="https://www.rfc-editor.org/rfc/rfc6347" class="eref">6347</a>, <a href="https://www.rfc-editor.org/rfc/rfc9147" class="eref">9147</a> (if approved)</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-10-06" class="published">6 October 2023</time>
+<time datetime="2023-10-09" class="published">9 October 2023</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="2024-04-08">8 April 2024</time></dd>
+<dd class="expires"><time datetime="2024-04-11">11 April 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1108,7 +1108,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 8 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 11 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2003,10 +2003,10 @@ <h3 id="name-timer-choice">
       <h2 id="name-example">
 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-example" class="section-name selfRef">Example</a>
       </h2>
-<p id="section-8-1">In the example TLS 1.3 handshake shown in <a href="#fig-handshake" class="auto internal xref">Figure 7</a>, a client
+<p id="section-8-1">In the example DTLS 1.3 handshake shown in <a href="#fig-handshake" class="auto internal xref">Figure 7</a>, a client
 and a server successfully negotiate support for both CID and the RRC
 extension.<a href="#section-8-1" class="pilcrow">¶</a></p>
-<span id="name-message-flow-for-full-tls-h"></span><div id="fig-handshake">
+<span id="name-message-flow-for-full-dtls-"></span><div id="fig-handshake">
 <figure id="figure-7">
         <div class="alignLeft art-text artwork" id="section-8-2.1">
 <pre>
@@ -2047,7 +2047,7 @@ <h2 id="name-example">
 </pre>
 </div>
 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
-<a href="#name-message-flow-for-full-tls-h" class="selfRef">Message Flow for Full TLS Handshake</a>
+<a href="#name-message-flow-for-full-dtls-" class="selfRef">Message Flow for Full DTLS Handshake</a>
         </figcaption></figure>
 </div>
 <p id="section-8-3">Once a connection has been established, the client and the server
diff --git a/marco-wglc-review/draft-ietf-tls-dtls-rrc.txt b/marco-wglc-review/draft-ietf-tls-dtls-rrc.txt
index 6c2f40a..7414668 100644
--- a/marco-wglc-review/draft-ietf-tls-dtls-rrc.txt
+++ b/marco-wglc-review/draft-ietf-tls-dtls-rrc.txt
@@ -6,9 +6,9 @@ TLS                                                   H. Tschofenig, Ed.
 Internet-Draft                                                          
 Updates: 6347, 9147 (if approved)                               A. Kraus
 Intended status: Standards Track                                        
-Expires: 8 April 2024                                         T. Fossati
+Expires: 11 April 2024                                        T. Fossati
                                                                   Linaro
-                                                          6 October 2023
+                                                          9 October 2023
 
 
            Return Routability Check for DTLS 1.2 and DTLS 1.3
@@ -46,7 +46,7 @@ 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."
 
-   This Internet-Draft will expire on 8 April 2024.
+   This Internet-Draft will expire on 11 April 2024.
 
 Copyright Notice
 
@@ -598,7 +598,7 @@ Table of Contents
 
 8.  Example
 
-   In the example TLS 1.3 handshake shown in Figure 7, a client and a
+   In the example DTLS 1.3 handshake shown in Figure 7, a client and a
    server successfully negotiate support for both CID and the RRC
    extension.
 
@@ -637,7 +637,7 @@ Auth | {CertificateVerify}
               [] Indicates messages protected using keys
                  derived from [sender]_application_traffic_secret_N.
 
-            Figure 7: Message Flow for Full TLS Handshake
+            Figure 7: Message Flow for Full DTLS Handshake
 
    Once a connection has been established, the client and the server
    exchange application payloads protected by DTLS with a unilaterally