
From darxus@chaosreigns.com  Sun Dec 11 11:24:37 2011
Return-Path: <darxus@chaosreigns.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC6421F84A0 for <asrg@ietfa.amsl.com>; Sun, 11 Dec 2011 11:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.001,  NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jUwzd4IG1YH for <asrg@ietfa.amsl.com>; Sun, 11 Dec 2011 11:24:36 -0800 (PST)
Received: from panic.chaosreigns.com (panic.chaosreigns.com [IPv6:2001:470:1f05:1b8a::1]) by ietfa.amsl.com (Postfix) with ESMTP id A64E021F849E for <asrg@irtf.org>; Sun, 11 Dec 2011 11:24:36 -0800 (PST)
Received: by panic.chaosreigns.com (Postfix, from userid 1000) id 4CCD0AC7B4; Sun, 11 Dec 2011 14:24:32 -0500 (EST)
Date: Sun, 11 Dec 2011 14:24:32 -0500
From: darxus@chaosreigns.com
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20111211192432.GT28130@chaosreigns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Asrg] Reminds me of this list the most
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 19:24:37 -0000

http://tompreston.deviantart.com/art/Welcome-to-the-Internet-273281497

From vesely@tana.it  Tue Dec 13 09:04:04 2011
Return-Path: <vesely@tana.it>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6146E21F84D7 for <asrg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.739
X-Spam-Level: 
X-Spam-Status: No, score=-3.739 tagged_above=-999 required=5 tests=[AWL=-0.879, BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKB9D+H-ZNlQ for <asrg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:04:03 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C4FE721F84A7 for <asrg@irtf.org>; Tue, 13 Dec 2011 09:04:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1323795840; bh=6MHJSr/AQKIUCQPuCV8j1VdZB0UUqubSSj8B7iYs/iQ=; l=269; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=OLvlevw95bdmK47kHfkyNm7zhWq/G4dqnJiiZuggu2rTCEwLxym8Vgv59mYnabM13 emLOA+Jc3IzMJpa/pGEULZ/AjG6v+yslYWc0tCtp78CguWba9LMa94mHNAjicEv6qG P6oC2J5RMo0hzeGIr9lSkWdJ42/MjavNmsDaYBCY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 13 Dec 2011 18:04:00 +0100 id 00000000005DC039.000000004EE78580.00006740
Message-ID: <4EE78580.8070109@tana.it>
Date: Tue, 13 Dec 2011 18:04:00 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111211192432.GT28130@chaosreigns.com>
In-Reply-To: <20111211192432.GT28130@chaosreigns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Reminds me of this list the most
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 17:04:04 -0000

On 11/Dec/11 20:24, darxus@chaosreigns.com wrote:
> http://tompreston.deviantart.com/art/Welcome-to-the-Internet-273281497

Already "gray"!  However, someone copied that image here:
http://rubymight.tumblr.com/post/14042875759/adobsonart-welcome-to-the-internet-by


From darxus@chaosreigns.com  Thu Dec 22 07:12:20 2011
Return-Path: <darxus@chaosreigns.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D9B21F84E5 for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 07:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+z03oZ7fDt0 for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 07:12:15 -0800 (PST)
Received: from panic.chaosreigns.com (panic.chaosreigns.com [IPv6:2001:470:1f05:1b8a::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCEB521F84FD for <asrg@irtf.org>; Thu, 22 Dec 2011 07:12:15 -0800 (PST)
Received: by panic.chaosreigns.com (Postfix, from userid 1000) id E089C2C6BE7; Thu, 22 Dec 2011 10:12:08 -0500 (EST)
Date: Thu, 22 Dec 2011 10:12:08 -0500
From: darxus@chaosreigns.com
To: asrg@irtf.org
Message-ID: <20111222151208.GF28224@chaosreigns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Asrg] Handling of abusive DNSBL/WL clients
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 15:12:20 -0000

This spamassassin bug comment provides some information on what happens
when various methods of blocking abusive DNS queries are attempted.
The tests were conducted on dnswl.org, a public email whitelist enabled
by default in spamassassin, and presumably other things.

There seems to be a surprising lack, in RFCs and BCPs, of statements
that clients and forwarding DNS servers should stop querying if they
receive an NXDOMAIN, REFUSED, or an answer with the TLD of "invalid",
which seem likely to help if they were widely implemented.

It also seems like it would be good to define best practices for handling
this situation, quite possibly based on the information below.

SpamAssassin is currently asking DNS black/white list providers
to indicate the client is being blocked via a specified returned
IP value for all queries, in the case of DNSWL, 127.0.0.255.
There has been some debate on what would be an ideal value.
This is not in line with the blacklist BCP's suggestion to check
the values of 127.0.0.1 and 127.0.0.2, I guess because the SA devs
feel it's easier to implement.  Some related discussion was here:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6724

(My involvement - I'm not a SA dev, I've been participating on the dev
mailing list for a number of months.  I've been helping DNSWL on and
off for about 5 years.)

----- Forwarded message from bugzilla-daemon@bugzilla.spamassassin.org -----

Date: Thu, 22 Dec 2011 10:32:43 +0000
From: bugzilla-daemon@bugzilla.spamassassin.org
To: Darxus@ChaosReigns.com
Subject: [Bug 6728] DNSBLs need a way to turn off queries based on BLOCKED
	rules triggering

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6728

--- Comment #13 from Matthias Leisi <matthias@leisi.net> 2011-12-22 10:32:43 UTC ---
I did some additional tests on how best to block abusive query sources. "Best"
is defined as three goals: 

1) Reduce the overall traffic on parent (dnswl.org) and data (list.dnswl.org)
zone
2) Avoid or minimize collateral damage on root and gTLD servers
3) Make it easy for operators of abusive query sources to find out what is
happening

