Difference between revisions of "Ns-3.4"

From Nsnam
Jump to: navigation, search
(Other Proposals)
(Candidates for Merge into ns-3.4)
Line 35: Line 35:
 
As you can see in the [[Roadmap]], we have identified several candidates for inclusion in ns-3.4.  As time passes and details become more evident, more status regarding the progress of these new features will be added.
 
As you can see in the [[Roadmap]], we have identified several candidates for inclusion in ns-3.4.  As time passes and details become more evident, more status regarding the progress of these new features will be added.
  
=== Near term merge items (December and early January) ===
+
=== Random Number Generator and RandomVariable Changes. ===
* Tap Net Device (emulation) Support;
+
* Removal of static APIs for drawing random numbers
* bug 215 Object Naming Feature with Attribute/Config Integration;
+
* New seeding API separates seeding functionality into a separate class
* bug 434 Build System Refactoring;
+
* Exposure of the run number and global seed to the attributes/config system
* (various bugs) Random Number Generator and RandomVariable Changes.
+
* Review is converging
* bug 443 Tracing Consistency (pcap model for devices);
+
* Cut over some examples into a "testing" or "validation" framework
+
  
=== Later merge items (end of January) ===
+
=== bug 215 Object Naming Feature with Attribute/Config Integration; ===
 +
* Named objects
 +
* Requires review
 +
 
 +
=== JSON-RPC Proposal ===
 +
 
 +
=== Tap Net Device (emulation) Support ===
 +
 
 +
=== bug 434 Build System Refactoring ===
 +
 
 +
=== bug 443 Tracing Consistency (pcap model for devices) ===
 +
 
 +
=== Cut over some examples into a "testing" or "validation" framework ==
 +
 
 +
 
 +
=== Later merge items (end of January / Early February) ===
 
* [http://www.nsnam.org/wiki/index.php/Current_Development#Ipv4_API.2C_routing.2C_cleanup IPv4 Routing Refactoring;]
 
* [http://www.nsnam.org/wiki/index.php/Current_Development#Ipv4_API.2C_routing.2C_cleanup IPv4 Routing Refactoring;]
 
* Additional IPv6 Support;
 
* Additional IPv6 Support;
 
* (bug 425,426 and others) TCP close behavior not standards conformant
 
* (bug 425,426 and others) TCP close behavior not standards conformant
  
=== Other Proposals ===
+
 
* Cooperative ns-3 simulation with third party software via JSON-RPC
+
 
  
 
=== TBD (no commitments yet from anyone to work on them) ===
 
=== TBD (no commitments yet from anyone to work on them) ===

Revision as of 19:14, 21 January 2009

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

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

The ns-3.4 Release

This page summarizes the ongoing release planning for the Fourth stable release of ns-3.

ns-3-dev is scheduled to enter the open phase for ns-3.4 on December 17, 2009. Until then, checkins of new features are forbidden.

The Release Manager

The release manager is Raj Bhattacharjea.

The ns-3.4 Release Schedule

ns-3 releases are based on date-driven schedules as opposed to feature-driven schedules. We decide on an approximate release date and then the release manager works backward to define windows during which time certain activites related to the release can happen. This was done for ns-3.3 and the important milestones for that release can be found here.

  1. December 17, 2008 -- ns-3.4 Open phase begins.
  2. January 20 -- Recommended cutoff for new feature submission;
  3. January 27 -- Deadline for new feature submissions that require design review;
  4. February 3 -- Approved new feature ready-for-merge deadline;
  5. February 3 -- Late merge period begins (Merge Week Begins);
  6. February 10 -- Late merge period ends;
  7. February 10 -- Open phase ends;
  8. February 10 -- Maintenance phase begins;
  9. March 1 -- Maintenance phase ends;
  10. March 1 -- Code freeze phase begins;
  11. March 2 -- ns-3.4-RC1;
  12. March 5 -- ns-3.4-RC2;
  13. March 9 -- ns-3.4-RC3;
  14. March 12 -- ns-3.4-RC4;
  15. March 16 -- ns-3.4-RC5;
  16. March 17 -- ns-3.4-RC6;
  17. March 18 -- ns-3.4 posted;
  18. March 18 -- Code freeze phase ends;
  19. March 18 -- ns-3.5 Open phase begins.

Candidates for Merge into ns-3.4

As you can see in the Roadmap, we have identified several candidates for inclusion in ns-3.4. As time passes and details become more evident, more status regarding the progress of these new features will be added.

Random Number Generator and RandomVariable Changes.

  • Removal of static APIs for drawing random numbers
  • New seeding API separates seeding functionality into a separate class
  • Exposure of the run number and global seed to the attributes/config system
  • Review is converging

bug 215 Object Naming Feature with Attribute/Config Integration;

  • Named objects
  • Requires review

JSON-RPC Proposal

Tap Net Device (emulation) Support

bug 434 Build System Refactoring

bug 443 Tracing Consistency (pcap model for devices)

= Cut over some examples into a "testing" or "validation" framework

Later merge items (end of January / Early February)



TBD (no commitments yet from anyone to work on them)

  • Perfect/Global ARP;
  • bug 231 Packet Tag Use Problems;
  • Packet Fragmentation;
  • Netfilter Hooks;
  • bug 190 : NS_LOG_APPEND_CONTEXT for the internet stack
  • bug 407 OLSR HNA support
  • bug 424 socket API
  • bug 341 setsendcallback problems



Craigdo 21:54, 12 December 2008 (UTC)