Skip to content

Commit fb9c93a

Browse files
committed
Section 3.2.1: Clarify Game streaming requirements
Partial fixes for w3c#103 Updated requiements by the feedbacks frome the First December WebRTC WG Virtual Interim (12-05-2023)
1 parent 3ca2396 commit fb9c93a

File tree

1 file changed

+31
-1
lines changed

1 file changed

+31
-1
lines changed

index.html

+31-1
Original file line numberDiff line numberDiff line change
@@ -299,6 +299,21 @@ <h4>Game streaming</h4>
299299
delay. This requirement is addressed by jitterBufferTarget, defined in
300300
[[?WebRTC-Extensions]] Section 6.</td>
301301
</tr>
302+
<tr>
303+
<td>N48</td>
304+
<td>The application must be able to control video decoding to continue even
305+
after a frame-loss without waiting for a key frame. This helps the application recover
306+
faster from lossy network conditions.</td>
307+
</tr>
308+
<td>N49</td>
309+
<td>To adapt the video quality to the varying network and maintain consistent latency,
310+
the application needs to configure the TWCC (Transport-wide Congestion Control)
311+
RTCP feedback transmission interval. (TWCC RTCP feedback currently provides
312+
the packet loss information, but there are no knobs to configure its period.
313+
Moreover, TWCC-02 does not meet the requirement, because it relies on the sender’s request,
314+
which adds header overhead and is susceptible to sender packet loss and jitter.)</td>
315+
<tr>
316+
</tr>
302317
</tbody>
303318
</table>
304319
<p>Experience: Microsoft's Xbox Cloud Gaming and NVIDIA's GeForce NOW are examples of this use case, with media
@@ -1071,9 +1086,24 @@ <h3>Requirements Summary</h3>
10711086
<td>The WebRTC connection can generate signals indicating demands
10721087
for keyframes, and surface those to the application.</td>
10731088
</tr>
1089+
<tr id="N48">
1090+
<td>N48</td>
1091+
<td>The application must be able to control video decoding to continue even
1092+
after a frame-loss without waiting for a key frame. This helps the application
1093+
recover faster from lossy network conditions.</td>
1094+
</tr>
1095+
<tr id="N49">
1096+
<td>N49</td>
1097+
<td>To adapt the video quality to the varying network and maintain consistent latency,
1098+
the application needs to configure the TWCC (Transport-wide Congestion Control)
1099+
RTCP feedback transmission interval. (TWCC RTCP feedback currently provides
1100+
the packet loss information, but there are no knobs to configure its period.
1101+
Moreover, TWCC-02 does not meet the requirement, because it relies on the sender’s request,
1102+
which adds header overhead and is susceptible to sender packet loss and jitter.)</td>
1103+
</tr>
10741104
</tbody>
10751105
</table>
1076-
<p class="note">Requirements N40-N47 have unresolved comments from a Call for Consensus (CfC).</p>
1106+
<p class="note">Requirements N40-N49 have unresolved comments from a Call for Consensus (CfC).</p>
10771107
</section>
10781108
</body>
10791109
</html>

0 commit comments

Comments
 (0)