Re: Issue found in RFC 3667 text

"todd glassey" <todd.glassey@worldnet.att.net> Wed, 28 April 2004 15:59 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 LAA24300 for <ipr-wg-archive@odin.ietf.org>; Wed, 28 Apr 2004 11:59:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIrLG-0008SP-P1 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 11:51:23 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SFpMgY032509 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 11:51:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIr66-0002lB-Ja for ipr-wg-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 11:35:42 -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 LAA22096 for <ipr-wg-web-archive@ietf.org>; Wed, 28 Apr 2004 11:35:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIr64-0007lq-4n for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:35:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIr5E-0007gY-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:34:49 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIr4a-0007be-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:34:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqll-0007Yt-Nx; Wed, 28 Apr 2004 11:14:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqBC-0001dL-Vf for ipr-wg@optimus.ietf.org; Wed, 28 Apr 2004 10:36:55 -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 KAA18547 for <ipr-wg@ietf.org>; Wed, 28 Apr 2004 10:36:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIqAn-0002IH-6t for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:36:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIpy0-0000Lx-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:23:16 -0400
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115]) by ietf-mx with esmtp (Exim 4.12) id 1BIpxI-0000F3-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:22:32 -0400
Received: from gw (29.san-jose-09-10rs.ca.dial-access.att.net[12.72.195.29]) by worldnet.att.net (mtiwmhc11) with SMTP id <2004042814220011100icg5ve>; Wed, 28 Apr 2004 14:22:01 +0000
Message-ID: <005e01c42d2c$12e82070$010aff0a@gw>
From: todd glassey <todd.glassey@worldnet.att.net>
To: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>, fred@cisco.com, sob@harvard.edu
Cc: ipr-wg@ietf.org, rbarr@cisco.com
References: <93DB9233B42C2844B0A1B7E8B94D99C30148F888@HDBOSMX.haleanddorr.com>
Subject: Re: Issue found in RFC 3667 text
Date: Wed, 28 Apr 2004 07:21:10 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
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.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jorge - in the US Instance  The PEARS system *The PTO's online System shows
all US Patent's in filed and granted states. The EuroPatent Office is doing
similar efforts and access levels for their information so there is no
reason that ANYONE *(yes anyone) has any issues with doing a Patent Search.

http://appft1.uspto.gov/netahtml/PTO/help/status.html

In the US's case the updates happen Thursday's so Friday is the first
glimpse that the public gets at the updated USPTO data... and its all online
from the mid 1700's onwards (and I am referring to the years the 'mid
1700's' onwards).

Todd

----- Original Message ----- 
From: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>
To: <fred@cisco.com>; <sob@harvard.edu>
Cc: <ipr-wg@ietf.org>; <rbarr@cisco.com>
Sent: Wednesday, April 28, 2004 4:49 AM
Subject: RE: Issue found in RFC 3667 text


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


_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg