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

Keith Moore <moore@network-heretics.com> Mon, 10 November 2008 18:07 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 4380128C0F6; Mon, 10 Nov 2008 10:07:50 -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 01ECC3A6A56 for <ietf@core3.amsl.com>; Mon, 10 Nov 2008 10:07:49 -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 xusIg706D3um for <ietf@core3.amsl.com>; Mon, 10 Nov 2008 10:07:48 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 401FF3A68AB for <ietf@ietf.org>; Mon, 10 Nov 2008 10:07:48 -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 BEF33691 (AUTH admin@network-heretics.com) for ietf@ietf.org; Mon, 10 Nov 2008 10:07:42 -0800 (PST)
Message-ID: <4918786C.7000804@network-heretics.com>
Date: Mon, 10 Nov 2008 13:07:40 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Steve Linford <linford@spamhaus.org>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <A.1KzaJs-0008yI-GB@smtp-ext-layer.spamhaus.org>
In-Reply-To: <A.1KzaJs-0008yI-GB@smtp-ext-layer.spamhaus.org>
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

Steve Linford wrote:

> I certainly agree that there are hundreds of small DNSBLs run from kid's
> bedrooms which list on incomprehensible wildly over-broad policies and
> that such DNSBLs are both antagonistic and useless and as a result are
> used by almost nobody - that's 'market force'. But to pretend that the
> dozen major DNSBLs make listings based on "unauthenticated rumor" or
> "because the IP did not have 'mail.' or 'mx.'" is just silly
> mud-slinging itself based on equally "unauthenticated rumor" and is
> especially odd if it's coming from within IETF itself.

It's only odd if you refuse to recognize our experiences as valid.

> The fact some DNSBLs are in widespread use (I can speak only for
> Spamhaus, our DNSBLs are today used by something in the region of 2/3 of
> internet networks) is good reason why it's important to publish a
> standard and format for the technology.

Wrong.  Read RFC 2026 and stop demanding that we change our technical
criteria just for you.

> Like everyone we'd like to see poorly managed, arrogant or anonymous
> DNSBLs given a high standard to attain ('shape up or ship out'), since
> an irresponsible DNSBL listing something for little discernible reason
> is what creates "I hate all DNSBLs" poster children. Lets have the
> technology, standards and how to do it correctly published for the
> future and leave aside silly "I once had a client blacklisted"
> arguments. The question "are DNSBLs bad for the world" or "are DNS
> queries a bad use" is irrelevant to the need for draft-irtf-asrg-dnsbl
> and a false argument against it.
> 
> I can see no legitimate reason for IETF not publishing
> draft-irtf-asrg-dnsbl.

The proposal has neither technical soundness nor rough consensus of the
community.

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