RE: Issue found in RFC 3667 text
"Contreras, Jorge" <Jorge.Contreras@haledorr.com> Wed, 28 April 2004 13:20 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 JAA14342 for <ipr-wg-archive@odin.ietf.org>; Wed, 28 Apr 2004 09:20:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIoyI-0003YT-0M for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 09:19:30 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SDJTJq013632 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 09:19:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIom1-0000B4-NG for ipr-wg-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 09:06:49 -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 JAA13375 for <ipr-wg-web-archive@ietf.org>; Wed, 28 Apr 2004 09:06:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIom0-0002g2-1p for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 09:06:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIol4-0002aJ-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 09:05:50 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIokG-0002Wg-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 09:05:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIoa5-0006W0-Uz; Wed, 28 Apr 2004 08:54:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BInbW-0002VO-P0 for ipr-wg@optimus.ietf.org; Wed, 28 Apr 2004 07:51:54 -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 HAA08452 for <ipr-wg@ietf.org>; Wed, 28 Apr 2004 07:51: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 1BInbV-0007lB-RN for ipr-wg@ietf.org; Wed, 28 Apr 2004 07:51:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BInaX-0007Rn-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 07:50:54 -0400
Received: from hdbosdmz2.haleanddorr.com ([148.139.190.21]) by ietf-mx with esmtp (Exim 4.12) id 1BInZX-0006tA-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 07:49:51 -0400
Received: from HDBOSMX.haleanddorr.com ([148.139.4.241]) by hdbosdmz2.haleanddorr.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 28 Apr 2004 07:49:20 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Issue found in RFC 3667 text
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
Date: Wed, 28 Apr 2004 07:49:20 -0400
Message-ID: <93DB9233B42C2844B0A1B7E8B94D99C30148F888@HDBOSMX.haleanddorr.com>
Thread-Topic: Issue found in RFC 3667 text
Thread-Index: AcQs1kIGpd7qeZCsR+Wzi1WZlA9l5QAQEcKw
From: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>
To: fred@cisco.com, sob@harvard.edu
Cc: ipr-wg@ietf.org, rbarr@cisco.com
X-OriginalArrivalTime: 28 Apr 2004 11:49:20.0872 (UTC) FILETIME=[D7F22E80:01C42D16]
Content-Transfer-Encoding: quoted-printable
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=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
I agree that the 'race condition' is a bug in the 3667 legend language. Making it consistent with 3668 would be more accurate. 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. -----Original Message----- From: ipr-wg-admin@ietf.org [mailto:ipr-wg-admin@ietf.org]On Behalf Of fred@cisco.com Sent: Wednesday, April 28, 2004 2:50 AM To: sob@harvard.edu Cc: ipr-wg@ietf.org; rbarr@cisco.com Subject: Issue found in RFC 3667 text Robert Barr and I were discussing, and concluded that there is an error in the language required by section 5.1 of RFC 3667. Consider the text: "By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668." I cannot file an IPR notice without a posted draft to file it concerning, and this statement says that at the time I post it I have already revealed all IPR known to me. In communication protocol design, we refer to this as a "race condition." There is also another issue with it; IPR is generally not granted for years after filing, the contents of the filing are confidential, and one doesn't know what subset of the claims in the filing will be granted. So this, I believe, requires me to not file an internet draft describing any algorithms concerning which I may have filed for IPR claims until those claims have been granted or denied and I can talk about my IPR. The claim is also inconsistent with RFC 3668, which states: 6.2.1. Timing of disclosure under Section 6.1.1 The IPR disclosure required pursuant to section 6.1.1 must be made as soon as reasonably possible after the Contribution is published in an Internet Draft unless the required disclosure is already on file. Is this what was intended? _______________________________________________ Ipr-wg mailing list Ipr-wg@ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg _______________________________________________ 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