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

Keith Moore <moore@network-heretics.com> Sat, 08 November 2008 17:32 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 3E6A03A69EA; Sat, 8 Nov 2008 09:32:01 -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 E3C083A69EA for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 09:31:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.731
X-Spam-Level:
X-Spam-Status: No, score=-1.731 tagged_above=-999 required=5 tests=[AWL=0.069, 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 L0nhWOBKpXK3 for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 09:31:59 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 4EFCA3A6816 for <ietf@ietf.org>; Sat, 8 Nov 2008 09:31:59 -0800 (PST)
Received: from lust.indecency.org (adsl-155-115-114.tys.bellsouth.net [72.155.115.114]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BED03552 (AUTH admin@network-heretics.com) for ietf@ietf.org; Sat, 8 Nov 2008 09:31:54 -0800 (PST)
Message-ID: <4915CD08.7040901@network-heretics.com>
Date: Sat, 08 Nov 2008 12:31:52 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <20081108170500.1881.qmail@simone.iecc.com>
In-Reply-To: <20081108170500.1881.qmail@simone.iecc.com>
Cc: john-ietf@jck.com, 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

John Levine wrote:
>> standardizing them and formally recommending their use
> 
> I'm not aware of any language in the current draft that recommends
> that people use DNSBLs. 

Standardizing it is an implicit recommendation.  In particular it's a
statement that there are "no known technical omissions" about the
protocol.  Which is not an accurate description of the protocol at hand.

 What it does say is that if you use or
> publish DNSBLs, here's how they work so you can, you know,
> interoperate and all that.  As I'm sure everyone is aware, there are
> large numbers of independently written implementations, both
> publishers and users of DNSBLs, so they seem ripe to me for
> standardization.

So there's a clear justification for an Informational document
describing current practice - and also what's wrong with it.
Widespread deployment is not a justification for standardization.

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