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

Author: ID Bot

draft-ietf-moq-transport.html

@@ -1055,7 +1055,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Nandakumar, et al.</td>
-<td class="center">Expires 29 May 2026</td>
+<td class="center">Expires 30 May 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-11-25" class="published">25 November 2025</time>
+<time datetime="2025-11-26" class="published">26 November 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-05-29">29 May 2026</time></dd>
+<dd class="expires"><time datetime="2026-05-30">30 May 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 29 May 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 30 May 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2058,8 +2058,8 @@ <h3 id="name-subgroups">
 stream and are sent on a single stream whenever possible. A Group is delivered
 using at least as many streams as there are Subgroups,
 typically with a one-to-one mapping between Subgroups and streams.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
-<p id="section-2.2-2">When a Track's forwarding preference (see <a href="#object-properties" class="auto internal xref">Section 10.2.1</a>) is
-"Datagram", Objects are not sent in Subgroups and the
+<p id="section-2.2-2">When an Object's forwarding preference (see <a href="#object-properties" class="auto internal xref">Section 10.2.1</a>) is
+"Datagram", it is not sent in Subgroups and the
 description in the remainder of this section does not apply.<a href="#section-2.2-2" class="pilcrow">¶</a></p>
 <p id="section-2.2-3">Streams offer in-order reliable delivery and the ability to cancel sending and
 retransmission of data. Furthermore, many QUIC and WebTransport implementations
@@ -2249,7 +2249,7 @@ <h4 id="name-malformed-tracks">
 </li>
             <li id="section-2.4.2-2.10">
               <p id="section-2.4.2-2.10.1">An Object is received with a different Forwarding Preference than previously
-observed from the same Track.<a href="#section-2.4.2-2.10.1" class="pilcrow">¶</a></p>
+observed.<a href="#section-2.4.2-2.10.1" class="pilcrow">¶</a></p>
 </li>
           </ol>
 <p id="section-2.4.2-3">The above list of conditions is not considered exhaustive.<a href="#section-2.4.2-3" class="pilcrow">¶</a></p>
@@ -3001,8 +3001,7 @@ <h3 id="name-definitions">
             <p id="section-7.1-2.1.1">The first or next Object in a Subgroup that is in response to a subscription.<a href="#section-7.1-2.1.1" class="pilcrow">¶</a></p>
 </li>
           <li id="section-7.1-2.2">
-            <p id="section-7.1-2.2.1">An Object in response to a subscription that belongs to a Track with
-delivery preference Datagram.<a href="#section-7.1-2.2.1" class="pilcrow">¶</a></p>
+            <p id="section-7.1-2.2.1">An Object with forwarding preference Datagram.<a href="#section-7.1-2.2.1" class="pilcrow">¶</a></p>
 </li>
           <li id="section-7.1-2.3">
             <p id="section-7.1-2.3.1">An Object in response to a FETCH where that Object is the next
@@ -3065,9 +3064,10 @@ <h3 id="name-scheduling-algorithm">
           <li id="section-7.2-2.4">
             <p id="section-7.2-2.4.1">If two objects in response to the same request have the same subscriber
 and publisher priority and belong to the same group of the same track, the
-one with <strong>the lowest Subgroup ID</strong> (for tracks with delivery preference
-Subgroup), or <strong>the lowest Object ID</strong> (for tracks with delivery preference
-Datagram) is scheduled to be sent first.<a href="#section-7.2-2.4.1" class="pilcrow">¶</a></p>
+one with <strong>the lowest Subgroup ID</strong> (for objects with forwarding preference
+Subgroup), or <strong>the lowest Object ID</strong> (for objects with forwarding preference
+Datagram) is scheduled to be sent first.  If the two objects have
+different Forwarding Preferences the order is implementation dependent.<a href="#section-7.2-2.4.1" class="pilcrow">¶</a></p>
 </li>
         </ol>
 <p id="section-7.2-3">The definition of "scheduled to be sent first" in the algorithm is implementation
@@ -4728,7 +4728,7 @@ <h3 id="name-publish_done">
 opened for this subscription.  This helps the subscriber know if it has received
 all of the data published in this subscription by comparing the number of
 streams received.  The subscriber can immediately remove all subscription state
-once the same number of streams have been processed.  If the track had
+once the same number of streams have been processed.  If the track had only Objects with
 Forwarding Preference = Datagram, the publisher <span class="bcp14">MUST</span> set Stream Count to 0.  If
 the publisher is unable to set Stream Count to the exact number of streams
 opened for the subscription, it <span class="bcp14">MUST</span> set Stream Count to 2^62 - 1. Subscribers
