Re: Consensus call for multipath QUIC explicit path IDs

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Sat, 13 April 2024 06:47 UTC

Return-Path: <mikkelfj@gmail.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 3DB2CC14F68B; Fri, 12 Apr 2024 23:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rnCHdTVd3Rui; Fri, 12 Apr 2024 23:47:40 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 CC65FC14CEE4; Fri, 12 Apr 2024 23:47:40 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a46de423039so91736166b.0; Fri, 12 Apr 2024 23:47:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712990858; x=1713595658; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=jiKCrdpOH33XSFG3qXh62qm/2mMFXgpprYY2zz7M1UM=; b=nsLKxc/a+M7SSH45ZSydGbqDlxAhfAnIEUWucy1EJYNoNPs1NIPc+rAuP/G7d6CywH 59vjCC+tEVcKZwc7SM6XRT1maz1x9z4tiApMf0KuzJ7VXFzhf1/U1TLMGWlVmSxvEiTk 0mzuLCTWuPXGpmwg7UiQgdIBHFPXmbESgrWZ25v5E4Ikz8fwejPW1uL36g1ybcMuDTe4 EDpbMv082t1+LvMWrs796H1Yi+5c2GBpLSbmtFlT71feOiMIE7csjAMcu573k3ey9XRk NzvDLczZjFjM3S5y9LqCeik8U8gB6iJu0VsYUJeAvmm08d9GyZyLxXUhVtpOqef/Ir89 wF+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712990858; x=1713595658; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jiKCrdpOH33XSFG3qXh62qm/2mMFXgpprYY2zz7M1UM=; b=IiH8PqbzRSqZ2NI9OpWm54WggKYe8ZVcLDuHvMsVhwPGSfZT81pzoATvXYYv8ppEGG zd1ruMctKkQWbF/F3zvgTkA1MW6OrNDS/WU7WqlsLdmzFUvDIHpc5B050ssGD2z/5hS9 7tmiNRPutvD89UoFPMYVFw4U8QrUWSuXMzfMoh4KMtd4bvbecAcbrIqLWHyf7WlAnZQX 0qgPTVE4nWf8E0Ga2tre+JlDTdEzLmgDXwRrRpy6wJiCuG1Y+MIGTey7S+hWGVeQ+vYi +L8SxHW0YqBZssqwNaSgAviSMdrJ6VaqrCf0cWD29RYiI3e/nz0JVLfbf35JWHfBDTlS 66ig==
X-Forwarded-Encrypted: i=1; AJvYcCWTNFtFRVxHRgiK6T5IpcAcnFteNQ9YAsMp6PLi9MO9tN/nICpGZXyBmp9pp5xUUyjHV7db7RILSuLOofMXIJf8W7l5//diBc0sxggYrXhKZ2WYNA==
X-Gm-Message-State: AOJu0Yye0WpEPz5IXDgNImsUs8G5R4he6lEaZAldt3PvvmKpMVtSTSXM ssErFgI9bDGbocC61n5yw/9Z6yDKdU4X0PSvioFIkBKKLloYPF2F
X-Google-Smtp-Source: AGHT+IFsIqyvm15AMsQ/685el9MUofDsblC6cC1w7NnC5fx47a5mExjOvPI8apqaPYYX1GvqNa0tDQ==
X-Received: by 2002:a50:8e5d:0:b0:56e:2cb6:480e with SMTP id 29-20020a508e5d000000b0056e2cb6480emr3752716edx.38.1712990857637; Fri, 12 Apr 2024 23:47:37 -0700 (PDT)
Received: from smtpclient.apple ([87.72.40.193]) by smtp.gmail.com with ESMTPSA id i41-20020a0564020f2900b0057002563103sm1006765eda.54.2024.04.12.23.47.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2024 23:47:36 -0700 (PDT)
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Message-Id: <38398579-7FC3-4F41-88DC-2AB5699276AA@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7E0FBF57-37AE-40DE-81A2-D6F83967FF7E"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: Consensus call for multipath QUIC explicit path IDs
Date: Sat, 13 Apr 2024 08:47:25 +0200
In-Reply-To: <C0E18A64-B3CE-4158-9478-26B519C2556C@apple.com>
Cc: Marten Seemann <martenseemann@gmail.com>, Lucas Pardue <lucas@lucaspardue.com>, IETF QUIC WG <quic@ietf.org>, QUIC WG Chairs <quic-chairs@ietf.org>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
References: <d9da0101-f371-47bb-abef-c2cd516f58c3@app.fastmail.com> <CAOYVs2rMfDLzaVT9re0T-mCHvrqCh9Yx6OdPgmXb+1P-NmMkkw@mail.gmail.com> <C0E18A64-B3CE-4158-9478-26B519C2556C@apple.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cURnbpdsOCfTaORh455WkNabKKI>
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: Sat, 13 Apr 2024 06:47:45 -0000

I haven’t been following QUIC development closely recently, but I am happy to see multi-path  with separate package number spaces and separate path IDs.

Mikkel

> On 13 Apr 2024, at 04.29, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> wrote:
> 
> Yes, let’s go ahead with this (explicit) path.
> 
> Tommy
> 
>> On Apr 12, 2024, at 10:45 AM, Marten Seemann <martenseemann@gmail.com> wrote:
>> 
>> Perhaps unsurprisingly, I support the move to explicit path IDs.
>> 
>> On Fri, 12 Apr 2024 at 13:32, Lucas Pardue <lucas@lucaspardue.com <mailto: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 <mailto:internet-drafts@ietf.org>
>>> To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
>>> Cc: quic@ietf.org <mailto: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 <mailto: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
>>> 
>>> 
>>> 
>>> 
>