Re: RFC 5378 "contributions"

TSG <tglassey@earthlink.net> Fri, 23 January 2009 20:13 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 5874D3A69AB; Fri, 23 Jan 2009 12:13:13 -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 928383A69AB for <ietf@core3.amsl.com>; Fri, 23 Jan 2009 12:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 dO3+3sSD2T5j for <ietf@core3.amsl.com>; Fri, 23 Jan 2009 12:13:09 -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 4F55F3A691A for <ietf@ietf.org>; Fri, 23 Jan 2009 12:13:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=fNLQ5aQDmJWX9PwvPL5mBv09Z5G151d2ez8h+WseaJ1G8uDAo/coTbauZP23SWjr; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.66] (helo=[192.168.1.101]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1LQSOZ-0002mP-Ro; Fri, 23 Jan 2009 15:12:51 -0500
Message-ID: <497A24C4.4080707@earthlink.net>
Date: Fri, 23 Jan 2009 12:12:52 -0800
From: TSG <tglassey@earthlink.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
Subject: Re: RFC 5378 "contributions"
References: <50E312B117033946BA23AA102C8134C6031B3970@SDCPEXCCL2MX.wilmerhale.com>
In-Reply-To: <50E312B117033946BA23AA102C8134C6031B3970@SDCPEXCCL2MX.wilmerhale.com>
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7999d06d4921d45afc2cc5fbacd61aec0d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.66
Cc: randy_presuhn@mindspring.com, 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org Contreras, Jorge wrote:

>
> 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).
>
Jorge - if the contributor's in a RC2026 controlled submission choose 
NOT to allow the new licensing models, then you are saying that the 
IETF's new rules apply?

If not specifically - which rules would apply. The point is that 
contracts require that the people being bound by them fully understand 
the terms and conditions, and if they don't then their gifts are faulty 
at best.

Is this or is it not true - and if not why Counsel

Todd Glassey
>
>
>
> ----- 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
>   
> ------------------------------------------------------------------------
>
>
> Internal Virus Database is out of date.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.176 / Virus Database: 270.10.4/1880 - Release Date: 1/7/2009 8:49 AM
>
>   

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