From Nsnam
Revision as of 14:52, 19 March 2010 by Jpelkey (Talk | contribs)

Jump to: navigation, search

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

This page summarizes the ongoing release planning for ns-3.8. The release manager is Josh Pelkey <jpelkey@gatech.edu>.

Tentative ns-3.8 Release Schedule

  1. January 27 -- ns-3.7 posted
  2. January 27 -- ns-3.8 Open phase begins
  3. March 8 -- Deadline for new feature merge
  4. March 8 -- Begin the phase of small feature development and bug fixing
  5. March 27 -- Small feature development and bug fixing ends
  6. March 27 -- Open phase ends
  7. March 27 -- Maintenance phase begins
  8. April 13 -- Maintenance phase ends
  9. April 13 -- Code freeze phase begins
  10. April 13 -- ns-3.8-RC1
  11. April 15 -- ns-3.8-RC2
  12. April 19 -- ns-3.8-RC3
  13. April 22 -- ns-3.8-RC4
  14. April 27 -- ns-3.8 posted
  15. April 27 -- Code freeze phase ends
  16. April 27 -- ns-3.9 Open phase begins

As described in the Roadmap there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.8 should contact Josh and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

  • A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests successfully on all of our target machines
  • A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to generate release notes and will be provided to maintainers if a code review is indicated)
  • Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the book of instructions a code review requiring positive acknowledgment by maintainers is indicated if:

  • Your proposed feature does not work with all models or on all platforms
  • Your feature changes pre-existing APIs
  • Your feature crosses maintainer boundaries

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:

  • Review the code that might be merged
  • Clean up the bug tracker: solve as much bugs as possible
  • Merge the new features that has +1 and from maintainers

After March 8th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:

  • Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted
  • Review the code to be merged for next releases
  • Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (March 27th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On April 13th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our goal will be to reduce the number of P1 bugs to zero before the release of ns-3.8.

We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.

ns-3.8 Features Merged

Topology read system (Inet/Orbis)

Matrix propagation loss model

MPI-based parallelization


Redo ASCII and pcap Traces

Gauss-Markov Mobility Model

Steady state random waypoint mobility model

802.11n block ack

Enhancements to src/core/random-variable.cc/h

Two ray ground radio propagation model

Move propagation models to src/common

Pareto rng constructors using scale and shape instead of mean and shape

Postponed Candidate Contributions

Chord/DHash DHT

Underwater Acoustic Network Device


  • Code: No available code for the moment
  • Developer: Tom Wambold
  • Status: waiting to the code to be ready to review

Internet stack roadmap

NAT traversal

The ns-3.8 Bug List

High Priority Blockers

blockers list

P1 Bugs

Bug 806 - TCP doesn't work over a CSMA link

  • Assigned to: ns-bugs
  • Probably only affects ns-3.7 release
  • Tom is working on a small test suite for this case

High Priority Non-Blockers

High priority non blockers

P2 Bugs with patches

Bug 772 - AODV is unable to correctly buffer packets waiting for route reply

  • Assigned to: Pavel Boyko
  • Patch available, needs review

Bug 810 - In TCP, Socket::GetSockName() does not return the local socket address

  • Assigned to: Josh Pelkey
  • Patch available, looks ready to go

Bug 794 - Ipv4Mask constructor for "/yy"-notation is wrong

  • Assigned to: Craig Dowell
  • +1 from Tom and Craig, looks ready to go

Bug 231 - SocketAddressTag needs to be removed from a packet before forwarding the packet to the user

  • Assigned to: Faker Moatamri
  • Possibly trivial now with RemovePacketTag API

Bug 778 - OLSR ignores specified outgoing interface in RouteOutput()

  • Assigned to: Gustavo J. A. M. Carneiro
  • Patch from Tom, Gustavo pretty much +1
  • looks ready to go


  • Assigned to: Gustavo J. A. M. Carneiro
  • looks ready to go

Bug 747 - Listening TCP socket closes on RST

  • Assigned to: Josh Pelkey
  • +1 from me, looks ready to go

Bug 748 - Cloned TCP socket uses wrong source address

  • Assigned to: Josh Pelkey
  • Patch proposal from Fabian Mauchle
  • need to look at this

Bug 555 - DCF immediate access bug

  • Assigned to: Mathieu Lacage
  • patch needs review

Bug 602 - WifiRemoteStation lacks information about the access class of outgoing packets

  • Assigned to: Mathieu Lacage
  • patch needs review
  • possibly fixed in changeset 0f012e7d9128

Bug 521 - Ipv4 global routing inefficient

  • Assigned to: Tom Henderson
  • I think this one was re-opened, and not sure if the patch is still valid
  • I know that Tom has mentioned he is working on this one

Bug 385 - Add a generic "sequence number" class

  • Assigned to: Mathieu Lacage
  • patch exists, but there is still some issues about implementation
  • tracing is important for this one

Bug 184 - GtkConfigStore do not support ConfigureDefault

  • Assigned to: Faker Moatamri
  • another oldie
  • Mathieu says, "This bug is now really about making GtkConfigStore do what ConfigStore already does and provide a GUI for the 'default' + 'global' values."
  • Faker just updated the patch (Feb. 16, 2010), needs review

P2 Bugs without patches

Bug 818 - TCP Socket implementation does not set ACK flag on retransmits

  • Assigned to: Josh Pelkey
  • Possible fix mentioned, but it causes crash in tcp test suite

Bug 822 - Default attributes in abstract base classes not working

  • Assigned to: Mathieu Lacage
  • Has test case to show bug
  • Possibly two bugs

Bug 812 - Assert when getting socket in RecvReply for AODV

  • Assigned to: Pavel Boyko
  • changed to P2 crit, as this is blocking some people's research
  • has example showing assert

Bug 796 - TCP bug in ns-3-dev branch : Crash detected during retesting of Chord on ns-3-dev branch

  • Assigned to: Craig Dowell
  • logs attached to this one
  • worked in ns-3.6 but not ns-3.7
  • possibly bug 806 fix fixed this

Bug 409 - Routing messages can exceed MTU, and fragmentation not supported

  • Assigned to: Mathieu Lacage
  • Quick fix available
  • IP fragmentation support for UDP is needed

Bug 631 - RealtimeSimulatorImpl not compatible with python bindings

  • Assigned to: Mathieu Lacage
  • lots of discussion here, no consensus it seems