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

John C Klensin <john-ietf@jck.com> Tue, 27 January 2015 14:56 UTC

Return-Path: <john-ietf@jck.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 EAEAB1A6F2D for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 06:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 jutfDeKN5kgq for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 06:56:52 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B05B21A1A25 for <ietf@ietf.org>; Tue, 27 Jan 2015 06:56:52 -0800 (PST)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YG7ZT-000Fxb-43 for ietf@ietf.org; Tue, 27 Jan 2015 09:56:51 -0500
Date: Tue, 27 Jan 2015 09:56:46 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
Message-ID: <69BB994D3A6C37396C70C9BC@JcK-HP8200.jck.com>
In-Reply-To: <54C79F50.20106@gondrom.org>
References: <54C79F50.20106@gondrom.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eNU18HCNBr9735Pk-seMdwsGiY8>
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 14:56:54 -0000


--On Tuesday, January 27, 2015 14:23 +0000 Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:

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

Tobias,

IANAL (other disclaimers incorporated by hand-waving), but a
plain-English reading of this indicated that the text gives
permission to modify the text of the template itself.  That
raises all of the issues that caused us to try to make
enforceable copyright claims on the RFC series in the first
place-- someone could use such derived text (maliciously or not)
to mislead others about IETF statements, intent, and
requirements.

I'll leave it to the Trustees and Counsel to determine whether
that threat is worth worrying about, but it seems to me it would
be easy, if desired, to allow copying but restrict it, either by
intended use or by not allowing the template text to be
modified, only that the template be filled in and used as
specified, or both.

     john