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

Tobias Gondrom <tobias.gondrom@gondrom.org> Tue, 27 January 2015 14:23 UTC

Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971831A8757; Tue, 27 Jan 2015 06:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.665
X-Spam-Level:
X-Spam-Status: No, score=-96.665 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=1.951, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 5Qu9_0YIrDAD; Tue, 27 Jan 2015 06:23:15 -0800 (PST)
Received: from lvps5-35-241-16.dedicated.hosteurope.de (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48A281A8749; Tue, 27 Jan 2015 06:23:15 -0800 (PST)
Received: from [163.119.49.29] (unknown [163.119.49.29]) by lvps5-35-241-16.dedicated.hosteurope.de (Postfix) with ESMTPSA id 6F5F663034; Tue, 27 Jan 2015 15:23:13 +0100 (CET)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=cpCBrp0OJxeftsX/wo8/EpIhxqk8FDePDGDf7G/Ov2DFMT1xH4StHluU5lczHtnr3GwJiJsg/KHs78th+Ly2c36m6KxGEc387xgBoqin+Y+95qq2yyz3y2p+68saBuwlDh9LQ9AMxEyz+aHwSKYsQPIba701hkkIl8NzR7xqUw8=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
Message-ID: <54C79F50.20106@gondrom.org>
Date: Tue, 27 Jan 2015 14:23:12 +0000
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: ietf@ietf.org, ietf-announce@ietf.org
Subject: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/i9kryXy1nukC1nfombHMpc1O4c8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 14:23:17 -0000

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