Main.Release86 History
Hide minor edits - Show changes to output
Changed lines 16-17 from:
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification.
to:
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification (RFC6824).
Changed line 19 from:
* Multiplexing the data among the subflows (thus increasing the bandwidth)
to:
* Multiplexing the data among the subflows (thus increasing the bandwidth) with the coupled congestion control from %newwin%[[https://datatracker.ietf.org/doc/rfc6356/|RFC6356]] or %newwin%[[https://datatracker.ietf.org/doc/draft-khalili-mptcp-congestion-control/|olia]]
Changed line 46 from:
Do you have a mobile phone with Android? [[http://multipath-tcp.org/pmwiki.php?n=Users.Android | Check this out]] on how to install MPTCP on your Android.
to:
Do you have a mobile phone with Android? %newwin%[[http://multipath-tcp.org/pmwiki.php?n=Users.Android | Check this out]] on how to install MPTCP on your Android.
Added lines 44-46:
Do you have a mobile phone with Android? [[http://multipath-tcp.org/pmwiki.php?n=Users.Android | Check this out]] on how to install MPTCP on your Android.
Changed line 43 from:
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the %newwin%[[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
to:
Further, there are pre-compiled packages for Ubuntu Quantal (amd64) and Debian (amd64 or i386) available in the %newwin%[[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Changed line 8 from:
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will be maintained until the next release with bugfixes. However, no new features or performance improvements will be added to the releases.
to:
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will be maintained until the next release with bugfixes. However, no new features or performance improvements will be added to the individual releases. For new features/improvements you will have to wait for the next release :)
Changed line 5 from:
Thus, since the IETF 86 in Orlando the MultiPath TCP developers will make periodic releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before the IETF meeting.
to:
Thus, since the IETF 86 in Orlando the MultiPath TCP developers will make periodic releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before each IETF meeting.
Changed line 55 from:
Since the beginning of this project (2008), we received many contributions from different people.
to:
Since the beginning of this project (around 2008), we received many contributions from different people.
Changed lines 18-19 from:
to:
* Creating new subflows
* Multiplexing the data among the subflows (thus increasing the bandwidth)
* Handing traffic over from one subflow to another (resilience to failure)
* Adding/Removing IP-Addresses (thus it supports mobile hosts)
* Most middleboxes are supported (segment splitting, coalescing, payload-rewriting)
A list of the currently unsupported features:
* Multiplexing the data among the subflows (thus increasing the bandwidth)
* Handing traffic over from one subflow to another (resilience to failure)
* Adding/Removing IP-Addresses (thus it supports mobile hosts)
* Most middleboxes are supported (segment splitting, coalescing, payload-rewriting)
A list of the currently unsupported features:
Changed line 31 from:
* Support for payload-modifying middleboxes is not 100% stable.
to:
* Validating the support of middleboxes to be 100% sure.
Changed line 41 from:
Although this is a stable release of MPTCP, bugs may always exist. If you encounter a bug, please contact us on the %newwin%[[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
to:
Although this is a stable release, bugs may always exist. If you encounter a bug, please contact us on the %newwin%[[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
Changed line 51 from:
Sébastien Barré (UCLouvain, now working at Thelis)\\
to:
Sébastien Barré (UCLouvain, now at Thelis)\\
Changed lines 25-26 from:
to:
\\
Changed lines 37-38 from:
to:
\\
Changed line 44 from:
to:
\\
Changed lines 12-13 from:
to:
! MPTCP v0.86 Release
Changed line 12 from:
! MPTCP v0.86 Release
to:
!! MPTCP v0.86 Release
Changed lines 1-2 from:
!! MPTCP periodic releases
to:
!!! MPTCP periodic releases
Changed lines 10-12 from:
!
to:
\\
\\
! MPTCP v0.86 Release
\\
! MPTCP v0.86 Release
Changed lines 3-10 from:
As the official MPTCP specification has now been published in %newwin%[[https://datatracker.ietf.org/doc/rfc6824/ | RFC 6824]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the
to:
The MPTCP specification has now been published in %newwin%[[https://datatracker.ietf.org/doc/rfc6824/ | RFC 6824]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
Thus, since the IETF 86 in Orlando the MultiPath TCP developers will make periodic releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before the IETF meeting.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will be maintained until the next release with bugfixes. However, no new features or performance improvements will be added to the releases.
Thus, since the IETF 86 in Orlando the MultiPath TCP developers will make periodic releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before the IETF meeting.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will be maintained until the next release with bugfixes. However, no new features or performance improvements will be added to the releases.
Changed line 17 from:
to:
Listing all supported features would be too long. Thus, here a list of the currently unsupported features:
Changed lines 5-10 from:
As the official MPTCP specification has now been published in [[https://datatracker.ietf.org/doc/rfc6824/ | RFC 6824]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
to:
As the official MPTCP specification has now been published in %newwin%[[https://datatracker.ietf.org/doc/rfc6824/ | RFC 6824]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the %newwin%[[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
Changed lines 31-36 from:
Or, in zip-format through [[https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip | this link ]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
to:
Or, in zip-format through %newwin%[[https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip | this link ]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the %newwin%[[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the %newwin%[[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Changed lines 39-40 from:
Although this is a stable release of MPTCP, bugs may always exist. If you encounter a bug, please contact us on the [[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
to:
Although this is a stable release of MPTCP, bugs may always exist. If you encounter a bug, please contact us on the %newwin%[[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
Changed line 67 from:
Have a look [[http://multipath-tcp.org/mptcp_stats/authors.html | here]] for a more detailed view of all contributors.
to:
Have a look %newwin%[[http://multipath-tcp.org/mptcp_stats/authors.html | here]] for a more detailed view of all contributors.
Changed lines 65-67 from:
Brandon Heller (Stanford University)\\
to:
Brandon Heller (Stanford University)
Have a look [[http://multipath-tcp.org/mptcp_stats/authors.html | here]] for a more detailed view of all contributors.
Have a look [[http://multipath-tcp.org/mptcp_stats/authors.html | here]] for a more detailed view of all contributors.
Changed lines 49-65 from:
Sébastien Barré (UCLouvain, now working at Thelis)
Christoph Paasch (UCLouvain)
Gregory Detal (UCLouvain)
Jakko Korkeaniemi (Aalto University)
Mihai P. Andrei (Intel)
Fabien Duchêne (UCLouvain)
Andreas Seelinger (RWTH Aachen)
Stefan Sicleru (Intel)
Lavkesh Lahngir
Catalin Nicutar (PUB Bucharest)
Andrei Maruseac (Intel)
Andreas Ripke (NEC)
Vlad Dogaru (Intel)
Octavian Purdila (Intel)
Niels Laukens (VRT Belgium)
John Ronan (TSSG)
Brandon Heller (Stanford University)
Christoph Paasch (UCLouvain)
Gregory Detal (UCLouvain)
Jakko Korkeaniemi (Aalto University)
Mihai P. Andrei (Intel)
Fabien Duchêne (UCLouvain)
Andreas Seelinger (RWTH Aachen)
Stefan Sicleru (Intel)
Lavkesh Lahngir
Catalin Nicutar (PUB Bucharest)
Andrei Maruseac (Intel)
Andreas Ripke (NEC)
Vlad Dogaru (Intel)
Octavian Purdila (Intel)
Niels Laukens (VRT Belgium)
John Ronan (TSSG)
Brandon Heller (Stanford University)
to:
Sébastien Barré (UCLouvain, now working at Thelis)\\
Christoph Paasch (UCLouvain)\\
Gregory Detal (UCLouvain)\\
Jakko Korkeaniemi (Aalto University)\\
Mihai P. Andrei (Intel)\\
Fabien Duchêne (UCLouvain)\\
Andreas Seelinger (RWTH Aachen)\\
Stefan Sicleru (Intel)\\
Lavkesh Lahngir\\
Catalin Nicutar (PUB Bucharest)\\
Andrei Maruseac (Intel)\\
Andreas Ripke (NEC)\\
Vlad Dogaru (Intel)\\
Octavian Purdila (Intel)\\
Niels Laukens (VRT Belgium)\\
John Ronan (TSSG)\\
Brandon Heller (Stanford University)\\
Christoph Paasch (UCLouvain)\\
Gregory Detal (UCLouvain)\\
Jakko Korkeaniemi (Aalto University)\\
Mihai P. Andrei (Intel)\\
Fabien Duchêne (UCLouvain)\\
Andreas Seelinger (RWTH Aachen)\\
Stefan Sicleru (Intel)\\
Lavkesh Lahngir\\
Catalin Nicutar (PUB Bucharest)\\
Andrei Maruseac (Intel)\\
Andreas Ripke (NEC)\\
Vlad Dogaru (Intel)\\
Octavian Purdila (Intel)\\
Niels Laukens (VRT Belgium)\\
John Ronan (TSSG)\\
Brandon Heller (Stanford University)\\
Changed lines 14-15 from:
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification. As the list of unsupported features is much shorter, here it is:
to:
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification.
A list of the currently unsupported features is:
A list of the currently unsupported features is:
Changed lines 24-27 from:
to:
!!!! Get it!
Changed lines 34-65 from:
to:
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
!!!! Reporting Bugs / Asking Questions
Although this is a stable release of MPTCP, bugs may always exist. If you encounter a bug, please contact us on the [[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
Feel free to send an e-mail to the [[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List in case you have problems installing or using MPTCP.
!!!! Contributors
Since the beginning of this project (2008), we received many contributions from different people.
Here is the exhaustive list (ordered by number of commits).
Sébastien Barré (UCLouvain, now working at Thelis)
Christoph Paasch (UCLouvain)
Gregory Detal (UCLouvain)
Jakko Korkeaniemi (Aalto University)
Mihai P. Andrei (Intel)
Fabien Duchêne (UCLouvain)
Andreas Seelinger (RWTH Aachen)
Stefan Sicleru (Intel)
Lavkesh Lahngir
Catalin Nicutar (PUB Bucharest)
Andrei Maruseac (Intel)
Andreas Ripke (NEC)
Vlad Dogaru (Intel)
Octavian Purdila (Intel)
Niels Laukens (VRT Belgium)
John Ronan (TSSG)
Brandon Heller (Stanford University)
!!!! Reporting Bugs / Asking Questions
Although this is a stable release of MPTCP, bugs may always exist. If you encounter a bug, please contact us on the [[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List.
Feel free to send an e-mail to the [[https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev | mptcp-dev]] Mailing-List in case you have problems installing or using MPTCP.
!!!! Contributors
Since the beginning of this project (2008), we received many contributions from different people.
Here is the exhaustive list (ordered by number of commits).
Sébastien Barré (UCLouvain, now working at Thelis)
Christoph Paasch (UCLouvain)
Gregory Detal (UCLouvain)
Jakko Korkeaniemi (Aalto University)
Mihai P. Andrei (Intel)
Fabien Duchêne (UCLouvain)
Andreas Seelinger (RWTH Aachen)
Stefan Sicleru (Intel)
Lavkesh Lahngir
Catalin Nicutar (PUB Bucharest)
Andrei Maruseac (Intel)
Andreas Ripke (NEC)
Vlad Dogaru (Intel)
Octavian Purdila (Intel)
Niels Laukens (VRT Belgium)
John Ronan (TSSG)
Brandon Heller (Stanford University)
Changed lines 5-10 from:
As the official MPTCP specification has now been published in [[RFC 6824 || https://datatracker.ietf.org/doc/rfc6824/]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[github | https://github.com/multipath-tcp/mptcp]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[
to:
As the official MPTCP specification has now been published in [[https://datatracker.ietf.org/doc/rfc6824/ | RFC 6824]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[https://github.com/multipath-tcp/mptcp | github]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
Changed lines 30-33 from:
Or, in zip-format through [[this link | https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[apt-repository || http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[
to:
Or, in zip-format through [[https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip | this link ]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository | apt-repository]].
Changed lines 16-20 from:
to:
* Hardware-offloading (TSO/LRO) - Code is (almost) ready. It will be released in v0.87
* TCP sendfile - Code is (almost) ready. It will be released in v0.87
* 64-bit Data Sequence Numbers and Data Acks are not supported.
* Support for NFS is not stable (needs more testing).
* Support for payload-modifying middleboxes is not 100% stable.
* TCP sendfile - Code is (almost) ready. It will be released in v0.87
* 64-bit Data Sequence Numbers and Data Acks are not supported.
* Support for NFS is not stable (needs more testing).
* Support for payload-modifying middleboxes is not 100% stable.
Added lines 1-33:
!! MPTCP periodic releases
Since the IETF 86 in Orlando the MultiPath TCP developpers will make again regular releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before the IETF meeting.
As the official MPTCP specification has now been published in [[RFC 6824 || https://datatracker.ietf.org/doc/rfc6824/]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[github | https://github.com/multipath-tcp/mptcp]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
!! MPTCP v0.86 Release
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification. As the list of unsupported features is much shorter, here it is:
* Hardware-offloading (TSO/LRO) - Code is (almost) ready. It will be released in v0.87
* TCP sendfile - Code is (almost) ready. It will be released in v0.87
* 64-bit Data Sequence Numbers and Data Acks are not supported.
* Support for NFS is not stable (needs more testing).
* Support for payload-modifying middleboxes is not 100% stable.
All the rest is supported in MPTCP.
MPTCP v0.86 is available through git:
@@git clone --depth=1 -b mptcp_v0.86 git://github.com/multipath-tcp/mptcp@@
Or, in zip-format through [[this link | https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[apt-repository || http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository]].
Since the IETF 86 in Orlando the MultiPath TCP developpers will make again regular releases of MPTCP's Linux Kernel implementation. Each release will be published shortly before the IETF meeting.
As the official MPTCP specification has now been published in [[RFC 6824 || https://datatracker.ietf.org/doc/rfc6824/]]. The Linux Kernel implementation of MPTCP has always been following very closely the MPTCP draft and has been stabilized a lot over the last months.
With the new release schedule we want to give people a "stable point" of the MPTCP implementation. The releases will be available on the [[github | https://github.com/multipath-tcp/mptcp]], at branch @@mptcp_v0.XX@@ (XX being the number of the IETF meeting which will follow the MPTCP release) . The releases will receive a limited maintenance, namely fixing urgent bugs in the release. However, no new features or performance improvements will be added to the releases.
!! MPTCP v0.86 Release
The MPTCP v0.86 release is based on Linux Kernel v3.5.7. It supports almost all features of the MPTCP specification. As the list of unsupported features is much shorter, here it is:
* Hardware-offloading (TSO/LRO) - Code is (almost) ready. It will be released in v0.87
* TCP sendfile - Code is (almost) ready. It will be released in v0.87
* 64-bit Data Sequence Numbers and Data Acks are not supported.
* Support for NFS is not stable (needs more testing).
* Support for payload-modifying middleboxes is not 100% stable.
All the rest is supported in MPTCP.
MPTCP v0.86 is available through git:
@@git clone --depth=1 -b mptcp_v0.86 git://github.com/multipath-tcp/mptcp@@
Or, in zip-format through [[this link | https://github.com/multipath-tcp/mptcp/archive/mptcp_v0.86.zip]].
Further, there are pre-compiled packages for Ubuntu Quantal (amd64), Debian (amd64 or i386) available in the [[apt-repository || http://multipath-tcp.org/pmwiki.php?n=Users.AptRepository]].