Re: [DNSOP] [Ext] Re: Comments on draft-wessels-dns-zone-digest-02
"John R Levine" <johnl@taugh.com> Mon, 13 August 2018 17:35 UTC
Return-Path: <johnl@taugh.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 07132130FAC for <dnsop@ietfa.amsl.com>; Mon, 13 Aug 2018 10:35:40 -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 gPJYPZwdwkV4 for <dnsop@ietfa.amsl.com>; Mon, 13 Aug 2018 10:35:38 -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 76C3B130E02 for <dnsop@ietf.org>; Mon, 13 Aug 2018 10:35:38 -0700 (PDT)
Received: (qmail 98925 invoked from network); 13 Aug 2018 17:35:36 -0000
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 13 Aug 2018 17:35:36 -0000
Date: Mon, 13 Aug 2018 13:35:36 -0400
Message-ID: <alpine.OSX.2.21.1808131330440.95713@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Edward Lewis <edward.lewis@icann.org>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <55C39266-40BA-4266-B631-28050CCE8242@icann.org>
References: <7223EEB4-57A4-4C54-8C62-631B5FBEE0A5@icann.org> <20180813154946.A0D5020036E99E@ary.qy> <55C39266-40BA-4266-B631-28050CCE8242@icann.org>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qJf0dvc_PjeHF3WHYV17rxPEbXE>
Subject: Re: [DNSOP] [Ext] Re: Comments on draft-wessels-dns-zone-digest-02
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: Mon, 13 Aug 2018 17:35:40 -0000
>> but the obvious consumer is a DNS server. > > Maybe, maybe not. I've seen DNS used in turnkey ways. Nevertheless, > given the complexity of DNSSEC validation, a wise implementer should > re-use the parts of a DNS server for this. If the question is whether one might use this to create a kludge and shoot yourself in the foot, well, sure, but in the DNS world that goes without saying. On the other hand, I would think that in a reasonbly well written DNSSEC implementation it wouldn't be too hard to reuse the code that checks the signature on a record received as a response to a query to check the signature on the ZONEMD. >> it'd be nice to be able to check that the zone is correct and get notified of failure > > There are many existing tools for such a set up. For one, use a VPN or > in-band channel security, and/or make sure the zone file received > matches the zone file sent. Hey, I have a great idea. We could make sure that the zone file received matches the zone file sent by including a hash of the zonee in a record in the zone. Whaddaya think? R's, John PS: > In essence, what would do DNSSEC validation for the ZONEMD and not for data sets within the zone? The glue. I realize you could refetch all the glue and check it but that's a lot more work.
- [DNSOP] Comments on draft-wessels-dns-zone-digest… Edward Lewis
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Viktor Dukhovni
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Edward Lewis
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Hoffman
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Wessels, Duane
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Wessels, Duane
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… John Levine
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Joe Abley
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… John Levine
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Edward Lewis
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… John Levine
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Paul Wouters
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Edward Lewis
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… John R Levine
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Edward Lewis
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Brian Dickson
- Re: [DNSOP] [Ext] Re: Comments on draft-wessels-d… Edward Lewis
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Bob Harold
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Shumon Huque
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Brian Dickson
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… Paul Wouters
- Re: [DNSOP] Comments on draft-wessels-dns-zone-di… John Levine