-
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
Clarification in Section 7.3.2 #153
Comments
An update to the proposed text (assuming that codecs without an intrinsic kind are returned at all): Obtain the receiver capabilities, based on kind. If kind is omitted or set to "", then all capabilities are returned. To avoid confusion, getCapabilities(kind) should return codecs with a matching intrinsic kind value, as well as codecs with no intrinsic kind, (such as the retransmission payload [RFC4588] and redundancy [RFC2198]). For codecs with no intrinsic kind, RTCRtpCapabilities.RTCRtpCodecCapability[i].kind returned by getCapabilities(kind> should be set to the value of kind if kind is equal to "audio" or "video". If the kind argument was omitted or set to "", then the value of RTCRtpCapabilities.RTCRtpCodecCapability[i].kind is set to "". Also, in the same section, the following modified receive text is proposed: receive |
…3c#146 Address questions about RTCRtpCodecCapability.preferredPayloadType, as noted in: Issue w3c#147 Address questions about RTCRtpSender.setTrack() error handling, as noted in: Issue w3c#148 Partially address 'automatic' use of scalable video coding (in RTCRtpReceiver.receive()) as noted in: Issue w3c#149 Renamed RTCIceListener to RTCIceGatherer as noted in: Issue w3c#150 Added text on multiplexing of STUN, TURN, DTLS and RTP/RTCP, as noted in: Issue w3c#151 Address issue with queueing of candidate events within the RTCIceGatherer, as noted in: Issue w3c#152 Clarify behavior of RTCRtpReceiver.getCapabilities(kind), as noted in: Issue w3c#153
A question has arisen as to how RTCRtpReceiver.getCapabilities(kind) should behave with respect to codecs that have no intrinsic kind (such as RTX or RED). For example, if we assume that RTX and RED can be used with kind === 'audio' or 'video', should these codecs be returned regardless of the value of kind? Also, should RTX and/or RED be returned as a codec capability at all?
Below is some proposed text for Section 7.3.2 to describe the desired behavior of RTCRtpReceiver.getCapabilities:
getCapabilities, static
Obtain the receiver capabilities, based on kind. If kind is omitted or set to "", then all capabilities are returned. To avoid confusion, getCapabilities(kind) should return codecs with a matching intrinsic kind value, as well as codecs with no intrinsic kind, (such as the retransmission payload [RFC4588] and redundancy [RFC2198]), with the value of RTCRtpCapabilities.RTCRtpCodecCapability[i].kind set to the value of kind passed as an argument to RTCRtpReceiver.getCapabilities(kind).
The text was updated successfully, but these errors were encountered: