[newtrk] Re: I-D ACTION:draft-savola-ipr-lastcall-04.txt (fwd)

John C Klensin <john-ietf@jck.com> Sat, 23 October 2004 16:21 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07022 for <newtrk-archive@lists.ietf.org>; Sat, 23 Oct 2004 12:21:25 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i9NG96IU010468; Sat, 23 Oct 2004 09:09:06 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i9NG96wJ010467; Sat, 23 Oct 2004 09:09:06 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i9NG94Qd010452 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <newtrk@lists.uoregon.edu>; Sat, 23 Oct 2004 09:09:05 -0700 (PDT)
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1CLORx-0002h2-Ud; Sat, 23 Oct 2004 12:09:02 -0400
Date: Sat, 23 Oct 2004 12:09:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: ipr-wg@ietf.org, newtrk@lists.uoregon.edu
Subject: [newtrk] Re: I-D ACTION:draft-savola-ipr-lastcall-04.txt (fwd)
Message-ID: <171F1FF7EA97E9BC3AE6F15E@scan.jck.com>
In-Reply-To: <Pine.LNX.4.44.0410230757580.4387-100000@netcore.fi>
References: <Pine.LNX.4.44.0410230757580.4387-100000@netcore.fi>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: John C Klensin <john-ietf@jck.com>
Content-Transfer-Encoding: 7bit

Pekka,

I'm copying newtrk on this because the last substantive sentence
of your abstract implies a profound change to the standards
process.  In particular, as I read it, for existing documents,
it implies a review process that is far more burdensome than
that contemplated for "cruft" -- someone needs to go through the
RFC file, identify "IETF documents" separately from individual
submissions, and then subject every document of the former
category to a new Last Call and IESG reevaluation process if
there is the slightest hint of a  IPR claim.  I think that would
place virtually all of our basic protocols back on the table, as
well as causing complete IESG paralysis as we abruptly added
hundreds of documents to the Last Call and processing queues.

This, or some small variation on it, actually impresses me as a
great idea going forward.  However, I suggest that you need to
either drop the notion of applying the procedure to documents
already approved or that you reissue the I-D with some specifics
about how older documents might be identified and reviewed
without bringing the entire IETF to a screeching halt.

     john


--On Saturday, 23 October, 2004 07:59 +0300 Pekka Savola
<pekkas@netcore.fi> wrote:

> FYI --
> 
> There was a mention of this in the IETF list, so I decided to
> resurrect this draft.  This might end up as a July14
> experiment after IETF61. If you have opinions about this, I
> guess you should speak up.
> 
> ---------- Forwarded message ----------
>...
 
> 	Title		: Mentioning Intellectual Property Rights
> Considerations in Last Calls 	Author(s)	: P. Savola
> 	Filename	: draft-savola-ipr-lastcall-04.txt
> 	Pages		: 9
> 	Date		: 2004-10-22
> 	
> This memo describes an additional policy with last calls
> regarding Intellectual Property Rights (IPR) disclosures or
> other knowledge of IPR.  The existence and the pointer to the
> IPR disclosures or an indication of non-existence of knowledge
> of such disclosures must be mentioned in all IETF last calls
> and should be mentioned in working group last calls.
> Additionally, all documents under the IETF change control for
> which a last call prior to the approval was not required and
> IPR disclosures are known, must now be either last-called or
> rejected.  This memo updates RFC 2026 and RFC 2418.
>...



.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html