Fw: New Version Notification for draft-ietf-quic-multipath-11.txt
Yanmei Liu <miaoji.lym@alibaba-inc.com> Tue, 22 October 2024 09:38 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 56990C14F5FE for <quic@ietfa.amsl.com>; Tue, 22 Oct 2024 02:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.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_BLOCKED=0.001, 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_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 i666T2Pf6xav for <quic@ietfa.amsl.com>; Tue, 22 Oct 2024 02:38:55 -0700 (PDT)
Received: from out0-213.mail.aliyun.com (out0-213.mail.aliyun.com [140.205.0.213]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F7F1C151998 for <quic@ietf.org>; Tue, 22 Oct 2024 02:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1729589931; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=WiGt9tte4rIXS2+iohKXPo8jA8L/VMqy5QtsCorYmFo=; b=s9SZUOpd2Upknq0x9sUSDHxk494HbjNQCfWBOdLKDQEsLmQvbYTrZAqzhT0pSNcD+dWGepk04L99yJXCewUv2geZYJ38GFbXZMFnArU1tghlLd8mLUaV+e2yk0LuIXQU0P0Z5GsMv/e4gcC6pmqWbamZlqJb5IBuuBjfsKrCGm0=
X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R111e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=maildocker-contentspam033037219169;MF=miaoji.lym@alibaba-inc.com;NM=1;PH=DW;RN=5;SR=0;TI=W4_0.2.3_v5ForWebDing_21260AEB_1729587925469_o7001c67m;
Received: from WS-web (miaoji.lym@alibaba-inc.com[W4_0.2.3_v5ForWebDing_21260AEB_1729587925469_o7001c67m] cluster:ay29) at Tue, 22 Oct 2024 17:38:50 +0800
Date: Tue, 22 Oct 2024 17:38:50 +0800
From: Yanmei Liu <miaoji.lym@alibaba-inc.com>
To: quic <quic@ietf.org>, Christian Huitema <huitema@huitema.net>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, "Ma, Yunfei" <yunfei.ma@alibaba-inc.com>, Quentin De Coninck <quentin.deconinck@uclouvain.be>, "Olivier.Bonaventure" <Olivier.Bonaventure@uclouvain.be>
Message-ID: <13a062c8-5e29-4f30-b8df-decb8d6db9b9.miaoji.lym@alibaba-inc.com>
Subject: Fw: New Version Notification for draft-ietf-quic-multipath-11.txt
X-Mailer: [Alimail-Mailagent revision 6][W4_0.2.3][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-im-through: {"version":"v1.0"}
References: <172952835919.1992747.15841170161247511097@dt-datatracker-78dc5ccf94-w8wgc>
x-aliyun-mail-creator: W4_0.2.3_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzEyOS4wLjAuMCBTYWZhcmkvNTM3LjM2La
In-Reply-To: <172952835919.1992747.15841170161247511097@dt-datatracker-78dc5ccf94-w8wgc>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_1751_7fe0681ce700_671772aa_3556b"
Message-ID-Hash: 3ZVWYNUPT4VIHK6S5KB2AZBBYHNGX7FI
X-Message-ID-Hash: 3ZVWYNUPT4VIHK6S5KB2AZBBYHNGX7FI
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.9rc6
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/byuMGyuBsrTHlOvQWyWzhgsqRfo>
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 -11 for multipath extension: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ <https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ > This version contains several modifications: 1. Add more guidance on using multiple paths with the same 4-tuple 2. Editorial changes on renaming frames, such as replacing MP_ACK with PATH_ACK, replace MP_NEW_CONNECTION_ID frame with PATH_NEW_CONNECTION_ID frame, and replace MP_RETIRE_CONNECTION_ID frame with PATH_RETIRE_CONNECTION_ID frame 3. Replace PATH_STANDBY frame with PATH_BACKUP frame 4. Add PATHS_BLOCKED frame to tell the peer that the maximum path identifier limit is reached 5. Re-define the Error Code field of PATH_ABANDON frame, and delete the Reason Phrase field 6. Claim that Connection ID sequence number space starts at 0 for all paths 7. Allow endpoints to send packets without challenge if the 4-tuple address has already been validated 8. Add more implementation comments for key rotation, more guidance on when to use PATH_ACK frames The diff link between -10 and -11: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-11 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-11 > Please have a look and feel free to share ideas! Best Regards, Yanmei ------------------------------------------------------------------ From:internet-drafts <internet-drafts@ietf.org> Send Time:2024 Oct. 22 (Tue.) 00:32 To:"刘彦梅(喵吉)"<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> Subject:New Version Notification for draft-ietf-quic-multipath-11.txt A new version of Internet-Draft draft-ietf-quic-multipath-11.txt has been successfully submitted by Mirja Kühlewind and posted to the IETF repository. Name: draft-ietf-quic-multipath Revision: 11 Title: Multipath Extension for QUIC Date: 2024-10-21 Group: quic Pages: 38 URL: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-11.txt <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-11.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-11.html <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-11.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-11 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-11 > 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