Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-zone-digest-02.txt

Vladimír Čunát <> Thu, 07 November 2019 11:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4244D120133 for <>; Thu, 7 Nov 2019 03:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id G6qU6Sjlxu3Z for <>; Thu, 7 Nov 2019 03:55:36 -0800 (PST)
Received: from ( [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 389C212012E for <>; Thu, 7 Nov 2019 03:55:35 -0800 (PST)
Received: from [IPv6:2001:1488:fffe:6:a9d5:8b63:1002:9e05] (unknown [IPv6:2001:1488:fffe:6:a9d5:8b63:1002:9e05]) by (Postfix) with ESMTPSA id 1CE4A140D1A for <>; Thu, 7 Nov 2019 12:55:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=default; t=1573127733; bh=+MpVVFbTnrVzIqnI9gy5EuX8maP+d5ebbRJOX3Dutvo=; h=From:To:Date; b=Z9gPOUHJb4/SNZC8G3RLTe3mSFx2m4T6WPH5AzkxgjnQqsYptTRmxd1PoibIRZTLw JO060kZDd8rnq1Iev2NVicuQYBpamvhg11NYOUFzUuUftJVwZz8eAs0JdRIloIQ4wh HK9pemgv78xf/TZ0Bu71ho9cxQdU6I6hS/lyHhgg=
References: <> <>
From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?= <>
Message-ID: <>
Date: Thu, 7 Nov 2019 12:56:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.100.3 at
X-Virus-Status: Clean
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-zone-digest-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Nov 2019 11:55:38 -0000


On 10/28/19 10:32 PM, Wessels, Duane wrote:
> The one defined hash algorithm SHA384 has been renamed to SHA384-STABLE to reflect that it designed for use on stable (or small) zones where it is not burdensome to recalculate the digest over the entire zone data each time.

Tiny nitpick: calling it "SHA384-STABLE" might be a tiny bit confusing
(to me), as I've seen that word refer to some particular hashing
approaches/properties.  Actually some of the algorithms that efficiently
recompute after small changes in large zones... I'd even tend to call
those digests (more) "stable"/"steady" intuitively, but that might be
personal :-)  I certainly don't have a strong opinion on the naming and
don't want to bike-shed, but I could imagine calling it "simple" or
"flat" or something along those lines.