IETF Logo Mail Archive

Re: [Asrg] I-D Action: draft-irtf-asrg-dnsbl-08.txt (fwd)

Matthias Leisi <matthias@leisi.net> Wed, 19 November 2008 13:34 UTC

Return-Path: <asrg-bounces@irtf.org>
X-Original-To: asrg-archive@optimus.ietf.org
Delivered-To: ietfarch-asrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B68A33A6B8B; Wed, 19 Nov 2008 05:34:10 -0800 (PST)
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF22B3A6B8A for <asrg@core3.amsl.com>; Wed, 19 Nov 2008 05:34:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.189
X-Spam-Level:
X-Spam-Status: No, score=-9.189 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, RCVD_IN_DNSWL_HI=-8, 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 BLfq56Sa9CfI for <asrg@core3.amsl.com>; Wed, 19 Nov 2008 05:34:09 -0800 (PST)
Received: from mail.leisi.net (trillian.net.astrum.ch [213.144.132.251]) by core3.amsl.com (Postfix) with ESMTP id A303C3A6B89 for <asrg@irtf.org>; Wed, 19 Nov 2008 05:34:08 -0800 (PST)
X-Spam-ASN: AS44038 195.186.0.0/17
X-Spam-Relays: trusted= untrusted=[ ip=195.186.55.199 rdns=tower.bluewin.ch helo=!172.22.44.226! by=mail.leisi.net ident= envfrom= intl=0 id=B4CBFDED32 auth= msa=0 ] internal= external=[ ip=195.186.55.199 rdns=tower.bluewin.ch helo=!172.22.44.226! by=mail.leisi.net ident= envfrom= intl=0 id=B4CBFDED32 auth= msa=0 ]
X-Spam-Hammy: 0.000-+--H*u:2.0.0.17, 0.000-+--H*UA:2.0.0.17, 0.000-+--H*UA:20080914, 0.000-+--H*u:20080914, 0.000-+--schrieb
X-Spam-Spammy: 0.905-7--donate
X-Spam-LastExternal: ip=195.186.55.199 rdns=tower.bluewin.ch helo=!172.22.44.226!
X-Spam-DNSWL: NO
Received: from [172.22.44.226] (tower.bluewin.ch [195.186.55.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.leisi.net (Postfix) with ESMTP id B4CBFDED32 for <asrg@irtf.org>; Wed, 19 Nov 2008 14:34:02 +0100 (CET)
Message-ID: <492415CA.6080207@leisi.net>
Date: Wed, 19 Nov 2008 14:34:02 +0100
From: Matthias Leisi <matthias@leisi.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4606143.01227048087075.JavaMail.franck@franck-martins-macbook-pro.local> <49235469.8090306@nortel.com> <4923AC56.8060509@leisi.net> <492410A0.7050804@nortel.com>
In-Reply-To: <492410A0.7050804@nortel.com>
Subject: Re: [Asrg] I-D Action: draft-irtf-asrg-dnsbl-08.txt (fwd)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: asrg-bounces@irtf.org
Errors-To: asrg-bounces@irtf.org

Chris Lewis schrieb:

>> An old wish: Have some protocol to enable queries like "return all
>> listings for IP addresses in a.b.c.d/N" (for some reasonably max value
>> of N, possibly 24?).
> 
> We'd only have to issue more than 65536 of those to check our space ;-)

Maybe you should donate some of that space ;-)

> Yes, something like that would be nice and I don't think too many DNSBL
> operators would object (at least in theory).  Some DNSBLs offer by-email
> notification.  Others might want to, but don't for whatever reason.

Thinking a bit further, such a "range query" is not only a nice to have, 
but pure necessity in IPv6-land, where you will hardly ever will want to 
deal with individual IP addresses, but with - what is the current 
smallest customer allocation? /64? - /64s.

> However:
> 
> 1) The BCP is a wrong place to describe a protocol for that.

ACK.

Maybe it's time to start experimenting with some kind of an "IPv6 
reputation protocol". The more I think about it, the less I'm convinced 
that we can (or should) simply continue using the IPv4 approach.

-- Matthias

_______________________________________________
Asrg mailing list
Asrg@irtf.org
https://www.irtf.org/mailman/listinfo/asrg

v2.23.0 | Report a Bug | By Email