Re: References to Redphone's "patent"

Thomas Narten <narten@us.ibm.com> Fri, 13 February 2009 20:31 UTC

Return-Path: <narten@us.ibm.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 3C0F43A69DF for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 12:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YUoLd9kB7ElW for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 12:31:48 -0800 (PST)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by core3.amsl.com (Postfix) with ESMTP id 295493A69AB for <ietf@ietf.org>; Fri, 13 Feb 2009 12:30:40 -0800 (PST)
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e2.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n1DKSiYg012156 for <ietf@ietf.org>; Fri, 13 Feb 2009 15:28:44 -0500
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id n1DKUkVi198002 for <ietf@ietf.org>; Fri, 13 Feb 2009 15:30:46 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n1DKUkSE012594 for <ietf@ietf.org>; Fri, 13 Feb 2009 15:30:46 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-228-230.mts.ibm.com [9.65.228.230]) by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n1DKUibc012471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Feb 2009 15:30:45 -0500
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id n1DKUfnJ010952; Fri, 13 Feb 2009 15:30:44 -0500
Message-Id: <200902132030.n1DKUfnJ010952@cichlid.raleigh.ibm.com>
To: jnc@mercury.lcs.mit.edu
Subject: Re: References to Redphone's "patent"
In-reply-to: <20090213190630.56CF76BE54F@mercury.lcs.mit.edu>
References: <20090213190630.56CF76BE54F@mercury.lcs.mit.edu>
Comments: In-reply-to jnc@mercury.lcs.mit.edu (Noel Chiappa) message dated "Fri, 13 Feb 2009 14:06:30 -0500."
Date: Fri, 13 Feb 2009 15:30:41 -0500
From: Thomas Narten <narten@us.ibm.com>
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 20:31:49 -0000

jnc@mercury.lcs.mit.edu (Noel Chiappa) writes:

>     > From: "Lawrence Rosen" <lrosen@rosenlaw.com>

>     > the previous IPR WG .. refused even to discuss a patent policy for IETF.

> I thought the IETF sort of had one, though (see RFC mumble)?

> I definitely agree that the IETF could use some sort of permanent
> legal IPR consulting board that WG's could go to and say 'we have
> this IPR filing, what does it mean, and what is the likely impact on
> our work'.

Please don't go there.

IPR consultation is all about risk analysis. And risk to the IETF
vs. risk to me personally vs. risk to my employer vs. risk to somebody
else's employer, etc. All are VERY different things.

I don't see an IPR consulting board as being helpful at all. It will
still come down to someone else trying to tell *me* (or you) that I
(or you) shouldn't worry about something, yet it might well be *my*
(or your) skin if things go awry.

The IETF absolutely and fundamentally needs stay out of evaluating the
merits of potential IPR and what the associated risks are. This is
fundamentally an individual decision that every implementor needs to
make on their own.

This principle has been a bedrock of the IETF's IPR policy for a very
long time, and for good reason.

Oh, and another important point, even when we have IPR disclosures,
they are often for patent applications, which are not public, nor have
they been issued (so they are only potential patents). In such cases,
there is precious little an advisory board could tell us, other than
"we don't know"...

Thomas