[dnssd] Erik Kline's No Objection on draft-ietf-dnssd-srp-23: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Tue, 08 August 2023 22:32 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 D0A8AC151538; Tue, 8 Aug 2023 15:32:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnssd-srp@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, dschinazi.ietf@gmail.com, dschinazi.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 11.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <169153396584.54400.16885223429826572480@ietfa.amsl.com>
Date: Tue, 08 Aug 2023 15:32:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/vq8aTkB6e9V0WibTo7xaKs2NVWw>
Subject: [dnssd] Erik Kline's No Objection on draft-ietf-dnssd-srp-23: (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: Tue, 08 Aug 2023 22:32:45 -0000

Erik Kline has entered the following ballot position for
draft-ietf-dnssd-srp-23: 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-srp/



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


# Internet AD comments for draft-ietf-dnssd-srp-23
CC @ekline

* comment syntax:
  - https://github.com/mnot/ietf-comments/blob/main/format.md

* "Handling Ballot Positions":
  - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/

## Comments

### S3.1.1

* "discover the server to which they should send SRP updates"

  What about servers, plural?  Can there reasonably be more than one
  registrar, and if so does a client just send updates to all of them
  (and, further, how does it handle a partial failure issuing an update)?

### S6.1

* When checking an update for its on-link property, consider whether
  recommending RFC 5082 "The Generalized TTL Security Mechanism (GTSM)"
  might be appropriate.

### S10.6

* How should DNS-over-TLS work in this scenario?  Should the certificate
  claim to be valid for this address, or for default.service.arpa.,
  or something?