Section 9.7: RTCRtpCodecParameters #113

Closed
aboba opened this Issue Jun 25, 2014 · 1 comment

Projects

None yet

2 participants

@aboba
Contributor
aboba commented Jun 25, 2014

Currently, we have:

partial dictionary RTCRtpCodecParameters {
DOMString name = "";
unsigned short payloadType;
sequence headerExtensionURIs;
};

What does this mean for an RTCRtpReceiver? If a headerExtensionURI is not specified for a given payloadType, does this mean that the header extension will be ignored if it is included in an RTP packet with that Payload Type? Probably not.

Also, what does it mean for an RTCRtpSender? If the headerExtensionURI is not specified for a given Codec name and payloadType, does it mean that the header extension is never sent in an RTP packet with that Payload Type?

@aboba
Contributor
aboba commented Jun 26, 2014

The argument here is that a RTCRtpSender object will only have one codec, and therefore that the headerextensions need only be configured globally. On the receiver the header extensions will also be global. So the proposed resolution is to remove the sequence of headerExtensionURIs from RTCRtpCodecParameters.

@robin-raymond robin-raymond added the 1.1 label Jun 28, 2014
@aboba aboba closed this Jul 8, 2014
@robin-raymond robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jul 16, 2014
Robin Raymond Added section on WebRTC 1.0 compatibility issues, responding to Issue #…
…66

Added Identity support, as described in Issue #78
Reworked getStats method, as described in Issue #85
Removed ICE restart method described in Issue #93
Addressed CNAME and synchronization context issues described in Issue #94
Fixed WebIDL issues noted in Issue #97
Addressed NITs described in Issue #99
DTLS transport issues fixed as described in Issue #100
ICE transport issues fixed as described in Issue #101
ICE transport controller fixes made as described in Issue #102
Sender and Receiver object fixes made as described in Issue #103
Fixed RTCRtpEncodingParameter default issues described in Issue #104
Fixed 'Big Picture' issues descibed in Issue #105
Fixed RTCRtpParameter default issues described in Issue #106
Added a multi-stream capability, as noted in Issue #108
Removed quality scalability capabilities and parameters, as described in Issue #109
Added scalability examples as requested in Issue #110
Addressed WebRTC 1.0 Data Channel compatibility issue described in Issue #111
Removed header extensions from RTCRtpCodecParameters as described in Issue #113
Addressed RTP/RTCP non-mux issues with IdP as described in Issue #114
Added getParameter methods to RTCRtpSender and RTCRtpReceiver objects, as described in Issue #116
Added layering diagrams as requested in Issue #117
Added a typedef for payload type, as described in Issue #118
Moved onerror from the RTCIceTransport object to the RTCIceListener object as described in Issue #121
Added explanation of Voice Activity Detection (VAD), responding to Issue #129
Clarified the meaning of maxTemporalLayers and maxSpatialLayers, as noted in Issue #130
Added RFC 6051 to the list of header extensions and removed RFC 5450, as noted in Issue #131
Addressed ICE terminology issues, as described in Issue #132
Separated references into Normative and Informative, as noted in Issue #133
6f8216a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment