RE: How IETF treats contributors
ned.freed@mrochek.com Wed, 01 September 2004 00:28 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 UAA17570; Tue, 31 Aug 2004 20:28:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2J0t-00044W-23; Tue, 31 Aug 2004 20:30:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IsQ-0001C4-T0; Tue, 31 Aug 2004 20:21:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Iij-0006Zf-2V for ietf@megatron.ietf.org; Tue, 31 Aug 2004 20:11:25 -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 UAA15850 for <ietf@ietf.org>; Tue, 31 Aug 2004 20:11:23 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com ([209.55.107.55]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Ikm-0003ZM-V6 for ietf@ietf.org; Tue, 31 Aug 2004 20:13:34 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01LEBHXX0X9S0087C0@mauve.mrochek.com> for ietf@ietf.org; Tue, 31 Aug 2004 17:11:14 -0700 (PDT)
Date: Tue, 31 Aug 2004 17:10:42 -0700
In-reply-to: "Your message dated Mon, 30 Aug 2004 15:18:17 -0700" <DAC3FCB50E31C54987CD10797DA511BA0AB9C1B6@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@windows.microsoft.com>
Message-id: <01LEBLH4LFTU0087C0@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Content-transfer-encoding: 7bit
References: <DAC3FCB50E31C54987CD10797DA511BA0AB9C1B6@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <hardie@qualcomm.com>, ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
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.3 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
> > 9. Acknowledgements > > > > Variations on the idea of using a DNS record to check the > > legitimacy > > of an email address have occurred multiple times. The earliest > > known > > work is [Vixie]; others include [RMX], [SPF] and [CallerID]. > > > > The current document borrows heavily from each of the above, > and > > incorporates ideas proposed by many members of the MARID > working > > group. The contributions of each of the above are gratefully > > acknowledged. > Ted, > My personal practice, when writing such acknowledgement sections, is to > write down the names of the individuals who contributed the idea, or > contributed significant comments to a draft. > It is true that if one follows references such as [RMX] one eventually > find the list of authors of the proposal, but they are still at least > one level of indirection away. The MARID draft could just as well say > something like "The earliest work was submitted to the IETF by Paul > Vixie [Vixie]; others include ..." ASCII bits are cheap. This would be a very reasonable thing to do IMO. Ned _______________________________________________ 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