[Ohai] Éric Vyncke's No Objection on draft-ietf-ohai-svcb-config-06: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 02 October 2023 08:59 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ohai@ietf.org
Delivered-To: ohai@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C442C1519BF; Mon, 2 Oct 2023 01:59:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ohai-svcb-config@ietf.org, ohai-chairs@ietf.org, ohai@ietf.org, shivankaulsahib@gmail.com, shivankaulsahib@gmail.com, dns@fl1ger.de
X-Test-IDTracker: no
X-IETF-IDTracker: 11.12.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <169623718728.57709.13618162864498393044@ietfa.amsl.com>
Date: Mon, 02 Oct 2023 01:59:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/-X1F9d648htExuP3kcxMSIalZT4>
Subject: [Ohai] Éric Vyncke's No Objection on draft-ietf-ohai-svcb-config-06: (with COMMENT)
X-BeenThere: ohai@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Oblivious HTTP Application Intermediation <ohai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohai>, <mailto:ohai-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohai/>
List-Post: <mailto:ohai@ietf.org>
List-Help: <mailto:ohai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohai>, <mailto:ohai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2023 08:59:47 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-ohai-svcb-config-06: 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-ohai-svcb-config/



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


# Éric Vyncke, INT AD, comments for draft-ietf-ohai-svcb-config-06

Thank you for the work put into this document.

Please find below one blocking DISCUSS points (easy to address), some
non-blocking COMMENT points (but replies would be appreciated even if only for
my own education), and some nits.

Special thanks to Shivan Kaul Sahib for the shepherd's detailed write-up
including the WG consensus ***and*** the justification of the intended status.

Please note that Ralf Weber is the DNS directorate reviewer and you may want to
consider this dns-dir review as well when it will be available (no need to wait
for it though):
https://datatracker.ietf.org/doc/draft-ietf-ohai-svcb-config/reviewrequest/18156/
(and I have read Tommy's reply to Ralf's Last Call review)

I hope that this review helps to improve the document,

Regards,

-éric

# DISCUSS

As noted in https://www.ietf.org/blog/handling-iesg-ballot-positions/, a
DISCUSS ballot is a request to have a discussion on the following topics:

##

# COMMENTS

## Section 1

Should DNR also be mentioned (if applicable) ? Esp as this I-D contains section
4.2.2.

## Section 3

I would expect a direct object in ` it "upgrades"`, i.e., what is upgraded ?

## Section 4.2.2

Suggest to also add examples as in the DDR/HTTP sections above.

## Section 5

I hesitated to raise a DISCUSS level on this one... Should normative language
be used in `By default, the gateway for a target is defined as a well-known
resource ([WELLKNOWN]) on the target, "/.well-known/ohttp-gateway".` ? I.e.,
'by default' is rather vague.