IETF Logo Mail Archive

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

John Levine <johnl@iecc.com> Sun, 16 November 2008 21:46 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 172FB3A697B; Sun, 16 Nov 2008 13:46:31 -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 A2E313A697B for <ietf@core3.amsl.com>; Sun, 16 Nov 2008 13:46:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.448
X-Spam-Level:
X-Spam-Status: No, score=-14.448 tagged_above=-999 required=5 tests=[AWL=-0.348, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, 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 1TfDD9XGsUzC for <ietf@core3.amsl.com>; Sun, 16 Nov 2008 13:46:28 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 8E49B3A6953 for <ietf@ietf.org>; Sun, 16 Nov 2008 13:46:28 -0800 (PST)
Received: (qmail 73401 invoked from network); 16 Nov 2008 21:46:27 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 16 Nov 2008 21:46:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=t1108; i=johnl@user.iecc.com; bh=OxUrOXl07/YK3SUQ1vcQ+zxUtKWkOYOQwQ/pwhW0Gg8=; b=QWtokb99O7P7/q4fMF5YuyOaPeb2EWiwmjzZkgnwlHlZmG7EJYNDcfLKFF6SLb7JeeaUFr1WN+/1MFLwI1ANCcsIA5uO6R9ASwfoJNKuJ4//SpMWC0F7egR9T4z480qu
Date: Sun, 16 Nov 2008 21:46:27 -0000
Message-ID: <20081116214627.59277.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
In-Reply-To: <87vdunqxlo.fsf@mid.deneb.enyo.de>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: fw@deneb.enyo.de
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

>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.

Some do, some don't.  In any event I agree that DNSSEC is not ideally
suited to signing DNSBLs, but I would think that with some judicious
partitioning into subzones the problem wouldn't be intractable.

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email