Re: [Taps] Abstracting away multi-streaming and usage of multiple paths

2016-07-19 Thread Mirja Kühlewind
Hi Michael, hi all, I believe there is actually quite a bit of discussion currently in MPTCP about how important it probably is to have an interface to the application and get input about upper layer preferences. Maybe ask on the mptcp list for input? Mirja > Am 19.07.2016 um 09:49 schrieb

Re: [Taps] Abstracting away multi-streaming and usage of multiple paths

2016-07-19 Thread Aaron Falk
Hi Michael- It seems to me that one could answer the question separately whether the upper layer should be able to control the use of multi-streaming or multi-paths vs. know whether multi-streaming or multi-paths are in use. I would think that there no reason to hide this information from apps.

[Taps] Abstracting away multi-streaming and usage of multiple paths

2016-07-18 Thread Michael Welzl
Hi, draft-gjessing-taps-minset-02 suggests that all transport service features related to multi-streaming and usage of multiple paths are “automatable”. The rationale is given in Section 4: https://tools.ietf.org/html/draft-gjessing-taps-minset-02#section-4 (this particular section says