Nsnam - User contributions [en]

Ns-3.12

2011-06-01T17:55:46Z

Jpelkey: /* Candidate Contributions for Inclusion in ns-3.12 */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.12. No release manager is named yet.

= Proposed Release Schedule =

# May 25 -- ns-3.11 posted, ns-3.12 open phase begins.
# August/September timeframe: ns-3.12 release

More schedule details will be posted soon. Please see [[Release Process]] concerning general aspects of the release schedule.

= Candidate Contributions for Inclusion in ns-3.12 =

* [http://codereview.appspot.com/4517125/ BRITE Integration]
** insufficient reviews
* [http://codereview.appspot.com/2104052/show Virtual Access Point (VAP) for WiFi]
** insufficient reviews
* [http://codereview.appspot.com/2135046/show GetRelativeVelocity() for MobilityModel]
** insufficient reviews
* [http://codereview.appspot.com/2173042/show PhySimWifi]
** insufficient reviews
* [http://codereview.appspot.com/2334041/show thread-safe implementation of ScheduleWithContext]
* [http://codereview.appspot.com/1587041/show simple wireless models]
* [http://codereview.appspot.com/1055041/show Jamming model]
* [http://codereview.appspot.com/850045/show MPLS]
* [http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html TCP Vegas] (blocked by lack of progress on TCP congestion control architecture)
* [http://codereview.appspot.com/3374041/ NetAnim trace hooks for wireless]
** needs to be updated for modularity

= ns-3.12 Features Merged =

To be listed here.

= The ns-3.12 Bug List =

* [http://codereview.appspot.com/4440051/ IP fragmentation] (bugs 1100, 1102)

= Feature requests =

* make spectrum model compatible with ns-3 WiFi
* ns-2 packet UID feature
* API for TOS bytes (issue 897) ''may wait for netfilter support''
* Chord/DHT (authors are planning to revise code based on comments)
* app store and build system refactoring
* fragmentation for IPv4: being worked by Vedran Miletic and Tommaso Pecorella
* TDMA wireless model
** being worked on by Hemanth Narra
* Netdevice queue state support
** being worked on by Ruben Merz

Website-review

2011-05-31T14:33:57Z

Jpelkey:

{{TOC}}

This page is to track issues reported with the new website design on [http://www2.nsnam.org www2.nsnam.org].

* Does not work on Opera (reported by Andrey Mazo)

* Downloads link broken; points to www2.nsnam.org links (reported by Emmanuelle Laprise)
** '''Status:''' Fixed.

* Typo in Simulation models: "The ns-3 project is commited to build a solid simulation core that is well documented" (check spelling of committed and s/building/build) (reported by Emmanuelle Laprise)
** '''Status:''' fixed

* Not all per-release documentation sets built yet (reported by Tom Henderson)
** '''Status:''' Tom will fix.

* High-resolution configuration broken (reported by Leo Razoumov)
** reported here: http://mailman.isi.edu/pipermail/ns-developers/2011-April/008807.html

* would prefer text-based links and menus (reported by Gustavo Carneiro)

* Typo on Overview->News and Events at the top underneath the page title, it says "Oldser entries" (reported by Josh Pelkey)
** '''Status:''' Fixed.

* Under Overview->Media Kit it says "The font used for the text ns-3 is ." (reported by Josh Pelkey)
** '''Status:''' I changed to "italics"

* Text on the left navigation bar seems like it might be a bit small and kind of hard to read (esp. the second indent text) (reported by Josh Pelkey)

* Media kit images are missing

* partners-acknoledgment page name is mangled; probably should delete and generate one with proper spelling

* Legals page and Credits page (visible from bottom of main page) are blank

* Links to various release and documentation pages resolve to http://www2.nsnam.org/... and result in 404 Not Found.
** '''Status:''' this should automatically be fixed when the website goes live, and when the next item is resolved.

* Not clear how to reference content stored at filesystem paths relative to /var/www/html

* There is no integrated search button

* "All releases" and "All documentation" link not placed correctly in Chrome: [[Media:Ns-3-website.png]]
** '''Status:''' Fixed, at least as of Chrome 13.0.772.0

* Different number of bars in the logo: 3 in the favicon, 4 in the pseudo-3d illustration and 5 in the navigation bar.

Roadmap

2011-05-25T22:07:23Z

Jpelkey: /* Release schedule */

{{TOC}}

This page summarizes the release roadmap for ns-3. A summary of current development activities can be found [[Current Development|here]].

__FORCETOC__

== Release schedule ==

ns-3 makes regular date-driven (not feature driven) releases, roughly quarterly. ns-3 stable releases are sequentially numbered starting with minor version 1 (for example, ns-3.1 released June 30 2008 was followed by ns-3.2 released September 22, 2008).

=== ns-3.12 ===

ns-3.11 was released on May 25, 2011. ns-3.12 is scheduled for Fall 2011. See the [[Ns-3.12]] release page.

== Release process ==

ns-3 releases are based on date-driven schedules: rather than target a set of features for a specific version number, we aim instead for a release date and ship whatever is ready by that date. If a cool new feature misses that date, it is not a big deal because the next release is never too far away. The current interval between releases is about 3 months.

An ns-3 release manager will manage each release. Following ns-3.X release, the release manager is selected for ns-3.X+1. Old ns-3.X release manager is typically responsible for any maintenance releases.

There are three time windows between releases:
# Open
# Maintenance only (no new features)
# Code freeze (P1 checkins)

Depending on the proposed next release date, the release manager sets dates
for milestones 2 and 3. The release manager has the authority to slip
the milestone 2, 3, and final release dates.

In "Open" phase, the release manager has a low profile. However, the release
manager should be involved with scheduling and approving major merges,
because he or she may want to manage the dependencies and do some testing
in a particular order. In open phase, modules that are self contained
(e.g. a new channel model for WiFi) don't really need much coordination
with the release manager.

(See below for "major merges").

In "Maintenance" phase, no new features are to be added, but the maintainers
may check in fixes to bugs. Maintainers may appeal to the release manager
for adding new self-contained features, but it is release manager's call.

In Code freeze phase, the release manager must approve (or apply) all changes
to ns-3-dev outside of documentation. The release manager may also set
a freeze date on documentation.

Typically, the feature freeze is 4-6 weeks before the projected release
date, and the code freeze is 2 weeks before the projected release date.

The release manager is responsible for preparing and maintaining RELEASE_NOTES,
changes.html, and release candidates, and for updating web pages and
wikis concerning release-specific information (e.g., update the Installation
wiki page if there is an issue discovered with a compiler).

Detailed steps for doing the source code release are found in the [http://code.nsnam.org/ns-3-dev/file/1e8249c58fda/doc/release_steps.txt doc/release_steps.txt] file in the ns-3-dev repository.

=== Major merges ===

Major merges are those that are not self contained within the scope of a
single maintainer, those that change API, and those that have some issues
with the build system or other dependencies.

Past examples of major merges:
* NSC
* Bridge device and promiscuous mode
* Attribute system
* Python bindings

If a proposed new feature (or refactoring) meets one of these criteria:
# Does not work with all models or on all platforms
# Changes existing APIs
# Crosses maintainer boundaries

then, the release manager will ask for code review by all maintainers and
request a positive ack that the maintainer is comfortable with the
proposed merge and believes that it will interact well with, or have
no effect on, his or her component. This code review process will typically
lead to questions and comments that need resolution.

In the case where a new model does not work with the existing simulator,
(not on all platforms, not with all existing models) then the model
must receive an approval (exception) from the architecture board or project
lead. Typically, they will either grant this exception or ask the model
author to improve the support and come back later.

The release manager can veto a major merge based on preliminary testing or
concern about looming problems to finalize things for the release.

Finally, it is good practice to coordinate among the active committers and release manager when you are doing a major merge, to avoid bad merge collisions.

Main Page

2011-05-25T22:06:52Z

Jpelkey: /* Upcoming Releases */

{{TOC}}

This [http://en.wikipedia.org/wiki/MediaWiki wiki] complements the [http://www.nsnam.org/ ns-3] main web site.
'''Account Policy:''' Due to spam problems, we have disabled the ability for newly created user accounts to edit/move pages; even our experience on the ns-2 wiki with [http://www.mediawiki.org/wiki/Extension:ConfirmEdit Mediawiki captchas] has ineffective. For now, if you create a new account and want edit privileges, just email [mailto:ns-developers-owner@isi.edu?subject=ns-3-wiki-enable] with your username and we will enable it for write privileges. '''Note:''' [http://www.isi.edu/nsnam/ns ns-2] has a separate wiki, at http://nsnam.isi.edu/nsnam

== Upcoming Releases ==
* Information about '''ns-3.12''', tentatively scheduled for Fall 2011, will be tracked [[Ns-3.12 | on the ns-3.12 wiki page]]. Our most recent release was [[Ns-3.11 | ns-3.11]].

== Upcoming Events ==
* Three students are working on the 2011 '''[[NSOC2011AcceptedProjects | ns-3 Summer of Code (NSOC)]]'''. The announcement is posted [http://mailman.isi.edu/pipermail/ns-developers/2011-April/008935.html here].

== Recent Events ==
* '''[[DevelMeetingMarch2011]]''' March 26, Barcelona Spain; [http://www.nsnam.org/docs/meetings/march11.txt meeting minutes].
* '''[[Wns3-2011]]:''' The third annual Workshop on ns-3, Friday 25 March 2011, Barcelona Spain.
* '''[[DevelMeetingNov2010]]''' Friday Nov. 5, 2010 after the [http://www.geni.net GENI Engineering Conference] in Washington DC; [http://www.nsnam.org/docs/meetings/november10.txt meeting minutes]
* 2010 Google Summer of Code [http://www.nsnam.org/wiki/index.php/GSOC2010AcceptedProjects project page] and [http://nsnam.blogspot.com/2010/10/2010-google-summer-of-code-wrapup.html wrapup].

== Current ns-3-dev Build and Test Results ==
* [http://ns-regression.ee.washington.edu:8010/waterfall Buildbot Waterfall Display]

To see detailed information for a particular system and compiler combination, find the appropriate column. For example, "fc10-g++-4.4.0" indicates that a Fedora Core 10 system using the g++ 4.4.0 compiler has been used to build and run the tests. Scroll down until you see build results in that column. Select a "[view results]" link to view the test framework reports for the current build. Note that time flows from bottom to top in this display. This means that most recent build is shown first in the column, but it also means that the results for each build instance are shown "backward" with the Mercurial pull at the bottom, and the optimized build results at the top.

== Next Level ==
We have created the following pages to allow ns-3 users to contribute various information:
* '''[[Roadmap]]''' - Plans for future releases, and what developers are working on
* '''[[Current Development]]''' - What people are working on for ns-3
* '''[[Developer FAQ]]''' - Answers to frequently asked questions for ns-3 developers
* '''[[User FAQ]]''' - Answers to frequently asked questions for ns-3 users
* '''[[HOWTOs]]''' - HOWTOs guides for various simulation activities
* '''[http://www.nsnam.org/wiki/index.php/Category:Samples Samples]''' - Code samples and examples
* '''[[Troubleshooting]]''' - Tips for working around compilation, etc. problems
* '''[[Contributed Code]]''' - Links to third-party ns-3 software contributions
* '''[[Papers]]''' - Research papers about ns-3 or using ns-3

Roadmap

2011-05-25T22:05:58Z

2011-04-04T14:46:37Z

Jpelkey:

Website-review

2011-04-04T14:42:10Z

Jpelkey:

Jpelkey:

{{TOC}}

On this page, we will try to maintain pointers to current ns-3 development work, and post some suggested project ideas. If you are interested in collaborating on one of these projects, please do not hesitate to contact the individuals identified.

Much of the current activity is centered around the next release, which is ns-3.11 due in April 2011. The release page should list code that is under active review for merging: [[Ns-3.10 | ns-3.10 release page]]

If you are new to ns-3 and want to contribute, please read these guidelines: [http://www.nsnam.org/contributing.html Contributing to ns-3] and review the information on this page below. Please visit our [[Suggested_Projects]] page.

'''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net.

We conduct many of our reviews at http://codereview.appspot.com.

= Reviews requested for ns-3 merge =

The [[Ns-3.11 | ns-3.11 release page]] has the most recent list of things under review for merge.

= NSF Frameworks for ns-3 project =

A multi-year project funded by NSF to improve usability of ns-3. Please see [[NSF_Frameworks]] page.

= Publicly announced development projects =

== ns-3 core ==

=== Multi-threaded simulation implementation for multicore ===

* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html
* ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/
* ''status'': ns-3.10 merge?

=== Synchronized emulation ===

* ''code location'': http://www.comsys.rwth-aachen.de/projects/slicetime/
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2010-November/008488.html
* ''status'': announced in Nov. 2010

=== Linux namespaces and ns-3 ===

* ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.
* ''code location'': See the below wiki page.
* ''background'': http://www.nsnam.org/wiki/index.php/HOWTO_use_Linux_namespaces_with_ns-3
* ''status'': Working on integration of this capability with the [http://cs.itd.nrl.navy.mil/work/core/index.php CORE network emulator]. Some form of this will likely be merged with ns-3 and CORE in the future.

== Device and channel models ==

=== Miscellaneous wifi enhancements ===

* ''code location'': http://codereview.appspot.com/65051
* ''reviewer(s)'': Mathieu Lacage
* ''status'': Some of these pieces made it into ns-3.5-- others are pending
* ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#

=== Patch to pause and resume an interface ===

* ''code location'': http://codereview.appspot.com/62054
* ''reviewer(s)'': TBD
* ''status'':

=== 802.11 model extensions ===

There are several efforts ongoing to extend the ns-3 Wifi model.

==== Harmonization with ns-2 802.11 Ext models ====
* ''summary'': ns-2.33 added a new 802.11 model with much more detailed channel modeling. An effort has been started to port over reusable components from that implementation to ns-3's wifi model, while reusing already implemented basic components. The goal is a harmonization of the 802.11 models of ns-2 and ns-3. Leading aim is to support research on vehicular networks. Planned near-term features:
** Equalizing PHY models including capture effects, user-definable coding rates (e.g. 5.9 GHz from 802.11p)
** EDCA QoS extensions of 802.11e
* Already finished features:
** Nakagami/Rayleigh propagation loss model
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-November/004936.html
* ''code location'': http://idlebox.net/2008/ns-3-wifi/code/ns-3-wifiex/
* ''status'': under current active development. Time frame till this is completed: 4-5 month.

==== 802.11n ====

* ''summary'': University of Florence (LART lab) has begun work on an 802.11n model for ns3. The main goal is to simulate the frame aggregation feature. In the future, they aim to implement the High Throughput terminal behaviour with MIMO technology. They plan to add, to ns-3's 802.11 model, the following 802.11n features:
** Frame Aggregation
** Block ACK
** HCF (EDCA and support for HCCA)
** TXOP
** HT terminal (also with protection modes)
** MIMO
Also interested to verify the 11n terminal throughput when are associated terminal of a/b/g standards.
* Already finished features (in ns-3.5):
** HCF, TXOP, Frame Aggregation
* Merged for ns-3.8:
** Block ACK
* ''code location'': http://code.nsnam.org/mirko/ns-3-80211n
* ''status'': Frame aggregation and block ack merged already; Tommaso Pecorella announced his lab's next steps [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008303.html here]

=== Wireless Interference (Jamming) Model ===

* ''summary'': [http://www.ee.washington.edu/research/nsl/faculty/radha/ Network Security Lab (NSL)], University of Washington, Seattle has begun work on a wireless interference (jamming) model for ns3. The goal is to to enable researchers to use ns3 to study jamming and its mitigation methods.
* ''wiki page'': http://www.nsnam.org/wiki/index.php/NS-3_wireless_jamming_model
* ''code location'': http://codereview.appspot.com/1055041/show
* ''status'': Public review.

=== Vehicular Ad Hoc Networks (VANET) ===

* ''summary'': Michele Weigle's group is working on VANET and has posted a patch for review in the past, but has taken it off the table for ns-3 merge consideration until more work is done.
* ''code location'': None publicly posted at this time.

=== ns-3, 802.15.4 + 6LoWPAN ===

* ''status'': Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]

=== LTE ===

Several developers expressed their interest in enhancing the LTE code developed within the GSoC 2010:
* Nicola Baldo and Marco Miozzo (CTTC) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008461.html announced] to be working on the following:
** adding UL link adaptation
** modeling inter-cell interference
** reworking the RRM/scheduling API
* Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:
** MIMO
** PHY model abstractions
** scheduling models
** mobility and traffic models
* Giuseppe Piro and his group (DEE, Politecnico di Bari) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008469.html announced] the intent to continue with the development of the LTE module, focusing mainly on the following MAC layer aspects:
** RRM
** scheduling
** AMC
* Marco Mezzavilla and his group (DEI, University of Padova) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008483.html announced] interest in working on the following:
** MAC layer
** mobility
** traffic modelization
** MIMO

== Link layer ==

=== 802.21 media independent handover ===

* ''wiki page'': http://www.nsnam.org/wiki/index.php/NS-3_MIH_implementation
* ''code location'': http://code.nsnam.org/salumu/ns-3-mih/
* ''status'': Dormant-- no merge plans announced.

== MPLS ==

* ''Submitted by'': Andrey Churin
* ''code location'': http://code.google.com/p/ns-3-shop/
* ''reviewer(s)'': None
* ''status'': Project has moved to Google hosting.

== Network layer ==

=== IPv6 for ns-3 ===

* ''summary'': Ipv6 support for ns-3
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-June/004283.html
* ''code location'': hg clone https://svnet.u-strasbg.fr/hg/ns-3-ipv6-2nd/
* ''status'': ns-3.3 contains the first merge (Ipv6Address) of this code. ns-3.7 and ns-3.8 will continue to add features. Here is a tentative roadmap: http://mailman.isi.edu/pipermail/ns-developers/2009-July/006211.html

=== API and functionality for marking TOS bytes in packets ===

* ''Submitted by:'' Antti Makela
* ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897
* ''reviewer(s):'' None
* ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned

=== DSR routing ===

* ''Submitted by:'' Yufei Cheng
* ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html

=== DSDV routing ===

* ''Submitted by:'' Hemanth Narra
* ''code location:'' http://codereview.appspot.com/1668042/show
* ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html

== Transport layer ==

=== TCP Vegas ===

* ''Submitted by:'' Juan Pablo Poujade
* ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html
* ''reviewers:'' none officially
* ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general

== Application layer ==

=== Chord/DHash DHT ===

* ''Submitted by'': Harjot Gill
* ''code location:'' http://codereview.appspot.com/180107/show
* ''reviewers:'' Mathieu Lacage, Tom Henderson
* ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html
* ''status:'' Dormant for a while

=== Synchronous posix/sockets API ===

* ''summary'': An ns-3 "process" environment
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html
* ''code location'': http://code.nsnam.org/mathieu/ns-3-simu
* ''status'': still in development

=== real-world application integration ===

* ''summary'': port of quagga routing to ns-3
* ''wiki page'': http://www.nsnam.org/wiki/index.php/Real_World_Application_Integration
* ''code location'': http://code.nsnam.org/lj/quagga-porting/
* ''status'': Was developed by Liu Jian, Google Summer of Code. Portions of this code are planned for a future release (ns-3.8 or later) when ns-3-simu is merged.

=== ns-3-simu sockopt patches ===

* ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html
* ''reviewer(s)'': TBD
* ''status'': review requested on June 22
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html

== Visualization ==

Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:
* http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html
* http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html

George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.

Joe Kopena is working on what he calls a "decorator" http://code.nsnam.org/tjkopena/

Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/

=== Graphical simulation builder ===

Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt.
* http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html
* Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/

=== NetExplorer ===

[http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3.

== Miscellaneous ==

=== L2 Ethernet switch module ===

* ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#
* ''status'': No code yet, starting development.

=== Parallel simulations (2008) ===

* ''summary'': ns-3 extensions for parallelization
* ''wiki page'': http://www.nsnam.org/wiki/index.php/Parallel_Simulations
* ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/
* ''status'': dormant since 2008 Google Summer of Code

=== Delay Box for ns-3 ===

Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.
* ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)
* ''code location'': http://freehg.org/u/mlaw
* ''status'': No status update recently. Dormant.

=== Simulation Configuration and State Detection ===

In order to configure simulations across multiple, probably virtualized, machines a large amount of configuration must be performed in order to construct the component systems. The oppportunity for human error to creep in during this process renders it essentially manually unworkable for all but the simplest topologies. Craig Dowell is thinking about how to address this problem.

[[SimulationConfiguration | Simulation Configuration]]

= Build system and project infrastructure =

== Modular build and package management ==

This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]

== State of Doxygen ==

Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).

== Buildbots ==

* investigate hooking code coverage (lcov) into the report
* investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo.

== Code contribution guidance ==

Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).

== Samples directory ==

Consider cleanup and move of samples/ directory to examples/?

== Documentation ==

Considering to refactor documentation to split the existing manual into a model library and a software core reference manual, to add a lighter-weight tutorial, and to add a "cookbook" of howtos for common ns-3 tasks.

== Website ==

Status: INRIA is organizing some updates to the website.

Current Development

2011-01-14T20:57:32Z

Jpelkey: /* Reviews requested for ns-3 merge */

{{TOC}}

On this page, we will try to maintain pointers to current ns-3 development work, and post some suggested project ideas. If you are interested in collaborating on one of these projects, please do not hesitate to contact the individuals identified.

Much of the current activity is centered around the current release, which is now ns-3.10 due in early 2011. The release page should list code that is under active review for merging: [[Ns-3.10 | ns-3.10 release page]]

If you are new to ns-3 and want to contribute, please read these guidelines: [http://www.nsnam.org/contributing.html Contributing to ns-3] and review the information on this page below. Please visit our [[Suggested_Projects]] page.

'''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net.

We conduct many of our reviews at http://codereview.appspot.com.

= Reviews requested for ns-3 merge =

The [[Ns-3.11 | ns-3.11 release page]] has the most recent list of things under review for merge.

= NSF Frameworks for ns-3 project =

A multi-year project funded by NSF to improve usability of ns-3. Please see [[NSF_Frameworks]] page.

= Publicly announced development projects =

== ns-3 core ==

=== Multi-threaded simulation implementation for multicore ===

* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html
* ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/
* ''status'': ns-3.10 merge?

=== Synchronized emulation ===

* ''code location'': http://www.comsys.rwth-aachen.de/projects/slicetime/
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2010-November/008488.html
* ''status'': announced in Nov. 2010

=== Linux namespaces and ns-3 ===

* ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.
* ''code location'': See the below wiki page.
* ''background'': http://www.nsnam.org/wiki/index.php/HOWTO_use_Linux_namespaces_with_ns-3
* ''status'': Working on integration of this capability with the [http://cs.itd.nrl.navy.mil/work/core/index.php CORE network emulator]. Some form of this will likely be merged with ns-3 and CORE in the future.

== Device and channel models ==

=== Miscellaneous wifi enhancements ===

* ''code location'': http://codereview.appspot.com/65051
* ''reviewer(s)'': Mathieu Lacage
* ''status'': Some of these pieces made it into ns-3.5-- others are pending
* ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#

=== Patch to pause and resume an interface ===

* ''code location'': http://codereview.appspot.com/62054
* ''reviewer(s)'': TBD
* ''status'':

=== 802.11 model extensions ===

There are several efforts ongoing to extend the ns-3 Wifi model.

==== Harmonization with ns-2 802.11 Ext models ====
* ''summary'': ns-2.33 added a new 802.11 model with much more detailed channel modeling. An effort has been started to port over reusable components from that implementation to ns-3's wifi model, while reusing already implemented basic components. The goal is a harmonization of the 802.11 models of ns-2 and ns-3. Leading aim is to support research on vehicular networks. Planned near-term features:
** Equalizing PHY models including capture effects, user-definable coding rates (e.g. 5.9 GHz from 802.11p)
** EDCA QoS extensions of 802.11e
* Already finished features:
** Nakagami/Rayleigh propagation loss model
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-November/004936.html
* ''code location'': http://idlebox.net/2008/ns-3-wifi/code/ns-3-wifiex/
* ''status'': under current active development. Time frame till this is completed: 4-5 month.

==== 802.11n ====

* ''summary'': University of Florence (LART lab) has begun work on an 802.11n model for ns3. The main goal is to simulate the frame aggregation feature. In the future, they aim to implement the High Throughput terminal behaviour with MIMO technology. They plan to add, to ns-3's 802.11 model, the following 802.11n features:
** Frame Aggregation
** Block ACK
** HCF (EDCA and support for HCCA)
** TXOP
** HT terminal (also with protection modes)
** MIMO
Also interested to verify the 11n terminal throughput when are associated terminal of a/b/g standards.
* Already finished features (in ns-3.5):
** HCF, TXOP, Frame Aggregation
* Merged for ns-3.8:
** Block ACK
* ''code location'': http://code.nsnam.org/mirko/ns-3-80211n
* ''status'': Frame aggregation and block ack merged already; Tommaso Pecorella announced his lab's next steps [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008303.html here]

=== Wireless Interference (Jamming) Model ===

* ''summary'': [http://www.ee.washington.edu/research/nsl/faculty/radha/ Network Security Lab (NSL)], University of Washington, Seattle has begun work on a wireless interference (jamming) model for ns3. The goal is to to enable researchers to use ns3 to study jamming and its mitigation methods.
* ''wiki page'': http://www.nsnam.org/wiki/index.php/NS-3_wireless_jamming_model
* ''code location'': http://codereview.appspot.com/1055041/show
* ''status'': Public review.

=== Vehicular Ad Hoc Networks (VANET) ===

* ''summary'': Michele Weigle's group is working on VANET and has posted a patch for review in the past, but has taken it off the table for ns-3 merge consideration until more work is done.
* ''code location'': None publicly posted at this time.

=== ns-3, 802.15.4 + 6LoWPAN ===

* ''status'': Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]

=== LTE ===

Several developers expressed their interest in enhancing the LTE code developed within the GSoC 2010:
* Nicola Baldo and Marco Miozzo (CTTC) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008461.html announced] to be working on the following:
** adding UL link adaptation
** modeling inter-cell interference
** reworking the RRM/scheduling API
* Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:
** MIMO
** PHY model abstractions
** scheduling models
** mobility and traffic models
* Giuseppe Piro and his group (DEE, Politecnico di Bari) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008469.html announced] the intent to continue with the development of the LTE module, focusing mainly on the following MAC layer aspects:
** RRM
** scheduling
** AMC
* Marco Mezzavilla and his group (DEI, University of Padova) [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008483.html announced] interest in working on the following:
** MAC layer
** mobility
** traffic modelization
** MIMO

== Link layer ==

=== 802.21 media independent handover ===

* ''wiki page'': http://www.nsnam.org/wiki/index.php/NS-3_MIH_implementation
* ''code location'': http://code.nsnam.org/salumu/ns-3-mih/
* ''status'': Dormant-- no merge plans announced.

== MPLS ==

* ''Submitted by'': Andrey Churin
* ''code location'': http://code.google.com/p/ns-3-shop/
* ''reviewer(s)'': None
* ''status'': Project has moved to Google hosting.

== Network layer ==

=== IPv6 for ns-3 ===

* ''summary'': Ipv6 support for ns-3
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-June/004283.html
* ''code location'': hg clone https://svnet.u-strasbg.fr/hg/ns-3-ipv6-2nd/
* ''status'': ns-3.3 contains the first merge (Ipv6Address) of this code. ns-3.7 and ns-3.8 will continue to add features. Here is a tentative roadmap: http://mailman.isi.edu/pipermail/ns-developers/2009-July/006211.html

=== API and functionality for marking TOS bytes in packets ===

* ''Submitted by:'' Antti Makela
* ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897
* ''reviewer(s):'' None
* ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned

=== DSR routing ===

* ''Submitted by:'' Yufei Cheng
* ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html

=== DSDV routing ===

* ''Submitted by:'' Hemanth Narra
* ''code location:'' http://codereview.appspot.com/1668042/show
* ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html

== Transport layer ==

=== TCP Vegas ===

* ''Submitted by:'' Juan Pablo Poujade
* ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html
* ''reviewers:'' none officially
* ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general

== Application layer ==

=== Chord/DHash DHT ===

* ''Submitted by'': Harjot Gill
* ''code location:'' http://codereview.appspot.com/180107/show
* ''reviewers:'' Mathieu Lacage, Tom Henderson
* ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html
* ''status:'' Dormant for a while

=== Synchronous posix/sockets API ===

* ''summary'': An ns-3 "process" environment
* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html
* ''code location'': http://code.nsnam.org/mathieu/ns-3-simu
* ''status'': still in development

=== real-world application integration ===

* ''summary'': port of quagga routing to ns-3
* ''wiki page'': http://www.nsnam.org/wiki/index.php/Real_World_Application_Integration
* ''code location'': http://code.nsnam.org/lj/quagga-porting/
* ''status'': Was developed by Liu Jian, Google Summer of Code. Portions of this code are planned for a future release (ns-3.8 or later) when ns-3-simu is merged.

=== ns-3-simu sockopt patches ===

* ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html
* ''reviewer(s)'': TBD
* ''status'': review requested on June 22
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html

== Visualization ==

Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:
* http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html
* http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html

George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.

Joe Kopena is working on what he calls a "decorator" http://code.nsnam.org/tjkopena/

Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/

=== Graphical simulation builder ===

Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt.
* http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html
* Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/

=== NetExplorer ===

[http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3.

== Miscellaneous ==

=== L2 Ethernet switch module ===

* ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#
* ''status'': No code yet, starting development.

=== Parallel simulations (2008) ===

* ''summary'': ns-3 extensions for parallelization
* ''wiki page'': http://www.nsnam.org/wiki/index.php/Parallel_Simulations
* ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/
* ''status'': dormant since 2008 Google Summer of Code

=== Delay Box for ns-3 ===

Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.
* ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)
* ''code location'': http://freehg.org/u/mlaw
* ''status'': No status update recently. Dormant.

=== Simulation Configuration and State Detection ===

In order to configure simulations across multiple, probably virtualized, machines a large amount of configuration must be performed in order to construct the component systems. The oppportunity for human error to creep in during this process renders it essentially manually unworkable for all but the simplest topologies. Craig Dowell is thinking about how to address this problem.

[[SimulationConfiguration | Simulation Configuration]]

= Build system and project infrastructure =

== Modular build and package management ==

This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]

== State of Doxygen ==

Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).

== Buildbots ==

* investigate hooking code coverage (lcov) into the report
* investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo.

== Code contribution guidance ==

Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).

== Samples directory ==

Consider cleanup and move of samples/ directory to examples/?

== Documentation ==

Considering to refactor documentation to split the existing manual into a model library and a software core reference manual, to add a lighter-weight tutorial, and to add a "cookbook" of howtos for common ns-3 tasks.

== Website ==

Status: INRIA is organizing some updates to the website.