-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Script updating gh-pages from 6858853. [ci skip]
- Loading branch information
ID Bot
committed
May 30, 2024
1 parent
3fb26a8
commit cc03349
Showing
2 changed files
with
35 additions
and
71 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1037,7 +1037,7 @@ | |
| </tr></thead> | ||
| <tfoot><tr> | ||
| <td class="left">Ott, et al.</td> | ||
| <td class="center">Expires 30 November 2024</td> | ||
| <td class="center">Expires 1 December 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-29" class="published">29 May 2024</time> | ||
| <time datetime="2024-05-30" class="published">30 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-30">30 November 2024</time></dd> | ||
| <dd class="expires"><time datetime="2024-12-01">1 December 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 30 November 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> | ||
| This Internet-Draft will expire on 1 December 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> | ||
| </section> | ||
| </div> | ||
| <div id="copyright"> | ||
|
|
@@ -2892,7 +2892,7 @@ <h3 id="name-future-work-resulting-from-"> | |
| <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.1-2.1"> | ||
| <p id="section-13.1-2.1.1">More guidance on transport for RTCP (for example, when to use QUIC streams vs. DATAGRAMs).<a href="#section-13.1-2.1.1" class="pilcrow">¶</a></p> | ||
| <p id="section-13.1-2.1.1">More guidance on transport for RTCP (for example, when to use QUIC streams vs. DATAGRAMs) including guidance on prioritization between streams and DATAGRAMs for the performance of RTCP.<a href="#section-13.1-2.1.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-13.1-2.2"> | ||
| <p id="section-13.1-2.2.1">More 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> | ||
|
|
@@ -2902,6 +2902,12 @@ <h3 id="name-future-work-resulting-from-"> | |
| </li> | ||
| <li class="normal" id="section-13.1-2.4"> | ||
| <p id="section-13.1-2.4.1">Possible guidance for connection sharing between real-time and non-real-time 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> | ||
| <li class="normal" id="section-13.1-2.5"> | ||
| <p id="section-13.1-2.5.1">Investigation of the effects of delaying or dropping DATAGRAMs due to congestion before they can be transmitted by the QUIC stack.<a href="#section-13.1-2.5.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-13.1-2.6"> | ||
| <p id="section-13.1-2.6.1">Implementation of translating middleboxes for translating between RoQ and RTP over UDP. As described in <a href="#topologies" class="auto internal xref">Section 3.3</a>, RoQ can be used to connect to some RTP middleboxes using some topologies, and these middleboxes might be connecting RoQ endpoints and non-RoQ endpoints, so will need to translate between RoQ and RTP over UDP.<a href="#section-13.1-2.6.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| </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> | ||
|
|
@@ -3008,47 +3014,18 @@ <h3 id="name-mengelbart-roq"> | |
| <dd class="break"></dd> | ||
| <dt id="section-14.1-3.5">Implementation Experience:</dt> | ||
| <dd style="margin-left: 1.5em" id="section-14.1-3.6"> | ||
| <p id="section-14.1-3.6.1">The implementer reports they have no experience with the following:<a href="#section-14.1-3.6.1" class="pilcrow">¶</a></p> | ||
| <p id="section-14.1-3.6.1">The implementer reports they have no experience with the topics discussed in | ||
| <a href="#futures" class="auto internal xref">Section 13</a>.<a href="#section-14.1-3.6.1" class="pilcrow">¶</a></p> | ||
| </dd> | ||
| <dd class="break"></dd> | ||
| </dl> | ||
| <ul class="normal"> | ||
| <li class="normal" id="section-14.1-4.1"> | ||
| <p id="section-14.1-4.1.1">Using RoQ with QUIC connections during path changes, whether due to QUIC | ||
| connection migration or use of the Multipath Extension for QUIC. As described | ||
| in <a href="#futures-new-ext" class="auto internal xref">Section 13.2</a>, we expect future work on this topic.<a href="#section-14.1-4.1.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-14.1-4.2"> | ||
| <p id="section-14.1-4.2.1">Influence of default priorities of QUIC implementations between streams and | ||
| DATAGRAMs on the performance of RTCP. As described in <a href="#futures-impl-deploy" class="auto internal xref">Section 13.1</a>, | ||
| we expect future work on this topic.<a href="#section-14.1-4.2.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-14.1-4.3"> | ||
| <p id="section-14.1-4.3.1">DATAGRAMs that are queued (and thus delayed) or dropped on expiration before | ||
| being transmitted due to congestion. As described in <a href="#futures-impl-deploy" class="auto internal xref">Section 13.1</a>, | ||
| we expect future work on this topic.<a href="#section-14.1-4.3.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-14.1-4.4"> | ||
| <p id="section-14.1-4.4.1">Translating between RoQ and RTP over UDP. As described in <a href="#topologies" class="auto internal xref">Section 3.3</a>, RoQ | ||
| can be used to connect to some RTP middleboxes using some topologies, and | ||
| these middleboxes might be connecting RoQ endpoints and non-RoQ endpoints, so | ||
| will need to translate between RoQ and RTP over UDP.<a href="#section-14.1-4.4.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| <li class="normal" id="section-14.1-4.5"> | ||
| <p id="section-14.1-4.5.1">Performance impacts of multiplexing many RTP sessions on a single QUIC | ||
| connection. As described in <a href="#futures-impl-deploy" class="auto internal xref">Section 13.1</a>, we expect future work on | ||
| this topic.<a href="#section-14.1-4.5.1" class="pilcrow">¶</a></p> | ||
| </li> | ||
| </ul> | ||
| <span class="break"></span><dl class="dlParallel" id="section-14.1-5"> | ||
| <dt id="section-14.1-5.1">Contact Information:</dt> | ||
| <dd style="margin-left: 1.5em" id="section-14.1-5.2"> | ||
| <p id="section-14.1-5.2.1">Mathis Engelbart ([email protected])<a href="#section-14.1-5.2.1" class="pilcrow">¶</a></p> | ||
| <dd class="break"></dd> | ||
| <dt id="section-14.1-3.7">Contact Information:</dt> | ||
| <dd style="margin-left: 1.5em" id="section-14.1-3.8"> | ||
| <p id="section-14.1-3.8.1">Mathis Engelbart ([email protected])<a href="#section-14.1-3.8.1" class="pilcrow">¶</a></p> | ||
| </dd> | ||
| <dd class="break"></dd> | ||
| <dt id="section-14.1-5.3">Last Updated:</dt> | ||
| <dd style="margin-left: 1.5em" id="section-14.1-5.4"> | ||
| <p id="section-14.1-5.4.1">25 May 2024<a href="#section-14.1-5.4.1" class="pilcrow">¶</a></p> | ||
| <dt id="section-14.1-3.9">Last Updated:</dt> | ||
| <dd style="margin-left: 1.5em" id="section-14.1-3.10"> | ||
| <p id="section-14.1-3.10.1">25 May 2024<a href="#section-14.1-3.10.1" class="pilcrow">¶</a></p> | ||
| </dd> | ||
| <dd class="break"></dd> | ||
| </dl> | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,9 +5,9 @@ | |
| Audio/Video Transport Core Maintenance J. Ott | ||
| Internet-Draft M. Engelbart | ||
| Intended status: Experimental Technical University Munich | ||
| Expires: 30 November 2024 S. Dawkins | ||
| Expires: 1 December 2024 S. Dawkins | ||
| Tencent America LLC | ||
| 29 May 2024 | ||
| 30 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 30 November 2024. | ||
| This Internet-Draft will expire on 1 December 2024. | ||
|
|
||
| Copyright Notice | ||
|
|
||
|
|
@@ -1786,7 +1786,8 @@ Table of Contents | |
| Possible directions would include | ||
|
|
||
| * More guidance on transport for RTCP (for example, when to use QUIC | ||
| streams vs. DATAGRAMs). | ||
| streams vs. DATAGRAMs) including guidance on prioritization | ||
| between streams and DATAGRAMs for the performance of RTCP. | ||
|
|
||
| * More guidance on the use of real-time-friendly congestion control | ||
| algorithms (for example, Copa [Copa], L4S [RFC9330], etc.). | ||
|
|
@@ -1799,6 +1800,15 @@ Table of Contents | |
| control and rate adaptation, scheduling, prioritization, and which | ||
| ALPNs to use. | ||
|
|
||
| * Investigation of the effects of delaying or dropping DATAGRAMs due | ||
| to congestion before they can be transmitted by the QUIC stack. | ||
|
|
||
| * Implementation of translating middleboxes for translating between | ||
| RoQ and RTP over UDP. As described in Section 3.3, RoQ can be | ||
| used to connect to some RTP middleboxes using some topologies, and | ||
| these middleboxes might be connecting RoQ endpoints and non-RoQ | ||
| endpoints, so will need to translate between RoQ and RTP over UDP. | ||
|
|
||
| For these reasons, publication of this document as a stable reference | ||
| for implementers to test with, and report results, seems useful. | ||
|
|
||
|
|
@@ -1885,30 +1895,7 @@ Table of Contents | |
| Licensing: MIT License | ||
|
|
||
| Implementation Experience: The implementer reports they have no | ||
| experience with the following: | ||
|
|
||
| * Using RoQ with QUIC connections during path changes, whether due | ||
| to QUIC connection migration or use of the Multipath Extension for | ||
| QUIC. As described in Section 13.2, we expect future work on this | ||
| topic. | ||
|
|
||
| * Influence of default priorities of QUIC implementations between | ||
| streams and DATAGRAMs on the performance of RTCP. As described in | ||
| Section 13.1, we expect future work on this topic. | ||
|
|
||
| * DATAGRAMs that are queued (and thus delayed) or dropped on | ||
| expiration before being transmitted due to congestion. As | ||
| described in Section 13.1, we expect future work on this topic. | ||
|
|
||
| * Translating between RoQ and RTP over UDP. As described in | ||
| Section 3.3, RoQ can be used to connect to some RTP middleboxes | ||
| using some topologies, and these middleboxes might be connecting | ||
| RoQ endpoints and non-RoQ endpoints, so will need to translate | ||
| between RoQ and RTP over UDP. | ||
|
|
||
| * Performance impacts of multiplexing many RTP sessions on a single | ||
| QUIC connection. As described in Section 13.1, we expect future | ||
| work on this topic. | ||
| experience with the topics discussed in Section 13. | ||
|
|
||
| Contact Information: Mathis Engelbart ([email protected]) | ||
|
|
||
|
|
||