Re: Mapping RTX in SDP to ORTC RtpParameters from Sergio Garcia Murillo on 2016-03-04 (public-ortc@w3.org from March 2016)

From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Fri, 4 Mar 2016 17:04:39 +0100
To: Philipp Hancke <fippo@goodadvice.pages.de>
Cc: public-ortc@w3.org
Message-ID: <CA+ag07akwqUHR=hd2zg=QRGvfoaMVbfmnpgoC06Rqgkx1NB+yg@mail.gmail.com>

El 4/3/2016 16:57, "Philipp Hancke" <fippo@goodadvice.pages.de> escribió:
>>>
>>> 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?
>

Not following you, FEC and RTX are orthogonal. You can have FEC without RTX
and vice versa.

BR
Sergio

Received on Friday, 4 March 2016 16:05:10 UTC