Re: [dhcwg] IPR statement related to draft-ietf-dhc-subscriber-id-X.txt
Mark Stapp <mjs@cisco.com> Fri, 06 February 2004 22:18 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 RAA25794 for <dhcwg-archive@odin.ietf.org>; Fri, 6 Feb 2004 17:18:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEIY-0004m6-IU for dhcwg-archive@odin.ietf.org; Fri, 06 Feb 2004 17:18:06 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16MI6S1018348 for dhcwg-archive@odin.ietf.org; Fri, 6 Feb 2004 17:18:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApEIY-0004lr-Ea for dhcwg-web-archive@optimus.ietf.org; Fri, 06 Feb 2004 17:18:06 -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 RAA25784 for <dhcwg-web-archive@ietf.org>; Fri, 6 Feb 2004 17:18:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApEIW-0007DZ-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 17:18:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApEHe-0007AE-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 17:17:11 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApEHL-000769-00 for dhcwg-web-archive@ietf.org; Fri, 06 Feb 2004 17:16:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApE6r-0003X0-LY; Fri, 06 Feb 2004 17:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApE6p-0003Wn-Mw for dhcwg@optimus.ietf.org; Fri, 06 Feb 2004 17:05:59 -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 RAA25010 for <dhcwg@ietf.org>; Fri, 6 Feb 2004 17:05:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApE6n-00069g-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 17:05:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApE5r-00067T-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 17:05:00 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1ApE5f-00065C-00 for dhcwg@ietf.org; Fri, 06 Feb 2004 17:04:48 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 06 Feb 2004 14:11:36 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id i16M4FT5012781; Fri, 6 Feb 2004 14:04:15 -0800 (PST)
Received: from mjs-xp.cisco.com ([161.44.65.244]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFW72658; Fri, 6 Feb 2004 17:04:14 -0500 (EST)
Message-Id: <4.3.2.7.2.20040206162911.01d58ab0@goblet.cisco.com>
X-Sender: mjs@goblet.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 06 Feb 2004 17:02:04 -0500
To: Ted Lemon <mellon@fugue.com>
From: Mark Stapp <mjs@cisco.com>
Subject: Re: [dhcwg] IPR statement related to draft-ietf-dhc-subscriber-id-X.txt
Cc: John Schnizlein <jschnizl@cisco.com>, dhcwg@ietf.org
In-Reply-To: <9C7A0F2C-58E8-11D8-A6E8-000A95D9C74C@fugue.com>
References: <4.3.2.7.2.20040206144519.02205e38@wells.cisco.com> <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
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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
this is an ietf-wide issue, and this is the wrong forum for it. the ietf has had a consistent expectation, and that's what companies have met. it doesn't make sense to me to try to establish a different expectation in this one working group. if you want to change the way that the ietf handles IP (Intellectual Property, I mean, not the other thing) and IP licensing, more power to you and godspeed. take your issue to the proper forum - take it to the IPR WG, for example, or to the IAB. it doesn't make sense to me to complain that the ietf expectation is wrong, and that the ietf wg that's working on the issue is also wrong, and so the only way to get the policy to be what you want is to make some other wg do something different from the ietf as a whole. the tone of this thread has gotten a little hysterical, it seems to me. it's not really the thing to suggest that cisco people are trying to compete with you unfairly because they have a bigger legal department than nominum does. the cisco people who contribute to this wg are, as you know well, committed to doing the right thing. Let's take the thread back to the specific issue: I objected to the initial, vague packetfront IPR statement because I didn't like the implication that someone could stop progress in the standards body without substantial claims. the vague statement has been amended and brought in line with ietf expectations. I'm not aware of any DHC work that has related IPR statements that don't meet the ietf's expectations. it may even have been a good thing that we've had this blow-up, because it will certainly make us more aware of the issues going forward. now that the issue has been resolved, I'd like to continue the progress of this draft. -- Mark At 03:08 PM 2/6/2004 -0600, Ted Lemon wrote: >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. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] IPR statement related to draft-ietf-dhc-s… Ralph Droms
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- RE: [dhcwg] IPR statement related to draft-ietf-d… Bernie Volz
- Re: [dhcwg] IPR statement related to draft-ietf-d… Thomas Narten
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… Thomas Narten
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ralph Droms
- Re: [dhcwg] IPR statement related to draft-ietf-d… Mark Stapp
- Re: [dhcwg] IPR statement related to draft-ietf-d… Bud Millwood
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… John Schnizlein
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… Kim Kinnear
- Re: [dhcwg] IPR statement related to draft-ietf-d… Mark Stapp
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… Vernon Schryver
- RE: [dhcwg] IPR statement related to draft-ietf-d… Barr Hibbs
- RE: [dhcwg] IPR statement related to draft-ietf-d… Mark Stapp
- RE: [dhcwg] IPR statement related to draft-ietf-d… Bernie Volz
- RE: [dhcwg] IPR statement related to draft-ietf-d… Barr Hibbs
- RE: [dhcwg] IPR statement related to draft-ietf-d… Bernie Volz
- RE: [dhcwg] IPR statement related to draft-ietf-d… Ralph Droms
- RE: [dhcwg] IPR statement related to draft-ietf-d… Bernie Volz
- RE: [dhcwg] IPR statement related to draft-ietf-d… Barr Hibbs
- RE: [dhcwg] IPR statement related to draft-ietf-d… Barr Hibbs
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- Re: [dhcwg] IPR statement related to draft-ietf-d… Ted Lemon
- RE: [dhcwg] IPR statement related to draft-ietf-d… Ralph Droms