Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)

Keith Moore <moore@network-heretics.com> Mon, 10 November 2008 18:39 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E376928C11C; Mon, 10 Nov 2008 10:39:10 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9494A28C11C for <ietf@core3.amsl.com>; Mon, 10 Nov 2008 10:39:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyoVszvOPoNO for <ietf@core3.amsl.com>; Mon, 10 Nov 2008 10:39:09 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id F2D7A3A6A70 for <ietf@ietf.org>; Mon, 10 Nov 2008 10:39:08 -0800 (PST)
Received: from lust.indecency.org (adsl-242-100-123.tys.bellsouth.net [74.242.100.123]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BEF37541 (AUTH admin@network-heretics.com) for ietf@ietf.org; Mon, 10 Nov 2008 10:39:02 -0800 (PST)
Message-ID: <49187FC3.4070308@network-heretics.com>
Date: Mon, 10 Nov 2008 13:38:59 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <20081110130255.49372.qmail@simone.iecc.com> <491850D0.2070300@network-heretics.com> <alpine.LSU.2.00.0811101820090.30582@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.0811101820090.30582@hermes-1.csi.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Tony Finch wrote:
> On Mon, 10 Nov 2008, Keith Moore wrote:
>> I suspect it will be very difficult to make IPv6 DNSxLs work anywhere
>> nearly as well as IPv4 DNSxLs, because in IPv6 it is fairly easy to use
>> a different address for every SMTP conversation.
> 
> I expect that attack will make /48 or /64 listings common. This has the
> obvious downside of an increased risk of one infected host spoiling email
> connectivity for its immediate neighbours, even more than is already the
> case for IPv4 DNSBLs. Perhaps ISPs and hosting providers can mitigate that
> by enforcing address allocation policies.

Or perhaps enterprise networks will be forced to outsource their mail
submission to third parties with supposedly "trustworthy" addresses.
Which IMHO would not be a desirable result.

> In any case, DNSBLs should scale roughly according to the size of the
> routing table, not the size of the address space.

What does it mean for a DNSBL to "scale"?

Keith
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf