IETF Logo Mail Archive

Re: Proposed response to Liaison Statement "LS on need for Multi-Path QUIC for ATSSS"

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 14 May 2020 02:56 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 DB13F3A093E for <quic@ietfa.amsl.com>; Wed, 13 May 2020 19:56:11 -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 zyBobi-r2aG8 for <quic@ietfa.amsl.com>; Wed, 13 May 2020 19:56:10 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 1213C3A093C for <quic@ietf.org>; Wed, 13 May 2020 19:56:10 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id g1so1799419ljk.7 for <quic@ietf.org>; Wed, 13 May 2020 19:56:09 -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=6+WLw2e0FgWb3RpJBCalVBmDNS4Wid6K/qncBDOb31g=; b=ugXuHrSnu34oIgkvudDn6CnJg2e01HqJspz94qdqjNdpEitJdBt/gAVk3GpMSKJSj0 a8GrsfnfeIruG7pnonkRQtnEKx+GBuHJPVlywQCOiUbei6sYEvKqccRJer0ELaphidpj HXWNpdvV/T3Wk1CMOMNo3LCLZwK3yCY6ZYcxXRwsIqK5oJFCDFUiEoZd2+NDCgoWqfZr PhL86nG5DefqY6sckcTz3nIqaazYVgWxnYCVC2nOF/bOFeGoUxT1LrnO34vl01QzsmAc pYN/9SN7WVN8jtwgiv7luqvkz8P1x1mjUqreZ0PaMhtz+zzIOI5cV2UFM1s2qONLEz3e 8QIA==
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=6+WLw2e0FgWb3RpJBCalVBmDNS4Wid6K/qncBDOb31g=; b=IrEj2EDaz1yG/UThe+9rPvQPKBZSj/wl2BToBtCv6f9a98V0Q3YGYz6ybIDky85J2/ RrudRslqydJy0xhwkzPL4lNEkui89HN3ReUZgKEKCKLXH5bzyY/+W5pduTVe8EEMm71A CIgkYsnI+vOkUtZYYM8FVjwdoGCKumq7CVOHpJAoPPmY9A463bAXE+q/zB+2lxstUIJW shsaMQIjWZib+mA7cls/j+3WlMazgREgOkBoq02rv1TE7D6/no8CMQFcTR2RiESwxUUY AEpAxxp2Z4rHyKLHsk8H8PXNkEtzbwwgxE5XcicXLBF1KNd9bMYZiOOGU5otLf8qr2zx v6Pw==
X-Gm-Message-State: AOAM532VJ5MVuQTTRET1RfSAhFemovh0Hh2+yIi7kCt8IxLl+WJT1z7s 3Zd/40TJjQeWiGBptZfrZYZ0aFCZzW82DhmS41w=
X-Google-Smtp-Source: ABdhPJzQWxcrlecFX2icquBA9diF7UI8ezqNl8+sod22xWHPnl/0NbTfFcCYrzmONEquYNzYsE7VrSeC4vC1zGxYVss=
X-Received: by 2002:a2e:9255:: with SMTP id v21mr1213884ljg.222.1589424968231; Wed, 13 May 2020 19:56:08 -0700 (PDT)
MIME-Version: 1.0
References: <158575376802.30598.14992202513752114049@ietfa.amsl.com> <53440b6005987fe7b3608186a48428d626d92422.camel@ericsson.com> <890062AB-4F69-490E-95DF-E13841442489@eggert.org> <2D62E1CA-AD7F-4D16-BB98-FDDB0B5F4EE4@eggert.org>
In-Reply-To: <2D62E1CA-AD7F-4D16-BB98-FDDB0B5F4EE4@eggert.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 13 May 2020 21:55:41 -0500
Message-ID: <CAKKJt-dRiueGOXtSB1aknVtvhLi7oNW4rhFbCCDsuQud=QJozA@mail.gmail.com>
Subject: Re: Proposed response to Liaison Statement "LS on need for Multi-Path QUIC for ATSSS"
To: Lars Eggert <lars@eggert.org>
Cc: "quic@ietf.org" <quic@ietf.org>, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a0ff7a05a592d693"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/v4OZKAKJviqX3cTrKfh4oF0uaYc>
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, 14 May 2020 02:56:12 -0000

Hi, Lars,

On Wed, May 13, 2020 at 8:11 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> incorporating the received feedback, we plan on sending the attached
> response shortly.
>
> Thanks,
> Lars
>
> ---
>
> Thank you for your input to our specifications.
>
> Multipath capabilities for QUIC are currently under active discussion in
> the
> IETF's QUIC WG. Several individual proposals have been made, but the group
> is
> also considering whether the already-specified connection migration
> capabilities
> are sufficient to cover the majority of use cases.
>
> We encourage 3GPP to contribute their requirements for QUIC multipath
> capabilities
>

I had suggested using some other term than "requirements", because the
liaison to the IETF came from SA2 (architecture) in 3GPP, not SA1
(requirements), and I'm concerned about this turning into a three-ring
circus between SA2, SA1, and SA plenary (all of which communicate with each
other through formal liaison statements approved at formal meetings).

Perhaps I worry too much. Do the right thing, of course.

The rest of this response seems fine. Thanks for the quick reaction.

Best,

Spencer


> in an Internet-Draft, especially if the already-specified connection
> migration
> capabilities are deemed insufficient. 3GPP's active involvement in any
> multipath
> QUIC standardization would be the best way to remain informed of the
> progress of
> any such work in the IETF.
>
> Kind regards,
> Mark Nottingham, Lucas Pardue and Lars Eggert, QUIC Working Group chairs
>

v2.23.0 | Report a Bug | By Email