Section 3.2.1: Clarify Game streaming requirements

Partial fixes for w3c#103

Author: xingri

index.html

@@ -298,6 +298,30 @@ <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 enables fast recovery
+           from lossy network conditions.</td>
+	</tr>
+        <tr>
+           <td>N49</td>
+           <td>The Application must be able to configure RTCP feedback transmission
+           interval (e.g., Transport-wide RTCP Feedback Message). This helps application
+	   to adapt video quality to varying network.</td>
+        </tr>
+        <tr>
+           <td>N50</td>
+           <td>The user agent must use the most efficient congestion control based on
+           platform, network’s capability, and other factors such as L4S. This helps
+           application to adapt video quality to varying network.</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 application 
+           to 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 +1089,33 @@ <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 enables fast recovery
+           from lossy network conditions.</td>
+        </tr>
+        <tr id="N49">
+           <td>N49</td>
+           <td>The Application must be able to configure RTCP feedback transmission
+           interval (e.g., Transport-wide RTCP Feedback Message). This helps application
+	   to adapt video quality to varying network.</td>
+        </tr>
+        <tr id="N50">
+           <td>N50</td>
+           <td>The user agent must use the most efficient congestion control based on
+           platform, network’s capability, and other factors such as L4S. This helps
+           application to adapt video quality to varying network.</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 application 
+           to 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>