From 93fd0e8e44861c71679efa3309f92d96f14a6469 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Fri, 4 Oct 2024 09:19:42 +0000
Subject: [PATCH] Script updating gh-pages from 70eca76. [ci skip]

---
 cp_mtu/draft-dekater-scion-controlplane.html | 10 +++++-----
 cp_mtu/draft-dekater-scion-controlplane.txt  | 18 ++++++++----------
 2 files changed, 13 insertions(+), 15 deletions(-)

diff --git a/cp_mtu/draft-dekater-scion-controlplane.html b/cp_mtu/draft-dekater-scion-controlplane.html
index 299d17b..c5c14e7 100644
--- a/cp_mtu/draft-dekater-scion-controlplane.html
+++ b/cp_mtu/draft-dekater-scion-controlplane.html
@@ -1031,7 +1031,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">de Kater, et al.</td>
-<td class="center">Expires 6 April 2025</td>
+<td class="center">Expires 7 April 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1044,12 +1044,12 @@
 <dd class="internet-draft">draft-dekater-scion-controlplane-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-10-03" class="published">3 October 2024</time>
+<time datetime="2024-10-04" class="published">4 October 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Informational</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-04-06">6 April 2025</time></dd>
+<dd class="expires"><time datetime="2025-04-07">7 April 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1103,7 +1103,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 6 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 7 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2478,7 +2478,7 @@ <h5 id="name-hop-entry">
                 <p id="section-2.2.1.5-5.1.1"><code>hop_field</code>: Contains the authenticated information about the ingress and egress interfaces in the direction of beaconing. The data plane needs this information to forward packets through the current AS. For further specifications, see <a href="#hopfield" class="auto internal xref">Section 2.2.1.6</a>.<a href="#section-2.2.1.5-5.1.1" class="pilcrow">¶</a></p>
 </li>
               <li class="normal" id="section-2.2.1.5-5.2">
-                <p id="section-2.2.1.5-5.2.1"><code>ingress_mtu</code>: Specifies the maximum transmission unit (MTU) of the ingress interface (in beaconing direction) of the hop being described. Packets traversing the associated inter-AS link in either direction cannot be larger than this size. As a result, no path segment constructed from the containing beacon can have an MTU greater than this. How the control service obtains the MTU of an inter-AS link is implementation dependent. It may be discovered or configured. Current practice to make it a configuration item.<a href="#section-2.2.1.5-5.2.1" class="pilcrow">¶</a></p>
+                <p id="section-2.2.1.5-5.2.1"><code>ingress_mtu</code>: Specifies the maximum transmission unit (MTU) of the ingress interface (in beaconing direction) of the hop being described. The MTU of path segments constructed from the containing beacon is necessarily less than or equal to this value. How the control service obtains the MTU of an inter-AS link is implementation dependent. It may be discovered or configured. Current practice to make it a configuration item.<a href="#section-2.2.1.5-5.2.1" class="pilcrow">¶</a></p>
 </li>
             </ul>
 <p id="section-2.2.1.5-6">In this description, MTU and packet size are to be understood in the same sense as in <span>[<a href="#RFC1122" class="cite xref">RFC1122</a>]</span>. That is, exclusive of any layer 2 framing or packet encapsulation (for links using an underlay network).<a href="#section-2.2.1.5-6" class="pilcrow">¶</a></p>
diff --git a/cp_mtu/draft-dekater-scion-controlplane.txt b/cp_mtu/draft-dekater-scion-controlplane.txt
index af2af0b..c0b445e 100644
--- a/cp_mtu/draft-dekater-scion-controlplane.txt
+++ b/cp_mtu/draft-dekater-scion-controlplane.txt
@@ -5,9 +5,9 @@
 Network Working Group                                        C. de Kater
 Internet-Draft                                             N. Rustignoli
 Intended status: Informational                         SCION Association
-Expires: 6 April 2025                                            S. Hitz
+Expires: 7 April 2025                                            S. Hitz
                                                          Anapaya Systems
-                                                          3 October 2024
+                                                          4 October 2024
 
 
                           SCION Control Plane
@@ -63,7 +63,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 6 April 2025.
+   This Internet-Draft will expire on 7 April 2025.
 
 Copyright Notice
 
@@ -1429,13 +1429,11 @@ path segment 4 |             |     |             |     |             |
 
    *  ingress_mtu: Specifies the maximum transmission unit (MTU) of the
       ingress interface (in beaconing direction) of the hop being
-      described.  Packets traversing the associated inter-AS link in
-      either direction cannot be larger than this size.  As a result, no
-      path segment constructed from the containing beacon can have an
-      MTU greater than this.  How the control service obtains the MTU of
-      an inter-AS link is implementation dependent.  It may be
-      discovered or configured.  Current practice to make it a
-      configuration item.
+      described.  The MTU of path segments constructed from the
+      containing beacon is necessarily less than or equal to this value.
+      How the control service obtains the MTU of an inter-AS link is
+      implementation dependent.  It may be discovered or configured.
+      Current practice to make it a configuration item.
 
    In this description, MTU and packet size are to be understood in the
    same sense as in [RFC1122].  That is, exclusive of any layer 2