IETF Logo Mail Archive

Re: [rtcweb] Consensus vs. Voting (was Re: Call for Consensus Regarding Selecting Recommended Audio Codecs)

Adam Roach <adam@nostrum.com> Thu, 17 January 2013 02:28 UTC

Return-Path: <adam@nostrum.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 B640321F861A for <rtcweb@ietfa.amsl.com>; Wed, 16 Jan 2013 18:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, SPF_PASS=-0.001, 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 TkLVBGE2ASEP for <rtcweb@ietfa.amsl.com>; Wed, 16 Jan 2013 18:28:09 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2549821F857C for <rtcweb@ietf.org>; Wed, 16 Jan 2013 18:28:08 -0800 (PST)
Received: from Orochi.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0H2RxfB073453 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 Jan 2013 20:27:59 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <50F761AE.9080408@nostrum.com>
Date: Wed, 16 Jan 2013 20:27:58 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <50D2CC6A.4090500@ericsson.com> <6515_1357907583_50F0067F_6515_1738_1_2842AD9A45C83B44B57635FD4831E60A0747CC@PEXCVZYM14.corporate.adroot.infra.ftgroup> <BLU0-SMTP880A602A311CE05C9DC39FD0290@phx.gbl> <A26C56D5-C501-4823-8099-62AF7910B8A4@ntt-at.com> <580BEA5E3B99744AB1F5BFF5E9A3C67D16813E56EC@HE111648.emea1.cds.t-internal.com> <50F41D97.1030508@nostrum.com> <CAD5OKxtsWMfAV=K4sM+zLXoyVCgihwujH2gG9ziA5GuEtsU0sQ@mail.gmail.com> <50F43ACA.80206@nostrum.com> <CAD5OKxug2qB+Xi_cp87Lt7BiPwJ1Eq1rNuioj+zDZFf=RRckPw@mail.gmail.com> <50F44AF0.4060304@nostrum.com> <CAD5OKxs7Ueto0k-5TWnQtgb+Pocp-SSu3ctr3qFs5qrcPgMtkQ@mail.gmail.com> <50F4619F.7040208@nostrum.com> <CAD5OKxu3_JJ3zS8hCeG-nHM72t=0j--ihUR8E5NvL9--wmmnEA@mail.gmail.com> <7CBFD4609D19C043A4AC4FD8381C6E2602386636@DEMUEXC014.nsn-intra.net> <50F5A74C.3030203@nostrum.com> <CABkgnnXRcFHj4gi6WEDDqU+S-adnjd91wQW4bL2S6pO8YtzE3w@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D7468A700@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20D7468A700@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Consensus vs. Voting (was Re: 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: Thu, 17 Jan 2013 02:28:09 -0000

On 1/16/13 18:27, DRAGE, Keith (Keith) wrote:
> If you refer back to the earlier mail from Stephane, there was also the point, which I agree with, that if you have a licensed version of any codec on your device, ideally you want your browser to support that codec. You don't want to be told that you cannot talk to another user who only has codec B, when you have already paid the license fee to use codec B, just because your browser vendor decides it is not its favourite codec.

That's not an argument for "implementations SHOULD implement codec X," 
which is the question at hand (where X is a set of one or more specific, 
named codecs).

What you're putting forth is a vaguely related argument for 
"implementations SHOULD make use of all codecs provided by the 
underlying platform on which they are deployed." But that's a very 
different question.

And, to be clear, if the other device that you're talking to "only has 
codec B," where B is not "the set of both G.711 and Opus," then we're 
already wandering off into the realm of fully non-compliant implementations.

/a

v2.23.0 | Report a Bug | By Email