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> Wed, 21 January 2009 15:40 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 0EFBC28C0F3; Wed, 21 Jan 2009 07:40:52 -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 A09C628C0F6 for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 07:40:50 -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 teAjhAOwBapg for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 07:40:50 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 52A8E28C0F3 for <ietf@ietf.org>; Wed, 21 Jan 2009 07:40:50 -0800 (PST)
Received: (qmail 20210 invoked by uid 0); 21 Jan 2009 15:33:50 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.143.24) by woodstock.binhost.com with SMTP; 21 Jan 2009 15:33:50 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 21 Jan 2009 10:33:10 -0500
To: Doug Ewell <doug@ewellic.org>
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: <218FC843709642BD99EB307EC129D199@DGBP7M81>
References: <70873A2B7F744826B0507D4B84903E60@noisy> <54974382E5FF41D3A40EFDF758DB8C49@DGBP7M81> <20090112211809.515993A67EA@core3.amsl.com> <A2460A3CBF9453B10BC02375@PST.jck.com> <20090112221608.5659A3A67EA@core3.amsl.com> <7FCA5612-AACD-404A-A454-E72AB9A5F51E@softarmor.com> <5B38FE0B-B5C9-45CA-ABC4-245E95EF7E96@multicasttech.com> <218FC843709642BD99EB307EC129D199@DGBP7M81>
Mime-Version: 1.0
Message-Id: <20090121154050.52A8E28C0F3@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 >>>Given that we've historically weeded out the contributor-list on a

>>>document to "four or less", even if there were really dozens of 
>>>"contributors" at the alleged insistence of the RFC Editor, I 
>>>don't see how any older document or even a majority of new 
>>>documents-in-progress could be adapted to the new rules.
>>>
>>>This appears to require complete abandonment of all previous works 
>>>and "clean room" rewrites under the new terms.
>>
>>Even in this worse case scenario (which clearly won't be true in 
>>all cases), I think that that is only true for documents that need 
>>to be licensed outside of the IETF process.
>
>Is there any wording in RFC 5378 which states that the additional 
>burden imposed on RFC authors applies only to documents that are 
>intended to be licensed outside of the IETF process?  I realize this 
>may be the intent, but this is legal wording, where <ianal>the words 
>are binding and not the intent</ianal>.

That is one component of the proposed update to the Trust License 
Policy.  If the notice in 6.c.iii is in the document, the authors are 
telling the Trust that it may not have the rights outside the IETF 
Standards Process.  In this case, the Trust or anyone else that wants 
to make use outside the IETF Standards Process must obtain those 
rights directly from the copyright holders.

Russ 

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