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

[webrtc-pc] Validation of reordered readonly parameters in setParameters

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

== Validation of reordered readonly parameters in setParameters ==
Step 7 of setParameters says:

> If parameters.encodings.length is different from N, or if any parameter in the parameters argument, marked as a Read-only parameter, has a value that is different from the corresponding parameter value returned from sender.getParameters(), abort these steps and return a promise rejected with a newly created InvalidModificationError. Note that this also applies to transactionId.

And the description for `codec` field for `RTCRtpParameters` says:

> When using the setParameters method, the codecs sequence from the corresponding call to getParameters can be reordered and entries can be removed, but entries cannot be added, and the RTCRtpCodecParameters dictionary members cannot be modified.

This seems to require step 7 to handle reordering/dropping of readonly parameters as well, but it is a bit ambiguous in step 7 whether reordering/dropping is allowed. Even if it allows, does this mean that `encodings` elements can be reordered, and `headerExtensions` elements can be reordered/dropped as well?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1492 using your GitHub account
Received on Monday, 17 July 2017 08:43:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC