[dnssd] Warren Kumari's No Objection on draft-ietf-dnssd-update-lease-08: (with COMMENT)

Warren Kumari via Datatracker <noreply@ietf.org> Wed, 09 August 2023 21:19 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A8DC15106A; Wed, 9 Aug 2023 14:19:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnssd-update-lease@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, chris.box.ietf@gmail.com, chris.box.ietf@gmail.com, tale@dd.org, dnsdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 11.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <169161595873.42908.15475579126047868396@ietfa.amsl.com>
Date: Wed, 09 Aug 2023 14:19:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/FdlOufIAlvX0KoKCgjW_h_w78io>
Subject: [dnssd] Warren Kumari's No Objection on draft-ietf-dnssd-update-lease-08: (with COMMENT)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Aug 2023 21:19:18 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-dnssd-update-lease-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnssd-update-lease/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for writing this document. I'd also like to explicitly thank David
Lawrence for the comprehensive DNSDIR review
(https://datatracker.ietf.org/doc/review-ietf-dnssd-update-lease-07-dnsdir-lc-tale-2023-06-14/
), and for the followup during a natural disaster!

Like Paul Wouters I find the "the Update Lease interval should be at least 30
minutes, unless you really want it to be shorter" text to be suboptimal, but I
do understand what you are trying to say. How about something like: "By
default, the minimum Update Lease option SHOULD be no shorter than 1800 seconds
(30 minutes). If the requestor anticipates that the records being updated will
change sooner than 30 minutes it MAY choose a shorter interval. Requestors that
expect the updated records to be relatively static SHOULD request appropriately
longer leases." This says basically the same thing, but the "By default" clause
seems to make it less jarring. As this is a "No Objection" ballot, feel free to
ignore this suggestion...