Re: [rtcweb] Confirmation of consensus on audio codecs

Randall Gellens <randy@qualcomm.com> Wed, 29 August 2012 16:29 UTC

Return-Path: <randy@qualcomm.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 488BE21F84B2 for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 09:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.87
X-Spam-Level:
X-Spam-Status: No, score=-104.87 tagged_above=-999 required=5 tests=[AWL=-1.729, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_MED=-4, SARE_RAND_1=2, 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 SeHVZgQOtSqq for <rtcweb@ietfa.amsl.com>; Wed, 29 Aug 2012 09:29:01 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 41DF821F84AE for <rtcweb@ietf.org>; Wed, 29 Aug 2012 09:29:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1346257742; x=1377793742; h=message-id:x-mailer:date:to:from:subject:mime-version: content-type:x-random-sig-tag:x-originating-ip; bh=uGhRfwbTvLM5gN9HlBFZ7jexQay01HNpeoBV3PWf0sc=; b=HJ62vcwWYdZy80HNnp3UvAwjW9edsG2CZ44eKwJ4zV0pnyoVNpluVqEM He1LGSAOZk7v7elV27DKW61/0M4asCxqYxUjcLdwlk5IlYo4//JJT1J9w DVujowVyiWwedU36YV3yPRzOzpms6OjzOeMtIYUoyzWdfQoJEb0HAhSoL 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6819"; a="228451864"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 29 Aug 2012 09:28:59 -0700
X-IronPort-AV: E=Sophos; i="4.80,334,1344236400"; d="scan'208,217"; a="160835134"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Aug 2012 09:28:59 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Wed, 29 Aug 2012 09:28:57 -0700
Message-ID: <p06240600cc63f2eedf3d@[99.111.97.136]>
X-Mailer: Eudora for Mac OS X
Date: Wed, 29 Aug 2012 09:25:53 -0700
To: <Markus.Isomaki@nokia.com>, <fluffy@cisco.com>, <rtcweb@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
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 16:29:02 -0000

Re: [rtcweb] Confirmation of consensus on audio codecs
At 7:26 PM +0000 8/28/12, <Markus.Isomaki@nokia.com> wrote:

We do not recommend Opus to be taken as a mandatory codec for RTCWeb at this point. From high quality low bit rate and mobile applications point of view the 3GPP AMR-WB codec (also known as ITU-T G.722.2) is the most preferable for us. For interoperability with implementations restricted to unencumbered codecs, we prefer G.711 and G.722.

Mandating only G.711 provides a floor to prevent total failure to negotiate codecs, while allowing implementations to support whichever codecs make sense in their environments.


At 8:39 PM -0700 8/21/12, Ted Hardie <ted.ietf at gmail.com> wrote:

the fundamental design of RTCWEB allows for the
negotiation of any codec mutually supported.  The decision to chose a
Mandatory-to-implement was not made to eliminate other choices, but to
eliminate interoperability failures by ensuring that at least one
common codec is always available.

I think this is a key point.  Codecs should be mandated only to prevent negotiation failure, not to guarantee ideal performance, especially in light of Ted's next statement:

At 8:39 PM -0700 8/21/12, Ted Hardie <ted.ietf at gmail.com> wrote:

the group presumes that codec support does not
come from the downloadable Javascript application, but from the
application environment into which it is downloaded (commonly a
browser or mobile environment using similar technology).  Promoting
support for those environments to have access to codecs supported by
the underlying hardware is the best way to further this goal, at least
in my personal opinion.

This makes a lot of sense. Especially on mobile devices, natively supported codecs are likely to have optimized performance within the operating environment (e.g., mobile device and cellular channel).

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
#Random Tag
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
When you're young, you look at television and think, There's a
conspiracy. The networks have conspired to dumb us down. But when
you get a little older, you realize that's not true. The networks
are in business to give people exactly what they want. That's a
far more depressing thought. Conspiracy is optimistic! You can
shoot the bastards! We can have a revolution! But the networks
are really in business to give people what they want. It's the
truth.              --Steve Jobs, Wired Magazine, February 1996