Section 3.2.1: Add N48 - bandwidth feedback speed

Partial fixes for #103

index.html

@@ -299,6 +299,16 @@ <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 should be designed to offer suggestions for
+           timing parameter preferences to the User Agent (UA). This allows
+           the application to contribute to the management of packet loss
+           and optimization of packet reception timing without interfering
+           with UA congestion control algorithms. A 'Feedback Timing Hint'
+           mechanism could be introduced, enabling the application to indicate
+	   preferences such as 'default', 'rapid', or 'delayed'.</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 +1081,19 @@ <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 should be designed to offer suggestions for
+           timing parameter preferences to the User Agent (UA). This allows
+           the application to contribute to the management of packet loss
+           and optimization of packet reception timing without interfering
+           with UA congestion control algorithms. A 'Feedback Timing Hint'
+           mechanism could be introduced, enabling the application to indicate
+	   preferences such as 'default', 'rapid', or 'delayed'.</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-N48 have unresolved comments from a Call for Consensus (CfC).</p>
 </section>
 </body>
 </html>