draft-ietf-mptcp-experience-04.txt   draft-ietf-mptcp-experience-05.txt 
MPTCP Working Group O. Bonaventure MPTCP Working Group O. Bonaventure
Internet-Draft UCLouvain Internet-Draft UCLouvain
Intended status: Informational C. Paasch Intended status: Informational C. Paasch
Expires: October 3, 2016 Apple, Inc. Expires: January 9, 2017 Apple, Inc.
G. Detal G. Detal
Tessares Tessares
April 01, 2016 July 08, 2016
Use Cases and Operational Experience with Multipath TCP Use Cases and Operational Experience with Multipath TCP
draft-ietf-mptcp-experience-04 draft-ietf-mptcp-experience-05
Abstract Abstract
This document discusses both use cases and operational experience This document discusses both use cases and operational experience
with Multipath TCP in real world networks. It lists several with Multipath TCP in real world networks. It lists several
prominent use cases for which Multipath TCP has been considered and prominent use cases for which Multipath TCP has been considered and
is being used. It also gives insight to some heuristics and is being used. It also gives insight to some heuristics and
decisions that have helped to realize these use cases. decisions that have helped to realize these use cases.
Status of This Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 3, 2016. This Internet-Draft will expire on January 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Datacenters . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Datacenters . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Cellular/WiFi Offload . . . . . . . . . . . . . . . . . . 5 2.2. Cellular/WiFi Offload . . . . . . . . . . . . . . . . . . 5
2.3. Multipath TCP proxies . . . . . . . . . . . . . . . . . . 8 2.3. Multipath TCP proxies . . . . . . . . . . . . . . . . . . 9
3. Operational Experience . . . . . . . . . . . . . . . . . . . 9 3. Operational Experience . . . . . . . . . . . . . . . . . . . . 11
3.1. Middlebox interference . . . . . . . . . . . . . . . . . 9 3.1. Middlebox interference . . . . . . . . . . . . . . . . . . 11
3.2. Congestion control . . . . . . . . . . . . . . . . . . . 11 3.2. Congestion control . . . . . . . . . . . . . . . . . . . . 13
3.3. Subflow management . . . . . . . . . . . . . . . . . . . 12 3.3. Subflow management . . . . . . . . . . . . . . . . . . . . 13
3.4. Implemented subflow managers . . . . . . . . . . . . . . 12 3.4. Implemented subflow managers . . . . . . . . . . . . . . . 14
3.5. Subflow destination port . . . . . . . . . . . . . . . . 14 3.5. Subflow destination port . . . . . . . . . . . . . . . . . 16
3.6. Closing subflows . . . . . . . . . . . . . . . . . . . . 15 3.6. Closing subflows . . . . . . . . . . . . . . . . . . . . . 17
3.7. Packet schedulers . . . . . . . . . . . . . . . . . . . . 17 3.7. Packet schedulers . . . . . . . . . . . . . . . . . . . . 18
3.8. Segment size selection . . . . . . . . . . . . . . . . . 17 3.8. Segment size selection . . . . . . . . . . . . . . . . . . 19
3.9. Interactions with the Domain Name System . . . . . . . . 18 3.9. Interactions with the Domain Name System . . . . . . . . . 19
3.10. Captive portals . . . . . . . . . . . . . . . . . . . . . 19 3.10. Captive portals . . . . . . . . . . . . . . . . . . . . . 20
3.11. Stateless webservers . . . . . . . . . . . . . . . . . . 20 3.11. Stateless webservers . . . . . . . . . . . . . . . . . . . 21
3.12. Loadbalanced serverfarms . . . . . . . . . . . . . . . . 20 3.12. Loadbalanced serverfarms . . . . . . . . . . . . . . . . . 22
4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 21 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 5. Security Considerations . . . . . . . . . . . . . . . . . . . 24
6. Informative References . . . . . . . . . . . . . . . . . . . 22 6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 28 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 8. Informative References . . . . . . . . . . . . . . . . . . . . 27
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
Multipath TCP was standardized in [RFC6824] and five independant Multipath TCP was standardized in [RFC6824] and five independent
implementations have been developed implementations have been developed
[I-D.eardley-mptcp-implementations-survey]. As of September 2015, [I-D.eardley-mptcp-implementations-survey]. As of September 2015,
Multipath TCP has been or is being implemented on the following Multipath TCP has been or is being implemented on the following
platforms : platforms:
o Linux kernel [MultipathTCP-Linux] o Linux kernel [MultipathTCP-Linux]
o Apple iOS and MacOS [Apple-MPTCP] o Apple iOS and MacOS [Apple-MPTCP]
o Citrix load balancers o Citrix load balancers
o FreeBSD [FreeBSD-MPTCP] o FreeBSD [FreeBSD-MPTCP]
o Oracle o Oracle
skipping to change at page 3, line 45 skipping to change at page 4, line 15
Multipath TCP enabled devices. However, this particular Multipath Multipath TCP enabled devices. However, this particular Multipath
TCP implementation is currently only used to support a single TCP implementation is currently only used to support a single
application. Unfortunately, there is no public information about the application. Unfortunately, there is no public information about the
lessons learned from this large scale deployment. lessons learned from this large scale deployment.
Section 3 is organized as follows. Supporting the middleboxes was Section 3 is organized as follows. Supporting the middleboxes was
one of the difficult issues in designing the Multipath TCP protocol. one of the difficult issues in designing the Multipath TCP protocol.
We explain in Section 3.1 which types of middleboxes the Linux Kernel We explain in Section 3.1 which types of middleboxes the Linux Kernel
implementation of Multipath TCP supports and how it reacts upon implementation of Multipath TCP supports and how it reacts upon
encountering these. Section 3.2 summarises the MPTCP specific encountering these. Section 3.2 summarises the MPTCP specific
congestion controls that have been implemented. Section 3.3 and congestion controls that have been implemented. Section 3.3 to
Section 3.7 discuss heuristics and issues with respect to subflow Section 3.7 discuss heuristics and issues with respect to subflow
management as well as the scheduling across the subflows. management as well as the scheduling across the subflows.
Section 3.8 explains some problems that occurred with subflows having Section 3.8 explains some problems that occurred with subflows having
different Maximum Segment Size (MSS) values. Section 3.9 presents different Maximum Segment Size (MSS) values. Section 3.9 presents
issues with respect to content delivery networks and suggests a issues with respect to content delivery networks and suggests a
solution to this issue. Finally, Section 3.10 documents an issue solution to this issue. Finally, Section 3.10 documents an issue
with captive portals where MPTCP will behave suboptimally. with captive portals where MPTCP will behave suboptimally.
2. Use cases 2. Use cases
skipping to change at page 6, line 34 skipping to change at page 7, line 27
interface remains up [Cellnet12]. This implies that the cellular interface remains up [Cellnet12]. This implies that the cellular
interface can remain idle and battery capacity is preserved. When interface can remain idle and battery capacity is preserved. When
the WiFi interface fails, a new subflow is established over the the WiFi interface fails, a new subflow is established over the
cellular interface in order to preserve the established Multipath TCP cellular interface in order to preserve the established Multipath TCP
sessions. Compared to the backup mode described earlier, sessions. Compared to the backup mode described earlier,
measurements reported in [Cellnet12] indicate that this mode of measurements reported in [Cellnet12] indicate that this mode of
operation is characterised by a throughput drop while the cellular operation is characterised by a throughput drop while the cellular
interface is brought up and the subflows are reestablished. interface is brought up and the subflows are reestablished.
From a protocol viewpoint, [Cellnet12] discusses the problem posed by From a protocol viewpoint, [Cellnet12] discusses the problem posed by
the unreliability of the ADD_ADDR option and proposes a small the unreliability of the REMOVE_ADDR option and proposes a small
protocol extension to allow hosts to reliably exchange this option. protocol extension to allow hosts to reliably exchange this option.
It would be useful to analyze packet traces to understand whether the It would be useful to analyze packet traces to understand whether the
unreliability of the REMOVE_ADDR option poses an operational problem unreliability of the REMOVE_ADDR option poses an operational problem
in real deployments. in real deployments.
Another study of the performance of Multipath TCP in wireless Another study of the performance of Multipath TCP in wireless
networks was reported in [IMC13b]. This study uses laptops connected networks was reported in [IMC13b]. This study uses laptops connected
to various cellular ISPs and WiFi hotspots. It compares various file to various cellular ISPs and WiFi hotspots. It compares various file
transfer scenarios. [IMC13b] observes that 4-path MPTCP outperforms transfer scenarios. [IMC13b] observes that 4-path MPTCP outperforms
2-path MPTCP, especially for larger files. The comparison between 2-path MPTCP, especially for larger files. However, for three
LIA, OLIA and Reno does not reveal a significant performance congestion control algorithms (LIA, OLIA and Reno - see Section 3.2),
difference for file sizes smaller than 4MB. there is no significant performance difference for file sizes smaller
than 4MB.
A different study of the performance of Multipath TCP with two A different study of the performance of Multipath TCP with two
wireless networks is presented in [INFOCOM14]. In this study the two wireless networks is presented in [INFOCOM14]. In this study the two
networks had different qualities : a good network and a lossy networks had different qualities : a good network and a lossy
network. When using two paths with different packet loss ratios, the network. When using two paths with different packet loss ratios, the
Multipath TCP congestion control scheme moves traffic away from the Multipath TCP congestion control scheme moves traffic away from the
lossy link that is considered to be congested. However, [INFOCOM14] lossy link that is considered to be congested. However, [INFOCOM14]
documents an interesting scenario that is summarised in Figure 1. documents an interesting scenario that is summarised in Figure 1.
client ----------- path1 -------- server client ----------- path1 -------- server
skipping to change at page 16, line 28 skipping to change at page 17, line 37
MPTCP: closed | <------------------------ | MPTCP: closed | <------------------------ |
Sub: fin-wait-2 | | Sub: fin-wait-2 | |
| | | |
| subflow-FIN | | subflow-FIN |
MPTCP: closed | <------------------------ | subflow-close() MPTCP: closed | <------------------------ | subflow-close()
Sub: time-wait | subflow-ACK | Sub: time-wait | subflow-ACK |
(step 3) | ------------------------> | MPTCP: time-wait (step 3) | ------------------------> | MPTCP: time-wait
| | Sub: closed | | Sub: closed
| | | |
Figure 5: Multipath TCP may not be able to avoid time-wait state Figure 5: Multipath TCP may not be able to avoid time-wait state on
(even if enforced by the application). the subflow (indicated as "Sub
Figure 5 shows a very particular issue within Multipath TCP. Many Figure 5 shows a very particular issue within Multipath TCP. Many
high-performance applications try to avoid Time-Wait state by high-performance applications try to avoid Time-Wait state by
deferring the closure of the connection until the peer has sent a deferring the closure of the connection until the peer has sent a
FIN. That way, the client on the left of Figure 5 does a passive FIN. That way, the client on the left of Figure 5 does a passive
closure of the connection, transitioning from Close-Wait to Last-ACK closure of the connection, transitioning from Close-Wait to Last-ACK
and finally freeing the resources after reception of the ACK of the and finally freeing the resources after reception of the ACK of the
FIN. An application running on top of a Multipath TCP enabled Linux FIN. An application running on top of a Multipath TCP enabled Linux
kernel might also use this approach. The difference here is that the kernel might also use this approach. The difference here is that the
close() of the connection (Step 1 in Figure 5) only triggers the close() of the connection (Step 1 in Figure 5) only triggers the
skipping to change at page 21, line 21 skipping to change at page 23, line 5
indicating which MPTCP-session the subflow belongs to. As the token indicating which MPTCP-session the subflow belongs to. As the token
is a hash of the key, servers are not able to generate the token in is a hash of the key, servers are not able to generate the token in
such a way that the token can provide the necessary information to such a way that the token can provide the necessary information to
the loadbalancers which would allow them to route TCP subflows to the the loadbalancers which would allow them to route TCP subflows to the
appropriate server. [I-D.paasch-mptcp-loadbalancer] discusses this appropriate server. [I-D.paasch-mptcp-loadbalancer] discusses this
issue in detail and suggests two alternative MP_CAPABLE handshakes to issue in detail and suggests two alternative MP_CAPABLE handshakes to
overcome these. As of September 2015, it is not yet clear how MPTCP overcome these. As of September 2015, it is not yet clear how MPTCP
might accomodate such use-case to enable its deployment within might accomodate such use-case to enable its deployment within
loadbalanced serverfarms. loadbalanced serverfarms.
4. Conclusion 4. IANA Considerations
There are no IANA considerations in this informational document.
5. Security Considerations
The security considerations for Multipath TCP have already been
documented in [RFC6181], [RFC6182], [RFC6824] and [RFC7430].
6. Conclusion
In this document, we have documented a few years of experience with In this document, we have documented a few years of experience with
Multipath TCP. The different scientific publications that have been Multipath TCP. The different scientific publications that have been
summarised confirm that Multipath TCP works well in different use summarised confirm that Multipath TCP works well in different use
cases in today's Internet. None of the cited publications has cases in today's Internet. None of the cited publications has
identified major issues with Multipath TCP and its utilisation in the identified major issues with Multipath TCP and its utilisation in the
current Internet. Some of these publications list directions for current Internet. Some of these publications list directions for
future improvements that mainly affect the subflow managers and future improvements that mainly affect the subflow managers and
packet schedulers. These heuristics affect the performance of packet schedulers. These heuristics affect the performance of
Multipath TCP, but not the protocol itself. It is likely that these Multipath TCP, but not the protocol itself. It is likely that these
skipping to change at page 21, line 47 skipping to change at page 26, line 5
end-to-end deployment. This deployment uses Multipath TCP to support end-to-end deployment. This deployment uses Multipath TCP to support
fast handover between cellular and WiFi networks. A wider deployment fast handover between cellular and WiFi networks. A wider deployment
of Multipath TCP on servers seems to be blocked by the necessity to of Multipath TCP on servers seems to be blocked by the necessity to
support Multipath TCP on load balancers. Given the influence that support Multipath TCP on load balancers. Given the influence that
middleboxes had on the design of Multipath TCP, it is interesting to middleboxes had on the design of Multipath TCP, it is interesting to
note that the other industrial deployments use Multipath TCP inside note that the other industrial deployments use Multipath TCP inside
middleboxes. These middelboxes use Multipath TCP to efficiently middleboxes. These middelboxes use Multipath TCP to efficiently
combine several access links while still interacting with legacy TCP combine several access links while still interacting with legacy TCP
servers. servers.
5. Acknowledgements 7. Acknowledgements
This work was partially supported by the FP7-Trilogy2 project. We This work was partially supported by the FP7-Trilogy2 project. We
would like to thank all the implementers and users of the Multipath would like to thank all the implementers and users of the Multipath
TCP implementation in the Linux kernel. This document has benefited TCP implementation in the Linux kernel. This document has benefited
from the comments of John Ronan, Yoshifumi Nishida, Phil Eardley and from the comments of John Ronan, Yoshifumi Nishida, Phil Eardley and
Jaehyun Hwang. Jaehyun Hwang.
6. Informative References 8. Informative References
[Apple-MPTCP] [Apple-MPTCP]
Apple, Inc, ., "iOS - Multipath TCP Support in iOS 7", Apple, Inc, ., "iOS - Multipath TCP Support in iOS 7",
n.d., <https://support.apple.com/en-us/HT201373>. n.d., <https://support.apple.com/en-us/HT201373>.
[BBF-WT348] [BBF-WT348]
Fabregas (Ed), G., "WT-348 - Hybrid Access for Broadband Fabregas (Ed), G., "WT-348 - Hybrid Access for Broadband
Networks", Broadband Forum, contribution bbf2014.1139.04 , Networks", Broadband Forum, contribution bbf2014.1139.04 ,
June 2015. June 2015.
[CACM14] Paasch, C. and O. Bonaventure, "Multipath TCP", [CACM14] Paasch, C. and O. Bonaventure, "Multipath TCP",
Communications of the ACM, 57(4):51-57 , April 2014, Communications of the ACM, 57(4):51-57 , April 2014,
<http://inl.info.ucl.ac.be/publications/multipath-tcp>. <http://inl.info.ucl.ac.be/publications/multipath-tcp>.
[COMCOM2016] [COMCOM2016]
"Observing real Multipath TCP traffic", Computer "Observing real Multipath TCP traffic", Computer
Communications , April 2016, Communications , April 2016, <http://inl.info.ucl.ac.be/
<http://inl.info.ucl.ac.be/publications/ publications/observing-real-multipath-tcp-traffic>.
observing-real-multipath-tcp-traffic>.
[COMMAG2016] [COMMAG2016]
De Coninck, Q., Baerts, M., Hesmans, B., and O. De Coninck, Q., Baerts, M., Hesmans, B., and O.
Bonaventure, "Observing Real Smartphone Applications over Bonaventure, "Observing Real Smartphone Applications over
Multipath TCP", IEEE Communications Magazine , March 2016, Multipath TCP", IEEE Communications Magazine , March 2016,
<http://inl.info.ucl.ac.be/publications/observing-real- <http://inl.info.ucl.ac.be/publications/
smartphone-applications-over-multipath-tcp>. observing-real-smartphone-applications-over-multipath-
tcp>.
[CONEXT12] [CONEXT12]
Khalili, R., Gast, N., Popovic, M., Upadhyay, U., and J. Khalili, R., Gast, N., Popovic, M., Upadhyay, U., and J.
Leboudec, "MPTCP is not pareto-optimal performance issues Leboudec, "MPTCP is not pareto-optimal performance issues
and a possible solution", Proceedings of the 8th and a possible solution", Proceedings of the 8th
international conference on Emerging networking international conference on Emerging networking
experiments and technologies (CoNEXT12) , 2012. experiments and technologies (CoNEXT12) , 2012.
[CONEXT13] [CONEXT13]
Paasch, C., Khalili, R., and O. Bonaventure, "On the Paasch, C., Khalili, R., and O. Bonaventure, "On the
Benefits of Applying Experimental Design to Improve Benefits of Applying Experimental Design to Improve
Multipath TCP", Conference on emerging Networking Multipath TCP", Conference on emerging Networking
EXperiments and Technologies (CoNEXT) , December 2013, EXperiments and Technologies (CoNEXT) , December 2013, <ht
<http://inl.info.ucl.ac.be/publications/benefits-applying- tp://inl.info.ucl.ac.be/publications/
experimental-design-improve-multipath-tcp>. benefits-applying-experimental-design-improve-multipath-
tcp>.
[CONEXT15] [CONEXT15]
Hesmans, B., Detal, G., Barre, S., Bauduin, R., and O. Hesmans, B., Detal, G., Barre, S., Bauduin, R., and O.
Bonaventure, "SMAPP - Towards Smart Multipath TCP-enabled Bonaventure, "SMAPP - Towards Smart Multipath TCP-enabled
APPlications", Proc. Conext 2015, Heidelberg, Germany , APPlications", Proc. Conext 2015, Heidelberg, Germany ,
December 2015, <http://inl.info.ucl.ac.be/publications/ December 2015, <http://inl.info.ucl.ac.be/publications/
smapp-towards-smart-multipath-tcp-enabled-applications>. smapp-towards-smart-multipath-tcp-enabled-applications>.
[CSWS14] Paasch, C., Ferlin, S., Alay, O., and O. Bonaventure, [CSWS14] Paasch, C., Ferlin, S., Alay, O., and O. Bonaventure,
"Experimental Evaluation of Multipath TCP Schedulers", "Experimental Evaluation of Multipath TCP Schedulers",
SIGCOMM CSWS2014 workshop , August 2014. SIGCOMM CSWS2014 workshop , August 2014.
[Cellnet12] [Cellnet12]
Paasch, C., Detal, G., Duchene, F., Raiciu, C., and O. Paasch, C., Detal, G., Duchene, F., Raiciu, C., and O.
Bonaventure, "Exploring Mobile/WiFi Handover with Bonaventure, "Exploring Mobile/WiFi Handover with
Multipath TCP", ACM SIGCOMM workshop on Cellular Networks Multipath TCP", ACM SIGCOMM workshop on Cellular Networks
(Cellnet12) , 2012, (Cellnet12) , 2012, <http://inl.info.ucl.ac.be/
<http://inl.info.ucl.ac.be/publications/ publications/exploring-mobilewifi-handover-multipath-tcp>.
exploring-mobilewifi-handover-multipath-tcp>.
[DetalMSS] [DetalMSS]
Detal, G., "Adaptive MSS value", Post on the mptcp-dev Detal, G., "Adaptive MSS value", Post on the mptcp-dev
mailing list , September 2014, <https://listes- mailing list , September 2014, <https://
2.sipr.ucl.ac.be/sympa/arc/mptcp-dev/2014-09/ listes-2.sipr.ucl.ac.be/sympa/arc/mptcp-dev/2014-09/
msg00130.html>. msg00130.html>.
[FreeBSD-MPTCP] [FreeBSD-MPTCP]
Williams, N., "Multipath TCP For FreeBSD Kernel Patch Williams, N., "Multipath TCP For FreeBSD Kernel Patch
v0.5", n.d., <http://caia.swin.edu.au/urp/newtcp/mptcp>. v0.5", n.d., <http://caia.swin.edu.au/urp/newtcp/mptcp>.
[HotMiddlebox13] [HotMiddlebox13]
Hesmans, B., Duchene, F., Paasch, C., Detal, G., and O. Hesmans, B., Duchene, F., Paasch, C., Detal, G., and O.
Bonaventure, "Are TCP Extensions Middlebox-proof?", CoNEXT Bonaventure, "Are TCP Extensions Middlebox-proof?", CoNEXT
workshop HotMiddlebox , December 2013, workshop HotMiddlebox , December 2013, <http://
<http://inl.info.ucl.ac.be/publications/ inl.info.ucl.ac.be/publications/
are-tcp-extensions-middlebox-proof>. are-tcp-extensions-middlebox-proof>.
[HotMiddlebox13b] [HotMiddlebox13b]
Detal, G., Paasch, C., and O. Bonaventure, "Multipath in Detal, G., Paasch, C., and O. Bonaventure, "Multipath in
the Middle(Box)", HotMiddlebox'13 , December 2013, the Middle(Box)", HotMiddlebox'13 , December 2013, <http:/
<http://inl.info.ucl.ac.be/publications/ /inl.info.ucl.ac.be/publications/multipath-middlebox>.
multipath-middlebox>.
[HotNets] Raiciu, C., Pluntke, C., Barre, S., Greenhalgh, A., [HotNets] Raiciu, C., Pluntke, C., Barre, S., Greenhalgh, A.,
Wischik, D., and M. Handley, "Data center networking with Wischik, D., and M. Handley, "Data center networking with
multipath TCP", Proceedings of the 9th ACM SIGCOMM multipath TCP", Proceedings of the 9th ACM SIGCOMM
Workshop on Hot Topics in Networks (Hotnets-IX) , 2010, Workshop on Hot Topics in Networks (Hotnets-IX) , 2010,
<http://doi.acm.org/10.1145/1868447.1868457>. <http://doi.acm.org/10.1145/1868447.1868457>.
[I-D.boucadair-mptcp-max-subflow] [I-D.boucadair-mptcp-max-subflow]
Boucadair, M. and C. Jacquenet, "Negotiating the Maximum Boucadair, M. and C. Jacquenet, "Negotiating the Maximum
Number of Multipath TCP (MPTCP) Subflows", draft- Number of Multipath TCP (MPTCP) Subflows",
boucadair-mptcp-max-subflow-01 (work in progress), draft-boucadair-mptcp-max-subflow-02 (work in progress),
December 2015. May 2016.
[I-D.deng-mptcp-proxy] [I-D.deng-mptcp-proxy]
Lingli, D., Liu, D., Sun, T., Boucadair, M., and G. Lingli, D., Liu, D., Sun, T., Boucadair, M., and G.
Cauchie, "Use-cases and Requirements for MPTCP Proxy in Cauchie, "Use-cases and Requirements for MPTCP Proxy in
ISP Networks", draft-deng-mptcp-proxy-01 (work in ISP Networks", draft-deng-mptcp-proxy-01 (work in
progress), October 2014. progress), October 2014.
[I-D.eardley-mptcp-implementations-survey] [I-D.eardley-mptcp-implementations-survey]
Eardley, P., "Survey of MPTCP Implementations", draft- Eardley, P., "Survey of MPTCP Implementations",
eardley-mptcp-implementations-survey-02 (work in draft-eardley-mptcp-implementations-survey-02 (work in
progress), July 2013. progress), July 2013.
[I-D.hampel-mptcp-proxies-anchors] [I-D.hampel-mptcp-proxies-anchors]
Hampel, G. and T. Klein, "MPTCP Proxies and Anchors", Hampel, G. and T. Klein, "MPTCP Proxies and Anchors",
draft-hampel-mptcp-proxies-anchors-00 (work in progress), draft-hampel-mptcp-proxies-anchors-00 (work in progress),
February 2012. February 2012.
[I-D.ietf-dnsop-edns-client-subnet] [I-D.ietf-dnsop-edns-client-subnet]
Contavalli, C., Gaast, W., tale, t., and W. Kumari, Contavalli, C., Gaast, W., tale, t., and W. Kumari,
"Client Subnet in DNS Queries", draft-ietf-dnsop-edns- "Client Subnet in DNS Queries",
client-subnet-07 (work in progress), March 2016. draft-ietf-dnsop-edns-client-subnet-08 (work in progress),
April 2016.
[I-D.lhwxz-gre-notifications-hybrid-access] [I-D.lhwxz-gre-notifications-hybrid-access]
Leymann, N., Heidemann, C., Wasserman, M., Xue, L., and M. Leymann, N., Heidemann, C., Wasserman, M., Xue, L., and M.
Zhang, "GRE Notifications for Hybrid Access", draft-lhwxz- Zhang, "GRE Notifications for Hybrid Access",
gre-notifications-hybrid-access-01 (work in progress), draft-lhwxz-gre-notifications-hybrid-access-01 (work in
January 2015. progress), January 2015.
[I-D.lhwxz-hybrid-access-network-architecture] [I-D.lhwxz-hybrid-access-network-architecture]
Leymann, N., Heidemann, C., Wasserman, M., Xue, L., and M. Leymann, N., Heidemann, C., Wasserman, M., Xue, L., and M.
Zhang, "Hybrid Access Network Architecture", draft-lhwxz- Zhang, "Hybrid Access Network Architecture",
hybrid-access-network-architecture-02 (work in progress), draft-lhwxz-hybrid-access-network-architecture-02 (work in
January 2015. progress), January 2015.
[I-D.paasch-mptcp-loadbalancer] [I-D.paasch-mptcp-loadbalancer]
Paasch, C., Greenway, G., and A. Ford, "Multipath TCP Paasch, C., Greenway, G., and A. Ford, "Multipath TCP
behind Layer-4 loadbalancers", draft-paasch-mptcp- behind Layer-4 loadbalancers",
loadbalancer-00 (work in progress), September 2015. draft-paasch-mptcp-loadbalancer-00 (work in progress),
September 2015.
[I-D.paasch-mptcp-syncookies] [I-D.paasch-mptcp-syncookies]
Paasch, C., Biswas, A., and D. Haas, "Making Multipath TCP Paasch, C., Biswas, A., and D. Haas, "Making Multipath TCP
robust for stateless webservers", draft-paasch-mptcp- robust for stateless webservers",
syncookies-02 (work in progress), October 2015. draft-paasch-mptcp-syncookies-02 (work in progress),
October 2015.
[I-D.walid-mptcp-congestion-control] [I-D.walid-mptcp-congestion-control]
Walid, A., Peng, Q., Hwang, J., and S. Low, "Balanced Walid, A., Peng, Q., Hwang, J., and S. Low, "Balanced
Linked Adaptation Congestion Control Algorithm for MPTCP", Linked Adaptation Congestion Control Algorithm for MPTCP",
draft-walid-mptcp-congestion-control-04 (work in draft-walid-mptcp-congestion-control-04 (work in
progress), January 2016. progress), January 2016.
[I-D.wei-mptcp-proxy-mechanism] [I-D.wei-mptcp-proxy-mechanism]
Wei, X., Xiong, C., and E. Ed, "MPTCP proxy mechanisms", Wei, X., Xiong, C., and E. Ed, "MPTCP proxy mechanisms",
draft-wei-mptcp-proxy-mechanism-02 (work in progress), draft-wei-mptcp-proxy-mechanism-02 (work in progress),
skipping to change at page 25, line 29 skipping to change at page 30, line 26
[IMC11] Honda, M., Nishida, Y., Raiciu, C., Greenhalgh, A., [IMC11] Honda, M., Nishida, Y., Raiciu, C., Greenhalgh, A.,
Handley, M., and H. Tokuda, "Is it still possible to Handley, M., and H. Tokuda, "Is it still possible to
extend TCP?", Proceedings of the 2011 ACM SIGCOMM extend TCP?", Proceedings of the 2011 ACM SIGCOMM
conference on Internet measurement conference (IMC '11) , conference on Internet measurement conference (IMC '11) ,
2011, <http://doi.acm.org/10.1145/2068816.2068834>. 2011, <http://doi.acm.org/10.1145/2068816.2068834>.
[IMC13a] Detal, G., Hesmans, B., Bonaventure, O., Vanaubel, Y., and [IMC13a] Detal, G., Hesmans, B., Bonaventure, O., Vanaubel, Y., and
B. Donnet, "Revealing Middlebox Interference with B. Donnet, "Revealing Middlebox Interference with
Tracebox", Proceedings of the 2013 ACM SIGCOMM conference Tracebox", Proceedings of the 2013 ACM SIGCOMM conference
on Internet measurement conference , 2013, on Internet measurement conference , 2013, <http://
<http://inl.info.ucl.ac.be/publications/ inl.info.ucl.ac.be/publications/
revealing-middlebox-interference-tracebox>. revealing-middlebox-interference-tracebox>.
[IMC13b] Chen, Y., Lim, Y., Gibbens, R., Nahum, E., Khalili, R., [IMC13b] Chen, Y., Lim, Y., Gibbens, R., Nahum, E., Khalili, R.,
and D. Towsley, "A measurement-based study of MultiPath and D. Towsley, "A measurement-based study of MultiPath
TCP performance over wireless network", Proceedings of the TCP performance over wireless network", Proceedings of the
2013 conference on Internet measurement conference (IMC 2013 conference on Internet measurement conference (IMC
'13) , n.d., <http://doi.acm.org/10.1145/2504730.2504751>. '13) , n.d., <http://doi.acm.org/10.1145/2504730.2504751>.
[IMC13c] Pelsser, C., Cittadini, L., Vissicchio, S., and R. Bush, [IMC13c] Pelsser, C., Cittadini, L., Vissicchio, S., and R. Bush,
"From Paris to Tokyo on the suitability of ping to measure "From Paris to Tokyo on the suitability of ping to
latency", Proceedings of the 2013 conference on Internet measure latency", Proceedings of the 2013 conference on
measurement conference (IMC '13) , 2013, Internet measurement conference (IMC '13) , 2013,
<http://doi.acm.org/10.1145/2504730.2504765>. <http://doi.acm.org/10.1145/2504730.2504765>.
[INFOCOM14] [INFOCOM14]
Lim, Y., Chen, Y., Nahum, E., Towsley, D., and K. Lee, Lim, Y., Chen, Y., Nahum, E., Towsley, D., and K. Lee,
"Cross-Layer Path Management in Multi-path Transport "Cross-Layer Path Management in Multi-path Transport
Protocol for Mobile Devices", IEEE INFOCOM'14 , 2014. Protocol for Mobile Devices", IEEE INFOCOM'14 , 2014.
[IOS7] "Multipath TCP Support in iOS 7", January 2014, [IOS7] Apple, ., "Multipath TCP Support in iOS 7", January 2014,
<http://support.apple.com/kb/HT5977>. <http://support.apple.com/kb/HT5977>.
[KT] Seo, S., "KT's GiGA LTE", July 2015, [KT] Seo, S., "KT's GiGA LTE", July 2015, <https://
<https://www.ietf.org/proceedings/93/slides/slides-93- www.ietf.org/proceedings/93/slides/slides-93-mptcp-3.pdf>.
mptcp-3.pdf>.
[MBTest] Hesmans, B., "MBTest", 2013, [MBTest] Hesmans, B., "MBTest", 2013,
<https://bitbucket.org/bhesmans/mbtest>. <https://bitbucket.org/bhesmans/mbtest>.
[MPTCPBIB] [MPTCPBIB]
Bonaventure, O., "Multipath TCP - An annotated Bonaventure, O., "Multipath TCP - An annotated
bibliography", Technical report , April 2015, bibliography", Technical report , April 2015,
<https://github.com/obonaventure/mptcp-bib>. <https://github.com/obonaventure/mptcp-bib>.
[Mobicom15] [Mobicom15]
De Coninck, Q., Baerts, M., Hesmans, B., and O. De Coninck, Q., Baerts, M., Hesmans, B., and O.
Bonaventure, "Poster - Evaluating Android Applications Bonaventure, "Poster - Evaluating Android Applications
with Multipath TCP", Mobicom 2015 (Poster) , September with Multipath TCP", Mobicom 2015 (Poster) ,
2015. September 2015.
[MultipathTCP-Linux] [MultipathTCP-Linux]
Paasch, C., Barre, S., and . et al, "Multipath TCP Paasch, C., Barre, S., and . et al, "Multipath TCP
implementation in the Linux kernel", n.d., implementation in the Linux kernel", n.d.,
<http://www.multipath-tcp.org>. <http://www.multipath-tcp.org>.
[NSDI11] Wischik, D., Raiciu, C., Greenhalgh, A., and M. Handley, [NSDI11] Wischik, D., Raiciu, C., Greenhalgh, A., and M. Handley,
"Design, implementation and evaluation of congestion "Design, implementation and evaluation of congestion
control for Multipath TCP", In Proceedings of the 8th control for Multipath TCP", In Proceedings of the 8th
USENIX conference on Networked systems design and USENIX conference on Networked systems design and
implementation (NSDI11) , 2011. implementation (NSDI11) , 2011.
[NSDI12] Raiciu, C., Paasch, C., Barre, S., Ford, A., Honda, M., [NSDI12] Raiciu, C., Paasch, C., Barre, S., Ford, A., Honda, M.,
Duchene, F., Bonaventure, O., and M. Handley, "How Hard Duchene, F., Bonaventure, O., and M. Handley, "How Hard
Can It Be? Designing and Implementing a Deployable Can It Be? Designing and Implementing a Deployable
Multipath TCP", USENIX Symposium of Networked Systems Multipath TCP", USENIX Symposium of Networked Systems
Design and Implementation (NSDI12) , April 2012, Design and Implementation (NSDI12) , April 2012, <http://
<http://inl.info.ucl.ac.be/publications/how-hard-can-it- inl.info.ucl.ac.be/publications/
be-designing-and-implementing-deployable-multipath-tcp>. how-hard-can-it-be-designing-and-implementing-deployable-
multipath-tcp>.
[PAM2016] De Coninck, Q., Baerts, M., Hesmans, B., and O. [PAM2016] De Coninck, Q., Baerts, M., Hesmans, B., and O.
Bonaventure, "A First Analysis of Multipath TCP on Bonaventure, "A First Analysis of Multipath TCP on
Smartphones", 17th International Passive and Active Smartphones", 17th International Passive and Active
Measurements Conference (PAM2016) , March 2016, Measurements Conference (PAM2016) , March 2016, <http://
<http://inl.info.ucl.ac.be/publications/ inl.info.ucl.ac.be/publications/
first-analysis-multipath-tcp-smartphones>. first-analysis-multipath-tcp-smartphones>.
[PAMS2014] [PAMS2014]
Arzani, B., Gurney, A., Cheng, S., Guerin, R., and B. Loo, Arzani, B., Gurney, A., Cheng, S., Guerin, R., and B. Loo,
"Impact of Path Selection and Scheduling Policies on MPTCP "Impact of Path Selection and Scheduling Policies on MPTCP
Performance", PAMS2014 , 2014. Performance", PAMS2014 , 2014.
[PaaschPhD] [PaaschPhD]
Paasch, C., "Improving Multipath TCP", Ph.D. Thesis , Paasch, C., "Improving Multipath TCP", Ph.D. Thesis ,
November 2014, <http://inl.info.ucl.ac.be/publications/ November 2014, <http://inl.info.ucl.ac.be/publications/
improving-multipath-tcp>. improving-multipath-tcp>.
[Presto08] [Presto08]
Greenberg, A., Lahiri, P., Maltz, D., Parveen, P., and S. Greenberg, A., Lahiri, P., Maltz, D., Parveen, P., and S.
Sengupta, "Towards a Next Generation Data Center Sengupta, "Towards a Next Generation Data Center
Architecture - Scalability and Commoditization", ACM Architecture - Scalability and Commoditization", ACM
PRESTO 2008 , August 2008, PRESTO 2008 , August 2008,
<http://dl.acm.org/citation.cfm?id=1397732>. <http://dl.acm.org/citation.cfm?id=1397732>.
[RFC1812] Baker, F., Ed., "Requirements for IP Version 4 Routers", [RFC1812] Baker, F., Ed., "Requirements for IP Version 4 Routers",
RFC 1812, DOI 10.17487/RFC1812, June 1995, RFC 1812, DOI 10.17487/RFC1812, June 1995,
<http://www.rfc-editor.org/info/rfc1812>. <http://www.rfc-editor.org/info/rfc1812>.
[RFC1928] Leech, M., Ganis, M., Lee, Y., Kuris, R., Koblas, D., and [RFC1928] Leech, M., Ganis, M., Lee, Y., Kuris, R., Koblas, D., and
L. Jones, "SOCKS Protocol Version 5", RFC 1928, DOI L. Jones, "SOCKS Protocol Version 5", RFC 1928,
10.17487/RFC1928, March 1996, DOI 10.17487/RFC1928, March 1996,
<http://www.rfc-editor.org/info/rfc1928>. <http://www.rfc-editor.org/info/rfc1928>.
[RFC4987] Eddy, W., "TCP SYN Flooding Attacks and Common [RFC4987] Eddy, W., "TCP SYN Flooding Attacks and Common
Mitigations", RFC 4987, DOI 10.17487/RFC4987, August 2007, Mitigations", RFC 4987, DOI 10.17487/RFC4987, August 2007,
<http://www.rfc-editor.org/info/rfc4987>. <http://www.rfc-editor.org/info/rfc4987>.
[RFC6181] Bagnulo, M., "Threat Analysis for TCP Extensions for
Multipath Operation with Multiple Addresses", RFC 6181,
DOI 10.17487/RFC6181, March 2011,
<http://www.rfc-editor.org/info/rfc6181>.
[RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J. [RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J.
Iyengar, "Architectural Guidelines for Multipath TCP Iyengar, "Architectural Guidelines for Multipath TCP
Development", RFC 6182, DOI 10.17487/RFC6182, March 2011, Development", RFC 6182, DOI 10.17487/RFC6182, March 2011,
<http://www.rfc-editor.org/info/rfc6182>. <http://www.rfc-editor.org/info/rfc6182>.
[RFC6356] Raiciu, C., Handley, M., and D. Wischik, "Coupled [RFC6356] Raiciu, C., Handley, M., and D. Wischik, "Coupled
Congestion Control for Multipath Transport Protocols", RFC Congestion Control for Multipath Transport Protocols",
6356, DOI 10.17487/RFC6356, October 2011, RFC 6356, DOI 10.17487/RFC6356, October 2011,
<http://www.rfc-editor.org/info/rfc6356>. <http://www.rfc-editor.org/info/rfc6356>.
[RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, [RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure,
"TCP Extensions for Multipath Operation with Multiple "TCP Extensions for Multipath Operation with Multiple
Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013, Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013,
<http://www.rfc-editor.org/info/rfc6824>. <http://www.rfc-editor.org/info/rfc6824>.
[RFC7430] Bagnulo, M., Paasch, C., Gont, F., Bonaventure, O., and C.
Raiciu, "Analysis of Residual Threats and Possible Fixes
for Multipath TCP (MPTCP)", RFC 7430, DOI 10.17487/
RFC7430, July 2015,
<http://www.rfc-editor.org/info/rfc7430>.
[SIGCOMM11] [SIGCOMM11]
Raiciu, C., Barre, S., Pluntke, C., Greenhalgh, A., Raiciu, C., Barre, S., Pluntke, C., Greenhalgh, A.,
Wischik, D., and M. Handley, "Improving datacenter Wischik, D., and M. Handley, "Improving datacenter
performance and robustness with multipath TCP", performance and robustness with multipath TCP",
Proceedings of the ACM SIGCOMM 2011 conference , n.d., Proceedings of the ACM SIGCOMM 2011 conference , n.d.,
<http://doi.acm.org/10.1145/2018436.2018467>. <http://doi.acm.org/10.1145/2018436.2018467>.
[StrangeMbox] [StrangeMbox]
Bonaventure, O., "Multipath TCP through a strange Bonaventure, O., "Multipath TCP through a strange
middlebox", Blog post , January 2015, middlebox", Blog post , January 2015, <http://
<http://blog.multipath-tcp.org/blog/html/2015/01/30/ blog.multipath-tcp.org/blog/html/2015/01/30/
multipath_tcp_through_a_strange_middlebox.html>. multipath_tcp_through_a_strange_middlebox.html>.
[TMA2015] Hesmans, B., Tran Viet, H., Sadre, R., and O. Bonaventure, [TMA2015] Hesmans, B., Tran Viet, H., Sadre, R., and O. Bonaventure,
"A First Look at Real Multipath TCP Traffic", Traffic "A First Look at Real Multipath TCP Traffic", Traffic
Monitoring and Analysis , 2015, Monitoring and Analysis , 2015, <http://
<http://inl.info.ucl.ac.be/publications/ inl.info.ucl.ac.be/publications/
first-look-real-multipath-tcp-traffic>. first-look-real-multipath-tcp-traffic>.
[ietf88] Stewart, L., "IETF'88 Meeting minutes of the MPTCP working [ietf88] Stewart, L., "IETF'88 Meeting minutes of the MPTCP working
group", n.d., <http://tools.ietf.org/wg/mptcp/ group", n.d., <http://tools.ietf.org/wg/mptcp/
minutes?item=minutes-88-mptcp.html>. minutes?item=minutes-88-mptcp.html>.
[tracebox] [tracebox]
Detal, G. and O. Tilmans, "tracebox", 2013, Detal, G. and O. Tilmans, "tracebox", 2013,
<http://www.tracebox.org>. <http://www.tracebox.org>.
 End of changes. 43 change blocks. 
100 lines changed or deleted 125 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/