Re: How IETF treats contributors
"Clint Chaplin" <cchaplin@symbol.com> Tue, 31 August 2004 00:05 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 UAA16000; Mon, 30 Aug 2004 20:05:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1wAs-00042T-Jm; Mon, 30 Aug 2004 20:07:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1w5r-0007Rt-Do; Mon, 30 Aug 2004 20:01:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1vqc-0004Xa-R5 for ietf@megatron.ietf.org; Mon, 30 Aug 2004 19:46:02 -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 TAA14868 for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:58 -0400 (EDT)
Received: from mail66.messagelabs.com ([193.109.254.35]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C1vsS-0003bg-Kr for ietf@ietf.org; Mon, 30 Aug 2004 19:47:58 -0400
X-VirusChecked: Checked
X-Env-Sender: cchaplin@symbol.com
X-Msg-Ref: server-14.tower-66.messagelabs.com!1093909527!2078476
X-StarScan-Version: 5.2.10; banners=symbol.com,-,-
X-Originating-IP: [167.206.235.72]
Received: (qmail 13287 invoked from network); 30 Aug 2004 23:45:27 -0000
Received: from mx2.symbol.com (167.206.235.72) by server-14.tower-66.messagelabs.com with SMTP; 30 Aug 2004 23:45:27 -0000
Received: from proxy.symbol.com (proxy.symbol.com [157.235.5.10]) by mx2.symbol.com (8.12.8/8.12.8) with ESMTP id i7UNjRn6028566 for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:27 -0400
Received: from RUNABOUT ([157.235.95.252]) by proxy.symbol.com (8.12.11/8.12.8) with ESMTP id i7UNjLmv004933 for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:22 -0400
Received: from SJ-DOM-MTA by RUNABOUT with Novell_GroupWise; Mon, 30 Aug 2004 16:45:18 -0700
Message-Id: <s133599e.083@RUNABOUT>
X-Mailer: Novell GroupWise Internet Agent 6.0.4
Date: Mon, 30 Aug 2004 16:45:12 -0700
From: Clint Chaplin <cchaplin@symbol.com>
To: hadmut@danisch.de, ietf@ietf.org, day@std.com
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 30 Aug 2004 20:01:45 -0400
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: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Well, at least for 802.11, this isn't true. There is a section to list the contributors who had contributed a significant contribution to the standards process. This list can get quite lengthy. Clint (JOATMON) Chaplin Wireless Security Advisor Wireless Standards Lead >>> John Day <day@std.com> 8/30/04 16:05:30 >>> 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 ________________________________________________________________________ This email has been scanned for computer viruses. ________________________________________________________________________ This email has been scanned for computer viruses. _______________________________________________ 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