W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2018

[webrtc-pc] RTCRtpReceiver.getParameters() clarification

From: Florent Castelli via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Nov 2018 17:45:59 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-380813999-1542217558-sysbot+gh@w3.org>
Orphis has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCRtpReceiver.getParameters() clarification ==
> encodings is populated based on the RIDs present in the current remote description.

What happens before negotiation? Should this be an empty array?

> The headerExtensions sequence is populated based on the header extensions that the receiver is currently prepared to receive.
The codecs sequence is populated based on the codecs that the receiver is currently prepared to receive.

What is meant by "prepared to receive"?
Does it mean that previous to negotiation those lists are similar to RTCRtpReceiver.getCapabilities()?
What happens if the user calls setCodecPreferences()?

It seems that it should be equivalent to RTCRtpSender.getParameters() and list codecs and headerExtensions that have been negotiated in the call (or an empty list before negotiation).

> rtcp.reducedSize is set to true if the receiver is currently prepared to receive reduced-size RTCP packets, and false otherwise. rtcp.cname is left out.

Why is the rtcp.cname left out? If the client knows the value, why wouldn't we then return it?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2032 using your GitHub account
Received on Wednesday, 14 November 2018 17:46:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:45 UTC