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

Theodore Tso <tytso@mit.edu> Sat, 08 November 2008 22:05 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 C7B023A6A10; Sat, 8 Nov 2008 14:05:11 -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 6D1853A69F7 for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 14:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level:
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 vOfwQDQwIS5T for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 14:05:09 -0800 (PST)
Received: from thunker.thunk.org (www.church-of-our-saviour.org [69.25.196.31]) by core3.amsl.com (Postfix) with ESMTP id 84D323A6A10 for <ietf@ietf.org>; Sat, 8 Nov 2008 14:05:09 -0800 (PST)
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1KyvvN-0005Rx-3B; Sat, 08 Nov 2008 17:04:57 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.69) (envelope-from <tytso@mit.edu>) id 1KyvvL-0003lC-QI; Sat, 08 Nov 2008 17:04:55 -0500
Date: Sat, 08 Nov 2008 17:04:55 -0500
From: Theodore Tso <tytso@mit.edu>
To: Chris Lewis <clewis@nortel.com>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
Message-ID: <20081108220455.GB13108@mit.edu>
References: <4915DE02.2010803@nortel.com> <4915EA94.6020706@network-heretics.com> <491601C4.3090803@nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <491601C4.3090803@nortel.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@mit.edu
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
Cc: john-ietf@jck.com, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, Keith Moore <moore@network-heretics.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

Speaking as someone who runs their own private mail server
(thunk.org), and having suffered from "collateral damage" when an
entire ISP range was listed, and where I had absolutely no way of
getting off a DNSBL that operating in a liability-free zone, with
administrators who refused to communicate with me, and where I had no
way of getting off the list, and thus had my e-mail blocked(*), forgive
me if I'm a bit less sanguine than you about the suitability of
DNSBL's, and whether your BCP will have any effectiveness whatsoever.
If DNSBL operators are content to operate in the dark, and refuse to
communicate, what makes you think they will pay attention to a BCP?

(*) Fortunately in most cases it was people asking me for help with
Linux, so I simply found another way to send the e-mail, and then sent
them a note saying that until they switched ISP's or fixed their mail
server to remove the use of the DNSBL, I would refuse to help them
with their Linux ext3 problem.  :-)

But I view DNSBL's as fundamentally the Wrong Answer, and it breaks
the intended SMTP and Internet architecture, with fundamentally wrong
power dynamics.  Of course, if you run a major mail operation, where
DNSBL's don't dare block you lest it become obvious that the whole
mechanism is corrupt, you don't see these problems.

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