Re: [DNSOP] I-D Action: draft-ietf-dnsop-nsec-aggressiveuse-02.txt

Bob Harold <rharolde@umich.edu> Tue, 13 September 2016 19:50 UTC

Return-Path: <rharolde@umich.edu>
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 13950126FDC for <dnsop@ietfa.amsl.com>; Tue, 13 Sep 2016 12:50:25 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 hJAhWqsUHsAV for <dnsop@ietfa.amsl.com>; Tue, 13 Sep 2016 12:50:22 -0700 (PDT)
Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FFB712B00C for <dnsop@ietf.org>; Tue, 13 Sep 2016 12:50:21 -0700 (PDT)
Received: by mail-yb0-x22e.google.com with SMTP id x93so66203947ybh.1 for <dnsop@ietf.org>; Tue, 13 Sep 2016 12:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=k3JIojJ8+jUSq7qgW6UxTk0qIND33vkxo6E057s6Zlk=; b=UdtrhmJPvWYuCqFoMSzM2T1FbhByebTIfPm/p0HnS90quVNb3acBlxRLIBNcJednas 312Vg5KwCHwfwflZ2l6Gva7P77htRM8L7kV/3fho496VkDJOzIwwfm6OpFoLZfUO69Gq ZMGGE7o+8zQ+vZOo55T9LBzoc8kcwayLnQyK0Zl8Gn0iTeNlreXmpLB0/ylqic36y396 LMpHUOf4nb2TWq7Kw2iwQ/Ar+vQir5GkkAxcF0Z6z7JhOfuihZ1+IIO+2Y+VhAEAumXt uKoiWMg+ee1gFfJC8Ql1hEYoSlomj6Sus6WK5gCl3dpTgPgSwWzWwCpnIDapOvINP8bL DF/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=k3JIojJ8+jUSq7qgW6UxTk0qIND33vkxo6E057s6Zlk=; b=YG5RtHMGE3rJeBh0Dtfi4N+i73VldHS1P6CPedpATbDpNu2d9bI8Ej/V0gKcSzOhSD DrbB3gP2F14QwGSHWBUuiiue/vOWedusCbK2ObQtOFxoyKO1KNpWKJqN5UudI9z1eS6s 3UuDWffu9ewYs00R0iBlRDJtEJsQkQ3Q6tjkNUNDPcKXeW3FRaR8pkHvA83cxyB7GT6j sEPNSupNa3KL/Jm8+zgNWwBcrmTQJ3ababoFLZ5qp3dXgMAgHTZxFRpkHD2HZ9iicu6b Yf1GIc9+K+tXR3azpRfJcUhyIP3Mv6mcX2ptdnriAr2A9b08FnpqDoIq3O0NCT0lm5Yc GOeA==
X-Gm-Message-State: AE9vXwO1qQfh0UfSBAc+NiTCEJdJmHv/UhV6LTiPKQ+LR8kpWPAghs4+AfyNnnWdqNslGBb6XQat4V2h7DAxTsH+
X-Received: by 10.37.123.68 with SMTP id w65mr2786697ybc.116.1473796221029; Tue, 13 Sep 2016 12:50:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.255.3 with HTTP; Tue, 13 Sep 2016 12:50:20 -0700 (PDT)
In-Reply-To: <147378048323.23516.13638129997007497154.idtracker@ietfa.amsl.com>
References: <147378048323.23516.13638129997007497154.idtracker@ietfa.amsl.com>
From: Bob Harold <rharolde@umich.edu>
Date: Tue, 13 Sep 2016 15:50:20 -0400
Message-ID: <CA+nkc8AGUPafGmRsfs+0gRk6ZZ-aeFK4VPwmZdSVqUHy0We9Gw@mail.gmail.com>
To: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=001a114dc0c839e01e053c68ec35
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EbPuBgFykHoA0yBrrQTQTt41nJQ>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-nsec-aggressiveuse-02.txt
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, 13 Sep 2016 19:50:25 -0000

On Tue, Sep 13, 2016 at 11:28 AM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations of the IETF.
>
>         Title           : Aggressive use of NSEC/NSEC3
>         Authors         : Kazunori Fujiwara
>                           Akira Kato
>                           Warren Kumari
>         Filename        : draft-ietf-dnsop-nsec-aggressiveuse-02.txt
>         Pages           : 13
>         Date            : 2016-09-13
>
> Abstract:
>    The DNS relies upon caching to scale; however, the cache lookup
>    generally requires an exact match.  This document specifies the use
>    of NSEC/NSEC3 resource records to generate negative answers within a
>    range.  This increases performance / decreases latency, decreases
>    resource utilization on both authoritative and recursive servers, and
>    also increases privacy.  It may also help increase resilience to
>    certain DoS attacks in some circumstances.
>
>    This document updates RFC4035 by allowing resolvers to generate
>    negative answers based upon NSEC/NSEC3 records.
>
>    [ Ed note: Text inside square brackets ([]) is additional background
>    information, answers to frequently asked questions, general musings,
>    etc.  They will be removed before publication.This document is being
>    collaborated on in Github at: https://github.com/wkumari/draft-ietf-
>    dnsop-nsec-aggressiveuse.  The most recent version of the document,
>    open issues, etc should all be available here.  The authors
>    (gratefully) accept pull requests.
>
>    Known / open issues [To be moved to Github issue tracker]:
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-nsec-aggressiveuse/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-nsec-aggressiveuse-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-nsec-aggressiveuse-02
>
>
> Looks good, but this one sentence in  "5.4. Wildcard" does not read well
to me:

"But, it will be more
effective when both are enabled since the resolver can determine the
name subject to wildcard would not otherwise exist more efficiently."

Not sure how to reword it.

-- 
Bob Harold