Nsnam - User contributions [en]

Education

2017-07-05T13:14:15Z

Vedranm: Add another paper.

{{TOC}}

= Using ns-3 in Education =

This page is a resource for learning about ns-3 as an educational tool for networking education.

== Papers ==

The [https://www.computer.org/csdl/proceedings/etcs/2009/3557/01/3557ztoc.pdf 2009 First International Workshop on Education Technology and Computer Science (ETCS '09)] had a paper on teaching ns-3 titled [http://ieeexplore.ieee.org/abstract/document/4959116/ Research of Teaching on Network Course Based on NS-3].

The [http://education.sigcomm.org/Workshop2011/Workshop2011 2011 Sigcomm Education workshop] had a paper regarding ns-3 use in the classroom [http://edusigcomm.info.ucl.ac.be/Workshop2011/20110310001 An Open-source and Declarative Approach Towards Teaching Large-scale Networked Systems Programming].

== Courses using ns-3 ==

The following courses have used ns-3 as courseware or to support projects
* [https://griley.ece.gatech.edu/riley/ece6110/ Georgia Tech. ECE 6110] Dr. George Riley, Spring 2013, Fall 2011, and Fall 2010
* The University of Kansas
** [https://www.ittc.ku.edu/~jpgs/courses/nets/ EECS 780] Dr. James Sterbenz, Fall 2017, Fall 2016, Fall 2015, Fall 2014, Spring 2013, Spring 2012, Spring 2011, Spring 2010, Spring 2009
** [https://www.ittc.ku.edu/~jpgs/courses/mwnets/ EECS 882] Dr. James Sterbenz, Spring 2016, Fall 2013, Fall 2011, Fall 2009
** [https://www.ittc.ku.edu/~jpgs/courses/rsnets/ EECS 983] Dr. James Sterbenz, Spring 2014, Spring 2012, Spring 2010
* [https://www.cis.upenn.edu/~boonloo/cis553-fa10/ University of Pennsylvania CIS 553/TCOM 512] Dr. Boon Thau Loo, Spring 2013, also Fall 2010
* [https://noppa.tkk.fi/noppa/kurssi/s-38.2188/ Aalto University] Jose Costa-Requena and Markus Peuhkuri, Fall 2011
* [https://www.cse.iitb.ac.in/synerg/doku.php?id=public:courses:cs641-autumn08:start Indian Institute of Technology Bombay] Bhaskaran Raman, Autumn 2011, Autumn 2010, Autumn 2009, and Autumn 2008
* University of Rijeka
** [https://lab.miletic.net/hr/nastava/kolegiji/RM2/ RM2-Inf], Dr. Mario Radovan and [[User:Vedranm|Dr. Vedran Miletić]], Spring 2015, Spring 2014, Spring 2013, and Spring 2012
** [https://lab.miletic.net/hr/nastava/kolegiji/RM-RiTeh RM-RiTeh], Dr. Mladen Tomić and [[User:Vedranm|Dr. Vedran Miletić]], Spring 2014 and Spring 2013
* [http://research.cs.queensu.ca/~wireless_p/ Queen's University CISC 834] Dr. Hossam S. Hassanein, Ramy Atawia and Hisham Farahat, Winter 2015, Fall 2013, and Fall 2012

== Other resources ==

* Lalith Suresh's [[Lab Assignments using ns-3]] page.

== ns-2 Education ==

This page contains references to the use of ns-2 and nam in education:
http://www.isi.edu/nsnam/ns/edu/

Education

2017-07-05T09:07:40Z

Vedranm: Refresh

{{TOC}}

= Using ns-3 in Education =

This page is a resource for learning about ns-3 as an educational tool for networking education.

== Papers ==

The [http://education.sigcomm.org/Workshop2011/Workshop2011 2011 Sigcomm Education workshop] had a paper regarding ns-3 use in the classroom:
* [http://edusigcomm.info.ucl.ac.be/Workshop2011/20110310001 An Open-source and Declarative Approach Towards Teaching Large-scale Networked Systems Programming]

== Courses using ns-3 ==

The following courses have used ns-3 as courseware or to support projects
* [https://griley.ece.gatech.edu/riley/ece6110/ Georgia Tech. ECE 6110] Dr. George Riley, Spring 2013, Fall 2011, and Fall 2010
* The University of Kansas
** [https://www.ittc.ku.edu/~jpgs/courses/nets/ EECS 780] Dr. James Sterbenz, Fall 2017, Fall 2016, Fall 2015, Fall 2014, Spring 2013, Spring 2012, Spring 2011, Spring 2010, Spring 2009
** [https://www.ittc.ku.edu/~jpgs/courses/mwnets/ EECS 882] Dr. James Sterbenz, Spring 2016, Fall 2013, Fall 2011, Fall 2009
** [https://www.ittc.ku.edu/~jpgs/courses/rsnets/ EECS 983] Dr. James Sterbenz, Spring 2014, Spring 2012, Spring 2010
* [https://www.cis.upenn.edu/~boonloo/cis553-fa10/ University of Pennsylvania CIS 553/TCOM 512] Dr. Boon Thau Loo, Spring 2013, also Fall 2010
* [https://noppa.tkk.fi/noppa/kurssi/s-38.2188/ Aalto University] Jose Costa-Requena and Markus Peuhkuri, Fall 2011
* [https://www.cse.iitb.ac.in/synerg/doku.php?id=public:courses:cs641-autumn08:start Indian Institute of Technology Bombay] Bhaskaran Raman, Autumn 2011, Autumn 2010, Autumn 2009, and Autumn 2008
* University of Rijeka
** [https://lab.miletic.net/hr/nastava/kolegiji/RM2/ RM2-Inf], Dr. Mario Radovan and [[User:Vedranm|Dr. Vedran Miletić]], Spring 2015, Spring 2014, Spring 2013, and Spring 2012
** [https://lab.miletic.net/hr/nastava/kolegiji/RM-RiTeh RM-RiTeh], Dr. Mladen Tomić and [[User:Vedranm|Dr. Vedran Miletić]], Spring 2014 and Spring 2013
* [http://research.cs.queensu.ca/~wireless_p/ Queen's University CISC 834] Dr. Hossam S. Hassanein, Ramy Atawia and Hisham Farahat, Winter 2015, Fall 2013, and Fall 2012

== Other resources ==

* Lalith Suresh's [[Lab Assignments using ns-3]] page.

== ns-2 Education ==

This page contains references to the use of ns-2 and nam in education:
http://www.isi.edu/nsnam/ns/edu/

User:Vedranm

2017-06-10T14:57:38Z

Vedranm: Update of personal page

__TOC__

== Vedran Miletić ==
* Work: Senior Research and Teaching Assistant, [https://lab.miletic.net/ Computer Networks, Parallelization, and Simulation Laboratory], [https://www.inf.uniri.hr/ Department of Informatics], [https://www.uniri.hr/ University of Rijeka], Rijeka, Croatia
* External links: [https://vedran.miletic.net/ Homepage] [https://nudgedelastic.band/ Blog]
* Social networking profiles: [https://twitter.com/vedranmiletic Twitter] [https://bitbucket.org/vedranmiletic Bitbucket] [https://github.com/vedranmiletic GitHub]

== Interests inside ns-3 ==
* [[Object Start Stop specification]]
* [[Optical network models|Photonic WDM Network Simulator]]

== Other interests related to ns-3 ==
* [http://mailman.isi.edu/pipermail/ns-developers/2011-April/008856.html improve CSMA model]
* [https://fedoraproject.org/wiki/Features/Ns3 get RPM package included in Fedora]

Optical network models

2017-06-10T14:51:33Z

Vedranm: Update of info regarding PWNS

ns-3 network simulator presently doesn't include any support for simulation of WDM optical networks in the official distribution. There are three optical network simulation modules under active development as of January 2013, that have the goal to make ns-3 into optical network simulator. Note, however, that the term "optical network simulator" is rather broad, as there are many types and features of optical networks one might want to model and use in simulation. This page tracks info about these optics modules, intented for simulating
* Optical Transport Network (OTN),
* Passive Optical Network (PON), and
* Radio over Fiber (RoF).

This page will be updated with new info as time permits.

== Optical Transport Network: Photonic WDM Network Simulator (PWNS) ==
[[File:PwnsLogo.png|thumb|PWNS project logo]]

=== Project scope ===
[https://lab.miletic.net/en/research-and-development/#photonic-wdm-network-simulator-pwns Photonic WDM Network Simulator (PWNS)] is an extension that provides support for simulating optical transport network. The project name is a parody on OWns (Optical WDM network simulator, described in [1]), a project with similar goals implemented in ns-2.

PWNS provides models for optical network components [2]:

* edge network devices
* core network devices
* physical interfaces
* channels
* control plane

PWNS also provides models for physical and virtual entities [3]:

* physical cable containing one or more fibers
* shared risk link group containing parts of two or more cables that share a physical location
* lightpath passing through one or more network devices
* logical channel that has working and spare wavelength path
* failure and repair models
* uptime and downtime trackers

=== Source code ===
Current version is available at [https://bitbucket.org/pwns/ns-3-dev-pwns Bitbucket PWNS project]. Contact [[User:Vedranm|Vedran Miletić]] with any questions you may have). Code contributions are welcome. Merge of selected components to ns-3-dev might happen in the future.

=== References ===
# Wen, B. and Bhide, N.M. and Shenai, R.K. and Sivalingam, K.M., ''Optical wavelength division multiplexing (WDM) network simulator (OWns): architecture and performance studies''
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Modelling optical network components: a network-simulator based approach'' // Proceedings on the IX. International symposium on Telecommunications - BIHTEL 2012.
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Impact Evaluation of Physical Length of Shared Risk Link Groups on Optical Network Availability Using Monte Carlo Simulation'' // Proceedings of the 18th European Conference on Networks and Optical Communications, NOC 2013 / Leitgeb, Erich (ur.).

== Passive Optical Network ==
=== Project Summary ===

The aim of this project is to develop PON (passive optical network) models for NS-3. It is under the umbrella of [http://www.ctvr.ie/ CTVR] that supports various research topics related with telecommunication.

=== Project Scope ===

The project will implement models for passive optical networks. The current focus is to develop one model for simulating XG-PON, which is also known as [http://en.wikipedia.org/wiki/10G-PON 10G-PON]. We will also investigate how to use this model and WiMAX/LTE models distributed with NS-3 to simulate the coming FTTC (Fiber To The Cell) network scenario. In the future, models for other PON technologies, such as [http://en.wikipedia.org/wiki/10G-EPON 10G-EPON] and [http://en.wikipedia.org/wiki/Passive_optical_network#Long-Reach_Optical_Access_Networks Long Reach PON], will also be developed to carry out comparative studies.

The current prototype is described in [1] and more detailed description will be posted here as soon as possible.

=== Code ===

The code will be made public in September-December, 2013 timeframe through the websites of CTVR and [http://www.ucc.ie/en/misl/ MISL].

=== References ===

# X. Wu, K.N. Brown, C.J. Sreenan, P. Alvarez, M. Ruffini, N. Marchetti, D. Payne, and L. Doyle, ''An XG-PON Module for the NS-3 Network Simulator'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

== Radio over Fiber ==
=== Project scope ===
The goal of our work is to investigate and optimize the performance of MAC (Medium Access Control) radio protocols when it is used in a RoF (Radio-over-Fiber) architecture. Our study is mainly focused on IEEE 802.11 over RoF transmissions. We developed a RoF model in ns-3 based on the YANS Wi-Fi model which enables the simulation of 802.11 RoF systems. The current model includes [1]:

* Distributed Antenna Systems RoF modeling;
* Optical module computing delays and attenuations undergone by the radio signal transmission over fiber links.

Further points to be implemented:

* Protocol-independent model (not limited to Wi-Fi transmissions);
* Integration of optical network component models developed by PWNS (Prototype WDM Network Simulator).

=== Code ===
The source code is not yet available for the public.

=== References ===
# Sebastien Deronne, Veronique Moeyaert and Sebastien Bette, ''Simulation of 802.11 Radio-over-Fiber Networks using ns-3'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

[[Category:Models]]

User:Vedranm

2015-04-28T15:47:55Z

Vedranm: Update links and contact info

__TOC__

== About me ==
* Name: Vedran Miletić
* Contact: [http://vedranmileti.ch/ Personal homepage]
* Work: Research and Teaching Assistant [http://www.uniri.hr/ University of Rijeka] [http://www.inf.uniri.hr/ Department of Informatics], Rijeka, Croatia
* Study: PhD student at [http://www.unizg.hr/ University of Zagreb] [http://www.fer.unizg.hr/ Faculty of Electrical Engineering and Computing], Zagreb, Croatia
* Social networking profiles: [https://twitter.com/vedranmiletic Twitter] [https://bitbucket.org/rivanvx Bitbucket] [https://github.com/rivanvx GitHub]

== Presently working on ==
* [[Object Start Stop specification]]
* [[Optical network models|Prototype WDM Network Simulator]]

== Other interests related to ns-3 ==
* [http://mailman.isi.edu/pipermail/ns-developers/2011-April/008856.html improve CSMA model]
* [https://fedoraproject.org/wiki/Features/Ns3 get RPM package included in Fedora]

Optical network models

2014-10-27T21:56:40Z

Vedranm: Update for PWNS public release

ns-3 network simulator presently doesn't include any support for simulation of WDM optical networks in the official distribution. There are three optical network simulation modules under active development as of January 2013, that have the goal to make ns-3 into optical network simulator. Note, however, that the term "optical network simulator" is rather broad, as there are many types and features of optical networks one might want to model and use in simulation. This page tracks info about these optics modules, intented for simulating
* Optical Transport Network (OTN),
* Passive Optical Network (PON), and
* Radio over Fiber (RoF).

This page will be updated with new info as time permits.

== Optical Transport Network: Prototype WDM Network Simulator (PWNS) ==
[[File:PwnsLogo.png|thumb|PWNS project logo]]

=== Project scope ===

[http://pwns.github.io Prototype WDM Network Simulator (PWNS)] provides models for optical network components [2]:

* edge network devices
* core network devices
* physical interfaces
* channels
* control plane

PWNS also provides models for physical and virtual entities [3]:

* physical cable containing one or more fibers
* shared risk link group containing parts of two or more cables that share a physical location
* lightpath passing through one or more network devices
* logical channel that has working and spare wavelength path
* failure and repair models
* uptime and downtime trackers

=== Project name ===
Project name is a parody on OWns (Optical WDM network simulator, described in [1]), a project with similar goals implemented in ns-2.

=== Source code ===
Current version is available at [http://bitbucket.org/pwns/ns-3-dev-pwns Bitbucket PWNS project]. Contact [[User:Vedranm|Vedran Miletić]] with any questions you may have). Code contributions are welcome.

Merge of selected components to ns-3-dev might happen in the future.

=== References ===
# Wen, B. and Bhide, N.M. and Shenai, R.K. and Sivalingam, K.M., ''Optical wavelength division multiplexing (WDM) network simulator (OWns): architecture and performance studies''
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Modelling optical network components: a network-simulator based approach'' // Proceedings on the IX. International symposium on Telecommunications - BIHTEL 2012.
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Impact Evaluation of Physical Length of Shared Risk Link Groups on Optical Network Availability Using Monte Carlo Simulation'' // Proceedings of the 18th European Conference on Networks and Optical Communications, NOC 2013 / Leitgeb, Erich (ur.).

== Passive Optical Network ==
=== Project Summary ===

The aim of this project is to develop PON (passive optical network) models for NS-3. It is under the umbrella of [http://www.ctvr.ie/ CTVR] that supports various research topics related with telecommunication.

=== Project Scope ===

The project will implement models for passive optical networks. The current focus is to develop one model for simulating XG-PON, which is also known as [http://en.wikipedia.org/wiki/10G-PON 10G-PON]. We will also investigate how to use this model and WiMAX/LTE models distributed with NS-3 to simulate the coming FTTC (Fiber To The Cell) network scenario. In the future, models for other PON technologies, such as [http://en.wikipedia.org/wiki/10G-EPON 10G-EPON] and [http://en.wikipedia.org/wiki/Passive_optical_network#Long-Reach_Optical_Access_Networks Long Reach PON], will also be developed to carry out comparative studies.

The current prototype is described in [1] and more detailed description will be posted here as soon as possible.

=== Code ===

The code will be made public in September-December, 2013 timeframe through the websites of CTVR and [http://www.ucc.ie/en/misl/ MISL].

=== References ===

# X. Wu, K.N. Brown, C.J. Sreenan, P. Alvarez, M. Ruffini, N. Marchetti, D. Payne, and L. Doyle, ''An XG-PON Module for the NS-3 Network Simulator'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

== Radio over Fiber ==
=== Project scope ===
The goal of our work is to investigate and optimize the performance of MAC (Medium Access Control) radio protocols when it is used in a RoF (Radio-over-Fiber) architecture. Our study is mainly focused on IEEE 802.11 over RoF transmissions. We developed a RoF model in ns-3 based on the YANS Wi-Fi model which enables the simulation of 802.11 RoF systems. The current model includes [1]:

* Distributed Antenna Systems RoF modeling;
* Optical module computing delays and attenuations undergone by the radio signal transmission over fiber links.

Further points to be implemented:

* Protocol-independent model (not limited to Wi-Fi transmissions);
* Integration of optical network component models developed by PWNS (Prototype WDM Network Simulator).

=== Code ===
The source code is not yet available for the public.

=== References ===
# Sebastien Deronne, Veronique Moeyaert and Sebastien Bette, ''Simulation of 802.11 Radio-over-Fiber Networks using ns-3'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

[[Category:Models]]

GSOC2014Projects

2014-03-11T08:07:53Z

Vedranm: Add wscript reorganization and refactoring to idea

{{TOC}}

* [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page GSoC Frequently Asked Questions]
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]
* [[GSOC2014StudentGuide |ns-3's GSoC Student guide]]
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]
* [[GSOCSelectionProcess | GSoC Student Selection Process]]
* [[GSOC2014PatchRequirement | Patch Requirement Guidelines]]
* [[GSOC2014StudentApplicationTemplate |GSoC Student application template]]
* [[GSOC2013Projects |GSoC 2013 page]] | [[GSOC2013AcceptedProjects | GSoC 2013 Accepted Projects]]
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net

= GSoC 2014 Ideas =

This webpage highlights project ideas for ns-3's Google Summer of Code 2014 effort.

GSOC 2014 Timeline is:
* February 3 - 20:00 UTC: Mentoring organizations can begin submitting applications to Google.
* February 14 - 20:00 UTC: Mentoring organization application deadline.
* February 24 - 20:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2014 site.
* February 24 - March 21: Would-be student participants discuss application ideas with mentoring organizations.
* March 10 - 19:00 UTC: Student application period opens.
* March 21 - 19:00 UTC: Student application deadline.
* April 21 - 19:00 UTC: Student selections announced
* May 19 - Coding begins
* August 18 - Coding ends
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2014

== About the ns-3 project ==

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.

Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

Our GSoC organizational admin is [mailto:tomhend@u.washington.edu Tom Henderson] and our backup org admin is [mailto:tpecorella@mac.com Tommaso Pecorella]. The project has participated in past GSoCs during 2008-10 and 2012-13.

Mentors will be paired with students based on the projects that are selected. Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring. Prospective mentors should notify Tom Henderson of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.

== ns-3 and other GSoC mentoring organisations ==

ns-3 is one of 190 mentoring organizations, and at other organizations have posted project ideas related to ns-3 in the past. For instance, the Wiselib project has listed ns-3 integration as one of its project ideas at http://www.Wiselib.org/gsoc.

Students interested in ns-3 and GSoC are also encouraged to explore whether other organizations might be a suitable mentoring organization for their project idea. Please keep in mind, though, that the ns-3 project is not involved in the selection process for these other mentoring organizations, and you will have to apply there instead.

== Getting started ==

For students interested in applying to ns-3 for GSOC, go through the following list to get started:
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].
* Look through our ideas list below to see if you find a project that interests you.
* Review the [http://www.nsnam.org/ns-3-19/documentation/ ns-3 tutorial] thoroughly, if you have not already done so.
* Look through the [[GSOC2014StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.
* In parallel, make sure you prepare a patch as per the [[GSOC2014PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.

== Project Ideas ==

The following are a list of project proposals from the ns-3 team for Google Summer of Code 2014. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.

<blockquote>
Each project idea within a particular priority has been tagged with the following properties:
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
* ''Difficulty:'' easy, medium or difficult
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.
</blockquote>

= Guidelines for project ideas =

For mentors who're adding project ideas to the list below, please ensure that:

* The projects are sized such that there can be a code merge by the end of the coding period. The scope of the project should be such that it is very difficult to not have a code merge by the end of the summer.
* The proposed projects are not too open-ended. That is, if the deliverables or a clear path to the same are not well understood, it is better kept outside GSOC.
* There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.

= Project Ideas =

Please see [[GSOC2013Projects | last year's page]] for guidelines on how to create project ideas.

'''Note to students:''' These ideas are not listed in any priority order, and other project ideas not listed here are also encouraged.

=== Decouple traffic generators from sockets ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]

* ns-3 uses applications that are part traffic generator, part socket-based application. The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks. This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.
* ''Required Experience:'' C++, sockets API
* ''Interests:''
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** Unix Network Programming (Stevens) or equivalent

=== ARP and NDisc cache visibility ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]

* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches. Something similar to how PrintRoutes is done for IPv4 would be useful. Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).
* ''Required Experience:'' C++
* ''Interests:'' IPv4 and Ipv6
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** source code in src/internet, and the bugs mentioned above

=== INSTOOLS for ns-3 ===

Mentors: [mailto:tomh@tomh.org Tom Henderson]

'''INSTOOLS for ns-3:''' [http://groups.geni.net/geni/wiki/InstrumentationTools INSTOOLS] is a software instrumentation package for GENI experiments. It logs a lot of artifacts of experiments, such as ARP and IP routing tables, Netflow graphs, etc, to databases. The aim of this project is to instrument ns-3 nodes to capture as much of this data as is applicable. A bonus is to try to integrate further with ProtoGENI and INSTOOLS such as making the ns-3 data archived just like it was a GENI experiment.
* ''Required Experience:'' Familiarity with Linux networking and with C++ programming.
* ''Bonus Experience:'' Experience with GENI and/or Emulab
* ''Interests:'' Simulator tool development, integration with testbed experiments
* ''Difficulty:'' Medium
* ''Recommended Reading:'' http://groups.geni.net/geni/wiki/InstrumentationTools

=== bufferbloat-related models ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:dave.taht@gmail.com Dave Taht]

'''bufferbloat models:''' [https://www.youtube.com/watch?v=-D-cJNtKwuw Bufferbloat] is an interesting contemporary research topic.
This project proposal is to develop models, examples, and visualizations around the bufferbloat problem. Some technical solutions include Linux Byte Queue Limits (BQL) and active queue management (AQM) techniques (we just have RED queues in ns-3-dev but no models yet for the others). Note: There is already some ns-3 code available (see below) but the authors have not updated it for a while; this or some recent ns-2 code could be a starting point. Also, work could be done on using actual Linux code in the ns-3 Direct Code Execution (DCE) project.
* ''Interests:'' Internet performance, linux kernel networking
* ''Difficulty:'' easy to hard, depending on the depth of the project
* ''Recommended reading:''
** http://gettys.wordpress.com/category/bufferbloat/
** [http://www.bufferbloat.net/projects/cerowrt CeroWrt]
** [http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf ICCRG presentation]
** [http://pollere.net/CoDel.html ns-2 code]
** [https://codereview.appspot.com/6463048/ ns-3 code review]

=== 802.15.4 realistic MAC and Energy Model ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''802.15.4 realistic MAC and Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Moreover it does not model the radio interface sleep status. The current model assumes that the radio is always active. As a consequence, the MAC layer is quite simple, since it does not needs to guess when the receiver's radio interface is active.
The goal of the project are:
# Model the 4-state radio model (Sleep, Tx, Rx, Transitioning)
# Develop one 'realistic' MAC model (the choice is left to the student)
# Link the 4-state model with the Energy module.

* ''Required Experience:'' C++, WSN
* ''Bonus Experience:'' ns-3 Energy model, lr-wpan module
* ''Interests:'' WSN, Battery discharge
* ''Difficulty:'' hard
* ''Recommended reading:''
** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes]
** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]
** [http://dunkels.com/adam/dunkels11contikimac.pdf The ContikiMAC Radio Duty Cycling Protocol]

=== 802.15.4 Bootstrap ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''802.15.4 Bootstrap:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. An useful extension is to fully support the node bootstrap phase, including node association and beacon request/reply. The goal of the project is to enhance the lr-wpan module so to use beacons in the bootstrap phase along with network scanning and pan-id resolution for in-range coordinators.
* ''Required Experience:'' C++, WSN
* ''Bonus Experience:'' 802.15.4 standard
* ''Interests:'' WSN
* ''Difficulty:'' medium
* ''Recommended reading:''
** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== 802.15.4 Beacon-enabled mode ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''802.15.4 Beacon-enabled mode:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. Unlike Contiki-os, the model could benefit from supporting beacon-enabled mode of operation. The beacon-enabled mode is a fully slotted transmission mode, with guaranteed slots and bound performances, unlike the ad-hoc mode. This is especially important because the L3 routing protocols might be strongly affected by the lower-layer topology. Hence it is of paramount importance to be able to simulate both in ns-3. The goal of the project is to develop the new beacon-enabled MAC layer for the lr-wpan module.
* ''Required Experience:'' C++, WSN
* ''Bonus Experience:'' 802.15.4 standard
* ''Interests:'' WSN
* ''Difficulty:'' medium/hard
* ''Recommended reading:''
** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''6LoWPAN-nd implementation and testing:''' [https://datatracker.ietf.org/doc/rfc6775/ 6LoWPAN-nd] is novel protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested.
* ''Required Experience:'' C++, IPv6, RPL
* ''Bonus Experience:'' WSN networking
* ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression
* ''Difficulty:'' hard
* ''Recommended reading:''
** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals
** [https://datatracker.ietf.org/doc/rfc6775/ RFC 6775] Neighbor Discovery Optimization for Low Power and Lossy Networks

=== IPv6 stack validation and improvements ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):
# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].
# Flow Monitor module does not work on the IPv6 stack
# FlowLabel header field is not currenly used
# IPSec is not supported
The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.
* ''Required Experience:'' C++, TCP/IP networking
* ''Bonus Experience:'' IPv6 protocols
* ''Interests:'' IPv6 internetworking
* ''Difficulty:'' easy / medium, depending on the features implemented
* ''Recommended reading:''
** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]
** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]
** ns-3 Flowmon module documentation
** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]
** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]
** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]

=== Multicast IPv6 traffic support ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

'''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.
* ''Required Experience:'' C++, IPv6,
* ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)
* ''Interests:'' routing, multicast
* ''Difficulty:'' medium/hard
* ''Recommended reading:''
** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]
** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]
** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])

=== Licklider Transmission Protocol (LTP) ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella] [mailto:luca.ronga@cnit.it Luca Ronga]

'''ns-3-LTP''' Licklider Transmission Protocol (LTP) is a point to point protocol for the use in deep space links. It have a number of interesting properties, mainly related to the constraints found in space links, like ultra-high round trip delay and so on. LTP is currenlty under revision as a proposed standard by the Consultative Committee for Space Data Systems (CCSDS), however its principles are well-known to the satellite networking community, RFCs and reference Linux implementations are available. An ns-3 implementation should comply with the already existing IETF specification and with the CCSDS one.
* ''Required Experience:'' C++
* ''Bonus Experience:'' Satellite and Deep Space networking
* ''Interests:'' Deep Space networking
* ''Difficulty:'' easy / medium
* ''Recommended reading:''
** [http://en.wikipedia.org/wiki/Licklider_Transmission_Protocol Licklider Transmission Protocol]
** [http://tools.ietf.org/html/rfc5325 RFC 5325: Licklider Transmission Protocol—Motivation]
** [http://tools.ietf.org/html/rfc5326 RFC 5326: Licklider Transmission Protocol—Specification]
** [http://public.ccsds.org/sites/cwe/rids/Lists/CCSDS%207341R2/Attachments/734x1r2.pdf Licklider Transmission Protocol (LTP) for CCSDS]

=== Inter-frequency measurement support for the LTE module ===

Mentors: [mailto:nbaldo@cttc.es Nicola Baldo] [mailto:mmiozzo@cttc.es Marco Miozzo]

* The ns-3 LTE module already allows to simulate LTE deployments where the base stations are placed at different carrier frequency; however, this is currently limited to static scenarios with no mobility, because only intra-frequency UE measurement are supported, and hence handover can only occur among cells at the same carrier frequency. The aim of this project is to develop supports for inter-frequency UE measurements, so that it can be leveraged both for idle and connected node mobility.

* ''Required Experience:'' C++, LTE
* ''Interests:'' Mobility Management in LTE
* ''Difficulty:'' hard
* ''Recommended reading:''
** [http://www.nsnam.org/docs/release/3.19/models/html/lte-design.html#ue-rrc-measurements-model documentation of the UE Measurement model in the ns-3 LTE module]
** 3GPP TS 36.331 section 5.5 Measurements
** 3GPP TS 36.133, Section 8.2 UE Measurements Procedures in RRC_CONNECTED State

=== LTE Fractional Frequency Reuse algorithms ===

Mentors: [mailto:nbaldo@cttc.es Nicola Baldo] [mailto:mmiozzo@cttc.es Marco Miozzo]

* The aim of this project is to develop a set of state-of-the-art Fractional Frequency Reuse algorithm implementations for the ns-3 LTE module. Interested students shall select a set of representative algorithms published in the scientific literature, and implement them in ns-3. The implementation shall be done within the LTE MAC Scheduler leveraging the X2 SON primitives.
* ''Required Experience:'' C++, LTE
* ''Interests:'' Self Organized Networks, HetNets, Inter Cell Interference Coordination
* ''Difficulty:'' hard
* ''Recommended reading:''
** [http://www.nsnam.org/docs/release/3.19/models/html/lte-design.html#mac LTE MAC in ns-3]
** [http://www.nsnam.org/docs/release/3.19/models/html/lte-design.html#x2-c-son-primitives LTE SON primitives in ns-3]
** Thomas Novlan, Jeffrey G. Andrews, Illsoo Sohn, Radha Krishna Ganti, Arunabha Ghosh, "Comparison of Fractional Frequency Reuse Approaches in the OFDMA Cellular Downlink"
** Alexander L. Stolyar, Harish Viswanathan, "Self-organizing Dynamic Fractional Frequency Reuse for Best-Effort Traffic Through Distributed Inter-cell Coordination"
** Heui-Chang Lee, Dong-Chan Oh, and Yong-Hwan Lee, "Mitigation of Inter-Femtocell Interference with Adaptive Fractional Frequency Reuse"
** there are lots of other papers on this topic, please do your own research

=== GPU acceleration for vector arithmetics in the spectrum module ===

Mentors: [mailto:nbaldo@cttc.es Nicola Baldo] [mailto:mmiozzo@cttc.es Marco Miozzo]

* The ns-3 spectrum module does a lot of vector arithmetics which in the current ns-3 version are just run on the CPU. The aim of this project is to develop the necessary code to offload these calculations to a GPU in order to achieve a hopefully significant speedup in the simulation of scenarios relying on the spectrum model (e.g., including LTE scenarios).
* ''Required Experience:'' C++
* ''Bonus Experience:'' CUDA, OpenCL...
* ''Interests:'' GPU acceleration
* ''Difficulty:'' hard
* ''Recommended reading:''
** [http://www.nsnam.org/docs/models/html/spectrum.html ns-3 spectrum module documentation]
** http://en.wikipedia.org/wiki/OpenCL
** http://en.wikipedia.org/wiki/CUDA

=== Carrier Aggregation support for the LTE module ===

Mentors: [mailto:mmiozzo@cttc.es Marco Miozzo] [mailto:nbaldo@cttc.es Nicola Baldo]

* The aim of this project is to bring the ns-3 LTE module closer to the LTE-A paradigm and, more in detail, consists of the introduction of the Carrier Aggregation (CA) functionality. The student will have to collect information from the 3GPP specification for what concerns the relevant EUTRA aspects. The implementation will involve mainly the physical, MAC and RRC layers.

* ''Required Experience:'' C++, LTE
* ''Interests:'' LTE-A, HetNet
* ''Difficulty:'' hard
* ''Recommended reading:''
** LTE-A HetNets using Carrier Aggregation, Nomor whitepaper [http://www.nomor.de/uploads/db/a3/dba3e71e617a0ab4b7d3821afd59cc5e/Newsletter_CA_HetNet_2013-06.pdf]
** [http://www.nsnam.org/docs/release/3.19/models/html/lte-design.html]
** 3GPP TS 36.211
** 3GPP TS 36.213
** 3GPP TS 36.331

=== Support of RRC IDLE mode procedures for the LTE module ===

Mentors: [mailto:nbaldo@cttc.es Nicola Baldo] [mailto:mmiozzo@cttc.es Marco Miozzo]

* The ns-3 LTE module currently supports a vast number of RRC CONNECTED mode procedures (e.g., handover, measurement reporting, etc), but has very limited support for RRC IDLE mode procedures (basically, only cell selection). The aim of this project is to 'close the circle' and provide full support for critical RRC IDLE mode procedures, such as PLMN selection, cell reselection, Tracking Area Update, Paging, etc.
* ''Required Experience:'' C++, LTE
* ''Interests:'' Mobility Management in LTE systems
* ''Difficulty:'' hard
* ''Recommended reading:''
** 3GPP TS 36.304 [http://www.3gpp.org/DynaReport/36304.htm]
** 3GPP TS 23.401, Section 5.3.3 ("Tracking Area Update Procedures") [http://www.3gpp.org/DynaReport/23401.htm]
** 3GPP TS 36.331

=== Improve ns-3 support to sensor networks, RIOT adaptation ===

Mentors: [mailto:danielcamara@gmail.com Daniel Camara]

The wireless sensor networks field is a rising star in terms of research, the number of applications and problems related to it increases every day. In fact, a whole new set of other research fields rely heavily on wireless sensor networks. E.g. smart cities, internet of the things, vehicular networks and public safety networks . This project intends to improve the support of ns-3 to to sensor networks. RIOT[1][2] is a brand new operating system for wireless sensor networks. It has a series of interesting characteristics that makes it a perfect candidate to became THE standard OS for small sensor devices.

This project intends to enable the execution of several instances of RIOT OS, over the same machine, and link these instances using ns-3. Why to simulate a sensor devices if we can emulate a whole network using a real sensor OS? Not only the simulations will be more realistic, but also we will be sure that the applications developed over this simulation environment will run seamless over real sensor nodes. The importance of this project is two folded. Without a shadow of a doubt it will be important and useful for the ns-3 community. However, up today RIOT still does not have a standard simulation environment. This project will provide RIOT users an invaluable access to the whole power of ns-3 simulations. It will be a tool that will be certainly used on all future developments and tests of RIOT.

* ''Support:'' The RIOT developers are interested on this project, since it will make their life easier ;). This means we will have access to them and any doubts about the operating system itself ''should'' be fast addressed by them.

* ''Required Experience:'' C/C++
* ''Interests:'' Sensor networks, simulation, operating systems
* ''Difficulty:'' medium
* ''Recommended reading:''
** [1] E. Baccelli, O. Hahm, M. Wählisch, M. Günes, T. C. Schmidt, [http://hal.inria.fr/hal-00768685/ RIOT: One OS to Rule Them All in the IoT], INRIA Research Report N° 8176, Project-Team HiPERCOM, ISSN 0249-6399 ISRN INRIA/RR--8176--FR+ENG, December 2012
** [2] RIOT OS web site, [http://riot-os.github.io/RIOT/ http://riot-os.github.io/RIOT/]
** [3] Heiko Will, Kaspar Schleiser, Jochen Schiller, [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.173.1862 A Real-Time Kernel for Wireless Sensor Networks Employed in Rescue Scenarios] The 4th IEEE International Workshop on Practical Issues In Building Sensor Network Applications (SenseApp 2009) Zürich, Switzerland; 20-23 October 2009

=== Port ns-3 components to Python 3.3 and improve Python code quality ===

Mentors: To be determined

Linux distributions in 2014 are expected to transition away from Python 2.7 support to Python 3.3 support. Ubuntu 14.04 release is already planning a Python 3.3-only default.

ns-3 has several components that rely on Python, and not all are Python 3.3+ compatible. This GSoC project would focus on updating our bindings generation process (pygccxml), PyViz visualizer, and wscript files (used by Waf) to support Python 3.3. Regarding wscript files in particular, student should also propose a refactoring and reorganization to make them easier to maintain in the future.
* ''Required Experience:'' C++ and Python
* ''Interests:'' Python development
* ''Difficulty:'' medium
* ''Recommended reading:'' pygccxml: http://sourceforge.net/projects/pygccxml/
* ''Recommended reading:'' Discussion on ns-developers list: http://mailman.isi.edu/pipermail/ns-developers/2014-March/011794.html

[[Category:GSoC]]

Optical network models

2013-12-18T21:14:58Z

Vedranm: PWNS project status update

ns-3 network simulator presently doesn't include any support for simulation of WDM optical networks in the official distribution. There are three optical network simulation modules under active development as of January 2013, that have the goal to make ns-3 into optical network simulator. Note, however, that the term "optical network simulator" is rather broad, as there are many types and features of optical networks one might want to model and use in simulation. This page tracks info about these optics modules, intented for simulating
* Optical Transport Network (OTN),
* Passive Optical Network (PON), and
* Radio over Fiber (RoF).

This page will be updated with new info as time permits.

== Optical Transport Network: Prototype WDM Network Simulator (PWNS) ==
[[File:PwnsLogo.png|thumb|PWNS project logo]]

=== Project name ===
Project name is a parody on OWns (Optical WDM network simulator, described in [1]), a project with similar goals implemented in ns-2.

=== Project scope ===
The goal of PWNS project is to implement models for WDM optical network components, including:
* optical cable, optical fiber, wavelength channel,
* multiplexer and demultiplexer, add-drop multiplexor,
* wavelength converter, wavelength selective switch, arrayed waveguide grating,
* optical cross connect (MEMS plane).

Prototype version dated June 2012 is described in [2]. Application to availability estimation is described in [3].

=== Planned release date ===
Current plan is to post the source code along with ns-3 release 3.20, which would be around March 2014.

=== Code ===
* '''Current version:''' https://bitbucket.org/rivanvx/ns-3-dev-otn-reliability (private for the time being, access granted on request, contact [[User:Vedranm|Vedran Miletić]])
* older versions, severely out of date and likely broken: http://code.nsnam.org/vedranm/ns-3-dev-optics and http://code.nsnam.org/vedranm/ns-3-dev-optics-old

=== References ===
# Wen, B. and Bhide, N.M. and Shenai, R.K. and Sivalingam, K.M., ''Optical wavelength division multiplexing (WDM) network simulator (OWns): architecture and performance studies''
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Modelling optical network components: a network-simulator based approach'' // Proceedings on the IX. International symposium on Telecommunications - BIHTEL 2012.
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Impact Evaluation of Physical Length of Shared Risk Link Groups on Optical Network Availability Using Monte Carlo Simulation'' // Proceedings of the 18th European Conference on Networks and Optical Communications, NOC 2013 / Leitgeb, Erich (ur.).

== Passive Optical Network ==
=== Project Summary ===

The aim of this project is to develop PON (passive optical network) models for NS-3. It is under the umbrella of [http://www.ctvr.ie/ CTVR] that supports various research topics related with telecommunication.

=== Project Scope ===

The project will implement models for passive optical networks. The current focus is to develop one model for simulating XG-PON, which is also known as [http://en.wikipedia.org/wiki/10G-PON 10G-PON]. We will also investigate how to use this model and WiMAX/LTE models distributed with NS-3 to simulate the coming FTTC (Fiber To The Cell) network scenario. In the future, models for other PON technologies, such as [http://en.wikipedia.org/wiki/10G-EPON 10G-EPON] and [http://en.wikipedia.org/wiki/Passive_optical_network#Long-Reach_Optical_Access_Networks Long Reach PON], will also be developed to carry out comparative studies.

The current prototype is described in [1] and more detailed description will be posted here as soon as possible.

=== Code ===

The code will be made public in September-December, 2013 timeframe through the websites of CTVR and [http://www.ucc.ie/en/misl/ MISL].

=== References ===

# X. Wu, K.N. Brown, C.J. Sreenan, P. Alvarez, M. Ruffini, N. Marchetti, D. Payne, and L. Doyle, ''An XG-PON Module for the NS-3 Network Simulator'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

== Radio over Fiber ==
=== Project scope ===
The goal of our work is to investigate and optimize the performance of MAC (Medium Access Control) radio protocols when it is used in a RoF (Radio-over-Fiber) architecture. Our study is mainly focused on IEEE 802.11 over RoF transmissions. We developed a RoF model in ns-3 based on the YANS Wi-Fi model which enables the simulation of 802.11 RoF systems. The current model includes [1]:

* Distributed Antenna Systems RoF modeling;
* Optical module computing delays and attenuations undergone by the radio signal transmission over fiber links.

Further points to be implemented:

* Protocol-independent model (not limited to Wi-Fi transmissions);
* Integration of optical network component models developed by PWNS (Prototype WDM Network Simulator).

=== Code ===
The source code is not yet available for the public.

=== References ===
# Sebastien Deronne, Veronique Moeyaert and Sebastien Bette, ''Simulation of 802.11 Radio-over-Fiber Networks using ns-3'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

[[Category:Models]]

Doxygen-warnings

2013-11-26T23:17:35Z

Vedranm: Replace wiki http links with Mediawiki syntax

{{TOC}}

= Doxygen warning removal =

This page is to help coordinating the efforts in fixing [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].

As a followup of [[Sprints|Friday November 15 ns-3 Sprint]], we'd like to coordinate the efforts of Doxygen warning removal.

It must be pointed out that warning removing is not good per-se. It is a way to complete the documentation and make it better. 

Undocumented functions leads to poor coding and, ultimately, not be able to use the ns-3 full power. 

Moreover, bad or missing documentation means '''bugs''' !

= Doxygen work status =
The following table might seems overwhelming. And the warning are just the ones in the model and helper folders. 

However, mind that many are chain-warnings, meaning that once you fix the master one in the base class, many of them will disappear. More on that at the bottom of the page.

The current doxygen warning status, by module is:
{| class="wikitable"
|-
! Number of warnings !! Module !! Who's working on it
|-

| 4086 || lte ||
|-
| 1903 || wifi || Daniel L.
|-
| 1727 || wimax ||
|-
| 1416 || core ||
|-
| 696 || network || Vedran M.
|-
| 466 || mesh ||
|-
| 368 || uan ||
|-
| 363 || dsr ||
|-
| 259 || mobility ||
|-
| 237 || spectrum ||
|-
| 209 || propagation ||
|-
| 191 || olsr ||
|-
| 188 || applications ||
|-
| 171 || stats ||
|-
| 133 || netanim ||
|-
| 133 || config-store ||
|-
| 129 || visualizer ||
|-
| 126 || buildings ||
|-
| 84 || energy ||
|-
| 48 || openflow ||
|-
| 47 || point-to-point ||
|-
| 46 || dsdv ||
|-
| 41 || point-to-point-layout ||
|-
| 39 || mpi ||
|-
| 38 || aodv ||
|-
| 33 || fd-net-device ||
|-
| 30 || bridge ||
|-
| 24 || brite ||
|-
| 22 || nix-vector-routing ||
|-
| 21 || antenna ||
|-
| 18 || emu ||
|-
| 17 || virtual-net-device ||
|-
| 16 || csma ||
|-
| 11 || tap-bridge ||
|-
| 8 || csma-layout ||
|}

= How to proceed =
The procedure is simple.
# Post online that you're working on a module. Eventually coordinate with who's already working on the same module.
# Follow the direction in the [[Sprints|Sprint]] page to setup Doxygen to show you the warnings.
# Start with base classes. Mind that ''virtual'' functions can (and should) be documented only in the base class.
# Don't be afraid of the numbers. I was able to kill 1400 warnings in 2 days (just in my spare time).
# Once you have a patch, post it in Bugzilla: [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].
# Go drink a beer, you deserve it.

= Hint and tips =

The doxygen.warnings.report.sh script will make a long list of warnings. You're probably interested in the ones from a single module. The following command might help:

grep <module name> doc/doxygen.warnings.log | sort > doc/my.doxygen.warnings.txt
Now you have a shorter list of bugs to work with. Cut out the ones from the tests and examples (or not, depends on how pedantic you are). Those are your warnings to kill.

--[[User:Tommaso|Tommaso]] ([[User talk:Tommaso|talk]]) 16:29, 26 November 2013 (EST)

Doxygen-warnings

2013-11-26T23:16:08Z

Vedranm: Add myself on network module

{{TOC}}

= Doxygen warning removal =

This page is to help coordinating the efforts in fixing [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].

As a followup of [http://www.nsnam.org/wiki/Sprints Friday November 15 ns-3 Sprint], we'd like to coordinate the efforts of Doxygen warning removal.

It must be pointed out that warning removing is not good per-se. It is a way to complete the documentation and make it better. 

Undocumented functions leads to poor coding and, ultimately, not be able to use the ns-3 full power. 

Moreover, bad or missing documentation means '''bugs''' !

= Doxygen work status =
The following table might seems overwhelming. And the warning are just the ones in the model and helper folders. 

However, mind that many are chain-warnings, meaning that once you fix the master one in the base class, many of them will disappear. More on that at the bottom of the page.

The current doxygen warning status, by module is:
{| class="wikitable"
|-
! Number of warnings !! Module !! Who's working on it
|-

| 4086 || lte ||
|-
| 1903 || wifi || Daniel L.
|-
| 1727 || wimax ||
|-
| 1416 || core ||
|-
| 696 || network || Vedran M.
|-
| 466 || mesh ||
|-
| 368 || uan ||
|-
| 363 || dsr ||
|-
| 259 || mobility ||
|-
| 237 || spectrum ||
|-
| 209 || propagation ||
|-
| 191 || olsr ||
|-
| 188 || applications ||
|-
| 171 || stats ||
|-
| 133 || netanim ||
|-
| 133 || config-store ||
|-
| 129 || visualizer ||
|-
| 126 || buildings ||
|-
| 84 || energy ||
|-
| 48 || openflow ||
|-
| 47 || point-to-point ||
|-
| 46 || dsdv ||
|-
| 41 || point-to-point-layout ||
|-
| 39 || mpi ||
|-
| 38 || aodv ||
|-
| 33 || fd-net-device ||
|-
| 30 || bridge ||
|-
| 24 || brite ||
|-
| 22 || nix-vector-routing ||
|-
| 21 || antenna ||
|-
| 18 || emu ||
|-
| 17 || virtual-net-device ||
|-
| 16 || csma ||
|-
| 11 || tap-bridge ||
|-
| 8 || csma-layout ||
|}

= How to proceed =
The procedure is simple.
# Post online that you're working on a module. Eventually coordinate with who's already working on the same module.
# Follow the direction in the [http://www.nsnam.org/wiki/Sprints Sprint] page to setup Doxygen to show you the warnings.
# Start with base classes. Mind that ''virtual'' functions can (and should) be documented only in the base class.
# Don't be afraid of the numbers. I was able to kill 1400 warnings in 2 days (just in my spare time).
# Once you have a patch, post it in Bugzilla: [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].
# Go drink a beer, you deserve it.

= Hint and tips =

The doxygen.warnings.report.sh script will make a long list of warnings. You're probably interested in the ones from a single module. The following command might help:

grep <module name> doc/doxygen.warnings.log | sort > doc/my.doxygen.warnings.txt
Now you have a shorter list of bugs to work with. Cut out the ones from the tests and examples (or not, depends on how pedantic you are). Those are your warnings to kill.

--[[User:Tommaso|Tommaso]] ([[User talk:Tommaso|talk]]) 16:29, 26 November 2013 (EST)

Ns-3.19

2013-10-13T14:29:48Z

Vedranm: Add time units as something being worked on

{{TOC}}

This page summarizes the ongoing release planning for ns-3.19. The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].

The release managers are [mailto:tomh@tomh.org Tom Henderson] and [bpswenson3@gatech.edu Brian Swenson]. Contact them if you would like to coordinate your software inclusion with this release.

= Release schedule =

ns-3.19 is scheduled for December 11, 2013. There will likely be a new feature freeze about 1 month prior to that, and a code freeze about a week before the final release. More details will be posted at a later date.

= Proposed supported platforms =

Our primary platforms for this release are planned to be:
* Latest Fedora (32/64 bit systems)
* Ubuntu 13.10 (32/64 bit systems)
* Ubuntu 12.04 LTS and 10.04 LTS (64 bit)
* Mac OS 10.8 Mountain Lion and 10.9 Mavericks (64 bit) with Xcode 5.0
* FreeBSD 8.4, 9.2 (64 bit) using gcc and clang compilers

= Packaging =

ns-3.19 will be packaged as a source tarball as before: ns-allinone-3.19.tar.bz2.

The tarball will contain:
* pybindgen
* netanim
* ns-3.19
* bake

where bake is used to fetch optional ns-3 components.

= Release goals =

This release will be mainly aimed at cleaning out the tracker as much as possible. After this release, we plan to take the next step at further [[BakeIntegration | modularizing the code]].

We aim to merge our 2013 GSoC contributions in this release.

The following goals are being worked on at this time:
* fix Python bindings generation so that it works on recent gccs (clang also?) (bug 1530)
* resolve all clang errors (bug 1560)
* '''Clang 3.2''': https://codereview.appspot.com/10975043
* '''Visual Studio''': https://codereview.appspot.com/8932044/
* '''Introduce additional time units''': https://codereview.appspot.com/14632043/

More goals to be added at a later date.

= Schedule =

== Oct 1-15 ==

* clang support
* look into Python bindings problem/resolution again
* clean up Roadmap and CurrentDevelopment wiki pages

== Oct 16-31 ==

== Nov 1-15 ==

== Nov 16-30 ==

= Bugs being worked =

We will use bugzilla to track [http://www.nsnam.org/wiki/index.php/User_FAQ#Bug_Priorities bug priorities] (esp. P1 blocker bugs) for the next release.

Data Collection Framework

2013-08-05T11:50:11Z

Vedranm: Note about statistics

== Scope ==
Data Collection Framework is responsible for simulation data monitoring, on-line reduction and storage

== Arch and API Proposal ==

Simulation data collection process is a three-stage pipeline (''Felipe, I am sorry for badly misusing your terms''):

1. Models report ''events'' using existing trace source mechanism.

2. A number of ''probes'' are set up to listen interesting events. Probes are responsible for on-line data normalization and reduction.
Probes report reduced data using trace source mechanism, this allows user to organize probes into trees.

3. One or more ''collectors'' are set up to listen interesting probes. Collectors are responsible to store data in some meaningful format.

The following design restrictions are suggested to follow:

1. Probes should not generate data by themselves. This restriction allow probes to be reusable.

2. Collectors should not change data they receive from probes. This restriction allow collectors to be reusable.

Proof of concept implementation of these architecture is located here: http://codereview.appspot.com/3105042 and explained in some detail below.

=== Events & Probes ===

Events can be of any type (= trace source signature), actually every trace source can be considered as an event for data collection framework.

To be visible to the data collection framework event must be listened by some ''probe'' object. This is a probe responsibility to match event signature and produce some meaningful output. The simplest probe can listen for (void) events and count them.

Probes report their output data streams as trace sources, e.g. probe reporting {time, double} time series can have an "Output" trace source with (Time, double) signature. This allow user to create probe trees. Note that while number of probe inputs is not restricted here, it is recommended to have single probe output for all probes.

The following probe hierarchy is implemented in the [http://codereview.appspot.com/3105042 proof-of-concept example]:

- Probe
- DoubleProbe
- CountProbe
- DivProbe
- StringProbe
- AttributeProbe

It is assumed that there will be created large number of "basic" probes, implementing all simple data reduction/normalization operations. Users can add their own probes as well.

=== Collectors ===

Collectors are responsible to listen probes and store data to some user-meaningful format. In current implementation collector also owns all registered probes (i.e. controls their lifetime). Only ''supported'' probe types can be registered on the collector, because collector must know how to store probe output data. This is the only place in the data collection pipeline, where data type is restricted.

CsvCollector in the [http://codereview.appspot.com/3105042 proof-of-concept example] supports string and double time series (StringProbe and DoubleProbe and their subclasses) and stores every registered probe as single CSV file. Many more useful collectors can be created.

There can be more than one collector in the running application. I can imagine one collector saving output data series, another one deciding for transient detection and run termination and the last one saving mobility/topology events in the visualization-compatible format.

== Informal requirements ==

This is a place to collect functional requirements, examples of intended use and expected behavior for the data collection framework.

=== Null ===
I don't want to collect any data from my simulation. In this case I expect that I don't need to use (and even known about) the data collection framework. Also I expect no notable performance degradation of my legacy ns-3 applications.

=== Global data collection window ===
I want to setup data collection start and stop times. All events before start and after stop will be ignored by this framework.

=== Local data collection window ===
I want to be able to individually change data collection window for every enabled data source.

=== Local scalar counter ===
I have some interesting event in my model and I have a number of model instances.
I want data collection framework to count the number of events and at any time in simulation access per-instance values of the counter for some (m.b. all) model instances. I expect that to do this I will need a single line of code for every model instance being monitored or one line to enable data collection from all already created instances. I expect that data collection configuration will give me some "handles" to address counter values for individual model instances. I'd like to have simple way to apply avg, sum, min, max, var, ... functions to the vector of these "handles", as well as save all values to the output database.

=== Global scalar counter ===
As above, but I just want to access the sum of counter value over all model instances at the end of simulation. I expect that to do this I need to add single line of code to configure data collection and one more line to configure how this data will be stored. I want to both store this single value to the output database and access it as a variable from the code.

=== Local vector double ===
As above I have an interesting event in my model (e.g. packet was queued) but this time I have some additional double number for that event (e.g. packet size). All events in the data collection window result in the sample of pairs (time, double) for every model instance. I want to access (iterate, store to the output database, apply function) this sample.

=== Global vector double ===
As above, but I don't care of which model instance fires events. I want to access global sample (time, double) produced by several (m.b. all) model instances.

=== Vector to scalar reduction ===
I want to automatically apply some function to the vector double statistics. The following functions must be "built-in":
*sample size
*sample total time
*last value, last timestamp
*sum
*sample average (\sum x / size)
*time average (\sum (x * \delta t) / time)
*sum / time
*min, max, var
I should be able to write my own reduction function. The function output can be accessed as scalar double, like the counter from above. Since vectors can be huge I need an option of keeping only reduced value in memory / output database. Arbitrary number of reduced scalars can be obtained from the same vector.

==== Use case: wifi throughput ====
Classical experiment of measuring aggregate wifi throughput a-la Bianchi is an illustration of reduced (sum/time) global double (packet size received at wifi MAC) use case.

==== Use case: wifi channel utilization ====
I want to calculate per-device wifi channel utilization defined as the fraction of time PHY was not IDLE. To do this, I can add new trace source with single double argument and call it with 1.0 when PHY goes from IDLE state and with 0.0 when PHY becomes IDLE. Then I apply "time average" reduction (reduced local double). Alternatively I can do this in non-intrusive way, writing an adapter class, which listenes to PHY state change events of the form (old_state, new_state) and produces data source events as above.

==== Use case: average MANET node degree ====
I want to access time- and node-average node degree (number of neighbors) in some particular manet scenario using OLSR routing. To do this, I can add new double data source "Number of neighbors" to OLSR protocol and fire it when number of neighbors changes and reduce these per-node vectors to per-node time averages. At the end of simulation I will apply "avg" function to the resulting set of per-node values to get node- and time- average degree.

=== Vector resampling ===
I want to automatically convert my "raw" vector of (time, double) samples to the new vector of (time, double) samples in such way, that new time values are strictly periodical and _globally_ synchronous. Example: vector of samples {(0, x1), (1, x2), (3.5, x3), (4.1, x4)} is resampled to the vector {(0, y1), (2, y2), (4, y4)}. A set of original samples inside the same time "slot" of the resampled vector produce one value which is representative of the "slot". The resampled value is computed in the same way as the whole vector is reduced to scalar, see above. The same built-in reduction function are supported:
*count (= number of events in the slot, = sub-sample size)
*last value, last timestamp
*sum
*sub-sample average (\sum x / size)
*time average (\sum (x * \delta t) / time)
*sum / time
*min, max, var
User specified functions are supported too. The size of the time slot for resampling is restricted to be the same for _all_ data vectors (global framework parameter) and all resampled vectors are synchronous in the corresponding data collection windows. Vectors, resampled in this way can be compared slot-by-slot.

=== Functions on vectors and pipelines ===
A want to apply a function to several (in general) resampled vectors to produce single new vector. This vector can be used in the same way as
original ones: feed to the input of another function, reduced to scalar, written to the output database.

==== Use case: moving window average ====
I can apply moving window average (window size is a multiple of the time slot) to detect the end of transient process in my observable.

==== Use case: packet delivery ratio ====
I want to measure the PDR of single CBR stream. CBR stream is implemented as two applications: traffic source and traffic sink. Source application fires a "packet send" event, this produces a vector of counters of the form (time, 1.0). Sink application fires a "packet received" event, this produces an another vector of counters. Both vectors are resampled with "count" function. Resampled vector are inputs to the "a/b" function and the output vector is a time-dependent packet delivery ratio.

==== Use case: ITU R-factor ====
As above, but I want to automatically measure the ITU E-model R factor, which is a function of PDR and average packet delay. To do this, sink application from above also fires "packet received" events with a double delay parameter. This vector is resampled and feed to the R-factor calculation module together with PDR vector. Total pipeline looks this way:

Packet send
Source: ---------------\
| Packet delivery ratio
Packet recvd |--------------------------\
Sink : ---------------/ | R-factor
delay |-----------------
------------------------------------------/

=== Local factor ===
I want to access per-instance model attributes using data collection framework on the same basis as counter above, e.g. store to the output database as factors (inputs) of my experimental plan. Attributes can be both integers/doubles, strings (e.g. "11Mbps" or "Minstrel") or booleans (true/false or on/off semantics) and the last value will be recorded if attribute changes with time.

=== Global factor ===
In my simulation all instances of the same model have the same value of some particular attribute (e.g. the same Slot for all WifiMac instances). I want to access this value as above using model TypeId. I want to know, what will happen if different instances of the model do have different values for this attribute.

== March 2013 code review ==

This is just a placeholder on the wiki to store some documentation related to the code review (please discuss on ns-3-reviews or within the code review issue):
https://codereview.appspot.com/7436051/

* Slides [https://www.nsnam.org/wiki/index.php/File:Data-collection-framework-code-review.pdf summarizing this issue]
* Draft of [https://www.nsnam.org/wiki/index.php/File:Ns-3-experiment.pdf proposed manual documentation]

== July 2013 code review ==

The code review issue has been updated:
https://codereview.appspot.com/10974043

The data collection code is intended for src/stats directory. New ns-3 manual documentation is posted here:
* Draft of [https://www.nsnam.org/wiki/index.php/File:Ns-3-data-collection-manual.pdf proposed manual documentation]

== Use cases ==

This section describes a few use cases that the framework is intended to be able to support (not all capabilities are implemented).

This supplements the discussion on informal requirements [[Data_Collection_Framework#Informal_requirements | above]].

=== interface bandwidth statistics ===

A user previously asked on ns-3-users:

Basically, what is suggested to take a percentage of how much
bandwidth is taken in a point to point link? Is flowmonitor the
right tool for this, because I have gone through the documentation
of the module however I am not sure that I require all that
complexity. basically, I would like to simple take bandwidth
measurements at any given point in time during the simulation of
certain designated links.

One could envision some kind of PointToPointHelper methods to print this information out, using BasicStatsCollector.

/* Plot sending and receiving throughput, averaged at 1 second
intervals, in a Gnuplot */
PointToPointHelper::PlotInterfaceThroughput (Ptr<NetDevice> nd)
PointToPointHelper::PlotInterfaceThroughputAll (const NetDeviceContainer &ndc)
PointToPointHelper::WriteInterfaceThroughtput ... /* File variant*/

=== athstats helper ===

There is an athstats helper class that prints out formatted text statistics of the Wifi NetDevice corresponding to what the athstats tool might print out:

examples/wireless/wifi-ap.cc:
AthstatsHelper athstats;
examples/wireless/wifi-ap.cc: athstats.EnableAthstats ("athstats-sta", stas);
examples/wireless/wifi-ap.cc: athstats.EnableAthstats ("athstats-ap", ap);

This was written before the data collection framework existed. It consists of a helper class that mainly hooks a number of traces in the WifiNetDevice, collects statistics from them, and periodically writes the statistics out to file, and resets:

void DevTxTrace (std::string context, Ptr<const Packet> p);
void DevRxTrace (std::string context, Ptr<const Packet> p);
void TxRtsFailedTrace (std::string context, Mac48Address address);
void TxDataFailedTrace (std::string context, Mac48Address address);
void TxFinalRtsFailedTrace (std::string context, Mac48Address address);
void TxFinalDataFailedTrace (std::string context, Mac48Address address);
void PhyRxOkTrace (std::string context, Ptr<const Packet> packet, double snr, WifiMode mode, enum WifiPreamble preamble);
void PhyRxErrorTrace (std::string context, Ptr<const Packet> packet, double snr);
void PhyTxTrace (std::string context, Ptr<const Packet> packet, WifiMode mode, WifiPreamble preamble, uint8_t txPower);
void PhyStateTrace (std::string context, Time start, Time duration, enum WifiPhy::State state);

The print to file is just a formatted printf:

snprintf (str, 200, "%8u %8u %7u %7u %7u %6u %6u %6u %7u %4u %3uM\n"

In the context of the data collection framework, this helper is analogous to a custom Collector object, that hooks directly to trace sources (without probes), and also contains FileAggregator support (that is, it is a combined Collector+Aggregator).

The DCF way to write this would be as follows. First, if there were probes available for these trace signatures, they could be added, but this is not strictly necessary. The Athstats helper could be written still largely as a custom collector, but the file handling aspects could be handled perhaps by a stock file aggregator object, to which the specially formatted printf string format could be provided.

=== object start/stop time tracker ===

Vedran asked whether the Object Start/Object Stop time tracker could be implemented with DCF. Basically, this is a variation on the requirement stated above for "Wifi Throughput"; what is desired is something like a "Duty Cycle collector" that will keep track of the proportion of time that an object was on or off, and report statistics at the end of the simulation.

In discussing this use case, we observed that there is a need to actually stop the statistics framework at the end of the simulation, so that the time from the last event was recorded to the end of the simulation. That is, if the last state transition was at time t=1000 seconds, but the simulation ended at time t=2000 seconds, we need to ensure that this kind of report covers the time range of 1000-2000 seconds, so we need to stimulate somehow the report at time t=2000 seconds even if there is not an underlying state change to drive it. (Actually, '''this should be discussed further''': it could cause problems with reliability analysis -- it actually did in my experiments -- as it can happen that a certain object whose state changes depend on another object remains in started or stopped state until the end of simulation because that another object ended its state changing time. Sorry if this explanation isn't very clear; I'm willing to elaborate further if necessary. -- [[User:Vedranm|Vedran Miletić]])

== Development road map ==

''This section was last edited July 29, 2013''

We are planning to merge the initial portion of data collection framework for ns-3.18 (August release).
* basic probes
* file aggregators
* gnuplot aggregators

Goal: easily enable the dumping of raw ns-3 trace source data into files and gnuplots

=== Items to complete for ns-3.18 ===

* test code coverage for helpers, file and gnuplot aggregators, and additional probes
* add coverage in ns-3 tutorial

=== Prioritized list for ns-3.19 ===

* Support more probes of all ns-3 trace sources
* BasicStatsCollector, helpers, and examples: compute statistics to reduce probe'd data before writing to files, plots, and databases
** provide helper objects, similar to Pcap and Ascii trace helpers, that easily enable the generation of output files or gnuplots for device-level interface bandwidth usage statistics, for Lte, WiFi, WiMax, Csma, PointToPoint devices
* StateTrackerCollector: support the Wifi state machine, and Object Start/Stop time tracker use cases
* Migrate Joe Kopena's data collection code and example to the new framework
** this will enable some SQLite database support
* Add ability to periodically write out interim results for long simulations

=== Some core ns-3 issues ===

* This [https://www.nsnam.org/bugzilla/show_bug.cgi?id=127 | bug] on lack of type information in trace sources needs a solution, to clean up the helpers
* DCF heavily uses the configuration store and config path database, these configuration paths should be [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1213 audited (bug 1213)]

== Background and related work ==

* Joe Kopena's framework (stats module): [[Statistical Framework for Network Simulation]]
* Akaroa: http://www.cosc.canterbury.ac.nz/research/RG/net_sim/simulation_group/akaroa/about.chtml
* Poster at simutools: http://www.eg.bucknell.edu/~perrone/Research_files/poster.pdf
* Research paper on automation: http://www.eg.bucknell.edu/~perrone/Research_files/paper.pdf
* Another related paper: M. Andreozzi, G. Stea, C. Vallati, "A Framework for Large-scale Simulations and Output Result Analysis with ns-2", Proceedings of QoSim 2009, Rome, Italy, March 6, 2009 [11/24].

Installation

2013-08-01T14:09:04Z

Vedranm: Update link for QtCreator, add link for NetBeans

{{TOC}}

This is a detailed installation guide for ns-3. Basic installation instructions can be found in the [http://www.nsnam.org/docs/release/tutorial/html/index.html ns-3 tutorial] (see [http://www.nsnam.org/docs/release/tutorial/html/getting-started.html Getting Started chapter]).

== Supported platforms ==

ns-3 is primarily developed on GNU/Linux platforms, and the minimal requirements to run basic simulations are a [http://gcc.gnu.org/ gcc] or [http://clang.llvm.org/ clang] compiler and [http://www-python.org/ Python] interpreter (details on versions below).

=== Operating system and compiler support ===

ns-3 is supported on the following primary platforms:

# Linux x86 and x86_64: gcc versions 4.1 through 4.7 and, 3.4.6, clang versions 3.0 and 3.1.
# FreeBSD x86 and x86_64: gcc version 4.2, clang versions 3.0 and 3.1.
# Mac OS X ppc and x86: gcc versions 4.0 and 4.2,

By supported, we mean that the project tries to support most or all of the build options on these platforms unless there is a good reason to exclude the option; and at least the debug build will compile. If you intend to do serious work using ns-3, and are forced by circumstances to use a Windows platform, consider virtualization of a popular Linux platform or using [http://www.ubuntu.com/download/desktop/windows-installer Ubuntu with wubi]. In both cases you end up with a fully functional Linux system and ns-3 distribution.

ns-3 may also run on currently unsupported platforms. For example, an alternative Windows platform is MinGW. There are maintainers who attempt to keep a subset of ns-3 running on MinGW, but it is not "officially" suppported. Previously, ns-3 also ran on Cygwin, but it's not officially supported anymore. This means that bugs filed against MinGW will be addressed as time permits.

Additional maintainers are invited to make more platforms, compilers and environments supported.

=== Integrated development environment support ===

==== Eclipse ====
The [http://www.eclipse.org/ Eclipse IDE] is not an officially supported platform, but some developers use it and have compiled a [[HOWTO configure Eclipse with ns-3|HOWTO]].

==== NetBeans ====
[https://netbeans.org/ NetBeans] is not officially supported either, but there is a [[HOWTO_configure_NetBeans_with_ns-3|HOWTO]] as well.

==== QtCreator ====
Same rule applies to [http://qt-project.org/wiki/category:tools::qtcreator Qt Creator]; it's not officially supported, but there are developers that use it and [[HOWTO configure QtCreator with ns-3|HOWTO]] is available.

=== Support for optional features ===

There are a few options that are not enabled by default and are not available on all platforms. At the end of the configuration process (explained below), the status of these options are shown as detected by a '''waf''' script:

<pre>
---- Summary of optional NS-3 features:
Python Bindings : not enabled (Python library or headers missing)
BRITE Integration : not enabled (BRITE not enabled (see option --with-brite))
NS-3 Click Integration : not enabled (nsclick not enabled (see option --with-nsclick))
GtkConfigStore : not enabled (library 'gtk+-2.0 >= 2.12' not found)
XmlIo : not enabled (library 'libxml-2.0 >= 2.7' not found)
Threading Primitives : enabled
Real Time Simulator : enabled
Emulated Net Device : not enabled (<netpacket/packet.h> include not detected)
Network Simulation Cradle : not enabled (architecture None not supported)
MPI Support : not enabled (option --enable-mpi not selected)
NS-3 OpenFlow Integration : not enabled (Required boost libraries not found)
SQlite stats data output : not enabled (library 'sqlite3' not found)
Tap Bridge : not enabled (<linux/if_tun.h> include not detected)
PyViz visualizer : not enabled (Python Bindings are needed but not enabled)
Use sudo to set suid bit : not enabled (option --enable-sudo not selected)
Build tests : not enabled (defaults to disabled)
Build examples : not enabled (defaults to disabled)
GNU Scientific Library (GSL) : not enabled (GSL not found)
</pre>

Generally if the platform is missing some requirement for an option it is marked as "not enabled." Note that "disabled by user request" will be shown when the user explicitly disables a feature (such as "--disable-python"); and if a feature defaults to disabled this will also be noted (e.g., option --enable-sudo not selected).

The table below is meant to help sort out the different features and on which platforms they are supported. This table reflects the status as of ns-3.15 and may have changed since then:

{| border=1 cellspacing=0 cellpadding=3

|+ Option status
! Option !! Linux !! FreeBSD !! Mac OS X
|-
! Optimized build
| Y || Y || Y
|-
! Python bindings
| Y || Y || Y
|-
! Threading
| Y || Y || Y
|-
! Real-time simulator
| Y || Y || N
|-
! Emulated Net Device
| Y || N || N
|-
! Tap Bridge
| Y || N || N
|-
! Network simulation cradle
| Y1 || ? || N
|-
! Static builds
| Y || Y || Y

|}

''Key:'' '''Y''' = supported; '''N''' = not supported; '''?''' = unknown; '''dev''' = support in ns-3-dev (next release)

''Notes:''

# NSC works best with gcc-3.4 or gcc-4.2 or greater series. Try to avoid using gcc-4.0 and gcc-4.1 series; some build problems have been found with these versions of compilers.

== Prerequisites ==

The core of ns-3 requires a gcc/g++ installation of 3.4 or greater, and Python 2.4 or greater. As mentioned above, different options require additional support. This is a list of packages (for Debian/Ubuntu systems) that are needed to support different ns-3 options. Note that other distributions (e.g., Fedora, FreeBSD) may have different package names or capitalization (e.g. ImageMagik). Installation should be similar for Red Hat/Fedora based systems, with "yum" replacing "apt-get", but some differences exist, so below is a guide for both Ubuntu (should generally apply to Debian) and Fedora/RedHat-based systems:

=== Linux ===

==== Ubuntu/Debian ====

The following list of packages should be accurate for Ubuntu 12.04 release; other releases or other Debian-based systems may slightly vary.

* '''minimal requirements for C++ (release):''' This is the minimal set of packages needed to run ns-3 from a released tarball.

sudo apt-get install gcc g++ python

* '''minimal requirements for Python (release):''' This is the minimal set of packages needed to work with Python bindings from a released tarball.

sudo apt-get install gcc g++ python python-dev

* Mercurial is needed to work with ns-3 development repositories.

sudo apt-get install mercurial

* Running python bindings from the ns-3 development tree (ns-3-dev) requires bazaar

sudo apt-get install bzr

* Debugging:

sudo apt-get install gdb valgrind

* GNU Scientific Library (GSL) support for more accurate WiFi error models

sudo apt-get install gsl-bin libgsl0-dev libgsl0ldbl

* The Network Simulation Cradle (nsc) requires the flex lexical analyzer and bison parser generator:

sudo apt-get install flex bison libfl-dev

* To install gcc-3.4 for some Network Simulation Cradle (nsc) stacks:

sudo apt-get install g++-3.4 gcc-3.4

* To read pcap packet traces

sudo apt-get install tcpdump

* Database support for statistics framework

sudo apt-get install sqlite sqlite3 libsqlite3-dev

* Xml-based version of the config store (requires libxml2 >= version 2.7)

sudo apt-get install libxml2 libxml2-dev

* A GTK-based configuration system

sudo apt-get install libgtk2.0-0 libgtk2.0-dev

* To experiment with virtual machines and ns-3

sudo apt-get install vtun lxc

* Support for utils/check-style.py code style check program

sudo apt-get install uncrustify

* Doxygen and related inline documentation:

sudo apt-get install doxygen graphviz imagemagick
sudo apt-get install texlive texlive-extra-utils texlive-latex-extra

* The ns-3 manual and tutorial are written in reStructuredText for Sphinx (doc/tutorial, doc/manual, doc/models), and figures typically in dia:

sudo apt-get install python-sphinx dia

'''Note:''' Sphinx version >= 1.12 required for ns-3.15. To check your version, type "sphinx-build". To fetch this package alone, outside of the Ubuntu package system, try "sudo easy_install -U Sphinx".

* Support for Gustavo Carneiro's ns-3-pyviz visualizer

sudo apt-get install python-pygraphviz python-kiwi python-pygoocanvas libgoocanvas-dev

* Support for openflow module (requires some boost libraries)

sudo apt-get install libboost-signals-dev libboost-filesystem-dev

* Support for MPI-based distributed emulation

sudo apt-get install openmpi*

==== Fedora/RedHat ====

The following list of packages should be accurate for Fedora 12/CentOS 5.4 release; other releases may slightly vary.

* '''minimal requirements for C++ (release):''' This is the minimal set of packages needed to run ns-3 from a released tarball.

yum install gcc gcc-c++ python

* '''Note:''' If you are using CentOS 5.4 or RHEL 5, you may want to also get and use the gcc44 packages; see the [[Troubleshooting]] page.

* '''minimal requirements for Python (release):''' This is the minimal set of packages needed to work with Python bindings from a released tarball.

yum install gcc gcc-c++ python python-devel

* Mercurial is needed to work with ns-3 development repositories.
You may want to install mercurial from rpmforge repository (instructions [http://www.trinitycore.org/forum/mercurial-centos-t3113.html here]) or EPEL.

yum install mercurial

* Running python bindings from the ns-3 development tree (ns-3-dev) requires bazaar. You may need EPEL repository for this.

yum install bzr

* An optional but recommended package (for improving some wireless model fidelity) is GNU scientific library:

yum install gsl gsl-devel

* A GTK-based configuration system

yum install gtk2 gtk2-devel

* Debugging:

yum install gdb valgrind

* Doxygen and related inline documentation:

yum install doxygen graphviz ImageMagick

* The ns-3 manual and tutorial are written in reStructuredText for Sphinx (doc/tutorial, doc/manual, doc/models), and figures typically in dia:

yum install python-sphinx dia texlive texlive-latex

'''Note:''' Sphinx version >= 1.12 required for ns-3.15. To check your version, type "sphinx-build". To fetch this package alone, outside of the Fedora package system, try "sudo easy_install -U Sphinx"

* The Network Simulation Cradle (nsc) requires the flex lexical analyzer and bison parser generator:

yum install flex bison

* To read pcap packet traces

yum install tcpdump

* Database support for statistics framework

yum install sqlite sqlite-devel

* Xml-based version of the config store (requires libxml2 >= version 2.7)

yum install libxml2 libxml2-devel

* Support for utils/check-style.py style check program

yum install uncrustify

* Support for MPI distributed simulations

yum install openmpi-devel

* Support for openflowswitch

yum install boost-devel

* Support for ns-3-pyviz visualizer

sudo apt-get install graphviz graphviz-devel python-setuptools-devel python-kiwi pygoocanvas
sudo easy_install pygraphviz

==== Gentoo ====

The following list of packages should be accurate for Gentoo as of 04/22/2010; due to possible changes in USE-flags or package names the list may slightly vary.
First of all, become root as usual.

* '''minimal requirements for C++ or Python (release):''' This is the minimal set of packages needed to run ns-3 or to work with Python bindings from a released tarball.

USE="threads -nocxx nptl" emerge -uavN gcc python

* Mercurial is needed to work with ns-3 development repositories.

emerge -av --noreplace mercurial

* Running python bindings from the ns-3 development tree (ns-3-dev) requires bazaar

USE="curl" emerge -uavN bzr

* A GTK-based configuration system

emerge -av --noreplace gtk+:2

* Debugging:

emerge -av --noreplace gdb valgrind

* Doxygen and related inline documentation; also ns-3 manual and tutorial (written in Texinfo):

USE="extra graphics png" emerge -uavN texlive
USE="cairo graphviz latex png svg" emerge -uavN doxygen imagemagick dia

* The Network Simulation Cradle (nsc) requires the flex lexical analyzer and bison parser generator:

emerge -av --noreplace flex bison

* Some basic mobility visualization tests require goocanvas:

emerge -av --noreplace goocanvas

* To install gcc-3.4 for some Network Simulation Cradle (nsc) stacks:

USE="-nocxx nptl" emerge -uavN gcc:3.4

* To read pcap packet traces

emerge -av --noreplace tcpdump

or you may prefer

emerge -av --noreplace wireshark

* Database support for statistics framework

USE="threadsafe" emerge -uavN sqlite:3

* Xml-based version of the config store (requires libxml2 >= version 2.7)

emerge -av --noreplace libxml2

* Support for Gustavo's ns-3-pyviz visualizer (following packages have no stable version as of day of writing, so ~arch for ACCEPT_KEYWORDS)

ACCEPT_KEYWORDS="~x86" emerge -av --noreplace pygraphviz kiwi pygoocanvas

* Support for utils/check-style.py style check program

ACCEPT_KEYWORDS="~x86" emerge -av --noreplace uncrustify

* To summarize all of above up (without not yet stable pygraphviz, kiwi, pygoocanvas, uncrustify):
USE="cairo curl extra graphics graphviz latex -nocxx nptl png svg\
threads threadsafe" emerge -uavN bison bzr dia doxygen flex gcc\
gcc:3.4 goocanvas gtk+:2 imagemagick libxml2 mercurial python\
sqlite:3 tcpdump texlive valgrind wireshark

=== FreeBSD ===

Many versions of FreeBSD provide gcc compiler. The latest version of gcc maintained for FreeBSD is 4.2.1. ns-3 (as of ns-3.17 release) builds on gcc-4.2.1 for FreeBSD.

FreeBSD is transitioning to the clang/LLVM compiler. ns-3 is gradually adding support for clang.

To use clang, one must set the 'CC=clang' and 'CXX=clang++' environment variables at compile time, such as:

CC=clang CXX=clang++ ./waf configure

or set these in your environment variables.

Support for clang-3.2 and greater is awaiting a patch planned in the August 2013 timeframe. clang-3.1 also has some problems with ns-3.17. This code review issue contains a patch that may enable you to build with clang: https://codereview.appspot.com/10975043

=== Mac OS X (Snow Leopard) ===

Please see [[HOWTO_get_ns-3_running_on_Mac_OS_X_(10.6.2_Intel)]] and follow steps 1 and 2 (prerequisites) and continue reading below if you want to work with a released version, and follow all steps if you want to work with a development version of ns-3.

== Installation ==

=== Installation with Bake ===

Bake is a new tool for installing, building and finding out the missing requirements for ns-3 in your own environment.

To use Bake you need to have at least Python (preferably 2.6 and above) and mercurial in your machine (see the section Prerequisites above to see how to install these).

First you need to download Bake using Mercurial, go to where you want Bake to be installed and call

hg clone http://code.nsnam.org/bake

It is advisable to add bake to your patch.

export BAKE_HOME=`pwd`/bake
export PATH=$PATH:$BAKE_HOME
export PYTHONPATH=$PYTHONPATH:$BAKE_HOME

After that you can use Bake to find the missing packages, download build and install ns-3 and its modules.

To find out what is missing in your system and may be needed for installing ns-3 you can call bake check:

bake.py check

You should have seen something like:

> Python - OK > GNU C++ compiler - OK > Mercurial - OK > CVS - OK > GIT - OK > Bazaar - OK > Tar tool - OK > Unzip tool - OK > Unrar tool - OK > 7z data compression utility - OK > XZ data compression utility - OK > Make - OK > cMake - OK > patch tool - OK > autoreconf tool - OK > Path searched for tools: /usr/lib64/qt-3.3/bin /usr/lib64/ccache /usr/local/bin /usr/bin/bin/usr/local/sbin /usr/sbin /sbin /user/dcamara/home/scripts/user/dcamara/home/INRIA/Programs/bin /user/dcamara/home/INRIA/repos/llvm/build/Debug+Asserts/bin 

Before downloading and building ns-3 you need to configure bake to inform it which are the modules you want added to ns-3, the standard distribution for example.

bake.py configure -e ns-3.17

Then to see the modules it has added, and the specific system requirements for this configuration, you can call bake show:

bake.py show

To download the modules, build and install you can call bake deploy

bake.py deploy

This will download the selected modules, all their dependencies and build ns-3 with all these independent modules. You can also perform this installation step by step, i.e. by calling download and build in different steps.

bake.py download
bake.py build

=== Manual installation ===
The ns-3 code is available in Mercurial repositories on the server http://code.nsnam.org (look for the latest release e.g., "ns-3.4"). You can download a tarball of the latest release at http://www.nsnam.org/releases or you can work with our repositories using Mercurial. We recommend using Mercurial unless there's a good reason not to (See the end of this section for instructions on how to get a tarball release).

The simplest way to get started using Mercurial repositories is to use the '''ns-3-allinone''' environment. This is a set of scripts that manages the downloading and building of various subystems of ns-3 for you. We recommend that you begin your ns-3 adventures in this environment as it can really simplify your life at this point.

==== Downloading ns-3 Using Mercurial ====

One practice is to create a directory called '''repos''' in one's home directory under which one can keep local Mercurial repositories. If you adopt that approach, you can get a copy of ns-3-allinone by typing the following into your Linux shell (assuming you have installed Mercurial):

cd
mkdir repos
cd repos
hg clone http://code.nsnam.org/ns-3-allinone

As the hg (Mercurial) command executes, you should see something like the following displayed,

destination directory: ns-3-allinone
requesting all changes
adding changesets
adding manifests
adding file changes
added 26 changesets with 40 changes to 7 files
7 files updated, 0 files merged, 0 files removed, 0 files unresolved

After the clone command completes, you should have a directory called ns-3-allinone under your ~/repos directory, the contents of which should look something like the following:

build.py* constants.py dist.py* download.py* README util.py

Notice that you really just downloaded some Python scripts. The next step will be to use those scripts to download and build the ns-3 distribution of your choice.

If you go to the following link: http://code.nsnam.org/ you will see a number of repositories. Many are the private repositories of the ns-3 development team. The repositories of interest to you will be prefixed with '''ns-3'''. Official releases of ns-3 will be numbered as ns-3.release.hotfix. For example, a second hotfix to a still hypothetical release nine of ns-3 would be numbered as ns-3.9.2 on this page.

The current development snapshot (unreleased) of ns-3 may be found at http://code.nsnam.org/ns-3-dev/. The developers attempt to keep these repository in consistent, working states but they are in a development area with unreleased code present, so you may want to consider staying with an official release if you do not need newly-introduced features.

Since the release numbers are going to be changing, we will stick with the more constant ns-3-dev here, but you can replace the string ''ns-3-dev'' with your choice of release (e.g., ns-3.4) in the text below. You can find the latest version of the code either by inspection of the repository list or by going to the ''Getting Started'' web page and looking for the latest release identifier.

To download the most common options type the following into your shell (remember you can substitute the name of your chosen release number instead of ns-3-dev)

./download.py -n ns-3-dev

After download process completes, you should have several new directories under ~/repos/ns-3-allinone:

build.py* constants.pyc download.py* nsc/ README util.pyc
constants.py dist.py* ns-3-dev/ pybindgen/ util.py

Go ahead and change into ns-3-dev under your ~/repos/ns-3-allinone directory. You should see something like the following there:

AUTHORS examples/ RELEASE_NOTES utils/ wscript
bindings/ LICENSE samples/ VERSION wutils.py
CHANGES.html ns3/ scratch/ waf*
doc/ README src/ waf.bat*

You are now ready to build the ns-3 distribution.

==== Downloading ns-3 Using a Tarball ====

The process for downloading ns-3 via tarball is simpler than the Mercurial process since all of the pieces are pre-packaged for you. You just have to pick a release, download it and decompress it.

As mentioned above, one practice is to create a directory called '''repos''' in one's home directory under which one can keep local Mercurial repositories. One could also keep a tarballs directory. If you adopt the tarballs directory approach, you can get a copy of a release by typing the following into your Linux shell (substitute the appropriate version numbers, of course):

cd
mkdir tarballs
cd tarballs
wget http://www.nsnam.org/release/ns-allinone-3.13.tar.bz2
tar xjf ns-allinone-3.13.tar.bz2

If you change into the directory '''ns-allinone-3.13''' you should see a number of files:

build.py* ns-3.13/ pybindgen-0.15.0.795/ util.py
constants.py nsc-0.5.2/ README

You are now ready to build the ns-3 distribution.

== Building ns-3 with build.py ==

The first time you build the ns-3 project you should build using the allinone environment. This will get the project configured for you
in the most commonly useful way.

Change into the directory you created in the download section above. If you downloaded using Mercurial you should have a directory called ns-3-allinone under your ~/repos directory. If you downloaded using a tarball you should have a directory called something like ns-allinone-3.13 under your ~/tarballs directory. Type the following:

./build.py

You will see lots of typical compiler output messages displayed as the build script builds the various pieces you downloaded. Eventually you should see the following magic words:

Build finished successfully (00:02:37)
Leaving directory `./ns-3-dev'

Once the project has built you typically will not use ns-3-allinone scripts. You will now interact directly with Waf and we '''do it in the ns-3-dev directory and not in the ns-3-allinone directory'''.

=== Configuration with Waf ===

To see valid configure options, type ./waf --help. The most important option is -d <debug level>. Valid debug levels (which are listed in waf --help) are: "debug" or "optimized". It is also possible to change the flags used for compilation with (e.g.):

CXXFLAGS="-O3" ./waf configure

or, alternately, the gcc compiler

CXX=g++-3.4 ./waf configure

'''Note:''' Unlike some other build tools, to change the build target, the option must be supplied during the configure stage rather than the build stage (i.e., "./waf -d optimized" will not work; instead, do

./waf -d optimized configure; ./waf

The resulting binaries are placed in build/<debuglevel>/srcpath. For example, in a debug build you can find the executable for the first.cc example as build/examples/first. You can debug the executable directly by:

./waf --shell
cd build/debug/examples
gdb ns-<version>-first-debug

Of course, you can run gdb in emacs, or use your favorite debugger such as ddd or insight just as easily. In an optimized build you can find the executable for the first.cc example as build/examples/ns-<version>-first-optimized.

In order to forcibly disable python bindings, you can provide the following option:

./waf --disable-python configure

In order to tell the build system to use the sudo program to set the suid bit if required, you can provide the following option:

./waf --enable-sudo configure

To start over a configuration from scratch, type:

./waf distclean

Or if you get stuck and all else fails:

rm -rf build

followed by changing back into ns-3-allinone and doing:

./build.py

will basically reset your build state.

To see all waf options:

./waf --help

== Validating ==

ns-3 has unit tests that can be run to verify the installation:

./test.py

which should produce output like:
<pre>
PASS: TestSuite histogram
PASS: TestSuite ns3-wifi-interference
PASS: TestSuite ns3-tcp-cwnd
PASS: TestSuite ns3-tcp-interoperability
PASS: TestSuite sample
...
</pre>

== Using Python ==

See [[NS-3 Python Bindings|this page]].

== Troubleshooting ==

See [[Troubleshooting|this page]].

== Obsolete information ==
Older versions of ns-3, prior to 3.15, supported using cygwin to run on Windows platform.

=== Windows ===

There are three basic options for Windows support:

# We provide HOWTO documents describing the process for installing Linux support and getting ns-3 running using two popular virtualization products: VirtualBox ([[HOWTO use VirtualBox to run simulations on Windows machines]]) and VMware ([[HOWTO use VMware to set up virtual networks (Windows)]]).
# There is an experimental project, [[Ns3 on windows|Ns3 on Windows]], using Visual Studio 2010.
# [http://www.cygwin.com Cygwin] has been supported in the past: gcc 3.4.4 (debug only), gcc 4.3.2 (debug and optimized). Note, however, that there are limitations with regard to [[NS-3_Python_Bindings#Cygwin_limitation|Python bindings]], and that Real-time simulator, Emulated Net Device, Tap Bridge and Network simulation cradle are not supported.

An alternative Windows platform is MinGW. There are maintainers who attempt to keep a subset of ns-3 running on MinGW, but it is not "officially" suppported. This means that bugs filed against MinGW will be addressed as time permits.

Cygwin can sometimes be problematic due to the way it actually does its emulation, and sometimes interactions with other Windows software can cause problems. If you do use Cygwin or MinGW; and use Logitech products, we will save you quite a bit of heartburn right off the bat and encourage you to take a look at the [http://oldwiki.mingw.org/index.php/FAQ MinGW FAQ].

Search for "Logitech" and read the FAQ entry, "why does make often crash creating a sh.exe.stackdump file when I try to compile my source code." Believe it or not, the ``Logitech Process Monitor`` insinuates itself into every DLL in the system when it is running. It can cause your Cygwin or MinGW DLLs to die in mysterious ways and often prevents debuggers from running. Beware of Logitech software when using Cygwin.

GSOC2013WAVE MAC

2013-07-28T21:45:30Z

Vedranm: Fix midterm report wiki link

= Project =
* Project Name: Implementation of WAVE 1609.4/802.11p
* Student: [mailto:linlinjavaer@gmail.com Junling Bu]
* Mentor: [mailto:guillaume.remy@ieee.org Guillaume Remy], [mailto:tomh@tomh.org Tom Henderson], [mailto:nikkipui@gmail.com Daniel Lertpratchya]
* Abstract: Since WAVE communication standards have been published, there exist many relevant implementations including prototypes, products, and simulations. However the implementation varies significantly, some of them even based on old draft standards. Besides that, ns-3 has no complete WAVE module yet. So this project will implement WAVE 1609.4/802.11p in mac layer for ns-3, with complete testsuits, examples, helpers and documents.
* Code: Because of access restrictions from China, the code repository of this project cannot host on ns-3 code server with ssh command connected to. For now, an easy solution is to host the code on github website (mainly under src/wave directory).[https://github.com/linlinjava/ns-3-dev-git Code repository].
* Midterm report: [[GSOC2013WAVE MAC/MidTermReport]]
* About me: I am a second year Master student from China, and now is researching on vehicular network communication.

= Introduction =
== Vehicluar Networks and VANET simulations ==
Vehicular networks called VANETs are an important area of research in the field of Intelligent Transportation Systems (ITS). A wide range of safety and infotainment systems have been envisioned using this technology. Cooperative active safety systems, urban traffic control and the study of the inherent communication protocols are currently drawing great research interest [8-9]. The protocol stacks dedicated for VANET include WAVE from US IEEE, C2C-CC from Europe and CALM from ISO. Note that: this project is mainly focus on MAC layer of WAVE architecure described in section 2.2 and 2.3.
 
VANET simulations are the most practicable methodology to study vehicular networks. First, it is the only viable solution to evaluate applications in large-scale scenarios with thousands of vehicles. Second, it allows for the control of parameters that are usually unavailable in real experiments such as traffic lights algorithms. Third, it provides a cost-effective solution for trying new applications or simulating accidents [8]. The challenge of VANET simulations mainly includes network simulation, vehicular mobility, channel model and large-scale simulation [11].

== IEEE Std 802.11p-2010 [1] ==
802.11p is an amendment of the IEEE standard 802.11, specifying extensions to 802.11a, adapting it to VANET communications in the 5.9 GHz band, fitting the VANET requirements of high mobility and short-duration communications. This specification includes: functions and services required by stations to operate correctly and to exchange messages without joining a BSS; signaling techniques and interface functions used by stations to communicate outside the context of a BSS.
== IEEE Std 1609.4-2010 [4] ==
1609.4 means multi-channel operations, providing enhancements to IEEE 802.11 MAC to support WAVE operations, namely number and type of channels, channel routing and coordination, QoS mechanisms and node synchronization. 75MHz channel spacing is divided into one CCH (control channel) and six SCHs (service channels). Based on GPS time information or 802.11p Timing Advertisement frame, wireless devices synchronously switch between CCHI (control channel interval) and SCHI (service channel interval)。

= Approach =
[[File:Architecture_of_the_implementation_of_1609.4_and_802.11p.jpg|

300px|thumb|right|Architecture of the implementation of 1609.4/802.11p in ns-3]]
== Implement 802.11p mac in ns-3 ==
The OCB mac mode named OcbWifiMac will be defined(Outside the context of a BSS), which is like ad-hoc rather than AP and station. According to the discussion among ns-3 developers [2-3],OcbWifiMac will inherit from RegularWifiMac class, which is very similar to AdhocWifiMac. The OcbWifiMac will overwrite some unsuitable functions to only log warn message, overwrite some functions to operate in OCB mode, and also provider some specific functions defined only in 802.11p. Moreover, OcbWifiMac will also set some arguments like default EDCA value.
== Implement 1609.4 mac extension in ns-3 ==
Since 1609.4 has already been implemented in some other simulations[5-6], this project will adopt some ideas from these papers as well as take the discussion among ns-3 developers[2-3] as the guideline for implementing. A subclass inheriting from NetDevice named WaveNetDevice will be defined, composed of (a) OcbWifiMac mac defined in 802.11p, (b) WaveNetDevice mac extension dealing with functions of 1609.4 management and data plane,(c) subcomponents in 1609.4 including ChannelCoordinator, ChannelManager, SchChannelScheduler and VSARepeater.

== Development methodology ==
* First,based on ns-3 manual and model documents, abstract high basic classes, define common functions, and also add ns-3 features including Log and Attributes;
* Then, develop real working subclass inheriting from base class.
* After that, write test suits and examples, find bug, and check whether they work well;
* Last, complete manual documents about how to implement and how to use.

 
And the most important point is that it’s an iterative process like Extreme Programming. Because this is a light project, we can develop simple functions, work well, then go back to develop a little more complex and accurate.
== Testing approach ==
When programming codes, test codes meanwhile. And testing approach is mainly based on log functions, examples and test suits. According to the Test part of ns-3 manual, it includes:
a) Unit test, each layer's important functions and classes will be tested independently.
b) Integrated test, integrating multiple classes will be tested.
c) System test, examples will be used to test WAVE implementation.
== Deliverables ==
According to the ns-3 architecture, deliverables are in a new module named WAVE, including Model, Doc, Helper, Binding, Test, and Examples.
* Model mainly contains : a) implementations of 802.11p, including ocb-wifi-mac.h/.cc; b) implementations of 1609.4, including wave-net-device.h/.cc, vsa-repeater.h/.cc, sch-channel-scheduler.h/.cc, channel-manager.h/.cc, channel-coordinator.h/.cc,vendor-specific-frame.h/.cc.
* Doc contains design ideas, implementation details, and manual. Helper contains nice helpers to simplify operation, including wave-helper.h/.cc.
* Test contains some test suits, including ocb-wifi-mac-test-suit.cc, wave-net-device-test-suit.cc.
* Examples contain useful examples, including simple-wave-example.c, and simple-802.11p-example.c.

= Plan and Weekly Progress=

Based on the GSoC 2013 timeline, there are totally 12 weeks. The following is the plan of this project (Implementation not only means source codes, but also contains relevant test suits, examples and documents):
* Community bonding period [status: completed]
Before June 17: learn Python, ns-3 coding style, read relevant ns-3 codes,talk with mentors about implementation details.
* Week 1/2 [status: completed]
June 17 – June 30: implement OcbWifiMac.
a) remove deprecated 802.11p code from wifi module.
b) complete a management frame header named VendorSpecificActionHeader.
c) complete wifi-80211p-helper
d) declare and implement OcbWifiMac class.
e) finish two examples and one test suit.
* Week 3/4 [status: completed]
June 1 – July 14: implement WaveNetDevice
a) define initial ChannelCoordinator, ChannelManager and ChannelScheduler which are used in WaveNetDevice
b) define WifiNetDevice that has specific methods to deal with multiple channel operation.
c) refactor helpers and implement WaveHelper
d) finish a simple example to send WSMP packets.
* Week 5/6 [status: ]
July 15 – July 28: implement SchChannelScheduler
* mid-term report [status: ]
July 29 - August 2:submit source files including ocb-wifi-mac.h/.cc, wave-net-device.h/.cc, ocb-wifi-mac-test-suit.cc, simple-802.11p-example.cc. And submit a document about partial technical details and usage for VANET researchers and a relatively simple introduction of WAVE for other users
 
* Week 7 [status: ]
August 3 – August 11: implement ChannelCoordinator
* Week 8 [status: ]
August 12 – August 18: implement ChannelManager
* Week 9/10 [status: ]
August 19 – September1: implement VSARepeater
* Week 11 [status: ]
September 2 – September 8: complete documents, useful helpers
* Week 12 [status: ]
September 9 – September 15: complete some WAVE examples, system test.
* Final [status: ]
September 16 – September 23: scrub code, and improve documentation.

= Usage =
== How to use wifi80211p device ? ==
This model defines some wifi-like helpers: NqosWaveMacHelper, QosWaveMacHelper, Wifi80211pHelper and WaveHelper. NqosWaveMacHelper and QosWaveMacHelper deal with OcbWifiMac configuration that are similar to NqosWifiMacHelper and QosWifiMacHelper. Wifi80211pHelper is used to create a WifiNetDevice that combines one OcbWifiMac and one WifiPhy, which is a conceptual 802.11p wifi netdevice. WifiHelper is used to create WaveNetDevice that combines multiple OcbWifiMacs and one WifiPhy to deal with multiple channel operation, which is a conceptual WAVE device (although now still miss 1609.3 standards).

Usage:
#include "ns3/wave.h"
NodeContainer nodes;
NetDeviceContainer devices;
nodes.Create (2);
YansWifiPhyHelper wifiPhy = YansWifiPhyHelper::Default ();
YansWifiChannelHelper wifiChannel = YansWifiChannelHelper::Default ();
wifiPhy.SetChannel (wifiChannel.Create ());
NqosWaveMacHelper wifi80211pMac = NqosWaveMacHelper::Default();
Wifi80211pHelper wifi80211p = Wifi80211pHelper::Default ();
devices = wifi80211p.Install (wifiPhy, wifi80211pMac, nodes);
see wave/examples/wave-simple-ocb.cc

== How to use wave device ? ==
Users can use WaveHelper to create a WaveNetDevice. Then before send or receive packets, we should assign channel access by StartSch method, then we can call SendX to send WSMP packets or call StartVsa to send VSA frames, and before send IP-based packets, we also need call RegisterTxProfile to indicate which channel to send, then we can call Send method. Usage:

see wave/examples/wave-simple-device.cc

== How to use VSA frame to send management information ? ==
Normally the up layer can send packets in different protocols via 802.11 data frame, like ipv4 and ipv6. However, actually wifi know nothing about these differences, because this work has been done with LlcSnapHeader with protocol field. So if up layer wants to send different management informations over 802.11 management frame (of course nobody can prevent someone just wants to send management information over 802.11 data frame), how can we do?
The 802.11 and 802.11p can allow the up layer send different information over Vendor Specific Action management frame by using different OrganizationIdentifier fields (now only support 3 and 5 bytes according to the standard) to identify differences.

If you want to use 802.11p device to send VSAs.Usage:

0. refer to 5.1, already has some Nodes and WifiNetdevices
1. define an OrganizationIdentifier
uint8_t oi_bytes[5] = {0x00, 0x50, 0xC2, 0x4A, 0x40};
OrganizationIdentifier oi(oi_bytes,5);
2. define a Callback for the defined OrganizationIdentifier
VscCallback vsccall = MakeCallback (&VsaExample::GetWsaAndOi, this);
3. OcbWifiMac regists this identifier and function
Ptr<WifiNetDevice> device1 = DynamicCast<WifiNetDevice>(nodes.Get (i)->GetDevice (0));
Ptr<OcbWifiMac> ocb1 = DynamicCast<OcbWifiMac>(device->GetMac ());
ocb1->AddReceiveVscCallback (oi, vsccall);
4. now you can send management packet over VSA frame
Ptr<Packet> vsc = Create<Packet> ();
ocb2->SendVsc (vsc, Mac48Address::GetBroadcast (), m_16093oi);
5. then registered callback in other devices will be called.
see wave/examples/wave-simple-vsa.cc

If you want to use wave device to send VSAs under multi-channel environment.Usage:

= Issues =
== Is this model going to involve vehicular mobility of some sort ==
Vehicular network involves not only communication protocol, but also communication environment including vehicular mobility and propagation models. Because of specific features of the latters than normal MANET, the protocols need to change. The MAC layer model
in this project just adopts MAC changes to vehicular environment. However this model not involves any vehicular mobility with time limit.Users can use any mobility model in ns-3, but should know these models are not real vehicular mobility. More work is need.

== Is your model going to use different propagation models ==
Refer to the first issue, some more realistic propagation models for vehicualr environment are suggested and welcome. And some existed propagation models in ns-3 are also suitable. Normally users can use Friis,Two-Ray Ground and Nakagami model [7].

== What specifically is different about your mac other than wildcard BSSID ==
== are there any vehicular application models to drive the code ==
About vehicular application models, I only know SAE J2375 depend on WAVE architecture is application message set in US; CAM and DENM in Europe is between network and application layer but is very close to application model. The BSM in J2375 and CAM is alert messages that every vehicle node will sent periodicity about its status information to cooperate with others. Fow now, here is no plan to develop a vehicular application model. But to drive WAVE MAC layer code, a simple application model will be tried to develop.

== Any previous code you think you can leverage ==
This project will provide two netdevice. First is normal 802.11p netdevice which uses new implemented OcbWifiMac, this is very useful for those people who only want to simulate route protocols or up protocols for vehicular environment and do not need whole WAVE architecture. For any previous code, my suggestion is to use Wifi80211phelper with little modification or just set ad-hoc mode with 802.11a 10MHz (this is enough to simulate main characteristic of 802.11p). The second netdevice is 1609.4 netdevice which providers some methods to deal with multi-channel operation. This is part of whole WAVE architecture and provides service for up 1609.3 standards.

== Why here are two kinds of NetDevice ==
In wave module, actually here are two device, one is 802.11p device which is the object of WifiNetDevice class, another is wave device which is the object of WaveNetDevice class. An "802.11p Net Device" is one that just runs the 802.11p extensions (channel frequency = 802.11a 5.9GHz, channel width = 10MHz, single instance of OcbWifiMac, and specific EDCA parameters). A "WAVE Net Device" is one that implements also 1609.1-4 standards based on 802.11p, and now we are focusing only on 1609.4 modeling aspects (multi channel).
The reason to provide a 802.11p device is that considering the fact many researchers are interested in route protocol or other aspects on vehicular environment of single channel, so they need no multi-channel operation and WAVE architectures. Besides that, the European standard could use 802.11p device in an modified ITS-G5 implementation (maybe named ITSG5NetDevice).

= Acknowledgement =
Thanks for all comments from Guillaume Rémy, Lalith Suresh, Tommaso Pecorella, and Tom Henderson.

= References =

* [1] IEEE Std 802.11p. IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 6: Wireless Access in Vehicular Environments, 2010.
* [2] ns-3.Bug 945 - Revise how we provide support for vehicular communications. [Online]. Available: https://www.nsnam.org/bugzilla/show_bug.cgi?id=978.
* [3] ns-3.Bug 978 - Consolidate Wi-Fi MAC high functionality. [Online].Available: http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16.
* [4] IEEE Std 1609.4-2010. IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-Channel Operation, 2010.
* [5] Chen Qi, Daniel Jiang, and Luca Delgrossi. "IEEE 1609.4 DSRC multi-channel operations and its implications on vehicle safety communications."Vehicular Networking Conference (VNC), 2009 IEEE. IEEE, 2009.
* [6] Ghandour, Ali J., et al. "Modeling and simulation of WAVE1609.4-based multi-channel vehicular ad hoc networks." Proceedings of the 5th International ICST Conference on Simulation Tools and Techniques. ICST (Institute for Computer Sciences, Social-Informatics and Telecommunications Engineering), 2012.
* [7] Benin, Joseph, Michael Nowatkowski, and Henry Owen. "Vehicular Network simulation propagation loss model parameter standardization in ns-3 and beyond." Southeastcon, 2012 Proceedings of IEEE. IEEE, 2012.
* [8] Fernandes, Ricardo, Fausto Vieira, and Michel Ferreira. "VNS: An integrated framework for vehicular networks simulation." Vehicular Networking Conference (VNC), 2012 IEEE. IEEE, 2012.
* [9] Karagiannis, Georgios, et al. "Vehicular networking: A survey and tutorial on requirements, architectures, challenges, standards and solutions."Communications Surveys & Tutorials, IEEE 13.4 (2011): 584-616.
* [10] Stanica, Razvan, Emmanuel Chaput, and André-Luc Beylot. "Simulation of vehicular ad-hoc networks: Challenges, review of tools and recommendations." Computer Networks 55.14 (2011): 3179-3188

GSoC2013WAVE MAC

2013-07-28T20:58:27Z

Vedranm: Add redirect

#REDIRECT [[GSOC2013WAVE MAC]]

Optical network models

2013-06-21T14:43:12Z

Vedranm: Add a reference

ns-3 network simulator presently doesn't include any support for simulation of WDM optical networks in the official distribution. There are three optical network simulation modules under active development as of January 2013, that have the goal to make ns-3 into optical network simulator. Note, however, that the term "optical network simulator" is rather broad, as there are many types and features of optical networks one might want to model and use in simulation. This page tracks info about these optics modules, intented for simulating
* Optical Transport Network (OTN),
* Passive Optical Network (PON), and
* Radio over Fiber (RoF).

This page will be updated with new info as time permits.

== Optical Transport Network: Prototype WDM Network Simulator (PWNS) ==
[[File:PwnsLogo.png|thumb|PWNS project logo]]

=== Project name ===
Project name is a parody on OWns (Optical WDM network simulator, described in [1]), a project with similar goals implemented in ns-2.

=== Project scope ===
The goal of PWNS project is to implement models for WDM optical network components, including:
* optical cable, optical fiber, wavelength channel,
* multiplexer and demultiplexer, add-drop multiplexor,
* wavelength converter, wavelength selective switch, arrayed waveguide grating,
* optical cross connect (MEMS plane).

Prototype version dated June 2012 is described in [2]; more detailed description will be posted here as soon as possible.

=== Code ===
* '''Current version:''' https://bitbucket.org/rivanvx/ns-3-dev-optics (private for the time being, access granted on request, contact [[User:Vedranm|Vedran Miletić]]; '''will be made public in July-August 2013 timeframe''')
* older versions, possibly broken: http://code.nsnam.org/vedranm/ns-3-dev-optics and http://code.nsnam.org/vedranm/ns-3-dev-optics-old

=== References ===
# Wen, B. and Bhide, N.M. and Shenai, R.K. and Sivalingam, K.M., ''Optical wavelength division multiplexing (WDM) network simulator (OWns): architecture and performance studies''
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Modelling optical network components: a network-simulator based approach'' // Proceedings on the IX. International symposium on Telecommunications - BIHTEL 2012.
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Impact Evaluation of Physical Length of Shared Risk Link Groups on Optical Network Availability Using Monte Carlo Simulation'' // Proceedings of the 18th European Conference on Networks and Optical Communications, NOC 2013 / Leitgeb, Erich (ur.).

== Passive Optical Network ==
=== Project Summary ===

The aim of this project is to develop PON (passive optical network) models for NS-3. It is under the umbrella of [http://www.ctvr.ie/ CTVR] that supports various research topics related with telecommunication.

=== Project Scope ===

The project will implement models for passive optical networks. The current focus is to develop one model for simulating XG-PON, which is also known as [http://en.wikipedia.org/wiki/10G-PON 10G-PON]. We will also investigate how to use this model and WiMAX/LTE models distributed with NS-3 to simulate the coming FTTC (Fiber To The Cell) network scenario. In the future, models for other PON technologies, such as [http://en.wikipedia.org/wiki/10G-EPON 10G-EPON] and [http://en.wikipedia.org/wiki/Passive_optical_network#Long-Reach_Optical_Access_Networks Long Reach PON], will also be developed to carry out comparative studies.

The current prototype is described in [1] and more detailed description will be posted here as soon as possible.

=== Code ===

The code will be made public in September-December, 2013 timeframe through the websites of CTVR and [http://www.ucc.ie/en/misl/ MISL].

=== References ===

# X. Wu, K.N. Brown, C.J. Sreenan, P. Alvarez, M. Ruffini, N. Marchetti, D. Payne, and L. Doyle, ''An XG-PON Module for the NS-3 Network Simulator'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

== Radio over Fiber ==
=== Project scope ===
The goal of our work is to investigate and optimize the performance of MAC (Medium Access Control) radio protocols when it is used in a RoF (Radio-over-Fiber) architecture. Our study is mainly focused on IEEE 802.11 over RoF transmissions. We developed a RoF model in ns-3 based on the YANS Wi-Fi model which enables the simulation of 802.11 RoF systems. The current model includes [1]:

* Distributed Antenna Systems RoF modeling;
* Optical module computing delays and attenuations undergone by the radio signal transmission over fiber links.

Further points to be implemented:

* Protocol-independent model (not limited to Wi-Fi transmissions);
* Integration of optical network component models developed by PWNS (Prototype WDM Network Simulator).

=== Code ===
The source code is not yet available for the public.

=== References ===
# Sebastien Deronne, Veronique Moeyaert and Sebastien Bette, ''Simulation of 802.11 Radio-over-Fiber Networks using ns-3'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

[[Category:Models]]

Optical network models

2013-05-26T09:10:46Z

Vedranm: /* Code */

ns-3 network simulator presently doesn't include any support for simulation of WDM optical networks in the official distribution. There are three optical network simulation modules under active development as of January 2013, that have the goal to make ns-3 into optical network simulator. Note, however, that the term "optical network simulator" is rather broad, as there are many types and features of optical networks one might want to model and use in simulation. This page tracks info about these optics modules, intented for simulating
* Optical Transport Network (OTN),
* Passive Optical Network (PON), and
* Radio over Fiber (RoF).

This page will be updated with new info as time permits.

== Optical Transport Network: Prototype WDM Network Simulator (PWNS) ==
[[File:PwnsLogo.png|thumb|PWNS project logo]]

=== Project name ===
Project name is a parody on OWns (Optical WDM network simulator, described in [1]), a project with similar goals implemented in ns-2.

=== Project scope ===
The goal of PWNS project is to implement models for WDM optical network components, including:
* optical cable, optical fiber, wavelength channel,
* multiplexer and demultiplexer, add-drop multiplexor,
* wavelength converter, wavelength selective switch, arrayed waveguide grating,
* optical cross connect (MEMS plane).

Prototype version dated June 2012 is described in [2]; more detailed description will be posted here as soon as possible.

=== Code ===
* '''Current version:''' https://bitbucket.org/rivanvx/ns-3-dev-optics (private for the time being, access granted on request, contact [[User:Vedranm|Vedran Miletić]]; '''will be made public in July-August 2013 timeframe''')
* older versions, possibly broken: http://code.nsnam.org/vedranm/ns-3-dev-optics and http://code.nsnam.org/vedranm/ns-3-dev-optics-old

=== References ===
# Wen, B. and Bhide, N.M. and Shenai, R.K. and Sivalingam, K.M., ''Optical wavelength division multiplexing (WDM) network simulator (OWns): architecture and performance studies''
# Miletić, Vedran; Mikac, Branko; Džanko, Matija. ''Modelling optical network components: a network-simulator based approach'' // Proceedings on the IX. International symposium on Telecommunications - BIHTEL 2012.

== Passive Optical Network ==
=== Project Summary ===

The aim of this project is to develop PON (passive optical network) models for NS-3. It is under the umbrella of [http://www.ctvr.ie/ CTVR] that supports various research topics related with telecommunication.

=== Project Scope ===

The project will implement models for passive optical networks. The current focus is to develop one model for simulating XG-PON, which is also known as [http://en.wikipedia.org/wiki/10G-PON 10G-PON]. We will also investigate how to use this model and WiMAX/LTE models distributed with NS-3 to simulate the coming FTTC (Fiber To The Cell) network scenario. In the future, models for other PON technologies, such as [http://en.wikipedia.org/wiki/10G-EPON 10G-EPON] and [http://en.wikipedia.org/wiki/Passive_optical_network#Long-Reach_Optical_Access_Networks Long Reach PON], will also be developed to carry out comparative studies.

The current prototype is described in [1] and more detailed description will be posted here as soon as possible.

=== Code ===

The code will be made public in September-December, 2013 timeframe through the websites of CTVR and [http://www.ucc.ie/en/misl/ MISL].

=== References ===

# X. Wu, K.N. Brown, C.J. Sreenan, P. Alvarez, M. Ruffini, N. Marchetti, D. Payne, and L. Doyle, ''An XG-PON Module for the NS-3 Network Simulator'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

== Radio over Fiber ==
=== Project scope ===
The goal of our work is to investigate and optimize the performance of MAC (Medium Access Control) radio protocols when it is used in a RoF (Radio-over-Fiber) architecture. Our study is mainly focused on IEEE 802.11 over RoF transmissions. We developed a RoF model in ns-3 based on the YANS Wi-Fi model which enables the simulation of 802.11 RoF systems. The current model includes [1]:

* Distributed Antenna Systems RoF modeling;
* Optical module computing delays and attenuations undergone by the radio signal transmission over fiber links.

Further points to be implemented:

* Protocol-independent model (not limited to Wi-Fi transmissions);
* Integration of optical network component models developed by PWNS (Prototype WDM Network Simulator).

=== Code ===
The source code is not yet available for the public.

=== References ===
# Sebastien Deronne, Veronique Moeyaert and Sebastien Bette, ''Simulation of 802.11 Radio-over-Fiber Networks using ns-3'', to be published in Proceedings of Workshop on ns-3 (WNS3), in conjunction with ICST SIMUTOOLS, 5 march 2013, Cannes (France)

[[Category:Models]]

File:PwnsLogo.png

2013-05-05T07:49:41Z

Vedranm: Vedranm uploaded a new version of "File:PwnsLogo.png"

PWNS project logo

Ns-3.17

2013-05-03T14:38:22Z

Vedranm: TwoBound callback

{{TOC}}

This page summarizes the ongoing release planning for ns-3.17. The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].

The release managers are [mailto:tomh@tomh.org Tom Henderson] and [mailto:bswenson3@gatech.edu Brian Swenson]. [mailto:tazaki@nict.go.jp Hajime Tazaki] will manage release issues for Direct Code Execution.

= Release schedule =

* <s>April 5 -- new feature freeze, ns-3.17 release candidate 1 posted</s>
** 21 April: release candidate 1 posted at http://www.nsnam.org/release/ns-allinone-3.17.rc1.tar.bz2
* <s>April 19</s> April 26 -- code freeze, final RC candidate <-- slipping until blocker bugs are resolved
* <s>April 24</s> April 30 -- ns-3.17 released if no blocking issues remain on April 26 RC <--slipping until blocker bugs are resolved
List of current blockers is [https://www.nsnam.org/wiki/index.php/Ns-3.17#Bugs_being_worked listed below]; more up to date list may be on the Bugzilla tracker itself.

= Proposed supported platforms =

Our primary platforms for this release are planned to be:
* Ubuntu 12.10 and 13.04 (32/64 bit systems)
* Ubuntu 12.04 LTS and 10.04 LTS (64 bit)
* Fedora 17 and 18 (32/64 bit systems)
* Mac OS 10.8 (64 bit)
* FreeBSD 8.2, 9.1 (64 bit)

The following also are planned to be lightly tested:
* Cygwin 1.7.6.1 (for Windows 7)
* Mac OS X 10.7 (64 bit)
* Linux on PowerPC hardware
* Debian 6.0 and 7.0 (64-bit)
* Linux Mint
* CentOS

= Packaging =

ns-3.17 will be packaged as a source tarball as before: ns-allinone-3.17.tar.bz2.

The main difference is that the [[BakeIntegration | bake build system]] is planned to be added, to support inclusion of [[Dce_release_schedule | Direct Code Execution]] project.

= new feature reviews =

The following code is likely to be merged provided that final integration issues (documentation, testing, examples) are resolved:

* bake: http://codereview.appspot.com/6761057/
** The [[BakeIntegration]] page has more details
** '''Status:''' Included, being tested as part of the release process.
* <s>Waf 1.7 upgrade: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1562</s> <--- Already merged
* <s>Burst error model: https://codereview.appspot.com/7183044/</s> <--- Already merged
* <s>TCP Westwood/Westwood+: https://codereview.appspot.com/7227059/</s> <--- Already merged
* <s>FDNetDevice: http://codereview.appspot.com/6458154/</s> <--- Already merged
* <s>LENA ns-3-dev merge (http://code.nsnam.org/nbaldo/ns-3-lena-dev-merge-ns-3-dev/)</s> <--- Already merged
* <s>Rename Object::Start/DoStart to Initialize/DoInitialize: http://codereview.appspot.com/8243044</s> <--- Already merged

----------------------

The following code is not currently on the merge path for ns-3.17:

* Node/NetDevice Start/Stop: http://codereview.appspot.com/6530051/
** Reworks were discussed at March developer meeting
* GSOC code review for HLA interfaces: http://codereview.appspot.com/6458160/
* GSOC code review for NAT and Netfilter: http://codereview.appspot.com/6454146/
* Low resolution radio model: [http://codereview.appspot.com/5466046 code review]
* Wideband propagation model (only exponential PDP is implemented); [https://codereview.appspot.com/5862047]
* Brian Panneton's antenna model updates http://mailman.isi.edu/pipermail/ns-developers/2012-April/010322.html
* [http://codereview.appspot.com/6201059/ New IEEE 802.11b indoor wireless channel models for (HMM and BEAR)]
* [http://codereview.appspot.com/6192052/ Longley-Rice and ITU terrain-aware propagation models]
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=454 TCP Echo] Code review [http://codereview.appspot.com/5654053/ here], needs updating
* [http://codereview.appspot.com/5552055/ Finishing ns-3-click-mac extensions] -> Blocked by queue API resolution
* [http://codereview.appspot.com/4685048/ Monitor mode support] ([http://codereview.appspot.com/5552055/ Update from Bjorn])
* [http://groups.google.com/group/ns-3-reviews/browse_thread/thread/512bf466d3cd5ec0?pli=1 UAN Mobility Model merge (from previous GSOC)]
** blocked on resolving changes to WaypointMobilityModel API
* BitTorrent: http://mailman.isi.edu/pipermail/ns-developers/2012-December/010783.html
** Sliding to ns-3.18 due to availability of contributors to work the comments
* Switched Ethernet device: http://codereview.appspot.com/5615049/
* HTTP traffic generator: http://codereview.appspot.com/4940041/
* GPSR: http://codereview.appspot.com/5401042
* TMix and Delaybox: http://code.google.com/p/tmix-ns3/
* SNR tag patches: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1566
* SMCEN/RNS: https://codereview.appspot.com/7304093/
* LR-WPAN: https://codereview.appspot.com/8339045/
* TwoBound callback: https://codereview.appspot.com/7103063

= Bugs being worked =

We will use bugzilla to track [http://www.nsnam.org/wiki/index.php/User_FAQ#Bug_Priorities bug priorities] (esp. P1 blocker bugs) for the release.

Current blockers:
* bug 1658 (documentation for bake)
* bug 1657 (bake)
* bug 1651 (DSR documentation of changes)
* bug 1650 (LTE documentation of changes)
* bug 1649 (bindings for fd-net-device)
* bug 1639 (bake)
* bug 1637 (bake)
* bug 1636 (bake)
* bug 1622 (apiscan)

Also, need to fix bug 1644 although we could probably release with it by changing the example:
* bug 1644 (flow monitor valgrind)

Also, bindings scanning depends on this, which may be resolved already by latest git repository version of gccxml (need to confirm):
* bug 1530 (apiscan)

== Bugs in ns-3 models ==

[https://www.nsnam.org/bugzilla/buglist.cgi?bug_status=__open__&content=&product=&query_format=specific&order=bug_id%20DESC&query_based_on= Open bugs] will be worked on a best-effort basis.

Ns-3.17

2013-04-27T18:11:28Z

Vedranm: Remove some useless CSS

{{TOC}}

This page summarizes the ongoing release planning for ns-3.17. The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].

The release managers are [mailto:tomh@tomh.org Tom Henderson] and [mailto:bswenson3@gatech.edu Brian Swenson]. [mailto:tazaki@nict.go.jp Hajime Tazaki] will manage release issues for Direct Code Execution.

= Release schedule =

* <s>April 5 -- new feature freeze, ns-3.17 release candidate 1 posted</s>
** 21 April: release candidate 1 posted at http://www.nsnam.org/release/ns-allinone-3.17.rc1.tar.bz2
* <s>April 19</s> April 26 -- code freeze, final RC candidate
* <s>April 24</s> April 30 -- ns-3.17 released if no blocking issues remain on April 26 RC

We will use bugzilla to track [http://www.nsnam.org/wiki/index.php/User_FAQ#Bug_Priorities bug priorities] (esp. P1 blocker bugs) for the next release.

= Proposed supported platforms =

Our primary platforms for this release are planned to be:
* Ubuntu 12.10 and 13.04 (32/64 bit systems)
* Ubuntu 12.04 LTS and 10.04 LTS (64 bit)
* Fedora 17 and 18 (32/64 bit systems)
* Mac OS 10.8 (64 bit)
* FreeBSD 8.2, 9.1 (64 bit)

The following also are planned to be lightly tested:
* Cygwin 1.7.6.1 (for Windows 7)
* Mac OS X 10.7 (64 bit)
* Linux on PowerPC hardware
* Debian 6.0 and 7.0 (64-bit)
* Linux Mint
* CentOS

= Packaging =

ns-3.17 will be packaged as a source tarball as before: ns-allinone-3.17.tar.bz2.

The main difference is that the [[BakeIntegration | bake build system]] is planned to be added, to support inclusion of [[Dce_release_schedule | Direct Code Execution]] project.

= new feature reviews =

The following code is likely to be merged provided that final integration issues (documentation, testing, examples) are resolved:

* bake: http://codereview.appspot.com/6761057/
** The [[BakeIntegration]] page has more details
** '''Status:''' Included, being tested as part of the release process.
* <s>Waf 1.7 upgrade: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1562</s> <--- Already merged
* <s>Burst error model: https://codereview.appspot.com/7183044/</s> <--- Already merged
* <s>TCP Westwood/Westwood+: https://codereview.appspot.com/7227059/</s> <--- Already merged
* <s>FDNetDevice: http://codereview.appspot.com/6458154/</s> <--- Already merged
* <s>LENA ns-3-dev merge (http://code.nsnam.org/nbaldo/ns-3-lena-dev-merge-ns-3-dev/)</s> <--- Already merged
* <s>Rename Object::Start/DoStart to Initialize/DoInitialize: http://codereview.appspot.com/8243044</s> <--- Already merged

----------------------

The following code is not currently on the merge path for ns-3.17:

* Node/NetDevice Start/Stop: http://codereview.appspot.com/6530051/
** Reworks were discussed at March developer meeting
* GSOC code review for HLA interfaces: http://codereview.appspot.com/6458160/
* GSOC code review for NAT and Netfilter: http://codereview.appspot.com/6454146/
* Low resolution radio model: [http://codereview.appspot.com/5466046 code review]
* Wideband propagation model (only exponential PDP is implemented); [https://codereview.appspot.com/5862047]
* Brian Panneton's antenna model updates http://mailman.isi.edu/pipermail/ns-developers/2012-April/010322.html
* [http://codereview.appspot.com/6201059/ New IEEE 802.11b indoor wireless channel models for (HMM and BEAR)]
* [http://codereview.appspot.com/6192052/ Longley-Rice and ITU terrain-aware propagation models]
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=454 TCP Echo] Code review [http://codereview.appspot.com/5654053/ here], needs updating
* [http://codereview.appspot.com/5552055/ Finishing ns-3-click-mac extensions] -> Blocked by queue API resolution
* [http://codereview.appspot.com/4685048/ Monitor mode support] ([http://codereview.appspot.com/5552055/ Update from Bjorn])
* [http://groups.google.com/group/ns-3-reviews/browse_thread/thread/512bf466d3cd5ec0?pli=1 UAN Mobility Model merge (from previous GSOC)]
** blocked on resolving changes to WaypointMobilityModel API
* BitTorrent: http://mailman.isi.edu/pipermail/ns-developers/2012-December/010783.html
** Sliding to ns-3.18 due to availability of contributors to work the comments
* Switched Ethernet device: http://codereview.appspot.com/5615049/
* HTTP traffic generator: http://codereview.appspot.com/4940041/
* GPSR: http://codereview.appspot.com/5401042
* TMix and Delaybox: http://code.google.com/p/tmix-ns3/
* SNR tag patches: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1566
* SMCEN/RNS: https://codereview.appspot.com/7304093/
* LR-WPAN: https://codereview.appspot.com/8339045/

= Bugs being worked =

We will use bugzilla to track [http://www.nsnam.org/wiki/index.php/User_FAQ#Bug_Priorities bug priorities] (esp. P1 blocker bugs) for the next release.

Aiming to fix before ns-3.17 release:
* bug 1651 (DSR documentation of changes)
* bug 1650 (LTE documentation of changes)
* bug 1649 (apiscan)
* bug 1644 (flow monitor valgrind)
* bug 1639 (bake)
* bug 1637 (bake)
* bug 1636 (bake)
* bug 1622 (apiscan)
* bug 1530 (apiscan)

== Bugs in ns-3 models ==

[https://www.nsnam.org/bugzilla/buglist.cgi?bug_status=__open__&content=&product=&query_format=specific&order=bug_id%20DESC&query_based_on= Open bugs] will be worked on a best-effort basis.

GSOC2013Projects

2013-03-28T10:51:09Z

Vedranm: Add myself as co-mentor on Tom's ideas

{{TOC}}

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net

= GSoC 2013 Ideas =

This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.

GSOC 2012 Timeline is:
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.
* March 29 - 19:00 UTC: Mentoring organization application deadline.
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.
* April 22 - 19:00 UTC: Student application period opens.
* May 3 - 19:00 UTC: Student application deadline.
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013

While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8.

== About the ns-3 project ==

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.

Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011). ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained. The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.

Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson]. The project has participated in past GSoCs during 2008-10 and 2012.

Mentors will be paired with students based on the projects that are selected. Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring. Prospective mentors should notify Lalith Suresh of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.

== Getting started ==

For students interested in applying to ns-3 for GSOC, go through the following list to get started:
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].
* Look through our ideas list below to see if you find a project that interests you.
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.

== Project Ideas ==

The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.

<blockquote>
Each project idea within a particular priority has been tagged with the following properties:
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
* ''Difficulty:'' easy, medium or difficult
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.
</blockquote>

= Guidelines for project ideas =

For mentors who're adding project ideas to the list below, please ensure that:

* The projects are sized such that there can be a code merge by the end of the coding period. The scope of the project should be such that it is very difficult to not have a code merge by the end of the summer.
* The proposed projects are not too open-ended. That is, if the deliverables or a clear path to the same are not well understood, it is better kept outside GSOC.

= Project Ideas =

=== Vehicular Ad-hoc Networks ===

Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]

* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)
# higher layers: nothing specific to WAVE is currently available.
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).
** ''Required experience:'' C++.
** ''Bonus experience:'' Wireless networking, WAVE.
** ''Interests:'' Wireless networking, VANETs.
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.
** ''Recommended reading''
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php

=== 802.15.4 Energy Model ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' ns-3 Energy model
** ''Interests:'' WSN, Battery discharge
** ''Difficulty:'' easy
** ''Recommended reading:''
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes]
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]

=== 802.15.4 Bootstrap ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Bootstrap:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. An useful extension is to fully support the node bootstrap phase, including node association and beacon request/reply. The goal of the project is to enhance the lr-wpan module so to use beacons in the bootstrap phase along with network scanning and pan-id resolution for in-range coordinators.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' 802.15.4 standard
** ''Interests:'' WSN
** ''Difficulty:'' medium
** ''Recommended reading:''
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== 802.15.4 Beacon-enabled mode ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Beacon-enabled mode:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. Unlike Contiki-os, the model could benefit from supporting beacon-enabled mode of operation. The beacon-enabled mode is a fully slotted transmission mode, with guaranteed slots and bound performances, unlike the ad-hoc mode. This is especially important because the L3 routing protocols might be strongly affected by the lower-layer topology. Hence it is of paramount importance to be able to simulate both in ns-3. The goal of the project is to develop the new beacon-enabled MAC layer for the lr-wpan module.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' 802.15.4 standard
** ''Interests:'' WSN
** ''Difficulty:'' medium/hard
** ''Recommended reading:''
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== Simulating the Internet of Things in NS-3 ===
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]

In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.
** ''Required experience'' : C++
** ''Bonus experience'' : NS-2, WSN, Matlab
** ''Interests'' : ZB, embedded, wireless, sensor networks
** ''Difficulty'' : medium
** ''Recommended reading'' :
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia

=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested.
** ''Required Experience:'' C++, IPv6, RPL
** ''Bonus Experience:'' WSN networking
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression
** ''Difficulty:'' hard
** ''Recommended reading:''
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks

=== RPL protocol Metric and Constraints ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).
** ''Required Experience:'' C++, IPv6,
** ''Bonus Experience:'' RPL protocol
** ''Interests:'' WSN, routing
** ''Difficulty:'' medium
** ''Recommended reading:''
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks

=== IPv6 stack validation and improvements ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].
*# Flow Monitor module does not work on the IPv6 stack
*# FlowLabel header field is not currenly used
*# IPSec is not supported
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.
** ''Required Experience:'' C++, TCP/IP networking
** ''Bonus Experience:'' IPv6 protocols
** ''Interests:'' IPv6 internetworking
** ''Difficulty:'' easy / medium, depending on the features implemented
** ''Recommended reading:''
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]
*** ns-3 Flowmon module documentation
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]

=== Multicast IPv6 traffic support ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.
** ''Required Experience:'' C++, IPv6,
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)
** ''Interests:'' routing, multicast
** ''Difficulty:'' medium/hard
** ''Recommended reading:''
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])

=== High performance ns-3 emulation with Direct NIC Access ===

Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]

The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets.
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.
* ''Required Experience:'' C++, Linux
* ''Interests:'' network performance, emulation
* ''Difficulty:'' hard
* ''Recommended reading:''
** http://www.ntop.org/products/pf_ring/libzero-for-dna/

=== LTE Idle Mode Procedures ===

Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]

* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.
* ''Required Experience:'' C++, LTE
* ''Interests:'' mobility management
* ''Difficulty:'' medium/hard
* ''Recommended reading:''
** 3GPP TS 36.300 "E-UTRA and E-UTRAN overall description", section 10.1.1 "Mobility Management in ECM-IDLE"
** 3GPP TS 36.304 "User Equipment (UE) procedures in idle mode"
** 3GPP TS 24.301 "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)"

=== Decouple traffic generators from sockets ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]

* ns-3 uses applications that are part traffic generator, part socket-based application. The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks. This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.
* ''Required Experience:'' C++, sockets API
* ''Interests:''
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** Unix Network Programming (Stevens) or equivalent

=== FlowMonitor for IPv6 ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]

* The flow monitor is popular with users for monitoring IPv4 traffic, but it is not compatible with IPv6. This project would first focus on enabling flow monitor for IPv6, and could be extended by general
* ''Required Experience:'' C++
* ''Interests:'' IPv6, data visualization
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** flow monitor code (src/flow-monitor), and ns-3-users posts over the past year regarding the flow monitor

=== ARP and NDisc cache visibility ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]

* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches. Something similar to how PrintRoutes is done for IPv4 would be useful. Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).
* ''Required Experience:'' C++
* ''Interests:'' IPv4 and Ipv6
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** source code in src/internet, and the bugs mentioned above

[[Category:GSoC]]

GSOC2013Projects

2013-03-28T10:49:52Z

Vedranm: Remove unnecessary HTML tags

{{TOC}}

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net

= GSoC 2013 Ideas =

This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.

GSOC 2012 Timeline is:
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.
* March 29 - 19:00 UTC: Mentoring organization application deadline.
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.
* April 22 - 19:00 UTC: Student application period opens.
* May 3 - 19:00 UTC: Student application deadline.
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013

While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8.

== About the ns-3 project ==

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.

Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011). ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained. The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.

Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson]. The project has participated in past GSoCs during 2008-10 and 2012.

Mentors will be paired with students based on the projects that are selected. Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring. Prospective mentors should notify Lalith Suresh of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.

== Getting started ==

For students interested in applying to ns-3 for GSOC, go through the following list to get started:
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].
* Look through our ideas list below to see if you find a project that interests you.
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.

== Project Ideas ==

The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.

<blockquote>
Each project idea within a particular priority has been tagged with the following properties:
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
* ''Difficulty:'' easy, medium or difficult
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.
</blockquote>

= Guidelines for project ideas =

For mentors who're adding project ideas to the list below, please ensure that:

* The projects are sized such that there can be a code merge by the end of the coding period. The scope of the project should be such that it is very difficult to not have a code merge by the end of the summer.
* The proposed projects are not too open-ended. That is, if the deliverables or a clear path to the same are not well understood, it is better kept outside GSOC.

= Project Ideas =

=== Vehicular Ad-hoc Networks ===

Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]

* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)
# higher layers: nothing specific to WAVE is currently available.
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).
** ''Required experience:'' C++.
** ''Bonus experience:'' Wireless networking, WAVE.
** ''Interests:'' Wireless networking, VANETs.
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.
** ''Recommended reading''
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php

=== 802.15.4 Energy Model ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' ns-3 Energy model
** ''Interests:'' WSN, Battery discharge
** ''Difficulty:'' easy
** ''Recommended reading:''
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes]
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]

=== 802.15.4 Bootstrap ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Bootstrap:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. An useful extension is to fully support the node bootstrap phase, including node association and beacon request/reply. The goal of the project is to enhance the lr-wpan module so to use beacons in the bootstrap phase along with network scanning and pan-id resolution for in-range coordinators.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' 802.15.4 standard
** ''Interests:'' WSN
** ''Difficulty:'' medium
** ''Recommended reading:''
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== 802.15.4 Beacon-enabled mode ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''802.15.4 Beacon-enabled mode:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is able to simulate an 802.15.4 network in ad-hoc mode, much like Contiki-os nodes do. Unlike Contiki-os, the model could benefit from supporting beacon-enabled mode of operation. The beacon-enabled mode is a fully slotted transmission mode, with guaranteed slots and bound performances, unlike the ad-hoc mode. This is especially important because the L3 routing protocols might be strongly affected by the lower-layer topology. Hence it is of paramount importance to be able to simulate both in ns-3. The goal of the project is to develop the new beacon-enabled MAC layer for the lr-wpan module.
** ''Required Experience:'' C++, WSN
** ''Bonus Experience:'' 802.15.4 standard
** ''Interests:'' WSN
** ''Difficulty:'' medium/hard
** ''Recommended reading:''
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]

=== Simulating the Internet of Things in NS-3 ===
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]

In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.
** ''Required experience'' : C++
** ''Bonus experience'' : NS-2, WSN, Matlab
** ''Interests'' : ZB, embedded, wireless, sensor networks
** ''Difficulty'' : medium
** ''Recommended reading'' :
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia

=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested.
** ''Required Experience:'' C++, IPv6, RPL
** ''Bonus Experience:'' WSN networking
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression
** ''Difficulty:'' hard
** ''Recommended reading:''
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks

=== RPL protocol Metric and Constraints ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).
** ''Required Experience:'' C++, IPv6,
** ''Bonus Experience:'' RPL protocol
** ''Interests:'' WSN, routing
** ''Difficulty:'' medium
** ''Recommended reading:''
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks

=== IPv6 stack validation and improvements ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].
*# Flow Monitor module does not work on the IPv6 stack
*# FlowLabel header field is not currenly used
*# IPSec is not supported
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.
** ''Required Experience:'' C++, TCP/IP networking
** ''Bonus Experience:'' IPv6 protocols
** ''Interests:'' IPv6 internetworking
** ''Difficulty:'' easy / medium, depending on the features implemented
** ''Recommended reading:''
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]
*** ns-3 Flowmon module documentation
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]

=== Multicast IPv6 traffic support ===

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.
** ''Required Experience:'' C++, IPv6,
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)
** ''Interests:'' routing, multicast
** ''Difficulty:'' medium/hard
** ''Recommended reading:''
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])

=== High performance ns-3 emulation with Direct NIC Access ===

Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]

The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets.
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.
* ''Required Experience:'' C++, Linux
* ''Interests:'' network performance, emulation
* ''Difficulty:'' hard
* ''Recommended reading:''
** http://www.ntop.org/products/pf_ring/libzero-for-dna/

=== LTE Idle Mode Procedures ===

Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]

* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.
* ''Required Experience:'' C++, LTE
* ''Interests:'' mobility management
* ''Difficulty:'' medium/hard
* ''Recommended reading:''
** 3GPP TS 36.300 "E-UTRA and E-UTRAN overall description", section 10.1.1 "Mobility Management in ECM-IDLE"
** 3GPP TS 36.304 "User Equipment (UE) procedures in idle mode"
** 3GPP TS 24.301 "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)"

=== Decouple traffic generators from sockets ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] (looking for another mentor, if interested)

* ns-3 uses applications that are part traffic generator, part socket-based application. The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks. This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.
* ''Required Experience:'' C++, sockets API
* ''Interests:''
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** Unix Network Programming (Stevens) or equivalent

=== FlowMonitor for IPv6 ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] (looking for another mentor, if interested)

* The flow monitor is popular with users for monitoring IPv4 traffic, but it is not compatible with IPv6. This project would first focus on enabling flow monitor for IPv6, and could be extended by general
* ''Required Experience:'' C++
* ''Interests:'' IPv6, data visualization
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** flow monitor code (src/flow-monitor), and ns-3-users posts over the past year regarding the flow monitor

=== ARP and NDisc cache visibility ===

Mentors: [mailto:tomh@tomh.org Tom Henderson] (looking for another mentor, if interested)

* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches. Something similar to how PrintRoutes is done for IPv4 would be useful. Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).
* ''Required Experience:'' C++
* ''Interests:'' IPv4 and Ipv6
* ''Difficulty:'' easy/medium
* ''Recommended reading:''
** source code in src/internet, and the bugs mentioned above

[[Category:GSoC]]

DevelMeetingMar2013

2013-02-26T16:58:23Z

Vedranm: time resolution

{{TOC}}

= Location and Schedule =

The meeting will occur Wed March 6 through Fri March 8 at INRIA Sophia Antipolis. INRIA will provide us with a large enough conference room to meet. We will meet for three days, and people can attend whatever portion they feel like.

A more detailed schedule will be posted at a later date.

== Other events this week ==

* Information about Monday's [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ Annual Meeting March 2013]
* Information about Tuesday's [http://www.nsnam.org/wns3/wns3-2013/ Workshop on ns-3 2013]

== Lodging and Directions ==

INRIA Sophia Antipolis is located on a hillside above [http://en.wikipedia.org/wiki/Antibes Antibes] / [http://en.wikipedia.org/wiki/Juan-les-Pins Juan les Pins], France. It is possible to reach the center by public transport from Antibes, Nice, and Cannes.

* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/venue-and-useful-information/ Venue and Useful Information]
* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/accommodation/ Hotel accommodations]

== Registration ==

Attendance is free but everyone must obtain a visitor badge to enter INRIA. Please list yourself as an attendee and provide contact information as needed to tomh@tomh.org if you want to attend.

== Attendees ==

Please add your name here if you intend to attend, and which days.

* [[User:Tomh|Tom Henderson]], Wed, Thurs, Fri
* [[User:Vedranm|Vedran Miletic]], Wed, Thurs, Fri (Fri half day only)
* George Riley, Wed, Thurs
* Brian Swenson, Wed, Thurs
* Nicola Baldo, Wed, Thurs, maybe Fri
* Daniel Camara, Wed, Thurs, Fri
* Peter Barnes, Fri (and possibly parts of Wed, Thurs)

* [[User:tommaso|Tommaso Pecorella]], Wed, Thurs, Fri (Fri half day only)

* [[User:Tazaki|Hajime Tazaki]], Wed, Thurs, Fri
* Alina Quereilhac, Wed, Thurs, Fri

= Suggested agenda/topics =

Please list suggested discussion topics below and we will build a schedule at a later date. Please also suggest 'read-ahead' items as needed.

* Object Start/Stop
* ns-3 in education
* XML as a language for simulation specification, Peter Barnes' talk
** some ideas could be taken from SimGrid guys, they have rather small XML files that say a lot of things
* data collection framework
* variable test scope (bug 1563)
* Modularization of ns-3
* user feedback: what areas (documentation, API) can be improved from a user standpoint? This discussion will be based on feedback from people who have been active on the ns-3-users mailing list.
* DCE release plan review
* Time::SetResolution patch by Peter Barnes and Mathieu Lacage, how to fix it and proceed with merging

[[Category:DevelMeeting]]

DevelMeetingMar2013

2013-02-26T14:58:07Z

Vedranm: I will attend Fri half day only

{{TOC}}

= Location and Schedule =

The meeting will occur Wed March 6 through Fri March 8 at INRIA Sophia Antipolis. INRIA will provide us with a large enough conference room to meet. We will meet for three days, and people can attend whatever portion they feel like.

A more detailed schedule will be posted at a later date.

== Other events this week ==

* Information about Monday's [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ Annual Meeting March 2013]
* Information about Tuesday's [http://www.nsnam.org/wns3/wns3-2013/ Workshop on ns-3 2013]

== Lodging and Directions ==

INRIA Sophia Antipolis is located on a hillside above [http://en.wikipedia.org/wiki/Antibes Antibes] / [http://en.wikipedia.org/wiki/Juan-les-Pins Juan les Pins], France. It is possible to reach the center by public transport from Antibes, Nice, and Cannes.

* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/venue-and-useful-information/ Venue and Useful Information]
* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/accommodation/ Hotel accommodations]

== Registration ==

Attendance is free but everyone must obtain a visitor badge to enter INRIA. Please list yourself as an attendee and provide contact information as needed to tomh@tomh.org if you want to attend.

== Attendees ==

Please add your name here if you intend to attend, and which days.

* [[User:Tomh|Tom Henderson]], Wed, Thurs, Fri
* [[User:Vedranm|Vedran Miletic]], Wed, Thurs, Fri (Fri half day only)
* George Riley, Wed, Thurs
* Brian Swenson, Wed, Thurs
* Nicola Baldo, Wed, Thurs, maybe Fri
* Daniel Camara, Wed, Thurs, Fri
* Peter Barnes, Fri (and possibly parts of Wed, Thurs)

* [[User:tommaso|Tommaso Pecorella]], Wed, Thurs, Fri (Fri half day only)

* [[User:Tazaki|Hajime Tazaki]], Wed, Thurs, Fri

= Suggested agenda/topics =

Please list suggested discussion topics below and we will build a schedule at a later date. Please also suggest 'read-ahead' items as needed.

* Object Start/Stop
* ns-3 in education
* XML as a language for simulation specification, Peter Barnes' talk
** some ideas could be taken from SimGrid guys, they have rather small XML files that say a lot of things
* data collection framework
* variable test scope (bug 1563)
* Modularization of ns-3
* user feedback: what areas (documentation, API) can be improved from a user standpoint? This discussion will be based on feedback from people who have been active on the ns-3-users mailing list.
* DCE release plan review

[[Category:DevelMeeting]]

DevelMeetingOct2011

2013-02-19T10:59:28Z

Vedranm: Add to DevelMeeting category

{{TOC}}

= Minutes =

[http://www.nsnam.org/docs/meetings/october11.txt meeting minutes]

Slides:
* [[Media:Developer-mtg-oct-2011-henderson.pdf | Tom Henderson's slides]]
* [[Media:LLNL_Intro_to_ns3_20111027.pdf | Peter Barnes' slides]]

= Location and Schedule =

Virtual, Thursday October 27 (19h00-21h00 UTC). For North American participants, this is 3pm-5pm EDT.

= Suggested agenda/topics =

(Not all items were covered during the actual meeting)

# Introductions: What is everyone working on these days?
#* Tom and Mitch, random number rework, 802.15.4, etc.
#* INRIA, introduce Daniel Camara, update on DCE and other INRIA activities
#* Peter Barnes, LLNL, would like to introduce his group
#* Vedran Miletic, CSMA; reliability (with Tommaso) and optics (hopefully)
#* others ...
# review of current codebase, buildbots, open code reviews, open bugs, release schedule, etc. (Tom)
# next steps with ns-3 app store concept and modular build (Mathieu)
# supporting GUIs (John)
# ns-3 for windows-- next steps (John)
# Code cleanups (Vedran Miletic)
# RPM packaging (Vedran Miletic)

[[Category:DevelMeeting]]

DevelMeetingNov2010

2013-02-19T10:59:19Z

Vedranm: Add to DevelMeeting category

{{TOC}}

= Logistics =

The meeting will be held on Friday November 5 at the following location in International Square:
1875 I Street, N.W. 5th floor, Washington, DC, 20006
[http://www.regus.com/locations/US/DC/Washington/DistrictOfColumbiaWashingtonInternationalSquare.htm?product=offices Site information]

The meeting will run from 8:30am-5pm. There will be no cost to attend. We are not presently planning to provide food and beverages but instead will likely break for lunch nearby.

This meeting is three [http://www.wmata.com/ Metro] stops from the site of the [http://www.geni.net GENI Engineering Conference] that concludes on November 4.

The meeting site is not a hotel but an office building. The [http://www.omnihotels.com/FindAHotel/WashingtonDCShoreham.aspx Omni Shoreham] will be hosting the GENI Engineering Conference. Please note that the Omni Shoreham is three metro stops away and is considered a luxury hotel from a price perspective. Attendees to the GENI meeting, who have obtained a room at the GENI rate of $181.00, should note that the Omni Shoreham has been extending the reservation to include Friday Nov. 5 if you phone them, although it is not available through the online reservation.

[http://www.omnihotels.com/FindAHotel/WashingtonDCShoreham/MeetingFacilities/NSFGENI9Engineering11.aspx Online booking link for GEC hotel]

= Attendance and RSVP =

Please contact [mailto:tomh@tomh.org Tom Henderson] if you want to attend, because space will be limited to roughly 20 people. Please also contact if you have agenda items to suggest.

= Agenda =

Please contribute ideas of things you would like to talk about. These topics are being developed further:

== ns-3 automation ==

We will review the current work on automation being led by Felipe Perrone at Bucknell. See the [http://www.nsnam.org/wiki/index.php/NSF_Frameworks Frameworks] page. See also [http://www.eg.bucknell.edu/safe/ this Bucknell page].

If any code is available for review prior to the meeting, a link will be posted here.

== Motion Planning Framework ==

David Claypool will present the mobility schema and tool framework that NRL has been working on.

== ns-3 modular build and package management system ==

We will review the status and priorities for ns-3 modular build and package management system. See [http://www.nsnam.org/wiki/index.php/App_Store_Technical_Requirements this page] for background information.

== Other topics ==

* Michele Weigle will update us on Tmix and Delaybox for ns-3
* non-internet architectures for ns-3
* review Hemanth Narra's TDMA model or other [https://wiki.ittc.ku.edu/resilinets/Main_Page ResiliNets] work
* Felipe Perrone may speak about his experience with ns-3, coming from an [http://www.ssfnet.org/homePage.html SSF] background
* talk about how to make progress on some bugs

= Last developers meeting =

Held in March 2010 in Malaga Spain.

* [http://www.nsnam.org/wiki/index.php/DevelMeeting wiki page]
* [http://www.nsnam.org/docs/meetings/march10.txt meeting notes]

[[Category:DevelMeeting]]

DevelMeetingMar2013

2013-02-19T10:59:08Z

Vedranm: Add to DevelMeeting category

{{TOC}}

= Location and Schedule =

The meeting will occur Wed March 6 through Fri March 8 at INRIA Sophia Antipolis. INRIA will provide us with a large enough conference room to meet. We will meet for three days, and people can attend whatever portion they feel like.

A more detailed schedule will be posted at a later date.

== Other events this week ==

* Information about Monday's [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ Annual Meeting March 2013]
* Information about Tuesday's [http://www.nsnam.org/wns3/wns3-2013/ Workshop on ns-3 2013]

== Lodging and Directions ==

INRIA Sophia Antipolis is located on a hillside above [http://en.wikipedia.org/wiki/Antibes Antibes] / [http://en.wikipedia.org/wiki/Juan-les-Pins Juan les Pins], France. It is possible to reach the center by public transport from Antibes, Nice, and Cannes.

* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/venue-and-useful-information/ Venue and Useful Information]
* [https://www.nsnam.org/consortium/activities/annual-meeting-march-2013/accommodation/ Hotel accommodations]

== Registration ==

Attendance is free but everyone must obtain a visitor badge to enter INRIA. Please list yourself as an attendee and provide contact information as needed to tomh@tomh.org if you want to attend.

== Attendees ==

Please add your name here if you intend to attend, and which days.

* [[User:Tomh|Tom Henderson]], Wed, Thurs, Fri
* [[User:Vedranm|Vedran Miletic]], Wed, Thurs, Fri
* George Riley, Wed, Thurs
* Brian Swenson, Wed, Thurs
* Nicola Baldo, Wed, Thurs, maybe Fri
* Daniel Camara, Wed, Thurs, Fri
* Peter Barnes, Fri (and possibly parts of Wed, Thurs)

= Suggested agenda/topics =

Please list suggested discussion topics below and we will build a schedule at a later date. Please also suggest 'read-ahead' items as needed.

* Object Start/Stop
* ns-3 in education
* XML as a language for simulation specification, Peter Barnes' talk
** some ideas could be taken from SimGrid guys, they have rather small XML files that say a lot of things
* data collection framework
* variable test scope (bug 1563)
* Modularization of ns-3
* user feedback: what areas (documentation, API) can be improved from a user standpoint? This discussion will be based on feedback from people who have been active on the ns-3-users mailing list.

[[Category:DevelMeeting]]

DevelMeetingMar2012

2013-02-19T10:58:55Z

Vedranm: Add to DevelMeeting category

{{TOC}}

= Location and Schedule =

At the same hotel as SIMUTools 2012, on Saturday March 24, the day after [http://www.nsnam.org/wns3/wns3-2012/ WNS3]

* The meeting site is the [http://www.simutools.org/2012/Venue/ConferenceSite same site] as the conference
* The meeting has no registration fees
* The meeting is open to anyone interested
* Lunch and coffee will be provided.
* The tentative schedule is 09h00-17h00 with lunch break.

= Attendance =

* Tommaso Pecorella (University of Florence)
* Tom Henderson
* Felipe Perrone
* George Riley
* Lalith Suresh
* Peter Barnes
* Nicola Baldo
* Pavel Boyko
* Kirill Andreev
* Dmitry Petrov (University of Jyväskylä, Magister Solutions, Finland)
* Jani Puttonen (Magister Solutions, Finland)
* Hajime Tazaki
* Mathieu Lacage
* Daniel Camara
* Alina Quereilhac
* Frederic Urbani
* James Sterbenz
* Chris Main
* Ken Renard

Remote:

* Gustavo Carneiro (remotely)
* Vedran Miletić (remotely)
* Resilinets group

= Tentative Topics =

Morning session: near-term release and development

* ns-3.14 and ns-3.15 release plans (Tom H)
** Review ns-3 packaging status ([http://fedoraproject.org/wiki/Features/Ns3 Fedora], [http://packages.qa.debian.org/n/ns3.html Debian]/[http://packages.ubuntu.com/source/precise/ns3 Ubuntu]), discuss long term support for releases
** Code reviews
** Bugs/patches to discuss
** ns-3-rng status
* Review requirements, plans, and schedule for further modularization of ns-3, including moving towards realizing the app store
** status of the 'bake' tool (http://www-sop.inria.fr/members/Daniel.Camara/bake/)
** metadata to describe modules
** app store infrastructure
* Imposing a check-style mercurial hook for ns-3-dev (for .cc files only) (Tom H)
* Documentation: what are requirements for future merges, and how to define a realistic path to clean up and finish the current codebase
* new [http://mailman.isi.edu/pipermail/ns-developers/2012-January/009789.html Jenkins CI system]: what are the near-term requirements/priorities for this
** Add clang build to build bots?
* Review Google Summer of Code plans

Afternoon session: longer-term development and project issues

* Memory leaks extermination process, see John Abraham mail: [http://mailman.isi.edu/pipermail/ns-developers/2012-February/009990.html]
* Review some emerging products of [http://redmine.eg.bucknell.edu/perrone/projects/framework SAFE]
** Steady state and termination detector (http://code.nsnam.org/safe/ns-3-safe/file/5acb941079b7/src/stats/model/output-analyzer.h)
** API and architecture for data collection (slides TBD)
** Experiment execution manager (slides TBD)
* Start/stop of nodes and net devices.
* list netiquette and FAQ. Draft here: https://www.nsnam.org/wiki/index.php/Ns-3-users-netiquette.
* Future WNS3 events
* ns-2 on www.nsnam.org

= Action Points =

[[Category:DevelMeeting]]

DevelMeetingMar2011

2013-02-19T10:58:41Z

Vedranm: Add to DevelMeeting category

{{TOC}}

= Location and Schedule =

Will be held in Barcelona, on Saturday, March 26th. That's one day after WNS3 co-located with Simutools 2011.

The meeting will be hosted at the CTTC Demo Centre, calle Sancho de Avila 110-130, 08018 Barcelona.



= Tentative Attendance =

If you'd like to attend, please add your name.
* Tom Henderson
* Nicola Baldo
* Ruben Merz
* Felipe Perrone
* Lalith Suresh
* Marco Miozzo
* Giuseppe Piro
* George Riley
* Mustafa Al-Bado
* Pavel Boyko
* Andrey Mazo
* Aurimas Liutikas
* Jose Nuñez
* Jaime Ferragut
* Justin P. Rohrer

= Tentative Topics =
* 9:30 A+) Data collection framework (Felipe)
* 10:30 A+) Review modular build system
* 11:00 A+) next phase of the modular build system
* 11:30 A) ns-3 Summer of Code (Lalith)
* 12:00 A) Website review (Tom)
* 12:30 lunch
* 14:00 A) Usability of ns-3
** e.g., using it as courseware
** also look at feedback from mailing lists
* 14:30 B) Documentation (Tom)
* 15:00 B) Deterministic MAC/Physical wireless models for new users and for routing/transport development (Justin)
* 15:30 B) Simple non-IP network layer example (Justin)
* 16:00 C) Topology generation (George)
* 16:15 C) ns-3-click development (Lalith, Ruben)
* 16:30 AOB
* 17:00 beer

= Action Points =

* Tom to write the guidelines for release managers
* Ruben to check for a polling system to poll/survey/googledocs

[[Category:DevelMeeting]]

DevelMeetingMar2010

2013-02-19T10:58:18Z

Vedranm: Add to DevelMeeting category

== When and where ==

Tuesday, 16 March 2010, Malaga, Spain, colocated with SIMUTools. ICST (the SIMUTools organizer) has arranged a room for us at the [http://www.simutools.org/Venue/ConferenceSite conference site].

== Who ==

If you are interested in attending, please put your name below:

* Tom Henderson
* Mathieu Lacage
* Faker Moatamri
* Hajime Tazaki
* George Riley
* Josh Pelkey
* Jens Mittag
* Nicola Baldo
* Stylianos Papanastasiou
* Pavel Boyko
* Kirill Andreev
* Patrick Fontaine
* Elias Weingartner
* Hendrik vom Lehn

== Cost ==

The developers meeting will be open without registration, and the conference will provide coffee breaks and lunch. However, ICST is assuming that most or all attendees will be registered for either WNS-3 or SIMUTools main track, so if you plan to attend and you are '''not''' also registered and attending one of the other events that week (WNS-3 or SIMUTools), please contact Tom Henderson so that we can arrange for your lunch and coffee.

== What ==

Here is a list of topics we could talk about: if you are interested in something, please, edit the following list accordingly and insert your name so that we can plan a useful list of discussion topics.

'''We will meet at 0900 and form an agenda based on the interests and peoples' availability'''

=== General maintenance issues ===

* review process:
** coding style updates
** timeliness of reviews
** usefulness of reviews
* zero errors in doxygen?
* documentation organization
* update website design?
* maintainers
* lcov code coverage goals

=== Wireless development issues ===

* Nicola would like to present his spectrum modeling repo
* Wifi:
** Status of work underway within various groups
** PHY layer modeling: preamble synchronization
** MAC block ack support: interaction with rate control
** PHY layer modeling: implementation based on complex time samples (Jens Mittag)
** Performance issues
* Wimax:
** current status, future work planned

=== General software issues ===

* core:
** missing features
** problems with current API
** NixVector in packet
** trace source overhead
* helper:
** feedback about state of current API
** improvements ?
* test framework
* build system and modularity
** optimized builds take forever (see: build/optimized/bindings/python/ns3_module_ping6_3.o)

=== Statistics and NSF frameworks ===

* Feedback/discussion on NSF plans and supporting better workflows
** How should this work be coordinated with devel community?
* what to do about statistics code in src/contrib
** what are the requirements for internal statistics vs external libraries?
** gather statistics about the simulator itself

=== Loose end development issues ===

* Running code simulation
** future work and plan (especially ns-3-simu)
* External file support
** e.g quagga.conf
* Bugs in tracker to discuss?

[[Category:DevelMeeting]]

Category:DevelMeeting

2013-02-19T10:56:26Z

Vedranm: Initial developer meeting category

This category contains all pages describing or relating to ns-3 developer meetings.

DevelMeetingMarch2012

2013-02-19T10:55:24Z

Vedranm: Vedranm moved page DevelMeetingMarch2012 to DevelMeetingMar2012: Renaming pages for consistent naming

#REDIRECT [[DevelMeetingMar2012]]

DevelMeetingMar2012

2013-02-19T10:55:24Z

Vedranm: Vedranm moved page DevelMeetingMarch2012 to DevelMeetingMar2012: Renaming pages for consistent naming

DevelMeetingMarch2011

2013-02-19T10:55:08Z

Vedranm: Vedranm moved page DevelMeetingMarch2011 to DevelMeetingMar2011: Renaming pages for consistent naming

#REDIRECT [[DevelMeetingMar2011]]

DevelMeetingMar2011

2013-02-19T10:55:08Z

Vedranm: Vedranm moved page DevelMeetingMarch2011 to DevelMeetingMar2011: Renaming pages for consistent naming

DevelMeeting

2013-02-19T10:54:42Z

Vedranm: Vedranm moved page DevelMeeting to DevelMeetingMar2010: Renaming pages for consistent naming

#REDIRECT [[DevelMeetingMar2010]]

DevelMeetingMar2010

2013-02-19T10:54:42Z

Vedranm: Vedranm moved page DevelMeeting to DevelMeetingMar2010: Renaming pages for consistent naming

User:Vedranm

2013-02-18T10:36:46Z

Vedranm: www, not wwww

__TOC__

== About me ==
* Name: Vedran Miletić
* Contact: vmileticATinfDOTuniriDOThr
* Work: [http://www.inf.uniri.hr/~vmiletic/ Teaching Assistant] in the [http://www.uniri.hr/ University of Rijeka] [http://www.inf.uniri.hr/ Department of Informatics], Croatia.
* Study: PhD student at [http://www.fer.unizg.hr/ University of Zagreb Faculty of Electrical Engineering and Computing]
* Social networking profiles: [https://twitter.com/vedranmiletic Twitter] [https://bitbucket.org/rivanvx Bitbucket] [https://github.com/rivanvx GitHub]

== Presently working on ==
* [[Object Start Stop specification]]
* [[Optical network models|Prototype WDM Network Simulator]]

== Other interests related to ns-3 ==
* [http://mailman.isi.edu/pipermail/ns-developers/2011-April/008856.html improve CSMA model]
* [https://fedoraproject.org/wiki/Features/Ns3 get RPM package included in Fedora]

Category:Models

2013-02-10T19:14:06Z

Vedranm: Link to http instead of https

Main documentation for models is [http://www.nsnam.org/docs/models/html/index.html ns-3 model library].

The pages in this category describe various models for ns-3, both those included in main distribution and those that aren't. Pages usually provide information such as general info, tips and tricks, installation inforamtion etc. Most of the time, the information provided here complements official documentation (if any) and doesn't serve as a reference; one should look into model library linked above for that.

Category:Models

2013-02-10T19:13:37Z

Vedranm: Link to model library

Main documentation for models is [https://www.nsnam.org/docs/models/html/index.html ns-3 model library].

The pages in this category describe various models for ns-3, both those included in main distribution and those that aren't. Pages usually provide information such as general info, tips and tricks, installation inforamtion etc. Most of the time, the information provided here complements official documentation (if any) and doesn't serve as a reference; one should look into model library linked above for that.

User:Vedranm

2013-02-10T18:13:37Z

Vedranm: Update

__TOC__

== About me ==
* Name: Vedran Miletić
* Contact: vmileticATinfDOTuniriDOThr
* Work: [http://wwww.inf.uniri.hr/~vmiletic/ Teaching Assistant] in the [http://www.uniri.hr/ University of Rijeka] [http://www.inf.uniri.hr/ Department of Informatics], Croatia.
* Study: PhD student at [http://www.fer.unizg.hr/ University of Zagreb Faculty of Electrical Engineering and Computing]
* Social networking profiles: [https://twitter.com/vedranmiletic Twitter] [https://bitbucket.org/rivanvx Bitbucket] [https://github.com/rivanvx GitHub]

== Presently working on ==
* [[Object Start Stop specification]]
* [[Optical network models|Prototype WDM Network Simulator]]

== Other interests related to ns-3 ==
* [http://mailman.isi.edu/pipermail/ns-developers/2011-April/008856.html improve CSMA model]
* [https://fedoraproject.org/wiki/Features/Ns3 get RPM package included in Fedora]

Education

2013-02-10T17:35:59Z

Vedranm: Actually link to new name

{{TOC}}

= Using ns-3 in Education =

This page is a resource for learning about ns-3 as an educational tool for networking education.

== Papers ==

The [http://education.sigcomm.org/Workshop2011/Workshop2011 2011 Sigcomm Education workshop] had a paper regarding ns-3 use in the classroom:
* [http://edusigcomm.info.ucl.ac.be/Workshop2011/20110310001 An Open-source and Declarative Approach Towards Teaching Large-scale Networked Systems Programming]

== Courses using ns-3 ==

The following courses have used ns-3 as courseware or to support projects
* [http://users.ece.gatech.edu/~riley/ece6110/ Georgia Tech. ECE 6110] Dr. George Riley, Fall 2011, also Fall 2010
* The University of Kansas [http://www.ittc.ku.edu/~jpgs/courses/nets/ EECS 780], [http://www.ittc.ku.edu/~jpgs/courses/mwnets/ EECS 882], and [http://www.ittc.ku.edu/~jpgs/courses/rsnets/ EECS 983] Dr. James Sterbenz, 2010 – 2012
* [http://www.cis.upenn.edu/~boonloo/cis553-fa10/ UPenn CIS 553/TCOM 512] Dr. Boon Thau Loo, Fall 2010
* [https://noppa.tkk.fi/noppa/kurssi/s-38.2188/ Aalto University] Jose Costa-Requena and Markus Peuhkuri, Fall 2011
* [http://www.cse.iitb.ac.in/synerg/doku.php?id=public:courses:cs641-autumn08:start Indian Institute of Technology Bombay] Bhaskaran Raman, Autumn 2008
* University of Rijeka
** [http://inf2.uniri.hr/hgwiki/RM2 RM2-InfUniRi], Dr. Mario Radovan and [[User:Vedranm|Vedran Miletić]], Spring 2013, also Spring 2012
** [http://inf2.uniri.hr/hgwiki/RM-RiTeh RM-RiTeh], Dr. Mladen Tomić and [[User:Vedranm|Vedran Miletić]], Spring 2013

== Other resources ==

* Lalith Suresh's [[Lab Assignments using ns-3]] page.

== ns-2 Education ==

This page contains references to the use of ns-2 and nam in education:
http://www.isi.edu/nsnam/ns/edu/

Education

2013-02-10T17:35:33Z

Vedranm: Link to new name

{{TOC}}

= Using ns-3 in Education =

This page is a resource for learning about ns-3 as an educational tool for networking education.

== Papers ==

The [http://education.sigcomm.org/Workshop2011/Workshop2011 2011 Sigcomm Education workshop] had a paper regarding ns-3 use in the classroom:
* [http://edusigcomm.info.ucl.ac.be/Workshop2011/20110310001 An Open-source and Declarative Approach Towards Teaching Large-scale Networked Systems Programming]

== Courses using ns-3 ==

The following courses have used ns-3 as courseware or to support projects
* [http://users.ece.gatech.edu/~riley/ece6110/ Georgia Tech. ECE 6110] Dr. George Riley, Fall 2011, also Fall 2010
* The University of Kansas [http://www.ittc.ku.edu/~jpgs/courses/nets/ EECS 780], [http://www.ittc.ku.edu/~jpgs/courses/mwnets/ EECS 882], and [http://www.ittc.ku.edu/~jpgs/courses/rsnets/ EECS 983] Dr. James Sterbenz, 2010 – 2012
* [http://www.cis.upenn.edu/~boonloo/cis553-fa10/ UPenn CIS 553/TCOM 512] Dr. Boon Thau Loo, Fall 2010
* [https://noppa.tkk.fi/noppa/kurssi/s-38.2188/ Aalto University] Jose Costa-Requena and Markus Peuhkuri, Fall 2011
* [http://www.cse.iitb.ac.in/synerg/doku.php?id=public:courses:cs641-autumn08:start Indian Institute of Technology Bombay] Bhaskaran Raman, Autumn 2008
* University of Rijeka
** [http://inf2.uniri.hr/hgwiki/RM2 RM2-InfUniRi], Dr. Mario Radovan and [[User:Vedranm|Vedran Miletić]], Spring 2013, also Spring 2012
** [http://inf2.uniri.hr/hgwiki/RM-RiTeh RM-RiTeh], Dr. Mladen Tomić and [[User:Vedranm|Vedran Miletić]], Spring 2013

== Other resources ==

* Lalith Suresh's [[Lab Assignments]] page.

== ns-2 Education ==

This page contains references to the use of ns-2 and nam in education:
http://www.isi.edu/nsnam/ns/edu/

Main Page

2013-02-10T17:34:02Z

Vedranm: Transclude current events

Nsnam:Current events

2013-02-10T17:32:28Z

Vedranm: Fill with current events for transclusion on main page

== Upcoming Releases ==
* [[ns-3.17]] is scheduled for mid-April, 2013.

== Upcoming Events ==
A full week of ns-3 activities is planned for the south of France, 4-8 March 2013.
* 4 March 2013, [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ NS-3 Consortium annual meeting] at INRIA. This is a free event with plenary talks and tutorials for newcomers and advanced users.
* 5 March 2013, [http://www.nsnam.org/wns3/wns3-2013/ WNS3-2013: The fifth annual Workshop on ns-3, Cannes, France]. Registration for this event is organized by [http://icst.org ICST] as part of [http://simutools.org/2013/ SIMUTools 2013], and is held in Cannes, France.
* 6-8 March 2013, [[DevelMeetingMar2013 | ns-3 developers meeting]] will be held at INRIA and will be a free, open meeting.
A large amount of logistic information is provided [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ here]. Please note that you must separately register for each event, as can be found on the links above.

== Recent Events ==
* [[ns-3.16]] was released on 21 December 2012.
* ns-3 was one of the [http://www.google-melange.com/gsoc/accepted_orgs/google/gsoc2012 180 projects] selected for the 2012 edition of Google Summer of Code. Three students have recently completed their projects. Our 2012 GSoC page: '''[[GSOC2012AcceptedProjects | 2012 GSOC accepted projects]]'''

Main Page

2013-02-10T17:28:24Z

Vedranm: Move next level content to community portal

{{TOC}}

This [http://en.wikipedia.org/wiki/Wiki wiki] complements the [http://www.nsnam.org/ main ns-3 web site]. It is powered by [[Special:Version|MediaWiki]].

'''Account Policy:''' Due to spam problems, we have disabled the ability to create new accounts and to edit/move pages without moderator approval; our experience on the ns-2 wiki with [http://www.mediawiki.org/wiki/Extension:ConfirmEdit Mediawiki captchas] has been ineffective. If you would like to edit this wiki, please email [mailto:webmaster@nsnam.org?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 ==
* [[ns-3.17]] is scheduled for mid-April, 2013.

== Upcoming Events ==

A full week of ns-3 activities is planned for the south of France, 4-8 March 2013.
* 4 March 2013, [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ NS-3 Consortium annual meeting] at INRIA. This is a free event with plenary talks and tutorials for newcomers and advanced users.
* 5 March 2013, [http://www.nsnam.org/wns3/wns3-2013/ WNS3-2013: The fifth annual Workshop on ns-3, Cannes, France]. Registration for this event is organized by [http://icst.org ICST] as part of [http://simutools.org/2013/ SIMUTools 2013], and is held in Cannes, France.
* 6-8 March 2013, [[DevelMeetingMar2013 | ns-3 developers meeting]] will be held at INRIA and will be a free, open meeting.
A large amount of logistic information is provided [http://www.nsnam.org/consortium/activities/annual-meeting-march-2013/ here]. Please note that you must separately register for each event, as can be found on the links above.

== Recent Events ==
* [[ns-3.16]] was released on 21 December 2012.
* ns-3 was one of the [http://www.google-melange.com/gsoc/accepted_orgs/google/gsoc2012 180 projects] selected for the 2012 edition of Google Summer of Code. Three students have recently completed their projects. Our 2012 GSoC page: '''[[GSOC2012AcceptedProjects | 2012 GSOC accepted projects]]'''

== Current ns-3-dev Build and Test Results ==

We use the [http://jenkins-ci.org Jenkins continuous integration (CI) tool] to regularly test our development tree.
* [https://ns-buildmaster.ee.washington.edu:8010 Jenkins CI dashboard]
* [http://code.nsnam.org/jenkins/ Scripts used to drive Jenkins builds]

== Next Level ==

See [[Nsnam:Community portal|our community portal]].

Nsnam:Community portal

2013-02-10T17:26:40Z

Vedranm: Create community portal

We have created the following pages to allow ns-3 users and developers to find and contribute various information:
* '''[[Roadmap]]''' - Plans for future releases, and what developers are working on
* '''[[Current Development]]''' - What people are working on for ns-3
* '''[[Project Ideas]]''' - Suggested projects at different degrees of difficulty
* '''[[Developer FAQ]]''' - Answers to frequently asked questions for ns-3 developers
* '''[[Tools]]''' - Useful tools
* '''[[Education]]''' - Links to sites containing information about use of ns-3 in education
* '''[[Installation]]''' - Installation tips and prerequisites
* '''[[User FAQ]]''' - Answers to frequently asked questions for ns-3 users
* '''[[HOWTOs]]''' - HOWTOs guides for various simulation activities
* '''[[:Category:Samples|Samples]]''' - Code samples and examples (wiki category)
* '''[[:Category:Models|Models]]''' - Information about various models (wiki category)
* '''[[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

Current Development

2013-02-10T17:16:59Z

Vedranm: Link to new page name

{{TOC}}

On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, please do not hesitate to contact the individuals identified.

There are a few other places to look for current activity on ns-3 development:
* the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.17 | ns-3.17 release]], is scheduled for April 2013.
* we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.
* [[Related_Projects | Related projects] list some active and past projects that are associated with ns-3.
* We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.
* We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'

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

'''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. However, attendance has been spotty lately.

= Development for main trunk of ns-3 =

Some of these projects are active, some dormant, but all seem oriented towards merging with the main trunk of ns-3 if they can be finished off.

== 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.11 merge?

=== 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'': [[HOWTO use Linux namespaces with ns-3]]
* ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.

== Device and channel models ==
=== Optical network: WDM, PON and RoF ===
See [[Optical network 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'': reimplemented in a more general way, see [[Object Start Stop Specification]]

=== 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'': <s>http://code.nsnam.org/mirko/ns-3-80211n</s> Repository has been removed.
* ''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]. Current development is on hold.

=== 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'': [[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 ===

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

Current status is:
* RPL implementation (storing, multicast): almost finished, will be posted for public discussion soon.
** RPL is based on [http://tools.ietf.org/wg/roll/ draft-ietf-roll-rpl-19]
** metrics implemented are of0 and minrank-hysteresis-of
* 6LoWPAN implementation: a development repository is [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN/ here]
* 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).

Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].

=== LTE ===

In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:

* 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, and have posted a repository in February 2011 [http://mailman.isi.edu/pipermail/ns-developers/2011-February/008653.html details here]:
** MAC layer
** mobility
** traffic modelization
** MIMO
* Sandra Frei [http://mailman.isi.edu/pipermail/ns-developers/2011-July/009195.html announced] that a group is working on Evolved Packet System (EPS) support
** GTPv1-U (for the user plane)
** GTPv2-C (for the control plane)
** Diameter: Supported use cases: default- and dedicated bearer establishment
** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment
** X2AP HO without SGW relocation. Endmarker messages are not supported
** PMIPv6: PBU/PBA, LMA, MAG

== Link layer ==

=== 802.21 media independent handover ===

* ''wiki page'': [[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 ===

IPv6 has been integrated into ns-3. Starting from ns-3.14 it will be possible to use TCP and UDP over IPv6. Any further development will be done directly on the main development tree.

Whoever is still using the old repositories previously linked in this section (i.e., https://svnet.u-strasbg.fr/hg/ns-3-ipv6-2nd/) should upgrade to the main ns-3 codebase as soon as possible.

=== 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

=== Multipath TCP ===

NS-3 module for [http://datatracker.ietf.org/wg/mptcp/charter/ MPTCP] (Multipath TCP). The current release is compatible with 3.8 version of NS-3.
A check of the compatibility with the latest version is needed.

* ''Submitted by:'' Bachir CHIHANI
* ''code location:'' http://code.google.com/p/mptcp-ns3/

=== Codel, fq_codel in ns-3 ===
* ''Submitted by:'' Andrew Mcgregor
* ''Code location:'' http://codereview.appspot.com/6463048
* ''Mailing list post:'' http://mailman.isi.edu/pipermail/ns-developers/2012-August/010572.html
* ''Reviewers:'' Tom Henderson and Mathieu Lacage

== 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'': [[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

=== Pastry ===

* ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.
* ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).
* ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: <nowiki>https://bitbucket.org/r_nitsch/libpastry/</nowiki>)
* ''Doxygen documentation:'' http://libpastry.robertnitsch.de
* ''Status:''
** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).
** Mostly finished.
** Node arrival process needs some tweaking.
** Review needed. (We're going to request one as soon as we're ready.)

== 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'': [[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.

GSOC2011StudentApplicationTemplate

2013-02-10T17:13:57Z

Vedranm: Remove manual links and replace them with wiki links

{{TOC}}

<blockquote style="padding: 2em ">

<blockquote style="background: Azure; border: 1px solid rgb(153, 153, 153); padding:1em; text-align: center">
<div> Check out the [[NSOC2011AcceptedProjects|Accepted Projects]] for NSoC 2011!</div>
</blockquote>

* [[GS02011StudentGuide |ns-3 NSoC Student guide]]
* [[GS02011StudentApplicationTemplate |NSoC Student application template]]
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net

</blockquote>

= Student Application Template =

The following are specific items that the ns-3 team requests NSoC applicants to include in their proposal.

== About You ==

<blockquote>
=== Identity Information ===
* ''Name''. Your name
* ''Email''. Your contact email
* ''Country''. Your country of citizenship
* ''Institution''. Accredited institution where you are enrolled as student (college, university, master program, PhD program, undergraduate program, etc).
* ''Advisor''. (if applicable). Is your research work supervised by a professor or research group?

=== Background ===
What experience or training do you have that makes you best suited to this project? 
What is your previous experience with ns-3? 

==== Education ====
Include your academic or professional background related to data networking, as well as any software experience with C++ and/or Python. 
In which school program are you currently enrolled at and what is your specialty there? 
When did you started your current studies?

==== Work ====
Be sure to denote any work experience you have in relevant areas. 
Your past work experience does not need to be a job where you got paid, you can mention any projects you have participated in. 
Have you ever worked on open source projects?

==== Research ====
Make sure to denote any research experience you have in relevant areas.

=== Personal Interests ===
Briefly tell us about the things you are interested in.
</blockquote>

== About The Project ==

<blockquote>
=== Project Proposal ===
What is the specific topic or area of interest you are proposing to work on? 
Explain what this project consists of.

=== Interest ===
Why are you particularly attracted to this project? What makes you the best candidate?

==== Future Plans ====
We are especially interested in NSoC applicants looking to pursue research or work in related areas in the future, so be sure to note any relevant plans you may have.

=== Approach ===
What is your technical plan for achieving the goals of the project? 
What components and functionality will have to be developed, integrated etc.? 
Which development methodology would you use? What testing approach are you going to use to ensure the code quality?

=== Deliverables ===
What do you plan as a mergeable code output for your NSoC effort? Please keep in mind that the program is only 10 weeks long and try to incorporate this realistically in your plan. 
Try to isolate the project's main features, group them into coherent units, and list them as 'milestones' or 'deliverables'. 
The order in which you list the deliverables should correspond to the chronological order in which they will be implemented.

=== Plan ===
What is your task schedule to implement your technical plan and develop your deliverables? 
Try to break down the deliverables into small tasks and assign to each of them the time you think it is going to take you. 
Make sure you consider the time you will need to test and fix your code after every deliverable is finished. 
Order all the tasks chronologically and assign a start and an end date to each of them. Verify that the resulting schedule fits into the 10 weeks you will have. 
It is important to leave some time at the end of the schedule for integrating, testing and fixing the complete project.

=== Timezone ===
What are your expected work hours (in UTC)? 
What is your physical location for the summer? 
The project places no requirements on these but it will affect chat scheduling as well as mentor availability and selection.

=== Commitments ===
Do you have any other commitments over the summer that would impair your ability to participate in the project, e.g., classes, thesis defense, existing work commitments, etc? Note: The project does not expect students to take personal vacations during this period; if there is a personal vacation planned, please state when, and how you would make up the time.
</blockquote>

Of these, the Approach and Deliverables elements will require significant thought, development and discussion. Applicants are advised to bring their ideas to the ns-developers list and open up a discussion with the ns-3 team to develop these portions of their application prior to submission. Only applications that have well refined and developed technical objectives and plans are likely to be competitive. The ns-3 team will provide comments and help refine proposals somewhat after they are initially submitted, but obviously the stronger they start the stronger they will be. Also understand that the better you plan your project by discussing it on the list, the more clearer your path will seem through your summer. In the 2008, 2009 and 2010 GSoCs, our strongest student proposals were clearly those which had discussed their projects at length beforehand on the mailing list and on IRC.

In addition, once NSoC proposals have been accepted and reviewed, promising candidates will be invited to "meet" some of the ns-3 team and discuss their project further in an IRC chat.

[[Category:GSoC]]

GSOC2011Projects

2013-02-10T17:13:42Z

Vedranm: Remove manual links and replace them with wiki links

{{TOC}}

<blockquote style="background: Azure; border: 1px solid rgb(153, 153, 153); padding:1em; text-align: center">
<div> Check out the [[NSOC2011AcceptedProjects|Accepted Projects]] for NSoC 2011!</div>
</blockquote>

<div style="float: left; width: 50%">

* [[GS02011StudentGuide |ns-3 GSoC/NSoC Student guide]]
* [[GS02011StudentApplicationTemplate |NSoC Student application template]]
* [[NSOC2011 |NSoC 2011 page]]
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net
</div><div style="float: left; width: 50%">
[[Image:Ns3GSOC2011Flyer.jpg]]
</div>


= NSoC 2011 Ideas =

This webpage highlights project ideas for ns-3's Summer of Code 2011 effort.

== About the ns-3 project ==

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.
Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011). ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained. The tool is coming into wide use; our web server logged almost 71000 successful downloads of our released software between January 2010 and January 2011, and we have a users mailing list of about 900 members now averaging 200-300 posts per month.

Our NSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson].

== Project Ideas ==

The following are project ideas which the ns-3 team has identified as important and is most interested in working on as part of the 2011 NS-3 Summer of Code. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to NSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being ranked high.

<blockquote>
Each project idea has been tagged with the following properties:
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
* ''Difficulty:'' easy, medium or difficult
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.
</blockquote>

=== Priority Project Ideas ===
---------

The following are work areas the ns-3 project has identified as the highest priorities, has several mentors available, and would be especially interested in having students work on.

<blockquote>

==== Antenna Models ====

Mentors: [mailto:ruben@net.t-labs.tu-berlin.de Ruben Merz]

* '''Antenna Radiation Patterns''' This project would implement support for antenna radiation patterns in the physical layer of ns-3. In addition to enhancing the realism of the ns-3 physical layer, this would also enable to implement directional antennas in ns-3. This project can have a large impact on the ns-3 simulator as it would allow several wireless physical layers to benefit from it, namely 802.11, WiMAX and LTE. If time permits, validation with an 802.11 testbed is envisioned.
** ''Required Experience:'' C++, some knowledge of radio propagation is a plus
** ''Bonus Experience:'' physical layer modeling and simulation, wireless networking
** ''Interests:'' wireless networking, physical layer modeling and simulation
** ''Difficulty'': medium
** ''Recommended readings'': ns-3 propagation models (files <code>*propagation*.{cc,h}</code>), [http://www.ece.cmu.edu/~andersoe/papers/simulation-wiopt.pdf The Impact of Directional Antenna Models on Simulation Accuracy]

==== Vehicular Ad-hoc Networks ====

Mentors: [mailto:g.remy00@gmail.com Guillaume Rémy]

* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement: 1) The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. 2) As for the PHY-specific parameters (slot duration etc.), currently only coverage class 0 is supported [0]. 3) The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented) 4) higher layers: nothing specific to WAVE is currently available. 5) mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3.
** ''Required experience:'' C++.
** ''Bonus experience:'' Wireless networking, WAVE.
** ''Interests:'' Wireless networking, VANETs.
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.
** ''Recommended reading''
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968

==== Satellite network stack ====

Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* '''Satellite networks''' ns-2 incorporates support for satellite network simulations (http://ala.isti.cnr.it/wnlab/tdmadama). Since that work some relevant standards have been approved, particularly by ETSI. This project would investigate the architecture needed to support ETSI-BSM interfaces and some simple satellite return links, like bent-pipe and basic DVB-RCS.
** ''Required Experience:'' C/C++
** ''Bonus Experience:'' Satellite communication protocols, ns-2, basic UML
** ''Interests:'' Satellite systems, Bandwidth-on-demand, control theory
** ''Difficulty'': medium to difficult (depending on the implementation details the student want to include)
** ''Recommended reading:''
*** [http://www.etsi.org/website/technologies/broadbandsatmultimedia.aspx Broadband Satellite Multimedia]
*** [http://en.wikipedia.org/wiki/DVB-RCS Digital Video Broadcasting - Return Channel via Satellite]
*** [http://en.wikipedia.org/wiki/DVB-S2 Digital Video Broadcasting - Satellite - Second Generation]

==== Advanced Queues for NS-3 ====

Mentors: TBD or [mailto:duy@soe.ucsc.edu Duy Nguyen]

* '''Advanced Queue Management''' ns-3 currently has very limited support for more advanced queuing disciplines. The goal of this project is to provide fresh implementation of RED queue to ns-3 by surveying RED queue implementation in ns-2, Linux Kernel (if applicable), and, especially, Sally's RED paper. The preferred outcome of this project will be NS-3 Simulator Tests for RED Technical Report (similar to NS Simulator Tests for RED Technical Report) with extensive validation test cases and providing a framework for other advanced queuing development in ns-3
** ''Required Experience:'' C/C++, knowledge of queuing theory
** ''Bonus Experience:'' ns-2 queues, Linux queues
** ''Interests:'' Advanced queuing models and simulations, queuing theory
** ''Difficulty'': medium to difficult
** ''Recommended reading:''
*** [http://groups.google.com/group/ns-3-reviews/browse_thread/thread/6359c7c94a334f03 Current Progress on Queues in ns-3]
*** [http://icir.org/floyd/red.html General Information on RED]
*** [http://sourceforge.net/projects/nsnam/files/ns-2/2.34/ See ns-2.34/queue/* ]
*** [http://icir.org/floyd/papers/red/red.html Sally's RED paper]
*** [http://icir.org/floyd/papers/redsims.ps NS Simulator Tests for RED Technical Report]
*** [http://code.nsnam.org/duy/ns-3-dev-queues/ If can be useful]

==== Click Modular Router ====

Mentors: [mailto:suresh.lalith@gmail.com Lalith Suresh] and [mailto:ruben@net.t-labs.tu-berlin.de Ruben Merz]

* '''Click MAC Extensions for ns-3-click''' Last year's GSoC saw the integration of the Click Modular router with ns-3. However, one of the limitations of the implementation was that the usage of Click was confined to layer 3 only so as to allow all of ns-3's network device types to work under Click. Click's Wifi MAC specific elements cannot be used with ns-3-click yet. This project would involve keeping ns-3-click compatible with Click's Wifi MAC layer elements. Some possible steps in this direction are: 1) Implementing full Radiotap and/or atheros-descriptor header support for ns-3, 2) Implementing a ClickWifiMac abstraction that acts as a MAC high model for a NetDevice, connecting Click's interfaces directly to the lower MAC layers, 3) possibly implementing tx-queue feedback. Getting step 2 right can be a little tricky. Helpers will also be required to ease the end user's life. The above should be implemented as an alternate run-mode for ns-3-click operation. This should then be extensively tested and validated against some stock Click graphs.
** ''Required Experience:'' C++.
** ''Bonus Experience:'' Click, routing architectures, wireless networking.
** ''Interests:'' Routing architectures, protocol development.
** ''Difficulty:'' Medium.
** ''Recommended Reading:''
*** [http://portal.acm.org/citation.cfm?id=570772 NS-Click original paper]
*** [http://read.cs.ucla.edu/click/nsclick NS-Click webpage]
*** [https://www.pats.ua.ac.be/software/nsmadwifi Integration of ns-2 wireless features and Click]
*** Lalith Suresh P., Ruben Merz, "NS-3-Click: Click Modular Router Integration for NS-3", In Proc. of Workshop on NS-3, Barcelona, Spain, Mar., 2011.

==== TinyOS code execution in ns-3 ====

Mentors: [mailto:marco.miozzo@cttc.es Marco Miozzo] (CTTC), [mailto:nicola.baldo@cttc.es Nicola Baldo] (CTTC), [mailto:nicola.bui@patavinatech.com Nicola Bui] (Patavina Technologies)

* '''TinyOS code execution in ns-3''' TinyOS is one of the most used operating system for wireless sensor networks; however the only tool available for simulating tinyOS code is TOSSIM, which supports the MicaZ platform only. The objective of this project is to allow the execution of TinyOS code within the ns-3 simulator, by simulating the hardware interfaces (radio, timers, etc.) of actual sensor platforms. To achieve this, the student will be asked to develop a phy/mac module that leverage on the Spectrum framework for channel modelling and that offers telosb-like interfaces to TinyOS. For the 2011 GSoC, we propose to focus on telosb hardware, since it is one of the most used research platform and mentors have strong expertise on it. The improvements with respect to TOSSIM are the possibility of testing real sensor application within mixed technology scenarios: i.e.: inter-technology interference in the ISM bands and interoperability (as a possible future extension).
** ''Required Experience:'' ns-3, C++, C, TinyOS
** ''Bonus Experience:'' nesC, telosb
** ''Interests:'' wireless sensor networks
** ''Difficulty:'' High
** ''Recommended reading:''
*** [http://www.tinyos.net/ TinyOS website]
*** [http://docs.tinyos.net/index.php/TinyOS_Tutorials TinyOS tutorials]
*** [http://nescc.sourceforge.net/ nesC]

==== Long Term Evolution networks ====

Mentors: [mailto:peppe@giuseppepiro.com Giuseppe Piro]

* Long Term Evolution represents an emerging and promising technology for providing broadband ubiquitous Internet access. Recently a basic LTE module, which includes both PHY and MAC layers, has been developed for ns-3. However, LTE is a very complex standard, and for this reason at this time it is not possible yet to simulate a complete LTE system. Possible aspects of the LTE networks that can be developed are: periodic and aperiodic CQI feedbacks management, a more complete AMC module, frequency-time correlated channel models for both pedestrian and vehicular environment, PHY error model based on BLER curves, uplink, packet scheduling and other MAC functionalities.
** ''Required experience:'' C++, generic understanding of PHY and MAC layers.
** ''Bonus experience:'' ns-3, LTE.
** ''Interests:'' 4G mobile communications.
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.
** ''Recommended reading''
*** Stefania Sesia, Matthew P. J. Baker, Issam Toufik, "Long Term Evolution: from theory to practice", John Wiley and Sons, 2009
*** Giuseppe Piro, Nicola Baldo, and Marco Miozzo", An LTE module for the ns-3 network simulator", Proc. of Workshop on NS-3, Barcelona, Spain, Mar., 2011.

==== LTE Time Division Duplex (TDD) support ====

Mentors: [mailto:nicola.baldo@cttc.es Nicola Baldo], [mailto:marco.miozzo@cttc.es Marco Miozzo]

* The currently available ns-3 LTE modules supports only the Frequency Division Duplex (FDD) mode of operation. Recently, a lot of interest has emerged for the Time Division Duplex (TDD) operation as well. As part of this project, the student is requested to extend the [http://mailman.isi.edu/pipermail/ns-developers/2011-March/008734.html ns-3 LTE module released by the LENA project] to support TDD. The suggested approach is to:
*** extend the MAC layer to handle the TDD frame structure (i.e., the uplink/downlink/special subframe allocation)
*** extend the PHY layer to support TX/RX in a single frequency band, including also the handling of the special subframe.
** ''Required experience:'' C++
** ''Bonus experience:'' ns-3, 3GPP standards
** ''Interests:'' LTE
** ''Difficulty:'' hard
** ''Recommended reading''
*** 3GPP TS 36.300 EUTRA-EUTRAN Overall Description (in particular Section 5 Physical Layer for E-UTRA)
*** [http://mailman.isi.edu/pipermail/ns-developers/2011-March/008734.html ns-3 LTE module released by the LENA project]
*** [http://www.femtoforum.org/femto/technical.php FemtoForum MAC LTE MAC Scheduler Interface Specification]
*** Stefania Sesia, Matthew P. J. Baker, Issam Toufik, ''Long Term Evolution: from theory to practice'', John Wiley and Sons, 2009

==== LTE Scheduling with the FemtoForum MAC Scheduler API ====

Mentors: [mailto:marco.miozzo@cttc.es Marco Miozzo], [mailto:nicola.baldo@cttc.es Nicola Baldo]

* The [http://mailman.isi.edu/pipermail/ns-developers/2011-March/008734.html ns-3 LTE module released by the LENA project] supports the [http://www.femtoforum.org/femto/technical.php FemtoForum MAC LTE MAC Scheduler Interface Specification] for the implementation of MAC schedulers. Currently, only a simple Round Robin scheduler is supported. As part of this project, the student is requested to implement one or more scheduling algorithms found in the literature on top of the FemtoForum MAC Scheduler API. A few example algorithms are listed below in the references; however, the choice of the algorithm is left to the student. In any case, we stress that the focus of this project should be on the implementation of an alredy defined algorithm (not on the design of a new algorithm).

** ''Required experience:'' C++
** ''Bonus experience:'' ns-3, 3GPP standards
** ''Interests:'' LTE, dynamic packet scheduling, radio resource management
** ''Difficulty:'' hard
** ''Recommended reading''
*** [http://mailman.isi.edu/pipermail/ns-developers/2011-March/008734.html ns-3 LTE module released by the LENA project]
*** [http://www.femtoforum.org/femto/technical.php FemtoForum MAC LTE MAC Scheduler Interface Specification]
*** Stefania Sesia, Matthew P. J. Baker, Issam Toufik, ''Long Term Evolution: from theory to practice'', John Wiley and Sons, 2009
*** B. Sadiq, R. Madan, and A. Sampath, ''Downlink scheduling for multiclass traffic in LTE'', EURASIP Journal on Wireless Communications andNetworking, vol. 2009, Article ID510617, 2009
*** G. Monghal, K. I. Pedersen, I. Z. Kov´acs, and P. E. Mogensen, ''QoS oriented time and frequency domain packet schedulers for the UTRAN long term evolution,'' in Proceedings of the IEEEVehicular Technology Conference (VTC 2008), pp. 2532– 2536, 2008.
*** D. López-Pérez, A. Ladanyi, A. Jüttner, H. Rivano and J. Zhang, ''Optimization Method for the Joint Allocation of Modulation Schemes, Coding Rates, Resource Blocks and Power in Self-Organizing LTE Networks'', IEEE INFOCOM (International Conference on Computer Communications), Shanghai, China, April 2011

==== Model Store ====

Mentors: [mailto:watrous@uw.edu Mitch Watrous]

* '''Model Store.''' The recent ns-3 developers meeting identified a high priority project need to extend the overall build and packaging system for ns-3 to support a user-contributed "model store" inspired by the iPhone App Store. Presently, ns-3 has a monolithic build system and model contributors from outside the project have the choice of trying to integrate their code into the main tree, or else maintaining it (or not) as an independent third-party archive. However, from a maintenance perspective, the project cannot accept maintenance of all contributed models in the long term, and users also do not want to download and build an ever growing code base that may contain many models of no interest to them. Yet we do not want this maintenance and build time bottleneck to stifle user contributions. What we envision is a student project to develop a system and template for future contributors that will allow third-party developers to package, distribute, and update ns-3 protocol models and manage dependencies between models and the core of ns-3.
* ''[[App Store Technical Requirements]]''
* ''Required Experience:'' Python (ns-3 build system is Python-based)
* ''Bonus Experience:'' Packaging frameworks, C++
* ''Interests:'' Build systems, packaging
* ''Difficulty:'' Medium to high
* ''Recommended reading:'' ns-3's waf build system, package management tools, Firefox plugin management, Apple App Store

==== LR-WPAN (IEEE 802.15.4-2006) ====

Mentors: [mailto:tomh@tomh.org Tom Henderson] and [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

* LR-WPAN (802.15.4-2006 standard) is the basis for several low power data networks such as [http://en.wikipedia.org/wiki/6LoWPAN 6LoWPAN] and [http://www.zigbee.org/ ZigBee]. Support for this MAC and PHY is lacking in ns-3. However, a [http://www-ee.ccny.cuny.edu/zheng/pub/index.html comprehensive model] exists for the ns-2 simulator. This project would consist of porting, validating, testing, and documenting the ns-2 LR-WPAN module.
** ''Required experience:'' C++
** ''Bonus experience:'' ns-2, experience with lr-wpan networks
** ''Interests:'' LR-WPAN
** ''Difficulty:'' medium
** ''Recommended reading''
*** http://www-ee.ccny.cuny.edu/zheng/pub/index.html

==== Route visualization and debugging ====

Mentors: [mailto:tomh@tomh.org Tom Henderson]

* One of the most prevalent needs among users is the need to understand what routing is doing in the simulation networks, especially for wireless networks. This proposed project would focus on helper classes and utilities to enable future users to more easily visualize and debug the routing code in ns-3 simulations. For wireless routing, ideas on how to distinguish between propagation-related and protocol-related routing failures would be helpful. Implementing approaches across different routing protocols already available in the simulator (AODV, DSDV, OLSR) is preferred. Some kind of support analogous to the traceroute tool is needed. Having some way to visualize routes taken in the network, such as overlaying route traces on a 2-D node display, would be useful. Tools to allow researchers to collect statistics on routing events in a uniform manner would help future routing research efforts.
* The above list of ideas is somewhat open-ended, so the successful application here will need to clearly state what is being proposed (e.g. example APIs, mock-ups of screenshots), and how it will be scheduled and accomplished within a 10-week project.
** ''Required experience:'' C++
** ''Interests:'' routing protocols
** ''Difficulty:'' medium
** ''Recommended reading''
*** (none yet)

==== Simple wireless models ====

Mentors: [mailto:tomh@tomh.org Tom Henderson]

* ns-3 has support for detailed wireless device models (WiFi, WiMAX) but is missing some basic wireless models that could be used as building blocks for future devices, could be used when simulations call for more abstract representations of wireless networks. These models could also be used in ns-3 courseware for students.
* Some initial capabilities suggested include basic parameterization of link budgets (antenna gain, propagation loss, transmit power, etc.) and BER curves based on modulations selected. At the MAC layer, basic MAC protocols (Aloha, TDMA, CSMA-CA, etc.) could be selected. Handling of interference in a computationally efficient manner is also desirable, both at physical layer and at mac layer (hidden/exposed terminal).
* Validation/testing of these models is a necessary component. It would be preferable for a GSoC project here to not try to shallowly cover all possible wireless models but to perhaps set up a framework for simple wireless and go into more depth on one or more specific models, with testing and validation to back those models up.
** ''Required experience:'' C++, wireless networking
** ''Interests:'' wireless network simulations
** ''Difficulty:'' medium to hard
** ''Recommended reading''
*** The spectrum framework for ns-3 (Baldo et al.)
*** 802.11 Phy validation (Pei et al.)

=== Additional Project Ideas ===
---------

The following are additional project ideas that the ns-3 team has highlighted as important projects to support, and are suggested for students to extend. Not all of them have specific mentors assigned yet but we would seek out mentors from our mentor pool if high quality applications came in on these topics (or any ns-3 topic, for that matter).

<blockquote>

==== General ====

Mentors: WANTED, contact [mailto:boyko@iitp.ru Pavel Boyko]

* '''Failure and Recovery Models'''
** ''Description'': Introduce the concept of node, device and link failure and recovery to NS-3. Implement.
** ''Required Experience:'' C++, basic software architecture, basic UML
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' modelling, software engineering, C++ programming
** ''Difficulty:'' medium, the most difficult part is to define "correct" failure&recovery model

==== Mobility ====

Mentors: WANTED, contact [mailto:boyko@iitp.ru Pavel Boyko]

* '''Coordinate Systems'''
** ''Description'': Introduce the concept of coordinate system to NS-3. Implement [http://en.wikipedia.org/wiki/Geographic_coordinate_system geographic], [http://en.wikipedia.org/wiki/Geocentric_coordinates geocentric] and local Cartesian ([http://en.wikipedia.org/wiki/Map_projection projected]) coordinate systems.
** ''Required Experience:'' C++, basic software architecture, basic UML, basic math
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' software engineering, C++ programming, geographic information systems 
** ''Difficulty:'' easy

Mentors: WANTED, contact [mailto:boyko@iitp.ru Pavel Boyko]

* '''Satellite Mobility Model'''
** ''Description'': Implement LEO/MEO satellite mobility model for NS-3.
** ''Required Experience:'' C++, basic math, orbit mechanics is a plus
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' satellite communications, C++ programming 
** ''Difficulty:'' medium
** ''Reading:'' [http://imj.ucsb.edu/papers/172.pdf A SATELLITE MOBILITY MODEL FOR QUALNET NETWORK SIMULATIONS]
** ''Reading:'' [http://www.isi.edu/nsnam/ns/doc/node197.html ns-2 LEO satellite models]

==== Routing ====

* '''Generalized Router Models/Structure.''' Many simulators, including ns-3, do not provide high fidelity models of Internet routers. For instance, intra-device latencies and input queuing behavior are not modeled. This project would adapt recent results on [http://www.cs.ucsb.edu/~rchertov/papers/infocom08.pdf empirical router testing] to develop a new, more detailed Router node type for ns-3.
** ''Required Experience:''
** ''Bonus Experience:'' Routing architectures, routing protocols, queueing theory, statistics
** ''Interests:'' High fidelity simulation, queueing theory, statistics, data driven model development
** ''Difficulty:'' medium-to-high, because there may be a dependency on Click router

Mentors: WANTED, contact [mailto:aachurin@gmail.com Andrey Churin]

* '''MPLS'''
** ''Description'': Implement basic MPLS + LDP + RSVP stack model.
** ''Required Experience:'' C++
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' MPLS, C++ programming 
** ''Difficulty:'' medium
** ''Reading:'' [http://code.google.com/p/ns3-mpls/source/checkout MPLS+LDP model by Andrey Churin], unfinished. Related RFC.

==== MAC and PHY Models ====

Mentors: [mailto:ruben@net.t-labs.tu-berlin.de Ruben Merz]

* '''CSMA/CD and Aloha'''
** ''Description'': Implement a CSMA/CD MAC protocol. Optionally, implement slotted aloha. A good reference describing the CSMA/CD and aloha protocols as well as basic theoretical results about these protocols is "Computer Networking: A Top-Down Approach.".
** ''Required Experience:'' basic C++, know what aloha and CSMA/CD are.
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' networking, C++ programming 
** ''Difficulty:'' easy
** ''Recommended reading:'' [http://www.scribd.com/doc/5367449/Computer-Networking-A-TopDown-Approach-Featuring-The-Internet-aa Computer Networking: a top down approach], chapter 5.

Mentors: TBD

* '''SNS for ns-3 Wifi.''' [http://www.cs.cornell.edu/people/egs/sns/ Staged Network Simulations (SNS)] is a patch for the ns-2 wireless models which provides for function approximation and caching. That mechanism greatly speeds up the many calculations required in mobile wireless simulations. This project would incorporate those techniques into the ns-3 WiFi model.
** ''Required Experience:''
** ''Bonus Experience:'' Software profiling, software tuning
** ''Interests:'' Approximation, caching, software profiling, high performance computing, scientific computing
** ''Difficulty:'' depends on what functionality the student proposes to implement

==== Applications and Systems ====

* '''Large Scale Topology Generation and Management.''' ns-2 incorporates support for [http://www.isi.edu/nsnam/ns/ns-topogen.html various topology generators], which would be useful to also support in ns-3. This project would investigate porting topology generators or mapping their output to ns-3 simulations. It would also touch on the problem of coherent IP addressing in generated topologies. In particular, [http://www.cs.utah.edu/flux/papers/ipassign-ftn2005-04-base.html recent work] by the Emulab project may be useful in this regard.
** ''Required Experience:''
** ''Bonus Experience:'' Graph theory, network management, Internet topology
** ''Interests:'' Internet topology, Internet autonomous systems, graph theory
** ''Difficulty:'' depends on what functionality the student proposes to implement

Mentors: WANTED, contact [mailto:boyko@iitp.ru Pavel Boyko]

* '''VoIP Toolkit'''
** ''Description'': Implement VoIP quality testing toolkit. Depending on author's skills and resources it can include
*** RTP model + sender and receiver applications measuring delay, jitter, packet loss and [http://www.itu.int/ITU-T/studygroups/com12/emodelv1/index.htm MOS]
*** SIP model measuring [http://en.wikipedia.org/wiki/Call_Setup_Success_Rate call setup success rate], call dropping rate, etc.
*** Application for sending and receiving real audio samples over simulated network to allow subjective QoS estimation
*** Video support
*** etc...
** ''Required Experience:'' C++, basic VoIP understanding
** ''Bonus Experience:'' ns-3 programming, contributions to open source projects.
** ''Interests:'' VoIP, software engineering, C++ programming 
** ''Difficulty:'' medium

* '''SNMP Agent'''
** ''Description'': Implement SNMP agent inside ns-3 to allow monitor, visualize and control simulated network using any available SNMP manager
** ''Required Experience:'' C++, basic SNMP understanding
** ''Bonus Experience:'' fun, ns-3 programming, contributions to open source projects.
** ''Interests:'' Network management, SNMP, C++ programming 
** ''Difficulty:'' medium

</blockquote>

[[Category:GSoC]]