[multipathtcp] RFC 8684 on TCP Extensions for Multipath Operation with Multiple Addresses
rfc-editor@rfc-editor.org Tue, 31 March 2020 04:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD0CB3A1A97; Mon, 30 Mar 2020 21:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 dRlK3Uh-Qxcn; Mon, 30 Mar 2020 21:34:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9219A3A1A95; Mon, 30 Mar 2020 21:34:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A4F3FF406CD; Mon, 30 Mar 2020 21:34:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, multipathtcp@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200331043425.A4F3FF406CD@rfc-editor.org>
Date: Mon, 30 Mar 2020 21:34:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/7lYkJ6qASRz4n0ivSbqF6O07HI0>
Subject: [multipathtcp] RFC 8684 on TCP Extensions for Multipath Operation with Multiple Addresses
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 04:34:30 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8684 Title: TCP Extensions for Multipath Operation with Multiple Addresses Author: A. Ford, C. Raiciu, M. Handley, O. Bonaventure, C. Paasch Status: Standards Track Stream: IETF Date: March 2020 Mailbox: alan.ford@gmail.com, costin.raiciu@cs.pub.ro, m.handley@cs.ucl.ac.uk, olivier.bonaventure@uclouvain.be, cpaasch@apple.com Pages: 68 Obsoletes: RFC 6824 I-D Tag: draft-ietf-mptcp-rfc6824bis-18.txt URL: https://www.rfc-editor.org/info/rfc8684 DOI: 10.17487/RFC8684 TCP/IP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of these multiple paths for a TCP/IP session would improve resource usage within the network and thus improve user experience through higher throughput and improved resilience to network failure. Multipath TCP provides the ability to simultaneously use multiple paths between peers. This document presents a set of extensions to traditional TCP to support multipath operation. The protocol offers the same type of service to applications as TCP (i.e., a reliable bytestream), and it provides the components necessary to establish and use multiple TCP flows across potentially disjoint paths. This document specifies v1 of Multipath TCP, obsoleting v0 as specified in RFC 6824, through clarifications and modifications primarily driven by deployment experience. This document is a product of the Multipath TCP Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC