On 27/03/18 - 14:04:28, Lorenzo Colitti wrote:
On Tue, Mar 27, 2018 at 11:18 AM, Christoph Paasch
> It also would allow us to expose subflows as file-descriptors to the
> user-space. That way the user-space can do setsockopt, getsockopt,... on
> subflows. An idea that came up in the past when we were thinking on how to
> expose an MPTCP API that allows apps to control certain things on the
+1 to this since it will allow client platforms to use setsockopt to, for
example, bind subflows to interfaces (e.g., with SO_BINDTODEVICE, or with
SO_MARK as used by Android).
Have you seen the netlink path-manager patches that have been sent to the
The goal of them is to allow a daemon to control the creation and
destruction of subflows through netlink.
Would that be something that fits your model?