IETF Logo Mail Archive

Re: [Asrg] seeking comments on new RMX article

Dave Crocker <dhc@dcrocker.net> Mon, 05 May 2003 19:37 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13638 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 15:37:19 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45JjRq29265 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 15:45:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45JjQ829262 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 15:45:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13630; Mon, 5 May 2003 15:36:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Clna-00008Q-00; Mon, 05 May 2003 15:38:55 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Clna-00008N-00; Mon, 05 May 2003 15:38:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45JeV829086; Mon, 5 May 2003 15:40:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Jb4828136 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 15:37:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13448 for <asrg@ietf.org>; Mon, 5 May 2003 15:28:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ClfU-00005N-00 for asrg@ietf.org; Mon, 05 May 2003 15:30:32 -0400
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com ident=root) by ietf-mx with esmtp (Exim 4.12) id 19ClfO-000058-00 for asrg@ietf.org; Mon, 05 May 2003 15:30:26 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged)) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h45JU8N15737; Mon, 5 May 2003 12:30:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <72917913720.20030505121611@brandenburg.com>
To: Hadmut Danisch <hadmut@danisch.de>
CC: Dave Crocker <dhc@dcrocker.net>, Alan DeKok <aland@freeradius.org>, asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: <20030505185145.GA13244@danisch.de>
References: <E19CiOf-0006dc-00@mail.nitros9.org> <101914858506.20030505112516@brandenburg.com> <20030505185145.GA13244@danisch.de>
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Mon, 05 May 2003 12:16:11 -0700
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hadmut,


>> Accountability does not mean that the originator is comforming to good
>> policies.
HD> Accountability requires the posibility to track back the originator.
HD> That's what's RMX is about.

>> Why?  What makes it likely or certain that someone coming through an RMX
>> host is not sending spam?
HD> Because he can be tracked back and hold responsible.

what does it mean to hold them responsible, when there are no global
rules to which a sender is held?



>> We have had PGP and S/MIME for approximately 10 years.  They permit
>> identifying the originator.  Yet they have not achieved any significant
>> adoption or use in the Internet.  How will you achieve success now?

HD> That's not logical. If PGP and S/MIME didn't have succes yet, it
HD> doesn't mean that no authentication method will ever have success.

However, it DOES mean that it is dangerous to claim that authentication
will be used as a basic technique, unless there is some reason to
believe that the technique will be successful now, in spite of not being
successful for 10 years.


HD> The failure of PGP and S/MIME is a design criterion for RMX:
HD> It is designed to avoid the problems of PGP and S/MIME,

they perform entirely different tasks.


HD> Furthermore, PGP and S/MIME are a completely different story.
HD> You're comparing apples and oranges.

the reference was to authenticated senders.  pgp and s/mime authenticate
senders.  rmx does not.


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>

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

v2.23.0 | Report a Bug | By Email