IETF Logo Mail Archive

Re: Multipath (was: Re: Re-chartering for extension work)

Olivier Bonaventure <olivier.bonaventure@tessares.net> Fri, 20 December 2019 13:30 UTC

Return-Path: <olivier.bonaventure@tessares.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70DC712010C for <quic@ietfa.amsl.com>; Fri, 20 Dec 2019 05:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=tessares-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNrABm1qeCVk for <quic@ietfa.amsl.com>; Fri, 20 Dec 2019 05:30:29 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 5FE22120025 for <quic@ietf.org>; Fri, 20 Dec 2019 05:30:29 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id c9so9427782wrw.8 for <quic@ietf.org>; Fri, 20 Dec 2019 05:30:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=7MX7jnx0BazTouubXpOgt4HeQpI00ulrCRrDRbcbpxY=; b=qp7OPe/CDEnoghxYyzh3HF6+SkISA0ZlnifSJeadH96Va/guDTmbfPycNgyIthnJof J6zrnkHucOk5buAoeP1CYG0/Sy5atfFoFFJsWVhJ+lW5DpbdznhzINXcxaPKiIEDzjwF Qd7YL+gnVV0AIx5PvApwrkegWoifE3iPORuFxdnP6Qrj9eelSkJDNO9vfoEOLtwmtpWz kQ1WQXc9Jp/yQWv4HbHkF5ZLLYnnYu3mOqmEGqSB2spmmGs7AAu33oJpScpImScEOmT1 qhb4naBvYbxg42vPG2DjHe2I4TFBJb5iPT3HYss/Iv7Q2wZ1Op6jL/X1w9dxrXn4/DUD odvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=7MX7jnx0BazTouubXpOgt4HeQpI00ulrCRrDRbcbpxY=; b=VG8ebJyVLzEyspUYL16D74GG6Vys71TVq/Es+WNkUyGnu/P1BHp5C3QxB5Z9HelSdM 56NYwPBKIcscIxLc/6XSXYD84lzd02WwEaHx5uyDe2lL7ZyjbpCCmYbkcqwtwmZyTthe MmAbWzcUX4rtitBVwH2S4cIVQ43atDaHpqTlG1GX+AvZ6Zb5ivcCmjvd0usmGaqYaHad 3Ri2+M/P122LFiRZP8vqoBp0RL70mQsOsQIi2dTcTir7VIMpMODP6iWDNIGx0VaB4PDT pfUVNVS9aPTKeOpThptOnl/pTfam/Is7Xoxx8V041lKnGH9y2YyaAu3x9xtMAg0n+7Ck NDMw==
X-Gm-Message-State: APjAAAXsJiM3Ki/gKE+xrMfp95idifIR47wWY/BYWFMlAZeXa3WTo2xp Tr1ANBJidsqDR3IskoswUhMQ3FUVvv74jbQf3WVBSrWwEDl0jIJr7dQN8STOs1rB8epAfCko
X-Google-Smtp-Source: APXvYqzDKZ6OPwrpGBUUGqvopDEV8Glj6a9sEyvAbyc1MIhBeHCX4MlHu2WHIuKGflO4OqbkowLXYA==
X-Received: by 2002:adf:dd46:: with SMTP id u6mr15795405wrm.13.1576848627653; Fri, 20 Dec 2019 05:30:27 -0800 (PST)
Received: from ?IPv6:2001:6a8:308f:2:4:3cec:cd70:33ea? ([2001:6a8:308f:2:4:3cec:cd70:33ea]) by smtp.gmail.com with ESMTPSA id v62sm9847239wmg.3.2019.12.20.05.30.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Dec 2019 05:30:25 -0800 (PST)
From: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Message-Id: <D9AB44F9-8EBA-42F7-957F-69622C0681CE@tessares.net>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Multipath (was: Re: Re-chartering for extension work)
Date: Fri, 20 Dec 2019 14:30:24 +0100
In-Reply-To: <CAJ_4DfT_riJr0n0KyD43iRZ+pmkqFiU3YPaTobZcLdqPJVUYYw@mail.gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Quentin De Coninck <quentin.deconinck@uclouvain.be>, Mark Nottingham <mnot@mnot.net>, Christian Huitema <huitema@huitema.net>, Lars Eggert <lars@eggert.org>, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>
To: Ryan Hamilton <rch@google.com>
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <1E872371-F543-4822-8C11-05601913A72E@tessares.net> <752D0B90-8B29-4DBC-9B2F-09E834335598@eggert.org> <49366B32-6425-486C-9453-96D27E2E8EAE@tessares.net> <CAN1APdfNyMBzeWKVRQojo4W_mgxXSSwj4X4EvFC9Pfz4bZ+Pdg@mail.gmail.com> <DF4E42C3-3D90-4C68-989C-6B11833005F9@tessares.net> <CAN1APddWow_QBs+_6GRLyauWFrLVvcr7LA9Mjqdgw-Bcp0d=tQ@mail.gmail.com> <9bc43313-7a06-8b01-75ef-ff1c3925a6cc@huitema.net> <CACpbDccdpKHygp87Be-ytC7juYZmUrfh-3a=4ESLCWMfE-t6Ww@mail.gmail.com> <839F7E31-FB6A-4846-A3C4-C5539E14407E@tessares.net> <CAJ_4DfT_riJr0n0KyD43iRZ+pmkqFiU3YPaTobZcLdqPJVUYYw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3851583-616B-4BA7-9910-B3F643768CC0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UfSkVRyx42d-9tMKdyIuaQhHSM8>
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: Fri, 20 Dec 2019 13:30:31 -0000

Ryan,

> On Wed, Dec 18, 2019 at 10:40 AM Olivier Bonaventure <olivier.bonaventure@tessares.net <mailto:olivier.bonaventure@tessares.net>> wrote:
> [snip]
> 
> A second use case is for mobile devices that need to preserve connectivity while switching from one wireless network to another. When such a device detects another wireless network, it needs to bet whether migrating the connection to the new network would improve performance. With a multipath transport, there is no need to bet as the transport will automatically select the best performing network. Apple’s deployment of Multipath TCP is a good example of the benefits of such a multipath strategy.
> 
> FWIW, QUIC connection migration was designed to do explicitly this and has been very successful in Google's deployment. I don't think this is a good justification for multipath QUIC.
> 

Connection migration works well when there is a clear indication that one path is clearly broken. Unfortunately, there are many practical situations where paths are partially broken or experience high packet losses and this is where multipath really brings benefits.

Olivier
-- 


Disclaimer: https://www.tessares.net/mail-disclaimer/ 
<https://www.tessares.net/mail-disclaimer/>

v2.23.0 | Report a Bug | By Email