IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Sat, 03 October 2020 00:53 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 9C14C3A176B for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 17:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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] 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 ZP9W8jIQqvSR for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 17:53:13 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 3AE443A176C for <quic@ietf.org>; Fri, 2 Oct 2020 17:53:13 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id a3so4184458ejy.11 for <quic@ietf.org>; Fri, 02 Oct 2020 17:53:13 -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=5vgf6JH8ctrDEexkZODELplagRY3Iv6nF29lrCjHTU0=; b=fLnsIDyZbBAhLjWXyB4+4gugrhWibseRIalDhn05AScjCnfW35+T3XaNCdWyEhPiT+ No776rpGCpwasFvYTee2Zhmkitf8RZlQlV4uQEhTJZ0ihXXUuEkZaMM4BESSTdEJuYeY Js2dfWzKVNZ5cwh9awCgjfg2rIPRO88K6tNM5XzAQTQgYJDe3a1HVC2y54MdYQoW0vcU 2noT3qUKm6oJUI3tsG+P5VYr0pzGIaWLbgA68zP4aEA8nEaR94QKWW1itceulwXaZI9E MX2jRZM6vA/Y/pZVjRpqLAgijjEIfPdH89EpDJKaoMV2iTV275XcX75H339J/7N+OBWQ j1EA==
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=5vgf6JH8ctrDEexkZODELplagRY3Iv6nF29lrCjHTU0=; b=AVrY0KYu6hshbd5WlvpQMkPD1VgymdZ2qAEahCRuz1AxfV9NrTrP0B6XHXYvdzT+fg ZfjBajPw2W+7YaBkMQ7OyKQQQ/n+7l0tVyoQPZzMCRlp1XmDwGV1tbgXNV5ZfTYCEhkX 2eVJVrOHsFd/BFyRtJPL8j1rlsMD0dE+BqO1Ra64Y1k+IYLqWcWzjbjIL9Ig/xF9T9Iy NGhpQIpPkgXiSRoCQanRUuvypGUrgxbZ+EKb/UygBpdCcgrSRsyxL4wADMicGmZrlSrJ vYmTQpA5wKIsTeeGrm2Hj9Y/4NAoHa0dpN7jUal6AQa80PicMHnt7mB7eXYcQewRiAw6 r+BA==
X-Gm-Message-State: AOAM531WASArwu64HuX0kNgTWyErQsEg6KDIYfuv8RGf9sF7femRJzNd eSM2LMMmNRrJKi/a/+WBYDaHgJ8Uv3h4Jotyk4s=
X-Google-Smtp-Source: ABdhPJzrgymfDbxkglhhng5Yisx7hyg2iTl5c98z8COtOxyEedRxm8ZNSMrQTzDf6k+XKnuxh5SCJFVouNwoKcQYQSU=
X-Received: by 2002:a17:906:2747:: with SMTP id a7mr4603113ejd.301.1601686391765; Fri, 02 Oct 2020 17:53:11 -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> <CALGR9ob39AhBQq5kt1tsBp6b3EHy8Aq-PkT_tSX3_hM-u9kYnQ@mail.gmail.com> <20201002232028.GG2124@MacBook-Pro.local> <CALGR9oYUcTeBjNba6xAj0YLJwQc772u6K4H=VBKbG6cRaAjUUQ@mail.gmail.com> <20201003000902.GA94326@MacBook-Pro.local>
In-Reply-To: <20201003000902.GA94326@MacBook-Pro.local>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Sat, 03 Oct 2020 01:53:02 +0100
Message-ID: <CALGR9oYZWxfE602b2YgHbyd-rz6KvCRtR5q4qY2Vjdiqmmy0NQ@mail.gmail.com>
Subject: Re: Preparing for discussion on what to do about the multipath extension milestone
To: Christoph Paasch <cpaasch@apple.com>
Cc: Matt Joras <matt.joras@gmail.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="0000000000006c41b805b0b9ac31"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b5h6YuGuQaexaIOs7XcrCR9E6z4>
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: Sat, 03 Oct 2020 00:53:15 -0000

Hey,

On Sat, 3 Oct 2020, 01:09 Christoph Paasch, <cpaasch@apple.com> wrote:

> Hello Lucas,
>
>
> "could hurt end users", you mean consume significant cellular data? Or do
> you mean hurt performance?


> If it is the former, I agree. And that's why the client should not
> establish
> a uniflow unless it actually is willing to receive data on that uniflow.
>

Yes I meant this former case. And by using the term end user I was very
much channeling RFC 8890.

I doubt there is a specific reason on why the MP-QUIC draft does not have
> such an "MP_PRIO"-concept. In any case, that would be a minor point that
> can
> easily be added.
>

Thats a good suggestion, I think adding something on this would help.

Cheers
Lucas


>

v2.23.0 | Report a Bug | By Email