From 20d81ab0b335ee4d0938da3a848a3dd31611654c Mon Sep 17 00:00:00 2001 From: ID Bot Date: Wed, 20 Sep 2023 08:26:48 +0000 Subject: [PATCH] Script updating gh-pages from 8c3af97. [ci skip] --- .../draft-ietf-avtcore-rtp-over-quic.html | 41 +- .../draft-ietf-avtcore-rtp-over-quic.txt | 417 +++++++++--------- 2 files changed, 233 insertions(+), 225 deletions(-) diff --git a/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.html b/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.html index 5e857c8..75fb82c 100644 --- a/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.html +++ b/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.html @@ -1059,7 +1059,7 @@ Ott, et al. -Expires 18 March 2024 +Expires 23 March 2024 [Page] @@ -1072,12 +1072,12 @@
draft-ietf-avtcore-rtp-over-quic-latest
Published:
- +
Intended Status:
Standards Track
Expires:
-
+
Authors:
@@ -1136,7 +1136,7 @@

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 18 March 2024.

+ This Internet-Draft will expire on 23 March 2024.

@@ -2687,9 +2687,9 @@

Generic Negative Acknowledgments (PT=205, FMT=1, Name=Generic NACK, [RFC4585]) contain information about RTP packets which the receiver considered lost. Section 6.2.1. of [RFC4585] recommends to use this feature -only, if the underlying protocol cannot provide similar feedback. QUIC does not +only if the underlying protocol cannot provide similar feedback. QUIC does not provide negative acknowledgments, but can detect lost packets based on the Gap -numbers contained in QUIC ACK frames Section 6 of [RFC9002].

+numbers contained in QUIC ACK frames (Section 6 of [RFC9002]).

@@ -3560,14 +3560,17 @@

This section lists all the RTCP packet types and RTP header extensions that were considered in the analysis described in Section 8.

+

Several but not all of these control packets and their attributes can be mapped +from QUIC, as described in Section 8.3. Mappable from QUIC +has one of three values: yes, partly, possibly, and no. Partly +is used for packet types for which some fields can be mapped from QUIC, but not +all. Possibly describes packet types which could be mapped with help from one +or more QUIC extensions.

B.1. RTCP Control Packet Types

-

Several but not all of these control packets and their attributes can be mapped -from QUIC, as described in Section 8.3. Mappable from QUIC -has one of three values: yes, QUIC extension required, and no.

@@ -3640,7 +3643,7 @@

- + @@ -3815,7 +3818,7 @@

- + @@ -4309,7 +4312,7 @@

- + @@ -4433,7 +4436,7 @@

