Section 3.2.1: Clarify Game streaming requirements

Partial fixes for #103

index.html

@@ -292,6 +292,27 @@ <h4>Game streaming</h4>
            <td>The application must be able to control the jitter buffer and rendering
            delay.</td>
         </tr>
+        <tr>
+           <td>N48</td>
+           <td>WebRTC must support a mode in which it allows video decoding to continue 
+           even after a frame loss without waiting for a key frame.</td>
+        </tr>
+        <tr>
+           <td>N49</td>
+           <td>The WebRTC connection should generate signals indicating to encoder about
+           loss of encoder-decoder synchronicity (DPB buffers) and sequence of the frame loss
+	   (RFC 4585 section-6.3.3: Reference Picture Selection Indication).</td>
+        </tr>
+        <tr>
+           <td>N50</td>
+           <td>Application must be able to configure RTCP feedback transmission interval
+           (Ex: Transport-wide RTCP Feedback Message).</td>
+        </tr>
+        <tr>
+           <td>N51</td>
+           <td>WebRTC neeed to provide the jitter buffer to account for jitter 
+           in the pipeline upto the frame render stage.</td>
+        </tr>
     </tbody>
 </table>
 <p>Experience: Microsoft's Xbox Cloud Gaming and NVIDIA's GeForce NOW are examples of this use case, with media
@@ -1052,9 +1073,31 @@ <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>WebRTC must support a mode in which it allows video decoding
+           to continue even after a frame loss without waiting for a key frame.
+           This enables addition of recovery methods such as using frames
+	   containing intra coded macroblocks and coding units.</td>
+        </tr>
+        <tr id="N49">
+           <td>N49</td>
+           <td>The WebRTC connection can generate signals indicating to encoder about
+           loss of encoder-decoder synchronicity and sequence of the loss. </td>
+        </tr>
+        <tr id="N50">
+           <td>N50</td>
+           <td>Application must be able to configure RTCP feedback transmission interval
+           (Ex: Transport-wide RTCP Feedback Message).</td>
+        </tr>
+        <tr id="N51">
+           <td>N51</td>
+           <td>Extend adaptation of the jitter buffer to account for jitter 
+           in the pipeline upto the frame render stage.</td>
+        </tr>
     </tbody>
 </table>
-<p class="note">Requirements N30-N47 have not completed a Call for Consensus (CfC).</p>
+<p class="note">Requirements N30-N51 have not completed a Call for Consensus (CfC).</p>
 </section>
 </body>
 </html>