Re: [Asrg] seeking comments on new RMX article

Dave Crocker <dhc@dcrocker.net> Mon, 05 May 2003 04:23 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 AAA12708 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 00:23:33 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h454VN622079 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 00:31: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 h454VN822076 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 00:31: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 AAA12695; Mon, 5 May 2003 00:23:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CXXK-0003c0-00; Mon, 05 May 2003 00:25:10 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CXXK-0003bx-00; Mon, 05 May 2003 00:25:10 -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 h454TQ821996; Mon, 5 May 2003 00:29:26 -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 h454RZ821938 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 00:27:35 -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 AAA12671 for <asrg@ietf.org>; Mon, 5 May 2003 00:18:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CXTP-0003bT-00 for asrg@ietf.org; Mon, 05 May 2003 00:21:07 -0400
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com ident=root) by ietf-mx with esmtp (Exim 4.12) id 19CXTJ-0003bJ-00 for asrg@ietf.org; Mon, 05 May 2003 00:21:01 -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 h454KvN07974; Sun, 4 May 2003 21:20:57 -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: <3863930786.20030504211628@brandenburg.com>
To: Mike Rubel <asrg@mikerubel.org>
CC: Dave Crocker <dhc@dcrocker.net>, asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: <Pine.LNX.4.44.0305041919440.9039-100000@tamale.caltech.edu>
References: <Pine.LNX.4.44.0305041919440.9039-100000@tamale.caltech.edu>
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: Sun, 04 May 2003 21:16:28 -0700
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mike,

DC>> those are not mail protocols.
MR> True, but they are "other methods which a mobile user may use to send
MR> mail."

no they are not.

in some cases, they are other methods for running smtp, besides using a
raw tcp/ip channel.

but they ultimately either use smtp or they are not for email.

please let's try not to introduce "let's invent new and special ways for
individual sites to do special things."  non-standardized methods do not
scale to the rest of the Internet.


MR> In any case, introducing RMX involves far less work than replacing SMTP,

and it does not accomplish what you seem to think it accomplishes.

you have not addressed the minor problem that failure to find an rmx
record has ambiguous meaning.  hence it is not at all clear what the
benefit is when you DO find the entry.


SN>> If the RMX matches the IP, it's a good bet the domain is not forged.
SN>> If the RMX doesn't match, all bets are off.
 MR> One more case here--if RMX is present and doesn't match, the message is
MR> definitely forged (or the system is misconfigured).

You are quite wrong.  When you do not find a matching rmx record, the
only thing you know is that there is no rmx record.  There are at least
two different reasons possible.  forgery is only one of them.

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