We have built the mechanism to redirect defined IPs to a special view of the
dnswl.org zone as part of bug 6724 (using BIND views). I wanted to do actual
tests to base at least the decision on the first goal on hard facts. We tested
three combinations:

A. Explicit nameserver in "nowhere land"
| list.dnswl.org.        21600 IN NS blockedview.dnswl.org.
| blockedview.dnswl.org. 21600 IN A  127.0.0.255

B. Explicit nameserver for data zone in .invalid
| list.dnswl.org.        21600 IN NS  _  
|   you.are.blocked.from.using.dnswl.org.thorugh.public.nameservers.invalid.

C. No zone apex
(no NS records for list.dnswl.org)

In all cases, we returned 127.0.0.255 for *.list.dnswl.org in this view. Also
in all cases, we return 127.0.0.255 for the nameservers of the original data
zone (a through l.ns.dnswl.org), which affected clients should not actually
ever have  seen. Also, if an affected client would ask a through l.ns.dnswl.org
they would always receive 127.0.0.255 as an answer. 

A. and B. showed no measurable difference in traffic levels on the parent and
the data zone. 

With C., the traffic on the parent zone nameservers grew by about 30%; traffic
on the data zone did only shrink by about half the amount that was added on the
parent zone.

This rules out C. as a viable option and makes the choice depend only on goals
2 and 3 above: minimize collateral damage (on root servers) and maximize
identifiability for operators. 

It can be expected that some resolvers will ask the roots for invalid., and it
can also be expected that not all resolvers will do proper negative caching for
B. 

This leaves A. as the most efficient option with the least collateral damage
(except for the timeouts on the affected DNS resolver / forwarder when trying
to reach 127.0.0.255). 

It should be remembered that this only applies to query sources who generate
excessive amounts of traffic over some period of time, and who do not react to
reasonable attempts at communication. 

The first line of defense would be to return 127.0.0.255 (or other BLOCKED
triggering value, to be defined) from the regular data zone nameservers, as
discussed in this bug.

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


----- End forwarded message -----

-- 
"Force, my friends, is violence; the supreme authority
from which all other authority is derived."
- Michael Ironside, Starship Troopers
http://www.ChaosReigns.com

From clewis+ietf@mustelids.ca  Thu Dec 22 08:06:36 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F2021F8AB0 for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 08:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.811
X-Spam-Level: 
X-Spam-Status: No, score=0.811 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmtQ91RJUI3i for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 08:06:35 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id ABC3721F8B2A for <asrg@irtf.org>; Thu, 22 Dec 2011 08:06:35 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pBMG6YP4025507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Thu, 22 Dec 2011 11:06:34 -0500
Message-ID: <4EF3558A.10109@mustelids.ca>
Date: Thu, 22 Dec 2011 11:06:34 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111222151208.GF28224@chaosreigns.com>
In-Reply-To: <20111222151208.GF28224@chaosreigns.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Handling of abusive DNSBL/WL clients
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 16:06:36 -0000

The BCP is fairly clear on this, especially when the DNSBL is being shut 
down.  As the BCP is this >< close to publication (I'm expecting 
official notification any minute now), it's way too late to make any 
substantive changes to it.  However, I was able to slip in a phrase in 
to further clarify how an answer outside of 127.0.0.0/8 should be 
treated - that was an oversight entirely aside from this issue.

Having a DNSBL return a value _inside_ 127.0.0.0/8 for _all_ queries in 
the "go away" case is an extremely bad idea, because many DNSBL clients, 
even strict RFC/BCP compliant ones (including my recollections of a 
brief glance at SA a few versions ago - I even STR SA treating TXT 
records back from SBL-XBL as "listed"), will treat it as "listing the 
world".