@@ -5391,9 +5391,8 @@ <h2 id="name-data-streams-and-datagrams">
 the datagram.  See <a href="#object-datagram" class="auto internal xref">Section 10.3.1</a>.<a href="#section-10-4" class="pilcrow">¶</a></p>
 <p id="section-10-5">An endpoint that receives an unknown stream or datagram type <span class="bcp14">MUST</span> close the
 session.<a href="#section-10-5" class="pilcrow">¶</a></p>
-<p id="section-10-6">Every Track has a single 'Object Forwarding Preference' and the Original
-Publisher <span class="bcp14">MUST NOT</span> mix different forwarding preferences within a single track
-(see <a href="#malformed-tracks" class="auto internal xref">Section 2.4.2</a>).<a href="#section-10-6" class="pilcrow">¶</a></p>
+<p id="section-10-6">Every Object has a 'Object Forwarding Preference' and the Original Publisher
+<span class="bcp14">MAY</span> mix different forwarding preference within a single track.<a href="#section-10-6" class="pilcrow">¶</a></p>
 <div id="track-alias">
 <section id="section-10.1">
         <h3 id="name-track-alias">
@@ -5439,13 +5438,10 @@ <h4 id="name-canonical-object-properties">
 </li>
             <li class="normal" id="section-10.2.1-2.5">
               <p id="section-10.2.1-2.5.1">Object Forwarding Preference: An enumeration indicating how a publisher sends
-an object. The preferences are Subgroup and Datagram.  Note that the Original
-Publisher determines the Forwarding Preference for the entire Track, and is a
-Track property that is implicitly signaled by the delivery of any Object using
-either Subgroups or Datagrams. Once the property is established for one Object
-of a Track, the same value <span class="bcp14">MUST</span> be used for all Objects of the Track.
-In a subscription, an Object <span class="bcp14">MUST</span> be sent according to its <code>Object Forwarding
-Preference</code>.<a href="#section-10.2.1-2.5.1" class="pilcrow">¶</a></p>
+an object. The preferences are Subgroup and Datagram.  <code>Object Forwarding
+Preference</code> is a property of an individual Object and can vary among
+Objects in the same Track.  In a subscription, an Object <span class="bcp14">MUST</span> be sent
+according to its <code>Object Forwarding Preference</code>.<a href="#section-10.2.1-2.5.1" class="pilcrow">¶</a></p>
 </li>
             <li class="normal" id="section-10.2.1-2.6">
               <p id="section-10.2.1-2.6.1">Subgroup ID: The identifier of the Object's Subgroup (see <a href="#model-subgroup" class="auto internal xref">Section 2.2</a>)

draft-ietf-moq-transport.txt

@@ -5,11 +5,11 @@
 Media Over QUIC                                            S. Nandakumar
 Internet-Draft                                                     Cisco
 Intended status: Standards Track                             V. Vasiliev
-Expires: 29 May 2026                                       I. Swett, Ed.
+Expires: 30 May 2026                                       I. Swett, Ed.
                                                                   Google
                                                         A. Frindell, Ed.
                                                                     Meta
-                                                        25 November 2025
+                                                        26 November 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 29 May 2026.
+   This Internet-Draft will expire on 30 May 2026.
 
 Copyright Notice
 
@@ -517,9 +517,9 @@ Table of Contents
    delivered using at least as many streams as there are Subgroups,
    typically with a one-to-one mapping between Subgroups and streams.
 
-   When a Track's forwarding preference (see Section 10.2.1) is
-   "Datagram", Objects are not sent in Subgroups and the description in
-   the remainder of this section does not apply.
+   When an Object's forwarding preference (see Section 10.2.1) is
+   "Datagram", it is not sent in Subgroups and the description in the
+   remainder of this section does not apply.
 
    Streams offer in-order reliable delivery and the ability to cancel
    sending and retransmission of data.  Furthermore, many QUIC and
@@ -694,7 +694,7 @@ Table of Contents
         Payload or other immutable properties.
 
    10.  An Object is received with a different Forwarding Preference
-        than previously observed from the same Track.
+        than previously observed.
 
    The above list of conditions is not considered exhaustive.
 
@@ -1362,8 +1362,7 @@ Table of Contents
    1.  The first or next Object in a Subgroup that is in response to a
        subscription.
 
-   2.  An Object in response to a subscription that belongs to a Track
-       with delivery preference Datagram.
+   2.  An Object with forwarding preference Datagram.
 
    3.  An Object in response to a FETCH where that Object is the next
        Object in the response.
@@ -1425,10 +1424,11 @@ Table of Contents
 
    4.  If two objects in response to the same request have the same
        subscriber and publisher priority and belong to the same group of
