Re: RFC 5378 "contributions"

TSG <tglassey@earthlink.net> Thu, 15 January 2009 17:34 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 941D13A6A35; Thu, 15 Jan 2009 09:34:37 -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 C98923A68C2 for <ietf@core3.amsl.com>; Thu, 15 Jan 2009 09:34:35 -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 aUdgEM41J22B for <ietf@core3.amsl.com>; Thu, 15 Jan 2009 09:34:34 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 5FA863A6A35 for <ietf@ietf.org>; Thu, 15 Jan 2009 09:34:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=B6eEFW0BD2y3kpsWYOkf99g7EubjnFwEVqA/NJ//85hAi4uMR8nz1Aw4+xvMBD1x; 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 [64.125.79.23] (helo=[192.168.0.32]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1LNW6i-0005TL-1s; Thu, 15 Jan 2009 12:34:16 -0500
Message-ID: <496F7398.7030104@earthlink.net>
Date: Thu, 15 Jan 2009 09:34:16 -0800
From: TSG <tglassey@earthlink.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: RFC 5378 "contributions"
References: <50E312B117033946BA23AA102C8134C6031B3970@SDCPEXCCL2MX.wilmerhale.com> <20090115035256.GB81320@shinkuro.com> <CFD40B6FB7A87F31F3D9CABE@PST.JCK.COM>
In-Reply-To: <CFD40B6FB7A87F31F3D9CABE@PST.JCK.COM>
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79b73e5ca0fb7929fe3f34c40082ce20fb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.125.79.23
Cc: 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

John C Klensin wrote:
> I have to agree with Andrew and Tom.
>
> If someone stood up in a WG prior to whenever 5378 was
> effective* and made a suggestion of some length, or made a
> lengthy textual suggestion on a mailing list, and I copied that
> suggestion into a draft without any paraphrasing, a plain-sense
> reading of 5378's definition of "Contributor" means that I have
> to go back, find that person, and get permission to post that
> draft today (without a disclaimer), just because, in making the
> posting, I'm asserting that rights are in place that were not
> granted when the Contribution was made. 
>   
Correct.
>
>     john
>
> * I've said this several times before, but neither common sense
> nor fairness permits the IETF to say "RFC 5378 became effective
> when it was published the first week in November, therefore any
> comments, contributions or drafts that appeared after that date
> constitute grants of permission under 5378's rules" ...
> especially in the absence of any specific notice to that effect
> on relevant mailing lists, the presence of a Note Well in the
> IETF registration packet that referred to the old rules, etc.
> Those of us who trust that common sense interpretation (or who
> have been given legal advice that the odds of a judge accepting
> an early-November date contrary to that interpretation are
> fairly small) need to behave as if we cannot assume that
> Contributions made before late November or early December do not
> imply permission to use the Contributions under 5378 rules.
>
> --On Wednesday, January 14, 2009 22:52 -0500 Andrew Sullivan
> <ajs@shinkuro.com> wrote:
>
>   
>> On Wed, Jan 14, 2009 at 08:33:35PM -0500, Contreras, Jorge
>> wrote:
>>     
>>> No, absolutely not.&nbsp; 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).
>>>       
>> Why is the actual situation of the use relevant?
>> "Contribution" is defined in section 1a of RFC 5378, and it
>> plainly says that mailing list posting and anything one says
>> at the microphone in any meeting is included in the
>> definition.  In section 5.1, RFC 5378 says that, by submitting
>> the Contribution, the Contributor is "deemed to have agreed
>> that he/she has obtained the necessary permissions" to enter
>> into the agreement allowing the IETF to use the Contribution
>> according to the new rules.
>>
>> So, just because the Contribution doesn't _happen_ to end up
>> in use outside the IETF by virtue of the IETF's actions does
>> not mean that a Contributor doesn't have to obtain the rights
>> to allow such re-use.  I believe that the _intent_ of 5378 is
>> ...
>>     
>
> _______________________________________________
> 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