Re: Issue found in RFC 3667 text
Pekka Savola <pekkas@netcore.fi> Wed, 28 April 2004 16:23 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 MAA25847 for <ipr-wg-archive@odin.ietf.org>; Wed, 28 Apr 2004 12:23:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIrdA-0004tL-Rl for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 12:09:53 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SG9qDf018798 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 12:09:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIrRN-0001mz-09 for ipr-wg-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 11:57:41 -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 LAA24031 for <ipr-wg-web-archive@ietf.org>; Wed, 28 Apr 2004 11:57:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIrRK-0002Ph-HP for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:57:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIrP4-0001uc-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:55:19 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BIrMd-0001JL-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:52:47 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BIrBD-0002S4-1G for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 11:40:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqmV-0007fb-Mf; Wed, 28 Apr 2004 11:15:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqJ9-0003uj-0m for ipr-wg@optimus.ietf.org; Wed, 28 Apr 2004 10:45:07 -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 KAA19542 for <ipr-wg@ietf.org>; Wed, 28 Apr 2004 10:44:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIqIj-0003XJ-8B for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:44:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIqHO-0003OE-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:43:19 -0400
Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12) id 1BIqFQ-0002vs-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 10:41:16 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id i3SEeC007783; Wed, 28 Apr 2004 17:40:12 +0300
Date: Wed, 28 Apr 2004 17:40:12 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: fred@cisco.com
cc: sob@harvard.edu, ipr-wg@ietf.org, rbarr@cisco.com
Subject: Re: Issue found in RFC 3667 text
In-Reply-To: <200404280149.SAA04765@irp-view7.cisco.com>
Message-ID: <Pine.LNX.4.44.0404281733540.6230-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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=AWL autolearn=no version=2.60
On Tue, 27 Apr 2004 fred@cisco.com wrote: > "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." This is probably more bug in our ipr notifications process than in the text itself. If you send in an IPR notice relating to draft-surname-foo-00.txt, you've fulfilled your obligations when you send in draft-surname-foo-00.txt to Internet-Drafts@ietf.org. I don't think anything in the policy requires that you send in your internet-draft only after the IPR notice has been filed at the web site, right? In other words, you can send the notice at 13:00:00, and send the draft in to internet-drafts@ at 13:00:01, and you'd fulfill your obligation to the letter. The main point appears to be whether the IETF executive director requires that the draft has been published before accepting an IPR note about a draft; IMHO, this should not be required, or one should be able to say "to-be-published draft-surname-foo". -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ 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