RTCRtpCodecCapability options vs parameters #412

Closed
ibc opened this Issue Mar 11, 2016 · 4 comments

Projects

None yet

3 participants

@ibc
Contributor
ibc commented Mar 11, 2016

RTCRtpCodecCapability

options of type Dictionary

Codec-specific parameters available for signaling.

parameters of type Dictionary

Codec-specific parameters that must be signaled to the remote party.

Honestly, no idea which the difference is :)

@robin-raymond
Contributor

parameters are those things that the remote party must know about where as options are either optional parameters to be sent to the remote party or other local/informational options for a particular codec (but the remote party need not know about it).

@robin-raymond
Contributor

@ibc can I close down this question issue now?

@ibc
Contributor
ibc commented Apr 16, 2016

Sure, if the spec clearly describes the above explanation (I've not checked the text regarding it in master).

@robin-raymond
Contributor

Hmm... I don't think the spec is clear enough. I think we need need a tweak:

We should likely change:

options of type Dictionary
Codec-specific parameters available for signaling.

To:

options of type Dictionary
Codec-specific parameters that may be optionally signalled and are available as additional supported information or settings about the codec.

... or something like that...

@aboba aboba added PR exists and removed question labels May 10, 2016
@aboba aboba added a commit that referenced this issue May 10, 2016
@aboba aboba RTCRtpCodecCapability options vs parameters
Fix for Issue #412
73a5d66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment