- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Fri, 4 Mar 2016 22:44:30 +0100
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: "public-ortc@w3.org" <public-ortc@w3.org>, Robin Raymond <robin@hookflash.com>, Philipp Hancke <philipp.hancke@googlemail.com>
2016-03-04 19:14 GMT+01:00 Bernard Aboba <Bernard.Aboba@microsoft.com>: > Also, including RTX/RED/FEC as codecs enables ORTC to be used with simple > capabilities exchange signaling where only payload types are available. An > example might be a 1-1 audio/video scenario where RTX/RED/FEC is turned on, > but encodings[0].ssrc, encodings[0].fec.ssrc and encodings[0].rtx.ssrc might > not be set. > > So given those concerns, RTX/RED/FEC have been kept as codecs, with codec > capabilities and settings having been filled in within the latest Editor’s > draft. My opinion regarding this is very clear: When an API offers more than a single way to express the same, something is wrong and will lead to interoperability problems (vendor A expects "way A" of indicating X which vendor B expects "way B" of indicating X). -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Friday, 4 March 2016 21:45:18 UTC