RE: How IETF treats contributors
"Nick Carter" <Nick.Carter@think3.com> Tue, 31 August 2004 01:14 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 VAA20219; Mon, 30 Aug 2004 21:14:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1xFq-0005Ya-AS; Mon, 30 Aug 2004 21:16:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1xA5-0004N1-Kk; Mon, 30 Aug 2004 21:10:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1x7W-0003TI-AC for ietf@megatron.ietf.org; Mon, 30 Aug 2004 21:07:34 -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 VAA19747 for <ietf@ietf.org>; Mon, 30 Aug 2004 21:07:32 -0400 (EDT)
Received: from [66.147.157.90] (helo=USEX.think3.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1x9O-0005Oi-Gr for ietf@ietf.org; Mon, 30 Aug 2004 21:09:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Aug 2004 20:03:12 -0500
Message-ID: <B1F1256E2FAEA049B5F11549870302B16646DE@USEX.think3.com>
Thread-Topic: How IETF treats contributors
Thread-Index: AcSO6JGg00lCCKHcTHCJG52617iU2wAAdwHgAAKF+xA=
From: Nick Carter <Nick.Carter@think3.com>
To: ThomasGal@LumenVox.com, John Day <day@std.com>, Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
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: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
The problem being discussed is not a matter of disliking or liking spam, but rather the problem of solving it. On that note, I agree with Dean Anderson. Everyone hates SPAM, but that is not in question. I think credit should be given to the individual that properly documented the solution and not just to someone that noted an idea. You could contest it saying it was an excrescence of Vixie's work, but the details do not exist in Vixie's work. As noted with Dean, Vixies work is implausible and therefore credit should not be given. All work submitted should be punctilio and of protocol. Nick -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Thomas Gal Sent: Monday, August 30, 2004 7:12 PM To: 'John Day'; 'Hadmut Danisch'; ietf@ietf.org Subject: RE: How IETF treats contributors I agree with: "This isn't suppose to be an ego trip. If people really think the documents are important, they don't need their names on them. If they need their name on it, they are doing it for the wrong reasons." Not to mention the spirit of removing authorship. In reality I feel like this amounts to removing the title or something else that is so obviuosly a part of a document. Certainly there is no shame in being proud of your work, and nobody can help but feel a little miffed when something they did may have been overlooked. Seems fairly possible however that the people who are most interested in this subject probably know what really maters, and one way or another EVERYONE on the IETF list now knows. The solutions to these kinds of problems have always been in your hands, and YOU are empowered when you choose not to care....or at least let something get under your skin. Isn't the point here that EVERYONE hates spam? -Tom -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John Day Sent: Monday, August 30, 2004 4:06 PM To: Hadmut Danisch; ietf@ietf.org Subject: Re: How IETF treats contributors The best solution is to remove all authorship from all Internet standards, then there will be no problems. This isn't suppose to be an ego trip. If people really think the documents are important, they don't need their names on them. If they need their name on it, they are doing it for the wrong reasons. You don't find authors on the output of the standards groups. The most you will find is a list of the membership at the time of approval. Take care, John _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ 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