Re: Consensus call for multipath QUIC explicit path IDs
Lucas Pardue <lucas@lucaspardue.com> Mon, 22 April 2024 18:00 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 C6168C17C8B3; Mon, 22 Apr 2024 11:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_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="VCvFYFg6"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="aHVuvzYx"
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 acXWJF339TSu; Mon, 22 Apr 2024 11:00:41 -0700 (PDT)
Received: from wfout7-smtp.messagingengine.com (wfout7-smtp.messagingengine.com [64.147.123.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B094DC17C8A2; Mon, 22 Apr 2024 11:00:41 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfout.west.internal (Postfix) with ESMTP id B110A1C00161; Mon, 22 Apr 2024 14:00:40 -0400 (EDT)
Received: from imap53 ([10.202.2.103]) by compute3.internal (MEProxy); Mon, 22 Apr 2024 14:00:40 -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:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=fm1; t=1713808840; x= 1713895240; bh=3EDgaKbgRht0yakYwQOpFOAUTjAA9Xqq7JWlQZqSAEA=; b=V CvFYFg6koRrXjAlQVNjBEkw61XJ82BRl+24jsxnZUzwfSoUkFnLk9XFxADhInltZ AbW0cti3wvLfH6IHGRP2chyUirwcQ2hzE1gveh4bKu7CaixHiGYtTfcEnCDC2vfd XAZY6d6a4iwiyC8F4xptip5O/Ld3k9c7ahOQBJm0jcT+Ek1qxAYmYVar9X5HAPXW 44htcp53RKDxLyTgiEjN4wuoV9mPCi/ppyEOaK0FosH5FHAFFhnbn6i+WzWIYO+1 es1jSVFX7S4WqDxJ8CzwwV2euYcSPLhyrxtOzD4Lxau/B82qpqvuA2QhbM+BGI3n RzY9VpOEnOKmscMvcxUEg==
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:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1713808840; x=1713895240; bh=3EDgaKbgRht0yakYwQOpFOAUTjAA 9Xqq7JWlQZqSAEA=; b=aHVuvzYxEiae7ps9tt/hTL0BU/PJUsEDwdQFaXAaCTS1 yps4SFZr46cUM/QWlvd8W8ZGyyLqYZEXRxLPEr8m6DPn8Arg5SX8DPBVLwd27P3k y7xN0ICjysJQjar0pW0URYmloKxPUsc0OlvhKHB4rRoNYFhd7Zx/MW/btCurc4lF vNmNZVNmdIaCsKBZJYl5UKQVXqqNPormb2diXGPhHs74DOG/kZ7utm9McMslqiZy 7inq6nGKvnHRbjObPxrXwTzkEqVxNKlR/jO5nzC9Gp8POyBqeVLQl3TazDDuatIq P9dcI1FVl6dpwpqmVb5EaOKqXNliShPw05i+Pet1hA==
X-ME-Sender: <xms:x6UmZgQaTiVMIJyDx7dusKUrNkn9-SXx9PVcMBECL1wADVEnkIVorQ> <xme:x6UmZtzHRslCcjJz3ZQJ_ULSkFZvjlfBhumBbQPJsx-a7GQ5bx3_Lc61WQHkAi3yt G7usblgkWed8bzu9M4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudekledguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvvefutgesrgdtreerreerjeenucfhrhhomhepfdfn uhgtrghsucfrrghrughuvgdfuceolhhutggrsheslhhutggrshhprghrughuvgdrtghomh eqnecuggftrfgrthhtvghrnhepkeekkeevlefhfeeghfdtfeehvdeftdefkefhffeiieeh ffdtteehtefgtdehlefhnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrd horhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep lhhutggrsheslhhutggrshhprghrughuvgdrtghomh
X-ME-Proxy: <xmx:x6UmZt0Y40izyX7dgKyDb2mPN0UMl5Qv4iU1_kLLe6_21UiIzYnzuA> <xmx:x6UmZkCQp-e_LaaXIRQfcNHJrd8A4cT2jZuo5qMS2OibMwq3qYTm9w> <xmx:x6UmZpivNeXfw5PXxdrBQgmu6Z_MhMiaL3ysLGvC_Va9jSV8bPo3EA> <xmx:x6UmZgrwpAQgKkIwGLLlZj1PVkqQue1i6SChkWD0746xBdgxtDHpdg> <xmx:yKUmZpZjyKNr5WudLn-u8PbOHXuMuQ1M7vm7mp78qd3FaGVSqY284-1x>
Feedback-ID: i23b94938:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C434B3640070; Mon, 22 Apr 2024 14:00:39 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-386-g4cb8e397f9-fm-20240415.001-g4cb8e397
MIME-Version: 1.0
Message-Id: <fb4f4111-09ab-4874-80c1-be290de18fd9@app.fastmail.com>
In-Reply-To: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com>
References: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com>
Date: Mon, 22 Apr 2024 19:00:15 +0100
From: Lucas Pardue <lucas@lucaspardue.com>
To: quic@ietf.org
Cc: QUIC WG Chairs <quic-chairs@ietf.org>
Subject: Re: Consensus call for multipath QUIC explicit path IDs
Content-Type: multipart/alternative; boundary="1b11dae974dd49358efee5afde3ad43f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LKoIAdfqJtm6i3J11w822gni16Y>
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: Mon, 22 Apr 2024 18:00:47 -0000
Thanks for all the responses. Consensus is declared. Cheers Lucas & Matt QUIC WG Chairs On Fri, Apr 12, 2024, at 18:24, Lucas Pardue wrote: > 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 > > > >
- Consensus call for multipath QUIC explicit path I… Lucas Pardue
- Re: Consensus call for multipath QUIC explicit pa… Marten Seemann
- Re: Consensus call for multipath QUIC explicit pa… Tommy Pauly
- Re: Consensus call for multipath QUIC explicit pa… Mikkel Fahnøe Jørgensen
- Re: Consensus call for multipath QUIC explicit pa… Michael Eriksson
- Re: Consensus call for multipath QUIC explicit pa… Lucas Pardue