Markdown Version | Recording 1 | Recording 2
Session Date/Time: 23 Jul 2024 00:30
tsvwg
Summary
This TSVWG meeting covered document status updates, discussion of UDP options, and careful resume. The group discussed the need for reviews and contributions to existing drafts. Key decisions included potentially dropping the "user ports for experiments" draft and proceeding with a working group last call for "Convergence of Congestion Control from Retail state" (Careful Resume) before the next IETF meeting.
Key Discussion Points
- Document Status: Review of RFC queue, IESG status, and documents needing revision before publication request (NQB, UDP Options, DPLPMTUD).
- Review Importance: Emphasis on the need for document reviews and feedback, even small suggestions are valuable.
- User Ports for Experiments: Lack of recent updates or discussion. Question of whether to unadopt this work.
- UDP Options: Review of working group last call comments documented in GitHub, covering issues like disambiguating surplus areas, definition of "unsafe," terminology fixes, and clarification on per-fragment options. Discussion about acceptability of passing datagrams when additional payload checksum and authentication fails.
- Careful Resume: Hackathon testing with multiple clients against a server implementation using Cloudflare's Kiche. Successful initial interop test. Discussion on observed variations in client behavior and plans for more rigorous performance testing in Dublin.
- Careful Resume Specification Updates: Draft 08 (CDDL updates, removing unnecessary requirements), Draft 09 (restructuring and cleaning up the document), Draft 10 (BBR support).
- Careful Resume Open Issues: Issue 22 (minimum number of RTT samples) - proposal to close with no action but after discussion it was decided to find a recommendation for a minimum number. Issue 13 (limited sending example) - awaiting feedback on the need for this addition.
- Careful Resume Minimum RTT samples: Discussion on suggested or required number of RTT samples to confirm path characteristics.
- Careful Resume Rationale and Requirements: Add a section stating goals.
- Careful Resume Implementation Experience: Existing implementations in Cloudflare's Kiche and Pico Quake. Testing plans.
Decisions and Action Items
- User Ports for Experiments: Chairs to liaise with the editor and solicit working group feedback to determine whether to unadopt the draft.
- UDP Options: Editor to prepare a new revision addressing the GitHub issues. Chairs will consult with the AD to determine if a new working group last call is needed.
- UDP Options: Zahid was to consider adding editors to this document.
- Careful Resume (Issue 22): Martin to propose a number of RTT samples for issue 22 in the Github
- Careful Resume Minimum RTT: To create a PR with a recommendation for a minimum number of RTT samples to confirm path characteristics.
- Careful Resume Rationale and Requirements: Editors to add a section re-stating requirements and goals.
- Careful Resume Working Group Last Call: Prepare a new version for working group last call before next meeting
Next Steps
- Continue discussions on the mailing list, particularly regarding the User Ports for Experiments draft and the remaining issues for Careful Resume.
- Editors to update drafts based on the meeting discussions.
- Next meeting to cover NQB, a forest deployment experience update, SCTP, and the new requirements document for network collaboration signaling and L4S interop activities.
Session Date/Time: 26 Jul 2024 16:30
tsvwg Meeting Minutes
Summary
The tsvwg meeting covered several active drafts, including NQB, L4S ops, SCTP authentication, DTLS for SCTP, and a new draft on network collaboration signaling. Discussions focused on resolving open issues, clarifying requirements, and determining the direction of future work.
Key Discussion Points
- NQB Draft: Discussion centered on traffic protection (mandatory vs. recommended implementation), applicability, and clarification of requirements. Issue 48, regarding traffic protection, was extensively discussed with arguments for and against making it mandatory.
- L4S Ops Draft: Decision on whether to keep the draft open as a living document or close it at the Dublin meeting was discussed. The lack of recent updates prompted the question.
- SCTP Authentication Draft: Integration of proposals for authenticated chunks and replay protection, along with privacy considerations, were discussed.
- DTLS for SCTP Draft: Updates on the detailed chunk and handshake drafts were presented, along with open issues, particularly whether handshake messages should be encrypted.
- Network Collaboration Signaling Draft: A new draft outlining requirements for host-to-network and server-to-network signaling was presented. Extensive discussion on its scope, existing solutions in other standards bodies (e.g., 3GPP), and its relationship to potential solutions.
Decisions and Action Items
- NQB Draft:
- Editor to propose a resolution to Issue 48 (traffic protection) that adheres to the working group consensus, separating out the Wi-Fi case.
- Editor to clarify options for managing traffic, rewrite sections, and work with other people to resolve this issue.
- Deliver Draft 25 in one or two weeks.
- L4S Ops Draft:
- Defer decision on whether to close the draft until the Dublin meeting. Chairs will bring up the topic again.
- SCTP Authentication Draft:
- Discussion of proposals 1 and 2 to continue on the mailing list.
- Update security considerations with privacy considerations (lack of encryption).
- Network Collaboration Signaling Draft:
- Authors to provide an analysis of how the requirements are covered by existing mechanisms in other standards bodies (e.g., 3GPP) and why those may be insufficient.
- Authors to consider the operational feedback and revise the document.
- Working group to determine the scope of this work and the path forward.
Next Steps
- Authors of various drafts to incorporate feedback and address open issues.
- Continue discussions on the mailing lists.
- Decision on L4S ops draft at the Dublin meeting.