The SDN-based MPTCP-aware and MPQUIC-aware Transmission Control Model using ALTO

Internet-Draft	SDN MPTCP-aware MPQUIC-aware using ALTO	April 2022
Xing, et al.	Expires 14 October 2022	[Page]

Abstract

This document aims to study and implement MPTCP (MultiPath Transmission Control Protocol) and MPQUIC (MultiPath Quick UDP Internet Connection) for software-defined networking. In an software-defined network, Alto (application layer traffic optimization) server collects network cost indicators (including link delay, availability, network traffic, bandwidth, etc.) and the controller extract MPTCP or MPQUIC packet header and allocate MPTCP or MPQUIC packet to suitable transmission path according to the obtained network state, reducing the probability of transmission path congestion and improving path utilization.¶

1. Introduction

The traditional TCP protocol only uses one path between the server and the client to transmit data. In order to realize the simultaneous transmission of data between multiple paths between the server and the client, the International Internet Engineering Task Force proposed and standardized MultiPath TCP (MPTCP) [RFC6897] . MPTCP realizes multiple paths between hosts to transmit data at the same time, but it is necessary to modify the operating system kernel to change the protocol stack of both parties in order to increase the MPTCP protocol. Therefore, MPTCP has disadvantages such as difficulty in deployment. In order to solve the drawbacks in the transmission network and adapt to the faster development of the Internet, Google proposed the HTTP/3 protocol which is Quick UDP Internet Connection (QUIC) [RFC9000]. QUIC has many new features, such as: 0-RTT, forward error correction, connection migration, flexible congestion control, multiplexing without head-of-line blocking, easy deployment, and more. MultiPath QUIC (MPQUIC) [MPQUIC] is a multi-path transmission protocol designed on the basis of QUIC. Software Defined Network (SDN) [RFC7426] is a new network innovation architecture implemented by virtualization. By separating control and forwarding, it breaks the closedness of traditional network equipment, and uses programming to make network management more concise and efficient. flexible. Application Layer Traffic Optimization (ALTO) [RFC7285] can obtain and provide global network information to the controller, such as network traffic, link delay, etc. The main multipath transmission protocols MPTCP and MPQUIC have their own characteristics [MultipathTester]. The application of multipath transmission in SDN can greatly improve the transmission throughput.The purpose of this research is to realize the coupling control of MPTCP or MPQUIC sub-flows in software-defined networks, and allocate the optimal path according to the network status information obtained by ALTO, so as to improve bandwidth utilization and resource allocation fairness, effectively alleviate network congestion and achieve load balancing between paths.¶

At present, some scholars have studied the model of deploying MPTCP or MPQUIC in software-defined network, [QUICSDN] \ [SDN_for_MPTCP] \ [SDN_MPTCP], but their SDN controller cannot manage the headers of MPTCP and MPQUIC data packets at the same time, and cannot achieve unified management of MPTCP and MPQUIC links.The ALTO protocol can easily obtain various network states (including multiple SDNs, dynamic networks) from SDN without the internal details of the network provider, and deliver controller decisions [SDN_ALTO_proof] \ [SDN_ALTO], which is already a mature solution.¶

The SDN-based MPTCP and MPQUIC transmission control using ALTO model consists of three parts.¶

The first part is the network status acquisition module, which acquires basic network status information from ALTO.¶
The second part is the control plane, that is the SDN controller, which includes extracting MPTCP / MPQUIC header module, path selection module, flow rules generation module and link management module. The main function is to extract the header identifier token or CID of MPTCP and MPQUIC according to the data packet (For details, see Section 4), obtain the global information of the whole network according to AlTO and allocate suitable paths and put flow rules to switches according to the global information of the entire network, and manage the links of the entire network at the same time.¶
The third part is the data plane which is some OpenFlow switches. It executes the flow rules issued by the controller and realizes the forwarding of data packets.¶

The purpose of this document is to:¶

Describe the model that the controller can extract MPTCP or MPQUIC data packets in the software-defined network.¶

According to the global information obtained by the AlTO, the controller allocates MPTCP or MPQUIC data packets with efficient transmission path.¶

The principle of multi-path transmission control model based on SDN controller MPTCP and MPQUIC using ALTO is shown in Figure 1.¶

+--------------Network Status Acquisition----------------+
|                     ALTO Server                        |
|       (network topology, traffic distribution,         |
|               link delay/bandwidth)                    |
+---------------^----------------------------------------+
                |
                +--Network Information--+
                                        |
