IETF Logo Mail Archive

Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse

Ralph Dolmans <ralph@nlnetlabs.nl> Tue, 20 December 2016 12:18 UTC

Return-Path: <ralph@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 610491295BA for <dnsop@ietfa.amsl.com>; Tue, 20 Dec 2016 04:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.101
X-Spam-Level:
X-Spam-Status: No, score=-10.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gheK6anhrXTV for <dnsop@ietfa.amsl.com>; Tue, 20 Dec 2016 04:18:41 -0800 (PST)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459631295E6 for <dnsop@ietf.org>; Tue, 20 Dec 2016 04:18:41 -0800 (PST)
Received: from [192.168.178.36] (a82-161-47-203.adsl.xs4all.nl [82.161.47.203]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 98305D526 for <dnsop@ietf.org>; Tue, 20 Dec 2016 13:18:38 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1482236318; bh=T8EkiQCL1MJhhH593V9V1r3CT2NRxu/hX474GLpKHVA=; h=Subject:To:References:From:Date:In-Reply-To; b=BFIKwrIZZ3CCwXUCKDlpokHw0M3r3EMwKaym7kI2ua/hYZsWupLXCOkPLsp7HV8jq fzmlfsXHVW6neI1ztsY+/BSzeENP0r8vdizddA/FkL2SY//TRTOuTIGz0Y/HsqShxR 2FXGm+6kl7FGUOH2TEev/BQBOTXyQwhxUD78oGOY=
To: dnsop@ietf.org
References: <CADyWQ+EJ0LO=pU-yUdEHwC3aP5KdXxsnD9kEvmmTeAoe0BxK3A@mail.gmail.com> <CAHw9_i+uwq9ofZ6hdG7Ngyz4s23F0XgiMSzazwFKw7DiTcEFDQ@mail.gmail.com> <20161220105915.xkrk5h57lqqfbsl2@nic.fr>
From: Ralph Dolmans <ralph@nlnetlabs.nl>
Message-ID: <934d3900-a1d9-66fd-dd28-f549f4f11370@nlnetlabs.nl>
Date: Tue, 20 Dec 2016 13:18:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <20161220105915.xkrk5h57lqqfbsl2@nic.fr>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Iv1mxko-ZtUBkNWPZnnnwT9LR-A>
Subject: Re: [DNSOP] Second Working Group Last Call - draft-ietf-dnsop-nsec-aggressiveuse
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2016 12:18:42 -0000

Hi,

On 20-12-16 11:59, Stephane Bortzmeyer wrote:
> One of my comments was not addressed. I would like, in section 10, see
> some details about what exactly is implemented by Unbound and Google
> Public DNS:
> 
> * synthesis of NXDOMAIN from NSEC (obviously; that's the minimum)
> * synthesis of NXDOMAIN from NSEC3 (if no opt-out)
> * synthesis of NODATA from NSEC/NSEC3
> * synthesis of positive answers from wilcards+NSEC
> * all of them?

NSEC reply synthesis is not (yet) implemented in Unbound. I do not know
why it is mentioned in section 10.
I know of the existence of a patch, but that one seems to have flaws and
is incomplete.

Unbound currently uses its negative cache to prove non-existence of DS
records. Not for synthesizing replies (although it is on our road-map
for the very near future).

Regards,
-- Ralph

v2.23.0 | Report a Bug | By Email