Re: [DNSOP] BULK vs. draft-ietf-dnsop-nsec-aggressiveuse

"John R Levine" <johnl@taugh.com> Sun, 23 July 2017 06:21 UTC

Return-Path: <johnl@taugh.com>
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 D4CDA129B2A for <dnsop@ietfa.amsl.com>; Sat, 22 Jul 2017 23:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=QCCcHMnG; dkim=pass (1536-bit key) header.d=taugh.com header.b=OZNK1HUb
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 bPMz1Bx0-hqm for <dnsop@ietfa.amsl.com>; Sat, 22 Jul 2017 23:21:55 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33AAE126C2F for <dnsop@ietf.org>; Sat, 22 Jul 2017 23:21:54 -0700 (PDT)
Received: (qmail 96820 invoked from network); 23 Jul 2017 06:21:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=17a32.59744081.k1707; bh=AIltPWpB24NM9mq+w6xoWuMo7N5V0Is9GRAUHDbyXBg=; b=QCCcHMnGGT0VzC+F0aaJdpsdTe02rmQ2dw3JBKw0C1ClL/06B2qCtj4utdrDaTce4hGa62A5pm7E/257m7FG2gtBPQlTfayhfNttmHv2boiaFhiWGbMofpe7Ox9KNI+hocRLUj490R94sLKb7Amp/OGUQQrq4zr9UpIRVTiVtv1WN7e2jemZXFBzDJ+Lz1REBVma6ABZTjDrcjSNRR8Es/+SrRHaLqTb6Qu3zp+NuUgDvSK9TJmjNtRRJ9DZsMB+
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=17a32.59744081.k1707; bh=AIltPWpB24NM9mq+w6xoWuMo7N5V0Is9GRAUHDbyXBg=; b=OZNK1HUb9sjtUlcSt9Ao5DNlYjT+sxCGUvCdqeMB82+ISLjW+siswggUVD+0zKCEQygaFXG+hUlQpX/vkns8hMpxjCJ/q6GH56LE6qqtXgEz89FdMDI56S41h4Pyt/N5ewiZ4Nd2mzBaUAH0mu0V2OPwWtKOqaZheFtBEuHgGV49gy+psbGnogmwE4BEYGZYerwVP1rUwBgN1CmgYVCeitRissK2aaRDj383m48tB+ZLKYgJ+HY0/xC2YSRZGYyx
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 23 Jul 2017 06:21:53 -0000
Date: Sun, 23 Jul 2017 08:21:53 +0200
Message-ID: <alpine.OSX.2.21.1707230821120.10444@ary.local>
From: John R Levine <johnl@taugh.com>
To: "Woodworth, John R" <John.Woodworth@CenturyLink.com>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <A05B583C828C614EBAD1DA920D92866BD082471E@PODCWMBXEX501.ctl.intranet>
References: <20170722155338.9829.qmail@ary.lan> <A05B583C828C614EBAD1DA920D92866BD082471E@PODCWMBXEX501.ctl.intranet>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3j_fKmmcJo0034HYiAhhzvLIGDA>
Subject: Re: [DNSOP] BULK vs. draft-ietf-dnsop-nsec-aggressiveuse
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 23 Jul 2017 06:21:57 -0000

>> Speaking of nsec-aggressiveuse, while staring out the window of
>> the train this morning it occurred to me that BULK breaks
>> NXDOMAIN synthesis, too, both the NSEC kind and the RFC 8020 kind.

> I'm confused, wouldn't a simple NS record solve this?

No, this is all within the zone where BULK is synthesizing records.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly