RE: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem

"Ed Juskevicius" <edj.etc@gmail.com> Tue, 13 January 2009 00:27 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C38D328C12F; Mon, 12 Jan 2009 16:27:41 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3D3628C12F; Mon, 12 Jan 2009 16:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CInwd1lj7oU8; Mon, 12 Jan 2009 16:27:39 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by core3.amsl.com (Postfix) with ESMTP id 6283728C12B; Mon, 12 Jan 2009 16:27:39 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so4916521ywj.49 for <multiple recipients>; Mon, 12 Jan 2009 16:27:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:in-reply-to:x-mimeole:thread-index; bh=Nj8eabvuxG3vv/fQEVobgRX6jBmn/0WLCo5lTYo0HcA=; b=uBp/zR8rZMpg11/8/yNa8yBnCUPelzjjFBn3H+LtjfRc1hnDHnKgUvCQXjGR3nHwL7 4QM8kUINIiz4Ez6aXew75VC4xWWCC5fBoSt4T6epidO/242FsIIFcQ34Ugnt+Imz+kMV TB/xbVBPB8k850RM1rzKFx297zr2gnAHiTE3Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :x-mimeole:thread-index; b=LEMSAYkkVs31iCQYkgcRuyiC+Ay9XUnDcMq1/FfepmTKQpdM+AKyqsGIxnfzc4dmnW roFEk6FUHvtJf2pRX09QmWTvsO8V+i2l1BvPCbSsrSMG6dbl6yw372U75LjsmpmhPI9I BQfofiZwaCEwOXbeESs67/2Yc47KMRNcg4jPk=
Received: by 10.65.177.6 with SMTP id e6mr20301100qbp.97.1231806443903; Mon, 12 Jan 2009 16:27:23 -0800 (PST)
Received: from noisy (bas3-ottawa23-1088835964.dsl.bell.ca [64.230.81.124]) by mx.google.com with ESMTPS id 12sm22641306qbw.9.2009.01.12.16.27.20 (version=SSLv3 cipher=RC4-MD5); Mon, 12 Jan 2009 16:27:22 -0800 (PST)
From: Ed Juskevicius <edj.etc@gmail.com>
To: 'John C Klensin' <john-ietf@jck.com>
References: <FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com><49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi><6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA><p06240800c58d5466241b@[10.227.48.131]><DBAA71AA401E5398212B1E03@PST.jck.com> <4967CAA1.9020608@gmail.com><B2385D8E5F5BA599A174BD43@PST.jck.com><4967E348.7050300@joelhalpern.com><87d4evgu35.fsf@mocca.josefsson.org><20090110191055.GB31579@mit.edu><7D0E9557A84E06BFB4E120CA@PST.jck.com> <496905AF.7090209@gmail.com><345C76B329D94E644F9DF70C@PST.jck.com> <12E8A3A1E7F956ECB7BEF9A1@PST.jck.com>
Subject: RE: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
Date: Mon, 12 Jan 2009 19:28:22 -0500
Message-ID: <8F00D7D8BE904CFBA08FF5D659C0A8D6@noisy>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <12E8A3A1E7F956ECB7BEF9A1@PST.jck.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: Acl1Efo9S/p8eKvvQUKz+GwJfTUFigAAfSzQ
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John Klensin wrote:

> The intent, as ekr and I understand it and as I think your and Ed's
> note indicated, was to eliminate the requirement that authors make any
> assertions at all about work other than their own, much less requiring 
> that they guarantee those assertions.  

Correct!  That is indeed the purpose of the proposed "work-around" legend
text.

> So I strongly support the general thrust of ekr's proposed modified
> text rather than the text as posted.  

Thank You.  This is good feedback.

Regards,

Ed  J.

-----Original Message-----
From: trustees-bounces@ietf.org [mailto:trustees-bounces@ietf.org] On Behalf
Of John C Klensin
Sent: January 12, 2009 7:01 PM
To: Russ Housley
Cc: trustees@ietf.org; ietf@ietf.org
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review
and comments on a proposed Work-Around to the Pre-5378 Problem



--On Monday, January 12, 2009 17:24 -0500 Russ Housley
<housley@vigilsec.com> wrote:

> John:
> 
> I think that the cover note from the Chair of the IETF Trust,
> Ed Juskevicius, included the vast bulk of the information that
> you are requesting. 

Russ,  I think your note addresses several more of the issues I
was concerned about than Ed's note did.  Assuming that your note
represents the consensus of the Trustees where that is relevant,
I don't see any reason to quibble about that point.

More to the point, while I think I disagree with parts of your
analysis, the disagreements, if any, are in areas that should
not block progress at this point, i.e., I can live with your
interpretation without any need to dispute those differences.

I do have a comment on (3) in context...

> (3)  "with the advice of Counsel, we believe that this fix
> represents
> a competent, best-efforts, legal-text representation of that
> principle
> and nothing else".
> 
> The cover note does not address all of these points.  The
> Trustees did seek legal advice, and Counsel fully support this
> work-around.  As you might imagine, Counsel was heavily
> involved in the discussions as well as the words themselves.
> The Trustees are trying to provide a near-term work-around
> within the current BCPs and nothing else.

Good. However, what I was looking for was assurance from Counsel
that he had done an in-depth analysis of the language and
concluded that it was both necessary and sufficient to address
and solve (or work around) the problem.  That is different from
"supporting the work-around", "involved in the discussions", etc.

Ekr's recent note points out part of the problem that I believe
that Counsel should have caught (and would have caught if asked
the right question).   The intent, as ekr and I understand it
and as I think your and Ed's note indicated, was to eliminate
the requirement that authors make any assertions at all about
work other than their own, much less requiring that they
guarantee those assertions.  Perhaps, for a document some of
whose text predates 5378, I am certain about the origins of all
of the text and can make assertions about it and about whether
or not everyone has signed off.  But, if I am not, I should not
be required to make assertions, one way or the other, that
require that I claim and take responsibility for, complete
knowledge.  Even if I am willing to take responsibility for
identify all of the relevant Contributors, unless there is a
compelling reason that I haven't heard yet, we should not be
requiring authors to search the Trust's archives to determine
who has signed off, who has not, and whether the statements they
made in signing off are sufficient to meet the conditions of
5378 as modified by the workaround.

So I strongly support the general thrust of ekr's proposed
modified text rather than the text as posted.  If a change is
made that is consistent with the general principle that authors
who know that they are working on documents that contain
pre-5378 text, text about which others might make claims, do not
need to make any affirmative assertions at all about the IPR
status of that other work.

      john



_______________________________________________
Trustees mailing list
Trustees@ietf.org
https://www.ietf.org/mailman/listinfo/trustees

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf