RE: Issue found in RFC 3667 text
Fred Baker <fred@cisco.com> Wed, 28 April 2004 17:31 UTC
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01441 for <ipr-wg-archive@odin.ietf.org>; Wed, 28 Apr 2004 13:31:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIsnB-0006Qa-JK for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 13:24:17 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SHOHIP024699 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 13:24:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIsX1-0001rp-56 for ipr-wg-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 13:07:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29382 for <ipr-wg-web-archive@ietf.org>; Wed, 28 Apr 2004 13:07:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIsWy-0007Nv-2n for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:07:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIsW7-0007Kf-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:06:39 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIsVd-0007Gk-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:06:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIsLo-0007Lt-Hx; Wed, 28 Apr 2004 12:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqSH-0005Ds-KZ for ipr-wg@optimus.ietf.org; Wed, 28 Apr 2004 10:54:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16179 for <ipr-wg@ietf.org>; Wed, 28 Apr 2004 10:00:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIpcM-00066k-2p for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:00:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIpbI-00063v-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 09:59:48 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1BIpaY-0005zS-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 09:59:03 -0400
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 28 Apr 2004 06:59:50 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i3SDwRjO027102; Wed, 28 Apr 2004 06:58:27 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id ASM71828; Wed, 28 Apr 2004 06:57:40 -0700 (PDT)
Message-Id: <6.1.0.6.2.20040428062836.0623f328@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 28 Apr 2004 06:47:05 -0700
To: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>
From: Fred Baker <fred@cisco.com>
Subject: RE: Issue found in RFC 3667 text
Cc: sob@harvard.edu, ipr-wg@ietf.org, rbarr@cisco.com
In-Reply-To: <93DB9233B42C2844B0A1B7E8B94D99C30148F888@HDBOSMX.haleanddo rr.com>
References: <93DB9233B42C2844B0A1B7E8B94D99C30148F888@HDBOSMX.haleanddorr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: ipr-wg-admin@ietf.org
Errors-To: ipr-wg-admin@ietf.org
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-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=1.3 required=5.0 tests=AWL autolearn=no version=2.60
At 07:49 AM 04/28/04 -0400, Contreras, Jorge wrote: >As far as the second issue raised by Fred, that was an intentional >feature. If a patent application has not been published and the applicant >wishes to maintain the confidentiality of its contents, then he/she should >not submit an ID covered by the application's claims unless willing to >disclose enough to satisfy the 3668 requirements. IANAL, and Todd Glassey advises me that there is some recent case law that sets aside what I'm about to say. Legal comment would be instructive to the discussion. My understanding is that the confidentiality of the filing is not at his option. Since the claims have been neither supported or denied, he cannot say what IPR claims he might have. At most, he can say that he "may have IPR" related to the draft. To say that he should not submit a draft in such a case is to say that the IETF should stop its work. Generally, invention happens in the course of solving a problem. I can solve a problem for my customer and in so doing generate potential IPR. If I can't talk about that in the course of standardization, the standard will therefore likely not meet my customer's needs. Voila, the internet runs on proprietary protocols and procedures, and standards lag. It is also to say that vendors are forced to develop early proprietary solutions, and their customers are forced to buy them, in addition to later standardized solutions, where what the customer is requesting is standardized solutions in the first place. Vendors today frequently contribute IPR to standardization discussions and solve their customers' issues in the context of the standard. I really need to be able to say that I have filed a defensive patent without going into the details of the patent, as I myself don't know more than that I have filed it. If the argument is that I should not have filed the patent, I can point to a case currently being litigated in which - I wrote some code (for a prior employer) - I didn't patent it as I had pulled the algorithm out of the research literature, - An employee of a related company wrote a patent on the algorithm, - Now Cisco and said other company are locked in a legal battle. Corporate policy requires me to write defensive patent applications to prevent such situations. So not filing the patent application, however much I might prefer it, is a violation of my company's policy. (I do push back when IMNSHO it gets to the point of being ridiculous, as rbarr will attest...) It seems that in a case where the license is free and is extended in any case except if the licensing company sues mine (Cisco's practice on such things), this should be sufficient. _______________________________________________ Ipr-wg mailing list Ipr-wg@ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg
- Re: Issue found in RFC 3667 text Scott Bradner
- RE: Issue found in RFC 3667 text Robert Barr
- Issue found in RFC 3667 text fred
- Re: Issue found in RFC 3667 text Fred Baker
- Re: Issue found in RFC 3667 text Brian E Carpenter
- RE: Issue found in RFC 3667 text Contreras, Jorge
- Re: Issue found in RFC 3667 text todd glassey
- Re: Issue found in RFC 3667 text Pekka Savola
- RE: Issue found in RFC 3667 text Fred Baker
- Re: Issue found in RFC 3667 text Harald Tveit Alvestrand
- Re: Issue found in RFC 3667 text todd glassey
- Re: Issue found in RFC 3667 text Steven M. Bellovin
- Re: Issue found in RFC 3667 text todd glassey
- Re: Issue found in RFC 3667 text Fred Baker
- RE: Issue found in RFC 3667 text Harald Tveit Alvestrand
- RE: Issue found in RFC 3667 text Lawrence Rosen
- RE: Issue found in RFC 3667 text Richard Barr Hibbs
- Re: Issue found in RFC 3667 text Scott W Brim
- Re: Issue found in RFC 3667 text Brian E Carpenter
- Re: Issue found in RFC 3667 text Pekka Savola
- Re: Issue found in RFC 3667 text Brian E Carpenter
- Re: Issue found in RFC 3667 text Pekka Savola
- Re: Issue found in RFC 3667 text todd glassey
- Re: Issue found in RFC 3667 text Brian E Carpenter
- Re: Issue found in RFC 3667 text Pekka Savola
- RE: Issue found in RFC 3667 text Robert Barr
- Re: Issue found in RFC 3667 text todd glassey
- RE: Issue found in RFC 3667 text Lawrence Rosen
- Re: Issue found in RFC 3667 text todd glassey
- re: Issue found in RFC 3667 text Larry Masinter
- re: Issue found in RFC 3667 text Ted Hardie