Re: [rtcweb] Confirmation of consensus on audio codecs

<Bernhard.Feiten@telekom.de> Wed, 29 August 2012 14:01 UTC

Return-Path: <Bernhard.Feiten@telekom.de>
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 6786411E80D1 for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 07:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 iTzXWvKo74zJ for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 07:01:14 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6B211E809A for <rtcweb@ietf.org>; Wed, 29 Aug 2012 07:01:14 -0700 (PDT)
Received: from he111528.emea1.cds.t-internal.com ([10.125.90.87]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 29 Aug 2012 16:01:11 +0200
Received: from HE111541.emea1.cds.t-internal.com ([169.254.2.25]) by HE111528.EMEA1.CDS.T-INTERNAL.COM ([2002:7cd:5a57::7cd:5a57]) with mapi; Wed, 29 Aug 2012 16:01:11 +0200
From: <Bernhard.Feiten@telekom.de>
To: <rtcweb@ietf.org>
Date: Wed, 29 Aug 2012 16:01:10 +0200
Thread-Topic: Confirmation of consensus on audio codecs
Thread-Index: AQHNe9LENUMF/Hj3nEmo2lnRJlNz25dwxSKw
Message-ID: <CE8995AB5D178F44A2154F5C9A97CAF402517E0F4517@HE111541.emea1.cds.t-internal.com>
References: <9E2843EA-EBB9-40B3-898C-6B5216FAE7A5@cisco.com>
In-Reply-To: <9E2843EA-EBB9-40B3-898C-6B5216FAE7A5@cisco.com>
Accept-Language: de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 29 Aug 2012 14:01:18 -0000

The mandatory-to implement (MTI) codec for rtcweb should ensure interoperability and good quality. 
It should be possible to implement the codec without hurdles.

The G.722 provides wideband quality at 64 kbit/s. It is easy to implement and causes no additional costs.
Hence G.722 should be a MTI codec for rtcweb. 
It provides also interoperability to other voice communication services.

For interoperability reasons to other voice communication services G.711 should be a MTI codec for rtcweb. 
It provides only narrow-band quality. But it is easy to implement and causes no additional costs.
 
For interoperability reasons to other voice communication services  AMR and AMR-WB should be supported.
As these codecs are not that easy to implement and may cause additional costs, they should not be MTI codecs for rtcweb.
If rtcweb is used for calls to mobile phones, it is likely that these codecs will be supported as this guarantees the best quality. 
  
Other  low bitrate codec may be supported , but should not be MTI codec for rtcweb. The codecs cause additional hurdles. Interoperability is already guaranteed by the MTI codecs. The implementer can decide on its own to support the codec.  

Best regards,
Bernhard


-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Cullen Jennings (fluffy)
Sent: Donnerstag, 16. August 2012 19:16
To: rtcweb@ietf.org
Subject: [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