Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Section 3.2.1: Add N48 - bandwidth feedback speed #118

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Section 3.2.1: Add N48 - bandwidth feedback speed #118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,6 +299,14 @@ <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.</td>
</tr>
</tbody>
</table>
<p>Experience: Microsoft's Xbox Cloud Gaming and NVIDIA's GeForce NOW are examples of this use case, with media
Expand Down Expand Up @@ -1068,9 +1076,17 @@ <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.</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>