- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Mar 2022 19:47:39 +0000
- To: public-webrtc-logs@w3.org
False alarm, sorry. The anomaly I recalled was _receiver-side_ in https://github.com/w3c/webrtc-pc/issues/2710: > * sender [getParameters](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-getparameters) gets [encodings](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsendparameters-encodings) from [[SendCodecs]] which is set in the answer or pranswer. > * receiver [getParameters](https://w3c.github.io/webrtc-pc/#dom-rtcrtpreceiver-getparameters) gets [encodings](https://w3c.github.io/webrtc-pc/#dom-rtcrtpsendparameters-encodings) from [[ReceiveCodecs]] which is set in SLD. IOW the [set a session description](https://w3c.github.io/webrtc-pc/#set-description) algorithm says that: * the _receiver_ returns _pending_ encodings in `"have-local-offer"`, whereas * the _sender_ always returns _current_ encodings >March 15 meeting discussion about re-negotiation: > > * Until re-negotiation is complete, RTCRtpSender.getParameters() should return the current configuration. Since `scalabilityMode` is sender-side, this decision is congruent with the current spec (and already specified). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/68#issuecomment-1069550482 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 March 2022 19:47:44 UTC