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

Matthew Lepinski <mlepinski.ietf@gmail.com> Fri, 30 January 2015 16:22 UTC

Return-Path: <mlepinski.ietf@gmail.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 A58951A1B47 for <ietf@ietfa.amsl.com>; Fri, 30 Jan 2015 08:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 PjkWTGX56tCf for <ietf@ietfa.amsl.com>; Fri, 30 Jan 2015 08:21:59 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C7671A1AF4 for <ietf@ietf.org>; Fri, 30 Jan 2015 08:21:59 -0800 (PST)
Received: by mail-oi0-f49.google.com with SMTP id a3so35281805oib.8 for <ietf@ietf.org>; Fri, 30 Jan 2015 08:21:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3plJGA1aDaaVHTYx7ACmOhbE9D3x7qhdlsjLHAzaskE=; b=CrngehuqNTcSEwMARtI9/lZcImw9MtPbhpc4riv0CgyMdbEm2KzJ8DVOZc0352LSMT xE7woEAkIP9Qb4L/sRKnHDuEQJ3JaAGV5KmaOWiDdieh9odel/aZ5R7/auby5MifEywI mzvt6KKgIJPk77yDsujZeXktlKFB7e5vxxXxnR/sjXXZ/Q2kvRXHcsNR4L+t7mK0Na5+ bEcl0C0Xxi9olE/nBACJxLR6cQi2AukIxQDtoAR+9iJrEEsHkA3tTajCkssOmFBURpAh 3EMmYxaX+oDyIIiBmJeGnAh04hPXGFQvgYq5Hq7De8Zf97xRX4zl54W1lvp7VrfOUowU IQMw==
MIME-Version: 1.0
X-Received: by 10.182.84.225 with SMTP id c1mr4200746obz.68.1422634918495; Fri, 30 Jan 2015 08:21:58 -0800 (PST)
Received: by 10.202.135.17 with HTTP; Fri, 30 Jan 2015 08:21:58 -0800 (PST)
In-Reply-To: <54C79F50.20106@gondrom.org>
References: <54C79F50.20106@gondrom.org>
Date: Fri, 30 Jan 2015 11:21:58 -0500
Message-ID: <CANTg3aAueUYcJ8+7u0CyWesefAYBXOUiyhB6D6APY4dw-nTt4Q@mail.gmail.com>
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
From: Matthew Lepinski <mlepinski.ietf@gmail.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Content-Type: multipart/alternative; boundary="089e01183ed6f64bc7050de1007b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YIcP5U1PAZQpEOwrUezCoYii8t4>
Cc: IETF-Discussion list <ietf@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: Fri, 30 Jan 2015 16:22:01 -0000

It would be good to be able to support templates in the RFC series.

The proposed text from Tobias looks quite reasonable.

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
>
>