RE: Previous consensus on not changing patent policy (Re: References to Redphone's "patent")

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 16 February 2009 23:20 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 E331C3A6A58 for <ietf@core3.amsl.com>; Mon, 16 Feb 2009 15:20:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 qr3mxDpEP5X2 for <ietf@core3.amsl.com>; Mon, 16 Feb 2009 15:20:28 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 727F53A6A3B for <ietf@ietf.org>; Mon, 16 Feb 2009 15:20:28 -0800 (PST)
Received: from [10.20.30.158] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n1GNKYUO050488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Feb 2009 16:20:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240839c5bfa3544666@[10.20.30.158]>
In-Reply-To: <3BEE4CFFA90F43B5917F328AE8BDF0EE@LROSENTOSHIBA>
References: <20090213190630.56CF76BE54F@mercury.lcs.mit.edu><200902132030.n1DKUfnJ0109 52@cichlid.raleigh.ibm.com> <2963ECA56B01F94B9964469DCB8A2B5A05610EF6@de01exm69.ds.mot.com> <265AEFC9577741F5A6B36FACDD757673@LROSENTOSHIBA> <499965B7.9050702@alvestrand.no> <3BEE4CFFA90F43B5917F328AE8BDF0EE@LROSENTOSHIBA>
Date: Mon, 16 Feb 2009 15:19:30 -0800
To: lrosen@rosenlaw.com, ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: RE: Previous consensus on not changing patent policy (Re: References to Redphone's "patent")
Content-Type: text/plain; charset="us-ascii"
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: Mon, 16 Feb 2009 23:20:30 -0000

At 2:11 PM -0800 2/16/09, Lawrence Rosen wrote:
>Let's forget the past; I acknowledge we lost that argument then among those
>few who bothered to hum.

Many of us have heard this in various technical working groups when people who didn't get their way come back later. Such reconsiderations, particularly on topics of a non-protocol nature, are rarely embraced. We are humans with limited time and energy and focus.

>But are the 1,000 or so emails in recent days from the FSF campaign not a
>loud enough hum to recognize that our IPR policy is out of tune?

No, it is a statement that a group of people who are not active in the IETF want us to spend our time and effort to fix a problem they feel that they have.

> This is not
>the first such open source campaign either. IETF needs a more sturdy process
>to deal with IPR issues. Please consider the suggestions now on the table.

Where? I see no Internet Draft, nor any significant group of people who have said they are willing to work on the problem. Seriously, if this is a significant issue for this motivated group of people, they can do some research and write one (or probably more) Internet Drafts.

The IETF has never been swayed by blitzes of a mailing list asking for us to do someone else's technical work; we should not be swayed by similar blitzes asking us to do their policy work. We are, however, amazingly (and sometime painfully) open to discussing worked-out solutions of either a technical or policy nature. In this case, "worked-out" means a document that describes the the current solution, the advantages and disadvantages of it, a proposal for a new solution, and a transition plan.

--Paul Hoffman, Director
--VPN Consortium