Skip to main content

Early Review of draft-ietf-alto-oam-yang-06
review-ietf-alto-oam-yang-06-tsvart-early-dawkins-2023-03-24-00

Request Review of draft-ietf-alto-oam-yang-06
Requested revision 06 (document currently at 17)
Type Early Review
Team Transport Area Review Team (tsvart)
Deadline 2023-03-26
Requested 2023-03-12
Requested by Mohamed Boucadair
Authors Jingxuan Zhang , Dhruv Dhody , Kai Gao , Roland Schott , Qiufang Ma
I-D last updated 2023-03-24
Completed reviews Dnsdir Last Call review of -12 by Scott Rose (diff)
Secdir Last Call review of -12 by Rich Salz (diff)
Genart Last Call review of -12 by Dan Romascanu (diff)
Dnsdir Telechat review of -14 by Scott Rose (diff)
Dnsdir Telechat review of -15 by Ted Lemon (diff)
Yangdoctors Early review of -06 by Andy Bierman (diff)
Opsdir Early review of -06 by Dan Romascanu (diff)
Tsvart Early review of -06 by Spencer Dawkins (diff)
Comments
The document is currently in the WGLC. We are interested in the directorate review to assess the design.

Thank you.
Assignment Reviewer Spencer Dawkins
State Completed
Request Early review on draft-ietf-alto-oam-yang by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/74xXjbXHd41VNYvbGJmQomuT8aI
Reviewed revision 06 (document currently at 17)
Result Ready
Completed 2023-03-24
review-ietf-alto-oam-yang-06-tsvart-early-dawkins-2023-03-24-00
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?