W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2017

[webrtc-pc] Undefined setParameters behavior of handling parameters fields other than transactionId and encodings

From: Soares Chen via GitHub <sysbot+gh@w3.org>
Date: Mon, 17 Jul 2017 04:27:26 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-243294519-1500265645-sysbot+gh@w3.org>
soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:

== Undefined setParameters behavior of handling parameters fields other than transactionId and encodings ==
- Currently it is not clear how `setParameters()` handle the fields `headerExtensions`, `rtcp`, `codecs`, and `degradationPreference`. 

- There is a section for handling codecs, but it is not clear why it is written separately instead of included inside the steps. 

- The spec doesn't specify the behavior when the argument fields are left undefined, or if they are set with invalid values.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1489 using your GitHub account
Received on Monday, 17 July 2017 04:27:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC