Ns-3.9

From Nsnam
Jump to navigation Jump to search

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 ongoing release planning for ns-3.9. We are seeking a volunteer for release manager for the final release stages. Josh Pelkey and Tom Henderson are acting release managers at this time.

Tentative Release Schedule

  1. May 3 -- ns-3.8 posted; ns-3.9 Open phase begins
  2. June 16 -- Deadline for proposing major new features to be merged; begin the phase of small feature development and bug fixing
  3. June 25 -- Deadline for merge of major features identified on the release page
  4. July 20 -- Small feature development and bug fixing ends; Maintenance phase begins
  5. August 6 -- Maintenance phase ends, code freeze phase begins; only P1 critical blockers and documentation

beyond this date

  1. August 9 -- First release candidate (ns-3.9 RC1)
  2. August 13 -- Documentation freeze (manuals/tutorials/Doxygen)
  3. August 18 -- ns-3.9 posted, ns-3.10 phase begins

Release status

New feature merges

Already merged:

Likely for ns-3.10:

Minor feature merges

Merged:

  • RecvIfIndex (issue 671)
  • Generic sequence number class (issue 385)
  • Issue 938: Add SO_BROADCAST socket option

Wait for ns-3.10:

  • API for TOS bytes (issue 897) may wait for netfilter support
  • Class name rename Scalar->Dimensionless (issue 445)
  • NetAnim trace hooks for wireless (patch in preparation)

Critical issues/bugs

  • Core/bindings:
    • 956 Bindings failure in core (traced-value) with older gcc
  • Point to Point:
    • 948 PointToPointNetDevice does not keep track of destination addresses
    • 949 Node::NonPromiscReceiveFromDevice reports a meaningless destination address to user callbacks
    • 950 PointToPointNetDevice says promisc support is not implemented but it is
  • InternetStack
    • 969 No SocketList is present in UdpL4Protocol class
    • 942 ipv4-raw-socket-impl should listen more than one protocol

Documentation

Features that may slip

The following features are in danger of slipping to ns-3.10 or later:

  • VANET mobility model (no reviews)
  • TCP Vegas (blocked by lack of progress on TCP congestion control architecture)
  • Chord/DHT (authors are planning to revise code based on comments)
  • app store and build system refactoring
  • remove ./waf --regression