From: <stephane.proust@orange.com>
To: 'Jean-Marc Valin' <jmvalin@mozilla.com>,
 "'Mo Zanaty (mzanaty)'" <mzanaty@cisco.com>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
Thread-Index: AQHOrkKBNf0VLpHUzEKr6spLBSmfVZnAQkCw
Date: Wed, 11 Sep 2013 09:19:41 +0000
Message-ID: <4066_1378891183_523035AF_4066_5132_1_2842AD9A45C83B44B57635FD4831E60A06C3C1BE@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <20130802162957.17108.79281.idtracker@ietfa.amsl.com>
 <BBE9739C2C302046BD34B42713A1E2A22DF83C31@ESESSMB105.ericsson.se>
 <3879D71E758A7E4AA99A35DD8D41D3D91D5260A2@xmb-rcd-x14.cisco.com>
 <56C2F665D49E0341B9DF5938005ACDF80E8A65@DEMUMBX005.nsn-intra.net>
 <BBE9739C2C302046BD34B42713A1E2A22DF88232@ESESSMB105.ericsson.se>
 <CAGgHUiSK-bZrdXtxf-An8NM+pw-iqoWCrsG_bRUpxcD2DOCQrQ@mail.gmail.com>
 <3879D71E758A7E4AA99A35DD8D41D3D91D5265C8@xmb-rcd-x14.cisco.com>
 <522F4836.6030001@mozilla.com>
In-Reply-To: <522F4836.6030001@mozilla.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "'rtcweb@ietf.org'" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt
Precedence: list

>These are the codecs that would be recommended under such text. None of th=
em is really ideal for interactive audio

That is the reason why the proposed text only applies to "suitable" audio c=
odecs
" If other suitable audio codecs..."

That's also why it cannot be interpreted as a strictly normative text and w=
hy I also suggested (as it was previously suggested by the Chairs) to have =
some additional informative (and separate) text about what are those suitab=
le codecs to be considered and what is the rationale behind this (http://ww=
w.ietf.org/mail-archive/web/rtcweb/current/msg08501.html)

St=E9phane


-----Message d'origine-----
De=A0: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] De la part =
de Jean-Marc Valin
Envoy=E9=A0: mardi 10 septembre 2013 18:27
=C0=A0: Mo Zanaty (mzanaty)
Cc=A0: rtcweb@ietf.org
Objet=A0: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-audio-02.txt

> To ensure a baseline level of interoperability between WebRTC clients,=20
> a minimum set of required codecs are specified below.
> If other suitable audio codecs are available to the browser to use, it=20
> is RECOMMENDED that they are also included in the offer in order to=20
> maximize the possibility to establish the session without the need for=20
> audio transcoding.

Let's look at the practical effect here, assuming people were to actually f=
ollow such a recommendation. The only audio codecs that are implemented in =
browsers but not available for WebRTC are the ones used for HTML5. Accordin=
g to http://html5test.com/ these codecs are Vorbis, MP3, AAC, and uncompres=
sed PCM. These are the codecs that would be recommended under such text. No=
ne of them is really ideal for interactive audio, none of them is implement=
ed in old phones AFAIK, but all of them would require time and effort to ad=
d to a browser's RTP stack. I really don't see the point here.

	Jean-Marc
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.