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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 18 January 2021 00:06 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 A503A3A0A1C for <quic@ietfa.amsl.com>; Sun, 17 Jan 2021 16:06:04 -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 GywXiqMlT9pY for <quic@ietfa.amsl.com>; Sun, 17 Jan 2021 16:06:02 -0800 (PST)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 BE7213A0A1B for <quic@ietf.org>; Sun, 17 Jan 2021 16:06:02 -0800 (PST)
Received: by mail-yb1-xb29.google.com with SMTP id y128so11043602ybf.10 for <quic@ietf.org>; Sun, 17 Jan 2021 16:06:02 -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=EAdzdmlhr9Pepjo98Yh/zOsEUD0ckAH1StDAF2hCoM4=; b=DxfD050Q34iwHLRRJdmcamjWSClRSXXDXO35iMYAv9fPXanaKSUr77V8dqj3tbzTQQ yeHcGg788hRAE1F74AnUntrRX/Hy+QkQAhejuMGGcfzwr0JwfVMlVZLpd1/O7GJUEYEt 2oBcpGlc+68ZEvzyPflPVyFtHBEuei+wzExfaPGyy5vlY9hBTXLR2k2B5h+3Yu8RULvU uFsW+kIhvyzIsPlrTHVvLyO+JwF/NHnJ4nvUJ39frNtnBEHJrXxNSNwJ01RtFttGupMl MMptkYHpwhohC3Cz0Da47IcyOhw+sNSC5DHwSsXOSoDD2lVQw+iV2L1V5sEbiBgRcbFX GftQ==
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=EAdzdmlhr9Pepjo98Yh/zOsEUD0ckAH1StDAF2hCoM4=; b=A+dFkWm1/6XwnYfEFV3YtUEAzSaFFhsYzYO98tMrpkD/6rRha8V/MUAvDIp8V4oOFj 7VRYuERkIFYsO7nvaNp2//RCKQhzSW6wCitSFxorozfFCDj/fAuxudJq62TlYipeaOOn fVvXK2XNc4h178/Eajxyld2C948n6DUvPzVfM5oYPNHAdeViNKJJymWDLBXznGrXbUcS htr6AndviDDKSobnhisn4VZTV8C89Of1jqQo/gl1pKgVnUIvGggTvtIpKyzBNIB3dX89 G+UlZ5cTrRTai7xFxXPbmZqv1lUJ+Q6Fo7SY8CHrj1050Pwr/O9D2cXCq6e34YZ8k61f AMLw==
X-Gm-Message-State: AOAM531kHXibsJIkEMutfVLWxfIMqP44/TaQCFdFEGt9J3T77HWGNZBi bZw3ax5LgZGFkIWRrFTImQY7/D6bCGXp4VY6NEt7e+BqT/Y=
X-Google-Smtp-Source: ABdhPJz/WztAh06itYg1GpYxTiGlhulyuks3IHro8/2l8cJNQ4H5664btzR4nTyXzTMZv/YqDnjwlZMIrTimW6z61aI=
X-Received: by 2002:a25:504c:: with SMTP id e73mr36292067ybb.84.1610928361585; Sun, 17 Jan 2021 16:06:01 -0800 (PST)
MIME-Version: 1.0
References: <161092793810.2411.16245648913613836765@ietfa.amsl.com>
In-Reply-To: <161092793810.2411.16245648913613836765@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 17 Jan 2021 18:05:35 -0600
Message-ID: <CAKKJt-ec-8LFUDYuO=pauTGncmsF5UADRyyLrAGV3TD9EiiDMA@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-dawkins-quic-multipath-questions-01.txt
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c03fc205b9217c72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TBbPY2TbpGQ8EJOB3o8vT3ZZHUM>
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, 18 Jan 2021 00:06:05 -0000

Just to let people know, I've been through the open issues in
and done some more work on my own since submitting -00.

Thanks to Mikkel, Lars, Mike, and Christian for your thoughts on this work.

I'm sure there's still more work to do, but I'm submitting this now, in the
hope that it will be helpful in discussions about multiple paths for QUIC,
which should take a back seat while the IESG is balloting on the core QUIC
specifications, but I hope will pop up before IETF 110.

If you have thoughts about -01, they're welcome, whether in Github, on the
mailing list, or in private e-mail (I've gotten all three forms of input on



---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, Jan 17, 2021 at 5:58 PM
Subject: New Version Notification for
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>

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

Name:           draft-dawkins-quic-multipath-questions
Revision:       01
Title:          Questions for Multiple Paths In QUIC
Document date:  2021-01-17
Group:          Individual Submission
Pages:          15

   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