RE: How we got here, RE: References to Redphone's "patent"

"Hallam-Baker, Phillip" <pbaker@verisign.com> Fri, 13 February 2009 23:59 UTC

Return-Path: <pbaker@verisign.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E17083A6C5D for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 15:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.458
X-Spam-Level:
X-Spam-Status: No, score=-6.458 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 vZjta-IZcIXl for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 15:59:13 -0800 (PST)
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by core3.amsl.com (Postfix) with ESMTP id DFE0F3A6833 for <ietf@ietf.org>; Fri, 13 Feb 2009 15:59:13 -0800 (PST)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id n1DNZS6T022642; Fri, 13 Feb 2009 15:35:28 -0800
Received: from MOU1WNEXMB09.vcorp.ad.vrsn.com ([10.25.15.197]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Feb 2009 15:59:19 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C98E37.153D7CF5"
Subject: RE: How we got here, RE: References to Redphone's "patent"
Date: Fri, 13 Feb 2009 15:59:18 -0800
Message-ID: <2788466ED3E31C418E9ACC5C3166155768B298@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: How we got here, RE: References to Redphone's "patent"
Thread-Index: AcmONIR9nJfwdGdMTCyP/wkWz40THwAAVCQT
References: <87skmknar8.fsf@ashbery.wjsullivan.net><tslfxiiuzs5.fsf@live.mit.edu> <1F52870FDF6C4903800E145AAEB9FAF7@LROSENTOSHIBA> <2788466ED3E31C418E9ACC5C3166155768B296@mou1wnexmb09.vcorp.ad.vrsn.com> <499604F9.5050209@gmail.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 13 Feb 2009 23:59:19.0289 (UTC) FILETIME=[15903E90:01C98E37]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2009 23:59:15 -0000

In my view major technical options should be decided before you start. This is a standards process, not an invention process.

I do not design protocols in committee, never have, never will. That type of work was possible when there were 40 people coming to IETF meetings and the problem was coordinating independent research projects. It is not a sensible use of people's time to do the type of unconstrained investigation you suggest with more than five people in the room.

Understanding the cost of the materials you intend to use is a key part of being an engineer. I like to work from price on the page catalogs. If a supplier wants to play 'guess my price' then I look to do the job another way.

What you suggest increases the leverage of patent trolls. The more working group effort is sunk into the idea that they claim proprietary ownership of, the more leverage they have. Moreover nobody can implement until the IPR issues are fully understood. 


-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
Sent: Fri 2/13/2009 6:40 PM
To: Hallam-Baker, Phillip
Cc: ietf@ietf.org
Subject: Re: How we got here, RE: References to Redphone's "patent"
 
Phill,

On 2009-02-14 10:41, Hallam-Baker, Phillip wrote:
...
> The proposal that I made then was that when a working group is started, it specify the IPR criteria under which it is chartered. In some cases it makes perfect sense to charter a group that will be using encumbered technology. In other cases the entire purpose of the group requires that any technology be open and unencumbered.

We've been round that argument enough times that it's become a tradition.

A priori rules like that make no sense for the IETF.

1. They inhibit innovative thinking within the WG process, because
they mean that the major technical options must basically be
decided before you start, so that you can decide which IPR regime
is going to work. And if you decide a priori to be RF, the available
solutions are dramatically constrained. Or to say it more emotively:
all the good ideas have been patented anyway.

2. They would assist the patent trolls, who could make sure to
quietly acquire patents that encumber the 'royalty free' solution
just in time for the standard to be widely adopted.

Leaving the choice until later in the process isn't perfect,
but it reduces these two risks and matches the reality of
IPR laws and practices, which are heavily based on RAND and
reciprocity, like it or not.

IMHO, as always.

    Brian