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

Re: [webrtc-stats] codec.sdpFmtpLine isn't clear about which description to use (#616)

From: docfaraday via GitHub <sysbot+gh@w3.org>
Date: Fri, 21 Jan 2022 22:18:06 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1018905073-1642803485-sysbot+gh@w3.org>
> > ...what's "currently being used".
> Unless... is early media still a thing? Is a receiver in "have-local-offer" or "have-remote-offer" prepared to receive any payload types defined in the union of currentLocalDescription _and_ pendingLocalDescription? cc @docfaraday

In the pre-webrtc days, it was a general rule that you never created an SDP that you were not prepared to honor immediately. However, this is often not possible due to ICE and BUNDLE, because those things rely on having both an offer and an answer to establish network connectivity. You could in theory do this on a renegotiation that reused already established transports, though, and webrtc-pc seems to hint that this is something we're expected to do (grep for "currently prepared to receive").

Of course, there's the whole pranswer business too.

GitHub Notification of comment by docfaraday
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/616#issuecomment-1018905073 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 January 2022 22:18:08 UTC

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