Re: Consensus call for multipath QUIC explicit path IDs

Marten Seemann <martenseemann@gmail.com> Fri, 12 April 2024 17:45 UTC

MIME-Version: 1.0
References: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com>
In-Reply-To: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Fri, 12 Apr 2024 13:45:31 -0400
Message-ID: <CAOYVs2rMfDLzaVT9re0T-mCHvrqCh9Yx6OdPgmXb+1P-NmMkkw@mail.gmail.com>
Subject: Re: Consensus call for multipath QUIC explicit path IDs
To: Lucas Pardue <lucas@lucaspardue.com>
Cc: quic@ietf.org, QUIC WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004fb59d0615e9d75a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/N79WILgkPmri54cvV-8d1aBMvqo>
Precedence: list

Perhaps unsurprisingly, I support the move to explicit path IDs.

On Fri, 12 Apr 2024 at 13:32, Lucas Pardue <lucas@lucaspardue.com> 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