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

Nico Williams <nico@cryptonector.com> Tue, 17 February 2015 22:32 UTC

Return-Path: <nico@cryptonector.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 DE1941A88B6 for <ietf@ietfa.amsl.com>; Tue, 17 Feb 2015 14:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.855
X-Spam-Level:
X-Spam-Status: No, score=0.855 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] 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 YhdAhF6v2RRk for <ietf@ietfa.amsl.com>; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
Received: from homiemail-a77.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D4FCC1A1B3A for <ietf@ietf.org>; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
Received: from homiemail-a77.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTP id 98D379406D for <ietf@ietf.org>; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=/BAUkjqQAk+YxOJjaZZ8 diw6R7w=; b=FoZ8UClzYLH5IaVIdbq66wiJ1xLCDvIjWD9HapmlglAwkHfe7hWq UGEShC8bbxPh6zKmaT519D3nvR4um45m4bqouvtAkKNZrjguQj+hgy4KWFGl3IOh xq9ewQVGX2RD5HDRZkrmQr/Co1Atr3luyGH2sc8KwAViyjzjx7hfeIY=
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com [209.85.213.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTPSA id 887AA9405E for <ietf@ietf.org>; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
Received: by mail-ig0-f170.google.com with SMTP id l13so44703767iga.1 for <ietf@ietf.org>; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.27.143 with SMTP id b137mr12784843iob.76.1424212357257; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
Received: by 10.64.130.66 with HTTP; Tue, 17 Feb 2015 14:32:37 -0800 (PST)
In-Reply-To: <tsl7fw8jkur.fsf@mit.edu>
References: <54C79F50.20106@gondrom.org> <69BB994D3A6C37396C70C9BC@JcK-HP8200.jck.com> <tsl7fw8jkur.fsf@mit.edu>
Date: Tue, 17 Feb 2015 16:32:37 -0600
Message-ID: <CAK3OfOgo1q0uXnZmdCQPqju9czdrj64VhMieDW7BWWb-YZv-cw@mail.gmail.com>
Subject: Re: Community Input on change to the Trust Legal Provisions to accommodate the inclusion of RFC Templates
From: Nico Williams <nico@cryptonector.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6xp0zROHw_eFOgcjzZeeH4G_xls>
Cc: "ietf@ietf.org" <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: Tue, 17 Feb 2015 22:32:39 -0000

Doesn't a filled-in template stop being a template?  Can't there be
two claims made, one about the template itself, and one about
filled-in templates?  Surely we might want to make strong copyright
claims about empty templates while allowing some other entity (the
submitter perhaps, or the recipient of a filled-in template) to claim
copyrights on filled-in templates?

Nico
--