Re: How IETF treats contributors

Hadmut Danisch <hadmut@danisch.de> Tue, 31 August 2004 19:04 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 PAA16408; Tue, 31 Aug 2004 15:04:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Dxe-0003mT-52; Tue, 31 Aug 2004 15:06:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Dt7-0006ru-NJ; Tue, 31 Aug 2004 15:01:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Drf-0005Yf-JA for ietf@megatron.ietf.org; Tue, 31 Aug 2004 15:00:21 -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 PAA16141 for <ietf@ietf.org>; Tue, 31 Aug 2004 15:00:18 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Dtg-0003hT-Dm for ietf@ietf.org; Tue, 31 Aug 2004 15:02:25 -0400
Received: from andromeda (uucp@localhost) by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id i7VJ05PH017570; Tue, 31 Aug 2004 21:00:05 +0200
Received: (from hadmut@localhost) by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id i7VIw2BW023241; Tue, 31 Aug 2004 20:58:02 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 31 Aug 2004 20:58:02 +0200
To: Dean Anderson <dean@av8.com>
Message-ID: <20040831185802.GA22942@danisch.de>
References: <20040830090627.GA22982@danisch.de> <Pine.LNX.4.44.0408301607571.28223-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0408301607571.28223-100000@cirrus.av8.net>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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: 21c69d3cfc2dd19218717dbe1d974352

Dean,

On Mon, Aug 30, 2004 at 04:43:57PM -0400, Dean Anderson wrote:
> 
> That said, it is a reprehensible shame that you are not being given credit
> for your work in SPF and RMX.

Thanks for that.


> We demonstrated that RMX did not solve the problem it set out to
> solve.

I do not remember that anyone did demonstrate that. 


On the contrary, RMX solved a major problem in contrast to the current
SenderID proposal.  Many people, including myself, do receive
significant more false bounce messages and spam complaints than 
spam messages, because spammers abuse my e-mail address or domain. 
Therefore RMX was designed to verify the envelope sender and it
does that job.

In contrast, SenderID does not solve that problem. Guess why.  





> No doubt, the
> MARID group chairs do not want to appear to simply re-hash RMX under a
> different name. In order to avoid that, they have to pretend it wasn't
> written by you.


This might be true.


Hadmut

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf