Skip to content

Commit

Permalink
Script updating gh-pages from bb1cc4b. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Apr 9, 2024
1 parent 29deb26 commit eef2f0c
Show file tree
Hide file tree
Showing 9 changed files with 124 additions and 15,616 deletions.
4,613 changes: 0 additions & 4,613 deletions draft-ietf-avtcore-rtp-over-quic-09/draft-ietf-avtcore-rtp-over-quic.html
View file

This file was deleted.

3,023 changes: 0 additions & 3,023 deletions draft-ietf-avtcore-rtp-over-quic-09/draft-ietf-avtcore-rtp-over-quic.txt
View file

This file was deleted.

45 changes: 0 additions & 45 deletions draft-ietf-avtcore-rtp-over-quic-09/index.html
View file

This file was deleted.

83 changes: 53 additions & 30 deletions draft-ietf-avtcore-rtp-over-quic.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1033,11 +1033,11 @@
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">RTP over QUIC (RoQ)</td>
<td class="right">March 2024</td>
<td class="right">April 2024</td>
</tr></thead>
<tfoot><tr>
<td class="left">Ott, et al.</td>
<td class="center">Expires 19 September 2024</td>
<td class="center">Expires 11 October 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -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-03-18" class="published">18 March 2024</time>
<time datetime="2024-04-09" class="published">9 April 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-09-19">19 September 2024</time></dd>
<dd class="expires"><time datetime="2024-10-11">11 October 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -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 19 September 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 11 October 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1307,7 +1307,15 @@ <h2 id="name-copyright-notice">
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
<p id="section-toc.1-1.13.1"><a href="#section-13" class="auto internal xref">13</a>. <a href="#name-directions-for-future-work" class="internal xref">Directions for Future work</a></p>
<p id="section-toc.1-1.13.1"><a href="#section-13" class="auto internal xref">13</a>. <a href="#name-directions-for-future-work" class="internal xref">Directions for Future Work</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.1">
<p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="auto internal xref">13.1</a>.  <a href="#name-future-work-resulting-from-" class="internal xref">Future Work Resulting from Implementation and Deployment Experience</a></p>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.2">
<p id="section-toc.1-1.13.2.2.1"><a href="#section-13.2" class="auto internal xref">13.2</a>.  <a href="#name-future-work-resulting-from-n" class="internal xref">Future Work Resulting from New QUIC Extensions</a></p>
</li>
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
<p id="section-toc.1-1.14.1"><a href="#section-14" class="auto internal xref">14</a>. <a href="#name-security-considerations" class="internal xref">Security Considerations</a></p>
Expand Down Expand Up @@ -2832,40 +2840,55 @@ <h3 id="name-coalescing-rtp-packets-in-a">
<div id="futures">
<section id="section-13">
<h2 id="name-directions-for-future-work">
<a href="#section-13" class="section-number selfRef">13. </a><a href="#name-directions-for-future-work" class="section-name selfRef">Directions for Future work</a>
<a href="#section-13" class="section-number selfRef">13. </a><a href="#name-directions-for-future-work" class="section-name selfRef">Directions for Future Work</a>
</h2>
<p id="section-13-1">This specification represents considerable work and discussion within the IETF, and describes RoQ in sufficient detail that an implementer can build a RoQ application, but we recognize that additional work is likely, after we have sufficient experience with RoQ to guide that work. Possible directions would include<a href="#section-13-1" class="pilcrow"></a></p>
<p id="section-13-1">This specification represents considerable work and discussion within the IETF, and describes RoQ in sufficient detail that an implementer can build a RoQ application, but we recognize that additional work is likely, after we have sufficient experience with RoQ to guide that work.<a href="#section-13-1" class="pilcrow"></a></p>
<div id="futures-impl-deploy">
<section id="section-13.1">
<h3 id="name-future-work-resulting-from-">
<a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-future-work-resulting-from-" class="section-name selfRef">Future Work Resulting from Implementation and Deployment Experience</a>
</h3>
<p id="section-13.1-1">Possible directions would include<a href="#section-13.1-1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-13-2.1">
<p id="section-13-2.1.1">Better guidance on transport for RTCP (for example, when to use QUIC streams vs. QUIC datagrams).<a href="#section-13-2.1.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.1-2.1">
<p id="section-13.1-2.1.1">Better guidance on transport for RTCP (for example, when to use QUIC streams vs. QUIC datagrams).<a href="#section-13.1-2.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-2.2">
<p id="section-13-2.2.1">Better guidance on the use of real-time-friendly congestion control algorithms (for example, Copa <span>[<a href="#Copa" class="cite xref">Copa</a>]</span>, L4S <span>[<a href="#RFC9330" class="cite xref">RFC9330</a>]</span>, etc.).<a href="#section-13-2.2.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.1-2.2">
<p id="section-13.1-2.2.1">Better guidance on the use of real-time-friendly congestion control algorithms (for example, Copa <span>[<a href="#Copa" class="cite xref">Copa</a>]</span>, L4S <span>[<a href="#RFC9330" class="cite xref">RFC9330</a>]</span>, etc.).<a href="#section-13.1-2.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-2.3">
<p id="section-13-2.3.1">Better guidance for congestion control and rate adaptation for multiple RoQ flows (whether streams or datagrams).<a href="#section-13-2.3.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.1-2.3">
<p id="section-13.1-2.3.1">Better guidance for congestion control and rate adaptation for multiple RoQ flows (whether streams or datagrams).<a href="#section-13.1-2.3.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-2.4">
<p id="section-13-2.4.1">Possible guidance for connection sharing between RoQ and non-RoQ flows, including considerations for congestion control and rate adaptation, scheduling, prioritization, and which ALPNs to use.<a href="#section-13-2.4.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.1-2.4">
<p id="section-13.1-2.4.1">Possible guidance for connection sharing between RoQ and non-RoQ flows, including considerations for congestion control and rate adaptation, scheduling, prioritization, and which ALPNs to use.<a href="#section-13.1-2.4.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-13-3">For these reasons, publication of this specification as a stable reference for implementers to test with, and report results, seems useful.<a href="#section-13-3" class="pilcrow"></a></p>
<p id="section-13-4">In addition, as noted in <a href="#new-quic" class="auto internal xref">Section 3.1.7</a>, one of the motivations for using QUIC as a transport for RTP is to exploit new QUIC extensions as they become available. We noted several proposed QUIC extensions in <a href="#optional-extensions" class="auto internal xref">Appendix A</a>, but these proposals are all solving relevant problems, and those problems are worthy of attention, no matter how they are solved for the QUIC protocol.<a href="#section-13-4" class="pilcrow"></a></p>
</ul>
<p id="section-13.1-3">For these reasons, publication of this specification as a stable reference for implementers to test with, and report results, seems useful.<a href="#section-13.1-3" class="pilcrow"></a></p>
</section>
</div>
<div id="futures-new-ext">
<section id="section-13.2">
<h3 id="name-future-work-resulting-from-n">
<a href="#section-13.2" class="section-number selfRef">13.2. </a><a href="#name-future-work-resulting-from-n" class="section-name selfRef">Future Work Resulting from New QUIC Extensions</a>
</h3>
<p id="section-13.2-1">In addition, as noted in <a href="#new-quic" class="auto internal xref">Section 3.1.7</a>, one of the motivations for using QUIC as a transport for RTP is to exploit new QUIC extensions as they become available. We noted several specific proposed QUIC extensions in <a href="#optional-extensions" class="auto internal xref">Appendix A</a>, but these proposals are all solving relevant problems, and those problems are worthy of attention, no matter how they are solved for the QUIC protocol.<a href="#section-13.2-1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-13-5.1">
<p id="section-13-5.1.1">Guidance for using RoQ with QUIC connection migration and over multiple paths. We note that the Multipath Extension for QUIC <span>[<a href="#I-D.draft-ietf-quic-multipath" class="cite xref">I-D.draft-ietf-quic-multipath</a>]</span> has been adopted and is relatively mature.<a href="#section-13-5.1.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.2-2.1">
<p id="section-13.2-2.1.1">Guidance for using RoQ with QUIC connection migration and over multiple paths. QUIC connection migration was already defined in <span>[<a href="#RFC9000" class="cite xref">RFC9000</a>]</span>, and the Multipath Extension for QUIC <span>[<a href="#I-D.draft-ietf-quic-multipath" class="cite xref">I-D.draft-ietf-quic-multipath</a>]</span> has been adopted and is relatively mature, so this is likely to be the first new QUIC extension we address.<a href="#section-13.2-2.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-5.2">
<p id="section-13-5.2.1">Guidance for using RoQ with QUIC NAT traversal solutions. This could use Interactive Connectivity Establishment (ICE) <span>[<a href="#RFC8445" class="cite xref">RFC8445</a>]</span> or other NAT traversal solutions.<a href="#section-13-5.2.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.2-2.2">
<p id="section-13.2-2.2.1">Guidance for using RoQ with QUIC NAT traversal solutions. This could use Interactive Connectivity Establishment (ICE) <span>[<a href="#RFC8445" class="cite xref">RFC8445</a>]</span> or other NAT traversal solutions.<a href="#section-13.2-2.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-5.3">
<p id="section-13-5.3.1">Guidance for improved jitter calculations to use with congestion control and rate adaptation.<a href="#section-13-5.3.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.2-2.3">
<p id="section-13.2-2.3.1">Guidance for improved jitter calculations to use with congestion control and rate adaptation.<a href="#section-13.2-2.3.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-13-5.4">
<p id="section-13-5.4.1">Guidance for other aspects of QUIC performance optimization relying on extensions.<a href="#section-13-5.4.1" class="pilcrow"></a></p>
<li class="normal" id="section-13.2-2.4">
<p id="section-13.2-2.4.1">Guidance for other aspects of QUIC performance optimization relying on extensions.<a href="#section-13.2-2.4.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-13-6">Other QUIC extensions, not yet proposed, may also be useful with RoQ.<a href="#section-13-6" class="pilcrow"></a></p>
</ul>
<p id="section-13.2-3">Other QUIC extensions, not yet proposed, may also be useful with RoQ.<a href="#section-13.2-3" class="pilcrow"></a></p>
</section>
</div>
</section>
</div>
<div id="sec-considerations">
Expand Down Expand Up @@ -3172,7 +3195,7 @@ <h3 id="name-informative-references">
<dd class="break"></dd>
<dt id="I-D.draft-ietf-avtcore-rtcp-green-metadata">[I-D.draft-ietf-avtcore-rtcp-green-metadata]</dt>
<dd>
<span class="refAuthor">He, Y.</span>, <span class="refAuthor">Herglotz, C.</span>, and <span class="refAuthor">E. Francois</span>, <span class="refTitle">"RTP Control Protocol (RTCP) Messages for Temporal-Spatial Resolution"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-avtcore-rtcp-green-metadata-02</span>, <time datetime="2023-10-12" class="refDate">12 October 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtcp-green-metadata-02">https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtcp-green-metadata-02</a>&gt;</span>. </dd>
<span class="refAuthor">He, Y.</span>, <span class="refAuthor">Herglotz, C.</span>, and <span class="refAuthor">E. Francois</span>, <span class="refTitle">"RTP Control Protocol (RTCP) Messages for Temporal-Spatial Resolution"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-avtcore-rtcp-green-metadata-03</span>, <time datetime="2024-04-08" class="refDate">8 April 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtcp-green-metadata-03">https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtcp-green-metadata-03</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.draft-ietf-avtext-lrr-07">[I-D.draft-ietf-avtext-lrr-07]</dt>
<dd>
Expand Down
40 changes: 26 additions & 14 deletions draft-ietf-avtcore-rtp-over-quic.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@
Audio/Video Transport Core Maintenance J. Ott
Internet-Draft M. Engelbart
Intended status: Experimental Technical University Munich
Expires: 19 September 2024 S. Dawkins
Expires: 11 October 2024 S. Dawkins
Tencent America LLC
18 March 2024
9 April 2024


