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

Olivier Bonaventure <olivier.bonaventure@tessares.net> Fri, 10 January 2020 09:51 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 E2E49120848 for <quic@ietfa.amsl.com>; Fri, 10 Jan 2020 01:51:03 -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 PRK9mHP2dVzf for <quic@ietfa.amsl.com>; Fri, 10 Jan 2020 01:51:01 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 AA83712081F for <quic@ietf.org>; Fri, 10 Jan 2020 01:51:00 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id b6so1187635wrq.0 for <quic@ietf.org>; Fri, 10 Jan 2020 01:51:00 -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=LVgvR2KQ/Eb58kaenVLnMFrEF6+Cz2c/Mllp1uU0UcA=; b=JziGezcpydyvTKtZEczkpwpvQ8/At9EnELPX2t7ZGLkPLz2YC5JLSrp9dY/djgG2ep NPeJ3I+XIA+ySASk1a7dOA7jt7WmpdUzCEJNHV460Rlgj96epIbr5wDVhQfH5H8LuSpw uWx521q/y8zMqsQwU4yJeBqGZZvBC7cnb4Kgf5SV0JnaE+h9lkksnu/EL6sx7QxirokR fnAzPZZjhQD67fEodKfAi3PEwa1SG5IlFutFRx7WfOnlLcMtXsKK1Ev+Jp/kpI7JrqC+ nnUo4o40fJxEmdJSiAPZMMwlYWmxybtrsFF9zjA2Bbmj6gHWJcpyH+b3ANaaJcMQII4P 3r+w==
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=LVgvR2KQ/Eb58kaenVLnMFrEF6+Cz2c/Mllp1uU0UcA=; b=h52F/sdk0Tm01eKYVfLhYOk5UsAFJyz1EqPmvCnso2FEU4uCb0gz5iTbpNr9LqxVNj oDAxbyu9+R2+NdvUteDf7EHl0ZGIe3HmZ3ExdO4iIsLhKk3mjoJOHOdYdH75fMMHSr7n uDvPzoB6A/4VGYzTueKFx9besIyPeCoOpp5m5iuBjS4rETYtoFiRCFmmFuyhMxUK3HSM cwF7IqpZHzliE3p1ok6/hQe9UFLgfYQybSMSnHOSVd0gRDLIFsKFGbBmY3MAZgCxFm8a UHWmfNfAfvUutcFjgjwkep1j9T6EH8vxs5xQceEMynSmU2GiKa30w0Luqc1OVcEh2cWh EFCA==
X-Gm-Message-State: APjAAAXNPxV2rK5BqhPJpSq6hZVvM7j93wLrSZhOstujBNRU89o237+S ry2Z4kX/bVrKAvHRK9ANaAqEFN6BTTzQvokDmB4ab8NNfRq1AwI77FEjHBHYJf7Ulu2ml9gu
X-Google-Smtp-Source: APXvYqxsRgp7kv+8shuvz3m4YjGI//s7avpoerPxLEgsZhiIRzTbG1PN2fIuLk8aOVn2ei++3yOA5g==
X-Received: by 2002:a5d:5491:: with SMTP id h17mr2584814wrv.374.1578649858821; Fri, 10 Jan 2020 01:50:58 -0800 (PST)
Received: from ?IPv6:2001:6a8:308f:2:e03b:2967:3016:4f90? ([2001:6a8:308f:2:e03b:2967:3016:4f90]) by smtp.gmail.com with ESMTPSA id r5sm1542723wrt.43.2020.01.10.01.50.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Jan 2020 01:50:58 -0800 (PST)
From: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Message-Id: <3A7DF177-3C7B-45AE-8677-BA1D0DC84A74@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, 10 Jan 2020 10:50:57 +0100
In-Reply-To: <148DA586-6EDF-4DBE-9CB0-685C66745A7C@ericsson.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Tommy Pauly <tpauly@apple.com>, Quentin De Coninck <quentin.deconinck@uclouvain.be>, Ryan Hamilton <rch@google.com>, 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: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
References: <D9AB44F9-8EBA-42F7-957F-69622C0681CE@tessares.net> <8EC91F90-2799-48EF-B083-D9C32F2D28F0@apple.com> <CACpbDcdsauAPDT0a_oqsMX1Dg+B8z61iAfurV1KwQwsUifGMcg@mail.gmail.com> <148DA586-6EDF-4DBE-9CB0-685C66745A7C@ericsson.com>
X-Mailer: Apple Mail (2.3445.104.11)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C72B095C-DB1B-4F80-A973-FF6D56D9AB73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/q3ND87OiJm34YrHwXoi99mpfZR8>
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, 10 Jan 2020 09:51:04 -0000

Dear Mirja,

>  
> As Tommy said, migration is already the first half of multipath support for QUIC. So I expect it will be easier to add it to QUIC than it was for TCP.

The main benefit of QUIC is that we do not need to take middleboxes into account and can reason about the transport layer directly. 

> I would at least be curious to spend some time on figuring out how much (or how less) effort it would be. Maybe there is also another step before going to full multipath support that could support the handover use case better, e.g. sending redundant data on multi paths or something. I think it worth think about it.


Please don’t do that. With QUIC,  have a unique opportunity to design an architecturally clean and easily deployable multipath transport protocol. We should not pollute this design with hacks and short term solutions that have been included in too many Internet protocols for various reasons. 

> However, while I would like to see this discussion starting now, I think it’s fine to wait for adoption of any draft until v1 is done.

As already explained in previous emails, Quentin De Coninck has leveraged all the lessons learned from Multipath TCP in a Multipath QUIC design that has evolved in parallel with the standardisation work of QUIC v1. The initial design was described in

https://multipath-quic.org/conext17-deconinck.pdf <https://multipath-quic.org/conext17-deconinck.pdf>  and in https://www.ietf.org/archive/id/draft-deconinck-multipath-quic-00.txt <https://www.ietf.org/archive/id/draft-deconinck-multipath-quic-00.txt>

There was a running implementation on top of quic-go that is available from https://multipath-quic.org <https://multipath-quic.org/>

The draft has evolved several times on https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/ <https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/> 

The recent draft has been implemented on top of picoquic and was released on pquic.org <http://pquic.org/> 

Quentin has studied these designs in details with many experiments, both in the lab and in the wild on smartphones. He’d be ready to present this in details to the working group if if eventually decides to work on the multipath item of its charter. I would encourage the working group members to start to read the last version of Quentin’s draft and provide comments.


Best regards,


Olivier


-- 


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