- + diff --git a/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.txt b/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.txt index 25edd00..c92496f 100644 --- a/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.txt +++ b/fix/80-rtcp-tables-appendix/draft-ietf-avtcore-rtp-over-quic.txt @@ -5,9 +5,9 @@ Audio/Video Transport Core Maintenance J. Ott Internet-Draft M. Engelbart Intended status: Standards Track Technical University Munich -Expires: 18 March 2024 S. Dawkins +Expires: 23 March 2024 S. Dawkins Tencent America LLC - 15 September 2023 + 20 September 2023 RTP over QUIC (RoQ) @@ -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 18 March 2024. + This Internet-Draft will expire on 23 March 2024. Copyright Notice @@ -1361,12 +1361,12 @@ Table of Contents _Extended Reports_ (PT=207, Name=XR, [RFC3611]) offer an extensible framework for a variety of different control messages. Some of the - standard report blocks which can be implemented in extended reports - can be implemented in QUIC, too. Other report blocks need to be - evaluated individually, to determine whether if the contained - information can be transmitted using QUIC instead. Table 4 in - Appendix B.2 lists considerations for mapping QUIC feedback to some - of the _Extended Reports_. + statistics that are defined as extended report blocks can be derived + from QUIC, too. Other report blocks need to be evaluated + individually, to determine whether if the contained information can + be transmitted using QUIC instead. Table 4 in Appendix B.2 lists + considerations for mapping QUIC feedback to some of the _Extended + Reports_. 8.3.3. Mapping QUIC Feedback to Generic RTP Feedback ("RTPFB") @@ -1378,10 +1378,10 @@ Table of Contents Generic _Negative Acknowledgments_ (PT=205, FMT=1, Name=Generic NACK, [RFC4585]) contain information about RTP packets which the receiver considered lost. Section 6.2.1. of [RFC4585] recommends to use this - feature only, if the underlying protocol cannot provide similar + feature only if the underlying protocol cannot provide similar feedback. QUIC does not provide negative acknowledgments, but can detect lost packets based on the Gap numbers contained in QUIC ACK - frames Section 6 of [RFC9002]. + frames (Section 6 of [RFC9002]). 8.3.3.2. ECN Feedback ("ECN") @@ -2241,12 +2241,14 @@ Appendix B. Considered RTCP Packet Types and RTP Header Extensions extensions that were considered in the analysis described in Section 8. -B.1. RTCP Control Packet Types - Several but not all of these control packets and their attributes can be mapped from QUIC, as described in Section 8.3. _Mappable from - QUIC_ has one of three values: _yes_, _QUIC extension required_, and - _no_. + QUIC_ has one of three values: _yes_, _partly_, _possibly_, and _no_. + _Partly_ is used for packet types for which some fields can be mapped + from QUIC, but not all. _Possibly_ describes packet types which could + be mapped with help from one or more QUIC extensions. + +B.1. RTCP Control Packet Types +==============+==========+===+===========+==========+==============+ | Name | Shortcut |PT | Defining | Mappable | Comments | @@ -2278,7 +2280,7 @@ B.1. RTCP Control Packet Types | Source | SDES |202| [RFC3550] | no | | | description | | | | | | +--------------+----------+---+-----------+----------+--------------+ - | Goodbye | BYE |203| [RFC3550] | possibly | see Section | + | Goodbye | BYE |203| [RFC3550] | partly | see Section | | | | | | | 8.3.4 | +--------------+----------+---+-----------+----------+--------------+ | Application- | APP |204| [RFC3550] | no | | @@ -2322,171 +2324,170 @@ B.1. RTCP Control Packet Types B.2. Extended Reports (XR) - +===============+==========+========+==================================+ - |Name |Document |Mappable|Comments | - | | |from | | - | | |QUIC | | - +===============+==========+========+==================================+ - |Loss RLE Report|[RFC3611] |yes |If only used for acknowledgment, | - |Block | | |could be replaced by QUIC | - | | | |acknowledgments, see Section 8.1 | - | | | |and Section 8.2 | - +---------------+----------+--------+----------------------------------+ - |Duplicate RLE |[RFC3611] |no | | - |Report Block | | | | - +---------------+----------+--------+----------------------------------+ - |Packet Receipt |[RFC3611] |possibly|QUIC could provide packet receive | - |Times Report | | |timestamps when using a timestamp | - |Block | | |extension that reports timestamp | - | | | |for every received packet, such as| - | | | |[I-D.draft-smith-quic-receive-ts].| - | | | |However, QUIC does not provide | - | | | |feedback in RTP timestamp format. | - +---------------+----------+--------+----------------------------------+ - |Receiver |[RFC3611] |possibly|Used together with DLRR Report | - |Reference Time | | |Blocks to calculate RTTs of non- | - |Report Block | | |senders. RTT measurements can | - | | | |natively be provided by QUIC. | - +---------------+----------+--------+----------------------------------+ - |DLRR Report |[RFC3611] |possibly|Used together with Receiver | - |Block | | |Reference Time Report Blocks to | - | | | |calculate RTTs of non-senders. | - | | | |RTT can natively be provided by | - | | | |QUIC natively. | - +---------------+----------+--------+----------------------------------+ - |Statistics |[RFC3611] |partly |Packet loss and jitter can be | - |Summary Report | | |inferred from QUIC | - |Block | | |acknowledgments, if a timestamp | - | | | |extension is used (see | - | | | |[I-D.draft-smith-quic-receive-ts] | - | | | |or [I-D.draft-huitema-quic-ts]). | - | | | |The remaining fields cannot be | - | | | |mapped to QUIC. | - +---------------+----------+--------+----------------------------------+ - |VoIP Metrics |[RFC3611] |no |as in other reports above, only | - |Report Block | | |loss and RTT available | - +---------------+----------+--------+----------------------------------+ - |RTCP XR |[RFC5093] |no | | - +---------------+----------+--------+----------------------------------+ - |Texas | | | | - |Instruments | | | | - |Extended VoIP | | | | - |Quality Block | | | | - +---------------+----------+--------+----------------------------------+ - |Post-repair |[RFC5725] |no | | - |Loss RLE Report| | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Multicast |[RFC6332] |no | | - |Acquisition | | | | - |Report Block | | | | - +---------------+----------+--------+----------------------------------+ - |IDMS Report |[RFC7272] |no | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |ECN Summary |[RFC6679] |partly |see Section 8.3.3.2 | - |Report | | | | - +---------------+----------+--------+----------------------------------+ - |Measurement |[RFC6776] |no | | - |Information | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Packet Delay |[RFC6798] |no |QUIC timestamps may be used to | - |Variation | | |achieve the same goal? | - |Metrics Block | | | | - +---------------+----------+--------+----------------------------------+ - |Delay Metrics |[RFC6843] |no |QUIC has RTT and can provide | - |Block | | |timestamps for one-way delay, but | - | | | |no way of informing peers about | - | | | |end-to-end statistics when QUIC is| - | | | |only used on one segment of the | - | | | |path. | - +---------------+----------+--------+----------------------------------+ - |Burst/Gap Loss |[RFC7004] | |QUIC ACKs? | - |Summary | | | | - |Statistics | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Burst/Gap |[RFC7004] |no | | - |Discard Summary| | | | - |Statistics | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Frame |[RFC7004] |no | | - |Impairment | | | | - |Statistics | | | | - |Summary | | | | - +---------------+----------+--------+----------------------------------+ - |Burst/Gap Loss |[RFC6958] | |QUIC ACKs? | - |Metrics Block | | | | - +---------------+----------+--------+----------------------------------+ - |Burst/Gap |[RFC7003] |no | | - |Discard Metrics| | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |MPEG2 Transport|[RFC6990] |no | | - |Stream PSI- | | | | - |Independent | | | | - |Decodability | | | | - |Statistics | | | | - |Metrics Block | | | | - +---------------+----------+--------+----------------------------------+ - |De-Jitter |[RFC7005] |no | | - |Buffer Metrics | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Discard Count |[RFC7002] |no | | - |Metrics Block | | | | - +---------------+----------+--------+----------------------------------+ - |DRLE (Discard |[RFC7097] |no | | - |RLE Report) | | | | - +---------------+----------+--------+----------------------------------+ - |BDR (Bytes |[RFC7243] |no | | - |Discarded | | | | - |Report) | | | | - +---------------+----------+--------+----------------------------------+ - |RFISD (RTP |[RFC7244] |no | | - |Flows Initial | | | | - |Synchronization| | | | - |Delay) | | | | - +---------------+----------+--------+----------------------------------+ - |RFSO (RTP Flows|[RFC7244] |no | | - |Synchronization| | | | - |Offset Metrics | | | | - |Block) | | | | - +---------------+----------+--------+----------------------------------+ - |MOS Metrics |[RFC7266] |no | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |LCB (Loss |[RFC7294],|no | | - |Concealment |Section | | | - |Metrics Block) |4.1 | | | - +---------------+----------+--------+----------------------------------+ - |CSB (Concealed |[RFC7294],|no | | - |Seconds Metrics|Section | | | - |Block) |4.1 | | | - +---------------+----------+--------+----------------------------------+ - |MPEG2 Transport|[RFC7380] |no | | - |Stream PSI | | | | - |Decodability | | | | - |Statistics | | | | - |Metrics Block | | | | - +---------------+----------+--------+----------------------------------+ - |Post-Repair |[RFC7509] |no | | - |Loss Count | | | | - |Metrics Report | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Video Loss |[RFC7867] |no | | - |Concealment | | | | - |Metric Report | | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ - |Independent |[RFC8015] |no | | - |Burst/Gap | | | | - |Discard Metrics| | | | - |Block | | | | - +---------------+----------+--------+----------------------------------+ + +===============+==========+=========+==================================+ + |Name |Document |Mappable |Comments | + | | |from QUIC| | + +===============+==========+=========+==================================+ + |Loss RLE Report|[RFC3611] |yes |If only used for acknowledgment, | + |Block | | |could be replaced by QUIC | + | | | |acknowledgments, see Section 8.1 | + | | | |and Section 8.2 | + +---------------+----------+---------+----------------------------------+ + |Duplicate RLE |[RFC3611] |no | | + |Report Block | | | | + +---------------+----------+---------+----------------------------------+ + |Packet Receipt |[RFC3611] |possibly |QUIC could provide packet receive | + |Times Report | | |timestamps when using a timestamp | + |Block | | |extension that reports timestamp | + | | | |for every received packet, such as| + | | | |[I-D.draft-smith-quic-receive-ts].| + | | | |However, QUIC does not provide | + | | | |feedback in RTP timestamp format. | + +---------------+----------+---------+----------------------------------+ + |Receiver |[RFC3611] |possibly |Used together with DLRR Report | + |Reference Time | | |Blocks to calculate RTTs of non- | + |Report Block | | |senders. RTT measurements can | + | | | |natively be provided by QUIC. | + +---------------+----------+---------+----------------------------------+ + |DLRR Report |[RFC3611] |possibly |Used together with Receiver | + |Block | | |Reference Time Report Blocks to | + | | | |calculate RTTs of non-senders. | + | | | |RTT can natively be provided by | + | | | |QUIC natively. | + +---------------+----------+---------+----------------------------------+ + |Statistics |[RFC3611] |possibly/|Packet loss and jitter can be | + |Summary Report | |partly |inferred from QUIC | + |Block | | |acknowledgments, if a timestamp | + | | | |extension is used (see | + | | | |[I-D.draft-smith-quic-receive-ts] | + | | | |or [I-D.draft-huitema-quic-ts]). | + | | | |The remaining fields cannot be | + | | | |mapped to QUIC. | + +---------------+----------+---------+----------------------------------+ + |VoIP Metrics |[RFC3611] |no |as in other reports above, only | + |Report Block | | |loss and RTT available | + +---------------+----------+---------+----------------------------------+ + |RTCP XR |[RFC5093] |no | | + +---------------+----------+---------+----------------------------------+ + |Texas | | | | + |Instruments | | | | + |Extended VoIP | | | | + |Quality Block | | | | + +---------------+----------+---------+----------------------------------+ + |Post-repair |[RFC5725] |no | | + |Loss RLE Report| | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Multicast |[RFC6332] |no | | + |Acquisition | | | | + |Report Block | | | | + +---------------+----------+---------+----------------------------------+ + |IDMS Report |[RFC7272] |no | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |ECN Summary |[RFC6679] |partly |see Section 8.3.3.2 | + |Report | | | | + +---------------+----------+---------+----------------------------------+ + |Measurement |[RFC6776] |no | | + |Information | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Packet Delay |[RFC6798] |no |QUIC timestamps may be used to | + |Variation | | |achieve the same goal? | + |Metrics Block | | | | + +---------------+----------+---------+----------------------------------+ + |Delay Metrics |[RFC6843] |no |QUIC has RTT and can provide | + |Block | | |timestamps for one-way delay, but | + | | | |no way of informing peers about | + | | | |end-to-end statistics when QUIC is| + | | | |only used on one segment of the | + | | | |path. | + +---------------+----------+---------+----------------------------------+ + |Burst/Gap Loss |[RFC7004] | |QUIC ACKs? | + |Summary | | | | + |Statistics | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Burst/Gap |[RFC7004] |no | | + |Discard Summary| | | | + |Statistics | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Frame |[RFC7004] |no | | + |Impairment | | | | + |Statistics | | | | + |Summary | | | | + +---------------+----------+---------+----------------------------------+ + |Burst/Gap Loss |[RFC6958] | |QUIC ACKs? | + |Metrics Block | | | | + +---------------+----------+---------+----------------------------------+ + |Burst/Gap |[RFC7003] |no | | + |Discard Metrics| | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |MPEG2 Transport|[RFC6990] |no | | + |Stream PSI- | | | | + |Independent | | | | + |Decodability | | | | + |Statistics | | | | + |Metrics Block | | | | + +---------------+----------+---------+----------------------------------+ + |De-Jitter |[RFC7005] |no | | + |Buffer Metrics | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Discard Count |[RFC7002] |no | | + |Metrics Block | | | | + +---------------+----------+---------+----------------------------------+ + |DRLE (Discard |[RFC7097] |no | | + |RLE Report) | | | | + +---------------+----------+---------+----------------------------------+ + |BDR (Bytes |[RFC7243] |no | | + |Discarded | | | | + |Report) | | | | + +---------------+----------+---------+----------------------------------+ + |RFISD (RTP |[RFC7244] |no | | + |Flows Initial | | | | + |Synchronization| | | | + |Delay) | | | | + +---------------+----------+---------+----------------------------------+ + |RFSO (RTP Flows|[RFC7244] |no | | + |Synchronization| | | | + |Offset Metrics | | | | + |Block) | | | | + +---------------+----------+---------+----------------------------------+ + |MOS Metrics |[RFC7266] |no | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |LCB (Loss |[RFC7294],|no | | + |Concealment |Section | | | + |Metrics Block) |4.1 | | | + +---------------+----------+---------+----------------------------------+ + |CSB (Concealed |[RFC7294],|no | | + |Seconds Metrics|Section | | | + |Block) |4.1 | | | + +---------------+----------+---------+----------------------------------+ + |MPEG2 Transport|[RFC7380] |no | | + |Stream PSI | | | | + |Decodability | | | | + |Statistics | | | | + |Metrics Block | | | | + +---------------+----------+---------+----------------------------------+ + |Post-Repair |[RFC7509] |no | | + |Loss Count | | | | + |Metrics Report | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Video Loss |[RFC7867] |no | | + |Concealment | | | | + |Metric Report | | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ + |Independent |[RFC8015] |no | | + |Burst/Gap | | | | + |Discard Metrics| | | | + |Block | | | | + +---------------+----------+---------+----------------------------------+ Table 4: Extended Report Blocks @@ -2626,7 +2627,8 @@ B.5. RTP Header extensions B.5.1. Compact Header Extensions +====================+================+=================+===========+ - |Extension URI |Description |Reference |QUIC | + |Extension URI |Description |Reference |Mappable | + | | | |from QUIC | +====================+================+=================+===========+ |urn:ietf:params:rtp-|Transmission |[RFC5450] |no | |hdrext:toffset |Time offsets | | | @@ -2710,30 +2712,33 @@ B.5.1. Compact Header Extensions B.5.2. SDES Compact Header Extensions - +=======================+=====================+===========+======+ - | Extension URI | Description | Reference | QUIC | - +=======================+=====================+===========+======+ - | urn:ietf:params:rtp- | Source Description: | [RFC7941] | no | - | hdrext:sdes:cname | Canonical End-Point | | | - | | Identifier (SDES | | | - | | CNAME) | | | - +-----------------------+---------------------+-----------+------+ - | urn:ietf:params:rtp- | RTP Stream | [RFC8852] | no | - | hdrext:sdes:rtp- | Identifier | | | - | stream-id | | | | - +-----------------------+---------------------+-----------+------+ - | urn:ietf:params:rtp- | RTP Repaired Stream | [RFC8852] | no | - | hdrext:sdes:repaired- | Identifier | | | - | rtp-stream-id | | | | - +-----------------------+---------------------+-----------+------+ - | urn:ietf:params:rtp- | CLUE CaptId | [RFC8849] | no | - | hdrext:sdes:CaptId | | | | - +-----------------------+---------------------+-----------+------+ - | urn:ietf:params:rtp- | Media | [RFC9143] | no | - | hdrext:sdes:mid | identification | | | - +-----------------------+---------------------+-----------+------+ - - Table 8 + +=======================+==================+===========+==========+ + | Extension URI | Description | Reference | Mappable | + | | | | from | + | | | | QUIC | + +=======================+==================+===========+==========+ + | urn:ietf:params:rtp- | Source | [RFC7941] | no | + | hdrext:sdes:cname | Description: | | | + | | Canonical End- | | | + | | Point Identifier | | | + | | (SDES CNAME) | | | + +-----------------------+------------------+-----------+----------+ + | urn:ietf:params:rtp- | RTP Stream | [RFC8852] | no | + | hdrext:sdes:rtp- | Identifier | | | + | stream-id | | | | + +-----------------------+------------------+-----------+----------+ + | urn:ietf:params:rtp- | RTP Repaired | [RFC8852] | no | + | hdrext:sdes:repaired- | Stream | | | + | rtp-stream-id | Identifier | | | + +-----------------------+------------------+-----------+----------+ + | urn:ietf:params:rtp- | CLUE CaptId | [RFC8849] | no | + | hdrext:sdes:CaptId | | | | + +-----------------------+------------------+-----------+----------+ + | urn:ietf:params:rtp- | Media | [RFC9143] | no | + | hdrext:sdes:mid | identification | | | + +-----------------------+------------------+-----------+----------+ + + Table 8 Appendix C. Experimental Results
Table 3
[RFC3550] possiblypartly see Section 8.3.4
[RFC3611] partlypossibly/partly Packet loss and jitter can be inferred from QUIC acknowledgments, if a timestamp extension is used (see [I-D.draft-smith-quic-receive-ts] or [I-D.draft-huitema-quic-ts]). The remaining fields cannot be mapped to QUIC.
Extension URI Description ReferenceQUICMappable from QUIC
Extension URI Description ReferenceQUICMappable from QUIC