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

Eric Gray <eric.gray@ericsson.com> Tue, 27 January 2015 18:48 UTC

Return-Path: <eric.gray@ericsson.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 D0D0A1A86DE; Tue, 27 Jan 2015 10:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 AaCCeFVVU_mz; Tue, 27 Jan 2015 10:48:54 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33F5F1A8547; Tue, 27 Jan 2015 10:48:54 -0800 (PST)
X-AuditID: c618062d-f79376d000000ceb-4f-54c78ab8e6ae
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id CA.5A.03307.8BA87C45; Tue, 27 Jan 2015 13:55:21 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0195.001; Tue, 27 Jan 2015 13:48:52 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Alia Atlas <akatlas@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: RE: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
Thread-Topic: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
Thread-Index: AQHQOjzZex3GHR2kHkKag9zpP1tSyJzUl+KA//+3ZYA=
Date: Tue, 27 Jan 2015 18:48:52 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF632C5235F@eusaamb107.ericsson.se>
References: <54C79F50.20106@gondrom.org> <CAG4d1rcBknu2uxPXGmSWU=+YpycMKB+oY8chAn56ERC3ZY7h2Q@mail.gmail.com>
In-Reply-To: <CAG4d1rcBknu2uxPXGmSWU=+YpycMKB+oY8chAn56ERC3ZY7h2Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_48E1A67CB9CA044EADFEAB87D814BFF632C5235Feusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyuXRPrO7OruMhBjt2CVt8eniJ2eLemels Fs82zmdxYPbYOesuu8eSJT+ZApiiuGxSUnMyy1KL9O0SuDJW9C9gK2iKqehumsHawHggsouR k0NCwETi47ojLBC2mMSFe+vZuhi5OIQEjjBKbP7/CcpZzijRd6qZHaSKTUBD4tidtYwgtohA kMTLnW2sXYwcHMwCphKrtvKBhIUFSiRWbLrGDFFSKrFv/182CNtK4vqzy2BjWARUJb5O+wc2 hlfAV6L39lYmkDFCAvkSf19IgYQ5BQIl/sw8DzaGEei276fWMIHYzALiEreezGeCuFlAYske iBoJAVGJl4//sULYihL7+qezQ1yWL9G6Pw1ik6DEyZlPWCYwis5CMmkWQtUsJFUQYU2J9bv0 IaoVJaZ0P2SHsDUkWufMZUcWX8DIvoqRo7Q4tSw33chgEyMwro5JsOnuYNzz0vIQowAHoxIP 74a+YyFCrIllxZW5hxilOViUxHkXPTgYIiSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFRePVH jwnzksy31Vik3n/ya+PlBPaQOiVJ/bM86Qz3zzk0nVwQ/uOY9hfPNK/Ah7q7Yi4ckzmb9fdO gvo6MfW0jOs12eph0ZUxD08syP6VvmoLr/ucbsvJGd2PbhYd/CAos+ZF9XFdxtWJB96q+Bq3 5+/IY/TrSLt0z0JnL2dBTbUNa90xr0wlluKMREMt5qLiRADYe+aIjAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/me5bbqgnOaoGViq7OG08Dm9bRgQ>
Cc: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
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 18:48:58 -0000

+1

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Tuesday, January 27, 2015 1:09 PM
To: IETF Discussion Mailing List
Cc: ietf-announce@ietf.org
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates

This looks very useful to me.

Thank you,
Alia

On Tue, Jan 27, 2015 at 9:23 AM, Tobias Gondrom <tobias.gondrom@gondrom.org<mailto:tobias.gondrom@gondrom.org>> 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