Skip to content

Commit

Permalink
Script updating gh-pages from 02fc457. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Apr 9, 2024
1 parent a45a814 commit dd8cc50
Show file tree
Hide file tree
Showing 2 changed files with 66 additions and 31 deletions.
69 changes: 46 additions & 23 deletions clarify-rtp/rtcp/draft-ietf-avtcore-rtp-over-quic.html
View file
Original file line number Diff line number Diff line change
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 @@ -2833,40 +2841,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 document 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>
<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 document 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 document 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
28 changes: 20 additions & 8 deletions clarify-rtp/rtcp/draft-ietf-avtcore-rtp-over-quic.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,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 @@ -1691,14 +1694,19 @@ 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 document 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

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 @@ -1716,17 +1724,21 @@ Table of Contents
For these reasons, publication of this document as a stable 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

0 comments on commit dd8cc50

Please sign in to comment.