IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Tue, 07 January 2020 02:36 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 57670120137 for <dnsop@ietfa.amsl.com>; Mon, 6 Jan 2020 18:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=qhBoDQlD; dkim=pass (1536-bit key) header.d=taugh.com header.b=hFKlzZf1
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 DNrCHngbs2TJ for <dnsop@ietfa.amsl.com>; Mon, 6 Jan 2020 18:36:32 -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 4DE63120123 for <dnsop@ietf.org>; Mon, 6 Jan 2020 18:36:32 -0800 (PST)
Received: (qmail 24300 invoked from network); 7 Jan 2020 02:36:31 -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=5ee9.5e13eeaf.k2001; i=printer-iecc.com@submit.iecc.com; bh=uqpyv08BdOMurBhCRdviJCJLgwMu2xybfWFkuRs25c8=; b=qhBoDQlDAoxf9Nj+IkSE3OdvhrZo5xHMHZs8H/aQJQUHKeCyxW8OHoYpw9nINc0RvW8WpKSnlMWQ1wbOa6V5NLLK9ivsy2mCf65kVr4aZFipmLeNQA9AA0Zny7YnFfBtIxR0dmaHT9L91OJia6FBVRZDWeKTr/lKrKCfAbzIcfd0CmDwko8VEYoYj8YpY57vkIs16lNoP7houGuMaiDjYuhltD/+1E7M0zihM1T/B8FNxf3MiJcFRNtKjuIsaD1X
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=5ee9.5e13eeaf.k2001; olt=printer-iecc.com@submit.iecc.com; bh=uqpyv08BdOMurBhCRdviJCJLgwMu2xybfWFkuRs25c8=; b=hFKlzZf1h6fUxaHUxex+zu43Km0O0t1icWZstMH5Ito33eFnu9oI+ScE5ppKlXxZ5cp7zeXP+jLd0ljKaMxgZtDUPXR3ZuT9OxPuUUGwCSE2dljkZ3nEmNdYo4hpsb1vEkJaf2ZOm1pz4qz/y9GZBBuXLN1rqC2jAtFwnGTExghi/Mr5HWqf/GJG5lub8qKzbFwO8AnW4SMDYsAJG9qhsC+zCNOuvs7xrD22l/dON5dzAmtoUcsx3GqSsW5F5teV
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; 07 Jan 2020 02:36:30 -0000
Received: by ary.qy (Postfix, from userid 501) id 628251208AAF; Mon, 6 Jan 2020 21:36:30 -0500 (EST)
Date: Mon, 06 Jan 2020 21:36:30 -0500
Message-Id: <20200107023630.628251208AAF@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: msj@nthpermutation.com
In-Reply-To: <7f298591-09b5-dd7c-0dab-afc60def874b@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/mS54SALqEAMLHlt6ws7k2dmudOk>
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: Tue, 07 Jan 2020 02:36:33 -0000

In article <7f298591-09b5-dd7c-0dab-afc60def874b@nthpermutation.com> you write:
>OK.� The point is not to self-approve, but to get a few other 
>non-authors to actually see if they can figure out what you're talking 
>about here and whether they're ever going to see this use case.��� E.g. 
>reach out to the consumer side for each of the 4 cases and see if you 
>can get some idea of a) would they actually use this, and b) what would 
>they do if validation failed or succeeded?

Hi again.  I actually do cases 1.3.1, 1.3.2, and 1.3.4 and would use
ZONEMD in all of them, particularly if someone else wrote the verification software.
(I never said I wasn't lazy.)

In my applications I don't think performance would be an issue.

R's,
John

v2.23.0 | Report a Bug | By Email