Re: [codec] WG Review: Internet Wideband Audio Codec (codec)

Russ Housley <housley@vigilsec.com> Wed, 13 January 2010 15:28 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19FEF3A69F7; Wed, 13 Jan 2010 07:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.914
X-Spam-Level:
X-Spam-Status: No, score=-101.914 tagged_above=-999 required=5 tests=[AWL=-0.607, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 x0Xuae+otvTw; Wed, 13 Jan 2010 07:28:18 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 5059F3A67AF; Wed, 13 Jan 2010 07:28:18 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D3B969A4737; Wed, 13 Jan 2010 10:05:33 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id VNGMJxOjY1CA; Wed, 13 Jan 2010 10:05:20 -0500 (EST)
Received: from [192.168.2.113] (pool-173-66-67-45.washdc.fios.verizon.net [173.66.67.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BA4859A4728; Wed, 13 Jan 2010 10:05:32 -0500 (EST)
Message-ID: <4B4DE130.4000506@vigilsec.com>
Date: Wed, 13 Jan 2010 10:05:20 -0500
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090902 Eudora/3.0b3
MIME-Version: 1.0
References: <20091223171501.7BAE33A697D@core3.amsl.com> <13194D66-2110-4CB2-B130-8807BE57488B@cisco.com> <458913681001111218o3b232e4sd785b3c09809fcbc@mail.gmail.com> <4B4C46E0.8020609@iptego.com> <8903A80C339345EA82F3AEB33F708840@your029b8cecfe> <4B4CAB6D.8060109@octasic.com> <6e9223711001121222w65e1a25ak60758f29c981efd7@mail.gmail.com> <806dafc21001121239o9e1897cu27fbb3ad5776f5bb@mail.gmail.com> <6e9223711001121248v4dbd0e3dxcccf44b268bce395@mail.gmail.com> <alpine.DEB.1.10.1001130803220.15329@uplift.swm.pp.se> <6e9223711001130322m69b994c2n3252d572d1323f0f@mail.gmail.com>
In-Reply-To: <6e9223711001130322m69b994c2n3252d572d1323f0f@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IAB IAB <iab@iab.org>, codec@ietf.org, IETF Discussion <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Should the IETF standardize wideband Internet codec\(s\)? " <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2010 15:28:19 -0000

>> I see absolutely no good reason not to start the work and do
>> negotiations with other SDOs on the side.
>
> That is thw way these joint bodies are usually formed (at least the
> MPEG/ITU-T ones).  The group(s) form, and begin their
> work.(independently)  In parallel the chairs and SDO management work out
> the joint body organization.  It is easiest if the discussions on joint
> body organization begin as soon as possible.

My experience is different.  When the IETF works with another SDO, the 
final steps in approval are extremely painful.  The IETF process does 
not meld well with others, and the result is that getting the exact same 
words published by both organizations is a near deadlock experience.  It 
has been done, but only because of heroic efforts by chairs and editors. 
  For this reason, I prefer a situation where one SDO runs their own 
process and the result is submitted to partners after the words are 
final.  Of course, collaboration during the development of the document 
is most welcome, but the process rules of one SDO are governing the 
development.

Russ