Re: [rtcweb] Confirmation of consensus on audio codecs

<stephane.proust@orange.com> Tue, 21 August 2012 07:57 UTC

Return-Path: <stephane.proust@orange.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D92D21F8549 for <rtcweb@ietfa.amsl.com>; Tue, 21 Aug 2012 00:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.794
X-Spam-Level:
X-Spam-Status: No, score=-0.794 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, SARE_MILLIONSOF=0.315, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HWx+T4vY0R9 for <rtcweb@ietfa.amsl.com>; Tue, 21 Aug 2012 00:57:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 3080D21F8540 for <rtcweb@ietf.org>; Tue, 21 Aug 2012 00:57:51 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 6148B264B97; Tue, 21 Aug 2012 09:57:50 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 4708735C048; Tue, 21 Aug 2012 09:57:50 +0200 (CEST)
Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Tue, 21 Aug 2012 09:57:49 +0200
From: <stephane.proust@orange.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Confirmation of consensus on audio codecs
Thread-Index: AQHNe9LENUMF/Hj3nEmo2lnRJlNz25dj6efA
Date: Tue, 21 Aug 2012 07:57:49 +0000
Message-ID: <20330_1345535870_50333F7E_20330_3420_1_2842AD9A45C83B44B57635FD4831E60A029156@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <9E2843EA-EBB9-40B3-898C-6B5216FAE7A5@cisco.com>
In-Reply-To: <9E2843EA-EBB9-40B3-898C-6B5216FAE7A5@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.2]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.8.21.70317
Subject: Re: [rtcweb] Confirmation of consensus on audio codecs
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 07:57:55 -0000

For voice and multimedia communication services as targeted by WebRTC, two codecs, G.711 and G.722, are fully fitting the conditions to get a mandatory to implement status: a fully ensured unencumbered status, a wide implementation in devices and legacy networks and a low complexity that ensures they can be supported on any types of plate-forms and terminals.

So we support both G.711 and G.722 to be specified as "mandatory to implement" codecs since G.722 will guarantee a much higher voice quality at same bit rate and almost no additional cost. At a minimum G.722 should be (strongly) recommended.

With respect to OPUS, it has currently no footprint on the market, its implementation complexity and resulting costs are unknown, including with respect to IPRs issues, and some performance aspects are still to be more deeply assessed, like for instance quality with packet losses and jitter which is a key issue for usage over internet. 

In addition, we believe that two additional requirements are necessary to make WebRTC a future proof technology and suitable for a wide range of applications and environments:
Firstly, the optional support of other widely deployed legacy codecs must be allowed which includes at least the codecs implemented in millions of mobile terminals: AMR and AMR-WB.
Secondly, the technology must be open enough to facilitate the usage of any other codecs supported by the device but external to the browser.


-----Message d'origine-----
De : rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] De la part de Cullen Jennings (fluffy)
Envoyé : jeudi 16 août 2012 19:16
À : rtcweb@ietf.org
Objet : [rtcweb] Confirmation of consensus on audio codecs


At the last meeting we took a hum on selecting Opus and G.711 as the mediatory to implement audio codecs. If there is any new opinions please send them to the list by August 30th, after which the chairs will make a determination of consensus.

Thanks,
Cullen

Please note that the following IPR disclosure have been made on these codecs. They can be found at 

http://datatracker.ietf.org/ipr/


2010-11-07	
. ID # 1445
"Broadcom Corporation's Statement about IPR related to draft-ietf-codec-opus-00 and draft-ietf-codec-description-00 (1)"
2010-11-07	
. ID # 1446
"Xiph.Org Foundation's Statement about IPR related to draft-ietf-codec-opus-00"
2010-11-12	
. ID # 1447
"Broadcom Corporation's Statement about IPR related to draft-ietf-codec-opus-00 and draft-ietf-codec-description-00 (2)"
2011-03-23	
. ID # 1520
"Qualcomm Incorporated's Statement about IPR related to draft-ietf-codec-opus-05"
2011-03-27	
. ID # 1524
"Xiph.Org Foundation's Statement about IPR related to draft-ietf-codec-opus-05"
2011-03-29	
. ID # 1526
"Broadcom Corporation's Statement about IPR related to draft-ietf-codec-opus-05"
2011-03-29	
. ID # 1525
"Skype Limited's Statement about IPR related to draft-ietf-codec-opus-05"
2011-07-23	
. ID # 1602
"Skype Limited's Statement about IPR related to draft-ietf-codec-opus-07"
2012-01-25	
. ID # 1670
"Microsoft Corporation's Statement about IPR related to draft-ietf-codec-opus-10"
2012-03-12	
. ID # 1712
"Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-codec-opus-11 (1)"
2012-04-02	
. ID # 1741
"Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-codec-opus-11 (2)"



_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles 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 electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information 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 delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.