From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============4519966401222979789==" MIME-Version: 1.0 From: Christoph Paasch To: mptcp at lists.01.org Subject: Re: [MPTCP] Call for ideas for a presentation about MPTCP Upstream project at NetDev 0x12 in July Date: Mon, 30 Apr 2018 09:12:35 -0700 Message-ID: <20180430161235.GL19260@MacBook-Pro-6.local> In-Reply-To: alpine.OSX.2.21.1804300856590.4562@seskerx-mobl.amr.corp.intel.com X-Status: X-Keywords: X-UID: 568 --===============4519966401222979789== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hello, On 30/04/18 - 09:05:41, Mat Martineau wrote: > = > On Mon, 30 Apr 2018, Matthieu Baerts wrote: > = > > Hi Mat, > > = > > On Mon, Apr 30, 2018 at 5:37 PM, Mat Martineau wrote: > > = > > On Sun, 29 Apr 2018, Matthieu Baerts wrote: > > = > > Hi Mat, > > = > > Thank you for your review and input! > > = > > On Sat, Apr 28, 2018 at 2:44 AM, Mat Martineau wrote: > > = > > =C2=A0 =C2=A0 =C2=A0 Hi Matthieu - > > = > > =C2=A0 =C2=A0 =C2=A0 On Fri, 27 Apr 2018, Matthieu Baerts w= rote: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Hello, > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Following yesterd= ay's discussion about NetDev 0x12, here is a proposition of mail to send to= NetDev > > committee. I > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 already put some = comments. Note that I have followed the submission guidelines from: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.netde= vconf.org/0x12/submit-proposal.html#proposals > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Please comment it= before Monday morning. Sorry for the rush but the deadline is the 1st of M= ay :) > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 * Name(s) of the submitter(s): Christoph Paasch (Apple), Mat Martineau > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Intel), Peter Kr= ystad (Intel), Ossama Othman (Intel) and myself, Matthieu Baerts (Tessares) > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I wrote down the = names of people who participated in the discussion in the ML and during the= weekly > > meetings. I can > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 add more people i= f more people would like to join the preparation and presentation of this t= utorial. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 @Christoph, Mat, = Peter, Ossama: can I write your names there? > > = > > = > > =C2=A0 =C2=A0 =C2=A0 Ossama won't be able to attend. It loo= ks like most sessions have 1 or 2 presenters, so I don't know if 4 is too > > many. I'm sure > > =C2=A0 =C2=A0 =C2=A0 they'll give us some feedback if they = want to limit the number of presenters. > > = > > = > > OK thank you! > > Yes indeed, I am sure they will say something if we are too= many. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 * Title of the submission: MPTCP: from the basic to an upstreamable base > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 We certainly need= a better title, please comment! > > = > > = > > =C2=A0 =C2=A0 =C2=A0 "Multipath TCP: Present Use Cases and = an Upstream Future" ? > > = > > = > > I was trying to find something that catch the attention but= it is maybe not needed for these kind of presentation. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 > * Label (one of= moonshot, nuts'n bolts, hands-on): hands-on > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "hands-on" seems = to be the correct one according to the Submission Types. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.netde= vconf.org/0x12/submit-proposal.html#types > > = > > = > > =C2=A0 =C2=A0 =C2=A0 It's a little bit of "nuts & bolts" to= o, but I agree that hands-on is the better match. > > = > > = > > Thank you! > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 * Submission type (one of talk, presentation, workshop): tutorial, > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 instructor-led se= ssions (minimum 1 hour long and not to exceed 1.5 hours. The instructor wil= l go over the > > technology > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 either through co= de review or execution and interact with the attendees.) > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I guess there is = a typo here: presentation should be replaced by tutorial in the guidelines. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Estimate of length of time for presentation: 1h > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 That's what we ag= reed yesterday but I can change. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Affiliations of submitters (needed for conflict of interest check): App= le, > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Intel, Tessares > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Description of proposal: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 A project to add an implementation of the MultiPath TCP p= rotocol to the > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Linux kernel is i= n progress by a small community. The goal of this tutorial is to discover w= hat is this > > TCP extension > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (RFC 6824), what = are the different use-cases already in production by some companies and wha= t are the > > challenges to > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 upstream MPTCP. W= e hope having interactive discussions and getting feedback from experienced= developers > > will help us > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 in this task of e= asily bringing MPTCP to all Linux users, a technology already used by milli= ons of > > people. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 In a bit more detail, we will start with a basic introduc= tion of MPTCP. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 A few use-cases w= ill be presented with a demo to explain how useful this protocol is in toda= y's Internet > > and how it > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 can be extended w= ith API's like Netlink and BPF. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 I recognize how Netlink is associated = with a userspace path manager, but what's the BPF extensibility you're > > referring to? > > = > > = > > It was only to mention that it would be possible to extend = MPTCP with eBPF. > > Even if it is not already available in the current Open-Sou= rce implementation, there is already the possibility to > > get a version with a > > programmable scheduler: https://progmp.net > > = > > = > > If we don't have something specific to our effort with BPF, I'm not sur= e it belongs in the summary. But I don't have a strong opinion > > about it. > > = > > = > > We are saying that "the [Open-Source] implementation can currently be e= xtended with netlink and BPF". It can come later :) > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Then we will have= some explanations about how MPTCP is currently implemented. This current i= mplementation > > is quite > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 intrusive and tha= t is certainly not something we would like to have upstream. We would like = to express > > what we have > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 in mind to change= that, with some samples and initiate discussions. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 My edit of the above: > > = > > =C2=A0 =C2=A0 =C2=A0 """ > > = > > =C2=A0 =C2=A0 =C2=A0 A community project is underway to add= Multipath TCP to the upstream Linux kernel. This tutorial will introduce > > the audience to > > =C2=A0 =C2=A0 =C2=A0 this TCP extension (RFC 6824), show so= me use cases already in production, and discuss the challenges in > > converging on an upstream > > =C2=A0 =C2=A0 =C2=A0 MPTCP implementation. > > = > > = > > Should we insist on the "discussion" part? Like saying: "di= scuss with the audience"? "have interactive discussions"? > > It is maybe not needed but it was mainly to express the int= eractivity, it is a tutorial, not just a "simple" > > presentation. > > = > > = > > I think it's ok to mention that - while I left the word "discuss"= in there for that reason, maybe that's not obvious or clear > > enough. > > = > > = > > It was maybe me, maybe no need to insist :-) > > = > > =C2=A0 =C2=A0 =C2=A0 We will use the current MPTCP implemen= tation to demonstrate the utility of the protocol on today's internet, > > and to show how this > > =C2=A0 =C2=A0 =C2=A0 implementation can currently be extend= ed with netlink and BPF. This not only has practical application for > > deploying MPTCP now, > > =C2=A0 =C2=A0 =C2=A0 but also illustrates how the APIs and = code will need to evolve in order to properly coexist with the optimized > > Linux TCP core we > > =C2=A0 =C2=A0 =C2=A0 all rely on. We will discuss our ideas= for bringing MPTCP to the upstream kernel so the technology is available > > to all Linux > > =C2=A0 =C2=A0 =C2=A0 users. > > = > > = > > To "attract" people, should we mention that the current imp= lementation is already used by millions of users? > > I like how your improve the last bit :-) > > = > > = > > Sure. I liked that in your text, but ran out of time figuring out= how to fit it in to the last sentence :) > > = > > = > > Could we simply say: > > = > > We will use the current MPTCP implementation to demonstrate the utility= of the protocol already used by millions of users on today's Internet > = > How about "used by millions of devices"? I think it flows a little better > than "used by ... users". +1 on the "used by millions of devices". Christoph > = > = > Thanks, > = > Mat > = > > = > > or: > > = > > and to show how this implementation - already used by millions of users= - can currently be extended with Netlink and BPF. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 """ > > = > > =C2=A0 =C2=A0 =C2=A0 Feel free to edit/merge/expand/discard= as needed :) > > = > > = > > Thank you for your edit, it is indeed cleaner! > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 For more information about this project: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://github.co= m/multipath-tcp/mptcp_net-next/wiki > > = > > = > > I guess I can keep this, right? > > = > > = > > Yes, that was my intent. > > = > > = > > Will do! > > = > > Thank you! > > = > > Matthieu > > = > > = > > = > > = > > Thanks, > > = > > Mat > > = > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Please feel free = to comment this as well. We are still far from the max 350 words limit we f= ound last > > time. But on > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the other hand, I= can no longer find this limit on their website :) > > = > > = > > =C2=A0 =C2=A0 =C2=A0 Hope the above is helpful. Thanks agai= n for your work on this proposal. > > = > > = > > Yes it is, thank you for your help! > > = > > Matthieu > > = > > = > > = > > =C2=A0 =C2=A0 =C2=A0 Mat > > = > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Thank you for you= r help! > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Have a good day/e= vening, > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Matthieu > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 On 25/04/2018 21:= 58, Mat Martineau wrote: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Hi Matthieu - > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 On Fri, 20 Apr 2018, Matthieu Baerts wrote: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 Hello, > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 NetDev 0x12 is coming to Montr=C3=A9al this summer= : July 11th to 13th, 2018. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 We already talked about this event on this ML and = at our weekly meetings but here is a > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 summary of the discussions we had: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- we would like to have a presentation there= mainly to get feedback and advice from other > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 kernel developers > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- a presentation would clearly indicate that= this MPTCP Upstream project exists and we could > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 get help from more developers > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- we would like to indicate that having MPTC= P upstream is asked by different companies, some > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 are even ready to contribute ; it is then importan= t to have MPTCP upstream > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 Also note that: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- David Miller will not be present in Montr= =C3=A9al [1] but other main contributors should be > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 there (we don't have a list) > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Side note, in the past day David reiterated his statement about not att= ending or supporting the > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 conference: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 https://marc.info/?l=3Dlinux-netdev&m=3D152466827203301&w=3D2 > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- A presentation by Octavian Purdila about "= MPTCP Upstreaming" has already been given in > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 2015 (NetDev 0.1) [2] > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- 3 types of presentation are available: tal= ks, tutorials and workshops [3] > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Call for Presentation Proposals closes on = May 1st, 2018. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 The current idea we briefly discussed during our w= eekly meetings is to give a tutorial: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- It is not useful to give almost the same p= resentation as the one of Octavian > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- It will allow us more flexibility somehow = to explain what is MPTCP, the different > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 use-cases, why it is important to have it upstream= and what problems we are currently facing. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- David Miller and many other kernel develop= ers will go to LPC in November: a good place to > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 give a talk this time. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 Do you have any ideas on what we could show in thi= s tutorial? > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 I recently discussed with my colleague Olivier Bon= aventure who has a lot of experiences in > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 giving different introductions and more about MPTC= P and here is what he suggests: > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- A first part about a basic introduction of= MPTCP > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Indicate different use-cases -- if possibl= e with a "closed demo" to be sure it is working > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 -- asking people to setup something is not easy in= 1h, max 1h30. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0From the description at [3], either "instructor-led" 60-90 minute= tutorials or > > "student-participation" > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 2-3 hour sessions are possible. The closed demo maps well to their "ins= tructor-led" category. > > Looking at > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 the schedule, the past two Netdev Conferences have had one tutorial eac= h, of 60-70 minutes. I think > > it > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 helps to be closer to an hour in length to hold the audience's attentio= n. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Then trying to have interactive discussion= s or explanations about how MPTCP is currently > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 implemented or should be implemented if it goes up= stream, e.g.: for MPTCP, we need to have > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 extra TCP Options, we need to support middleboxes,= we need to link subflows of the same > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 connection together, we need a scheduler, a PM, et= c. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 It's difficult to predict how interactive an audience will be. I've onl= y attended one Netdev > > Conference, > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 and it seemed like there were a lot more people with expertise and inte= rest in drivers, lower > > layers > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 (XDP, BPF, TC, netfilter), and network topology/simulation. Discussion = around middlebox support and > > the > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 userspace API might have more audience interaction. If we want to drive= a discussion, we could try > > to > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 strike a balance between topics for the broader audience and those with= more knowledge of TCP > > internals. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 (Hopefully some TCP internals people are still planning to attend) > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Of course, we should focus our discussions= on the upstreaming aspect, e.g. reducing the > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 footprint of MPTCP in the current TCP stack: what = are we allow to do, what not. It is linked > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 to many previous discussions we had on this ML, e.= g. why we need more indirect function calls > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 and how to reduce the impact, etc. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 The previous talk ([2]) had a section like this. I haven't watched it r= ecently, I should look at it > > again > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 to see what kind of questions the audience was asking. As you mentioned= above we should be careful > > to > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 have new content compared to the previous session. > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- If we have time, we could discuss about ho= w users could interact with MPTCP: enable it per > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 connection, control the path manager, maybe the sc= heduler, etc. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 What do you think about this? Feel free to comment= and even propose completely different > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 ideas! > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Thank you for outlining these ideas. I see that this topic is on our me= eting agenda so it will be > > good to > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 discuss the tutorial there. > > = > > = > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 [1] https://lists.01.org/pipermail/mptcp/2018-Marc= h/000379.html > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 [2] https://www.youtube.com/watch?v=3Dwftz2cU5SZs > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 [3] https://www.netdevconf.org/0x12/submit-proposa= l.html > > = > > = > > -- > > Mat Martineau > > Intel OTC > > = > > = > > = > > = > > -- > > Tessares SA > > Matthieu Baerts | R&D Engineer > > matthieu.baerts(a)tessares.net > > Tessares SA | Hybrid Access Solutions > > www.tessares.net 1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium > > = > > = > > _______________________________________________________________________= ______________________________________________________________________ > > DISCLAIMER. > > This email and any files transmitted with it are confidential and inten= ded solely for the use of the individual or entity to whom they are > > addressed. If you have received this email in error please notify the s= ystem manager. This message contains confidential information and is > > intended only for the individual named. If you are not the named addres= see you should not disseminate, distribute or copy this e-mail. Please > > notify the sender immediately by e-mail if you have received this e-mai= l by mistake and delete this e-mail from your system. If you are not > > the intended recipient you are notified that disclosing, copying, distr= ibuting or taking any action in reliance on the contents of this > > information is strictly prohibited. > > = > = > -- > Mat Martineau > Intel OTC --===============4519966401222979789==--