![]() Utilisation and resilience to a subset of node failures. Making use of multiple paths is beneficial, improving resource These paths need not be entirely disjoint: they may To simplify the design we assume that the presence of multipleĪddresses at a host is sufficient to indicate the existence of O It can be assumed that one or both hosts are multihomed and O It must be backwards-compatible with current, regular TCP, to Imposed two key constraints on the multipath TCP design presented in In order to limit the potentially huge design space, the authors MPTCP, and as a consequence of these factors, what API extensions Have on applications, what applications will want to do with ![]() O Application Considerations, discussing what impact MPTCP will Order to "do no harm" to other network users. O Congestion Control, presenting a safe congestion controlĪlgorithm for coupling the behaviour of the multiple paths in Separation through which an extensible MPTCP implementation can be This design is based, and an explanation of a functional TCP, contains a discussion of high-level design decisions on which O Architecture, which explains the motivations behind Multipath To create a Multipath TCP implementation, however. This is not the only information required ("subflows"), managing these subflows, reassembly of data, and Specifically, those for signalling and setting up multiple paths ![]() The protocol changes required to add multipath capability to TCP Operate across multiple paths simultaneously. Multipath TCP service, which enables a transport connection to MPTCP is a set of extensions to regular TCP to provide a Internet-Draft Multipath TCP March 2011 1. Changes since draft-ford-mptcp-multiaddressed-02. Changes since draft-ford-mptcp-multiaddressed-03. Changes since draft-ietf-mptcp-multiaddressed-00. Changes since draft-ietf-mptcp-multiaddressed-01. Changes since draft-ietf-mptcp-multiaddressed-02. Internet-Draft Multipath TCP March 2011 8. Address Knowledge Exchange (Path Management). The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal ![]() This Internet-Draft will expire on September 15, 2011.Ĭopyright (c) 2011 IETF Trust and the persons identified as the Material or to cite them other than as "work in progress." It is inappropriate to use Internet-Drafts as reference Internet-Drafts are draft documents valid for a maximum of six monthsĪnd may be updated, replaced, or obsoleted by other documents at any Note that other groups may also distribute Internet-Drafts are working documents of the Internet Engineering This Internet-Draft is submitted in full conformance with the Use multiple TCP flows across potentially disjoint paths. reliableīytestream), and provides the components necessary to establish and The same type of service to applications as TCP (i.e. Traditional TCP to support multipath operation. This document presents a set of extensions to Multipath TCP provides the ability to simultaneously use multiple Improve resource usage within the network, and thus improve userĮxperience through higher throughput and improved resilience to Simultaneous use of these multiple paths for a TCP/IP session would TCP/IP communication is currently restricted to a single path perĬonnection, yet multiple paths often exist between peers. TCP Extensions for Multipath Operation with Multiple Addresses draft-ietf-mptcp-multiaddressed-03
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |