[Tsv-art] Tsvart early review of draft-ietf-alto-oam-yang-06

Spencer Dawkins via Datatracker <noreply@ietf.org> Fri, 24 March 2023 08:15 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins via Datatracker <noreply@ietf.org>
To: tsv-art@ietf.org
Cc: alto@ietf.org, draft-ietf-alto-oam-yang.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167964571435.34095.11414687726185443311@ietfa.amsl.com>
Reply-To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Date: Fri, 24 Mar 2023 01:15:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/74xXjbXHd41VNYvbGJmQomuT8aI>
Subject: [Tsv-art] Tsvart early review of draft-ietf-alto-oam-yang-06

Reviewer: Spencer Dawkins
Review result: Ready

I didn't have any questions on the document as written, and it's worth adding
that I'm not a YANG person and was still able to follow the document and the
process it describes.

I did have one question, which might be out of scope for this document.

I didn't see a mention of APLNs for TLS, and, perhaps more importantly, I don't
see a mention of ALPNs, QUIC, or UDP parameters for HTTP/3 over QUIC. It looks
like this document is expecting to use NAPTR records, but I thought web servers
used RR records to provide ALPN names. My apologies if my question isn't
helpful, but is it expected that this document would also cover configuration
of ALTO servers listening over HTTP/3?

[Tsv-art] Tsvart early review of draft-ietf-alto-… Spencer Dawkins via Datatracker
Re: [Tsv-art] Tsvart early review of draft-ietf-a… Jensen Zhang