-       the same track, the one with *the lowest Subgroup ID* (for tracks
-       with delivery preference Subgroup), or *the lowest Object ID*
-       (for tracks with delivery preference Datagram) is scheduled to be
-       sent first.
+       the same track, the one with *the lowest Subgroup ID* (for
+       objects with forwarding preference Subgroup), or *the lowest
+       Object ID* (for objects with forwarding preference Datagram) is
+       scheduled to be sent first.  If the two objects have different
+       Forwarding Preferences the order is implementation dependent.
 
    The definition of "scheduled to be sent first" in the algorithm is
    implementation dependent and is constrained by the prioritization
@@ -2819,16 +2819,16 @@ Table of Contents
       know if it has received all of the data published in this
       subscription by comparing the number of streams received.  The
       subscriber can immediately remove all subscription state once the
-      same number of streams have been processed.  If the track had
-      Forwarding Preference = Datagram, the publisher MUST set Stream
-      Count to 0.  If the publisher is unable to set Stream Count to the
-      exact number of streams opened for the subscription, it MUST set
-      Stream Count to 2^62 - 1.  Subscribers SHOULD use a timeout or
-      other mechanism to remove subscription state in case the publisher
-      set an incorrect value, reset a stream before the SUBGROUP_HEADER,
-      or set the maximum value.  If a subscriber receives more streams
-      for a subscription than specified in Stream Count, it MAY close
-      the session with a PROTOCOL_VIOLATION.
+      same number of streams have been processed.  If the track had only
+      Objects with Forwarding Preference = Datagram, the publisher MUST
+      set Stream Count to 0.  If the publisher is unable to set Stream
+      Count to the exact number of streams opened for the subscription,
+      it MUST set Stream Count to 2^62 - 1.  Subscribers SHOULD use a
+      timeout or other mechanism to remove subscription state in case
+      the publisher set an incorrect value, reset a stream before the
+      SUBGROUP_HEADER, or set the maximum value.  If a subscriber
+      receives more streams for a subscription than specified in Stream
+      Count, it MAY close the session with a PROTOCOL_VIOLATION.
 
    *  Error Reason: Provides the reason for subscription error.  See
       Section 1.4.3.
@@ -3327,9 +3327,9 @@ Table of Contents
    An endpoint that receives an unknown stream or datagram type MUST
    close the session.
 
-   Every Track has a single 'Object Forwarding Preference' and the
-   Original Publisher MUST NOT mix different forwarding preferences
-   within a single track (see Section 2.4.2).
+   Every Object has a 'Object Forwarding Preference' and the Original
+   Publisher MAY mix different forwarding preference within a single
+   track.
 
 10.1.  Track Alias
 
@@ -3365,13 +3365,10 @@ Table of Contents
 
    *  Object Forwarding Preference: An enumeration indicating how a
       publisher sends an object.  The preferences are Subgroup and
-      Datagram.  Note that the Original Publisher determines the
-      Forwarding Preference for the entire Track, and is a Track
-      property that is implicitly signaled by the delivery of any Object
-      using either Subgroups or Datagrams.  Once the property is
-      established for one Object of a Track, the same value MUST be used
-      for all Objects of the Track.  In a subscription, an Object MUST
-      be sent according to its Object Forwarding Preference.
+      Datagram.  Object Forwarding Preference is a property of an
+      individual Object and can vary among Objects in the same Track.
+      In a subscription, an Object MUST be sent according to its Object
+      Forwarding Preference.
 
    *  Subgroup ID: The identifier of the Object's Subgroup (see
       Section 2.2) within the Group.  This field is omitted if the

index.html

@@ -141,7 +141,7 @@ <h2>Preview for branch <a href="ianswett-move-prior-group-id">ianswett-move-prio
       <tr>
         <td><a href="ianswett-move-prior-group-id/draft-ietf-moq-transport.html" class="html draft-ietf-moq-transport" title="Media over QUIC Transport (HTML)">moq-transport</a></td>
         <td><a href="ianswett-move-prior-group-id/draft-ietf-moq-transport.txt" class="txt draft-ietf-moq-transport" title="Media over QUIC Transport (Text)">plain text</a></td>
-        <td>same as main</td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://moq-wg.github.io/moq-transport/draft-ietf-moq-transport.txt&amp;url_2=https://moq-wg.github.io/moq-transport/ianswett-move-prior-group-id/draft-ietf-moq-transport.txt" class="diff draft-ietf-moq-transport">diff with main</a></td>
       </tr>
     </table>
     <h2>Preview for branch <a href="ianswett-largest-group">ianswett-largest-group</a></h2>