Adding new RTCConfiguration targetLatency parameter#247
Conversation
|
Fixes #244 |
youennf
force-pushed
the
expectedLatency-option
branch
from
e6c4e24 to
b7be19f
Compare
rdar://165386600 https://bugs.webkit.org/show_bug.cgi?id=303083 Reviewed by Jean-Yves Avenard. When we set service class to video interactive, we also need to set traffic to video interactive, so as to benefit from network slicing. For now, we force traffic class to video interactive when service class is enabled. In the future, we might finetune this heuristic based on w3c/webrtc-extensions#247. Canonical link: https://commits.webkit.org/303528@main
| </p> | ||
| <pre class="idl"> | ||
| enum RTCConfigurationExpectedLatency { | ||
| "best", |
There was a problem hiding this comment.
Consider using a more concrete term. Maybe "lowest"?
| <td> | ||
| <p> | ||
| The User Agent is expected to set up the network link to optimize the connection latency. | ||
| For that purpose, it SHOULD use techniques like network slicing if available. |
There was a problem hiding this comment.
This is an undefined reference. Two browsers implementing this don't have any means of understanding whether or not they are achieving the same thing.
| <td> | ||
| <p> | ||
| The User Agent is expected to set up the network link to optimize the connection latency. | ||
| For that purpose, it SHOULD use techniques like network slicing if available. |
There was a problem hiding this comment.
try to see if you can cite a spec for network slicing here
|
In terms of meaningful links to browser developers, we could use these informal references:
We could go deeper and mention 5G specs (3GPP TS 28.530) but I am unsure how much this would be meaningful for browser developers. |
|
Can you elaborate on the expectation of this parameter? It looks rather straightforward for iOS but what is it supposed to do with regards to the rather complicated asynchronous flow on Android (see https://developer.android.com/develop/connectivity/5g/use-network-slicing)? |
| "no-expectation" | ||
| }; | ||
| partial dictionary RTCConfiguration { | ||
| RTCConfigurationExpectedLatency expectedLatency = "lowest"; |
There was a problem hiding this comment.
Plan is to change name to targetLatency or maybe latencyTarget
| <pre class="idl"> | ||
| enum RTCConfigurationExpectedLatency { | ||
| "lowest", | ||
| "no-expectation" |
@lgrahl Please also refer to https://source.android.com/docs/core/connect/5g-slicing. For this to work, carriers must configure a URSP rule for PRIORITIZE_LATENCY and associate it with a low‑latency slice; otherwise, traffic defaults to the standard slice. |
jan-ivar
changed the title
6 participants
Preview | Diff