- From: Philipp Hancke <fippo@goodadvice.pages.de>
- Date: Fri, 4 Mar 2016 16:55:47 +0100
- To: public-ortc@w3.org
>> I think that is totally wrong: >> >> - 'apt' is just a SDP fmtp parameter, it does not even appear in ORTC, >> and I hope we don't must rely on a generic parameter/value container >> for associating a RTX and its related media codec. > > That complicates the mapping to/from SDP. But I suppose that is worth it. I just tried to parse the chrome SDP I showed earlier and this seemed quite messy. I shrugged but came up with a question... how do you determine your local FEC capabilities if rtx is not a codec? Does http://ortc.org/wp-content/uploads/2015/11/ortc.html#dictionary-rtcrtpcodeccapability-members need a rtx member as well?
Received on Friday, 4 March 2016 15:56:24 UTC