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

Lars Eggert <lars@eggert.org> Thu, 14 May 2020 04:01 UTC

Return-Path: <lars@eggert.org>
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 D7CB03A0B04 for <quic@ietfa.amsl.com>; Wed, 13 May 2020 21:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 D4mYO2Ix-Z9b for <quic@ietfa.amsl.com>; Wed, 13 May 2020 21:01:16 -0700 (PDT)
Received: from fgw20-4.mail.saunalahti.fi (fgw20-4.mail.saunalahti.fi [62.142.5.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 906EA3A0B0E for <quic@ietf.org>; Wed, 13 May 2020 21:01:14 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) by fgw20.mail.saunalahti.fi (Halon) with ESMTPSA id 675b1f86-9597-11ea-ba22-005056bd6ce9; Thu, 14 May 2020 07:00:10 +0300 (EEST)
Received: from [IPv6:2a00:ac00:0:35:f5bb:2f5e:3e6b:d95b] (unknown [IPv6:2a00:ac00:0:35:f5bb:2f5e:3e6b:d95b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 86C36691C53; Thu, 14 May 2020 06:59:57 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1589428797; bh=POUVRg09iFVgx0nppiiP7c4hkOmlzzeAVl2SQ9v9EPg=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=dfyRslbCwuyMv3oYpVMaiJyzZ0wKMsKqXRPlvvnUoQKcHm0NJjW/6nzB8raxvmIi+ EDMq9HSZIQz7nFwLhPHjstuWZwKAYNZDUFFfMvTENSR9Ttbx4kCRckQL22v5ciSu4P unDxYw68jwgwINmRI6L/obsOYtr2YqTXclMMGGbQ=
Content-Type: multipart/alternative; boundary=Apple-Mail-FD991A72-A776-41A3-A620-0252F9B3E480
Content-Transfer-Encoding: 7bit
From: Lars Eggert <lars@eggert.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Proposed response to Liaison Statement "LS on need for Multi-Path QUIC for ATSSS"
Date: Thu, 14 May 2020 06:59:54 +0300
Message-Id: <02844836-F2C4-41FB-8328-68EAA30CA5F7@eggert.org>
References: <CAKKJt-dRiueGOXtSB1aknVtvhLi7oNW4rhFbCCDsuQud=QJozA@mail.gmail.com>
Cc: "quic@ietf.org" <quic@ietf.org>, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
In-Reply-To: <CAKKJt-dRiueGOXtSB1aknVtvhLi7oNW4rhFbCCDsuQud=QJozA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-MailScanner-ID: 86C36691C53.A5F8F
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KMDmQAgc8LWEsSe_C0LYMRsibHg>
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 04:01:18 -0000

I changed “detail” to “contribute” in response to your email. I’m sorry if that didn’t fully capture your suggestions!

-- 
Sent from a mobile device; please excuse typos.

> On May 14, 2020, at 05:56, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> 
> 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