IETF Logo Mail Archive

Re: Preparing for discussion on what to do about the multipath extension milestone

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 02 October 2020 17:51 UTC

Return-Path: <lucaspardue.24.7@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 3E54D3A11F3 for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 10:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, 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 XG202IAcAN-0 for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 10:51:20 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 9074C3A1194 for <quic@ietf.org>; Fri, 2 Oct 2020 10:51:20 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id b12so2539003edz.11 for <quic@ietf.org>; Fri, 02 Oct 2020 10:51:20 -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=J7nR1i2MSiQToDDOt9u3DJsypUAXBp94ufsjAsFm7V4=; b=nzD6jcX0shj/Yulfz/jScn8pZGsa6dqyXZ8U0pIcJwbkcopvNfD3QTsLPN06sT01Ep hwEHeq73YlT0Bo3op/6SkTovS8nx8OsmzQRTgzBp1NhhqiJZ+XbIEZB7cM3LrSgJn0zl tn7eJjuLbkileqa+5OcHYZle721nckRp7j20DgxY9gETEgAXl+QtGf5fOeJujbJlHNOT +krv2kDl2yZSwJKt4LIhx54ZIKgxj5SF9CPnBKgMuuocMYtgllKyPImsKsuUPO4XzTih AaOPMNidAtGfsKkuD2pPoYsgWToQ1lC8741vkTe9ix0dQ4HzFpztumTCNx2/p6UTGMRK ijeA==
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=J7nR1i2MSiQToDDOt9u3DJsypUAXBp94ufsjAsFm7V4=; b=PCnhgkJEpUNvvmt6zFbgU6qGLztXKa792griPjqjhDfDUek9XvfOaJ9J+VE1zkg6E7 LbxodK6Qsbj5iuuC1AxaJffS9S/Q4Z8V4gqzN/dz2iLhwA+D2sARivS3kxl3hLu7+7JV OwPnatALUHDjIIz1cM+0/PqF3lyOKAVyGRJ0muo6VEeb+5H5hEfpCfsk8SDkxqH8ik93 w7leJWOVvrKrvBLPGjMDO/wG3LWiHYTrF8CDQBJzHUDjjA6Se91WSPgTCVdr7yMbvNkD 3zT4MD838w46DpTfaeOKWcmHMHtt1+Swz7em+80F3/WVLqhPViQIBuk5O0P3F83rgiqx O+Hg==
X-Gm-Message-State: AOAM531df1vhhULly29HG/UA+XbRvGhcMXXin9VpG3/GjNz6B7D89wky yv2sXurJSi4b8Kb8OL+WNDMho+oB6EEwUFYaeZI=
X-Google-Smtp-Source: ABdhPJzMQxmq7La+LoweDoNAxK7c70S3FDPttwedj/FHDcVBoL4wkrHDwKAKwAky25nZPQ5aXElCPCfy+Kqf//bIS08=
X-Received: by 2002:a50:da45:: with SMTP id a5mr3732825edk.152.1601661078918; Fri, 02 Oct 2020 10:51:18 -0700 (PDT)
MIME-Version: 1.0
References: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org> <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com> <78651438-2fce-ba67-4f44-4228bbc79a75@uclouvain.be> <CADdTf+hOACZ1x=d8SV-aX0f3vc+_fyqTziRqi5gi+nJgppaz8A@mail.gmail.com> <CAKcm_gNF=0gwrPt=Mr1P=dF_-wmXfz-OJkavFSDe1qrXFeMa4A@mail.gmail.com> <20201002164854.GA2124@MacBook-Pro.local> <CADdTf+heu4DGT8PsF0yL1cknTCB0CiHJ_jBwXZ86ccxL6740qA@mail.gmail.com>
In-Reply-To: <CADdTf+heu4DGT8PsF0yL1cknTCB0CiHJ_jBwXZ86ccxL6740qA@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 02 Oct 2020 18:51:07 +0100
Message-ID: <CALGR9ob39AhBQq5kt1tsBp6b3EHy8Aq-PkT_tSX3_hM-u9kYnQ@mail.gmail.com>
Subject: Re: Preparing for discussion on what to do about the multipath extension milestone
To: Matt Joras <matt.joras@gmail.com>
Cc: Christoph Paasch <cpaasch@apple.com>, QUIC WG <quic@ietf.org>, Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8d9d805b0b3c752"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/A1DhSRjuU4xCTliHts3_hJTeGz0>
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, 02 Oct 2020 17:51:22 -0000

+1 to the suggestion to discuss use cases, it is helpful for clarity. And
thanks Christoph for sharing some specific ones.

For the use cases "Siri" and "Apple Music", since I'm not experienced with
multipath there's a gap in my understanding of how the proposal in
draft-deconinck-quic-multipath would be used to satisfy these use cases.
For instance, is the behaviour client-driven, server-driven or does it
require coordination? Would anyone be so kind as to share _an example_ of
how uniflows would be used within a QUIC connection that uses a
request/response paradigm for data exchange.

> Another question, and perhaps this is getting increasingly off-topic, but
now that we are getting into designing "significant" extensions, I think it
is worth asking whether this should be an extension at all. I.e. should
MPQUIC be a core feature of QUICv2?

I tried to spin that out into another thread [1]. IIRC someone previously
suggested that MP-QUIC could start as an experimental version of it's own.
I can't find a citation for that though sorry.


[1] https://mailarchive.ietf.org/arch/msg/quic/p2II8y3y1FXy4kWMSuf1lgAXaFA/

v2.23.0 | Report a Bug | By Email