Re: [dhcwg] IPR statement related to draft-ietf-dhc-subscriber-id-X.txt

Ted Lemon <mellon@fugue.com> Fri, 06 February 2004 21:13 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16928 for <dhcwg-archive@odin.ietf.org>; Fri, 6 Feb 2004 16:13:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDHW-0007tI-MD for dhcwg-archive@odin.ietf.org; Fri, 06 Feb 2004 16:12:58 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16LCwuj030329 for dhcwg-archive@odin.ietf.org; Fri, 6 Feb 2004 16:12:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDHW-0007t6-HR for dhcwg-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 16:12:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16913 for <dhcwg-web-archive@ietf.org>; Fri, 6 Feb 2004 16:12:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApDHU-0004IE-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 16:12:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApDGZ-0004Dx-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 16:12:00 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApDFf-0004BE-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 16:11:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDFe-0007mS-2N; Fri, 06 Feb 2004 16:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDEh-0007as-T5 for dhcwg@optimus.ietf.org; Fri, 06 Feb 2004 16:10:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16860 for <dhcwg@ietf.org>; Fri, 6 Feb 2004 16:10:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApDEg-000486-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 16:10:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApDDz-00045A-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 16:09:19 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1ApDD8-00041I-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 16:08:26 -0500
Received: from [10.0.1.2] (dsl093-187-232.chi2.dsl.speakeasy.net [66.93.187.232]) by toccata.fugue.com (Postfix) with ESMTP id F18751B3CCB; Fri, 6 Feb 2004 14:58:00 -0600 (CST)
In-Reply-To: <4.3.2.7.2.20040206144519.02205e38@wells.cisco.com>
References: <200402061329.i16DT0r11498@cichlid.raleigh.ibm.com> <200402061329.i16DT0r11498@cichlid.raleigh.ibm.com> <4.3.2.7.2.20040206144519.02205e38@wells.cisco.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <9C7A0F2C-58E8-11D8-A6E8-000A95D9C74C@fugue.com>
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] IPR statement related to draft-ietf-dhc-subscriber-id-X.txt
Date: Fri, 06 Feb 2004 15:08:28 -0600
To: John Schnizlein <jschnizl@cisco.com>
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Feb 6, 2004, at 2:36 PM, John Schnizlein wrote:
> Let us not forget that this stipulation of royalty-free is unusual.
> Most IPR statements claim only the typical RAND statement.
> What is the reason for suddenly requiring the unusual IPR statement in 
> DHC?

Because the "RAND statement" is insufficient.   If I am distributing 
open-source software, I can't afford to pay you a royalty on the 
offchance that someone might use your patented technique, even if the 
royalty is "reasonable" by some standard.   I don't think it's even 
generally to your advantage to use the RAND terms, because it means 
that your devices can't be supported by open-source software.   I 
suppose it might sell a few extra copies of Network Registrar.

> Following the link Ralph posted, the Motorola-DHCP statement
> includes the usual RAND:

Yup.   I have no idea to what this statement applies.   I'm no happier 
about it than I am about Cisco's statement, but at this point it's a 
fait accompli, so there's no point in arguing about it.   This IPR 
statement was also never announced to the WG.

> Do you want to empower a company unrelated to the authors to block
> progress on a specification simply by filing a subjunctive statement:
> "that we may obtain intellectual property rights"

No.   Unfortunately, the present legal situation is that they can.   If 
you don't like that, contact your congresscritter - don't complain to 
me.

> Why is the IPR surprise and repair from PacketFront considered a reason
> to demand a new, unusual standard of zero-royalty from Cisco?

If you were to read the actual messages in the thread to which you were 
responding, you would already know the answer to this question.

> Note that there was no surprise in that filing since the original draft
> draft-droms-agentopt-8021x-00.txt in Nov 2001 included a RAND
> statement with a not-subjunctive patent declaration.

Putting an IPR statement at the bottom of an obscure draft that defines 
something very simple and obvious, that nobody would ever expect 
anybody to patent, isn't sufficient.   If you are claiming a patent on 
something, you should say so explicitly when you announce the draft, or 
when, subsequent to announcing the draft, you decide to add the IPR 
statement.   It has apparently become our collective job to read the 
IPR statement at the bottom of every copy of every draft that goes by 
to make sure there's no stealth patent claim, but tragically I wasn't 
aware of this until today.   Normally, I read drafts for technical 
issues, not for legal issues.   :'(


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg