Difference between revisions of "Ns-3.4"

From Nsnam
Jump to: navigation, search
(→‎The ns-3.4 High Priority Bug List)
Line 30: Line 30:
 
# March 18 -- ns-3.5 Open phase begins.
 
# March 18 -- ns-3.5 Open phase begins.
  
−
== The ns-3.4 High Priority Bug List ==  
+
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=63 63 flag needed in an internet node to distinguish routers from hosts]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=64 64 whether routing API needs to be split from Ipv4 API]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=74 74 Redundant routing table lookup for setting src addr of outoging IP packets]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=85 85 NetDevice::m_ifIndex not the same as Ipv4's ifIndex]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=101 101 random variable intialization]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=103 103 need an easy-to-use way to print and set the global seed for random variables]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=188 188 global routing does not handle ip aliasing]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=198 198 TcpSocketImpl doesn't send acks with data packets in two-way] transfers]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=215 215 Node names patch]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=219 219 Ipv4Interface is a poor API]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=222 222 Doxygen warnings in RC1]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=229 229 Inconsistent API definitions of the bounds in the API for RandomVariable subclasses]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341 Get unexpected dropped packets when using SetSendCallback with heavy traffic]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=370 370 ipv4-interface.h is installed]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=384 384 ipv4 API needs rework]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=407 407 OLSR is missing HNA support]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409 Routing messages can exceed MTU, and fragmentation not supported]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419 *Helper::SetAttribute* methods sometimes painful to use]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=424 424 TCP FIN notification callback needed]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=425 425 TCP FIN does not contain ACK]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=426 426 TCP: close does not send RST]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=427 427 TcpSocketImpl::Close calls ShutdownSend]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=434 434 build system revisions]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=438 438 csma helper hooks the transmit queue enqueue operation for pcap tracing]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=443 443 Net device pcap traces arent consistent with what tcpdump would display]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=458 458 socket attributes not hooked into the config namespace]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=465 465 examples/mixed-wireless.py does not work anymore]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=468 468 Test for possibly unreachable code-- please file a bug report, with a test case, if this is ever hit]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=489 489 ns-3-allinone inflexible WRT trace file location]
 +
Status:
 +
*[http://www.nsnam.org/bugzilla/show_bug.cgi?id=490 490 OnOffApplication: m_lastStartTime not set correctly]
 +
Status:
  
 
== Candidates for Merge into ns-3.4 ==
 
== Candidates for Merge into ns-3.4 ==

Revision as of 23:27, 6 February 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.

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.

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

Status:

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.

Build System Refactoring (bug 434)

http://www.nsnam.org/bugzilla/show_bug.cgi?id=434

  • Status: merged

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
  • Status: In release manager queue for a merge.


Object Naming Feature with Attribute/Config Integration (bug 215)

Tap Net Device (emulation) Support

Ipv4 refactoring

Tracing Consistency (pcap model for devices) (bug 443)

http://www.nsnam.org/bugzilla/show_bug.cgi?id=443

New drop tail queue (Bug 457)

http://www.nsnam.org/bugzilla/show_bug.cgi?id=457

  • Status: Waiting for review.

New Wifi AP Address Manager (Bug 471)

http://www.nsnam.org/bugzilla/show_bug.cgi?id=471

  • Status: waiting for review
  • (bug 425,426 and others) TCP close behavior not standards conformant

future releases

  • JSON/RPC proposal
    • Seen some review on the list, seems like this incarnation isn't quite mature enough at this stage for ns-3.4
  • Additional IPv6 Support;
  • 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 06:20, 5 February 2009 (UTC)

Retrieved from "https://www.nsnam.org/mediawiki/index.php?title=Ns-3.4&oldid=2327"