[webrtc-nv-use-cases] N15 latency control should be formulated in a technology-agnostic way (#91)

alvestrand has just created a new issue for https://github.com/w3c/webrtc-nv-use-cases:

== N15 latency control should be formulated in a technology-agnostic way ==
The current text of N15 is:

> The application must be able to control aspects of the data transport (e.g. set the SCTP heartbeat interval or turn it off), RTO values, etc.

This makes the assumption that 1) data transport is the only thing that needs controlling, and 2) that SCTP heartbeat and RTO are appropriate controls.

It should be restated in terms of what one wants to achieve, for instance:

> The application must be able to take steps to ensure a low and consistent latency for audio, video and data under varying network conditions. This may include tweaking of transport parameters for both media and data.


Please view or discuss this issue at https://github.com/w3c/webrtc-nv-use-cases/issues/91 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 12 January 2023 14:00:21 UTC