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

"John R Levine" <johnl@taugh.com> Mon, 30 July 2018 02:30 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 E8677130F76 for <dnsop@ietfa.amsl.com>; Sun, 29 Jul 2018 19:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 X-4HqeM0qfd1 for <dnsop@ietfa.amsl.com>; Sun, 29 Jul 2018 19:30:19 -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 07B1A130F73 for <dnsop@ietf.org>; Sun, 29 Jul 2018 19:30:18 -0700 (PDT)
Received: (qmail 65694 invoked from network); 30 Jul 2018 02:30:17 -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; 30 Jul 2018 02:30:17 -0000
Date: Sun, 29 Jul 2018 22:30:16 -0400
Message-ID: <alpine.OSX.2.21.1807292228330.53162@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
In-Reply-To: <CADyWQ+GoJeOQ4bGqZCQ6mETWCZZG2iEua9H=MdMvUaNMPuAOMQ@mail.gmail.com>
References: <20180730002348.GA41131@isc.org> <20180730012619.5AB982003100E2@ary.qy> <CADyWQ+GoJeOQ4bGqZCQ6mETWCZZG2iEua9H=MdMvUaNMPuAOMQ@mail.gmail.com>
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/r-zbdC_wgjqotKfZ1SsLl5xXpGw>
Subject: Re: [DNSOP] 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: Mon, 30 Jul 2018 02:30:21 -0000

Sorry, if that's what it sounded like.  I also think it's worth 
considering.  My point is that if it's worth trying, we should give it an 
rrtype and not screw around with overloaded TXT records.  It's not like 
we're in any immediate danger of running out of rrtypes.

R's,
John

> My email wasn't a statement that I don't think the work is relevant. It
> seems that interesting enough for the WG that there are
> two use cases: 1) the root zone; and 2) everything else.
>
> I had spent some time looking the draft over and realizing it was marked
> standards track, and I think it would be easier to adopt for the the
> specific use case if
> it wasn't standards track.
>
> And, why not combine zone-digest with 7706bis?
>
> Tim
>
> On Sun, Jul 29, 2018 at 9:26 PM, John Levine <johnl@taugh.com> wrote:
>
>> In article <20180730002348.GA41131@isc.org> you write:
>>> A good point. Technically, I don't think there's anything in ZONEMD that
>>> couldn't be implemented with TXT; using a dedicated rrtype for the purpose
>>> is mere convenience.
>>
>> Well, heck, we could do the whole DNS with TXT records.  But if it
>> were a TXT record, it'd either need a reserved prefix name or a
>> reserved string in the record to say what it is.  As Mark noted, that
>> makes calculating the hash a lot more fiddly.