Re: Consensus call for multipath QUIC explicit path IDs
Marten Seemann <martenseemann@gmail.com> Fri, 12 April 2024 17:45 UTC
Return-Path: <martenseemann@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 617A6C14F6B8; Fri, 12 Apr 2024 10:45:47 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 eYrIL5EslJ1H; Fri, 12 Apr 2024 10:45:46 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 954F5C14F6A9; Fri, 12 Apr 2024 10:45:46 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-56e136cbcecso1306033a12.3; Fri, 12 Apr 2024 10:45:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712943944; x=1713548744; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=32/Z6TyJpTLhiMpHWQL3Nm8Js10POe1WTSP3OfX552c=; b=hNcOW4/i2r4eIsKj5P4Qf8ypwitL5bql7JG8eFdCqPC1qwMH4UrhgLxPP+ie1nflz9 ujiFb3SDlo/sEj4sWXeItes24O9+zxAt4CwlSG7WgLAg3tXZ672OSOoWgrUYm4eY8gNA IY3p2JCEriEtRig71Aeu3waCf1dXMlNhil+nMyCu3rN27Wn7KrpLrb9KXpwWoe0oDS7B 8RTu3l5dKNx3F8YKJ8ot0vLT13cJnRPMZJhKiPxmDr0XZt3POJ98r4+FVyROzodDclMB bSk7Q7Yg/GT37EPJVhe2e5jbJLznNz9kSXWlQ3LdhyTMYMuqzNN+zI/zMNWnAxlCl8s9 DgkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712943944; x=1713548744; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=32/Z6TyJpTLhiMpHWQL3Nm8Js10POe1WTSP3OfX552c=; b=mD9SylcVXRxqZ6Qo5ucdEKZAZCVstCB+BWFJB1QoVLHbFKHdqgRPq/4niDGyZOfUAm rX3gUMmKqox+vG2RBciVRFnFRzczs4iEZEx9A5F9sYF87myXdOAukFSksZP1MoW8hfzy f6u3pF+hEszLHwew6uYAa8UjFS7/r2G9tVOq5IpkyVz8+lB+uHY1tlTphGlOvlGY43tV by8gm0iFHuaoF4Sd335K6PIseC+Jp7bux5N+rxOr/x1ebkY9y4kOf3xFq5ERRTR8FBkV zjMKuNSE3NiFmDyGcc+/rI68cIBORPRYUz8Ogenhl1boHOflv/UfZjabOVWak5Gfh6+u Rvcw==
X-Forwarded-Encrypted: i=1; AJvYcCWNI3R2jGBMSBo/dqw+stS9k/TSxga+jl+Glw7tqd+OQgkY99enAq1EEdneY3iBkoB2G3PLL7A5CwLFlqAs2znDKNU12w==
X-Gm-Message-State: AOJu0Yx0QuZe/orvZ8QyAMgQWkKtrd0I6/vOCzicicyySE06djMZJ56B Pdsc1f3wkruenDvu0TyRfgHZLQ/okxwsE4mlbxu+OgWeCDK2En2AIz2tOHhHpOpYYhgC+hbFniy XLDL/5Wu3RUBpPgNtWL9DmHPn5fr4lM1g
X-Google-Smtp-Source: AGHT+IHwWCxpkjpFrlat7podp9b+jlTxTdyDXtRe7GjcPutxnkWimqnQ145XtGFzAuleL4v+Uv8wZFRXXAMk+PevNqg=
X-Received: by 2002:a17:906:4f09:b0:a4e:9e78:ac92 with SMTP id t9-20020a1709064f0900b00a4e9e78ac92mr2408112eju.36.1712943944150; Fri, 12 Apr 2024 10:45:44 -0700 (PDT)
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>
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:45:47 -0000
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