Section 3.2.1: Add N49 - video decoding after loss

Partial fixes for w3c#103

index.html

@@ -299,6 +299,13 @@ <h4>Game streaming</h4>
            delay. This requirement is addressed by jitterBufferTarget, defined in
            [[?WebRTC-Extensions]] Section 6.</td>
         </tr>
+        <tr>
+           <td>N49</td>
+           <td>The application should be designed with a flexible video decoding
+           recovery system. This system must ensure uninterrupted decoding operations,
+           capable of handling frame-loss scenarios efficiently without the exclusive
+           reliance on key frames for recovery.<td>
+	</tr>
     </tbody>
 </table>
 <p>Experience: Microsoft's Xbox Cloud Gaming and NVIDIA's GeForce NOW are examples of this use case, with media
@@ -1071,9 +1078,16 @@ <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="N49">
+           <td>N49</td>
+           <td>The application should be designed with a flexible video decoding
+           recovery system. This system must ensure uninterrupted decoding operations,
+           capable of handling frame-loss scenarios efficiently without the exclusive
+           reliance on key frames for recovery.<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-N49 have unresolved comments from a Call for Consensus (CfC).</p>
 </section>
 </body>
 </html>