Re: How IETF treats contributors
"william(at)elan.net" <william@elan.net> Wed, 01 September 2004 16:51 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09126; Wed, 1 Sep 2004 12:51:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2YMV-0004MW-EP; Wed, 01 Sep 2004 12:53:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2XNe-0006xL-I6; Wed, 01 Sep 2004 11:50:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2VLa-0007tI-DS for ietf@megatron.ietf.org; Wed, 01 Sep 2004 09:40:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10874 for <ietf@ietf.org>; Wed, 1 Sep 2004 09:40:17 -0400 (EDT)
Received: from sokol.elan.net ([216.151.192.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Ppp-0004B2-8y for ietf@ietf.org; Wed, 01 Sep 2004 03:47:13 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1]) by sokol.elan.net (8.12.11/8.12.5) with ESMTP id i817ri2x026833; Wed, 1 Sep 2004 00:53:45 -0700
Received: from localhost (william@localhost) by sokol.elan.net (8.12.11/8.12.5/Submit) with ESMTP id i817rfge026829; Wed, 1 Sep 2004 00:53:41 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Wed, 01 Sep 2004 00:53:41 -0700
From: "william(at)elan.net" <william@elan.net>
To: Paul Vixie <vixie@vix.com>, Dean Anderson <dean@av8.com>, ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0409010125050.9376-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0408312327460.16427-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: IETF MARID WG <ietf-mxcomp@imc.org>
Subject: Re: How IETF treats contributors
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
On Wed, 1 Sep 2004, Dean Anderson wrote: > This is a personal message, and doesn't qualify as being published. You > mentioned that you failed to follow up. That may be true. And that's why > you shouldn't be credited for originating the idea, and why David Green > and later Hadmut Danisch should be credited. They did the work, and > unlike you, took it to the IETF, and published it first. What you did in > secret is irrelevant. You should have published it. > > That's just your oversight. However, the Namedroppers archives show that > you __replied__ to Green's proposal. He was __first__ to publish. Maybe > you had Miller's draft in the wings since 1997. But you didn't get it it > first. To be able to claim that somebody first discovered it, the person would have to either file a patent (and have patent filing date prior to when the idea is first discussed on introduced in public) or to actually post an idea in public forum (either internet or journal, etc). So I hate to say it, but it looks like Dean Anderson is right and based on the facts presented David Green should be credited as first person that introduced what is now being developed by MARID. I recommend MARID chairs or authors of the drafts make an appropriate changes to the Acknoledgement section of both core and protocol drafts, something like this (text mostly combination of what was in protocol and core acknoledgements sections): This design is based on earlier work published in 2003 in [RMX] and [DMP] drafts (by Hadmut Danisch and Gordon Fecyk respectively). The idea of using a DNS record to check the legitimacy of an email address traces its ancestry to "Repudiating Mail-From" draft by Paul Vixie [Vixie] (based on suggestion by Jim Miller) and to "Domain-Authorized SMTP Mail" draft by David Green [Green] who first introduced this idea on namedroppes maillist in 2002. With references as follows: [Green] http://www.atm.tut.fi/list-archive/namedroppers/msg01636.html [Vixie] http://www.atm.tut.fi/list-archive/namedroppers/msg01638.html And these acknolidgements should probably be the same for both marid-protocol and marid-core drafts. Although protocol can list additional people who contributed to design of SPF while marid-core may list those who contributed to caller-id. P.S. While the original thread started was more general question on "How IETF treats contributors", this has now become a discussion that is very particular to MARID WG documents. I think it might be appropriate that those wishing to participate and discuss futher what acknolidgement section of MARID drafts should say, should do it on MARID mail list, rather then on IETF general list, especially since only discussions there would count and we are already on the last week of "Last Call" on these drafts. Please see http://www.ietf.org/html.charters/marid-charter.html for information on how to participate in this WG to discuss these documents. I also would like to urge other IETF participants to look at some of the latest archives as we're discussing number of problems with these drafts and its important for WG chairs to hear from wide audience as to if we should proceed considering how many problems have been found already. Of great importance are also issues due to IPR claimed by Microsoft for something that many on the list said is obvious derivitive from RFC2822. Microsoft also provided license which is overly restrictive and would not allow to support new protocol by any software that is licensed under GNU or simular public source licenses and this has raised questions as to if we should proceed futher with these drafts considering possibility that protocol may not be adapted by large portion of internet community. --- William Leibzon, Elan Networks: mailto: william@elan.net Anti-Spam Research Worksite: http://www.elan.net/~william/asrg/ _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Marc Blanchet
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- RE: How IETF treats contributors Christian Huitema
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors John Day
- Re: How IETF treats contributors Clint Chaplin
- RE: How IETF treats contributors Thomas Gal
- RE: How IETF treats contributors Nick Carter
- Re: How IETF treats contributors Olaf M. Kolkman
- RE: How IETF treats contributors Scott Bradner
- Re: How IETF treats contributors Vernon Schryver
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- RE: How IETF treats contributors ned.freed
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- Re: How IETF treats contributors Harald Tveit Alvestrand
- Re: How IETF treats contributors Nathaniel Borenstein
- Re: How IETF treats contributors ned.freed
- Re: How IETF treats contributors grenville armitage