[DNSOP] Reserved field in draft-wessels-dns-zone-digest-04.txt

Paul Hoffman <paul.hoffman@icann.org> Tue, 23 October 2018 22:16 UTC

Return-Path: <paul.hoffman@icann.org>
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 0FAA4129BBF for <dnsop@ietfa.amsl.com>; Tue, 23 Oct 2018 15:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 t7NCfXXtHA7k for <dnsop@ietfa.amsl.com>; Tue, 23 Oct 2018 15:16:44 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1C89128CE4 for <dnsop@ietf.org>; Tue, 23 Oct 2018 15:16:44 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 23 Oct 2018 15:16:42 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Tue, 23 Oct 2018 15:16:42 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: Reserved field in draft-wessels-dns-zone-digest-04.txt
Thread-Index: AQHUax4TO0xq/GYn/0CpnXlBEtAZMA==
Date: Tue, 23 Oct 2018 22:16:41 +0000
Message-ID: <3AED6137-0957-4EEE-B317-7178B00AB7CF@icann.org>
References: <154020795105.15126.7681204022160033203@ietfa.amsl.com>
In-Reply-To: <154020795105.15126.7681204022160033203@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_4CECA1F9-C7BB-4784-AE46-8BDD31732E2B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6EDSr6Gtu7JG3O1E0m4FaCA5Y10>
Subject: [DNSOP] Reserved field in draft-wessels-dns-zone-digest-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 23 Oct 2018 22:16:46 -0000

Section 5 says:

   FOR DISCUSSION: The authors are willing to remove the Reserved field
   from this specification if the working group would prefer it.  It
   would mean, however, that a future version of this protocol designed
   to efficiently support large, dynamic zones would most likely require
   a new RR type.

Please strongly consider removing the Reserved field so that designing an way to do a message digest over a dynamic zone can be done independently.

Quite frankly, if the Reserved field isn't there and it's clear that this is for complete zones, I see no reason why this should even be considered experimental. The mic line at the presentation at the recent DNS-OARC seems to agree with wanting this for real, as soon as possible.

--Paul Hoffman