[alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

[Zaheduzzaman Sarker via Datatracker <[e-mail]>]

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-alto-oam-yang-15: Discuss

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-alto-oam-yang/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for working on this specification.

It appears that this specification does not support the
https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/, as it only
defines TCP server grouping but the new transport also compatible with HTTP/3
which would be running over QUIC. I would like to discuss why is that so and if
there explicit reasoning behind excluding HTTP/3 why is that described? It is
no longer the case that QUIC and HTTP/3 is work in progress.

Also supporting Roman's discuss. It is very important that we record under what
circumstances ALTO servers are configured to use HTTP instead of HTTPS.