Re: [multipathtcp] potential new work item on MPTCP API

["Scharf, Michael (Nokia - DE)" <[e-mail]>]

As author of RFC 6897 I'd be fine with revisiting that document as some aspects may be a bit outdated. I have not closely followed MPTCP recently but I'd assume that parts of RFC 6897 are still valid.

Michael



From: multipathtcp [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Thursday, July 21, 2016 5:43 PM
To: [e-mail]
Subject: [multipathtcp] potential new work item on MPTCP API

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.

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?

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