Fwd: New Version Notification for draft-dawkins-quic-multipath-questions-00.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 07 December 2020 05:26 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 109DD3A100D for <quic@ietfa.amsl.com>; Sun, 6 Dec 2020 21:26:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id UjqTjMFvhhFf for <quic@ietfa.amsl.com>; Sun, 6 Dec 2020 21:26:50 -0800 (PST)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31C863A0CEF for <quic@ietf.org>; Sun, 6 Dec 2020 21:26:50 -0800 (PST)
Received: by mail-yb1-xb33.google.com with SMTP id r127so11855838yba.10 for <quic@ietf.org>; Sun, 06 Dec 2020 21:26:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=xh9noP0oniCewM5GHDeilujUgVk+Jk9Si2xyvaIKXZY=; b=pw8EQoqgTHb4GLczRu2E8IlzLuEXxKW/yCeByNso/PjAvFCX5AUu414qada/DCrCen ukLG8QdyoaxCNw+5dRhu4LeB/NKSw6AUM/gHv4z+rNj5kUNfH+oBR97hotfM6et6cWDM hUHrCj1Fd3MJhKUj6exCzhsvULL3I7NYQt4e5CAr+vToXNn7Ah0Gu20hqEuMHf/Ck5TN NxwLRONNSdUQQO5to5avVlSy0xMCy9iGvLKMU6yd3mX5A2PBUiPvDdKCgqaK8FODFVN1 hGtO2NBQyASm2PZNducWckLFxTqkD9RPLZ8wrGvWDvyioWQwvG6PWjMIaJWup9t9Esvy Dw4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=xh9noP0oniCewM5GHDeilujUgVk+Jk9Si2xyvaIKXZY=; b=RRk2gLnKV1Y4aKK4cVLf2+RWhQbYTgkvHOBfN1LYlal0+z2w4Y1e+meL2yh0FHpQjQ eqpCMmEuTL0k0FuTXvnaIM15tGNtzohLE+QEdgFULDAME9EXIKPrWIprYNJ0KxCaTeRj S9VSdHYdtVOLM+O5/nbnhJS9lJ4PXHxp+Kezazf9YYNUbFL+LB6F9XATmNlyismJjckM VrKTtM8sjotAono/NCTKqXH8/2uA+//VB+c1QiEJvBLYQSKQIFQcMGFHvyermU7wqrbu V0l3OTx0d8uzVh/kKkUnX+ycUGr8OaRwBU+f4Z6nomNT2knzPVjuqjsopJhnJ5yT0If6 x5oQ==
X-Gm-Message-State: AOAM533pe6Ix3uMVXLRNUND+b6AhvIc04zNQ0hehfHvKyduFFXykFw05 oW4qg0tjJ5ScIcq1KrFbWrazfLa2KDkpqP5wwys5Qwvq/AJc8Q==
X-Google-Smtp-Source: ABdhPJxW+CurbLvfXGkNbg93cF4nZK8n3job0/LgHxkq+nHLOdpGh4yRfDcUHmZIOInG18c/VjEXotNReS5po7zDQqw=
X-Received: by 2002:a25:884:: with SMTP id 126mr20213121ybi.154.1607318808972; Sun, 06 Dec 2020 21:26:48 -0800 (PST)
MIME-Version: 1.0
References: <160731832334.29236.7841084320182421518@ietfa.amsl.com>
In-Reply-To: <160731832334.29236.7841084320182421518@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 06 Dec 2020 23:26:23 -0600
Message-ID: <CAKKJt-fHi_3HLvK4u2JbnmW_snT3qpVuiavKru5wM2hygNYJGQ@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-dawkins-quic-multipath-questions-00.txt
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6514705b5d9122f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vzH2UNbUdzy2HbVPuSsZoxq9WQY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2020 05:26:52 -0000

Dear QUIC working group,

We've exchanged a lot of e-mail about what support for multiple paths in
QUIC might look like on the mailing list, and talked about this at the
October virtual interim meeting and at the QUIC session at IETF 109, and it
seemed good to me, to try to summarize the discussions we've had so far.

Because this topic is of interest outside the IETF, I thought it better to
put the summary in an Internet Draft, than somewhere in Github issues or
Slack, or on the mailing list.

I also want to apologize in advance if I've misstated things - if so,
please let me know. I'd point out this text in the draft:

   Please note well that this document reflects the author's current
   understanding of working group discussions.  It is likely that there
   are more questions than currently included in the document, and it is
   even more likely that some of the suggested answers are incomplete or
   (unlike the people in Section 1.1) completely wrong.  Contributions
   that add or improve questions and answers are welcomed, as described
   in Section 1.4.

As always, Do The Right Thing.



---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, Dec 6, 2020 at 11:18 PM
Subject: New Version Notification for
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>

A new version of I-D, draft-dawkins-quic-multipath-questions-00.txt
has been successfully submitted by Spencer Dawkins and posted to the
IETF repository.

Name:           draft-dawkins-quic-multipath-questions
Revision:       00
Title:          Questions for Multiple Paths In QUIC
Document date:  2020-12-06
Group:          Individual Submission
Pages:          13

   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, and so had different
   assumptions about how applications might use QUIC over multiple

   This document is intended to capture questions that have come up in
   discussions, with some suggested answers, 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