Last Call Review of draft-ietf-alto-new-transport-15
review-ietf-alto-new-transport-15-genart-lc-dunbar-2023-10-12-00

Request Review of draft-ietf-alto-new-transport
Requested revision No specific revision (document currently at 22)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-10-06
Requested 2023-09-22
Authors Kai Gao , Roland Schott , Y. Richard Yang , Lauren Delwiche , Lachlan Keller
I-D last updated 2023-10-12
Completed reviews Httpdir Last Call review of -14 by Martin Thomson (diff)
Secdir Last Call review of -15 by Donald E. Eastlake 3rd (diff)
Genart Last Call review of -15 by Linda Dunbar (diff)
Iotdir Telechat review of -17 by Wesley Eddy (diff)
Intdir Telechat review of -16 by Bob Halley (diff)
Artart Early review of -01 by Spencer Dawkins (diff)
Secdir Early review of -07 by Donald E. Eastlake 3rd (diff)
Opsdir Early review of -07 by Sheng Jiang (diff)
Rtgdir Early review of -07 by Russ White (diff)
Tsvart Early review of -07 by Dr. Bernard D. Aboba (diff)
Artart Early review of -07 by Spencer Dawkins (diff)
Httpdir Early review of -07 by Martin Thomson (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-alto-new-transport by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/3q-ds8awHTaNIK4FRv1xTI_eqs8
Reviewed revision 15 (document currently at 22)
Result Ready w/issues
Completed 2023-10-12
review-ietf-alto-new-transport-15-genart-lc-dunbar-2023-10-12-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-alto-new-transport-15
Reviewer: Linda Dunbar
Review Date: 2023-10-12
IETF LC End Date: 2023-10-06
IESG Telechat date: Not scheduled for a telechat

Summary:
 Sorry for the late review. The document introduces a method for clients to
 make concurrent pulls of the incremental updates potentially through different
 HTTP connections.

Major issues:
Section 8.1 states:
"it introduces additional complexities when the ALTO server is being load
balanced",

Q: does it mean there is only one single ALTO server load balancing among
multiple pull requests from the same client? or Load balancing among pull
requests from multiple clients?

I would assume different clients request different incremental updates. Does it
mean that the ALTO server has to manage states for all the clients?

Minor issues:

Nits/editorial comments:

Thank you,

Linda