Script updating gh-pages from a0e6b3b. [ci skip]

Author: ID Bot

ianswett-streamy-namespaces/draft-ietf-moq-transport.html

@@ -1055,7 +1055,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Nandakumar, et al.</td>
-<td class="center">Expires 4 June 2026</td>
+<td class="center">Expires 5 June 2026</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1068,12 +1068,12 @@
 <dd class="internet-draft">draft-ietf-moq-transport-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2025-12-01" class="published">1 December 2025</time>
+<time datetime="2025-12-02" class="published">2 December 2025</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="2026-06-04">4 June 2026</time></dd>
+<dd class="expires"><time datetime="2026-06-05">5 June 2026</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1142,7 +1142,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 4 June 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 5 June 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2451,7 +2451,7 @@ <h3 id="name-session-initialization">
 messages defined in <a href="#message" class="auto internal xref">Section 9</a>.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
 <p id="section-3.3-2">This specification only specifies two uses of bidirectional streams, the control
 stream and SUBSCRIBE_NAMESPACE. Objects are sent on unidirectional streams.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
-<p id="section-3.3-3">A unidirectional stream or bidirectional stream containing a SUBSCRIBE_NAMESPACE
+<p id="section-3.3-3">A unidirectional stream containing Objects or bidirectional stream(s) containing a SUBSCRIBE_NAMESPACE
 could arrive prior to the control stream, in which case the data <span class="bcp14">SHOULD</span> be buffered
 until the control stream arrives and setup is complete.
 If an implementation does not want to buffer, it <span class="bcp14">MAY</span> reset other bidirectional

ianswett-streamy-namespaces/draft-ietf-moq-transport.txt

@@ -5,11 +5,11 @@
 Media Over QUIC                                            S. Nandakumar
 Internet-Draft                                                     Cisco
 Intended status: Standards Track                             V. Vasiliev
-Expires: 4 June 2026                                       I. Swett, Ed.
+Expires: 5 June 2026                                       I. Swett, Ed.
                                                                   Google
                                                         A. Frindell, Ed.
                                                                     Meta
-                                                         1 December 2025
+                                                         2 December 2025
 
 
                        Media over QUIC Transport
@@ -57,7 +57,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 4 June 2026.
+   This Internet-Draft will expire on 5 June 2026.
 
 Copyright Notice
 
@@ -871,12 +871,12 @@ Table of Contents
    the control stream and SUBSCRIBE_NAMESPACE.  Objects are sent on
    unidirectional streams.
 
-   A unidirectional stream or bidirectional stream containing a
-   SUBSCRIBE_NAMESPACE could arrive prior to the control stream, in
-   which case the data SHOULD be buffered until the control stream
-   arrives and setup is complete.  If an implementation does not want to
-   buffer, it MAY reset other bidirectional streams before the session
-   and control stream are established.
+   A unidirectional stream containing Objects or bidirectional stream(s)
+   containing a SUBSCRIBE_NAMESPACE could arrive prior to the control
+   stream, in which case the data SHOULD be buffered until the control
+   stream arrives and setup is complete.  If an implementation does not
+   want to buffer, it MAY reset other bidirectional streams before the
+   session and control stream are established.
 
    The control stream MUST NOT be closed at the underlying transport
    layer during the session's lifetime.  Doing so results in the session