- From: Peter Thatcher <pthatcher@google.com>
- Date: Fri, 17 Oct 2014 10:54:09 -0700
- To: "public-ortc@w3.org" <public-ortc@w3.org>
Received on Friday, 17 October 2014 17:55:17 UTC
They aren't real codecs, so it's kind of ugly going in "codecs", and it isn't completely obvious that doing so is necessary. It's also not obvious to use "APT" in an RTX "codec", not to mention that it's also kind of ugly. So, perhaps we could do something like this: dictionary RTCRtpParameters { DOMString muxId = ""; sequence<RTCRtpCodecParameters> codecs; * payloadtype redPayloadType; payloadtype fecPayloadType;* ... }; dictionary RTCRtpCodecParameters { DOMString name; payloadtype payloadType; * payloadtype rtxPayloadType;* ... }; Note that this does not tell the browser to send RTX, FEC, or RED. To do so, one must put in the correct per-encoding control points under RtpEncodingParameters. This merely specifies the payload types to send or receive in a way that's a little cleaner and more obvious than putting them in the list of RtpCodecParameters. Thoughts?
Received on Friday, 17 October 2014 17:55:17 UTC