Fw: New Version Notification for draft-ietf-quic-multipath-06.txt
Yanmei Liu <miaoji.lym@alibaba-inc.com> Mon, 23 October 2023 11: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 CDBB4C151080 for <quic@ietfa.amsl.com>; Mon, 23 Oct 2023 04:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_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 wrs1ze2WgN_6 for <quic@ietfa.amsl.com>; Mon, 23 Oct 2023 04:52:21 -0700 (PDT)
Received: from out0-210.mail.aliyun.com (out0-210.mail.aliyun.com [140.205.0.210]) (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 1AD03C14CE54 for <quic@ietf.org>; Mon, 23 Oct 2023 04:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1698061938; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=TwHfyv0XmDyW5EAK8SJGVzZmlatvFML3SVkrUlxSxCw=; b=mKSpY0/xjsSHAphqnus2p7nBnqprwwyklfkbT1BcTPDhEJT0K5mgWbYryMRv3rRhIxbb+NhMpMBPyybiLQQp7xVyey7WYAuS0VzO48MdBzyZY0uEHMQ5jWzBTW62J/xI6uQrQB1ro03H10QXPwP6hr1hbcFmG/bwvC5yQe73zus=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R321e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=ay29a033018047203; MF=miaoji.lym@alibaba-inc.com; NM=1; PH=DW; RN=6; SR=0; TI=W4_0.2.3_v5ForWebDing_211749EA_1698061576878_o7001c33h;
Received: from WS-web (miaoji.lym@alibaba-inc.com[W4_0.2.3_v5ForWebDing_211749EA_1698061576878_o7001c33h]) at Mon, 23 Oct 2023 19:52:15 +0800
Date: Mon, 23 Oct 2023 19:52:15 +0800
From: Yanmei Liu <miaoji.lym@alibaba-inc.com>
To: quic <quic@ietf.org>
Cc: "yunfei.ma" <yunfei.ma@alibaba-inc.com>, Christian Huitema <huitema@huitema.net>, Quentin De Coninck <quentin.deconinck@uclouvain.be>, "Olivier.Bonaventure" <Olivier.Bonaventure@uclouvain.be>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, LIU Yanmei <miaoji.lym@taobao.com>
Reply-To: Yanmei Liu <miaoji.lym@alibaba-inc.com>
Message-ID: <970d6f60-8bcd-48e6-a135-ff5f64c0954b.miaoji.lym@alibaba-inc.com>
Subject: Fw: New Version Notification for draft-ietf-quic-multipath-06.txt
X-Mailer: [Alimail-Mailagent revision 23][W4_0.2.3][v5ForWebDing][Chrome]
MIME-Version: 1.0
References: <169804807116.13099.6161004600573784433@ietfa.amsl.com>
x-aliyun-mail-creator: W4_0.2.3_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzExNy4wLjAuMCBTYWZhcmkvNTM3LjM2La
In-Reply-To: <169804807116.13099.6161004600573784433@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_128072_7fe4e2e1d700_65365e6f_45aa93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/60-Dz9RjVyNuQ4FEvp-qTk1Q7vY>
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: Mon, 23 Oct 2023 11:52:25 -0000
Hi Everyone, We have just published -06 version for multipath quic extension: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ <https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ > 06 version includes several modifications: - (Most important) Split PATH_STATUS frame into 2 new frames: PATH_STANDBY and PATH_AVAILABLE frames, which take place of PATH_STATUS frame. The usage of PATH_STANDBY and PATH_AVAILABLE frames are the nearly same to the "standby" and "available" status of the PATH_STATUS frame in the previous version, and they share a common sequence number space. - Any frame can be sent on a new path at any time when the anti-amplification limits and the congestion control limits are respected. - Expand scenes in which client uses only one IP address and server listens on only one IP address either. As a path is determined by 4-tuple, endpoints could use different ports with the same IP address when using multi-path extension. Here’s a link to the diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-06 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-06 > Please feel free to discuss the new version! Best regards, The mpquic-authors group ------------------------------------------------------------------ From:internet-drafts <internet-drafts@ietf.org> Sent At:2023 Oct. 23 (Mon.) 16:01 To:LIU Yanmei <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-06.txt A new version of Internet-Draft draft-ietf-quic-multipath-06.txt has been successfully submitted by Yanmei Liu and posted to the IETF repository. Name: draft-ietf-quic-multipath Revision: 06 Title: Multipath Extension for QUIC Date: 2023-10-23 Group: quic Pages: 33 URL: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-06.txt <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-06.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-06.html <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-06.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-06 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-06 > 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/mirjak/draft-lmbdhk-quic-multipath <https://github.com/mirjak/draft-lmbdhk-quic-multipath >. The IETF Secretariat