Re: RFC 5378 "contributions"
Marshall Eubanks <tme@multicasttech.com> Thu, 15 January 2009 13:24 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 A42633A696B; Thu, 15 Jan 2009 05:24:26 -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 A10903A696B for <ietf@core3.amsl.com>; Thu, 15 Jan 2009 05:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.382
X-Spam-Level:
X-Spam-Status: No, score=-103.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 YBoFFbddOSjd for <ietf@core3.amsl.com>; Thu, 15 Jan 2009 05:24:24 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 96F073A68D8 for <ietf@ietf.org>; Thu, 15 Jan 2009 05:24:24 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14257053; Thu, 15 Jan 2009 08:24:04 -0500
Message-Id: <0882F36F-6800-4E5E-BC9F-EBA8C7D1877D@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <CFD40B6FB7A87F31F3D9CABE@PST.JCK.COM>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: RFC 5378 "contributions"
Date: Thu, 15 Jan 2009 08:24:08 -0500
References: <50E312B117033946BA23AA102C8134C6031B3970@SDCPEXCCL2MX.wilmerhale.com> <20090115035256.GB81320@shinkuro.com> <CFD40B6FB7A87F31F3D9CABE@PST.JCK.COM>
X-Mailer: Apple Mail (2.930.3)
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"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Jan 15, 2009, at 7:09 AM, 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 John, I am not a lawyer, you are (AFAIK) not a lawyer, and if the IETF counsel says otherwise, I would just let this one lie. The reason why I do not agree with this reasoning is that these rights are claimed through authorship. If I do not claim authorship in your draft because you use my text, when I have ample opportunity to do so, then I have (in my opinion) effectively lost them, especially in this context (where there is a note well, an assumption of joint contributions, etc.). In another context, I know that this is why songwriters can be so vociferous about getting their name as co-authors when a song is published - that is how they get royalties. Yes, I am sure that there are corner cases here, but one thing I have found about legal affairs is that there are always corner cases. No legal matter is ever sewn up 100%, and judges actually do take into consideration when things are done "on advise of counsel." We have it, we should use it. Regards Marshall > > 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. > > > 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. 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 _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- RFC 5378 "contributions" Randy Presuhn
- Re: RFC 5378 "contributions" Brian E Carpenter
- Re: RFC 5378 "contributions" Marshall Eubanks
- Re: RFC 5378 "contributions" Paul Hoffman
- Re: RFC 5378 "contributions" Contreras, Jorge
- Re: RFC 5378 "contributions" Andrew Sullivan
- Re: RFC 5378 "contributions" Randy Presuhn
- Re: RFC 5378 "contributions" Tom.Petch
- Re: RFC 5378 "contributions" Harald Alvestrand
- Re: RFC 5378 "contributions" Martin Duerst
- Re: RFC 5378 "contributions" John C Klensin
- Re: RFC 5378 "contributions" TSG
- Re: RFC 5378 "contributions" Marshall Eubanks
- Re: RFC 5378 "contributions" Andrew Sullivan
- Re: RFC 5378 "contributions" Theodore Tso
- Re: RFC 5378 "contributions" Theodore Tso
- RE: RFC 5378 "contributions" Contreras, Jorge
- Re: RFC 5378 "contributions" John Levine
- Re: RFC 5378 "contributions" Marshall Eubanks
- Re: RFC 5378 "contributions" TSG
- Re: RFC 5378 "contributions" TSG
- Re: RFC 5378 "contributions" Theodore Tso
- Re: RFC 5378 "contributions" Doug Ewell
- Re: RFC 5378 "contributions" Simon Josefsson
- Re: RFC 5378 "contributions" Tom.Petch
- Re: RFC 5378 "contributions" Marshall Eubanks
- Re: RFC 5378 "contributions" Marshall Eubanks
- Re: RFC 5378 "contributions" Theodore Tso
- Re: RFC 5378 "contributions" SM
- Re: RFC 5378 "contributions" Simon Josefsson
- Re: RFC 5378 "contributions" Tom.Petch
- Re: RFC 5378 "contributions" John C Klensin
- Re: RFC 5378 "contributions" Theodore Tso
- Re: RFC 5378 "contributions" Simon Josefsson
- Re: RFC 5378 "contributions" Theodore Tso
- Re: RFC 5378 "contributions" Simon Josefsson
- Re: RFC 5378 "contributions" TSG
- Re: RFC 5378 "contributions" Tom.Petch