RTP over QUIC (RoQ)
Expand Down Expand Up @@ -49,7 +49,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 19 September 2024.
This Internet-Draft will expire on 11 October 2024.

Copyright Notice

Expand Down Expand Up @@ -118,7 +118,10 @@ Table of Contents
12.2.2. Effect of 0-RTT Replay Attacks for RoQ using Early
Data
12.3. Coalescing RTP packets in a single QUIC packet
13. Directions for Future work
13. Directions for Future Work
13.1. Future Work Resulting from Implementation and Deployment
Experience
13.2. Future Work Resulting from New QUIC Extensions
14. Security Considerations
15. IANA Considerations
15.1. Registration of a RoQ Identification String
Expand Down Expand Up @@ -1686,13 +1689,18 @@ Table of Contents
Application designers are advised to take these considerations into
account when selecting and configuring a QUIC stack for use with RoQ.

13. Directions for Future work
13. Directions for Future Work

This specification represents considerable work and discussion within
the IETF, and describes RoQ in sufficient detail that an implementer
can build a RoQ application, but we recognize that additional work is
likely, after we have sufficient experience with RoQ to guide that
work. Possible directions would include
work.

13.1. Future Work Resulting from Implementation and Deployment
Experience

Possible directions would include

* Better guidance on transport for RTCP (for example, when to use
QUIC streams vs. QUIC datagrams).
Expand All @@ -1712,17 +1720,21 @@ Table of Contents
reference for implementers to test with, and report results, seems
useful.

