Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 27 January 2015 15:47 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FE01A8869; Tue, 27 Jan 2015 07:47:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIFF0hiuAnrM; Tue, 27 Jan 2015 07:47:12 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D88831A88D8; Tue, 27 Jan 2015 07:44:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id BBAAB2A0397; Tue, 27 Jan 2015 07:44:22 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-12.clppva.east.verizon.net [70.106.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 032E02A0393; Tue, 27 Jan 2015 07:44:21 -0800 (PST)
Message-ID: <54C7B213.3020307@joelhalpern.com>
Date: Tue, 27 Jan 2015 10:43:15 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ietf@ietf.org, ietf-announce@ietf.org
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
References: <54C79F50.20106@gondrom.org>
In-Reply-To: <54C79F50.20106@gondrom.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/O-Tjw0dKc8dR_p12uOvG1ntcZB8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
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>
X-List-Received-Date: Tue, 27 Jan 2015 15:47:14 -0000

That seems like a good idea.
Thank you.
Joel

On 1/27/15 9:23 AM, Tobias Gondrom wrote:
> Dear IETFers,
>
> The IETF Trust has been requested by the IESG and RFC Editor to provide
> a license in cases
> where RFCs contain Templates. The Trustees propose modifying the Trust
> Legal Provisions
> (TLP) based upon a need to extract and fill in text from RFCs that
> contain Templates.  E.g.
> the Internet-Draft draft-ietf-sidr-cps-04 contains a Template for others
> to copy and modify.
> Under the normal TLP provisions this would be considered a derivative
> work and not permitted.
>
> The current TLP is here:
> <http://trustee.ietf.org/license-info/IETF-TLP-4.pdf>.
>
> The Trustees’ response is a proposed change to the TLP that addresses
> the issue for this and
> future RFCs.  The change enables specific text in an RFC that is
> designated as a Template to be
> subject to a new provision in the TLP that says that extraction and
> modification are authorized.
>
> The Trustees are considering the following language changes to the TLP
> to permit the modification
> of RFC Templates:
>
> 9.  Template Text
>
> a.  Certain RFCs may contain text designated as “Template Text” by the
> inclusion of the following
> legend in the introduction to the RFC:
>
>      “This RFC contains text intended for use as a template as
> designated below by the markers
> <BEGIN TEMPLATE TEXT> and <END TEMPLATE TEXT> or other clear
> designation.  Such
> Template Text is subject to the provisions of Section 9(b) of the Trust
> Legal Provisions.”
>
> b.   In addition to the other rights granted under the TLP with respect
> to each RFC, the Trust grants
> to all interested persons a non-exclusive, royalty-free, worldwide,
> perpetual right and license under
> all copyrights and rights of authors to make, reproduce, publish and
> distribute modifications of the
> Template Text (e.g., to insert specific information in place of blanks
> or place-holders), and reproduce,
> modify and distribute such modified Template Text.
>
> We would like hear your thoughts on changing the Trust Legal Provisions
> to accommodate the inclusion
> of RFC Templates. Comments will be considered that are received through
> 25th February.
>
> Thank you for your assistance.
>
> Tobias Gondrom
> Chair, IETF Trust
>
>