Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
Sean Turner <turners@ieca.com> Thu, 29 January 2015 20:21 UTC
Return-Path: <turners@ieca.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 833D71A7022 for <ietf@ietfa.amsl.com>; Thu, 29 Jan 2015 12:21:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.567
X-Spam-Level:
X-Spam-Status: No, score=-0.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FSL_HELO_BARE_IP_2=1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 uI9EwwWam1BO for <ietf@ietfa.amsl.com>; Thu, 29 Jan 2015 12:21:36 -0800 (PST)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [69.93.243.11]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 234941A86E5 for <ietf@ietf.org>; Thu, 29 Jan 2015 12:21:33 -0800 (PST)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id 90AF02645EE44; Thu, 29 Jan 2015 14:21:32 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 7A5B32645EDAC for <ietf@ietf.org>; Thu, 29 Jan 2015 14:21:32 -0600 (CST)
Received: from [96.231.226.60] (port=50810 helo=192.168.1.2) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <turners@ieca.com>) id 1YGval-0000pX-DJ for ietf@ietf.org; Thu, 29 Jan 2015 14:21:31 -0600
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
From: Sean Turner <turners@ieca.com>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF632C5235F@eusaamb107.ericsson.se>
Date: Thu, 29 Jan 2015 15:21:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD61D3E8-E127-4D4B-B113-455E11C24ADD@ieca.com>
References: <54C79F50.20106@gondrom.org> <CAG4d1rcBknu2uxPXGmSWU=+YpycMKB+oY8chAn56ERC3ZY7h2Q@mail.gmail.com> <48E1A67CB9CA044EADFEAB87D814BFF632C5235F@eusaamb107.ericsson.se>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 96.231.226.60
X-Exim-ID: 1YGval-0000pX-DJ
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (192.168.1.2) [96.231.226.60]:50810
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7YW2UTcrvSRLJShuqU-ssK7zdk0>
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: Thu, 29 Jan 2015 20:21:37 -0000
+1 spt On Jan 27, 2015, at 13:48, Eric Gray <eric.gray@ericsson.com> wrote: > +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> 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 >
- Community Input on change to the Trust Legal Prov… Tobias Gondrom
- Re: Community Input on change to the Trust Legal … John C Klensin
- Re: Community Input on change to the Trust Legal … Joel M. Halpern
- Re: Community Input on change to the Trust Legal … Sam Hartman
- Re: Community Input on change to the Trust Legal … Alia Atlas
- RE: Community Input on change to the Trust Legal … Eric Gray
- Re: Community Input on change to the Trust Legal … Stephan Wenger
- Re: Community Input on change to the Trust Legal … John Levine
- Re: Community Input on change to the Trust Legal … Brian E Carpenter
- Re: Community Input on change to the Trust Legal … John Levine
- Re: Community Input on change to the Trust Legal … Sean Turner
- Re: Community Input on change to the Trust Legal … Matthew Lepinski
- Re: Community Input on change to the Trust Legal … John C Klensin
- Re: Community Input on change to the Trust Legal … Nico Williams
- Re: Community Input on change to the Trust Legal … Nico Williams
- Re: Community Input on change to the Trust Legal … Sam Hartman
- Re: Community Input on change to the Trust Legal … John C Klensin