RE: Call for adoption: Multipath Extension for QUIC

Florin Baboescu <florin.baboescu@broadcom.com> Tue, 25 January 2022 17:37 UTC

Return-Path: <florin.baboescu@broadcom.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 5FF133A067B for <quic@ietfa.amsl.com>; Tue, 25 Jan 2022 09:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.673
X-Spam-Level:
X-Spam-Status: No, score=-2.673 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rsLPgBd1t7F for <quic@ietfa.amsl.com>; Tue, 25 Jan 2022 09:37:10 -0800 (PST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD94F3A0A1F for <quic@ietf.org>; Tue, 25 Jan 2022 09:37:09 -0800 (PST)
Received: by mail-lj1-x22a.google.com with SMTP id c15so12137246ljf.11 for <quic@ietf.org>; Tue, 25 Jan 2022 09:37:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=UUoGGrou0bskLhnrJZ062hIIILGR1Wn0MT8hvwxZ/5M=; b=L7wvLFDoRuBMS6PsdQfpCwAVEfJ0YQRSQNe9w8jpEOPSkeo8kG0IpjYI6NlkQjZdLV ep+K2eT35/6E7Az4MAHNHAHLO2hSxLZyv+OEsKO5GS8TdLt/YJ+phZN2pDn1ExJWsWuB 73P4C+OpUvvs+yjRy98ENIwTBmxYcRdDEVq1o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=UUoGGrou0bskLhnrJZ062hIIILGR1Wn0MT8hvwxZ/5M=; b=Jv563BiUCgJ0CeSO2KKpVwkMlzlaE3jfuzxBDMGqmWPysXD/XCITdunV683Ym1DU4h QmIIV8Ihw4MjhDKKtyw+EFrWQKvh8McqVMUae5/g6EfNyFAcr08jSarnkoCXIVWyZH91 Mq5BJ67KmipAvIPQcEwR4DZkkV3vbcQnWPFAo4WLh1wOpJ3Ga55y0Rb7iEZAjd8bwegs tEjGKe/ZJsdM8ekGKWKcXqovAaYjuJJg1Y6Jk4978Xb7ev8/UiB3T0OiOrq+21elA2C2 69fmKdhsw2qHjOIn1w9iBzE7V3IIFpREZxmNwkMJV37bC0ki408PDusoqB8JGZD1n5T4 vB8w==
X-Gm-Message-State: AOAM533DQ+9b+tPTy1SAPiLqknQNaSDD5J1GobF5ClGZdo2Mq95U6VtS GlEVGg2b3rhms/QktoSJSOZtDnLjP9NFNW7RSKmH29LrK5WKMmuQqzWAXTgrebN5b1Ro9wIMFMM 8XlN3Nr5Ud7E=
X-Google-Smtp-Source: ABdhPJxDzrbWoz2vdbhEoAgrxKvVq5kPeYxjiNuKm5SpI4HqmrEE6vtBPSKDswgUxOaaTTxAjJDN6vk1qGjgX4UH6Tc=
X-Received: by 2002:a2e:7f06:: with SMTP id a6mr14843898ljd.102.1643132225028; Tue, 25 Jan 2022 09:37:05 -0800 (PST)
From: Florin Baboescu <florin.baboescu@broadcom.com>
References: <CALGR9ob_wKOwsVcXY8oVGjDpuMW6dhBBw5skSgiFLTrbskRaiw@mail.gmail.com>
In-Reply-To: <CALGR9ob_wKOwsVcXY8oVGjDpuMW6dhBBw5skSgiFLTrbskRaiw@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQEz5VQ2dWtgFaLvN7D/LKAEMyQpgq28WOgg
Date: Tue, 25 Jan 2022 09:37:03 -0800
Message-ID: <bfd8210709bfd6de509b9036e4ab4984@mail.gmail.com>
Subject: RE: Call for adoption: Multipath Extension for QUIC
To: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>
Cc: QUIC WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000009c813405d66b8860"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eA63ffC61abr25rYSA15u2yjiv8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Jan 2022 17:37:14 -0000

Dear all,



I also support the adoption of the proposed draft into the QUIC WG.  It
represents a good solid basis addressing various use cases.

Thank you.

-Florin Baboescu





*From:* QUIC [mailto:quic-bounces@ietf.org] *On Behalf Of *Lucas Pardue
*Sent:* Thursday, January 13, 2022 7:14 AM
*To:* QUIC WG <quic@ietf.org>
*Cc:* QUIC WG Chairs <quic-chairs@ietf.org>
*Subject:* Call for adoption: Multipath Extension for QUIC



Greeting QUIC WG members,



During IETF 113 Mirja presented [1] about the unified multipath QUIC
proposal in draft-lmbdhk-quic-multipath [2]. There was a strong feeling in
the room that this draft was a good basis for adoption into the QUIC WG. So
we'd like to start an adoption call.



The adoption call will run for 2 weeks, ending on February 27 2021
(anywhere on earth). Please reply to this email with any comments.



As a reminder, the draft contains two approaches to using packet numbers.
The feeling in the room at IETF 113 was that it is suitable to adopt the
documents in this state and select a single approach as part of the regular
consensus process.



Since this is a draft that unifies different proposals, the chairs are
suggesting that should the WG agree to adopt draft-lmbdhk-quic-multipath,
the current author group be split into three editors (Mirja, Quentin,
Yanmei) and three authors (Chrisian, Olivier, Yunfei).



Kinds regards,

Matt & Lucas

QUIC WG Chairs



[1] -
https://datatracker.ietf.org/doc/slides-112-quic-unified-multipath-quic-extension/

[2] - https://datatracker.ietf.org/doc/draft-lmbdhk-quic-multipath/

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.