DNS record types; RE: [Asrg] Problems with RMX

"Bob Atkinson" <bobatk@exchange.microsoft.com> Tue, 06 May 2003 20:29 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 QAA07292 for <asrg-archive@odin.ietf.org>; Tue, 6 May 2003 16:29:07 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46KbiI26274 for asrg-archive@odin.ietf.org; Tue, 6 May 2003 16:37:44 -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 h46Kbi826271 for <asrg-web-archive@optimus.ietf.org>; Tue, 6 May 2003 16:37:44 -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 QAA07271; Tue, 6 May 2003 16:28:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D95F-00024e-00; Tue, 06 May 2003 16:30:41 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D95E-00024b-00; Tue, 06 May 2003 16:30:40 -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 h46KZ5825286; Tue, 6 May 2003 16:35:05 -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 h46KSO824916 for <asrg@optimus.ietf.org>; Tue, 6 May 2003 16:28:24 -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 QAA06951 for <asrg@ietf.org>; Tue, 6 May 2003 16:19:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D8wC-000218-00 for asrg@ietf.org; Tue, 06 May 2003 16:21:20 -0400
Received: from [131.107.8.10] (helo=exchange.microsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19D8wB-00020L-00 for asrg@ietf.org; Tue, 06 May 2003 16:21:19 -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); Tue, 6 May 2003 13:21:37 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 06 May 2003 13:21:32 -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); Tue, 6 May 2003 13:21:36 -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: DNS record types; RE: [Asrg] Problems with RMX
Message-ID: <27C4E14288DB344FBA10705D57A9BB043E55A9@DF-CHOPPER.platinum.corp.microsoft.com>
Thread-Topic: DNS record types; RE: [Asrg] Problems with RMX
Thread-Index: AcMUBPcaIyp7LwLdSQuSF2SLTKcXmgABtKiw
From: Bob Atkinson <bobatk@exchange.microsoft.com>
To: Ken Hirsch <kenhirsch@myself.com>, asrg@ietf.org
X-OriginalArrivalTime: 06 May 2003 20:21:36.0425 (UTC) FILETIME=[17E0E190:01C3140D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h46KSO824917
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: Tue, 06 May 2003 13:21:35 -0700
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> From: Ken Hirsch

> 1. It requires changes to DNS
> 
> The idea behind RMX can be implemented without changes to DNS,
however.
> For example, via MX records, as already mentioned, or via some
specially coded
> A record (see http://www.bondedsender.org/#dns-info)

I agree that using new DNS record types, which requires changes to DNS
clients and servers in order to be useful, would be a significant
barrier to adoption. 

My own preference is to store the new information in TXT record(s) in a
distinguished subdomain. For example, one might use the TXT records in
the '_rmx' subdomain of the domain in question: rather than querying for
the records of type RMX in domain domain.com, one queries for the
records of type TXT in the domain _rmx.domain.com.

A text encoding issue for the information remains, though XML is an
obvious candidate.

A final point is that we should remember that it's probable that as we
flush out an overall spam deterrence story we'll find that we want more
than just the specific RMX info that Hadmut has proposed to be published
in DNS. Anticipating that now is worth at least a few brain cycles.

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