Re: [DNSOP] [Ext] Working Group Last Call for draft-ietf-dnsop-nsec-ttl

Matthijs Mekking <matthijs@pletterpet.nl> Thu, 04 February 2021 07:54 UTC

Return-Path: <matthijs@pletterpet.nl>
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 219893A13C3 for <dnsop@ietfa.amsl.com>; Wed, 3 Feb 2021 23:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=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 oIVzZbNNUnuw for <dnsop@ietfa.amsl.com>; Wed, 3 Feb 2021 23:54:53 -0800 (PST)
Received: from lb3-smtp-cloud9.xs4all.net (lb3-smtp-cloud9.xs4all.net [194.109.24.30]) (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 D72DE3A13BF for <dnsop@ietf.org>; Wed, 3 Feb 2021 23:54:52 -0800 (PST)
Received: from cust-69fe625f ([IPv6:fc0c:c103:c4a6:cf3c:d2f9:56fe:3f93:cb0b]) by smtp-cloud9.xs4all.net with ESMTPSA id 7ZTUl34K9E1Ic7ZTWlLwuE; Thu, 04 Feb 2021 08:54:50 +0100
To: dnsop@ietf.org
References: <CADyWQ+En0_=LzynpgodOyPan0WD5HdtdqVdU6zw39-g_SCNL6A@mail.gmail.com> <edf948c2-f093-9850-805a-5ac05b27a2bd@nthpermutation.com> <7A8AD079-63AE-4AEA-830D-5971A7441AA7@icann.org>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <fc4c879d-a5c7-711a-8562-cd7b43bc8a50@pletterpet.nl>
Date: Thu, 04 Feb 2021 08:54:48 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <7A8AD079-63AE-4AEA-830D-5971A7441AA7@icann.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4xfP5D135Ufx3XT0RWAFwicEDdk5pPhj6Q16RTq/ANJOfcSZkmY/mVbtMqX3qzh/OMl98RaDgdygDU+aRUV1exQsRMYJObJNMLXAwoqpb0/yPXFfWbGOIx oeUdotlsCMOsgLJQZAViRArnbZu3InhMw7bR1JeRVcFs2mnUm7bswtJsxaz6EUJUZ/VvvlRexyouEOswqvGi6unNHRFrOwYqDlxOAjQqk7z/1tJYEncSlF09 3d3VLrf2CYEUTMojdm8pUv/FVnMb7uwGY1WmaLTsd0QvFey7yLt2AqXFqavrwm8E
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2h6pV6yE4BvFILzjK5kZsFhPgF4>
Subject: Re: [DNSOP] [Ext] Working Group Last Call for draft-ietf-dnsop-nsec-ttl
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 07:54:55 -0000


On 03-02-2021 20:31, Paul Hoffman wrote:
>> For each of these, I'd recommend specifying what a client does in each of the cases, rather than weasel wording the SHOULD with respect to the zone contents to turn this into an implementable protocol.
> 
> Here, I agree that the draft is unclear. It should say explicitly "resolvers keep doing $z, there is no change here". Also, for the text about authoritative servers, I agree that changing the SHOULDs from the current standards to MUSTs.

Changing this to MUST means that every time a zone changes its SOA TTL 
or SOA MINIMUM value, the whole chain of NSEC/NSEC3 records need to be 
updated accordingly immediately. That may be undesirable for a large zone.

BIND for example would make such a change incrementally, so there may be 
a period of time where the NSEC/NSEC3 records still have the TTL of the 
previous SOA TTL/MINIMUM value. With a SHOULD keyword we can keep this 
behavior. With a MUST less so, I think.

So I am against changing these SHOULDs to MUSTs.

Best regards,

Matthijs