Re: RFC 5378 "contributions"

"Randy Presuhn" <randy_presuhn@mindspring.com> Thu, 15 January 2009 04:00 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 AE1FE3A6809; Wed, 14 Jan 2009 20:00:44 -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 128903A6809 for <ietf@core3.amsl.com>; Wed, 14 Jan 2009 20:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 v3DrKSqxEX+m for <ietf@core3.amsl.com>; Wed, 14 Jan 2009 20:00:43 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 1005B3A679F for <ietf@ietf.org>; Wed, 14 Jan 2009 20:00:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=N86NMCRIYomBfd9o80cRk2aY2Jh6iZSvQ10FpIeC7QzRD0GSUF9aFXnSR4K3c/ny; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [66.167.206.176] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1LNJP9-0001ql-UY for ietf@ietf.org; Wed, 14 Jan 2009 23:00:28 -0500
Message-ID: <000a01c976c6$3cd89980$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
References: <50E312B117033946BA23AA102C8134C6031B3970@SDCPEXCCL2MX.wilmerhale.com>
Subject: Re: RFC 5378 "contributions"
Date: Wed, 14 Jan 2009 20:03:33 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173cf4ffcce22510ca10e2deb4cf0b05106350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.167.206.176
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

Hi -

Thanks for the clarification.  Does this mean that if a WG
really has no concern that the documents it's working on would be
spun off to another organization, then it doesn't need to
worry about tracking down "contributors"?

Randy

> From: "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
> To: <randy_presuhn@mindspring.com>; <ietf@ietf.org>
> Sent: Wednesday, January 14, 2009 5:33 PM
> Subject: Re: RFC 5378 "contributions"
>
> Re: RFC 5378 "contributions"No, absolutely not.  Use of pre-5378 materials in the IETF standards process has never been an issue,
only use outside the IETF is problematic (ie, allowed under 5378 but not the earlier rules).
>
>
> ----- Original Message -----
> From: ietf-bounces@ietf.org <ietf-bounces@ietf.org>
> To: IETF Discussion <ietf@ietf.org>
> Sent: Wed Jan 14 19:32:27 2009
> Subject: RFC 5378 "contributions"
>
> 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.
>
> Randy
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>


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