Re: RFC 5378 "contributions"

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 15 January 2009 00:39 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C4FB3A69A9; Wed, 14 Jan 2009 16:39:23 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4263F3A69A9 for <ietf@core3.amsl.com>; Wed, 14 Jan 2009 16:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vAD7s1ySx30s for <ietf@core3.amsl.com>; Wed, 14 Jan 2009 16:39:21 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by core3.amsl.com (Postfix) with ESMTP id 4BDF83A682C for <ietf@ietf.org>; Wed, 14 Jan 2009 16:39:21 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so927945wfd.31 for <ietf@ietf.org>; Wed, 14 Jan 2009 16:39:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4J80/sDcA/QYwxSkjVHIsweMxfGAWjh67+jzo3MJLRE=; b=Y87bHxeIsb62KCBg0o5zysx1UvKv0/cKKslHCWGzcGQDP6nMCtSlmRbhwBOxOLvxY6 REln9oOhINL1ptTbe/6buga5zgVXBgEs/iiHp7XQ5ZNw480vGjOV6emoAzuWZVW11XbP I0VXblXfbrYuJkNTOoDRfsHzaNTDukuJ0wL0I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=uKUVuYw+dYS7U/JLvNqEShrGGjzlK3C4xVdRVi0J375Q/rnfp058U0R+MKpRYHKyzs 8xuezgngHOrr5/Vfas4F3cOccyBZIxbTg50TnkEb8GAa/tAyKyC1eflJrZkrArxxp2ii PMo7Wc8RjYUZlxp/rjFIcq5tZLIWgC1/4b918=
Received: by 10.142.174.18 with SMTP id w18mr227473wfe.303.1231979946106; Wed, 14 Jan 2009 16:39:06 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 30sm2573001wfg.5.2009.01.14.16.39.04 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Jan 2009 16:39:05 -0800 (PST)
Message-ID: <496E85A1.8090908@gmail.com>
Date: Thu, 15 Jan 2009 13:38:57 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: RFC 5378 "contributions"
References: <001201c976a8$bee790c0$6801a8c0@oemcomputer>
In-Reply-To: <001201c976a8$bee790c0$6801a8c0@oemcomputer>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 2009-01-15 13:32, Randy Presuhn wrote:
> Hi -
> 
> I originally asked this question on the WG chairs' list, and
> was asked to ask again here...
> 
> The discussion about RFC 5378 (what little I've been able to
> understand of it, anyway) has focussed on I-Ds and RFCs.
> However, the definition of "contribution" in that document
> includes, among other things, mailing list discussions.
> 
> Does this mean that we need to get contributor permission
> before using, for example, material from a pre-5378 RFC in
> a mailing list discussion, or before including text from a
> pre-5378 email posting in an internet draft?
> 
> This seems really silly, but that's what the discussion is
> starting to sound like to me.

IANAL, but it seems to me that we should proceed on the assumption
that this would fall under fair use provisions. Anything else
would seem unreasonable to me.

It also seems to me that a WG Last Call on a draft containing the
new boilerplate would act as fair warning to all participants,
and if they don't object, they've effectively consented. But
again, IANAL. IJWTGMWD (I just want to get my work done).

    Brian
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf