Re: [Asrg] 6. Proposals - RMX-like implementation via rDNS (OMX v. DRIP)

david nicol <davidnicol@pay2send.com> Mon, 15 September 2003 06:12 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10279 for <asrg-archive@odin.ietf.org>; Mon, 15 Sep 2003 02:12:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ymas-0004VM-Cq for asrg-archive@odin.ietf.org; Mon, 15 Sep 2003 02:12:15 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8F6CEKI017309 for asrg-archive@odin.ietf.org; Mon, 15 Sep 2003 02:12:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ymap-0004Th-QW for asrg-web-archive@optimus.ietf.org; Mon, 15 Sep 2003 02:12:11 -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 CAA09801 for <asrg-web-archive@ietf.org>; Mon, 15 Sep 2003 02:12:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ymam-0005eS-00 for asrg-web-archive@ietf.org; Mon, 15 Sep 2003 02:12:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ymal-0005eP-00 for asrg-web-archive@ietf.org; Mon, 15 Sep 2003 02:12:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ymah-0004Q2-5Y; Mon, 15 Sep 2003 02:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ymac-0004OV-3Z for asrg@optimus.ietf.org; Mon, 15 Sep 2003 02:11:58 -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 CAA09610 for <asrg@ietf.org>; Mon, 15 Sep 2003 02:11:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ymaY-0005d7-00 for asrg@ietf.org; Mon, 15 Sep 2003 02:11:54 -0400
Received: from ms-smtp-01.rdc-kc.rr.com ([24.94.166.115]) by ietf-mx with esmtp (Exim 4.12) id 19ymaY-0005cx-00 for asrg@ietf.org; Mon, 15 Sep 2003 02:11:54 -0400
Received: from CPE-65-26-15-250.kc.rr.com (CPE-65-26-15-250.kc.rr.com [65.26.15.250]) by ms-smtp-01.rdc-kc.rr.com (8.12.8p1/8.12.7) with ESMTP id h8F6Bq2a017457; Mon, 15 Sep 2003 01:11:53 -0500 (CDT)
Subject: Re: [Asrg] 6. Proposals - RMX-like implementation via rDNS (OMX v. DRIP)
From: david nicol <davidnicol@pay2send.com>
To: waltdnes@waltdnes.org
Cc: ASRG list <asrg@ietf.org>
In-Reply-To: <20030910063545.GC2082@m450>
References: <20030910063545.GC2082@m450>
Content-Type: text/plain
Message-Id: <1063606311.2220.273.camel@plaza.davidnicol.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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/mail-archive/working-groups/asrg/>
Date: Mon, 15 Sep 2003 01:11:51 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2003-09-10 at 01:35, waltdnes@waltdnes.org wrote:

> The proposal
> ============
> 
>   The proposal is that ISPs publish a list of their outbound email
> servers and any static IP address ranges that are authorized to send
> email direct-to-MX.  All other IP addresses within the ISP's domain
> would be assumed to be unauthorized to send email direct-to-MX.  The
> publishing could be on a web page.  The addresses could be either
> numeric, or rDNS patterns.  A real-life example is AOL.

Does anyone argue with this?  The only problem is selecting
a standard for publishing the information.  I suggested one
last may (and june) in a message archived here:

http://msgs.securepoint.com/cgi-bin/get/djbdns-0306/9.html

and I suppose I'll keep posting links to it until I see something
equivalent in the form of an I-D, and then I'll link to that.

Okay, DRIP
http://www.ietf.org/internet-drafts/draft-brand-drip-01.txt
is very similar; however instead of 


         192_0_2_10.IPv4.relays._email_.M.EXAMPLE.COM.  IN A  192.0.2.10

         192_0_2_11.IPv4.relays._email_.M.EXAMPLE.COM.  IN A  192.0.2.11

         127_0_0_1.IPv4.relays._email_.M.EXAMPLE.COM.   IN A  127.0.0.1

OMX would have example.com list

	omx.m.example.com IN A 192.0.2.10
	omx.m.example.com IN A 192.0.2.11
	omx.m.example.com IN A 127.0.0.1

up to the first seven relays, if there are seven of
them then we put the next seven in omx1... and then
omx2... until there aren't any more.

This means, less DNS traffic.  It is harder to get wrong than
DRIP, which appears to insist that the address gets repeated
in the name and the response.


As for what it is reccommended that the MTA do with the listedness/notlistedness
of the peer, I guess that isn't beyond the scope of the to-be-written
OMX I-D, since it is included in the DRIP draft.




> Advantages
> ==========
> 
>   1) This proposal does *NOT* require new types of DNS records or other
> protocols.  It can be implemented within the existing structure.  AOL
> already does this, an example that it can be done.
> 
>   2) Lists of authorized sending addresses/rDNS-patterns will generally
> be much smaller than lists of residential IP addresses.

Amen.




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