IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 28 January 2015 04:23 UTC

Return-Path: <brian.e.carpenter@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 6B3E21A1BAC for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 20:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 Snpnzf8VAiLh for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 20:23:05 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73F5D1A1BC5 for <ietf@ietf.org>; Tue, 27 Jan 2015 20:23:05 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id y10so23116095pdj.9 for <ietf@ietf.org>; Tue, 27 Jan 2015 20:23:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Qr6LMqjpIjJ6vt0O4uptsw4x6LmNrqVxxjgbaU1Nn/A=; b=xBJA9eBwaMT96sYE0kyU/GXpZ5w+MMMCzgO1I1eia/qFtRlI48IQVJnXskyahqXbOS wdwg2289pPO4IzkfcTLUE3QRAhTz4922Xq3+SJhy/lp90arDwNWExuey5mMqXqw3qNJ1 pORoZb6qWen+7+i+dJnxhVGrrckTh3aQ/FTxNhzP1yE7M2EmeauhEoqXPiZEjtbk2v3D 1xALZ4GnWSnF3wpH0tTOzhIksuFgI5b226YWcdDcXQBocd4vb0+VjQZMeive0Mq9ySBq QIHx7RyoTJGsp1h3uYbkjgkVl8aQ8g65mlCta/rjWNETl1RUhrJZ1nEvdFRgUJfRlzCB rDrQ==
X-Received: by 10.69.16.99 with SMTP id fv3mr2477926pbd.98.1422418984790; Tue, 27 Jan 2015 20:23:04 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id jc4sm3092706pbd.71.2015.01.27.20.23.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Jan 2015 20:23:03 -0800 (PST)
Message-ID: <54C86423.4080509@gmail.com>
Date: Wed, 28 Jan 2015 17:22:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
References: <20150128031639.17437.qmail@ary.lan>
In-Reply-To: <20150128031639.17437.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uiNWKFutuPxCK4R7KViPO7JKOik>
Cc: john-ietf@jck.com
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: Wed, 28 Jan 2015 04:23:07 -0000

On 28/01/2015 16:16, John Levine wrote:
>> 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.
> 
> It does, but I don't see what practical problem this causes.
> 
> Templates are functional, so the copyrights on them are pretty thin in
> the first place, and once extracted from the RFC without the rest of
> the RFC text, what do we care?  We've allowed modified versions of
> code components for quite a while, and as far as I know that hasn't
> caused any problems for the IETF.

I agree, and in fact my first reaction was to wonder why we don't just
lump templates in with code.

    Brian

v2.23.0 | Report a Bug | By Email