IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Mon, 30 July 2018 18:15 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 64E701311C3 for <dnsop@ietfa.amsl.com>; Mon, 30 Jul 2018 11:15:13 -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 1aVAQGXqfpmz for <dnsop@ietfa.amsl.com>; Mon, 30 Jul 2018 11:15:11 -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 3965A131172 for <dnsop@ietf.org>; Mon, 30 Jul 2018 11:05:21 -0700 (PDT)
Received: (qmail 16266 invoked from network); 30 Jul 2018 18:05:19 -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 18:05:19 -0000
Date: Mon, 30 Jul 2018 14:05:19 -0400
Message-ID: <alpine.OSX.2.21.1807301403560.56898@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Evan Hunt <each@isc.org>
Cc: dnsop@ietf.org
In-Reply-To: <20180730172104.GA46824@isc.org>
References: <20180730002348.GA41131@isc.org> <20180730012619.5AB982003100E2@ary.qy> <20180730172104.GA46824@isc.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/mfnHDZ-bC2Q7KXv-KCMLbqq7LDk>
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 18:15:22 -0000

> No, not really - you couldn't do NSEC3 with TXT, for example. Or DNAME,
> or ANY, or lots of things.
>
> I'm just using "could I implement this with TXT?" as a proxy for whether
> it's a major change to the way the DNS works, or just a thing we can move
> forward on with expert review.

Ah.  I gather the question is whether the record has semantics beyond just 
serving it, like DNAME or the proposed BULK, or it's just another record 
with no special handling.  I think we agree this is clearly the latter, 
since any specialness is outside the DNS query/response protocol.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email