I just submitted a write-up based on the presentations given at the October QUIC virtual interim meeting on multicast, to try to identify commonalities between what various folks and groups of folks are thinking.
I hope this will be useful in understanding where the working group should go with the multipath extension mentioned in the charter. It's not likely that I got everything complete, or even completely right, and the draft includes a pointer to a Github repo where issues and PRs are welcomed. I'm sure I'll update it at least once, but I won't update it once today. (Enjoy your work on your own internet drafts!). Best, Spencer ---------- Forwarded message --------- From: <[email protected]> Date: Mon, Nov 2, 2020 at 4:15 PM Subject: New Version Notification for draft-dawkins-quic-what-to-do-with-multipath-00.txt To: Spencer Dawkins <[email protected]> A new version of I-D, draft-dawkins-quic-what-to-do-with-multipath-00.txt has been successfully submitted by Spencer Dawkins and posted to the IETF repository. Name: draft-dawkins-quic-what-to-do-with-multipath Revision: 00 Title: What To Do With Multiple Active Paths in QUIC Document date: 2020-11-01 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/archive/id/draft-dawkins-quic-what-to-do-with-multipath-00.txt Status: https://datatracker.ietf.org/doc/draft-dawkins-quic-what-to-do-with-multipath/ Htmlized: https://datatracker.ietf.org/doc/html/draft-dawkins-quic-what-to-do-with-multipath Htmlized: https://tools.ietf.org/html/draft-dawkins-quic-what-to-do-with-multipath-00 Abstract: The IETF QUIC working group has been chartered to produce extensions that would "enable ... multipath capabilities" since the working group was formed in 2016, but because multipath was an extension, work on multipath, and the other extensions named in the charter, waited while work proceeded on the core QUIC protocol specifications. After the QUIC working group chairs requested publication for the core QUIC protocol specifications, they scheduled a virtual interim meeting to understand the use cases that various groups inside and outside the IETF were envisioning for multipath with QUIC. As part of that discussion, it became obvious that people had a variety of ideas about how multiple paths would be used, because they weren't looking at the same use cases. This document is intended to capture that variety of ideas, to inform further discussion in the working group. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
