Hi Erik, That's the intuitive approach to follow but unfortunately the situation is not that obvious to get into.
Network providers do not have a control on the servers and the terminals that are enabled by customers behind the CPE. So making use of MPTCP to grab more resources (when available) or to provide better resiliency (when a network attachment is lost) will require both endpoints to be MPTCP-capable. We are in a situation where customers are provided with multiple accesses but these customers do only have the QoE as if they are single-connected. The network-assisted MPTCP is a feature to have immediately the benefits of MPTCP without requiring that all terminals and servers are MPTCP-capable. The design we are advocating for allows for the use of MPTCP along the path when both endpoints are MPTCP-capable and to bypass the proxy when it makes sense. Cheers, Med > -----Message d'origine----- > De : Erik Kline [mailto:e...@google.com] > Envoyé : mercredi 19 juillet 2017 10:30 > À : BOUCADAIR Mohamed IMT/OLN > Cc : Tom Herbert; Joe Touch; Internet Area; tsv-area@ietf.org > Objet : Re: [Int-area] Middleboxes to aid the deployment of MPTCP > > > [Med] We would love to avoid requiring adding a function in the network > to assist devices to make use of their multiple interfaces/paths. > Nevertheless, the situation is that servers do not support MPTCP. > > If server infrastructures aren't supporting MPTCP, maybe that's the > thing that needs to be looked at...if in fact it can be helped.
