IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Wed, 28 January 2015 04:41 UTC

Return-Path: <johnl@taugh.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 2EDFE1ACD1A for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 20:41:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 t3Vz4k21orls for <ietf@ietfa.amsl.com>; Tue, 27 Jan 2015 20:41:29 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E49701A8749 for <ietf@ietf.org>; Tue, 27 Jan 2015 20:41:28 -0800 (PST)
Received: (qmail 10450 invoked from network); 28 Jan 2015 04:41:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=28d1.54c86877.k1501; i=johnl-iecc.com@submit.iecc.com; bh=u7aa3qmsonVQV79zDloZAH9ZyHmZeD+BnPCbGSaD6yA=; b=Eejb44XspWYwJPbntCbfj0QtHsXTYnkvfRpgTaPpJ544cOdwOM6H6p/nKckVM6gFS7qQT9J6Iokpj1q2EyNo4RrYUX0Nq2U40U+a6y76kFrcstaDaxpYR1eOJMtGkiuZb7KzQeu0C63QUhGSNPrAyQqCxqYuYHqlr9YvHNsKzjWVX6gUVkeNczzhvLfTu7O4zQGqinWQcQXw+dCk+avDPCFVXnJuoMcqcvDoS8kBAmr0nc7OzNASeDJlIEwz4f+5
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=28d1.54c86877.k1501; olt=johnl-iecc.com@submit.iecc.com; bh=u7aa3qmsonVQV79zDloZAH9ZyHmZeD+BnPCbGSaD6yA=; b=cYEKn9BI4IGfpJcTzSD+Ij/BDmb6xSHeQ16IM/lmVQQWw6UjycAg36Cm7rs9ECYOynhhHPgMrq6FI3/jcV+IMZu4bt2k3ShSEkzS1jGSO7/U/BmUgW4V6z3Z0mNbZoGipdcv5C6QFd1TkYL8SDKZm/qtyOrs9CHX+mzzoqTxFxrZzXoVw/Js8583xK90JmOVeSn/EvGqgTGuhd5z1l9CLqphJTP8kyzIRzVAWPOirOEJjk5utNlSzhDC1qBbQszL
Received: from [IPv6:2604:6000:140d:3a:107b:6e0:1b39:92ce] ([IPv6:2604:6000:140d:3a:107b:6e0:1b39:92ce]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2/X.509/AEAD, johnl@iecc.com) via TCP6; 28 Jan 2015 04:41:27 -0000
Date: Tue, 27 Jan 2015 23:41:24 -0500
Message-ID: <20150127234124.10448.qmail@submit.iecc.com>
From: John Levine <johnl@taugh.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_WZROixP3t_dcyvCcCt-OKvZiZw>
Cc: john-ietf@jck.com, 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: Wed, 28 Jan 2015 04:41:30 -0000

Code demands a license acknowledgement which seems excessive for a template.On Jan 27, 2015 11:22 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
> 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