Re: [multipathtcp] Adding a new work item on MPTCP API

Hello,

On 09/11/16 - 10:21:42, philip.eardley@bt.com wrote:
> Following the earlier discussion, there is support to add a charter item as follows:
> <<RFC6897 defined an optional, basic application interface for MPTCP-aware applications, including a set of socket operations. Now there is more experience of how MPTCP is being used, the WG will re-visit this work, and consider adding more advanced socket operations. The document will be Informational.>>
> If you disagree with this being added, or suggest some mod to this item, please say.

I support this work as well.

But, I also agree with Mirja's comment that "socket operations" is not a
well-defined term. I guess, what has been meant was "socket options" - the
ones that are available in many operating systems.

I think the API should not limit itself to a specific way on how to
configure the stack (e.g., through socket-options, ioctl, netlink,...).
But rather be agnostic as to the technical details on how the higher
layer configures/controls the MPTCP-stack.

Christoph

> Thanks
> Phil & Yoshi
> 
> From: cpaasch@apple.com [mailto:cpaasch@apple.com]
> Sent: 31 July 2016 20:37
> To: Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com>
> Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org>
> Subject: Re: [multipathtcp] potential new work item on MPTCP API
> 
> 
> On Jul 26, 2016, at 7:35 AM, philip.eardley@bt.com<mailto:philip.eardley@bt.com> wrote:
> 
> Christoph,
> https://tools.ietf.org/html/rfc6897#section-5.3 is “Sockets Interface Extensions by the Basic MPTCP API”
> (also https://tools.ietf.org/html/rfc6897#appendix-A “Appendix A. Requirements on a Future Advanced MPTCP API”)
> 
> Ok, I see. Fair enough. Extension to RFC6897 seems fine to me then.
> 
> 
> Cheers,
> Christoph
> 
> 
> phil
> 
> From: cpaasch@apple.com<mailto:cpaasch@apple.com> [mailto:cpaasch@apple.com]
> Sent: 22 July 2016 09:48
> To: Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com<mailto:philip.eardley@bt.com>>
> Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>>
> Subject: Re: [multipathtcp] potential new work item on MPTCP API
> 
> Hello,
> 
> On Jul 21, 2016, at 5:43 PM, philip.eardley@bt.com<mailto:philip.eardley@bt.com> wrote:
> Yesterday Olivier presented about his & Benjamin’s recent work on MPTCP socket api. We didn’t have much discussion whether to add this to the charter. One comment was that any work should build on /reference RFC6897.
> https://www.ietf.org/proceedings/96/slides/slides-96-mptcp-4.pdf
> Please can you comment whether you see this as a useful work item, or you think it shouldn’t be worked on, or how it should be adapted to something you think the WG should work on.
> 
> yes, I think it is a very useful work item and am willing to contribute to this work.
> 
> I'm not sure whether this can be seen as an update to 6897. I'm under the impression that 6897 takes a different approach, giving users a high-level overview of how using MPTCP might look like to an application that is talking to a TCP-socket (which happens to end up using MPTCP).
> 
> Olivier's work seems to rather make MPTCP entirely explicit to the application. So, I think both works take a different approach.
> 
> 
> 
> To help prompt the discussion, here’s a very first version of some possible charter text
> RFC6897 defined an optional, basic application interface for MPTCP-aware applications, including a set of socket operations. Now there is more experience of how MPTCP is being used, the WG will re-visit this work, and consider adding more advanced socket operations.
> 
> RFC6897 was Informational – would this new Milestone be Informational or Experimental?
> 
> I think it should be Informational.
> 
> 
> Christoph
> 
> 
> 
> 
> Thanks
> phil
> 
> Philip Eardley
> Research and Innovation
> This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you've received this email in error, please let me know immediately on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp
> 

> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp