Re: [DNSOP] The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"

"Peter van Dijk" <peter.van.dijk@powerdns.com> Fri, 21 July 2017 23:59 UTC

Return-Path: <peter.van.dijk@powerdns.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 CB0241243F3 for <dnsop@ietfa.amsl.com>; Fri, 21 Jul 2017 16:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LHXLMnjq9bnU for <dnsop@ietfa.amsl.com>; Fri, 21 Jul 2017 16:59:01 -0700 (PDT)
Received: from shannon.7bits.nl (shannon.7bits.nl [IPv6:2a01:1b0:202:40::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 166B3126B7E for <dnsop@ietf.org>; Fri, 21 Jul 2017 16:59:01 -0700 (PDT)
Received: from [192.168.0.16] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peter) by shannon.7bits.nl (Postfix) with ESMTPSA id C24B61BD15; Sat, 22 Jul 2017 01:58:59 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: "dnsop WG" <dnsop@ietf.org>
Date: Sat, 22 Jul 2017 01:58:59 +0200
Message-ID: <3E029203-62B9-43ED-992C-CBF4A33156EC@powerdns.com>
In-Reply-To: <A05B583C828C614EBAD1DA920D92866BD081E686@PODCWMBXEX501.ctl.intranet>
References: <150040947342.11401.6673996996138598307.idtracker@ietfa.amsl.com> <CAKr6gn3xHZ6bzSSLoLt0FQzBrunqFPa-PFG6bAjLpfdEsD_iGQ@mail.gmail.com> <alpine.LRH.2.20.1707190347390.10419@ns0.nohats.ca> <alpine.DEB.2.11.1707191023090.27210@grey.csi.cam.ac.uk> <A05B583C828C614EBAD1DA920D92866BD081C441@PODCWMBXEX501.ctl.intranet> <AED0BED0-BF26-4FD2-9ACD-F2043C248C1A@rfc1035.com> <A05B583C828C614EBAD1DA920D92866BD081E686@PODCWMBXEX501.ctl.intranet>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/erM3baW2S6TwIRsELtxtp9pht_g>
Subject: Re: [DNSOP] The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"
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: Fri, 21 Jul 2017 23:59:04 -0000

Hello John,

On 20 Jul 2017, at 3:17, Woodworth, John R wrote:

> Although in practice the name would likely be shorter and potentially
> include other customer attributes,
> say acmewabbit-21f-5bff-fec3-ab9d.example.com
>
>    1. This shows the owner is example.com, customer acmewabbit
>    2. Reverse lookups are helpful for tools (e.g. traceroute)
>       and logs.

1 and 2 could be covered with a wildcard PTR, as I think Tony Finch 
pointed out.

> Forget for a moment about IPv6.  This draft makes $GENERATE more
> memory efficient, scales bigger, stays intact through AXFR's
> and yes -it makes some nameservers (authoritative) work a bit more
> as a trade-off.

One could make $GENERATE more efficient without actually implementing 
the BULK RR, by taking your pattern matching logic and implementing it 
inside the name server. Of course, this makes generating the NSEC/NSEC3 
chain much harder than it is with today’s $GENERATE implementations 
that actually generate all the names.

A very interesting puzzle would be implementing BULK support, based on 
the pattern matching in the draft, -without- doing NSEC(3) white/black 
lies - i.e. generating the widest possible NSEC instead of the narrowest 
one. For NSEC3 I suspect this is not feasible.

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/