Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG

David Singer <singer@apple.com> Tue, 02 June 2009 19:32 UTC

Return-Path: <singer@apple.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6D9B3A6D62; Tue, 2 Jun 2009 12:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ry59NX7lJluL; Tue, 2 Jun 2009 12:32:11 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 41F2028C124; Tue, 2 Jun 2009 12:32:11 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 84EE062DD73A; Tue, 2 Jun 2009 12:32:12 -0700 (PDT)
Received: from relay16.apple.com (unknown [127.0.0.1]) by relay16.apple.com (Symantec Brightmail Gateway) with ESMTP id 68B9C5A0005; Tue, 2 Jun 2009 12:32:12 -0700 (PDT)
X-AuditID: 11807137-a4d67bb00000380b-2f-4a257e3cc68f
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52]) by relay16.apple.com (Apple SCV relay) with ESMTP id 1C543558016; Tue, 2 Jun 2009 12:32:12 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408aac64b2d02ec07@[10.0.1.8]>
In-Reply-To: <ybu8wka5tjd.fsf@jesup.eng.wgate.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu> <p062408a5c64b21091de5@[10.0.1.8]> <ybu8wka5tjd.fsf@jesup.eng.wgate.com>
Date: Tue, 02 Jun 2009 12:31:53 -0700
To: Randell Jesup <rjesup@wgate.com>
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: dispatch@ietf.org, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>, stephen botzko <stephen.botzko@gmail.com>
Subject: Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2009 19:32:15 -0000

At 15:23  -0400 2/06/09, Randell Jesup wrote:
>  >FWIW, 3GPP SA4 is also a place with interest in codecs for packet networks,
>>and has standardized codecs in the past.  Opening a new work item there is
>>not trivial, but can be done.
>
>Again, I imagine even getting involved in 3GPP is tough with many hoops,
>let alone getting the rest of them to sanction a new codec not designed for
>radio use specifically.  You can't even directly apply to join; you have to
>go through an "Organizational Partner" like ATIS.  Not going to happen here...

The only hoop is an organizational partner.  For large companies, it 
can be expensive (e.g. ETSI sets your dues based on your telecoms 
related revenue, if I recall correctly).

On a spectrum of desirability of process etc., I'd guess that
* codecs from international bodies with a procedure and track record 
for doing them thoroughly, are preferred (MPEG, ITU, 3GPP)
* codecs from international bodies not normally in the codec field 
offer at least a stable specification and the opportunity for 
critique and refinement, leading to that specification (e.g. IETF)
* codecs developed in open-source  are at least open to anyone, but 
they have the issue that they lack a formal reference, a formal 
consensus process, a stable publication 'home', IPR rules for 
contributors, and so on
* commercial codecs have the backing of a company, and generally 
stability, interop, and so on are well managed (if they want to 
succeed), but are typically confidential and 'take it or leave it'.


And yes, it gets a little cheaper each time we move down a rung here, 
which is the trade-off.
-- 
David Singer
Multimedia Standards, Apple Inc.