[DNSOP] Fwd: Comments on draft-ietf-dnsop-qname-minimisation

Brian Dickson <brian.peter.dickson@gmail.com> Mon, 29 December 2014 22:22 UTC

Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA23F1A9172 for <dnsop@ietfa.amsl.com>; Mon, 29 Dec 2014 14:22:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 XVixCyfigRig for <dnsop@ietfa.amsl.com>; Mon, 29 Dec 2014 14:22:37 -0800 (PST)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAD991ACDF4 for <dnsop@ietf.org>; Mon, 29 Dec 2014 14:22:36 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id rl12so10701484iec.26 for <dnsop@ietf.org>; Mon, 29 Dec 2014 14:22:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=J/TFxvEdnvi/7OfJuMrMDCo94PE/+FSCzQNsXiP1Gio=; b=ujJxKqrjmmSY01rgO9eb8l4LorWM/1RxwhJE7K+onB/SDtD/djkKFYBBC99yojsPhq F7ai/ccxGJwM+MLt1nNwFXoSbhba44v9SJeanLA4pjlZbcVBTEQYg6SBTfnOppvkmgta +PFPV6B6TopNPYLTtXHEPWxYpCEuxHrXLT/rpS5IOxSyUVOSfWH4zLJMJ/wslD3vNWdB ur5cP9YY29AXLGYFlQA+Jxi5NZBUmNI1tad2zQPUlQ1+v+9GLLmUrNkW7m/W5zCZSPqb Sop7XXaBoYyK4ElHJr3RPEmSmiyELp+W1JlDH/CKNKdsabL1zg2OQDlWW69HSGew9vt5 8ipw==
MIME-Version: 1.0
X-Received: by 10.107.130.212 with SMTP id m81mr51671814ioi.46.1419891756117; Mon, 29 Dec 2014 14:22:36 -0800 (PST)
Received: by 10.64.69.167 with HTTP; Mon, 29 Dec 2014 14:22:36 -0800 (PST)
In-Reply-To: <CAH1iCirCRpJxHWu62nCSTCmSumXfTNHi=-jt5eWXzRgspJjm9w@mail.gmail.com>
References: <CAH1iCirCRpJxHWu62nCSTCmSumXfTNHi=-jt5eWXzRgspJjm9w@mail.gmail.com>
Date: Mon, 29 Dec 2014 14:22:36 -0800
Message-ID: <CAH1iCip7iGgM=eiaVcy3fHx+KdOJgd5Rh8zLsnDPMgoEnE-HvA@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f7d7abe37a6050b624f71"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/0tWPSDYMwam7573c3RE0SnLP8ug
Subject: [DNSOP] Fwd: Comments on draft-ietf-dnsop-qname-minimisation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 29 Dec 2014 22:22:39 -0000

I'm a big fan of this.

These comments are meant to be constructive, and with the goal of improving
the draft quality and/or quality of the underlying protocol.

And, of course, I speak only for myself.

In no particular order:

- In section 3, it might be good to add a paragraph about the implications
for HAMMER. Specifically, in addition to pre-fetching records that would
otherwise expire, it is probably worth probing for the introduction of zone
cuts where none previously existed (i.e. confirm their continued absence,
or discover them.)

- Another comment for Section 4 (other advantages), it may be worth
mentioning improved look-up performance for TLD operators, which offsets
the loss of query data. A 2-label QNAME query is optimal for finding the
delegation owner name in a delegation-only TLD.

- Another thing to possibly call out is the behavior of some name servers
when the QNAME is an Empty Non-Terminal, e.g. a non-zone-cut with a child,
but no RRs at the owner name. I seem to recall something along those lines
but don't recall details, e.g. which software, version, etc., has this
issue.

Hope this is helpful.

Brian Dickson