Re: Mapping RTX in SDP to ORTC RtpParameters

>> 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?

need a rtx member as well?

Received on Friday, 4 March 2016 15:56:24 UTC