Re: 2nd draft, response to Liaison Statement, "LS on ATSSS Phase 2Requirements to IETF QUIC Working Group"

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 01 October 2020 14:33 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 AB7313A1205 for <quic@ietfa.amsl.com>; Thu, 1 Oct 2020 07:33:39 -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 ARYvWGNdJt-B for <quic@ietfa.amsl.com>; Thu, 1 Oct 2020 07:33:37 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 948D43A1136 for <quic@ietf.org>; Thu, 1 Oct 2020 07:33:21 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id k2so4181382ybp.7 for <quic@ietf.org>; Thu, 01 Oct 2020 07:33:21 -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=IudtdgTalVzt2i0Mo1eO3T9jpxJMeVQNzxhBV7DQmKM=; b=AzPEVGhoedzTbpkg1hjUSKL/STgfsadjNEOb9WLq5kp4pp2H0GkqPj+0G8fhemLu1N fF/57yXF6z+B7py6VVM6d+4RQ7HiI/5gH3PaDPhcPI/7R5d7i+3wyW58/9GL+RUJEh/E 79M+e736pj/hIsZoQ8uAH9Y+WMaPB3B9S5wI6oHfgWGoMQZAkfJqWSq1taleA4cVa1Q4 63zeA4+CJVoGTC+2dDh2S1wApNBNAtSFR9bCd0RD0qv459zAhkXI2svzozbM4HPYdMUG OFmsWzcaXQdUXKwiErbHAxJ9qJ0H4LqIr7WWt2hyNJO0FncKWMNDMWfdb+aljh9t7eGB imoQ==
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=IudtdgTalVzt2i0Mo1eO3T9jpxJMeVQNzxhBV7DQmKM=; b=uaQV40NytyBAhzHgQ2WWyd7RfnIG0rylncknPDAA5n8zyzmsdQ68Hznzst6bKQNPT9 t+vdrSEc0teJ/rq91tCDq6QSXXVeNpZvWncHm1y0VaufYcHGsAdyum72I0UNQQENlfoA ZpcjdC7sJXS22qzL8WC6MsAaaFq8hrWug6cTPA/zw6lxe4ObyaxMnlAnPntWGE4WYHhK PL3wukKtBSFIbifJgqKmORZwGRhG45c9ZvKoUN3H7KNOl5rvgnZRw3eoQpis+hStAgJ6 2wraMt0tUMKhqUIN6bCXPPOF30MW2ZbiP1SbxcNTLxvZlt551WEvGoqhHfLYXhq83a48 72Ew==
X-Gm-Message-State: AOAM531ibUoQu7gp7w86hFcFbUbT6bBToK4qMBKGuAm7M6adUtY0kyD0 v7DMF9rOR/zpqGVncgLNoKZVtqM7Ydo1v8QwsviVnX4X
X-Google-Smtp-Source: ABdhPJx8ok5ngnUxOxTOauzipCbqflCM5XvPJ14bxArFPXtnMjj6aYNl18rU4pv3edVMJ4GOMd+t8tPDJKdyyeDLvD0=
X-Received: by 2002:a25:ab8e:: with SMTP id v14mr10953383ybi.465.1601562800713; Thu, 01 Oct 2020 07:33:20 -0700 (PDT)
MIME-Version: 1.0
References: <61E60D24-856D-44FF-B133-693FC9C40229@eggert.org>
In-Reply-To: <61E60D24-856D-44FF-B133-693FC9C40229@eggert.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 01 Oct 2020 09:32:54 -0500
Message-ID: <CAKKJt-fH1oSTaEw6_L6b-bdJxWP7RB2iVgeErRu4KW4zCNhZzg@mail.gmail.com>
Subject: Re: 2nd draft, response to Liaison Statement, "LS on ATSSS Phase 2Requirements to IETF QUIC Working Group"
To: Lars Eggert <lars@eggert.org>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2725e05b09ce511"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5h_LSvg7BmrUPyV93nsqdJDPu3s>
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, 01 Oct 2020 14:33:47 -0000

Hi, Lars,

On Thu, Oct 1, 2020 at 6:20 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> thanks for the feedback! Below is an updated draft that attempts to
> incorporate it.
>
> Please feel free to send further comments.
>
> Thanks,
> Lars, Lucas and Mark
>
> --
>
> Thank you for the update on your progress and your questions. Please find
> our
> responses below.
>
> On Qn-1: The future of multipath support for QUIC is currently under active
> discussion in the IETF QUIC working group. While it was part of the
> original
> charter due to being under active investigation for the pre-IETF "Google
> QUIC"
> protocol, several participants have argued during the last year that QUIC's
> connection migration support is sufficient for the majority of our use
> cases,
> and that full-blown support for multipath QUIC should consequently be
> abandoned
> as a WG deliverable. Other WG participants remain of the opinion that
> multipath
> support for QUIC is very important. Due to this active ongoing discussion,
> we do
> not have an estimate at this time whether WG drafts for multipath QUIC
> will be
> available in 1Q2021.
>

This is much improved.

Perhaps it is also worth pointing out that (just like 3GPP) the IETF and
QUIC working group are contribution-driven, so any timeline estimates
depend on people contributing to the work, and the IETF is open to
participation from anyone who can contribute to the work.


> On Qn-2: The QUIC WG is chartered to provide an encrypted transport
> protocol.
> An option to disable encryption will hence not be standardized.
>

That's the right answer to the question the QUIC working group was asked. I
agree that a different question might have gotten a different answer, but
you're not a mind reader ...

Best,

Spencer


> Kind regards,
> Mark Nottingham, Lucas Pardue and Lars Eggert, QUIC Working Group chairs
>
>