+--------------------Control Plane------v----------------+
|    +-------------------------------------------+       |
|    |     Extract MPTCP / MPQUIC header module  |       |
|    |          (Extract packet header)          |       |
|    +---------------------+---------------------+       |
|                          |                             |
|                     token or CID                       |
|                          |                             |
|    +---------------------v---------------------+       |
|    |            Path selection module          |       |
| +-->    (Select the appropriate path from      <--+    |
| |  |    the candidate path - assigned path)    |  |    |
| |  +---------------------+---------------------+  |    |
| |                        |                   Allocated |
| |            +-----Allocate path------+         path   |
| |            |                        |           |    |
| |  +---------v----------+ +-----------v--------+  |    |
| |  |     Flow rules     | |  Link management   |  |    |
| |  | generation module  | |      module        |  |    |
| |  |   (All switch      | |(Manage the mapping +--+    |
| |  |  assignment flow   | |table flows and save|       |
| |  |  tables for the    | |   the connection   |       |
| |  |  selected path)    | |    information)    |       |
| |  +---------+----------| +--------------------+       |
+-|------------|-----------------------------------------+
 Network       |
 status        +----Flow rules-----+
  |                                |
  |  +---------------Data Plane----v-------------+
  |  | +------------------+ +------------------+ |
  |  | |    SDN switch    | |    SDN switch    | |
  +--+ | (Forwarding flow | | (Forwarding flow | |
     | | rules and obtain | | rules and obtain | |
     | |  network status) | |  network status) | |
     | +------------------+ +------------------+ |
     +-------------------------------------------+

Figure 1 Schematic diagram of SDN-based MPTCP-aware and MPQUIC-aware
transmission control model using ALTO

4. SDN-based MPTCP-aware and MPQUIC-aware multi-path transmission control model using ALTO

      +---------------------+        +----------------------------+
      | Create a flow table |        |The packet p arrives at s1, |
      +----------+----------+        | and s1 performs flow rules |<-+
                 |                   |   item matching on p       |  |
                 v                   +--------------+-------------+  |
      +----------+----------+                       |                |
      |Obtain Network Status|                       |                |
      |Extract packet header|<-----+                |                |
      +----------+----------+      |                v                |
                 |                 |                /\               |
     +-----------+------------+    |               /  \              |
     |           |            |    +---NO-----Match successful?      |
     v           v            v                    \  /              |
    /\          /\           /\                     \/               |
   /  \        /  \         /  \                    YES              |
MP_CAPABLE     CID         MP_JOIN                   |               |
   \  /        \  /         \  /                     v               |
    \/          \/           \/         +------------+-------------+ |
    |            |            |         |Forward paket according to|-+
    |            |            v         |the flow rules instruction|
    |            |     +------+------+  +------------+-------------+
    |            |     |Extract token|               ^
    |            |     +------+------+               |
    |            |            |                      |
    |            v            v                      |
    |     +------+----+ +-----+-------+              |
    |     | key=Q+CID | | key=T+token |              |
    |     +-----+-----+ +------+------+              |
    |           |              |                     |
    |           +------+-------+                     |
    |                  |                             |
    |                  v                             |
    |                 /\                             |
    |                /  \                            |
    |             Is there a key                     |
    |        +--in the flow table?--+                |
    |        |       \  /           |                |
    |       NO        \/           YES               |
    |        |                      |                |
    |        v                      v                |
    | +-------+---------+   +-------+------+         |
    | |Extract source IP|   |              |         |
    | |destination IP   |   | Path of all  |         |
    | |source port      |   | subflows in  |         |
    | |destination port |   | value,RL     |         |
    | |and subflow      |   |              |         |
    | |identifier       |   |              |         |
    | +-------+---------+   +-------+------+         |
    |         |                     |                |
    |         v                     v                |
    | +-------+---------+   +-------+-------+        |
    | |Add the subflow  |   |Extract the    |        |
    | |meta information |   |subflow meta   |        |
    | |to value and then|   |information    |        |
    | |save <key:value> |   |and add it to  |        |
    | |to the flow rules|   |value          |        |
    | +-------+---------+   +--------+------+        |
    +-------->|                     |                |
              v                     v                |
      +-------+---------+   +-------+------+         |
      |                 |   |Allocate a new|         |
      |Allocate the     |   |path to p, and|         |
      |first path to p  |   |route does not|         |
      |route            |   |belong to RL  |         |
      +-------+---------+   +-------+------+         |
              |                     |                |
              +----------+----------+                |
                         |                           |
                         v                           |
   +---------------------+----------------------+    |
   |Put forward and reverse flow rules to switch|----+
   +--------------------------------------------+
