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

Russ Housley <housley@vigilsec.com> Tue, 13 January 2009 17:08 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 9F1DA3A6947; Tue, 13 Jan 2009 09:08:13 -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 B72313A6947 for <ietf@core3.amsl.com>; Tue, 13 Jan 2009 09:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 X+SWenw1bo-W for <ietf@core3.amsl.com>; Tue, 13 Jan 2009 09:08:10 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 94AAA3A688E for <ietf@ietf.org>; Tue, 13 Jan 2009 09:08:10 -0800 (PST)
Received: (qmail 2205 invoked by uid 0); 13 Jan 2009 17:07:51 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.143.189) by woodstock.binhost.com with SMTP; 13 Jan 2009 17:07:51 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 13 Jan 2009 12:07:47 -0500
To: John C Klensin <john-ietf@jck.com>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
In-Reply-To: <12E8A3A1E7F956ECB7BEF9A1@PST.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>
Mime-Version: 1.0
Message-Id: <20090113170810.94AAA3A688E@core3.amsl.com>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

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.

Counsel certainly reviewed the text, but like many groups, there was 
input from several individuals coming in at roughly the same 
time.  One of the portions the text that EKR is concerned about 
resulted from edits that I suggested.  I do not agree with some 
aspects of his interpretation, but that is not important because I 
think his suggested words are even better.  This is the point of the 
community review.  I'm pleased to support them.

Russ

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