A simple multipath OpenFlow controller using topology‐based algorithm for multipath TCP. (28th March 2017)

• Record Type: Journal Article
• Authors: Nakasan, Chawanat; Ichikawa, Kohei; Iida, Hajimu; Uthayopas, Putchong
• Other Names: Plale Beth guestEditor.; Chen Maio guestEditor.; Escudero‐Sahuquillo Jesús guestEditor.; Garcia Pedro Javier guestEditor.
• Is Part Of: Concurrency and computation. Volume 29:Number 13(2017)
• Page Start: n/a
• Page End: n/a
• Publication Date: 2017-03-28
• Subjects: MPTCP -- multipath routing -- OpenFlow -- pox; Parallel processing (Electronic computers) -- Periodicals; Parallel computers -- Periodicals; 004.35
• DOI: 10.1002/cpe.4134
• Languages: English
• ISSNs: 1532-0626

Abstract

Summary: Multipath 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.