Ziyang: Thanks for posting this draft to the list for discussion. It seems your idea is to use SDN controller to help the endpoint or host to select the path for traffic optimization, get better path utilization. To steer the traffic to appropriate path, you might have two different options: Option 1 On path method: endpoint or host decide itself how to steer traffic to multiple path not that host has already participant in flow forwarding Option 2 Off path method: SDN controller configure endpoint or host to decide which path it should select. Note that endpoint or host are located at two ends, it can be the MPTCP client or MPTCP server. Therefore two questions I have are:
1. have you compare performance difference between on path method and off path method? 2. Since you also adopt mpquic, have you compare the performance difference between using MPTCP and using MPQUIC? I think it will be nice you can elaborate your use cases you test: e.g., Alice starts download a streaming media in the building over WIFI and move outside of the building using 4G networks, MPTCP was configured on Alice’s mobile phone to use both WIFi and 4G Networks. Or MPTCP using in the data center, Multiple paths have been setup between two servers, when one path disconnected, how to detect path failure, or intermediate switch failure and switch the traffic to another path. Also you need to consider how frequent you can collect network performance data from the network, from which layer, how fast you can expose these information to the client who participant in flow forwarding? -Qin 发件人: alto [mailto:[email protected]] 代表 Ziyang Xing 发送时间: 2022年4月12日 22:10 收件人: [email protected] 主题: [alto] Asking for feedback on a proposal for draft-xing-alto-sdn-controller-aware-mptcp-mpquic-01 Dear group, I hope this mail finds all the members well. The document draft-xing-alto-sdn-controller-aware-mptcp-mpquic-01 (its full name: The SDN-based MPTCP-aware and MPQUIC-aware Transmission Control Model using ALTO, and its html link: https://www.ietf.org/archive/id/draft-xing-alto-sdn-controller-aware-mptcp-mpquic-01.html). 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. The intended final research value proposition of the draft is the formalization of a comprehensive architecture supporting recent advances on overall management procedures. While I think this fits on the purpose of ALTO, I would like to collect feedback from the group about if this approach makes sense for the group. Thank you. Best regards, Ziynag Xing April 12th, 2022
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
