Abstract
SummaryMultipath transmission control protocol(TCP), or MPTCP, is a widely‐researched mechanism that allows a single application‐level connection to be split to more than 1 TCP stream and, consequently, more than 1 network interface, as opposed to the traditional TCP/IP model. Being a transport layer protocol, MPTCP can easily interact between the application using it and the network supporting it. However, MPTCP does not have control of its own route. Default IP routing behavior generally takes all traffic through the shortest or best metric path. However, this behavior may actually cause paths to collide with each other, creating contention for bandwidth in a number of edges. This can result in a bottleneck that limits the throughput of the network. Therefore, a multipath routing mechanism is necessary to ensure smooth operation of MPTCP. We created smoc, a simple multipath OpenFlow controller, that uses only topology information of the network to avoid collision where possible. Evaluation of smoc in a virtual local‐area and a physical wide–area software‐defined networks showed favorable results as smoc provided better performance than simple or spanning tree–routing mechanisms.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: Concurrency and Computation: Practice and Experience
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.