Re: [Fwd: New Liaison Statement, "LS on need for Multi-Path QUIC for ATSSS"]

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 02 April 2020 02: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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0335E3A09C8 for <quic@ietfa.amsl.com>; Wed, 1 Apr 2020 19:06:06 -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 0IiS8k_IigiC for <quic@ietfa.amsl.com>; Wed, 1 Apr 2020 19:06:04 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 850253A09C2 for <quic@ietf.org>; Wed, 1 Apr 2020 19:06:03 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id b1so1584704ljp.3 for <quic@ietf.org>; Wed, 01 Apr 2020 19:06:03 -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 :cc; bh=XRiTxLBNuP25ondDwf4Pot1iu3dyOwumosXGkPLMv/I=; b=NQ27JQYgePuWiEGmZYyKgivLI2we9n+4coNeMcNYVR7imiDqqM6AC0h+bjBT1w0hkV RvPXJEQ4Bflb0FIEu4Xiv21RDylfy5ih784SmCJ0NV59Ku5aCwDgy5tlziIK22oTPtKz ehTh/a3dy++5UOfzDMnVB7azcf4veHckzqBwYc9fJSD4nTGJoI3/3ddvLbMtqyzL8IcN YsNOK8TtvMnt4NuNDNR0CoBdSv78Afok+oY4wrM/yCvEP1Zcv63ydQbr1+AuUTV5/f0w AjrAMOE2yeuey1QDa/H/knYKd0n7+gwRGbXleL1tSwf5D9xfFSOBu+KmL1rewlWvn43A 3afw==
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:cc; bh=XRiTxLBNuP25ondDwf4Pot1iu3dyOwumosXGkPLMv/I=; b=Y4OGWgrlmZRJAjGH8W6fsl35W/v77ZKaZT0C2ph0OgAPy7rDPFVOt/slMIGlK/41dI wMiMawqe+zcEW3hZTOiGEuhng1x6IQSARXrJxX/X69dUilC/9iHuiHvAUYzxz9qS8Amm seZ7VQI9IBpza9FYJWxovi5N3QiChZd+voAARmzGjD57jnRLLKag5VtWrYQNDkjgwDD+ iuLFWz0JGZBD4Pw3fSCgjAjMU7rZebDlz45FWYB37IQaUXJ67rKvHVCi6pqRYLZha67I IoJks+3pgvKhPmEL28E9vVTW8bflLIlNiE1WItyo9O+nvA0cJ9aTx+VEvzZKkuODTPTa Io+A==
X-Gm-Message-State: AGi0PuaWrLQf+ZpqeEoS6DKBA5j2JmSHpEP6RQkj8/RqVv9yXv1U5SRq o8XdZykRkfJF5mORWroPXdaJAGDYKxWkzl2bk7hEfQtu
X-Google-Smtp-Source: APiQypKinrDpdvXK0LtlTP9uwzkHBH8mVTfXBlFpgZw5iqo95tlNN+y+RzO/39sVJ9jGA9UgGf4ZcpJMJ+m61I6way0=
X-Received: by 2002:a2e:9a89:: with SMTP id p9mr573292lji.222.1585793161698; Wed, 01 Apr 2020 19:06:01 -0700 (PDT)
MIME-Version: 1.0
References: <158575376802.30598.14992202513752114049@ietfa.amsl.com> <53440b6005987fe7b3608186a48428d626d92422.camel@ericsson.com> <14c8e8d3-1c93-408c-80d5-4fc298b42583@www.fastmail.com>
In-Reply-To: <14c8e8d3-1c93-408c-80d5-4fc298b42583@www.fastmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 01 Apr 2020 21:05:36 -0500
Message-ID: <CAKKJt-eSYR1r5nWQQWbBnGCn1EKnNXoBWOrthCcgXdqg1cxFqQ@mail.gmail.com>
Subject: Re: [Fwd: New Liaison Statement, "LS on need for Multi-Path QUIC for ATSSS"]
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000017221105a2453e37"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5kdKyd39WI5Hu7tYVVBQyYsDyHk>
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: Thu, 02 Apr 2020 02:06:06 -0000

Hi, Martin,

On Wed, Apr 1, 2020 at 6:56 PM Martin Thomson <mt@lowentropy.net> wrote:

> If I read this liaison correctly, this is effectively a request to keep
> 3GPP in the loop.  The request to do multipath is more implied than
> anything else.  I think that the explicit request is fine.  The implicit
> one maybe less so.
>
> I suspect that work here would go faster if we had more input on the hard
> multipath problems.  That's not the spelling of the protocol (that's almost
> trivial, as demonstrated in proposals), but the assignment of different
> information elements paths that might have different characteristics.  What
> I heard in Zürich was that this was less of an engineering problem than a
> research one.
>
> I'd be interested in having active engagement from people who have use
> cases. Specifically, I would seek to learn whether this is truly a research
> question or whether there are simplifying assumptions that might make the
> problem tractable for some use cases.
>
> The more I think on this subject, the more that I think it was a mistake
> to charter to do multipath.  I don't believe that we properly answered the
> standard BoF questions with respect to this topic.
>

You rang? :-)

Multipath has been in the QUIC charter since the first proposed version
(see https://datatracker.ietf.org/doc/charter-ietf-quic/00-00/), at my
urging, because I couldn't imagine chartering a new transport protocol in
2016 without multipath, given that we'd had to retrofit that into both TCP
and SCTP. So this might have been a mistake, but it's not a recent one, and
I made it (and achieved IETF consensus, of course :-)

When we chartered QUIC, I don't think we had a clear picture of how much
MP-TCP was going to depend on use cases in order to justify deployment. I
think that now, if we know anything about multipath, we know that.

I agree that this could be a research topic (in at least one of two or
three existing research groups).

I note that 3GPP has been relying on MP-TCP for ATSSS, and I hope that we
might be able to better than that, for their use case.

But we definitely have some talking to do with them about their use case.

Best,

Spencer, who hopes Mirja told Magnus and Martin that they can ALWAYS blame
the previous AD ;-)

On Thu, Apr 2, 2020, at 01:15, Magnus Westerlund wrote:
> > QUIC WG,
> >
> > The IETF has received the attached Liasion statement (
> > https://datatracker.ietf.org/liaison/1678/) that is intended for the
> QUIC WG.
> > Please review it and the WG should considerd sending information to 3GPP
> as
> > requested at key points in the process of the multi-path
> extension/version of
> > QUIC.
> >
> > Cheers
> >
> > Magnus Westerlund
> > TSV AD
> >
> >
> > Attachments:
> > * Email.eml
> > * smime.p7s
>
>