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

"John Levine" <johnl@taugh.com> Tue, 31 July 2018 15:37 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 BBF6A130FE1 for <dnsop@ietfa.amsl.com>; Tue, 31 Jul 2018 08:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 N_frzIYohMxD for <dnsop@ietfa.amsl.com>; Tue, 31 Jul 2018 08:37:06 -0700 (PDT)
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 C9070130FDC for <dnsop@ietf.org>; Tue, 31 Jul 2018 08:37:04 -0700 (PDT)
Received: (qmail 46310 invoked from network); 31 Jul 2018 15:37:02 -0000
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 ESMTP via TCP6; 31 Jul 2018 15:37:02 -0000
Received: by ary.qy (Postfix, from userid 501) id 572AC200318A91; Tue, 31 Jul 2018 11:37:02 -0400 (EDT)
Date: Tue, 31 Jul 2018 11:37:02 -0400
Message-Id: <20180731153702.572AC200318A91@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: pch-dnsop-3@u-1.phicoh.com
In-Reply-To: <m1fkRCk-0000GTC@stereo.hq.phicoh.net>
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/vjha9XrSwQYBCcEWcrPYrLQbvXI>
Subject: Re: [DNSOP] distributing zones, was 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: Tue, 31 Jul 2018 15:37:15 -0000

In article <m1fkRCk-0000GTC@stereo.hq.phicoh.net> you write:
>I think there is a big difference between distributing the root zone and
>distributing a few 'local' zones.
>
>In the first case you need something that is massively scalable.

Fortunately, Cloudflare, Edgecast, Limelight, Azure, and Akamai are
only a phone call away.  That problem is pretty thoroughly solved.  Whether
you'd want to use them to distribute copies of root or TLD files is more of
a political than a technical question.

>In the second case, just create a tar file with a zone file and a hash, put
>it up on a web server and the problem is solved. Verifying the contents of a
>file is not exactly a new problem. 

It's not a new problem but it's not one we've addressed very well for
the DNS.  My DNS setup signs the zones and then uses rsync to
distribute the zone files, which I don't think is unusual.  I assume
that rsync doesn't scramble the zones, but it'd be enough of a pain to
create and distribute detached signatures that I don't.  If the signer
added ZONEMD at signing time which the servers could check before
using the zones, I think that would be useful.

R's,
John