Multipath TCP: an overview

remember that the server application/port can remain the same if the client has multiple connections. It's only in the case where the server has multiple connections that the it needs multiple IP addresses, and in that case I don't see any way around the issue.

I also don't expect servers to expose multiple connections very frequently, they don't need to and if they are serving substantial numbers of clients, they probably don't want to have any one client be able to use a substantial amount of bandwidth.

I see two categories where multipath TCP makes lots of sense

1. multi-homed clients (wifi + cell, DSL + cable + cell backup, etc)

Here, only the client has multiple IP addresses

2. huge file transfers within one organization on specially setup paths

Here both the client and server may have multiple IP addresses, and even with just a single IP at both ends, they may want to use many subconnections to be more resistant to the effects of packet loss.