FYI - probably of interest to this group... > Begin forwarded message: > > From: Olivier Bonaventure <[email protected]> > Subject: [multipathtcp] Socket API for MPTCP > Date: 8. juli 2016 kl. 17.56.45 CEST > To: multipathtcp <[email protected]>, "<[email protected]>" > <[email protected]> > Resent-From: <[email protected]> > Reply-To: [email protected] > > Hello, > > During the last years, we have received on a regular basis questions from > users of Multipath TCP on how they could control the utilisation of the > subflows. In the Linux implementation, the default solution was to tune the > path manager, but this is kernel code and few users actually managed to > change this path manager. > > Benjamin Hesmans has spent some time to think about simple extensions to the > socket API to allow applications to control the underlying Multipath TCP > stack. He has implemented his ideas and has running code. A first draft > describing his API has been submitted to the IETF : > > > Title: A socket API to control Multipath TCP > URL: https://www.ietf.org/internet-drafts/draft-hesmans-mptcp-socket-00.txt > > Abstract: > This document proposes an enhanced socket API to allow applications > to control the operation of a Multipath TCP stack. > > A related paper will also appear at the ANR workshop : > > https://irtf.org/anrw/2016/anrw16-final16.pdf > > > We have requested a slot to present in Berlin. We expect that agreeing on a > common socket API exposed by Multipath TCP implementations would help its > end-to-end deployment. > > > Olivier and Benjamin > > _______________________________________________ > multipathtcp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/multipathtcp
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