Figure 2 The flow chart of the SDN-based MPTCP-aware and MPQUIC-aware
 multi-path transmission control model using ALTO

The flow chart of the SDN-based MPTCP-aware and MPQUIC-aware multi-path transmission control model using ALTO is shown in Figure 2. The transmission control model is realized by the following steps:¶

Step 1. The SDN controller creates a mapping table flows for storing MPTCP or MPQUIC connection information, and each entry structure of the mapping table flows is <key:value>; wherein key is the unique identifier of MPTCP or MPQUIC connection, When the packet comes from MPTCP, key=T+token; and when the packet comes from MPQUIC, key=Q+CID (The letters T and Q are used to distinguish MPTCP and MPQUIC). value is a set of sub-stream meta-information, each item in the set is a sub-stream meta-information; each sub-stream meta-information consists of source IP, destination IP, source port, destination port, MPTCP (or MPQUIC) sub-stream identifier and the path route composition.¶
Step 2. When the data packet p of a certain MPTCP or MPQUIC subflow reaches the first switch s1, the first switch s1 extracts the header field of the data packet p, extracts the source IP, source port, destination IP and the destination port matches the source IP, source port, destination IP and destination port of the flow table in the first switch s1 respectively, and judges whether the matching is successful. If so, go to step 12; if not, then the first switch s1 encapsulates the data packet p and forwards it to the SDN controller, and at the same time adds the data packet p to the waiting queue.¶
Step 3. After receiving the data packet p, the SDN controller extracts the header field of the data packet p, extracts the connection identifier of the data packet, and generates a key value, where when the data packet comes from MPTCP, key=T+token; When the packet comes from MPQUIC, key=Q+CID. Then query whether there is a key in the mapping table flows, if so, go to step 7, if not, go to step 4.¶
Step 4. Extract the source IP, destination IP, source port, and destination port of the data packet p and generate a key value, where when the data packet comes from MPTCP, key=T+token; and when the data packet comes from MPQUIC, key=Q+CID .¶
Step 5. ALTO to get basic network information. The controller calculates the threshold T according to the global network state information (network topology, number of switches, etc.). Using the depth-first traversal algorithm, find the available path set R={r_1,...,r_i,...,r_m } from all source nodes whose length does not exceed a certain threshold T to the destination node, r_i is the i available path, in the available path set Select a shortest path r_i in R as the path route of the sub-flow, where r_i=<s_(i,1),...,s_(i,j),...>, s_(i,j) represents the i available path The switch numbered j, where i belong to [1,m],j belong to [1,T].¶
Step 6. Use the MPTCP and MPQUIC connection identifiers as the unique identifier key of the MPTCP and MPQUIC connections, where the key is the unique identifier of the MPTCP and MPQUIC connections. When the data packet comes from MPTCP, key=T+token; and the data packet comes from In MPQUIC, key=Q+CID. The source IP, source port, destination IP, destination port, MPTCP, MPQUIC sub-flow identifier and path route of the data packet p are added to the set value of sub-flow meta information as sub-flow meta-information, and then the <key:value> The form is saved to the mapping table flows, and go to step 10.¶
Step 7. The SDN controller updates the flows table according to the global information of the network, and takes out the value from the connection identifier, and then composes all paths in the value into a set RL={r_1,r_2,...}.¶
Step 8. The SDN controller searches for a suitable disjoint path for the data packet p according to the method in Step 5, and sets the found path as route=r_i, where r_i not belong to RL.¶
Step 9. Extract the source IP, destination IP, source port, destination port, and MPTCP, MPQUIC sub-flow identifiers of the data packet p, and convert the source IP, source port, destination IP, destination port, MPTCP (or MPQUIC) sub-flow identifiers and the path route is added to the value as sub-flow meta information.¶
Step 10. The SDN controller uses the source IP, source port, destination IP and destination port to issue the flow table to all switches in the route route, and set the route route=r_i=<s_(i,1),...,s_(i,j-1),s_(i.j),s_(i,j+1),...>, for the switch s_(i,j), the flow entry sent is the source IP, source port to the destination, the data packets of IP and destination port are forwarded to s_(i,j+1).¶
Step 11. The controller sends the reverse flow table to all switches on the route route and sets the route route=r_i=<s_(i,1),...,s_(i,j-1),s_(i,j),s_(i,j+1),...>, for the switch s_(i,j) ,the flow table entry sent is to forward the data packets from the destination IP, destination port to source IP, and source port to s_(i,j-1).¶
Step 12. The switch already contains a flow entry for processing the data packet p, and forwards the data packet according to the rules defined by the flow entry, and completes the processing of the data packet p. Step 2 is executed when the forwarding fails or the processing of other subsequent data packets returns.¶

