Re: [Asrg] seeking comments on new RMX article

Dave Crocker <dhc@dcrocker.net> Mon, 05 May 2003 15:26 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 LAA05494 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 11:26:20 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45FYNW10122 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 11:34:23 -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 h45FYN810119 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 11:34:23 -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 LAA05490; Mon, 5 May 2003 11:25:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Chsi-0006WE-00; Mon, 05 May 2003 11:27:56 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Chsh-0006WB-00; Mon, 05 May 2003 11:27:55 -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 h45FRR809742; Mon, 5 May 2003 11:27: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 h45FD4808934 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 11:13: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 LAA04947 for <asrg@ietf.org>; Mon, 5 May 2003 11:04:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ChY5-0006O6-00 for asrg@ietf.org; Mon, 05 May 2003 11:06:37 -0400
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com ident=root) by ietf-mx with esmtp (Exim 4.12) id 19ChXz-0006NX-00 for asrg@ietf.org; Mon, 05 May 2003 11:06:31 -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 h45F6DN32109; Mon, 5 May 2003 08:06:14 -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: <194902879171.20030505080536@brandenburg.com>
To: Alan DeKok <aland@freeradius.org>
CC: asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: <E19Ch0s-0006b5-00@mail.nitros9.org>
References: <E19Ch0s-0006b5-00@mail.nitros9.org>
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 08:05:36 -0700
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan,


>> so, what is the real utility of the rmx record?
AD>   Umm... you have more information with which to make better
AD> decisions?  That doesn't seem like a bad thing.


Spam is about filtering bad guys.  RMX is about labeling good guys.

Hence, with RMX, you still know nothing about bad guys.

How does it help to control spam if you continue to know nothing about
the bad guys?


>> that is, what can you safely do, versus not do?

AD>   For RMX systems, you can safely be more liberal in filtering
AD> messages, because you have some level of confidence that any spam
AD> coming from RMX systems will be traceable and accountable.  That
AD> doesn't seem like a bad thing to me.

What does this mean, exactly?  A different set of filters for RMX-based
mail?  The idea of maintaining two rulesets is a bit daunting.  Seems
unlikely to scale.


>> AD>   Are there NO other methods which a mobile user may use to send mail?
>> 
>> no.

AD>   I disagree most strongly.

>> AD> SMTP is only one of many protocols used to send/receive email.
>> 
>> interesting.  i believe there are no others.  ("submit" is simply smtp on
>> another port.)  which ones are you referring to?

AD>   Some people have posted other alternatives.

no they have not.

On the modern Internet, all of the mail posting semantics are achieved
with SMTP.

The "alternatives" presented were for alternative lower layers, or for
extremely limited email protocols that will never gain large-scale use.
(They have been around long enough to demonstrate this limitation
clearly.)


AD>  An additional one is
AD> mail via a web interface.

oh boy. now you are going to propose an array of non-standard user
interfaces as an email posting protocol?

methinks we have left the world of technical discussion of spam control.

the work here needs to be about protocols.


AD>   The feeling I get here is the same from everyone who's requiring
AD> that mobile users be allowed to send SMTP traffic to any port 25 on
AD> the planet, and to pretend to come from any domain.  They're adamant
AD> that that's the ONLY way they can send mail from remote sites, and
AD> that there are NO other workable alternatives.
...
AD>   I'm at a loss to respond to such a position.  It's so trivially,
AD> obviously wrong, that I'm left wondering what I'm missing.

You are over-interpreting my statements.  They were written carefully.
Please read them the same way.

By way of seeking something constructive out of this, would someone who
believes there are viable alternatives to SMTP -- and that they will

     a) solve or at least reduce the spam problem,

     b) match SMTP's functionality, and

     c) stand some chance of being adopted by the Internet's 100 million
     users

please put forward a technical specification of this "viable"
alternative, so that it moves from a general idea into something
concrete.


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