Re: Call for adoption: Multipath Extension for QUIC

Tommy Pauly <tpauly@apple.com> Fri, 14 January 2022 17:21 UTC

Return-Path: <tpauly@apple.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 EFFCD3A2B71; Fri, 14 Jan 2022 09:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.661
X-Spam-Level:
X-Spam-Status: No, score=-2.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, 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, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 Cb2iwRfsRhT7; Fri, 14 Jan 2022 09:21:12 -0800 (PST)
Received: from rn-mailsvcp-ppex-lapp24.apple.com (rn-mailsvcp-ppex-lapp24.rno.apple.com [17.179.253.38]) (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 1E48B3A2B6F; Fri, 14 Jan 2022 09:21:12 -0800 (PST)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp24.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp24.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 20EH9BwH032756; Fri, 14 Jan 2022 09:21:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : content-transfer-encoding : from : mime-version : subject : date : message-id : references : cc : in-reply-to : to; s=20180706; bh=07ctRPRjjfdRR0vbFKKZgBAvhJwOGeelK7XXxVMx2JY=; b=EGkTAZ8WwvAL2OjQ6cKoHnBDqSX3P7ucd7rgvXewhGBgnnE5Z6ROw5kUQHvgiDRaBpkg 5h0NbYPHpbNtxSm4xDMN3SEaXgsSozWe665RUNPXyeXk2BoN8F7IGlXNKCv6RcF5pgcM JxN8c0aP0eNLTt9kD0bv/eWP/lFQkg7KOvBp8QmTvexZyjVw4K1kvcscG+c1ldqNTy2C zj81Sdz01DsGd7G4NBG2MaFwDEoGoc8jz4fB45mpMZXL7yekH09Wd8LKEAvnDHd5e2vr KZdeb80Hr0+Gu4P5ieoCzu/2Tk6MT/INk8TGJKUn7oYS/xMTMKSXPxh6uY2j40PVb7E5 ow==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by rn-mailsvcp-ppex-lapp24.rno.apple.com with ESMTP id 3dj3dnmksh-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 14 Jan 2022 09:21:09 -0800
Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPS id <0R5P00T36MV7Q460@rn-mailsvcp-mta-lapp03.rno.apple.com>; Fri, 14 Jan 2022 09:21:07 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) id <0R5P00200MQD7900@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Fri, 14 Jan 2022 09:21:07 -0800 (PST)
X-Va-A:
X-Va-T-CD: 7c41845d202abaa5133654699ccc487a
X-Va-E-CD: 12ba1a2d20db0624daa835f99f0b9bb2
X-Va-R-CD: 3bcea838d83eb9e5d3633bbfbf32c1cc
X-Va-CD: 0
X-Va-ID: 48cdef17-85b7-4007-8d7e-e41c5f37adc6
X-V-A:
X-V-T-CD: 7c41845d202abaa5133654699ccc487a
X-V-E-CD: 12ba1a2d20db0624daa835f99f0b9bb2
X-V-R-CD: 3bcea838d83eb9e5d3633bbfbf32c1cc
X-V-CD: 0
X-V-ID: db6fca3c-01a6-4ae7-adb2-d17ea5c2ec57
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-01-14_06:2022-01-14, 2022-01-14 signatures=0
Received: from smtpclient.apple (unknown [17.11.50.36]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPSA id <0R5P00ND2MV6AC00@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Fri, 14 Jan 2022 09:21:07 -0800 (PST)
Content-type: multipart/alternative; boundary="Apple-Mail-CDF13058-01C7-4F0E-8834-18C48E06F6D8"
Content-transfer-encoding: 7bit
From: Tommy Pauly <tpauly@apple.com>
MIME-version: 1.0 (1.0)
Subject: Re: Call for adoption: Multipath Extension for QUIC
Date: Fri, 14 Jan 2022 09:21:06 -0800
Message-id: <16F8352F-49B0-45C2-87CE-5217E1116EF0@apple.com>
References: <CALGR9ob_wKOwsVcXY8oVGjDpuMW6dhBBw5skSgiFLTrbskRaiw@mail.gmail.com>
Cc: QUIC WG <quic@ietf.org>, QUIC WG Chairs <quic-chairs@ietf.org>
In-reply-to: <CALGR9ob_wKOwsVcXY8oVGjDpuMW6dhBBw5skSgiFLTrbskRaiw@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
X-Mailer: iPhone Mail (19E201)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-01-14_06:2022-01-14, 2022-01-14 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PC3ISE2_7SDJ95uvLo-RvpoJwak>
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, 14 Jan 2022 17:21:15 -0000

This draft is a good starting point for multipath work, and it seems to be the right time to take on this work. I support adoption. 

Best,
Tommy

> On Jan 13, 2022, at 7:14 AM, Lucas Pardue <lucaspardue.24.7@gmail.com> wrote:
> 
> 
> Greeting QUIC WG members,
> 
> During IETF 113 Mirja presented [1] about the unified multipath QUIC proposal in draft-lmbdhk-quic-multipath [2]. There was a strong feeling in the room that this draft was a good basis for adoption into the QUIC WG. So we'd like to start an adoption call.
> 
> The adoption call will run for 2 weeks, ending on February 27 2021 (anywhere on earth). Please reply to this email with any comments.
> 
> As a reminder, the draft contains two approaches to using packet numbers. The feeling in the room at IETF 113 was that it is suitable to adopt the documents in this state and select a single approach as part of the regular consensus process.
> 
> Since this is a draft that unifies different proposals, the chairs are suggesting that should the WG agree to adopt draft-lmbdhk-quic-multipath, the current author group  be split into three editors (Mirja, Quentin, Yanmei) and three authors (Chrisian, Olivier, Yunfei).
> 
> Kinds regards,
> Matt & Lucas
> QUIC WG Chairs
> 
> 
> [1] - https://datatracker.ietf.org/doc/slides-112-quic-unified-multipath-quic-extension/
> [2] - https://datatracker.ietf.org/doc/draft-lmbdhk-quic-multipath/