W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2022

[webrtc-pc] We should specify the intended behavior of addTrack, then setParameters(unicast), then sRD(simulcast offer) (#2777)

From: docfaraday via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 Oct 2022 22:12:59 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1398440918-1665007977-sysbot+gh@w3.org>
docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc:

== We should specify the intended behavior of addTrack, then setParameters(unicast), then sRD(simulcast offer) ==
There are two options here:

1. The setParameters (which by necessity will be unicast) establishes a unicast envelope; the sender should reject any new encodings in an sRD.
2. The setParameters does not set the simulcast envelope; a sRD(simulcast offer) can cause simulcast to happen, just like it could have if there was no setParameters call.

On the one hand, performing a unicast setParameters likely means that the user wants to do unicast. On the other hand, receiving a sRD(simulcast offer) might mean the opposite. The user is probably confused in some way here.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2777 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 October 2022 22:13:01 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC