Re: [DNSOP] One Chair's comments on draft-wessels-dns-zone-digest

"Wessels, Duane" <dwessels@verisign.com> Mon, 30 July 2018 21:36 UTC

Return-Path: <dwessels@verisign.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 B5FC9130EE3 for <dnsop@ietfa.amsl.com>; Mon, 30 Jul 2018 14:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 tnTS6kAhGb71 for <dnsop@ietfa.amsl.com>; Mon, 30 Jul 2018 14:36:42 -0700 (PDT)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 A0213130EF0 for <dnsop@ietf.org>; Mon, 30 Jul 2018 14:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=8925; q=dns/txt; s=VRSN; t=1532986603; h=from:to:cc:date:message-id:references:in-reply-to: mime-version:subject; bh=TXyKkGWcuCpNUmuXzNVHOnev/FviXJvcUWnGw2uH4Cs=; b=RSDTUUf3ZCjWkAgf3+g0jygT1+p4s0aZYuKRcMaoHvP2l8GfAYe3Hofl A6sEMl3x5ic3MUlzLdR+lmNiE09lgBZZ6iyJXAjhwWjvot734hF1qUqcp kgQRAiGRy3EjwS+pAI3qzeON9Rq6JqjG9NHvirr+OxnylpUy/751GcjRM AONIwc1Z7BEJbeejyVbZGaGzCe0FqjnZ5RHtyXSGgVoUsIahPah9LTVlK YJu5EYOxxJqAYKQjHXEtQE1KhYf5/LxWS7B/+TmgUvUECxOmpim/Iema5 oJue8L1x/yo392BLAalFQz+gUZqJPteuxluzIL9Y15ssiW+rSZpG15XTH g==;
X-IronPort-AV: E=Sophos; i="5.51,424,1526356800"; d="p7s'?scan'208"; a="5320833"
IronPort-PHdr: 9a23:iFBvFBafXvoPvlkGtriBJpX/LSx+4OfEezUN459isYplN5qZr8S6bnLW6fgltlLVR4KTs6sC17KI9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCa8bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjmk8qxlSgLniD0fOjA57m/Zl9BwgqxYrhKvpRN/wpLbb46OOfpxYq/deMkXSXZdUstTUSFKH4Oyb5EID+oEJetUoYnyqEUVrRulGwasAPjvxidVjXH4wK01yeIhHh/I0Ac9GN8BrXrVo8vuNKcJT++1yLLIwC7db/xIwzf96ZPIchEuofGKR75/bc3RyUw2Gg7Dk16eqpTlMiuI2ugRqWSX8uhtWOy1h2I6qwx8rCKjy8gvh4XRm44Z1krI+Th7zYopP9G0VUF2bN2+HJdNtCyWL4V2Td0hTm10vSs3z6cJtJ2/cScRzZkqyQDTZOGGfoWN+R3uUOecLDV9iX9rdr+yhQu9/E69wePmTMa0ykxFri9dn9nJsXACygLc59CcSvt44kehwTGP1x3P6u1cIUA7i67bK5k5z7MtipQdqVnPES/ulkv5jaCaalgo9vK26+v7ZbXmvIecO5VuhQ7jKKguhNa/Af8+MgQUQ2eb/uG82KXi/U3/XrpKkuU7nrTFvJzAOMgWpKC0DxVI3osj5RuzFTir3dcAkXkCNl1FeRaHj4bzO1HJJfD1Feqwglqynzdw3PDJILnhAo7WI3jdjrjhZ7d961VdyAo8y9BT/Y5bCrYEIP7rQE/+qMTYDgMlMwyz2+vnFNd9140EVWKOHKCZLK3SvESH5uIqOeaMZYsVtCzhJPgi4v7klWU5lkMFfam1wZsXb2i1EelgI0WCZnrsmswMEWYUsQoiQuzmklqCUSRcZyX6Y6Vp2jA+QL2nBobFXYOsyOid3jj9H5BKaEhJD1mNFTHjcIDSCNkWbyfHaPBsiScJUaPlA6M83Bej/keux6VqNfHZ/jYwq5/51cN06OuVnhY3o28nR/+B2n2AGjkn1lgDQCU7ifhy
X-IPAS-Result: A2GCAgDWg19b/zCZrQpcGwEBAQEDAQEBCQEBAYVYCoN0lioliEKPCQgDhGwCgzU4FAECAQEBAQEBAgEBAoERgjUigmEBAQEBAgEjSA4FCwIBCA4KKgICAh8RJQIEDgUOgxIBgWcDDaxigS6EXoI1DYMXD4kZgUI+gTkME4JMglaCAYMoMYIkApIQh1UrAwYCg2WBWYZrkRWLI4ZtAgQCBAUCFIFYgXRwFWUBgj6QU2+Mf4EugRsBAQ
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1466.3; Mon, 30 Jul 2018 17:36:41 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d]) by BRN1WNEX01.vcorp.ad.vrsn.com ([fe80::a89b:32d6:b967:337d%5]) with mapi id 15.01.1466.003; Mon, 30 Jul 2018 17:36:41 -0400
From: "Wessels, Duane" <dwessels@verisign.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
CC: dnsop <dnsop@ietf.org>
Thread-Topic: [EXTERNAL] [DNSOP] One Chair's comments on draft-wessels-dns-zone-digest
Thread-Index: AQHUJlWid7/zygOQ3UWQ7Csx+jA1CaSokPOA
Date: Mon, 30 Jul 2018 21:36:40 +0000
Message-ID: <AFF1322C-8DFD-4790-826E-84AA3A684D4E@verisign.com>
References: <CADyWQ+HizOJsE9EZ=VEvrbnnyPwaG_yBRg7fP5VvUNTdnidXZA@mail.gmail.com>
In-Reply-To: <CADyWQ+HizOJsE9EZ=VEvrbnnyPwaG_yBRg7fP5VvUNTdnidXZA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: multipart/signed; boundary="Apple-Mail=_A2DD2E3E-79C1-4786-B0BA-D6C0D5816694"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Hr5vXsixg1-lG0rpxvd1BCxngpw>
Subject: Re: [DNSOP] One Chair's comments on draft-wessels-dns-zone-digest
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 30 Jul 2018 21:36:45 -0000


> On Jul 28, 2018, at 2:30 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> (these are just my comments alone. So take it as such)

Thanks Tim,

I don't think these questions are already answered, so thank you for bringing them up.

> 
> The draft states in the Motivation section:
>  "The motivation and design of this protocol enhancement is tied to the DNS root zone [InterNIC]."
> 
> Your Design Overview states that this will work for zones that are "relatively stable and have infrequent updates".  I think some descriptive text about the type of zone this RR type attempts to address should be more clearly spelled out in your Abstract. 

Noted.

> 
> For the ZONEMD RR Type, where in the registry do the authors think it should go?  While some of that falls on the Expert Review process,  I think the document authors should capture their rationale in the document.  If the proposed RR Type is greater than 256 (which I think it does), it does not appear to require a Standards Track document, just Expert Review. 

Thanks. Is there a proper way to word such a request?  Looking at RFC6895 I'm not seeing a real difference in the way that ranges "<=127" and ">=256" are described.

> 
> I ask this since the document is listed as "Standards Track" and the document is narrowly scoped to focus on the Root  Zone. Additionally the document states: "This specification is OPTIONAL to implement by both publishers and consumers of zone file data."   This appears to be contradictory to me, but hopefully someone can illuminate me. 
> 
> I ask all of this because we have seen the working group start to push back on similarly scoped Proposed Standards (kskroll-sentinel).  
> 
> Though I do find it amusing that you use "The Camel" as the excuse for such a limited scope use case, even while requesting a Proposed Standard! 

I can accept that Standards Track is the wrong choice here.  Chalk it up to my naïveté.  I suppose Experimental would be more appropriate?

DW