Add MPTCP entry from Nigel Williams
This commit is contained in:
parent
600ecca962
commit
67aee3b18f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48052
1 changed files with 73 additions and 0 deletions
|
@ -3490,4 +3490,77 @@
|
|||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
<project cat='proj'>
|
||||
<title>Multipath TCP for &os;</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>Nigel</given>
|
||||
<common>Williams</common>
|
||||
</name>
|
||||
<email>njwilliams@swin.edu.au</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://bitbucket.org/nw-swin/caia-mptcp-FreeBSD/">MPTCP for &os; Repository</url>
|
||||
<url href="http://caia.swin.edu.au/urp/newtcp/mptcp/">MPTCP for &os; Project Website</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>Multipath TCP (MPTCP) is an extension to TCP that allows
|
||||
for the use of multiple network interfaces on a standard TCP
|
||||
session. The addition of new addresses and scheduling of data
|
||||
across these occurs transparently from the perspective of the TCP
|
||||
application.</p>
|
||||
|
||||
<p>The goal of this project is to deliver an MPTCP kernel
|
||||
patch that interoperates with the reference MPTCP implementation,
|
||||
along with additional enhancements to aid network research.</p>
|
||||
|
||||
<p>A v0.51 release has been tagged in our repository, with
|
||||
some minor improvements over v0.5.</p>
|
||||
|
||||
<p>We have now removed much of the MPTCP code that was inside
|
||||
the functions <tt>tcp_do_segment</tt>, <tt>tcp_output</tt>, and
|
||||
other code used for standard TCP connections. The goal of this is
|
||||
to restrict the added MPTCP code to just MPTCP connections,
|
||||
leaving regular TCP connections using the existing code.</p>
|
||||
|
||||
<p>We are currently in the process of implementing a subflow
|
||||
socket buffer upcall and event processing. These will handle
|
||||
changes in subflow socket state, MP-signalling, and incoming
|
||||
data segments.</p>
|
||||
|
||||
<p>This also requires some re-working of the MP option
|
||||
processing, particularly how incoming DSN maps are parsed and
|
||||
stored for use during MP-layer reassembly.</p>
|
||||
|
||||
<p>We are also looking at how our changes might take advantage
|
||||
of the new TCP stack modularisation enhancements to create
|
||||
subflow-specific TCP functions.</p>
|
||||
</body>
|
||||
|
||||
<sponsor>
|
||||
The Cisco University Research Program Fund at Community
|
||||
Foundation Silicon Valley
|
||||
</sponsor>
|
||||
|
||||
<sponsor>
|
||||
The FreeBSD Foundation
|
||||
</sponsor>
|
||||
|
||||
<help>
|
||||
<task>
|
||||
<p>Complete the implementations of subflow event processing
|
||||
and new option parsing.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Update documentation and task lists.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
</report>
|
||||
|
|
Loading…
Reference in a new issue