-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Section 9.7: RTCRtpCodecParameters #113
Labels
Comments
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
pushed a commit
to robin-raymond/ortc
that referenced
this issue
Jul 16, 2014
…3c#66 Added Identity support, as described in Issue w3c#78 Reworked getStats method, as described in Issue w3c#85 Removed ICE restart method described in Issue w3c#93 Addressed CNAME and synchronization context issues described in Issue w3c#94 Fixed WebIDL issues noted in Issue w3c#97 Addressed NITs described in Issue w3c#99 DTLS transport issues fixed as described in Issue w3c#100 ICE transport issues fixed as described in Issue w3c#101 ICE transport controller fixes made as described in Issue w3c#102 Sender and Receiver object fixes made as described in Issue w3c#103 Fixed RTCRtpEncodingParameter default issues described in Issue w3c#104 Fixed 'Big Picture' issues descibed in Issue w3c#105 Fixed RTCRtpParameter default issues described in Issue w3c#106 Added a multi-stream capability, as noted in Issue w3c#108 Removed quality scalability capabilities and parameters, as described in Issue w3c#109 Added scalability examples as requested in Issue w3c#110 Addressed WebRTC 1.0 Data Channel compatibility issue described in Issue w3c#111 Removed header extensions from RTCRtpCodecParameters as described in Issue w3c#113 Addressed RTP/RTCP non-mux issues with IdP as described in Issue w3c#114 Added getParameter methods to RTCRtpSender and RTCRtpReceiver objects, as described in Issue w3c#116 Added layering diagrams as requested in Issue w3c#117 Added a typedef for payload type, as described in Issue w3c#118 Moved onerror from the RTCIceTransport object to the RTCIceListener object as described in Issue w3c#121 Added explanation of Voice Activity Detection (VAD), responding to Issue w3c#129 Clarified the meaning of maxTemporalLayers and maxSpatialLayers, as noted in Issue w3c#130 Added RFC 6051 to the list of header extensions and removed RFC 5450, as noted in Issue w3c#131 Addressed ICE terminology issues, as described in Issue w3c#132 Separated references into Normative and Informative, as noted in Issue w3c#133
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
The text was updated successfully, but these errors were encountered: