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

draft-ietf-avtcore-rtp-over-quic.html

@@ -1037,7 +1037,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Ott, et al.</td>
-<td class="center">Expires 4 November 2024</td>
+<td class="center">Expires 9 November 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1050,12 +1050,12 @@
 <dd class="internet-draft">draft-ietf-avtcore-rtp-over-quic-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-05-03" class="published">3 May 2024</time>
+<time datetime="2024-05-08" class="published">8 May 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Experimental</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2024-11-04">4 November 2024</time></dd>
+<dd class="expires"><time datetime="2024-11-09">9 November 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1114,7 +1114,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 November 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 9 November 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2260,7 +2260,7 @@ <h3 id="name-quic-datagrams">
 <p id="section-5.3-1">Senders can also transmit RTP packets in QUIC DATAGRAMs, using
 a QUIC extension described in <span>[<a href="#RFC9221" class="cite xref">RFC9221</a>]</span>.
 DATAGRAMs can only be used if the use of the DATAGRAM extension was successfully negotiated during the QUIC handshake.
-If the QUIC extension was negotiated using a signaling protocol, but that extension was not negotiated during the resulting QUIC handshake, an endpoint MAY close the connection with the ROQ_EXPECTATION_UNMET error code.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
+If the DATAGRAM extension was negotiated using a signaling protocol, but was not also negotiated during the resulting QUIC handshake, an endpoint can close the connection with the ROQ_EXPECTATION_UNMET error code.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
 <p id="section-5.3-2">DATAGRAMs preserve application frame boundaries.
 Thus, a single RTP packet can be mapped to a single DATAGRAM without additional framing.
 Because QUIC DATAGRAMs cannot be IP-fragmented (<span><a href="https://rfc-editor.org/rfc/rfc9221#section-5" class="relref">Section 5</a> of [<a href="#RFC9221" class="cite xref">RFC9221</a>]</span>), senders need to consider the header overhead associated with DATAGRAMs, and ensure that the RTP packets, including their payloads, flow identifier, QUIC, and IP headers, will fit into the Path MTU.<a href="#section-5.3-2" class="pilcrow">¶</a></p>
@@ -3249,7 +3249,7 @@ <h3 id="name-informative-references">
 <dd class="break"></dd>
 <dt id="I-D.draft-ietf-wish-whip">[I-D.draft-ietf-wish-whip]</dt>
         <dd>
-<span class="refAuthor">Murillo, S. G.</span> and <span class="refAuthor">A. Gouaillard</span>, <span class="refTitle">"WebRTC-HTTP ingestion protocol (WHIP)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-wish-whip-13</span>, <time datetime="2024-02-07" class="refDate">7 February 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-wish-whip-13">https://datatracker.ietf.org/doc/html/draft-ietf-wish-whip-13</a>&gt;</span>. </dd>
+<span class="refAuthor">Murillo, S. G.</span> and <span class="refAuthor">A. Gouaillard</span>, <span class="refTitle">"WebRTC-HTTP ingestion protocol (WHIP)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-wish-whip-14</span>, <time datetime="2024-05-03" class="refDate">3 May 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-wish-whip-14">https://datatracker.ietf.org/doc/html/draft-ietf-wish-whip-14</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="I-D.draft-smith-quic-receive-ts">[I-D.draft-smith-quic-receive-ts]</dt>
         <dd>

draft-ietf-avtcore-rtp-over-quic.txt

@@ -5,9 +5,9 @@
 Audio/Video Transport Core Maintenance                            J. Ott
 Internet-Draft                                              M. Engelbart
 Intended status: Experimental                Technical University Munich
-Expires: 4 November 2024                                      S. Dawkins
+Expires: 9 November 2024                                      S. Dawkins
                                                      Tencent America LLC
-                                                              3 May 2024
+                                                              8 May 2024
 
 
                           RTP over QUIC (RoQ)
@@ -52,7 +52,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 November 2024.
+   This Internet-Draft will expire on 9 November 2024.
 
 Copyright Notice
 
@@ -1103,10 +1103,10 @@ Table of Contents
    Senders can also transmit RTP packets in QUIC DATAGRAMs, using a QUIC
    extension described in [RFC9221].  DATAGRAMs can only be used if the
    use of the DATAGRAM extension was successfully negotiated during the
-   QUIC handshake.  If the QUIC extension was negotiated using a
-   signaling protocol, but that extension was not negotiated during the
-   resulting QUIC handshake, an endpoint MAY close the connection with
-   the ROQ_EXPECTATION_UNMET error code.
+   QUIC handshake.  If the DATAGRAM extension was negotiated using a
+   signaling protocol, but was not also negotiated during the resulting
+   QUIC handshake, an endpoint can close the connection with the
+   ROQ_EXPECTATION_UNMET error code.
 
    DATAGRAMs preserve application frame boundaries.  Thus, a single RTP
    packet can be mapped to a single DATAGRAM without additional framing.
@@ -2124,9 +2124,9 @@ Table of Contents
    [I-D.draft-ietf-wish-whip]
               Murillo, S. G. and A. Gouaillard, "WebRTC-HTTP ingestion
               protocol (WHIP)", Work in Progress, Internet-Draft, draft-
-              ietf-wish-whip-13, 7 February 2024,
+              ietf-wish-whip-14, 3 May 2024,
               <https://datatracker.ietf.org/doc/html/draft-ietf-wish-
-              whip-13>.
+              whip-14>.
 
    [I-D.draft-smith-quic-receive-ts]
               Smith, C. and I. Swett, "QUIC Extension for Reporting

index.html

@@ -110,7 +110,7 @@ <h2>Preview for branch <a href="fix/remove-old-unknown-flow-id-error">fix/remove
       <tr>
         <td><a href="fix/remove-old-unknown-flow-id-error/draft-ietf-avtcore-rtp-over-quic.html" class="html draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (HTML)">RTP over QUIC (RoQ)</a></td>
         <td><a href="fix/remove-old-unknown-flow-id-error/draft-ietf-avtcore-rtp-over-quic.txt" class="txt draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (Text)">plain text</a></td>
-        <td>same as main</td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://mengelbart.github.io/rtp-over-quic-draft/draft-ietf-avtcore-rtp-over-quic.txt&amp;url_2=https://mengelbart.github.io/rtp-over-quic-draft/fix/remove-old-unknown-flow-id-error/draft-ietf-avtcore-rtp-over-quic.txt" class="diff draft-ietf-avtcore-rtp-over-quic">diff with main</a></td>
       </tr>
     </table>
     <h2>Preview for branch <a href="fix/rt-non-rt">fix/rt-non-rt</a></h2>
@@ -198,7 +198,7 @@ <h2>Preview for branch <a href="fix/expectation-unmet">fix/expectation-unmet</a>
       <tr>
         <td><a href="fix/expectation-unmet/draft-ietf-avtcore-rtp-over-quic.html" class="html draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (HTML)">RTP over QUIC (RoQ)</a></td>
         <td><a href="fix/expectation-unmet/draft-ietf-avtcore-rtp-over-quic.txt" class="txt draft-ietf-avtcore-rtp-over-quic" title="RTP over QUIC (RoQ) (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://mengelbart.github.io/rtp-over-quic-draft/draft-ietf-avtcore-rtp-over-quic.txt&amp;url_2=https://mengelbart.github.io/rtp-over-quic-draft/fix/expectation-unmet/draft-ietf-avtcore-rtp-over-quic.txt" class="diff draft-ietf-avtcore-rtp-over-quic">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <h2>Preview for branch <a href="fix/future-work-intro">fix/future-work-intro</a></h2>