Fwd: New Version Notification for draft-ietf-quic-multipath-09.txt
Yanmei Liu <miaoji.lym@alibaba-inc.com> Fri, 21 June 2024 16:52 UTC
Return-Path: <miaoji.lym@alibaba-inc.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 AA2CCC18DBB8 for <quic@ietfa.amsl.com>; Fri, 21 Jun 2024 09:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 (1024-bit key) header.d=alibaba-inc.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 laZ0ZWDN_uJw for <quic@ietfa.amsl.com>; Fri, 21 Jun 2024 09:52:47 -0700 (PDT)
Received: from out0-194.mail.aliyun.com (out0-194.mail.aliyun.com [140.205.0.194]) (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 428F9C14F5EF for <quic@ietf.org>; Fri, 21 Jun 2024 09:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1718988763; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=r8XHJpGF7rry7YWr+S916BB+Y9nAQgL43MJqnIvf0jM=; b=tRt8UH1mVuz4QP7Gm17J2Ou7K2mwEHq9og/Nxfy/eZqOpYnZrqURIq6fZB++BIkZFT6LrRLomyS2HkOPCkQ599rBIxEET/HCGviKc6DMoVl9ttaqFFQB6cisebGY0yuM5ut21u28yjbFfz3aTAjCbn7rQMTAfLbchhLKXX+QlhQ=
X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R141e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=maildocker-contentspam033068221070;MF=miaoji.lym@alibaba-inc.com;NM=1;PH=DW;RN=1;SR=0;TI=W4_0.2.3_v5ForWebDing_2144B8F6_1718987986019_o7001c106n;
Received: from WS-web (miaoji.lym@alibaba-inc.com[W4_0.2.3_v5ForWebDing_2144B8F6_1718987986019_o7001c106n]) at Sat, 22 Jun 2024 00:52:42 +0800
Date: Sat, 22 Jun 2024 00:52:42 +0800
From: Yanmei Liu <miaoji.lym@alibaba-inc.com>
To: quic <quic@ietf.org>
Message-ID: <34361e63-56f6-4692-a4f7-64fa28640d95.miaoji.lym@alibaba-inc.com>
Subject: Fwd: New Version Notification for draft-ietf-quic-multipath-09.txt
X-Mailer: [Alimail-Mailagent][W4_0.2.3][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-im-through: {"mailThroughImNew":true}
References: <171898556865.108471.15382531563980982862@dt-datatracker-6cc478f489-rscq2>
x-aliyun-mail-creator: W4_0.2.3_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzEyNS4wLjAuMCBTYWZhcmkvNTM3LjM2La
In-Reply-To: <171898556865.108471.15382531563980982862@dt-datatracker-6cc478f489-rscq2>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_1729_7f0457249700_6675afda_77155d"
Message-ID-Hash: 2RLPEQ6JSEPJDQFXUOMTW6THTIFVFXW2
X-Message-ID-Hash: 2RLPEQ6JSEPJDQFXUOMTW6THTIFVFXW2
X-MailFrom: miaoji.lym@alibaba-inc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Reply-To: Yanmei Liu <miaoji.lym@alibaba-inc.com>
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0TJHMc4mMxc4g444vcPr_AWD7Wg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>
Hi Everyone, We submitted a new draft version -09 for multipath extension. This version contains several modifications: - The transport parameter previously known as 'initial_max_paths' has been renamed to 'initial_max_path_id' (the updated value 0x0f739bbc1b666d09), containing the max path id instead of path count; also change the MAX_PATH_ID frame for the same semantics - Rewrite the Path Closure section: Endpoints send PATH_ABANDON frames in each scenes as an explicit signal for path closure, and endpoints don’t necessarily need to send MP_RETIRE_CID for CIDs belonging to the closing path. - Recommendations regarding Path ID continuity - Editorial Changes: reconstruct of the high level introduction and acknowledgement sending subsection, also rewrite the examples of path initiation and path closure - First update for Security Consideration Section The diff link between -08 and -09: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-09 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-09 > The semantics change are all from the consensus of last intern meeting. Please have a look and let us know if you have suggestions! Best Regards, Yanmei ------------------------------------------------------------------ 发件人：internet-drafts <internet-drafts@ietf.org> 发送时间：2024年6月21日(星期五) 23:59 收件人："刘彦梅"<miaoji.lym@alibaba-inc.com>; "马云飞"<yunfei.ma@uber.com>; Christian Huitema<huitema@huitema.net>; Mirja Kuehlewind<mirja.kuehlewind@ericsson.com>; Olivier Bonaventure<Olivier.Bonaventure@uclouvain.be>; Quentin De Coninck<quentin.deconinck@umons.ac.be>; "quic-chairs"<quic-chairs@ietf.org> 主 题：New Version Notification for draft-ietf-quic-multipath-09.txt A new version of Internet-Draft draft-ietf-quic-multipath-09.txt has been successfully submitted by Mirja Kühlewind and posted to the IETF repository. Name: draft-ietf-quic-multipath Revision: 09 Title: Multipath Extension for QUIC Date: 2024-06-21 Group: quic Pages: 34 URL: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-09.txt <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-09.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ <https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ > HTML: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-09.html <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-09.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath <https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath > Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-09 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-09 > 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/ <https://mailarchive.ietf.org/arch/browse/quic/ >. Source for this draft and an issue tracker can be found at https://github.com/quicwg/multipath <https://github.com/quicwg/multipath >. The IETF Secretariat