reverse DNS; RE: [Asrg] RMX proposals and Nash Equilibrium

"Bob Atkinson" <bobatk@exchange.microsoft.com> Mon, 05 May 2003 22:32 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 SAA20006 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 18:32:43 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45Meto10185 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 18:40:55 -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 h45Mee810175 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 18:40:40 -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 SAA19988; Mon, 5 May 2003 18:31:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoX6-0001UU-00; Mon, 05 May 2003 18:34:04 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CoX5-0001UP-00; Mon, 05 May 2003 18:34:03 -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 h45McM809980; Mon, 5 May 2003 18:38:22 -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 h45MPJ808530 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 18:25:19 -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 SAA18594 for <asrg@ietf.org>; Mon, 5 May 2003 18:16:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoIF-0001Mn-00 for asrg@ietf.org; Mon, 05 May 2003 18:18:43 -0400
Received: from [131.107.8.10] (helo=exchange.microsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19CoI9-0001Mf-00 for asrg@ietf.org; Mon, 05 May 2003 18:18:38 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 5 May 2003 15:18:41 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 05 May 2003 15:18:41 -0700
Received: from DF-CHOPPER.platinum.corp.microsoft.com ([10.197.0.104]) by DF-BEG.platinum.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6700); Mon, 5 May 2003 15:18:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6930.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: reverse DNS; RE: [Asrg] RMX proposals and Nash Equilibrium
Message-ID: <27C4E14288DB344FBA10705D57A9BB043E5477@DF-CHOPPER.platinum.corp.microsoft.com>
Thread-Topic: reverse DNS; RE: [Asrg] RMX proposals and Nash Equilibrium
Thread-Index: AcMR3AjiRV0p70XoQJyEJRHaSBeJCABdZSzA
From: Bob Atkinson <bobatk@exchange.microsoft.com>
To: "Eric D. Williams" <eric@infobro.com>, Daniel Feenberg <feenberg@nber.org>, asrg@ietf.org
X-OriginalArrivalTime: 05 May 2003 22:18:41.0613 (UTC) FILETIME=[48CDBFD0:01C31354]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h45MPn808547
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 15:18:39 -0700
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Reverse DNS has two quite important situations in which it does not
easily (if ever) give appropriate answers for use in spam deterrence.

1) If I host my own DNS servers, and have no DNS relationship with my
ISP, then (typically, if not mostly) the rDNS lookup will ultimately go
to him but have no means by which it can connect to my DNS servers and
thus give a meaningful response. As a result, the rDNS lookup yields
answers like

	dsl-209-123-212-68.myisp.com

rather than something related to the email domains that I actually send
from.

2) If, for one of possibly many reasons, I legitimately relay my
outbound mail through some other domain, then it becomes
administratively very cumbersome (if not logistically impossible,
pragmatically speaking) to have the rDNS lookup resolve to something in
my domain (in addition to the one through which I am relaying, and all
the others he relays for).

RMX-style proposals, which start their lookup at the domain purportedly
responsible for a message, don't suffer from these shortcomings.
(indeed, they can nicely leverage the existing administrative
infrastructure that I necessarily have to mange my MX records). This is
an important advantage.

Ultimately, these approaches yield the same information, namely an
answer to the question: "is this IP address authorized by the admin of
this domain to transmit mail on behalf of that domain". While the
spoofing that this prevents is VERY interesting and useful, it is, in
and of itself, of course not something that will eliminate spam.
Additional infrastructure is needed above and beyond RMX.

	Bob


-----Original Message-----
From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of Eric
D. Williams
Sent: Saturday, May 03, 2003 6:16 PM
To: 'Daniel Feenberg'; asrg@ietf.org
Subject: RE: [Asrg] RMX proposals and Nash Equilibrium

All of these are valid points to argue, but without addressing a
fundemental 
point (not described in most) RMX proposals from my understanding.  That
is, 
DNS can also be used to validate an IP reverse map so that not only the
domain 
is checked but also the IP.  In that case, IMHO, one could argue that an

additional check for IP origination or relay of delivery would mitigate
the 
concerns.

I could definitely be wrong but that always sticks out to me as a 
mis-understanding of that type of proposed solution/strategy.  I don't
think 
the forwarder of mail has to be penalized for forwarding if they are
properly 
registered in the forwarding path (open-relays are another matter in my 
opinion) and are no longer used in the historical context (helping a 
brother/sister system out).


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