Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01

[Jean-Marc Valin <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/13/2013 09:14 AM, Xavier Marjou wrote:
> - In order to reach a compromise, we would like to add some text in
> the WG draft draft-ietf-rtcweb-audio providing incentives for the
> browser to use these three codecs: make them mandatory to implement
> when there is no cost impact on the browser (e.g. if codec already
> installed, paid by the device vendor...).

I think this is the main faulty assumption here. "Royalties already
paid" does not imply "free". There's a real cost here because
supporting AMR, AMR-WB, G.722 and any other codecs added to that list
means that:
1) Someone has to write all the code for actually using these codecs
in their RTP stack.
2) There is no standard interface for accessing these codecs, so a
browser vendor would have to write code for each of these (often
undocumented) interface and *test* it on every device.
3) This code needs to be maintained and fixed for security
vulnerabilities.
4) If there's any issue (e.g. buffer overflow) in the platform
implementation of the codec, there's nothing the browser vendor can do
about it.

Oh, and that cost would be paid by pretty much all browser vendors
because they're all running on at least one platform that supports
each of these codecs.

Cheers,

	Jean-Marc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRQNc9AAoJEJ6/8sItn9q9WRYH/jzj4SoGpCQHZJGCO3Y0Ajuh
Eaj0rnJtHVg5LlR0QKEfJjXvqyyECAjfveJPnqFA8ALU8X1z+3McDsGJYisjpFm3
MbZKx3vE/Y/SYqy8jIP7/qPsba5eVuzKdUhoH4XzDNoowfBkQBkoys9JBpkL9osP
O+kRpXoouSu8CMGEuqgnl3gGddu/RayPaZTaDB0XICcxdsJF4S/C7E0RD3+XBr0f
rDcWQN4YkfI6VEaUZ+mGTAbMPBDCuahr8NYUJDwIQeqP7gWaAak/TV59+eZPi1El
o2qrom5fok1ZkWsC1izS4brs0tqmvggxYa9/snYnbjADmB9uOVtlH9Y+lrwHrRo=
=Ptz8
-----END PGP SIGNATURE-----