IETF Logo Mail Archive

Consensus call for multipath QUIC explicit path IDs

Lucas Pardue <lucas@lucaspardue.com> Fri, 12 April 2024 17:25 UTC

Return-Path: <lucas@lucaspardue.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 7C689C14F708; Fri, 12 Apr 2024 10:25:50 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lucaspardue.com header.b="Pf/r6Y83"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="S8ZFIWX2"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpUwgsWpHYnX; Fri, 12 Apr 2024 10:25:46 -0700 (PDT)
Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE165C14F74E; Fri, 12 Apr 2024 10:24:57 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfout.nyi.internal (Postfix) with ESMTP id 43EF4138027A; Fri, 12 Apr 2024 13:24:57 -0400 (EDT)
Received: from imap53 ([10.202.2.103]) by compute3.internal (MEProxy); Fri, 12 Apr 2024 13:24:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucaspardue.com; h=cc:cc:content-type:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to; s=fm1; t=1712942697; x=1713029097; bh=M8KyjLTmFzw/8Rk6LNYBH 3JbdWUvzEQJwSlwZEn3D74=; b=Pf/r6Y83UIWiUYkNc26sGdVkeT4tvc4fhc70B 2Dcpl3f0jyj1okVRDm27EeYTr5HN2l11hUug8jFj+xWQlHUCJ17z+jEZHylxZZ69 GcriBwMMCPQmUsFM9qizHh+P1K12EHaD8m6awazum47bjFW9w2m5m+Dt77e1Z/C+ 7nQpcbPLn5hcEwzDVzQuMbB5JSCjoyc/LdJt2szkX6n8tP9+ybmrppXjRwK1VG3t 19MYHnIdCLBSBX4ul7jlMoS/QNZfWGZwoOrrVTjtKQjODpIW8K9O71KGWpmluWQp uKjiOJDrAGozSOfFbYb8PAb/JK6X16qJ1t2ChTPuOcIMRKpBQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1712942697; x=1713029097; bh=M8KyjLTmFzw/8Rk6LNYBH3JbdWUvzEQJwSl wZEn3D74=; b=S8ZFIWX2hTj1NRGbxS7ZIpHxVXg208L//RFwFN6c5kQl7n9LUnJ 33exOO0n30fA+FA6bf1kmJGYaTGY0HQIR4yI7Nm26Phu45OHGL29MGJ8dshcxEqj KlfIF8MncvK4uWYr7bw2/OLmlcma6yx7oBJ+MnRhjSmuDyLmiZNl0Z3cEnRU+SkM uGmYgIt/U397bwi1ujnPcSWq/1MKIuRy6ONEYOF+Fdy8YYJXF+zNGCSVBP4szWpO JrjBGX/K3Qfp/F1e+kwgR7poA+He4isMLdEEDKtwqgociQ8cO1tuNB/88/0/dQZr Q0FpS73QbtHjwaMUbnoCBYFR7t8MI5ifCgw==
X-ME-Sender: <xms:aW4ZZvawTtVM0ezp2W9hhYZ6LbVWp55mb8uhPq9SD-2PAL0ShDGafA> <xme:aW4ZZuZ4PETtGQGHgcIURPJGB3p5HsNlKuvoGq0mTHawyxYaurR9hw57sBNS7Q9qT oM976wmFiSyesx7LeI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeiuddguddufecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfffhffvvefutgesrgdtreerreerjeenucfhrhhomhepfdfnuhgt rghsucfrrghrughuvgdfuceolhhutggrsheslhhutggrshhprghrughuvgdrtghomheqne cuggftrfgrthhtvghrnhepieevgfdthfehhffgfeetveffkedtuddvueeggeeuuddvudev fedtgefgfeefffehnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheplhhu tggrsheslhhutggrshhprghrughuvgdrtghomh
X-ME-Proxy: <xmx:aW4ZZh92xkHuuKFAb7t6eCPQjfEhap49_-Hx-6POiTn5p-OnySZ_Qg> <xmx:aW4ZZlqRF1um9MaV6s0vzzRPM1eZYl9N3g1kcJX9Ifa8bFh6GBoxzQ> <xmx:aW4ZZqqD2zy0DAEqkmNoZZl6ZpQfxpVcNtYkkXFJdLIbU72-y6IqqA> <xmx:aW4ZZrRnYG_HVOMAKF9TQCI-c7aOrwXWH8hU4osFNSYeS7duKVrqVQ> <xmx:aW4ZZvCtqWT_eP9xT9i-l6Do7fta6ePDUuXBZVc2-78yxVthmRNZw_vX>
Feedback-ID: i23b94938:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F1CBD3640070; Fri, 12 Apr 2024 13:24:56 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-379-gabd37849b7-fm-20240408.001-gabd37849
MIME-Version: 1.0
x-forwarded-message-id: <171280534449.60487.1848846324639002267@ietfa.amsl.com>
Message-Id: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com>
Date: Fri, 12 Apr 2024 18:24:31 +0100
From: Lucas Pardue <lucas@lucaspardue.com>
To: quic@ietf.org
Cc: QUIC WG Chairs <quic-chairs@ietf.org>
Subject: Consensus call for multipath QUIC explicit path IDs
Content-Type: multipart/alternative; boundary="e3bf6867b852461da3167fa6d2c49c52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AWqUO3ct-I3YxEHybFKAAaufGjA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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, 12 Apr 2024 17:25:50 -0000

Hi folks,

We saw extensive discussions about the use of explicit path IDs for Multipath over the last few months. At IETF 119, in the room there was strong support for merging PR 292 [1] into the document.

The chairs noted that we would direct the authors to move forward with merging unless objections were raised on the list. None have been seen, hence the change has been been merged and a new draft published (see below). This unblocked progress on a number of follow on design items now being actively worked on, see the issues on the repo.

The chairs would like to take one last opportunity to confirm consensus before drawing a line on this design choice. The email initates a 1-week consensus call for explicit path IDs [1], ending at end of day April 19 anywhere on earth.

Cheers
Lucas & Matt 
QUIC WG Chairs

[1] - https://github.com/quicwg/multipath/pull/292

----- Original message -----
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-multipath-07.txt
Date: Thursday, April 11, 2024 04:15

Internet-Draft draft-ietf-quic-multipath-07.txt is now available. It is a work
item of the QUIC (QUIC) WG of the IETF.

   Title:   Multipath Extension for QUIC
   Authors: 刘彦梅
            马云飞
            Quentin De Coninck
            Olivier Bonaventure
            Christian Huitema
            Mirja Kuehlewind
   Name:    draft-ietf-quic-multipath-07.txt
   Pages:   38
   Dates:   2024-04-10

Abstract:

   This document specifies a multipath extension for the QUIC protocol
   to enable the simultaneous usage of multiple paths for a single
   connection.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the QUIC Working Group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/quic/.

   Source for this draft and an issue tracker can be found at
   https://github.com/mirjak/draft-lmbdhk-quic-multipath.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-quic-multipath-07.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-07

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

v2.23.0 | Report a Bug | By Email