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

Dave CROCKER <dhc2@dcrocker.net> Sat, 08 November 2008 15:54 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 498823A6A57; Sat, 8 Nov 2008 07:54:04 -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 46FA13A6A57 for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 07:54:03 -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 LZ+3LwyxodOp for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 07:54:02 -0800 (PST)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 997F83A6A41 for <ietf@ietf.org>; Sat, 8 Nov 2008 07:54:01 -0800 (PST)
Received: from [192.168.0.3] (adsl-67-124-149-194.dsl.pltn13.pacbell.net [67.124.149.194]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id mA8Fru4f029629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Nov 2008 07:53:56 -0800
Message-ID: <4915B613.4070805@dcrocker.net>
Date: Sat, 08 Nov 2008 07:53:55 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <20081107111744.GA31018@nic.fr> <20081107141821.79303.qmail@simone.iecc.com> <45AEC6EF95942140888406588E1A660206A5D881@PACDCEXCMB04.cable.comcast.com> <4914D181.9090605@network-heretics.com> <278E245FD800CC334CA5100F@klensin-asus.icannmeeting.org>
In-Reply-To: <278E245FD800CC334CA5100F@klensin-asus.icannmeeting.org>
X-Virus-Scanned: ClamAV 0.92/8592/Fri Nov 7 21:40:23 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 08 Nov 2008 07:53:56 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


John C Klensin wrote:
> Sadly, I have to agree with Keith.   While these lists are a
> fact of life today, and I would favor an informational document
> or document that simply describes how they work and the issues
> they raise, standardizing them and formally recommending their
> use is not desirable at least without some major changes in our
> email model and standards for what gets addresses onto --and,
> more important, off of-- those lists.


John,

What are the technical deficiencies of this specification?

What are the specific problems the mechanism it defines pose to "our email model 
and standards"?

What are the specific, "major changes" that would be required to the model and 
standards, to make the current specification acceptable?

This type of mechanism has massive adoption throughput the Internet.  It's 
perceived efficacy also is massive.  The current specification merely seeks to 
provide a stable technical basis for that mechanism.

In the face of overwhelming community consensus for this mechanism, you offer a 
simple, flat, fundamental rejection, yet provide no substantiation.

Really, John, it would help for a posting to do more than say that you don't 
like the idea of the mechanism.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf