Re: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC

Phillip Hallam-Baker <hallam@gmail.com> Wed, 05 October 2011 20:22 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB0211E8103; Wed, 5 Oct 2011 13:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level:
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdY3rF2iG0UD; Wed, 5 Oct 2011 13:22:24 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1811921F8B6D; Wed, 5 Oct 2011 13:22:22 -0700 (PDT)
Received: by yxt33 with SMTP id 33so2378379yxt.31 for <multiple recipients>; Wed, 05 Oct 2011 13:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=hOex914GLKyK710+ikdpXkY3kSwt1G9X8rixsmieZJY=; b=VzTbSug2w45Juw2jeK7hzMnNJ4U0IcdnyOW7bQXHLAGkFHQpiQZkfr0+hYy+xzoU0r KnhFnhajEg59k9pTOuStn54+sHKLrLqAGZIl62E0X88OulTm/pJa9TOnt9ZjrfMWpfDd 12kJCxfwqSOlOCHwmZtKUhCEYSwu7HrG0qodg=
MIME-Version: 1.0
Received: by 10.101.11.36 with SMTP id o36mr2434235ani.74.1317846329714; Wed, 05 Oct 2011 13:25:29 -0700 (PDT)
Received: by 10.100.212.14 with HTTP; Wed, 5 Oct 2011 13:25:29 -0700 (PDT)
In-Reply-To: <20111005161247.1554.47741.idtracker@ietfa.amsl.com>
References: <20111005161247.1554.47741.idtracker@ietfa.amsl.com>
Date: Wed, 05 Oct 2011 16:25:29 -0400
Message-ID: <CAMm+LwiHo7Dz7ybcHcqy5NMhTZUPVT_i5=B3rG8Hf4jW52E8LQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: codec@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 05 Oct 2011 20:22:25 -0000

I have some issues with the way that the section on IPR is written.
While I agree with most of the statements there. I don't see my two
biggest IPR concerns listed.

1) Specific to this document, we already have unencumbered CODECs that
permit encoding of audio and video with acceptable fidelity and
adequate compression for 95% of all purposes. Thus it is essential
that the IPR regime for any future CODEC strictly limits the cost of
using that technique to some portion of the cost savings from
reduction in bandwidth use.

2) The principal concern I have with IPR licensing in general is not
the cost of licensing but the difficulty of licensing. I have on
several occasions been in negotiations with an IPR holder who is
completely unable to decide how much money they want or on what terms
they are willing to offer their IPR.

3) Linked to that is the problem of uncertainty. A purported rights
holder can only grant a license for the rights they hold, they cannot
and will not provide a warranty with respect to any other rights.
While due to the lingering effects of submarine patents it is
impossible to know if any CODEC is completely unencumbered, it is a
very safe bet that the audio codecs used for cinema sound in the mid
1980s are now unencumbered. It is not possible to be confident that
any new audio codec is unencumbered.

Taken in combination, I cannot imagine any reason to use any audio
codec other than MP3 or AC2 (or some other similar legacy scheme) once
we can be assured that the corresponding patents have expired. I
really could not care less what fidelity or other benefits might be
claimed for them. Bandwidth and storage are much cheaper than the
financial benefits offered by the technology held by the rights
holders.

The situation is very slightly different for video codecs, but not by
a great deal.


So the overall experience has been that it is like trying to negotiate
the purchase of some fancy-schmancy kitchen cabinets from some guy who
hasn't a clue about business but is desperate to make sure that they
don't leave a penny on the table even if his dithering about is likely
to cost him the business. Meanwhile you can get a perfectly
serviceable set of cabinets from Home Depot and Lowes where they will
give you price on the page ordering. In this case there is a free
alternative in almost every application worth bothering about.


On Wed, Oct 5, 2011 at 12:12 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Internet Wideband Audio Codec WG
> (codec) to consider the following document:
> - 'Guidelines for the Codec Development Within the IETF'
>  <draft-ietf-codec-guidelines-05.txt> as an Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-10-19. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   This document provides general guidelines for work on developing and
>   specifying a codec within the IETF.  These guidelines cover the
>   development process, evaluation, requirements conformance, and
>   intellectual property issues.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-codec-guidelines/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-codec-guidelines/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>



-- 
Website: http://hallambaker.com/