8. References

8.1. Informative References

[RFC2119]: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC6824]: Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, "TCP Extensions for Multipath Operation with Multiple Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013, <https://www.rfc-editor.org/info/rfc6824>.
[RFC6897]: Scharf, M. and A. Ford, "Multipath TCP (MPTCP) Application Interface Considerations", RFC 6897, DOI 10.17487/RFC6897, March 2013, <https://www.rfc-editor.org/info/rfc6897>.
[RFC7285]: Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S., Previdi, S., Roome, W., Shalunov, S., and R. Woundy, "Application-Layer Traffic Optimization (ALTO) Protocol", RFC 7285, DOI 10.17487/RFC7285, September 2014, <https://www.rfc-editor.org/info/rfc7285>.
[RFC7426]: Haleplidis, E., Ed., Pentikousis, K., Ed., Denazis, S., Hadi Salim, J., Meyer, D., and O. Koufopavlou, "Software-Defined Networking (SDN): Layers and Architecture Terminology", RFC 7426, DOI 10.17487/RFC7426, January 2015, <https://www.rfc-editor.org/info/rfc7426>.
[RFC9000]: Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, May 2021, <https://www.rfc-editor.org/info/rfc9000>.

8.2. Informative References

[MPQUIC]: "Multipath Extension for QUIC", <https://www.ietf.org/archive/id/draft-lmbdhk-quic-multipath-00.html>.
[MultipathTester]: "Coninck Q D , Bonaventure O . MultipathTester: Comparing MPTCP and MPQUIC in Mobile Environments[C]// 2019 Network Traffic Measurement and Analysis Conference (TMA). 2019.", <https://10.23919/TMA.2019.8784653>.
[QUICSDN]: "Kumar P , Chen J , Dezfouli B . QuicSDN: Transitioning from TCP to QUIC for Southbound Communication in SDNs[J]. 2021.", <https://ui.adsabs.harvard.edu/abs/2021arXiv210708336K>.
[SDN_ALTO]: "V. K. Gurbani, M. Scharf, T. V. Lakshman, V. Hilt and E. Marocco, "Abstracting network state in Software Defined Networks (SDN) for rendezvous services," 2012 IEEE International Conference on Communications (ICC), 2012, pp. 6627-6632.", <https://doi.org/10.1109/ICC.2012.6364858>.
[SDN_ALTO_proof]: "[1] Faigl, Z. , Z. Szabo , and R. Schulcz . "Application-layer traffic optimization in software-defined mobile networks: A proof-of-concept implementation." IEEE(2014):1-6.", <https://doi.org/10.1109/NETWKS.2014.6959200>.
[SDN_for_MPTCP]: "Hussein A , Elhajj I H , Chehab A , et al. SDN for MPTCP: An enhanced architecture for large data transfers in datacenters[C]// IEEE International Conference on Communications. IEEE, 2017.", <https://doi.org/10.1109/ICC.2017.7996653>.
[SDN_MPTCP]: "7. K. Gao, C. Xu, J. Qin, S. Yang, L. Zhong and G. Muntean, "QoS-driven Path Selection for MPTCP: A Scalable SDN-assisted Approach," 2019 IEEE Wireless Communications and Networking Conference (WCNC), 2019, pp. 1-6,", <https://doi.org/10.1109/WCNC.2019.8885585>.

The SDN-based MPTCP-aware and MPQUIC-aware Transmission Control Model using ALTO

Abstract

Status of This Memo

Copyright Notice

Table of Contents

1. Introduction

2. Terminology

3. Default transmission control mode of MPTCP or MPQUIC in SDN

4. SDN-based MPTCP-aware and MPQUIC-aware multi-path transmission control model using ALTO

5. Security Considerations

6. IANA Considerations

7. Discussion

8. References

8.1. Informative References

8.2. Informative References

Authors' Addresses