Ns-3.26: Difference between revisions
Line 14: | Line 14: | ||
To be determined | To be determined | ||
== TCP models == | |||
Natale Patriciello, Anh Nguyen, Tom Henderson, Matthieu Coudron, and Amir Modarresi are working on the following. | |||
1) Open tracker issues | |||
* 2263: Support processing multiple TCP options in 1 header | |||
* 2122: decouple TcpTxBuffer variables | |||
* 2264: Possibility to setup Initial Sequence Number | |||
* 1529: randomize TCP initial sequence number | |||
* 2285: loss of TCP 3-way handshake calls receive callback to fire | |||
* 1167: TCP socket deferring CLOSE forever | |||
* 2133: In TCP close procedure, assert fail when receive in FIN_WAIT_2 | |||
* 2278: in TcpSocketBase, need to advance NextTxSequence | |||
* 2256: TCPTxBuffer should be able to tell BytesInFlight | |||
* 2220: RAM usage reduction through reduction of retx events | |||
* 2214: TCP ScheduleNow for data transfer | |||
* 1783: experiencing drops during FastRec causes Tcp cw to blow up | |||
2) Try to merge as many TCP congestion control variants as are ready or nearly ready. | |||
* BIC | |||
* CUBIC | |||
* Vegas | |||
* Scalable | |||
* Veno | |||
* YeAH | |||
* Illinois | |||
* H-TCP: http://mailman.isi.edu/pipermail/ns-developers/2016-April/013541.html | |||
3) work on SACK: https://codereview.appspot.com/283880043/ | |||
* General Scoreboard | |||
* Tcp option SACK management | |||
* Tcp option SACK implementation | |||
MPTCP will not be merged for ns-3.26. | |||
== traffic-control module == | == traffic-control module == |
Revision as of 12:54, 16 April 2016
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
This page summarizes the release planning for ns-3.26 (planned for June 2016). The ns-3 release process is listed here and here.
Release goals
The following goals have been identified by maintainers.
Build system
To be determined
ns-3 core
To be determined
TCP models
Natale Patriciello, Anh Nguyen, Tom Henderson, Matthieu Coudron, and Amir Modarresi are working on the following.
1) Open tracker issues
- 2263: Support processing multiple TCP options in 1 header
- 2122: decouple TcpTxBuffer variables
- 2264: Possibility to setup Initial Sequence Number
- 1529: randomize TCP initial sequence number
- 2285: loss of TCP 3-way handshake calls receive callback to fire
- 1167: TCP socket deferring CLOSE forever
- 2133: In TCP close procedure, assert fail when receive in FIN_WAIT_2
- 2278: in TcpSocketBase, need to advance NextTxSequence
- 2256: TCPTxBuffer should be able to tell BytesInFlight
- 2220: RAM usage reduction through reduction of retx events
- 2214: TCP ScheduleNow for data transfer
- 1783: experiencing drops during FastRec causes Tcp cw to blow up
2) Try to merge as many TCP congestion control variants as are ready or nearly ready.
- BIC
- CUBIC
- Vegas
- Scalable
- Veno
- YeAH
- Illinois
- H-TCP: http://mailman.isi.edu/pipermail/ns-developers/2016-April/013541.html
3) work on SACK: https://codereview.appspot.com/283880043/
- General Scoreboard
- Tcp option SACK management
- Tcp option SACK implementation
MPTCP will not be merged for ns-3.26.
traffic-control module
Stefano Avallone (stavallo@unina.it) is leading ns-3.26 development for traffic control, and has the following goals:
- Add support for Byte Queue Limits (in progress)
- porting and polishing fq-codel (in progress)
- reviewing PIE contribution (in progress)
- introduce mq (a multi-queue queue disc configured by default on wifi, along with fq-codel)
- user priorities and QoS API
- provide a better solution for a couple of issues introduced by the requeue mechanism
lte module
To be determined
wifi module
To be determined
Release and development schedule
The following schedule is planned:
- May 11, 2016: New feature deadline.
- May 25, 2016: Planned code freeze date.
- June 1, 2016: Scheduled release date for ns-3.26
Help wanted
If you would like to help prepare the ns-3.26 release in some way, please contact Tom Henderson (tomhend@u.washington.edu).
Also, please check back at a later date as specific tasks may be listed here.