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

"Chris Lewis" <clewis@nortel.com> Sun, 09 November 2008 03:40 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 88A6E3A682E; Sat, 8 Nov 2008 19:40:54 -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 19D373A682E for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 19:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.154
X-Spam-Level:
X-Spam-Status: No, score=-5.154 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, 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 hqekgyEU6pFm for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 19:40:52 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 2B6A63A6819 for <ietf@ietf.org>; Sat, 8 Nov 2008 19:40:51 -0800 (PST)
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com [47.129.230.89]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id mA93eje02967 for <ietf@ietf.org>; Sun, 9 Nov 2008 03:40:45 GMT
Received: from [47.130.64.220] ([47.130.64.220] RDNS failed) by zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 8 Nov 2008 22:40:29 -0500
Message-ID: <49165BAA.7040301@nortel.com>
Date: Sat, 08 Nov 2008 22:40:26 -0500
From: Chris Lewis <clewis@nortel.com>
Organization: Nortel
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <A2A3269922C450550C530905@[172.16.0.38]>
In-Reply-To: <A2A3269922C450550C530905@[172.16.0.38]>
X-OriginalArrivalTime: 09 Nov 2008 03:40:29.0922 (UTC) FILETIME=[E9686420:01C9421C]
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 C Klensin wrote:

> As a thought experiment, if Nortel or Comcast are developing
> these lists and like them, are they willing to assume liability?

One would _assume_ you mean "assume liability if we lost a lawsuit",
rather than fork out money to anybody who sticks their hand out.

Well, of course we do.  We wouldn't be doing it if we didn't - we can't
wave a magic wand and escape the law.

We have MUCH bigger worries than legal liability like you're talking
about here.  Losing an important sale because of a filter mistake is a
far more likely risk than getting sued.  So, no lost legitimate email is
the absolute overriding priority.

Or, are you thinking that a whole new set of law needs to be created to
cover the source IP-based version of filtering, and holds DNSBL
operators to a higher standard than anyone else?

Why?  There have been many legal actions already.  A few losses, but
mostly wins.

Note also: e360 vs Comcast.  e360 sues Comcast for source-IP blocking
them.  Case thrown out on summary judgement.  Comcast has absolute right
to do it explicitly enshrined in the DMCA "hold harmless for good faith
blocking of objectionable email" clause.

This is probably extensible to the suppliers that ISPs use to do that
blocking.  Hence, DNSBLs are also immune as long as the plaintiff can't
prove bad faith.

That case is not entirely over yet, but the final result isn't going to
be any different.  Comcast's counter to the initial complaint is amazing
reading.

> If not, what does that say about the model?

Legal theory around DNSBLs has already been partially established in
case law.

Your questions have already had their answers demonstrated in a way that
only enhances the model.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf