- From: Sun Shin via GitHub <noreply@w3.org>
- Date: Fri, 12 Dec 2025 01:34:03 +0000
- To: public-webrtc-logs@w3.org
> 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)? @lgrahl Please also refer to https://source.android.com/docs/core/connect/5g-slicing. Our implementation (NVIDIA) relies on PRIORITIZE_LATENCY OSAppId mapping to the appropriate slice. The [bindProcessToNetwork() ](https://developer.android.com/reference/android/net/ConnectivityManager#bindProcessToNetwork(android.net.Network)) API can be used to direct requests to a network with this capability. Google defines additional OSAppIds for other use cases (e.g., PRIORITIZE_BANDWIDTH, PRIORITIZE_UNIFIED_COMMUNICATIONS, CBS). 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. -- GitHub Notification of comment by xingri Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/247#issuecomment-3644521314 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 December 2025 01:34:03 UTC