IETF Logo Mail Archive

Re: [dnsext] bitmap inference was Re: ... - NXDOMAIN for emptynon-terminals

"George Barwood" <george.barwood@blueyonder.co.uk> Tue, 29 March 2011 18:12 UTC

Return-Path: <george.barwood@blueyonder.co.uk>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B9543A6A7F for <dnsext@core3.amsl.com>; Tue, 29 Mar 2011 11:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.161
X-Spam-Level:
X-Spam-Status: No, score=-0.161 tagged_above=-999 required=5 tests=[AWL=0.685, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
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 4ZIl9w-KZixz for <dnsext@core3.amsl.com>; Tue, 29 Mar 2011 11:12:36 -0700 (PDT)
Received: from mtaout03-winn.ispmail.ntl.com (mtaout03-winn.ispmail.ntl.com [81.103.221.49]) by core3.amsl.com (Postfix) with ESMTP id 112063A6A76 for <dnsext@ietf.org>; Tue, 29 Mar 2011 11:12:35 -0700 (PDT)
Received: from know-smtpout-4.server.virginmedia.net ([62.254.123.1]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20110329181411.TONK13167.mtaout03-winn.ispmail.ntl.com@know-smtpout-4.server.virginmedia.net>; Tue, 29 Mar 2011 19:14:11 +0100
Received: from [92.238.99.235] (helo=GeorgeLaptop) by know-smtpout-4.server.virginmedia.net with smtp (Exim 4.63) (envelope-from <george.barwood@blueyonder.co.uk>) id 1Q4dQg-00043t-V9; Tue, 29 Mar 2011 19:14:11 +0100
Message-ID: <A5D8841CEB8F4BF9A007C8B6408C363C@local>
From: George Barwood <george.barwood@blueyonder.co.uk>
To: Edward Lewis <Ed.Lewis@neustar.biz>
References: <alpine.LSU.2.00.1103281507410.5244@hermes-1.csi.cam.ac.uk><8EA8D1A36B8F49 68ABE973C39CA5E0E0@local><a06240800c9b78d52751f@[10.31.200.116]><FCB25297B FF0419692724D36AF3BC99E@local> <a06240804c9b79c870558@[10.31.200.119]><55128075215341BD92DCAAD00450FA85@l ocal> <a06240809c9b7b7143e51@[10.31.200.119]> <3B987BF13718424BBA818C248C428E64@local> <a06240800c9b7c543104f@[10.31.200.119]>
Date: Tue, 29 Mar 2011 19:14:38 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-Cloudmark-Analysis: v=1.1 cv=R50lirqlHffDPPkwUlkuVa99MrvKdVWo//yz83qex8g= c=1 sm=0 a=dSD2fgld_FcA:10 a=8nJEP1OIZ-IA:10 a=a5Gf7U6LAAAA:8 a=48vgC7mUAAAA:8 a=bgHunIh9sCw15xUeD04A:9 a=pVe9PNzGAL91H791Ws9FEKGebxcA:4 a=wPNLvfGTeEIA:10 a=yHIqe9kG5mgA:10 a=lZB815dzVvQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, dnsext@ietf.org
Subject: Re: [dnsext] bitmap inference was Re: ... - NXDOMAIN for emptynon-terminals
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 18:12:37 -0000

----- Original Message ----- 
From: "Edward Lewis" <Ed.Lewis@neustar.biz>
To: "George Barwood" <george.barwood@blueyonder.co.uk>
Cc: <dnsext@ietf.org>; "Edward Lewis" <Ed.Lewis@neustar.biz>
Sent: Tuesday, March 29, 2011 6:28 PM
Subject: bitmap inference was Re: ... - NXDOMAIN for emptynon-terminals


> At 18:16 +0100 3/29/11, George Barwood wrote:
> 
>>What I'm saying is that an NSEC bitmap tells a client the complete set
>>of types that don't exist for a domain,
> 
> That's wrong.  The bitmap presents information signed by the 
> authority demonstrating that the type you requested does not exist at 
> the name.

The standard ( http://tools.ietf.org/html/rfc4034#section-4.1.2 ) says

   The Type Bit Maps field identifies the RRset types that exist at the
   NSEC RR's owner name.

That's clear and unambiguous, I cannot see how you can read that any other way.
But I'm going to stop here and see if others have views on this.

George

v2.23.0 | Report a Bug | By Email