Re: My BoF report: multipath
Jana Iyengar <jri.ietf@gmail.com> Tue, 27 October 2020 03:43 UTC
Return-Path: <jri.ietf@gmail.com>
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 9FCC93A1475 for <quic@ietfa.amsl.com>; Mon, 26 Oct 2020 20:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8H0U3Rfic5a7 for <quic@ietfa.amsl.com>; Mon, 26 Oct 2020 20:43:17 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 862223A1471 for <quic@ietf.org>; Mon, 26 Oct 2020 20:43:17 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id v6so432753lfa.13 for <quic@ietf.org>; Mon, 26 Oct 2020 20:43:17 -0700 (PDT)
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=oOc2hl8ZvPr+wZWc5Vj5nmvpU5Ah5bhDgUIxiI8q6vY=; b=HXn71xMb5hKOUCmdPZQaGMDePHPnAe2UTGbRTRvvNDAtdq67jzCXFAePB4BjbrLS4K CVZEP8RCyjfvxML1GpAp9gX0kLltsY4qT9VgqJFFQADmddS3gVG73SY6N3RcYIFB3Ck2 BL6vqPoV3FZc335lanxbmtmDFfq8AADTrwWKTBoLn+sGKN43DQPwD+bCgG6p3YY8dFTl cx6poCrjxilloOJhplzPxwe8VFlnR7URjV/RDZ9l7ex4dtNArwrhkmEoKUtX2RvxfHCP PZsnumiD6KL8xlOMLamtZ/cfkKFim4ctrPYjponbLnqbYhDH+1lUbgAbAYtjey0O+MIc FrWA==
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=oOc2hl8ZvPr+wZWc5Vj5nmvpU5Ah5bhDgUIxiI8q6vY=; b=lYqOuoYVZKQ12gmmL0uUl486YnEdxnwqmj1o0qV7smgXz75ExSEFQqkvmvwCDxrxOl OHb6Sa83twV6UpZ8JS57j6drh7cxWkBNnrzgG9weRVZbzeqfCJ9W0sILPEy8SsNXqxjW BdxDHuYzudpnHtsuOOfYUmcGocK+WsBEJqzmAA0cmDwwp8J8VI52lrUJlvYejU+Wpd3v ovGIoY2wdz46oUrL5PCk6J2Z50xeRPpDjtZvleiG9E5i+x+rQyrw7NQeis1qhI2fEXPX sSnAjMSq4bomxJApcPIAkqT7ekYcn1tp3Qn2WRJoWbaDi/gTTN4fbrqo4FTW7JDOPrPR sh/g==
X-Gm-Message-State: AOAM532upHQB01cYaI28VCjtF6HAPZdq+BcM/OF0G5YTbLtpBNrH8z8n 8xWj0f/6VwMS5rbahTXcdmWr/Kx+e2CneXY3GMTk4+by
X-Google-Smtp-Source: ABdhPJyufKFb4uAI/BrfBh+CJ2Dg3NdMnA++YDphNeUsH4zjJjiUNyKh2pUq5Wa2LtLQtpGm/mcVMuBJwGkDI9XNAPA=
X-Received: by 2002:a19:4a16:: with SMTP id x22mr100474lfa.66.1603770195325; Mon, 26 Oct 2020 20:43:15 -0700 (PDT)
MIME-Version: 1.0
References: <d84c82b1-fa67-4676-9ce2-d2a53d81b5f7@www.fastmail.com> <5741601d-7e67-898e-5840-70feceb994e9@uclouvain.be> <CALGR9oZW0s6c6+N+3R8bD17yPBPQa4E_cVOaTOSNTVQPYy6sUg@mail.gmail.com> <CAC8QAcditJ0nzdCNHOhi-1xtezoXb0u=hrGBWtZ3Cj3XP6CW4g@mail.gmail.com> <CALGR9oZfw5LqfPyZw6Yb8JTmuqi0prTL0f0yT9Rdq6oz5u51fg@mail.gmail.com> <ccbd3f9a-883e-6262-5735-2b9f25c6c6c4@zinks.de>
In-Reply-To: <ccbd3f9a-883e-6262-5735-2b9f25c6c6c4@zinks.de>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 26 Oct 2020 20:43:04 -0700
Message-ID: <CACpbDcfsD0wWe=E4of1r9OY=Ah4i6jxmbWKBqXhZOeu22-G+Vg@mail.gmail.com>
Subject: Re: My BoF report: multipath
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb374605b29ed8a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AhDWbrNYsdevwq9COGeGc2YK168>
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: Tue, 27 Oct 2020 03:43:20 -0000
Thanks for kicking off this thread, Martin. Yet again, I want to focus on what is most important for us to work on right now. Rather than answering the theoretical question of what a well-rounded transport looks like, we need to focus on the engineering decision of what problems we need to work on right now in QUIC. We have multipath in QUIC. It may not be enough, but we agreed in this wg that this would be a good first cut to have. I believe this satisfies the charter text as we have it right now. We've just finished building the use of multipath in QUIC, and I'd like us to get some experience with it before considering how to expand its scope or how to improve it further. For those who want to experiment with other ways of using multiple paths: QUIC has many ways of extending the protocol. All you need to do is to build, deploy, gain experience, and share it with the rest of this group. I would love to hear more about such experiments going forward. In the meantime, let's not forget that we still have important unfinished business (version negotiation, tooling, load balancer work, potential optimizations). We're about to see wider deployment of QUICv1 and HTTP/3, which will be a massive shift in traffic. We will need bandwidth to discuss issues related to this deployment that are inevitable, and deal with immediate protocol issues that arise from our deployment experience of all things QUIC, including the multipath that we will be deploying. - jana On Fri, Oct 23, 2020 at 12:34 PM Roland Zink <roland@zinks.de> wrote: > A application works with a single connection most of the time. As > application developer you probably can't afford to put any effort in > improving this when it isn't absolute necessary. If you do it on the > application layer then the application may also get location information > out of it, like IP addresses or WiFi names, and this is a privacy issue. > > > Regards, > > Roland > > > Am 23.10.2020 um 18:34 schrieb Lucas Pardue: > > Hi Behcet > > On Fri, Oct 23, 2020 at 4:15 PM Behcet Sarikaya <sarikaya2012@gmail.com> > wrote: > >> Hi Lucas, >> >> On Fri, Oct 23, 2020 at 4:28 AM Lucas Pardue <lucaspardue.24.7@gmail.com> >> wrote: >> >>> Posting as an individual. >>> >>> Thanks to the time that people took to prepare, present and discuss, I >>> gained a better understanding of this area. >>> >>> One main takeaway for me is that thinking of QUIC v1 as singlepath puts >>> it in an unfair box. Others, such as Jana, articulated this point better >>> than I. >>> >>> QUIC is path independent, path aware and provides mechanisms, written in >>> the core document, for endpoints to interact and interoperate about >>> path-related things. Through the course of specification development things >>> might have gone different, and we might be having a conversion now about >>> whether the group should adopt a document that describes for instance just >>> connection migration. >>> >>> But migration is in the core and, based on the Slack discussion >>> following the interim, there appear to be several parties that have >>> expressed an interest in testing deployments of Connection migration. This >>> can be seen as some form of success. >>> >>> The use cases indicate that things like active-active paths or bandwidth >>> aggregation are desirable. But I was unable to discern objectively how more >>> of an optimal experience they would provide over a well tuned QUIC v1 >>> endpoint that use connection migration. >>> >>> >> >> Coming from IP layer, I have a message to QUIC enthusiasts: >> >> Connection migration is a solution for mobility at transport layer. >> Ideally, it should be IP layer. If a node moves, its connections normally >> break. So connection migration of QUIC solves that issue at the transport >> layer. >> >> OTOH multipath QUIC is a solution for multiple interfaces. If a node can >> be connected to the Internet over more than one interface using them >> simultaneously provides several advantages like increasing bandwidth, etc. >> >> > As an individual. I'll repeat my comment, I've seen little evidence that > some design that enables bandwidth aggregation in the QUIC transport over > multiple paths offers advantages over a well-tuned QUIC stack that delivers > over a single path. If the benefits of bandwidth are so huge, I might > expect that people would be clambering to add this quickly with multiple > QUIC connections coordinated in the application layer. That would allow > deployment and testing without needing to wait for the transport to be > redesigned. > > Let's not forget the disadvantages that bundling bandwidth can come with > too. These could be perfunctory or monetary. > > Cheers > Lucas > >
- My BoF report: multipath Martin Thomson
- Re: My BoF report: multipath Christian Huitema
- Re: My BoF report: multipath Spencer Dawkins at IETF
- Re: My BoF report: multipath Olivier Bonaventure
- Re: My BoF report: multipath Christian Huitema
- RE: My BoF report: multipath Flinck, Hannu (Nokia - FI/Espoo)
- Re: My BoF report: multipath Lucas Pardue
- Re: My BoF report: multipath Spencer Dawkins at IETF
- Re: My BoF report: multipath Behcet Sarikaya
- Re: My BoF report: multipath Lucas Pardue
- Re: My BoF report: multipath Roland Zink
- Privacy considerations of multipath (Re: My BoF r… Lucas Pardue
- Re: Privacy considerations of multipath (Re: My B… Roland Zink
- Re: Privacy considerations of multipath (Re: My B… Lucas Pardue
- Re: Privacy considerations of multipath (Re: My B… Spencer Dawkins at IETF
- Re: Privacy considerations of multipath (Re: My B… Christian Huitema
- Re: Privacy considerations of multipath (Re: My B… Lucas Pardue
- Re: Privacy considerations of multipath (Re: My B… Spencer Dawkins at IETF
- Re: Privacy considerations of multipath (Re: My B… Eric Kinnear
- Re: Privacy considerations of multipath (Re: My B… Lucas Pardue
- Re: My BoF report: multipath Jana Iyengar
- Re: Privacy considerations of multipath (Re: My B… Eric Kinnear
- Re: Privacy considerations of multipath (Re: My B… Ian Swett
- Re: Privacy considerations of multipath (Re: My B… Mirja Kuehlewind
- Re: Privacy considerations of multipath (Re: My B… Behcet Sarikaya
- Re: Privacy considerations of multipath (Re: My B… Ian Swett
- Re: Privacy considerations of multipath (Re: My B… Spencer Dawkins at IETF
- Re: Privacy considerations of multipath (Re: My B… Lucas Pardue