Éric Vyncke has entered the following ballot position for draft-ietf-quic-multipath-19: 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-quic-multipath/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for the work done in this document. Special thanks to Antoine Fressancourt, the Internet directorate reviewer (at my request and on short notice), please consider this int-dir review: https://datatracker.ietf.org/doc/review-ietf-quic-multipath-19-intdir-telechat-fressancourt-2026-02-04/ In addition to Antoine's review, and in the light of https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/, I noted some SHOULD (e.g., sections 2.3, 2.5) that are without the required guidance per the IESG statement (in short, why not a MUST?). Let me also expression my surprise (knowing many of the authors) that section 5.2 uses IPv4 only example... On this topic, a dual-stack example would have been nice (especially, as Wi-Fi is often IPv4-only and 3GPP/cellular is often IPv6-enable or IPv6-only).
