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

Paul Vixie <paul@redbarn.org> Thu, 26 July 2018 18:12 UTC

Return-Path: <paul@redbarn.org>
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 D2037131243 for <dnsop@ietfa.amsl.com>; Thu, 26 Jul 2018 11:12:03 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 sqOovvGUSAEL for <dnsop@ietfa.amsl.com>; Thu, 26 Jul 2018 11:12:02 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 956FF130E8A for <dnsop@ietf.org>; Thu, 26 Jul 2018 11:12:02 -0700 (PDT)
Received: from [172.17.85.2] (unknown [69.85.218.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 30C62892B9 for <dnsop@ietf.org>; Thu, 26 Jul 2018 18:12:00 +0000 (UTC)
Message-ID: <5B5A0EEE.4070401@redbarn.org>
Date: Thu, 26 Jul 2018 11:11:58 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
References: <4DCC5A51-1AB0-47B6-92B5-79B6894F9A9C@verisign.com> <6FFED142-0752-40FD-AF5C-7E9D6617DC03@isc.org> <056430ED-F87E-4170-B2D0-0EA3F57D9C60@verisign.com> <3B9A8C03-3095-46EE-A5FF-0EFC0D9FD3ED@isc.org> <872BB5B5-A685-4B65-BA22-C9B352A58BD9@vpnc.org> <5ECF7D77-045A-4F7F-9126-289F62F97FE5@isc.org>
In-Reply-To: <5ECF7D77-045A-4F7F-9126-289F62F97FE5@isc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/j7_jUlh53Eno-TSoVAu3TSLJSBQ>
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: Thu, 26 Jul 2018 18:12:05 -0000

what i mean by incremental is that if a zone remains online and is only 
modified by UPDATE requests, then the identity hash of zone content must 
be updated by each successful update. if it's necessary after each 
update of this kind to iterate through the entire zone to make a new 
zone hash, that's quadratic behaviour ("won't scale").

egads, i may have stumbled upon a use case for block chains.