Re: How IETF treats contributors
Hadmut Danisch <hadmut@danisch.de> Tue, 31 August 2004 19:43 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 PAA20859; Tue, 31 Aug 2004 15:43:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2EZQ-0004lc-Gm; Tue, 31 Aug 2004 15:45:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2ESM-0001Y8-Od; Tue, 31 Aug 2004 15:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2EKZ-0006Bu-Qv for ietf@megatron.ietf.org; Tue, 31 Aug 2004 15:30:12 -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 PAA19943 for <ietf@ietf.org>; Tue, 31 Aug 2004 15:30:10 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2EMa-0004TQ-VZ for ietf@ietf.org; Tue, 31 Aug 2004 15:32:18 -0400
Received: from andromeda (uucp@localhost) by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id i7VJU5C9018306; Tue, 31 Aug 2004 21:30:05 +0200
Received: (from hadmut@localhost) by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id i7VJR6ea024501; Tue, 31 Aug 2004 21:27:06 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 31 Aug 2004 21:27:06 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-ID: <20040831192706.GB22942@danisch.de>
References: <20040831104016.4bf3d0c6.olaf@ripe.net> <200408311440.i7VEeiPX083988@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200408311440.i7VEeiPX083988@calcite.rhyolite.com>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: ietf@ietf.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: d185fa790257f526fedfd5d01ed9c976
[ Sorry, but I couldn't resists to give a nasty side comment: Vernon Shryver was one of the persons who most unobjectively and maliciously attacked RMX and any other proposal against Spam. He was displeased because his own invention has major flaws, and that I showed in the RMX draft that his proposal can and is abused for censoring e-mail traffic. His posting appears to me as if he took the opportunity for revenge. I'll nevertheless reply to correct some of his misleading and wrong statements. ] First, my name is Danisch, not Danish. On Tue, Aug 31, 2004 at 08:40:44AM -0600, Vernon Schryver wrote: > > - None of the versions of Mr. Danish's proposal that I've seen > credited Mr. Vixie's document or some others than preceded Mr. > Danish's work. I think that was due to ignornance and disinterest > instead of malice, but it does reduce Mr. Danish's standing to > more credit than he already receives. This is pure nonsense. The same kind of defamation he already used on the early asrg mailing list. I did not cite or credit anyone else because at the time I wrote RMX I did not know of anyone else's work in this field. RMX is in no way derived from or based on anyone else's work. If anyone has any doubt about this, I can show that I was working on organizational security, especially in context of e-mail, that RMX is just the logical continuation of my former work and that I had very good reasons to design RMX the way it is. How should I have cited or credited someone else's work without knowing it? And why? In contrast, SPF and CallerID were provably based on RMX, the authors were familiar with RMX, and the first version of SPF was explicetely announced to cover RMX. > - Mr. Danish's proposal was always an obvious non-starter for various > reasons, including the requirement for defining new DNS RR types > before it could be deployed or even tested. RMX is not the requirement for defining the new DNS RR type. This was just the proposal how to implement it. That's the illogical point of the story: SPF was derived from RMX by simply omitting the invention of a new DNS RR type. This didn't change the idea of RMX, just changed the way to implement it a little bit. And the same time certain people claimed that SPF is 'new' and that RMX is wrong because it required a new DNS RR type. Typical way of intentional misinformation. > - It is ironic or something that few people who are openly concerned > about credit for their work have enviable reputations. They tend > to be inventors of such as IPv8. ??? Does anyone have a clue what this is about? Hadmut Danisch _______________________________________________ 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