The DNSBL shutdown process would _also_ be perfectly appropriate for 
blocking abusive DNS queries, _without_ listing the world, _and_ by its 
very nature shedding the abusive queries.

From matthias@leisi.net  Thu Dec 22 13:25:17 2011
Return-Path: <matthias@leisi.net>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7A4421F8509 for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 13:25:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18UH3stv8czz for <asrg@ietfa.amsl.com>; Thu, 22 Dec 2011 13:25:17 -0800 (PST)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA2A21F8508 for <asrg@irtf.org>; Thu, 22 Dec 2011 13:25:17 -0800 (PST)
Received: by iadj38 with SMTP id j38so15505681iad.13 for <asrg@irtf.org>; Thu, 22 Dec 2011 13:25:16 -0800 (PST)
Received: by 10.50.12.167 with SMTP id z7mr10542326igb.19.1324589116540; Thu, 22 Dec 2011 13:25:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.50.197.133 with HTTP; Thu, 22 Dec 2011 13:24:55 -0800 (PST)
In-Reply-To: <4EF3558A.10109@mustelids.ca>
References: <20111222151208.GF28224@chaosreigns.com> <4EF3558A.10109@mustelids.ca>
From: Matthias Leisi <matthias@leisi.net>
Date: Thu, 22 Dec 2011 22:24:55 +0100
Message-ID: <CALgnk9rFb23WFK5bTM8zxvMAjOArva2+nQa09zogwhFiPneBOw@mail.gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Asrg] Handling of abusive DNSBL/WL clients
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 21:25:17 -0000

On Thu, Dec 22, 2011 at 5:06 PM, Chris Lewis <clewis+ietf@mustelids.ca> wrote:

> The DNSBL shutdown process would _also_ be perfectly appropriate for
> blocking abusive DNS queries, _without_ listing the world, _and_ by its very
> nature shedding the abusive queries.

Note that the case referred to by the OP is not about shutting down a
DNSxL, but about signaling to client applications (and
resolvers/forwarders) that their use is considered not acceptable by
the operator of the service.

Unfortunately, a straightforward REFUSED rcode results in a three-fold
increase in queries due to retries in most cases. A dedicated return
value which would cause at least certain applications to at least
temporarily suspend queries is helpful.

-- Matthias

From clewis+ietf@mustelids.ca  Sun Dec 25 11:21:31 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3C821F84B3 for <asrg@ietfa.amsl.com>; Sun, 25 Dec 2011 11:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.304
X-Spam-Level: 
X-Spam-Status: No, score=-0.304 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTOgQWuckWv9 for <asrg@ietfa.amsl.com>; Sun, 25 Dec 2011 11:21:31 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id 2E73421F8491 for <asrg@irtf.org>; Sun, 25 Dec 2011 11:21:31 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pBPJLUc6012470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Sun, 25 Dec 2011 14:21:30 -0500
Message-ID: <4EF777BA.9010409@mustelids.ca>
Date: Sun, 25 Dec 2011 14:21:30 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111222151208.GF28224@chaosreigns.com> <4EF3558A.10109@mustelids.ca> <CALgnk9rFb23WFK5bTM8zxvMAjOArva2+nQa09zogwhFiPneBOw@mail.gmail.com>
In-Reply-To: <CALgnk9rFb23WFK5bTM8zxvMAjOArva2+nQa09zogwhFiPneBOw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Handling of abusive DNSBL/WL clients
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Dec 2011 19:21:31 -0000

On 11-12-22 04:24 PM, Matthias Leisi wrote:
> On Thu, Dec 22, 2011 at 5:06 PM, Chris Lewis<clewis+ietf@mustelids.ca>  wrote:
>
>> The DNSBL shutdown process would _also_ be perfectly appropriate for
>> blocking abusive DNS queries, _without_ listing the world, _and_ by its very
>> nature shedding the abusive queries.
>
> Note that the case referred to by the OP is not about shutting down a
> DNSxL, but about signaling to client applications (and
> resolvers/forwarders) that their use is considered not acceptable by
> the operator of the service.

I realized that before I commented.

The point is that the "shutdown procedure" has the right result - 
shedding load and trying to signal to client applications that they 
should stop querying it.  All without touching any client code 
whatsoever.  A more sophisticated client could check the name server 
returned and thereby identify immediately that the DNSBL is in shutdown 
mode (if for an individual querier or in general).

> Unfortunately, a straightforward REFUSED rcode results in a three-fold
> increase in queries due to retries in most cases. A dedicated return
> value which would cause at least certain applications to at least
> temporarily suspend queries is helpful.

The problem is that with the installed base, returning any A record 
(whether 127/8 or not) has the risk of causing "list the world" 
behaviour in the client.
