From 27a6edda343a4e4ed9b966cb8ff168a58545395a Mon Sep 17 00:00:00 2001
From: Sun Shin <sushin@nvidia.com>
Date: Fri, 14 Jul 2023 22:54:15 -0700
Subject: [PATCH] Section 3.2.1: Clarify Game streaming requirements

Partial fixes for #103
---
 index.html | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 51 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 3dc2f0b..a29e787 100644
--- a/index.html
+++ b/index.html
@@ -298,6 +298,31 @@ <h4>Game streaming</h4>
            delay. This requirement is addressed by jitterBufferTarget, defined in
            [[?WebRTC-Extensions]] Section 6.</td>
         </tr>
+        <tr>
+           <td>N48</td>
+           <td>The application must be able to control video decoding to continue even
+           after a frame-loss without waiting for a key frame. This helps the application recover
+           faster from lossy network conditions.</td>
+	</tr>
+        <tr>
+           <td>N49</td>
+           <td>The application must be able to generate signals that indicate to the encoder
+           the loss of encoder-decoder synchronicity (DPB buffers) and the sequence
+           of frame loss using the platform-agnostic protocols. This helps the application recover
+           faster from lossy network conditions.</td>
+        </tr>
+        <tr>
+           <td>N50</td>
+           <td>The application must be able to configure RTCP feedback transmission
+           interval (e.g., Transport-wide RTCP Feedback Message). This helps the application adapt
+           the video quality to the varying network and maintain consistent latency.</td>
+	</tr>
+        <tr>
+           <td>N51</td>
+           <td>The user agent needs to provide the jitter buffer to account for jitter
+           in the pipeline up to the frame render stage. This helps the application adapt
+           the video quality to the varying network and maintain consistent latency.</td>
+	</tr>
     </tbody>
 </table>
 <p>Experience: Microsoft's Xbox Cloud Gaming and NVIDIA's GeForce NOW are examples of this use case, with media
@@ -1065,9 +1090,34 @@ <h3>Requirements Summary</h3>
            <td>The WebRTC connection can generate signals indicating demands
            for keyframes, and surface those to the application.</td>
         </tr>
+        <tr id="N48">
+           <td>N48</td>
+           <td>The application must be able to control video decoding to continue even
+           after a frame-loss without waiting for a key frame. This helps the application recover
+           faster from lossy network conditions.</td>
+        </tr>
+        <tr id="N49">
+           <td>N49</td>
+           <td>The application must be able to generate signals that indicate to the encoder
+           the loss of encoder-decoder synchronicity (DPB buffers) and the sequence
+           of frame loss using the platform-agnostic protocols. This helps the application recover
+           faster from lossy network conditions.</td>
+        </tr>
+        <tr id="N50">
+           <td>N50</td>
+           <td>The application must be able to configure RTCP feedback transmission
+           interval (e.g., Transport-wide RTCP Feedback Message). This helps the application adapt
+           the video quality to the varying network and maintain consistent latency.</td>
+        </tr>
+        <tr id="N51">
+           <td>N51</td>
+           <td>The user agent needs to provide the jitter buffer to account for jitter
+           in the pipeline up to the frame render stage. This helps the application adapt
+           the video quality to the varying network and maintain consistent latency.</td>
+        </tr>
     </tbody>
 </table>
-<p class="note">Requirements N40-N47 have unresolved comments from a Call for Consensus (CfC).</p>
+<p class="note">Requirements N40-N51 have unresolved comments from a Call for Consensus (CfC).</p>
 </section>
 </body>
 </html>