IETF Logo Mail Archive

Re: [DNSOP] New Version Notification for draft-wessels-dns-zone-digest-01.txt

"John Levine" <johnl@taugh.com> Fri, 27 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 D9711130F8D for <dnsop@ietfa.amsl.com>; Fri, 27 Jul 2018 08:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 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_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=QPBRK8Ci; dkim=pass (1536-bit key) header.d=taugh.com header.b=HMmHj5Jy
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 PHZfdNhmnVNx for <dnsop@ietfa.amsl.com>; Fri, 27 Jul 2018 08:37:03 -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 AD1E5130F8E for <dnsop@ietf.org>; Fri, 27 Jul 2018 08:37:03 -0700 (PDT)
Received: (qmail 82972 invoked from network); 27 Jul 2018 15:37:02 -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=1441a.5b5b3c1e.k1807; bh=QcvoCA5Q/BCM0HYJkyxPaC388gIeq9U05/GZFDvjZEI=; b=QPBRK8CiPwhjAMwOZKn/Q5VaE6Ice0etWBjT5FW7uLoFfc0pFobeFlke+mZ1LnmKdJx9Yq0ZLOLacRofyi3I2JQZGHf70xpOGyZidtev8jESoHV/dkZepVk+wJ/hEcQNVY0BtacnLU12lBB9lhgdl8pRJaPPB9lHbW+HdPRB270pa85beMJlTrUtwEC2GlLtsZCmWE/p0M3mNK3glCDR6hceFs2LYfQKHkDTeRJLxSpiYdkY1IXxIEHODdSq0NIW
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=1441a.5b5b3c1e.k1807; bh=QcvoCA5Q/BCM0HYJkyxPaC388gIeq9U05/GZFDvjZEI=; b=HMmHj5JyVoNCEOdk3VZuZVSsADniTZpRCImHYIODScxx9pIxHicwWA2mh3isEhPKCBdxqzz1DnmjWnDVYMr4Y/rBYGkaHMg3jXiigl9Bi9bi8DVwu+p4xzOqpoq486KprR9ZW5CdShk9jqQ1vsJK8AqfNLJMSVVl/bo/I5vEE0ddKS6sannl4+Qu7ejMUJEOYT/ffJCXojLAbh9A5LWukoHJVQVzT9oUA87rznQH91az10uO9ePdq5Yf74fG+1Tp
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; 27 Jul 2018 15:37:02 -0000
Received: by ary.qy (Postfix, from userid 501) id 468352002E2083; Fri, 27 Jul 2018 11:37:02 -0400 (EDT)
Date: Fri, 27 Jul 2018 11:37:02 -0400
Message-Id: <20180727153702.468352002E2083@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: steve@shinkuro.com
In-Reply-To: <CABf5zvKnV_YodJSE3UcEXVfJaew0enCzDg_T7Ni=D8xS=s8zAg@mail.gmail.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/iKSxNt1A6XsRGrkRUx0WAp4RHAY>
Subject: Re: [DNSOP] New Version Notification for draft-wessels-dns-zone-digest-01.txt
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: Fri, 27 Jul 2018 15:37:05 -0000

In article <CABf5zvKnV_YodJSE3UcEXVfJaew0enCzDg_T7Ni=D8xS=s8zAg@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>Let me play Candide and stumble into this naively.  If we’re imagining very
>wide spread distribution of the root zone, say 100,000 or 1,000,000 local
>copies distributed twice a day, I would expect the evolution of a set of
>trusted sources and the use of some existing secure transport protocol to
>protect the transmission.  No new protocol or data types, just a way of
>finding the address of one more trusted sources.  And the existing set of
>root servers seems like a perfectly good set of trusted sources.

I was with you until the last sentence.  This is about as ideal an
application for bittorrent as one can imagine.  No new protocol, but
it would be nice to have some way to validate it.

I also observe that about half of the roots allow AXFR and half don't.
It might be interesting to ask why they made those respective choices.

R's,
Pangloss

v2.23.0 | Report a Bug | By Email