IETF Logo Mail Archive

Re: [rtcweb] Call for Consensus Regarding Selecting Recommended Audio Codecs

Eric Burger <eburger@standardstrack.com> Fri, 18 January 2013 00:06 UTC

Return-Path: <eburger@standardstrack.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 BD54821F8895 for <rtcweb@ietfa.amsl.com>; Thu, 17 Jan 2013 16:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.142
X-Spam-Level:
X-Spam-Status: No, score=-101.142 tagged_above=-999 required=5 tests=[AWL=1.142, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
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 kqyxjniNdQgU for <rtcweb@ietfa.amsl.com>; Thu, 17 Jan 2013 16:06:27 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 34CB821F8A0D for <rtcweb@ietf.org>; Thu, 17 Jan 2013 16:06:27 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:62524 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1TvzTV-00038B-HM; Thu, 17 Jan 2013 16:06:25 -0800
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <24103_1358435764_50F815B4_24103_9252_1_2842AD9A45C83B44B57635FD4831E60A076013@PEXCVZYM14.corporate.adroot.infra.ftgroup>
Date: Thu, 17 Jan 2013 19:06:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE549A18-4272-4720-943B-E545956742A9@standardstrack.com>
References: <50D2CC6A.4090500@ericsson.com> <24103_1358435764_50F815B4_24103_9252_1_2842AD9A45C83B44B57635FD4831E60A076013@PEXCVZYM14.corporate.adroot.infra.ftgroup>
To: stephane.proust@orange.com
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Call for Consensus Regarding Selecting Recommended 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: Fri, 18 Jan 2013 00:06:30 -0000

So this says that hundreds of millions of mobile telephones do not support SIP, either. Therefore, should we care if we do not support this proprietary network? I don't.

On Jan 17, 2013, at 10:16 AM, stephane.proust@orange.com wrote:

> Strictly sticking to the current situation with only OPUS and G.711 will not solve properly the issue especially because this would mean to fail to address correctly the biggest market of hundreds of millions of mobiles terminals that currently support neither G.711 nor OPUS.

v2.23.0 | Report a Bug | By Email