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

Joe Abley <jabley@hopcount.ca> Sun, 29 July 2018 21:42 UTC

Return-Path: <jabley@hopcount.ca>
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 7EEA0130F05 for <dnsop@ietfa.amsl.com>; Sun, 29 Jul 2018 14:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 52zvxUrMbT3y for <dnsop@ietfa.amsl.com>; Sun, 29 Jul 2018 14:42:09 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8380130E40 for <dnsop@ietf.org>; Sun, 29 Jul 2018 14:42:09 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id z8-v6so6108505pgu.8 for <dnsop@ietf.org>; Sun, 29 Jul 2018 14:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7d0IoTvq3XNwOB0ZAhNToUS6uHqa/uuJyTWiP6pYZOM=; b=BEWQjH15QGS7oZS1Cxe+5fi0HafmB2Zem5qLNkJzqYMY7bZqG8SbygLJj97hPXy0RB h3mIp54XZNhZAwm1/mhXSacGRdKdkbryRp3BeSk4SiqSEg0ovXtU7NINtgIEiKZZMQwn gohDKmm+29At4EbD//eRu8j4NqS9QNLtSN0Q8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7d0IoTvq3XNwOB0ZAhNToUS6uHqa/uuJyTWiP6pYZOM=; b=OONVykTCk/RFUU0sw72exFVYsrhfcRC+2PmpyA64LR01YnuIdB0HYJR4ZnbM4uvbsf SibCzLzLZKlIPCe87rXoyjCNX3bta8LHWUqWcXaVn8NhQzg7bR+akA+1dtCR2nnX6QUg OxRdBS6sUWgZ0Nhx+LKubrwWtAzwlfCGFp6qm6CaI+vFjjGPYqTGsEImHkJVmdRCRkRN /oT5XdM/FKyQjxIWA+kmi1kD9Ycs2KslKizpHzcOLI+FKwWOPmKiq3apRmEK8spEAqh9 1keWU0bwGcHuU1sDnWhv1VX+AROpvyCsjRZS/b1k2An8vYpU2VVyOnksI5X+W/VNdnmm /xaQ==
X-Gm-Message-State: AOUpUlFClx5MvBTp9KTBbVcbtu9PQyWcDzxpzS+vMZym7bwNz4uOGXwv UKRb6/gI8sEp3nhucelVra4fvA==
X-Google-Smtp-Source: AAOMgpd+lZYGR262knggGZuG0FSQ2jwda3/1zVUHN8qoBLI3PJiKkRcLMhEZbLI7l2e8/nEscft/Kw==
X-Received: by 2002:aa7:84c2:: with SMTP id x2-v6mr15198261pfn.220.1532900529282; Sun, 29 Jul 2018 14:42:09 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:101:3:6d81:e02f:e86f:3b17? ([2607:f2c0:101:3:6d81:e02f:e86f:3b17]) by smtp.gmail.com with ESMTPSA id k79-v6sm3940476pfa.22.2018.07.29.14.42.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 14:42:07 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (15G77)
In-Reply-To: <87sh41u4mj.fsf@mid.deneb.enyo.de>
Date: Sun, 29 Jul 2018 17:42:04 -0400
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <409CDF7B-DED9-4671-9BE6-8398E4364B98@hopcount.ca>
References: <CADyWQ+HizOJsE9EZ=VEvrbnnyPwaG_yBRg7fP5VvUNTdnidXZA@mail.gmail.com> <87sh41u4mj.fsf@mid.deneb.enyo.de>
To: Florian Weimer <fw@deneb.enyo.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8TqwSpCHOrO71l7MwOKwhpSsL1o>
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: Sun, 29 Jul 2018 21:42:11 -0000

On Jul 29, 2018, at 17:13, Florian Weimer <fw@deneb.enyo.de> wrote:

> * Tim Wicinski:
> 
>> For the ZONEMD RR Type, where in the registry do the authors think it
>> should go?  While some of that falls on the Expert Review process,  I think
>> the document authors should capture their rationale in the document.  If
>> the proposed RR Type is greater than 256 (which I think it does), it does
>> not appear to require a Standards Track document, just Expert Review.
> 
> There is some talk in the draft about blocking ZONEMD queries through
> recursive resolvers, which wiuld put it into the meta RR space, I
> think.
> 
> (But I disagree that there wouldn't be a loss of functionality—if the
> ZONEMD record contained the size of the zone, clients might want to
> query it, verify its signature, and only download the specified number
> of bytes.)

I agree with that use-case. 

I also don't see a compelling reason to complicate the DNS protocol by specifying that QTYPE=ZONEMD needs special handling. That's camel territory as I think Jinmei expresed concern over the other day; better just to document the RRType and let the DNS be the DNS.

I also agree with Tim's observation the other day that if this is just a new RRType, then expert review is all that is procedurally required and it'd be a generous extension of what is required to document the implementation and use of the new RRType in the RFC series.

Such a document would only need to be an informational and could plausibly be independent stream or AD-sponsored if it doesn't fit the charter or is otherwise unpalatable to the working group.


Joe