Re: [DNSOP] Working Group Last Call for: Message Digest for DNS Zones

"John Levine" <johnl@taugh.com> Mon, 06 January 2020 17:13 UTC

Return-Path: <johnl@iecc.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 2BABA120869 for <dnsop@ietfa.amsl.com>; Mon, 6 Jan 2020 09:13:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=HQRiZNzb; dkim=pass (1536-bit key) header.d=taugh.com header.b=A1beA8rU
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 Nc0yV2NTQbfO for <dnsop@ietfa.amsl.com>; Mon, 6 Jan 2020 09:13:29 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 04642120861 for <dnsop@ietf.org>; Mon, 6 Jan 2020 09:13:28 -0800 (PST)
Received: (qmail 94880 invoked from network); 6 Jan 2020 17:13:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1729e.5e136ab7.k2001; i=printer-iecc.com@submit.iecc.com; bh=5J2AfboCtttUTuHyZ1L5z04+vbr++8T3mzOIMCaB21k=; b=HQRiZNzbC++fVR8WU9XZGECHRJmADZ//RDoAAR/9GcLUUs2BZUWNpgHXH/XUH++K67Cr4lu0BodV6uJslEO4F7HiSXEbxkGKa9/5LgPfgICO5NF40vu8c7jO9UN7ZNxULHmqPs6JXA6XrkIqr0hsSO0T3ldxRI6TFwRCmTp+AzDQrePt1AoMBlfaR37SyGkUl4ewOyI7O8x8IGcisFhnhM5pQj9mOMPV9GVsRxhiJQMYZIRJStE+4HnvGcON9D6k
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1729e.5e136ab7.k2001; olt=printer-iecc.com@submit.iecc.com; bh=5J2AfboCtttUTuHyZ1L5z04+vbr++8T3mzOIMCaB21k=; b=A1beA8rUgXlG/3GRp5hy/2LSwAu0nS4TlHu2x2DrlZj3z0q2RoQy7s6Nt4RARjPEe61rtiwAsaBpteoxMfGcfv4szFIqEajfVY8eWU5bP7RSfMqnLlE5XuNXa6Uh79ZnX4fMgKbTHVQVh2hUQSlLTvT+C66bWUBHzhT8WLfuHm80nob+5+qK02rdkMC06upfzh2d9YBZwDQbZVm3NjwemrvkNaYXBz+w1Iofwgtv3alHQZHEyd9aUkH6cL56pgxP
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 06 Jan 2020 17:13:27 -0000
Received: by ary.qy (Postfix, from userid 501) id E0E1E120301E; Mon, 6 Jan 2020 12:13:26 -0500 (EST)
Date: Mon, 06 Jan 2020 12:13:26 -0500
Message-Id: <20200106171326.E0E1E120301E@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: msj@nthpermutation.com
In-Reply-To: <9952199f-9ea5-2d51-a5d2-6aaf805774a5@nthpermutation.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jOv0Eh63J1OhzzhA-mNIfClekhY>
Subject: Re: [DNSOP] Working Group Last Call for: Message Digest for DNS Zones
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: Mon, 06 Jan 2020 17:13:30 -0000

In article <9952199f-9ea5-2d51-a5d2-6aaf805774a5@nthpermutation.com> you write:
>If a computer can't figure out what to do with a failed validation 
>absent human interaction then you might as well say:
>
>"ZONEMD RRs may be safely ignored by all but the geekiest of DNS human 
>operators as there is no guidance on what to do if you see a zone that 
>appears to be incomplete due to ZONEMD RR validation as it might not 
>actually be incomplete"

Well, OK, here's a concrete example.  I download the COM zone every
day from Verisign, and also a separate file with an MD5 hash of the
main file.  Using RFC 2119 language, what do I do if the hash I get
doesn't match their hash?

For background, there are about 1600 people with passwords to download
the .com file, with a few dozen new passwords issued each month.  I
can tell you what I do with the zone file, but I have no idea what the
other 1599 do.  The downloads are by plain old FTP, since this was set
up a long time ago.

R's,
John