13.2. Future Work Resulting from New QUIC Extensions

In addition, as noted in Section 3.1.7, one of the motivations for
using QUIC as a transport for RTP is to exploit new QUIC extensions
as they become available. We noted several proposed QUIC extensions
in Appendix A, but these proposals are all solving relevant problems,
and those problems are worthy of attention, no matter how they are
solved for the QUIC protocol.
as they become available. We noted several specific proposed QUIC
extensions in Appendix A, but these proposals are all solving
relevant problems, and those problems are worthy of attention, no
matter how they are solved for the QUIC protocol.

* Guidance for using RoQ with QUIC connection migration and over
multiple paths. We note that the Multipath Extension for QUIC
multiple paths. QUIC connection migration was already defined in
[RFC9000], and the Multipath Extension for QUIC
[I-D.draft-ietf-quic-multipath] has been adopted and is relatively
mature.
mature, so this is likely to be the first new QUIC extension we
address.

* Guidance for using RoQ with QUIC NAT traversal solutions. This
could use Interactive Connectivity Establishment (ICE) [RFC8445]
Expand Down Expand Up @@ -1984,9 +1996,9 @@ Table of Contents
He, Y., Herglotz, C., and E. Francois, "RTP Control
Protocol (RTCP) Messages for Temporal-Spatial Resolution",
Work in Progress, Internet-Draft, draft-ietf-avtcore-rtcp-
green-metadata-02, 12 October 2023,
green-metadata-03, 8 April 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-
rtcp-green-metadata-02>.
rtcp-green-metadata-03>.

[I-D.draft-ietf-avtext-lrr-07]
Lennox, J., Hong, D., Uberti, J., Holmer, S., and M.
Expand Down
Loading

0 comments on commit eef2f0c

Please sign in to comment.