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

Re: [webrtc-pc] Simulcast: Implementations do not fail (and that seems good) (#2762)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Oct 2022 17:46:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1271875081-1665164816-sysbot+gh@w3.org>
I closed #2779 because introducing more state requiring rollback seemed unwise when [no browser supports rolling it back](https://jsfiddle.net/jib1/kjn2deLm/18/).

It also violated the [original intent](https://github.com/w3c/webrtc-pc/pull/2081/files) which seemed to be for sRD(offer) to establish initial simulcast envelopes [in time for ontrack](https://github.com/w3c/webrtc-pc/issues/2014#issuecomment-432874655), but trim encodings only in answers (which cannot be rolled back). This and the spec's ban on _"[remotely initiated RID renegotiation](https://w3c.github.io/webrtc-pc/#set-description)"_ prevent `sender.getParameters().encodings.length` from decreasing in have-remote-offer (or increasing from their rollback).

One way to lift our ban on _"[remotely initiated RID renegotiation](https://w3c.github.io/webrtc-pc/#set-description)"_ (to comply with JSEP O/A) without giving up these invariants would be: once envelopes have been established, defer trimming them until the answer.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2762#issuecomment-1271875081 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 October 2022 17:47:00 UTC

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