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

Florian Weimer <fw@deneb.enyo.de> Sun, 16 November 2008 19:28 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 20E1B3A67FD; Sun, 16 Nov 2008 11:28:43 -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 9451C3A67FD for <ietf@core3.amsl.com>; Sun, 16 Nov 2008 11:28:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 Rqre4ckpKx3l for <ietf@core3.amsl.com>; Sun, 16 Nov 2008 11:28:40 -0800 (PST)
Received: from mail.enyo.de (mail.enyo.de [IPv6:2001:14b0:202:1::a7]) by core3.amsl.com (Postfix) with ESMTP id 39A523A67AA for <ietf@ietf.org>; Sun, 16 Nov 2008 11:28:40 -0800 (PST)
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1L1nIS-0008IM-4P; Sun, 16 Nov 2008 20:28:36 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from <fw@deneb.enyo.de>) id 1L1nIR-0003tt-JN; Sun, 16 Nov 2008 20:28:35 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
References: <200811161745.mAGHjEpQ016510@drugs.dv.isc.org>
Date: Sun, 16 Nov 2008 20:28:35 +0100
In-Reply-To: <200811161745.mAGHjEpQ016510@drugs.dv.isc.org> (Mark Andrews's message of "Mon, 17 Nov 2008 04:45:14 +1100")
Message-ID: <87vdunqxlo.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Cc: 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

* Mark Andrews:

> In message <87skpt279z.fsf@mid.deneb.enyo.de>, Florian Weimer writes:
>> * Stephane Bortzmeyer:
>> 
>> > Second question, the document indeed standardizes many things which
>> > are not in common use but does not point towards a rationale, so some
>> > choices are puzzling. Why TXT records to point to an URL and not
>> > NAPTR? Is this because of current usage in DNSxL? If so, this should
>> > be noted. But why IPv6 lists use a A record and not a AAAA? I am not
>> > aware of existing IPv6 lists so this cannot be the current usage?
>> 
>> The lack of a macro capability also means that it's basically
>> impossible to secure DNSBL zones with DNSSEC when they contain larger
>> chunks of address space; see the example in section 2.1.
>
> 	How so?

The expectation is that error messages generated from TXT records
contain the actual IP addresses which triggered the DNSBL lookups.  As
a result, if you list a /16 (say), you need publish 65,536 different
TXT records.

Currently, these records are synthesized using a macro capability in
the DNS server.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf