https://www.nsnam.org/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Sderonne 2026-05-02T11:45:57Z User contributions MediaWiki 1.39.8 https://www.nsnam.org/mediawiki/index.php?title=GSOC2020Projects&diff=11824 2020-01-21T20:44:56Z

<p>Sderonne: /* Wi-Fi code refactoring to facilitate integration of other 802.11 based standards */</p> <hr /> <div>{{TOC}}<br /> <br /> This page contains 2020 Google Summer of Code project ideas for ns-3. <br /> <br /> '''Note:''' ns-3 will apply to Google Summer of Code on February 5 and will be notified about acceptance on February 27.'''<br /> <br /> <br /> * [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC Frequently Asked Questions]<br /> * [[GSOC2019StudentGuide |ns-3's 2019 GSoC Student guide]] (will update to 2020 if we are selected)<br /> * [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide (not ns-3 specific)]<br /> * [[GSOC2019StudentApplicationTemplate |2020 GSoC Student application template]] (will update for 2020 if we are selected)<br /> * [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]<br /> * [http://en.flossmanuals.net/gsoc-mentoring/ GSoC Mentor guide (not ns-3 specific)]<br /> * [[GSOCSelectionProcess | GSoC Student Selection Process]]<br /> * ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''chat'' https://ns-3.zulipchat.com/<br /> <br /> === About the ns-3 project ===<br /> <br /> ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.<br /> <br /> 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.<br /> <br /> ns-3 has participated in past GSoCs during 2008-10, 2012-15, and 2017-19. We seek students interested in the intersection of wireless and computer networking, performance analysis, and open source software.<br /> <br /> === Org admins ===<br /> <br /> Google Summer of Code organizational admins for ns-3 are [mailto:tpecorella@mac.com Tommaso Pecorella] and [mailto:tomh@tomh.org Tom Henderson]; contact them with any questions. They also hang out on [https://ns-3.zulipchat.com Zulip].<br /> <br /> === Mentors ===<br /> <br /> 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 or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge. In 2020, we are going to be seeking two-person or multiple-person mentoring teams for projects, to help with the mentoring workload and bring more expertise.<br /> <br /> The current list of prospective mentors for 2020 will be announced here if/when we are selected for the program.<br /> <br /> === Students: how to participate ===<br /> <br /> For students interested in applying to ns-3 for GSOC, please go through the following list to get started:<br /> * Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].<br /> * Read [[GSOC2019StudentGuide |ns-3's GSoC Student guide]] (will be updated for 2020 if selected)<br /> * Look through our [[#Project Ideas]] below to see if you find a project that interests you.<br /> * Review the [http://www.nsnam.org/ns-3-30/documentation ns-3 tutorial] thoroughly, if you have not already done so.<br /> * Once it is posted, look through the [[GSOC2019StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.<br /> * Next, proceed to get in touch with the developers on the mailing list and refine your proposal.<br /> * In parallel, make sure you prepare a patch as per the patch requirement guidelines (to be posted at a later date). Your application to ns-3 will not be considered if you do not fulfill this requirement.<br /> <br /> Below is a list of [[#Project Ideas]] proposed by the ns-3 team for Google Summer of Code 2020. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the proposal it will develop into, and the higher your chances of being accepted into the programme.<br /> <br /> &lt;blockquote&gt;<br /> Each project idea within a particular priority has been tagged with the following properties:<br /> * ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.<br /> * ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.<br /> * ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.<br /> * ''Difficulty:'' easy, medium or difficult<br /> * ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.<br /> <br /> 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.<br /> &lt;/blockquote&gt;<br /> <br /> === Mentors: how to participate ===<br /> <br /> The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:<br /> <br /> * 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.<br /> * 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.<br /> * 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 to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.<br /> <br /> == Project Ideas ==<br /> <br /> '''Note to students:''' These ideas are not listed in any priority order. <br /> <br /> ==== Migrate contributed code to apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> A large amount of ns-3 code exists out of the mainline and falls out of date. This project would aim to update, finish off, and publish as many apps as possible to the [https://apps.nsnam.org ns-3 App Store]. The student will also be responsible for writing test scripts to test daily that compatibility of apps with the ns-3 mainline is not broken. A list of potential modules will be provided below:<br /> * [https://gitlab.com/tomhenderson/ns-3-ee-595/tree/course/contrib/simple-wireless Simple wireless]<br /> * 802.11ah<br /> * WiGig<br /> * Others TBD<br /> <br /> ==== Usability improvements ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson], others TBD<br /> <br /> Usability of ns-3 can always be improved, whether it is help with building simulations, running simulation campaigns, using the ns-3 C++ API, improving the Python user experience, visualizing simulations or data, software packaging (e.g. binary packages or Docker containers), or documentation. This project is for a student who has been using ns-3 for a while and has ideas on how to make it better during GSoC. We don't want to limit the scope of proposals here; we will consider any project ideas that improve ns-3 usability in some way (please explain to us why the usability improvement is important to users beyond yourself, and why you would argue for your particular solution, and of course describe how you plan to get it done during the timeframe of GSoC). Some possible project examples:<br /> * Tools and scripts to conduct and manage data from a large number of simulation runs<br /> * How to integrate a more Python-centric data flow and tools, such as [http://jupyter.org/ Jupyter Notebook] and [https://github.com/bloomberg/bqplot bqplot]<br /> * Internal state visualization of Wi-Fi or LTE, such as the kind of plots generated by [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.3791&amp;rep=rep1&amp;type=pdf Yavista]<br /> <br /> ==== User-friendly internet-apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> Ping is a ubiquitous application for reachability and latency measurements. ns-3 already has a ping model (the v4ping.cc and ping6.cc). However, a user-friendly API could still be added. It is not straightforward to configure an ns-3 program to do in a single statement, for example, &quot;Ping the IP address W.X.Y.Z from node 0 between times 5 and 50 seconds in my program, and save the output in traditional format to the file &lt;filename.txt&gt;&quot;, or to configure the many options found in the ping man page. This project is therefore not about developing brand new features as much as it is about making ping super-easy to use with a great API. Have a look at how ns-3 programs are written, and tell us what kind of API makes sense to you, and why, and how you would go about prioritizing its implementation. If ping is solved very early, the project can follow the same pattern for one or two more applications (e.g. netperf, iperf, etc.). <br /> <br /> * ''Required Experience:''C++<br /> * ''Interests:'' Network performance management<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> <br /> ==== nam upgrade and support for ns-3 ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [http://www.isi.edu/nsnam/nam/ nam] is a Tcl/Tk-based animator for ns-2. Some example videos are found at [https://www.youtube.com/results?search_query=nam+network+animator YouTube]. nam has been functionally replaced in many ways by [https://www.nsnam.org/wiki/NetAnim NetAnim], but it still has some attractive features and might make a complementary animation tool for ns-3. In fact, someone did a proof-of-concept support of nam for ns-3 many years ago: http://www.nsnam.org/contributed/ns-3-nam.tar.bz2. This project would involve upgrading nam support to the latest Tcl/Tk release series (8.6) and then using the existing ns-3 trace system to generate nam output files such as in ns-2, and documenting and testing the results, including some demonstration videos. <br /> <br /> * ''Required Experience:''C++, Tcl/Tk also preferred<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** the links listed above<br /> <br /> ==== NetAnim Python and examples ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [[NetAnim]] is an optional animator for ns-3. It has not been actively developed for a few years. It is written using Qt libraries, and works in an offline mode, meaning that the simulation run outputs a detailed animation trace file that is later imported into NetAnim to visualize the simulation. NetAnim is presently underutilized because of lack of documentation on many features and lack of examples/tutorials around its use. Python bindings for the animator are also not supported. We would be interested in a student who would focus a project around improving the usability, documentation, and examples around NetAnim.<br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' Python, Qt<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** https://www.nsnam.org/wiki/NetAnim<br /> ** https://www.qt.io/what-is-qt/<br /> ** https://www.nsnam.org/docs/release/3.29/manual/html/python.html#working-with-python-bindings<br /> <br /> ==== BPF support ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [https://lwn.net/ml/netdev/20191214004753.1653075-1-kafai@fb.com/ BPF] is a current networking implementation trend. What would it take to support BPF programs in ns-3? What are the use cases of interest?<br /> <br /> * ''Required Experience:''C++, C<br /> * ''Recommended Experience:'' BPF, Linux kernel<br /> * ''Interests:'' protocol implementation<br /> * ''Difficulty:'' Medium to hard?<br /> * ''Recommended reading:''<br /> ** https://lwn.net/Articles/740157/<br /> <br /> ==== Wi-Fi code refactoring to facilitate integration of other 802.11 based standards ====<br /> <br /> Mentors: [mailto:sebastien.deronne@gmail.com Sébastien Deronne] [mailto:hany.assasa@gmail.com Hany Assasa]<br /> <br /> Besides the commercial 802.11 standards (11b, 11a, 11g, 11n, 11ac &amp; 11ax) that have been implemented in mainstream ns-3 versions, some other modules have been developed to implement &quot;non-commercial&quot; 802.11 amendments, such as 802.11ah and 802.11ad/ay (Wigig), which exist in separate repositories. Since these make use of some common code from the wifi module, developers of these other modules implement their own models on top of the existing wifi model, which result in a very large amount of code in the same module. furthermore, this makes this code very difficult to maintain due to a lot of merge conflicts each time changes have been done in the mainline wifi. A much better approach would be to refactor the wifi module, so that common functionalities can be used from separate modules (802.11h, Wigig, ...) that would later be available in the ns-3 App Store and could be easily plugged in. The goal of this project is to identify a good approach to refactor the wifi module and start its implementation. <br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' 802.11 (Wi-Fi)<br /> * ''Interests:'' Code refactoring<br /> * ''Difficulty:'' Medium to hard<br /> * ''Recommended reading:''<br /> <br /> Wigig: https://github.com/wigig-tools/ns3-802.11ad<br /> <br /> 802.11ah: https://github.com/imec-idlab/IEEE-802.11ah-ns-3<br /> <br /> [[Category:GSoC]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=GSOC2020Projects&diff=11823 2020-01-15T20:25:17Z

<p>Sderonne: /* Wi-Fi code refactoring to facilitate integration of other 802.11 based standards */</p> <hr /> <div>{{TOC}}<br /> <br /> This page contains 2020 Google Summer of Code project ideas for ns-3. <br /> <br /> '''Note:''' ns-3 will apply to Google Summer of Code on February 5 and will be notified about acceptance on February 27.'''<br /> <br /> <br /> * [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC Frequently Asked Questions]<br /> * [[GSOC2019StudentGuide |ns-3's 2019 GSoC Student guide]] (will update to 2020 if we are selected)<br /> * [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide (not ns-3 specific)]<br /> * [[GSOC2019StudentApplicationTemplate |2020 GSoC Student application template]] (will update for 2020 if we are selected)<br /> * [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]<br /> * [http://en.flossmanuals.net/gsoc-mentoring/ GSoC Mentor guide (not ns-3 specific)]<br /> * [[GSOCSelectionProcess | GSoC Student Selection Process]]<br /> * ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''chat'' https://ns-3.zulipchat.com/<br /> <br /> === About the ns-3 project ===<br /> <br /> ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.<br /> <br /> 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.<br /> <br /> ns-3 has participated in past GSoCs during 2008-10, 2012-15, and 2017-19. We seek students interested in the intersection of wireless and computer networking, performance analysis, and open source software.<br /> <br /> === Org admins ===<br /> <br /> Google Summer of Code organizational admins for ns-3 are [mailto:tpecorella@mac.com Tommaso Pecorella] and [mailto:tomh@tomh.org Tom Henderson]; contact them with any questions. They also hang out on [https://ns-3.zulipchat.com Zulip].<br /> <br /> === Mentors ===<br /> <br /> 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 or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge. In 2020, we are going to be seeking two-person or multiple-person mentoring teams for projects, to help with the mentoring workload and bring more expertise.<br /> <br /> The current list of prospective mentors for 2020 will be announced here if/when we are selected for the program.<br /> <br /> === Students: how to participate ===<br /> <br /> For students interested in applying to ns-3 for GSOC, please go through the following list to get started:<br /> * Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].<br /> * Read [[GSOC2019StudentGuide |ns-3's GSoC Student guide]] (will be updated for 2020 if selected)<br /> * Look through our [[#Project Ideas]] below to see if you find a project that interests you.<br /> * Review the [http://www.nsnam.org/ns-3-30/documentation ns-3 tutorial] thoroughly, if you have not already done so.<br /> * Once it is posted, look through the [[GSOC2019StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.<br /> * Next, proceed to get in touch with the developers on the mailing list and refine your proposal.<br /> * In parallel, make sure you prepare a patch as per the patch requirement guidelines (to be posted at a later date). Your application to ns-3 will not be considered if you do not fulfill this requirement.<br /> <br /> Below is a list of [[#Project Ideas]] proposed by the ns-3 team for Google Summer of Code 2020. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the proposal it will develop into, and the higher your chances of being accepted into the programme.<br /> <br /> &lt;blockquote&gt;<br /> Each project idea within a particular priority has been tagged with the following properties:<br /> * ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.<br /> * ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.<br /> * ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.<br /> * ''Difficulty:'' easy, medium or difficult<br /> * ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.<br /> <br /> 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.<br /> &lt;/blockquote&gt;<br /> <br /> === Mentors: how to participate ===<br /> <br /> The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:<br /> <br /> * 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.<br /> * 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.<br /> * 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 to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.<br /> <br /> == Project Ideas ==<br /> <br /> '''Note to students:''' These ideas are not listed in any priority order. <br /> <br /> ==== Migrate contributed code to apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> A large amount of ns-3 code exists out of the mainline and falls out of date. This project would aim to update, finish off, and publish as many apps as possible to the [https://apps.nsnam.org ns-3 App Store]. The student will also be responsible for writing test scripts to test daily that compatibility of apps with the ns-3 mainline is not broken. A list of potential modules will be provided below:<br /> * [https://gitlab.com/tomhenderson/ns-3-ee-595/tree/course/contrib/simple-wireless Simple wireless]<br /> * 802.11ah<br /> * WiGig<br /> * Others TBD<br /> <br /> ==== Usability improvements ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson], others TBD<br /> <br /> Usability of ns-3 can always be improved, whether it is help with building simulations, running simulation campaigns, using the ns-3 C++ API, improving the Python user experience, visualizing simulations or data, software packaging (e.g. binary packages or Docker containers), or documentation. This project is for a student who has been using ns-3 for a while and has ideas on how to make it better during GSoC. We don't want to limit the scope of proposals here; we will consider any project ideas that improve ns-3 usability in some way (please explain to us why the usability improvement is important to users beyond yourself, and why you would argue for your particular solution, and of course describe how you plan to get it done during the timeframe of GSoC). Some possible project examples:<br /> * Tools and scripts to conduct and manage data from a large number of simulation runs<br /> * How to integrate a more Python-centric data flow and tools, such as [http://jupyter.org/ Jupyter Notebook] and [https://github.com/bloomberg/bqplot bqplot]<br /> * Internal state visualization of Wi-Fi or LTE, such as the kind of plots generated by [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.3791&amp;rep=rep1&amp;type=pdf Yavista]<br /> <br /> ==== User-friendly internet-apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> Ping is a ubiquitous application for reachability and latency measurements. ns-3 already has a ping model (the v4ping.cc and ping6.cc). However, a user-friendly API could still be added. It is not straightforward to configure an ns-3 program to do in a single statement, for example, &quot;Ping the IP address W.X.Y.Z from node 0 between times 5 and 50 seconds in my program, and save the output in traditional format to the file &lt;filename.txt&gt;&quot;, or to configure the many options found in the ping man page. This project is therefore not about developing brand new features as much as it is about making ping super-easy to use with a great API. Have a look at how ns-3 programs are written, and tell us what kind of API makes sense to you, and why, and how you would go about prioritizing its implementation. If ping is solved very early, the project can follow the same pattern for one or two more applications (e.g. netperf, iperf, etc.). <br /> <br /> * ''Required Experience:''C++<br /> * ''Interests:'' Network performance management<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> <br /> ==== nam upgrade and support for ns-3 ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [http://www.isi.edu/nsnam/nam/ nam] is a Tcl/Tk-based animator for ns-2. Some example videos are found at [https://www.youtube.com/results?search_query=nam+network+animator YouTube]. nam has been functionally replaced in many ways by [https://www.nsnam.org/wiki/NetAnim NetAnim], but it still has some attractive features and might make a complementary animation tool for ns-3. In fact, someone did a proof-of-concept support of nam for ns-3 many years ago: http://www.nsnam.org/contributed/ns-3-nam.tar.bz2. This project would involve upgrading nam support to the latest Tcl/Tk release series (8.6) and then using the existing ns-3 trace system to generate nam output files such as in ns-2, and documenting and testing the results, including some demonstration videos. <br /> <br /> * ''Required Experience:''C++, Tcl/Tk also preferred<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** the links listed above<br /> <br /> ==== NetAnim Python and examples ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [[NetAnim]] is an optional animator for ns-3. It has not been actively developed for a few years. It is written using Qt libraries, and works in an offline mode, meaning that the simulation run outputs a detailed animation trace file that is later imported into NetAnim to visualize the simulation. NetAnim is presently underutilized because of lack of documentation on many features and lack of examples/tutorials around its use. Python bindings for the animator are also not supported. We would be interested in a student who would focus a project around improving the usability, documentation, and examples around NetAnim.<br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' Python, Qt<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** https://www.nsnam.org/wiki/NetAnim<br /> ** https://www.qt.io/what-is-qt/<br /> ** https://www.nsnam.org/docs/release/3.29/manual/html/python.html#working-with-python-bindings<br /> <br /> ==== BPF support ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [https://lwn.net/ml/netdev/20191214004753.1653075-1-kafai@fb.com/ BPF] is a current networking implementation trend. What would it take to support BPF programs in ns-3? What are the use cases of interest?<br /> <br /> * ''Required Experience:''C++, C<br /> * ''Recommended Experience:'' BPF, Linux kernel<br /> * ''Interests:'' protocol implementation<br /> * ''Difficulty:'' Medium to hard?<br /> * ''Recommended reading:''<br /> ** https://lwn.net/Articles/740157/<br /> <br /> ==== Wi-Fi code refactoring to facilitate integration of other 802.11 based standards ====<br /> <br /> Mentors: [mailto:sebastien.deronne@gmail.com Sébastien Deronne]<br /> <br /> Besides the commercial 802.11 standards (11b, 11a, 11g, 11n, 11ac &amp; 11ax) that have been implemented in mainstream ns-3 versions, some other modules have been developed to implement &quot;non-commercial&quot; 802.11 amendments, such as 802.11ah and 802.11ad/ay (Wigig), which exist in separate repositories. Since these make use of some common code from the wifi module, developers of these other modules implement their own models on top of the existing wifi model, which result in a very large amount of code in the same module. furthermore, this makes this code very difficult to maintain due to a lot of merge conflicts each time changes have been done in the mainline wifi. A much better approach would be to refactor the wifi module, so that common functionalities can be used from separate modules (802.11h, Wigig, ...) that would later be available in the ns-3 App Store and could be easily plugged in. The goal of this project is to identify a good approach to refactor the wifi module and start its implementation. <br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' 802.11 (Wi-Fi)<br /> * ''Interests:'' Code refactoring<br /> * ''Difficulty:'' Medium to hard<br /> * ''Recommended reading:''<br /> <br /> [[Category:GSoC]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=GSOC2020Projects&diff=11822 2020-01-15T20:19:10Z

<p>Sderonne: /* Wi-Fi code refactoring to facilitate integration of other 802.11 based standards */</p> <hr /> <div>{{TOC}}<br /> <br /> This page contains 2020 Google Summer of Code project ideas for ns-3. <br /> <br /> '''Note:''' ns-3 will apply to Google Summer of Code on February 5 and will be notified about acceptance on February 27.'''<br /> <br /> <br /> * [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC Frequently Asked Questions]<br /> * [[GSOC2019StudentGuide |ns-3's 2019 GSoC Student guide]] (will update to 2020 if we are selected)<br /> * [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide (not ns-3 specific)]<br /> * [[GSOC2019StudentApplicationTemplate |2020 GSoC Student application template]] (will update for 2020 if we are selected)<br /> * [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]<br /> * [http://en.flossmanuals.net/gsoc-mentoring/ GSoC Mentor guide (not ns-3 specific)]<br /> * [[GSOCSelectionProcess | GSoC Student Selection Process]]<br /> * ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''chat'' https://ns-3.zulipchat.com/<br /> <br /> === About the ns-3 project ===<br /> <br /> ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.<br /> <br /> 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.<br /> <br /> ns-3 has participated in past GSoCs during 2008-10, 2012-15, and 2017-19. We seek students interested in the intersection of wireless and computer networking, performance analysis, and open source software.<br /> <br /> === Org admins ===<br /> <br /> Google Summer of Code organizational admins for ns-3 are [mailto:tpecorella@mac.com Tommaso Pecorella] and [mailto:tomh@tomh.org Tom Henderson]; contact them with any questions. They also hang out on [https://ns-3.zulipchat.com Zulip].<br /> <br /> === Mentors ===<br /> <br /> 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 or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge. In 2020, we are going to be seeking two-person or multiple-person mentoring teams for projects, to help with the mentoring workload and bring more expertise.<br /> <br /> The current list of prospective mentors for 2020 will be announced here if/when we are selected for the program.<br /> <br /> === Students: how to participate ===<br /> <br /> For students interested in applying to ns-3 for GSOC, please go through the following list to get started:<br /> * Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].<br /> * Read [[GSOC2019StudentGuide |ns-3's GSoC Student guide]] (will be updated for 2020 if selected)<br /> * Look through our [[#Project Ideas]] below to see if you find a project that interests you.<br /> * Review the [http://www.nsnam.org/ns-3-30/documentation ns-3 tutorial] thoroughly, if you have not already done so.<br /> * Once it is posted, look through the [[GSOC2019StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.<br /> * Next, proceed to get in touch with the developers on the mailing list and refine your proposal.<br /> * In parallel, make sure you prepare a patch as per the patch requirement guidelines (to be posted at a later date). Your application to ns-3 will not be considered if you do not fulfill this requirement.<br /> <br /> Below is a list of [[#Project Ideas]] proposed by the ns-3 team for Google Summer of Code 2020. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the proposal it will develop into, and the higher your chances of being accepted into the programme.<br /> <br /> &lt;blockquote&gt;<br /> Each project idea within a particular priority has been tagged with the following properties:<br /> * ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.<br /> * ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.<br /> * ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.<br /> * ''Difficulty:'' easy, medium or difficult<br /> * ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.<br /> <br /> 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.<br /> &lt;/blockquote&gt;<br /> <br /> === Mentors: how to participate ===<br /> <br /> The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:<br /> <br /> * 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.<br /> * 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.<br /> * 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 to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.<br /> <br /> == Project Ideas ==<br /> <br /> '''Note to students:''' These ideas are not listed in any priority order. <br /> <br /> ==== Migrate contributed code to apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> A large amount of ns-3 code exists out of the mainline and falls out of date. This project would aim to update, finish off, and publish as many apps as possible to the [https://apps.nsnam.org ns-3 App Store]. The student will also be responsible for writing test scripts to test daily that compatibility of apps with the ns-3 mainline is not broken. A list of potential modules will be provided below:<br /> * [https://gitlab.com/tomhenderson/ns-3-ee-595/tree/course/contrib/simple-wireless Simple wireless]<br /> * 802.11ah<br /> * WiGig<br /> * Others TBD<br /> <br /> ==== Usability improvements ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson], others TBD<br /> <br /> Usability of ns-3 can always be improved, whether it is help with building simulations, running simulation campaigns, using the ns-3 C++ API, improving the Python user experience, visualizing simulations or data, software packaging (e.g. binary packages or Docker containers), or documentation. This project is for a student who has been using ns-3 for a while and has ideas on how to make it better during GSoC. We don't want to limit the scope of proposals here; we will consider any project ideas that improve ns-3 usability in some way (please explain to us why the usability improvement is important to users beyond yourself, and why you would argue for your particular solution, and of course describe how you plan to get it done during the timeframe of GSoC). Some possible project examples:<br /> * Tools and scripts to conduct and manage data from a large number of simulation runs<br /> * How to integrate a more Python-centric data flow and tools, such as [http://jupyter.org/ Jupyter Notebook] and [https://github.com/bloomberg/bqplot bqplot]<br /> * Internal state visualization of Wi-Fi or LTE, such as the kind of plots generated by [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.3791&amp;rep=rep1&amp;type=pdf Yavista]<br /> <br /> ==== User-friendly internet-apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> Ping is a ubiquitous application for reachability and latency measurements. ns-3 already has a ping model (the v4ping.cc and ping6.cc). However, a user-friendly API could still be added. It is not straightforward to configure an ns-3 program to do in a single statement, for example, &quot;Ping the IP address W.X.Y.Z from node 0 between times 5 and 50 seconds in my program, and save the output in traditional format to the file &lt;filename.txt&gt;&quot;, or to configure the many options found in the ping man page. This project is therefore not about developing brand new features as much as it is about making ping super-easy to use with a great API. Have a look at how ns-3 programs are written, and tell us what kind of API makes sense to you, and why, and how you would go about prioritizing its implementation. If ping is solved very early, the project can follow the same pattern for one or two more applications (e.g. netperf, iperf, etc.). <br /> <br /> * ''Required Experience:''C++<br /> * ''Interests:'' Network performance management<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> <br /> ==== nam upgrade and support for ns-3 ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [http://www.isi.edu/nsnam/nam/ nam] is a Tcl/Tk-based animator for ns-2. Some example videos are found at [https://www.youtube.com/results?search_query=nam+network+animator YouTube]. nam has been functionally replaced in many ways by [https://www.nsnam.org/wiki/NetAnim NetAnim], but it still has some attractive features and might make a complementary animation tool for ns-3. In fact, someone did a proof-of-concept support of nam for ns-3 many years ago: http://www.nsnam.org/contributed/ns-3-nam.tar.bz2. This project would involve upgrading nam support to the latest Tcl/Tk release series (8.6) and then using the existing ns-3 trace system to generate nam output files such as in ns-2, and documenting and testing the results, including some demonstration videos. <br /> <br /> * ''Required Experience:''C++, Tcl/Tk also preferred<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** the links listed above<br /> <br /> ==== NetAnim Python and examples ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [[NetAnim]] is an optional animator for ns-3. It has not been actively developed for a few years. It is written using Qt libraries, and works in an offline mode, meaning that the simulation run outputs a detailed animation trace file that is later imported into NetAnim to visualize the simulation. NetAnim is presently underutilized because of lack of documentation on many features and lack of examples/tutorials around its use. Python bindings for the animator are also not supported. We would be interested in a student who would focus a project around improving the usability, documentation, and examples around NetAnim.<br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' Python, Qt<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** https://www.nsnam.org/wiki/NetAnim<br /> ** https://www.qt.io/what-is-qt/<br /> ** https://www.nsnam.org/docs/release/3.29/manual/html/python.html#working-with-python-bindings<br /> <br /> ==== BPF support ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [https://lwn.net/ml/netdev/20191214004753.1653075-1-kafai@fb.com/ BPF] is a current networking implementation trend. What would it take to support BPF programs in ns-3? What are the use cases of interest?<br /> <br /> * ''Required Experience:''C++, C<br /> * ''Recommended Experience:'' BPF, Linux kernel<br /> * ''Interests:'' protocol implementation<br /> * ''Difficulty:'' Medium to hard?<br /> * ''Recommended reading:''<br /> ** https://lwn.net/Articles/740157/<br /> <br /> ==== Wi-Fi code refactoring to facilitate integration of other 802.11 based standards ====<br /> <br /> Mentors: [mailto:sebastien.deronne@gmail.com Sébastien Deronne]<br /> <br /> Besides the commercial 802.11 standards (11b, 11a, 11g, 11n, 11ac &amp; 11ax) that have been implemented in mainstream ns-3 versions, some other modules have been developed to implement &quot;non-commercial&quot; 802.11 amendments, such as 802.11ah and 802.11ad/ay (Wigig).<br /> Since these make use of some common code from the wifi module, developers of these other modules implement their own models on top of the existing wifi model, which result in a very large amount of code in the same module. furthermore, this makes this code very difficult to maintain due to a lot of merge conflicts each time changes have been done in the mainline wifi. A much better approach would be to refactor the wifi module, so that common functionalities can be used from separate modules (802.11h, Wigig, ...) that would later be available in the ns-3 App Store and could be easily plugged in. The goal of this project is to identify a good approach to refactor the wifi module and start its implementation. <br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' 802.11 (Wi-Fi)<br /> * ''Interests:'' Code refactoring<br /> * ''Difficulty:'' Medium to hard<br /> * ''Recommended reading:''<br /> <br /> [[Category:GSoC]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=GSOC2020Projects&diff=11821 2020-01-15T20:18:42Z

<p>Sderonne: /* Wi-Fi code refactoring to facilitate integration of other 802.11 based standards */</p> <hr /> <div>{{TOC}}<br /> <br /> This page contains 2020 Google Summer of Code project ideas for ns-3. <br /> <br /> '''Note:''' ns-3 will apply to Google Summer of Code on February 5 and will be notified about acceptance on February 27.'''<br /> <br /> <br /> * [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC Frequently Asked Questions]<br /> * [[GSOC2019StudentGuide |ns-3's 2019 GSoC Student guide]] (will update to 2020 if we are selected)<br /> * [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide (not ns-3 specific)]<br /> * [[GSOC2019StudentApplicationTemplate |2020 GSoC Student application template]] (will update for 2020 if we are selected)<br /> * [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]<br /> * [http://en.flossmanuals.net/gsoc-mentoring/ GSoC Mentor guide (not ns-3 specific)]<br /> * [[GSOCSelectionProcess | GSoC Student Selection Process]]<br /> * ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''chat'' https://ns-3.zulipchat.com/<br /> <br /> === About the ns-3 project ===<br /> <br /> ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.<br /> <br /> 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.<br /> <br /> ns-3 has participated in past GSoCs during 2008-10, 2012-15, and 2017-19. We seek students interested in the intersection of wireless and computer networking, performance analysis, and open source software.<br /> <br /> === Org admins ===<br /> <br /> Google Summer of Code organizational admins for ns-3 are [mailto:tpecorella@mac.com Tommaso Pecorella] and [mailto:tomh@tomh.org Tom Henderson]; contact them with any questions. They also hang out on [https://ns-3.zulipchat.com Zulip].<br /> <br /> === Mentors ===<br /> <br /> 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 or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge. In 2020, we are going to be seeking two-person or multiple-person mentoring teams for projects, to help with the mentoring workload and bring more expertise.<br /> <br /> The current list of prospective mentors for 2020 will be announced here if/when we are selected for the program.<br /> <br /> === Students: how to participate ===<br /> <br /> For students interested in applying to ns-3 for GSOC, please go through the following list to get started:<br /> * Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].<br /> * Read [[GSOC2019StudentGuide |ns-3's GSoC Student guide]] (will be updated for 2020 if selected)<br /> * Look through our [[#Project Ideas]] below to see if you find a project that interests you.<br /> * Review the [http://www.nsnam.org/ns-3-30/documentation ns-3 tutorial] thoroughly, if you have not already done so.<br /> * Once it is posted, look through the [[GSOC2019StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.<br /> * Next, proceed to get in touch with the developers on the mailing list and refine your proposal.<br /> * In parallel, make sure you prepare a patch as per the patch requirement guidelines (to be posted at a later date). Your application to ns-3 will not be considered if you do not fulfill this requirement.<br /> <br /> Below is a list of [[#Project Ideas]] proposed by the ns-3 team for Google Summer of Code 2020. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the proposal it will develop into, and the higher your chances of being accepted into the programme.<br /> <br /> &lt;blockquote&gt;<br /> Each project idea within a particular priority has been tagged with the following properties:<br /> * ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.<br /> * ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.<br /> * ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.<br /> * ''Difficulty:'' easy, medium or difficult<br /> * ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.<br /> <br /> 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.<br /> &lt;/blockquote&gt;<br /> <br /> === Mentors: how to participate ===<br /> <br /> The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:<br /> <br /> * 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.<br /> * 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.<br /> * 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 to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.<br /> <br /> == Project Ideas ==<br /> <br /> '''Note to students:''' These ideas are not listed in any priority order. <br /> <br /> ==== Migrate contributed code to apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> A large amount of ns-3 code exists out of the mainline and falls out of date. This project would aim to update, finish off, and publish as many apps as possible to the [https://apps.nsnam.org ns-3 App Store]. The student will also be responsible for writing test scripts to test daily that compatibility of apps with the ns-3 mainline is not broken. A list of potential modules will be provided below:<br /> * [https://gitlab.com/tomhenderson/ns-3-ee-595/tree/course/contrib/simple-wireless Simple wireless]<br /> * 802.11ah<br /> * WiGig<br /> * Others TBD<br /> <br /> ==== Usability improvements ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson], others TBD<br /> <br /> Usability of ns-3 can always be improved, whether it is help with building simulations, running simulation campaigns, using the ns-3 C++ API, improving the Python user experience, visualizing simulations or data, software packaging (e.g. binary packages or Docker containers), or documentation. This project is for a student who has been using ns-3 for a while and has ideas on how to make it better during GSoC. We don't want to limit the scope of proposals here; we will consider any project ideas that improve ns-3 usability in some way (please explain to us why the usability improvement is important to users beyond yourself, and why you would argue for your particular solution, and of course describe how you plan to get it done during the timeframe of GSoC). Some possible project examples:<br /> * Tools and scripts to conduct and manage data from a large number of simulation runs<br /> * How to integrate a more Python-centric data flow and tools, such as [http://jupyter.org/ Jupyter Notebook] and [https://github.com/bloomberg/bqplot bqplot]<br /> * Internal state visualization of Wi-Fi or LTE, such as the kind of plots generated by [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.3791&amp;rep=rep1&amp;type=pdf Yavista]<br /> <br /> ==== User-friendly internet-apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> Ping is a ubiquitous application for reachability and latency measurements. ns-3 already has a ping model (the v4ping.cc and ping6.cc). However, a user-friendly API could still be added. It is not straightforward to configure an ns-3 program to do in a single statement, for example, &quot;Ping the IP address W.X.Y.Z from node 0 between times 5 and 50 seconds in my program, and save the output in traditional format to the file &lt;filename.txt&gt;&quot;, or to configure the many options found in the ping man page. This project is therefore not about developing brand new features as much as it is about making ping super-easy to use with a great API. Have a look at how ns-3 programs are written, and tell us what kind of API makes sense to you, and why, and how you would go about prioritizing its implementation. If ping is solved very early, the project can follow the same pattern for one or two more applications (e.g. netperf, iperf, etc.). <br /> <br /> * ''Required Experience:''C++<br /> * ''Interests:'' Network performance management<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> <br /> ==== nam upgrade and support for ns-3 ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [http://www.isi.edu/nsnam/nam/ nam] is a Tcl/Tk-based animator for ns-2. Some example videos are found at [https://www.youtube.com/results?search_query=nam+network+animator YouTube]. nam has been functionally replaced in many ways by [https://www.nsnam.org/wiki/NetAnim NetAnim], but it still has some attractive features and might make a complementary animation tool for ns-3. In fact, someone did a proof-of-concept support of nam for ns-3 many years ago: http://www.nsnam.org/contributed/ns-3-nam.tar.bz2. This project would involve upgrading nam support to the latest Tcl/Tk release series (8.6) and then using the existing ns-3 trace system to generate nam output files such as in ns-2, and documenting and testing the results, including some demonstration videos. <br /> <br /> * ''Required Experience:''C++, Tcl/Tk also preferred<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** the links listed above<br /> <br /> ==== NetAnim Python and examples ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [[NetAnim]] is an optional animator for ns-3. It has not been actively developed for a few years. It is written using Qt libraries, and works in an offline mode, meaning that the simulation run outputs a detailed animation trace file that is later imported into NetAnim to visualize the simulation. NetAnim is presently underutilized because of lack of documentation on many features and lack of examples/tutorials around its use. Python bindings for the animator are also not supported. We would be interested in a student who would focus a project around improving the usability, documentation, and examples around NetAnim.<br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' Python, Qt<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** https://www.nsnam.org/wiki/NetAnim<br /> ** https://www.qt.io/what-is-qt/<br /> ** https://www.nsnam.org/docs/release/3.29/manual/html/python.html#working-with-python-bindings<br /> <br /> ==== BPF support ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [https://lwn.net/ml/netdev/20191214004753.1653075-1-kafai@fb.com/ BPF] is a current networking implementation trend. What would it take to support BPF programs in ns-3? What are the use cases of interest?<br /> <br /> * ''Required Experience:''C++, C<br /> * ''Recommended Experience:'' BPF, Linux kernel<br /> * ''Interests:'' protocol implementation<br /> * ''Difficulty:'' Medium to hard?<br /> * ''Recommended reading:''<br /> ** https://lwn.net/Articles/740157/<br /> <br /> ==== Wi-Fi code refactoring to facilitate integration of other 802.11 based standards ====<br /> <br /> Mentors: [mailto:sebastien.deronne@gmail.com Sébastien Deronne]<br /> <br /> Besides the commercial 802.11 standards (11b, 11a, 11g, 11n, 11ac &amp; 11ax) that have been implemented in mainline ns-3 version, some other modules have been developed to implement &quot;non-commercial&quot; 802.11 amendments, such as 802.11ah and 802.11ad/ay (Wigig).<br /> Since these make use of some common code from the wifi module, developers of these other modules implement their own models on top of the existing wifi model, which result in a very large amount of code in the same module. furthermore, this makes this code very difficult to maintain due to a lot of merge conflicts each time changes have been done in the mainline wifi. A much better approach would be to refactor the wifi module, so that common functionalities can be used from separate modules (802.11h, Wigig, ...) that would later be available in the ns-3 App Store and could be easily plugged in. The goal of this project is to identify a good approach to refactor the wifi module and start its implementation. <br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' 802.11 (Wi-Fi)<br /> * ''Interests:'' Code refactoring<br /> * ''Difficulty:'' Medium to hard<br /> * ''Recommended reading:''<br /> <br /> [[Category:GSoC]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=GSOC2020Projects&diff=11820 2020-01-15T20:18:22Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> This page contains 2020 Google Summer of Code project ideas for ns-3. <br /> <br /> '''Note:''' ns-3 will apply to Google Summer of Code on February 5 and will be notified about acceptance on February 27.'''<br /> <br /> <br /> * [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC Frequently Asked Questions]<br /> * [[GSOC2019StudentGuide |ns-3's 2019 GSoC Student guide]] (will update to 2020 if we are selected)<br /> * [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide (not ns-3 specific)]<br /> * [[GSOC2019StudentApplicationTemplate |2020 GSoC Student application template]] (will update for 2020 if we are selected)<br /> * [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]<br /> * [http://en.flossmanuals.net/gsoc-mentoring/ GSoC Mentor guide (not ns-3 specific)]<br /> * [[GSOCSelectionProcess | GSoC Student Selection Process]]<br /> * ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''chat'' https://ns-3.zulipchat.com/<br /> <br /> === About the ns-3 project ===<br /> <br /> ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.<br /> <br /> 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.<br /> <br /> ns-3 has participated in past GSoCs during 2008-10, 2012-15, and 2017-19. We seek students interested in the intersection of wireless and computer networking, performance analysis, and open source software.<br /> <br /> === Org admins ===<br /> <br /> Google Summer of Code organizational admins for ns-3 are [mailto:tpecorella@mac.com Tommaso Pecorella] and [mailto:tomh@tomh.org Tom Henderson]; contact them with any questions. They also hang out on [https://ns-3.zulipchat.com Zulip].<br /> <br /> === Mentors ===<br /> <br /> 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 or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge. In 2020, we are going to be seeking two-person or multiple-person mentoring teams for projects, to help with the mentoring workload and bring more expertise.<br /> <br /> The current list of prospective mentors for 2020 will be announced here if/when we are selected for the program.<br /> <br /> === Students: how to participate ===<br /> <br /> For students interested in applying to ns-3 for GSOC, please go through the following list to get started:<br /> * Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].<br /> * Read [[GSOC2019StudentGuide |ns-3's GSoC Student guide]] (will be updated for 2020 if selected)<br /> * Look through our [[#Project Ideas]] below to see if you find a project that interests you.<br /> * Review the [http://www.nsnam.org/ns-3-30/documentation ns-3 tutorial] thoroughly, if you have not already done so.<br /> * Once it is posted, look through the [[GSOC2019StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.<br /> * Next, proceed to get in touch with the developers on the mailing list and refine your proposal.<br /> * In parallel, make sure you prepare a patch as per the patch requirement guidelines (to be posted at a later date). Your application to ns-3 will not be considered if you do not fulfill this requirement.<br /> <br /> Below is a list of [[#Project Ideas]] proposed by the ns-3 team for Google Summer of Code 2020. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the proposal it will develop into, and the higher your chances of being accepted into the programme.<br /> <br /> &lt;blockquote&gt;<br /> Each project idea within a particular priority has been tagged with the following properties:<br /> * ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.<br /> * ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.<br /> * ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.<br /> * ''Difficulty:'' easy, medium or difficult<br /> * ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.<br /> <br /> 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.<br /> &lt;/blockquote&gt;<br /> <br /> === Mentors: how to participate ===<br /> <br /> The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:<br /> <br /> * 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.<br /> * 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.<br /> * 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 to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.<br /> <br /> == Project Ideas ==<br /> <br /> '''Note to students:''' These ideas are not listed in any priority order. <br /> <br /> ==== Migrate contributed code to apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> A large amount of ns-3 code exists out of the mainline and falls out of date. This project would aim to update, finish off, and publish as many apps as possible to the [https://apps.nsnam.org ns-3 App Store]. The student will also be responsible for writing test scripts to test daily that compatibility of apps with the ns-3 mainline is not broken. A list of potential modules will be provided below:<br /> * [https://gitlab.com/tomhenderson/ns-3-ee-595/tree/course/contrib/simple-wireless Simple wireless]<br /> * 802.11ah<br /> * WiGig<br /> * Others TBD<br /> <br /> ==== Usability improvements ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson], others TBD<br /> <br /> Usability of ns-3 can always be improved, whether it is help with building simulations, running simulation campaigns, using the ns-3 C++ API, improving the Python user experience, visualizing simulations or data, software packaging (e.g. binary packages or Docker containers), or documentation. This project is for a student who has been using ns-3 for a while and has ideas on how to make it better during GSoC. We don't want to limit the scope of proposals here; we will consider any project ideas that improve ns-3 usability in some way (please explain to us why the usability improvement is important to users beyond yourself, and why you would argue for your particular solution, and of course describe how you plan to get it done during the timeframe of GSoC). Some possible project examples:<br /> * Tools and scripts to conduct and manage data from a large number of simulation runs<br /> * How to integrate a more Python-centric data flow and tools, such as [http://jupyter.org/ Jupyter Notebook] and [https://github.com/bloomberg/bqplot bqplot]<br /> * Internal state visualization of Wi-Fi or LTE, such as the kind of plots generated by [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.3791&amp;rep=rep1&amp;type=pdf Yavista]<br /> <br /> ==== User-friendly internet-apps ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> Ping is a ubiquitous application for reachability and latency measurements. ns-3 already has a ping model (the v4ping.cc and ping6.cc). However, a user-friendly API could still be added. It is not straightforward to configure an ns-3 program to do in a single statement, for example, &quot;Ping the IP address W.X.Y.Z from node 0 between times 5 and 50 seconds in my program, and save the output in traditional format to the file &lt;filename.txt&gt;&quot;, or to configure the many options found in the ping man page. This project is therefore not about developing brand new features as much as it is about making ping super-easy to use with a great API. Have a look at how ns-3 programs are written, and tell us what kind of API makes sense to you, and why, and how you would go about prioritizing its implementation. If ping is solved very early, the project can follow the same pattern for one or two more applications (e.g. netperf, iperf, etc.). <br /> <br /> * ''Required Experience:''C++<br /> * ''Interests:'' Network performance management<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> <br /> ==== nam upgrade and support for ns-3 ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [http://www.isi.edu/nsnam/nam/ nam] is a Tcl/Tk-based animator for ns-2. Some example videos are found at [https://www.youtube.com/results?search_query=nam+network+animator YouTube]. nam has been functionally replaced in many ways by [https://www.nsnam.org/wiki/NetAnim NetAnim], but it still has some attractive features and might make a complementary animation tool for ns-3. In fact, someone did a proof-of-concept support of nam for ns-3 many years ago: http://www.nsnam.org/contributed/ns-3-nam.tar.bz2. This project would involve upgrading nam support to the latest Tcl/Tk release series (8.6) and then using the existing ns-3 trace system to generate nam output files such as in ns-2, and documenting and testing the results, including some demonstration videos. <br /> <br /> * ''Required Experience:''C++, Tcl/Tk also preferred<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** the links listed above<br /> <br /> ==== NetAnim Python and examples ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [[NetAnim]] is an optional animator for ns-3. It has not been actively developed for a few years. It is written using Qt libraries, and works in an offline mode, meaning that the simulation run outputs a detailed animation trace file that is later imported into NetAnim to visualize the simulation. NetAnim is presently underutilized because of lack of documentation on many features and lack of examples/tutorials around its use. Python bindings for the animator are also not supported. We would be interested in a student who would focus a project around improving the usability, documentation, and examples around NetAnim.<br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' Python, Qt<br /> * ''Interests:'' Network visualization/animation<br /> * ''Difficulty:'' Medium<br /> * ''Recommended reading:''<br /> ** https://www.nsnam.org/wiki/NetAnim<br /> ** https://www.qt.io/what-is-qt/<br /> ** https://www.nsnam.org/docs/release/3.29/manual/html/python.html#working-with-python-bindings<br /> <br /> ==== BPF support ====<br /> <br /> Mentors: [mailto:tomh@tomh.org Tom Henderson]<br /> <br /> [https://lwn.net/ml/netdev/20191214004753.1653075-1-kafai@fb.com/ BPF] is a current networking implementation trend. What would it take to support BPF programs in ns-3? What are the use cases of interest?<br /> <br /> * ''Required Experience:''C++, C<br /> * ''Recommended Experience:'' BPF, Linux kernel<br /> * ''Interests:'' protocol implementation<br /> * ''Difficulty:'' Medium to hard?<br /> * ''Recommended reading:''<br /> ** https://lwn.net/Articles/740157/<br /> <br /> ==== Wi-Fi code refactoring to facilitate integration of other 802.11 based standards ====<br /> <br /> Mentors: [mailto:sebastien.deronne@gmail.com Sébastien Deronne]<br /> <br /> Besides the commercial 802.11 standards (11b, 11a, 11g, 11n, 11ac &amp; 11ax) that has been implemented in mainline ns-3 version, some other modules have been developed to implement &quot;non-commercial&quot; 802.11 amendments, such as 802.11ah and 802.11ad/ay (Wigig).<br /> Since these make use of some common code from the wifi module, developers of these other modules implement their own models on top of the existing wifi model, which result in a very large amount of code in the same module. furthermore, this makes this code very difficult to maintain due to a lot of merge conflicts each time changes have been done in the mainline wifi. A much better approach would be to refactor the wifi module, so that common functionalities can be used from separate modules (802.11h, Wigig, ...) that would later be available in the ns-3 App Store and could be easily plugged in. The goal of this project is to identify a good approach to refactor the wifi module and start its implementation. <br /> <br /> * ''Required Experience:''C++<br /> * ''Recommended Experience:'' 802.11 (Wi-Fi)<br /> * ''Interests:'' Code refactoring<br /> * ''Difficulty:'' Medium to hard<br /> * ''Recommended reading:''<br /> <br /> [[Category:GSoC]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Wns3-2019&diff=11658 2019-06-20T07:33:17Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> The main WNS3 2019 page is at https://www.nsnam.org/research/wns3/wns3-2019/<br /> <br /> This page is for Thursday June 20 activity planning.<br /> <br /> == Thursday June 20 ==<br /> <br /> * '''9:00-10:30''' Annual meeting of ns-3 consortium.<br /> * '''10:30:''' Informal coffee break (no catering service provided on Thursday)<br /> <br /> The remainder of Thursday will be devoted to an [https://en.wikipedia.org/wiki/Unconference Unconference]-style meeting (anyone who wants to grab a meeting slot, please do so).<br /> <br /> If you want to hold a sidebar meeting on a specialized topic (e.g. WiGig, 5GNR, 11ax), please list it here and where you will get together.<br /> <br /> === List of scheduled meetings: ===<br /> <br /> * '''11:00-11:30:'''&amp;nbsp;&amp;nbsp;&amp;nbsp;'''What can we remove from ns-3-dev?''' (organizer Tom Henderson)<br /> ** Can we clean out some less-used code from ns-3-dev? What about ns-3-allinone, etc.? What does a future minimal ns-3 release, or other release spins, look like?<br /> * '''11:30-12:00''&amp;nbsp;&amp;nbsp;&amp;nbsp;'''5G NR/LTE help desk''' (organizer Natale Patriciello)<br /> ** Next steps with 5G NR and LTE development and collaboration<br /> * '''12:00-12:30'''&amp;nbsp;&amp;nbsp;&amp;nbsp;'''Onboarding projects and GCI''' (organizers Mohit Tahiliani and Tom Henderson)<br /> ** How can we set the project up better for on boarding future contributors and for participating in the next Google Code-In event?<br /> <br /> <br /> * '''12:30 - 13:30''' Lunch (cafeteria)<br /> <br /> <br /> * '''13:30-14:00'''&amp;nbsp;&amp;nbsp;&amp;nbsp;'''Next steps with App Store and bake''' (organizers Tom Henderson, Ankit Deepak)<br /> ** Discuss Mishal Shah's GSOC project goals and requirements for bake and app store. We owe Mishal more guidance about long-term design goals.<br /> * '''14:00-14:30'''&amp;nbsp;&amp;nbsp;&amp;nbsp;'''Code review of GSoC Data Center project''' (organizer Tom Henderson)<br /> ** Code review of the code produced by Liangcheng Yu's project<br /> * '''14:30-15:00''' Next steps with WiGig models (organizer: Sébastien Deronne)<br /> * '''15:00-15:30'''<br /> * '''15:30-16:00'''<br /> <br /> === List of informal adhoc meetings planned for the afternoon: ===<br /> <br /> * Debug Python 3 issues with binding generation (Tom Henderson and Ankit Deepak)</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=11072 2018-05-26T09:34:25Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.29]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Another public repository for 11ax repositories exists at: https://github.com/cisco/ns3-802.11ax-simulator<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models ==<br /> <br /> Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are currently working on the following list of extensions to ns-3 WiFi models:<br /> * WiFi channel scanning (Tom Henderson and Muhammad Iqbal)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa and Sébastien Deronne)<br /> * 802.11ah support (Le Tian and Sébastien Deronne)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Ns-3.29&diff=11071 2018-05-26T09:28:03Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> This page summarizes the release planning for ns-3.29. The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].<br /> <br /> = Release status =<br /> <br /> ns-3.29 is not yet scheduled but should be published 2 to 4 months after ns-3.28.<br /> <br /> = Release goals =<br /> <br /> Of course, resolving all confirmed issues in our tracker is a priority. Here are a few more things we'd like to accomplish this cycle, and the names of people who volunteer to work on the issue.<br /> <br /> ==== System-wide ====<br /> <br /> * Finish the Python bindings scanning process using CastXML (Tom Henderson, Ankit Deepak, Gustavo Carneiro)<br /> ** https://www.nsnam.org/bugzilla/show_bug.cgi?id=2451#c22<br /> <br /> * Make ns-3 compatible with Windows Visual Studio (Robert Ammon)<br /> ** [[Ns-3_on_Visual_Studio]]<br /> <br /> * Get to zero Doxygen warnings (Robert Ammon, Tom Henderson)<br /> ** We are close; additional patches to merge (provided by Robert) are at: https://www.nsnam.org/bugzilla/show_bug.cgi?id=938<br /> <br /> ==== New features ====<br /> <br /> * Launch the ns-3 app store (Tom Henderson, Abhijith Anilkumar)<br /> ** Beta site: http://ns-apps.ee.washington.edu<br /> <br /> * Review and merge remaining summer project code (GSoC and SOCIS) (various project mentors)<br /> ** See [https://www.nsnam.org/wiki/Summer_Projects#European_Space_Agency_Summer_of_Code_in_Space_.28SOCIS.29_2017 this wiki page] for links<br /> <br /> * Other new features are listed on the tracker (some requiring reviews, and more work)<br /> ** [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr code review issues]<br /> <br /> ==== Wifi ====<br /> <br /> * PCF support (Sebastien Deronne)<br /> <br /> ==== TCP ====<br /> <br /> Feature level:<br /> * Westwood test suite<br /> <br /> Performance:<br /> * Performance improvements, by replacing RFC algorithms with faster versions: do RFC + faster version in debug mode (checking for result equality), and disable RFC algorithms in release mode<br /> <br /> Documentation:<br /> * Split TcpSocketBase in three different source files: one for input, one for output, other for the state machine. 3000+ lines to read are a non-starter for educational purpose.<br /> - Document the missing features when comparing ns-3 with Linux TCP.<br /> <br /> Bug Fixes:<br /> * Some of them in some order... I still haven't an exact plan.<br /> <br /> ==== Traffic control ====<br /> <br /> Stefano Avallone mentioned the following plans.<br /> <br /> * introduce other qdiscs: prio<br /> <br /> * help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> * if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> * review and merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE<br /> <br /> ==== Miscellaneous ====<br /> <br /> Mohit P. Tahiliani and his students are working on the following issues<br /> <br /> * [https://www.nsnam.org/bugzilla/show_bug.cgi?id=2856 Bug 2856: dumbbell-animation example breaks when RightCount &gt; LeftCount] (Status: patch submitted for review)</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Energy_model&diff=11070 2018-05-26T08:30:07Z

<p>Sderonne: </p> <hr /> <div>= General =<br /> <br /> [http://www.ee.washington.edu/research/nsl/faculty/radha/ Network Security Lab (NSL)], University of Washington, Seattle has begun work on an generic energy model for ns3. The goal is to simulate an energy source and keep track of energy consumptions of various devices in the node. Current version focuses on radio energy consumption.<br /> <br /> = Background =<br /> <br /> Energy modeling is a key element in wireless network simulation. In several simulation scenarios, the energy consumption at a particular node, or at a particular component of a node, is of interest. Further, energy consumption is an important metric for evaluating the performance of wireless network protocols. Also, if a protocol is energy-aware, i.e. its operation depends on the energy level, it cannot be effectively simulated without an energy model. An energy model has been implemented in ns2 ([http://www.isi.edu/nsnam/ns/doc/node224.html ns2 energy model]) but is yet to be implemented in ns3.<br /> <br /> = Project Goals =<br /> <br /> In this project, we aim to provide the basic structures for modeling energy sources and energy consumption of various devices on the node. The energy source class will enable the modeling of batteries, discharging models, etc. while the energy consumption models are used to represent the energy consumed by various components of a node. The energy model will provide the following components:<br /> *Energy source model.<br /> **Battery.<br /> **etc.<br /> *Device energy consumption model.<br /> **Radio.<br /> **etc.<br /> <br /> = Schedule =<br /> <br /> *03/24/2011 : Paper &quot;An Energy Framework for the Network Simulator 3 (ns-3)&quot; presentation at the [http://www.simutools.org/2011/Programme/Schedule SIMUTOOLS 2011] conference.<br /> *01/13/2011 : Paper &quot;An Energy Framework for the Network Simulator 3 (ns-3)&quot; accepted by the [http://www.simutools.org/2011/ SIMUTOOLS 2011] conference.<br /> *01/05/2011 : Code update released with ns-3.10 in src/contrib/energy<br /> *08/20/2010 - 01/04/2011: Public review. Code available at: http://codereview.appspot.com/1008043/show<br /> *08/20/2010 : Released with ns-3.9 in src/contrib/energy.<br /> *04/19/2010 - 4/23/2010: Private review of radio energy model.<br /> <br /> = Energy Model Hierarchy =<br /> <br /> [[File:Ns-3_energy_model_data_flow.PNG|thumb|Energy model information flow]]<br /> <br /> The energy model consists of 2 major components:<br /> *Energy source.<br /> *Device energy model.<br /> <br /> Only a single energy source will exist on a node, representing the total energy reserve at the node. Multiple device energy models can exist on a single node, representing different devices. Each device energy model will notify the energy source of the energy consumed by that device, and thus update the remaining energy of the source. When energy is completely drained, the energy source will notify all device energy models connected to it.<br /> <br /> == Energy Source ==<br /> <br /> [[File:Ns-3_energy_source.PNG|thumb|Energy source class structure. Classes in dotted boxes are not included in initial release.]]<br /> <br /> This is an abstract base class that provides interfaces for for updating/recording total energy consumption on the node. It also issues a notification when the remaining energy goes to zero.<br /> <br /> Child classes of the energy source class implement a specific type of energy source, eg. a battery. Some typical child classes are:<br /> *Basic energy source.<br /> **Provides basic functionalities such as keeping track of remaining energy, decrease remaining energy, notify device energy models on complete depletion of energy.<br /> *Rakhmatov-Vrudhula non-linear battery model.<br /> **Non-linear battery model capable of capturing Rate Capacity Effect and Recovery Effect.<br /> <br /> == Device Energy Model ==<br /> <br /> [[File:Ns-3_device_energy_model.PNG|thumb|Device energy model class structure. Classes in dotted boxes are not included in initial release.]]<br /> <br /> This is a base class and its main function is to monitor the state of a device, and accordingly calculate its energy consumption. It provides interfaces for updating remaining energy in the energy source and handles the notification from the energy source when node energy is depleted. It also maintains a record of the total energy consumption of the device.<br /> <br /> Child classes of the device energy consumption class implement energy consumption schemes of specific devices, eg. a radio device. Multiple device models can exist on a node, representing energy consumption due to its different components. Further, multiple objects of the same device model class can also be used in a node. eg. a node could have multiple radios, and hence will have multiple radio energy consumption models.<br /> <br /> A typical child implementation of this class is the radio energy model class.<br /> <br /> === Wifi Radio Energy Model ===<br /> <br /> This class represents energy model for Wifi radio devices with states:<br /> *IDLE<br /> *CCA_BUSY<br /> *TX<br /> *RX<br /> *SWITCHING<br /> *OFF<br /> <br /> These states are defined in the WifiPhy class of ns-3.<br /> <br /> = Usage =<br /> <br /> The following code snippet installs an energy source (BasicEnergySource) and a WifiRadioEnergyModel onto each node.<br /> <br /> /* create some nodes */ <br /> NodeContainer c;<br /> c.Create(5);<br /> <br /> /* energy source */<br /> BasicEnergySourceHelper basicSourceHelper;<br /> // configure energy source<br /> basicSourceHelper.Set (&quot;BasicEnergySourceInitialEnergyJ&quot;, DoubleValue (0.1));<br /> // install source<br /> EnergySourceContainer sources = basicSourceHelper.Install (c);<br /> /* device energy model */<br /> WifiRadioEnergyModelHelper radioEnergyHelper;<br /> // configure radio energy model<br /> radioEnergyHelper.Set (&quot;TxCurrentA&quot;, DoubleValue (0.0174));<br /> // install device model<br /> DeviceEnergyModelContainer deviceModels = radioEnergyHelper.Install (devices, sources);<br /> <br /> The WifiRadioEnergyModel class fully supports the ns-3 built-in WiFi PHY class (YansWifiPhy). A sample simulation script of using the energy model is available in the &quot;examples/energy&quot; folder of ns-3.10.<br /> <br /> = Expending the Energy Model =<br /> <br /> Initial release of the energy model only includes implementations of a basic energy source and a basic radio energy model. However, developers can use the interfaces provided to model a wide variety of energy sources and devices. <br /> <br /> == Energy Source ==<br /> <br /> === Public APIs ===<br /> <br /> The energy source base class provides the following interfaces:<br /> <br /> * '''GetSupplyVoltage:'''<br /> ** Returns the supply voltage of the energy source.<br /> ** Must be implemented by child classes.<br /> <br /> * '''GetInitialEnergy:'''<br /> ** Returns the initial energy (capacity) stored in the energy source.<br /> ** The initial energy (capacity) of a energy source is specific to each implementation. Therefore we do not enforce a &quot;SetInitialEnergy&quot; interface in the base class.<br /> <br /> * '''GetRemainingEnergy:'''<br /> ** Returns the remaining energy stored in the energy source.<br /> <br /> * '''GetEnergyFraction:'''<br /> ** Returns the energy fraction [0,1] at the energy source. Energy fraction is defined as (remaining energy) / (initial energy).<br /> <br /> * '''UpdateEnergySource:'''<br /> ** Notifies EnergySource of stage changes in DeviceEnergyModels. Typically called by DeviceEnergyModels to inform EnergySource of a state change.<br /> ** This interface is used to implement non-linear energy update.<br /> <br /> * '''SetNode:'''<br /> ** Sets reference (pointer) to node where EnergySource is installed on.<br /> <br /> * '''GetNode:'''<br /> ** Returns reference (pointer) to node where EnergySource is installed on.<br /> <br /> * '''AppendDeviceEnergyModel:'''<br /> ** Called when installing device energy models. Energy source object keeps track of every device energy models installed onto the node.<br /> <br /> * '''FindDeviceEnergyModels:'''<br /> ** Returns a DeviceEnergyModelContainer containing a list of device energy models installed on the node. Useful when one wants to query certain types of devices for it energy consumption.<br /> <br /> === Protected APIs ===<br /> <br /> * '''CalculateTotalCurrent:'''<br /> ** Returns total current draw from all DeviceEnergyModel objects.<br /> <br /> * '''NotifyEnergyDrained''':<br /> ** This function Notifies all DeviceEnergyModels installed on the node for the energy depletion event.<br /> ** It should be called when energy is drained (remaining energy = 0) in the energy source.<br /> <br /> * '''BreakDeviceEnergyModelRefCycle''':<br /> ** This function breaks the reference cycle between EnergySource and the list of DeviceEnergyModels.<br /> ** It should be called in DoDispose by all derived class of EnergySource.<br /> <br /> === Examples ===<br /> <br /> Please see the BasicEnergySource class implementation for how the interfaces are used.<br /> <br /> == Device Energy Model == <br /> <br /> === Public APIs ===<br /> <br /> The device energy model base class provides the following interfaces:<br /> <br /> * '''SetEnergySource''':<br /> ** Called when installing device energy models. A device energy model can not operate without an energy source.<br /> <br /> * '''GetTotalEnergyConsumption:'''<br /> ** Returns total energy consumed by the device.<br /> <br /> * '''ChangeState:'''<br /> ** Notifies DeviceEnergyModel of a state change.<br /> ** Input parameter can be the state number or a value used internally by the DeviceEnergyModel.<br /> <br /> * '''GetCurretA:'''<br /> ** Returns the current draw, in Ampere of the DeviceEnergyModel, at its current state.<br /> <br /> * '''HandleEnergyDepletion''':<br /> ** Automatically called by the energy source object when energy is depleted. It's implementation is specific for each device.<br /> <br /> === Examples ===<br /> <br /> Please see the WifiRadioEnergySource class implementation for how the interfaces are used.<br /> <br /> [[Category:Models]]</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Ns-3.29&diff=10945 2018-03-30T20:56:38Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> This page summarizes the release planning for ns-3.29. The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].<br /> <br /> = Release status =<br /> <br /> ns-3.29 is not yet scheduled but should be published 2 to 4 months after ns-3.28.<br /> <br /> = Release goals =<br /> <br /> Of course, resolving all confirmed issues in our tracker is a priority. Here are a few more things we'd like to accomplish this cycle, and the names of people who volunteer to work on the issue.<br /> <br /> ==== System-wide ====<br /> <br /> * Finish the Python bindings scanning process using CastXML (Tom Henderson, Ankit Deepak, Gustavo Carneiro)<br /> ** https://www.nsnam.org/bugzilla/show_bug.cgi?id=2451#c22<br /> <br /> * Make ns-3 compatible with Windows Visual Studio (Robert Ammon)<br /> ** [[Ns-3_on_Visual_Studio]]<br /> <br /> * Get to zero Doxygen warnings (Robert Ammon, Tom Henderson)<br /> ** We are close; additional patches to merge (provided by Robert) are at: https://www.nsnam.org/bugzilla/show_bug.cgi?id=938<br /> <br /> ==== New features ====<br /> <br /> * Launch the ns-3 app store (Tom Henderson, Abhijith Anilkumar)<br /> ** Beta site: http://ns-apps.ee.washington.edu<br /> <br /> * Review and merge remaining summer project code (GSoC and SOCIS) (various project mentors)<br /> ** See [https://www.nsnam.org/wiki/Summer_Projects#European_Space_Agency_Summer_of_Code_in_Space_.28SOCIS.29_2017 this wiki page] for links<br /> <br /> * Other new features are listed on the tracker (some requiring reviews, and more work)<br /> ** [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr code review issues]<br /> <br /> ==== Wifi ====<br /> <br /> * PCF support (Sebastien Deronne)<br /> * Wigig module (802.11ad)<br /> <br /> ==== TCP ====<br /> <br /> Feature level:<br /> * Westwood test suite<br /> <br /> Performance:<br /> * Performance improvements, by replacing RFC algorithms with faster versions: do RFC + faster version in debug mode (checking for result equality), and disable RFC algorithms in release mode<br /> <br /> Documentation:<br /> * Split TcpSocketBase in three different source files: one for input, one for output, other for the state machine. 3000+ lines to read are a non-starter for educational purpose.<br /> - Document the missing features when comparing ns-3 with Linux TCP.<br /> <br /> Bug Fixes:<br /> * Some of them in some order... I still haven't an exact plan.<br /> <br /> ==== Traffic control ====<br /> <br /> Stefano Avallone mentioned the following plans.<br /> <br /> * introduce other qdiscs: prio<br /> <br /> * help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> * if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> * review and merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10936 2018-03-28T20:11:17Z

<p>Sderonne: /* WiFi models (other) */</p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models ==<br /> <br /> Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are currently working on the following list of extensions to ns-3 WiFi models:<br /> * WiFi channel scanning (Tom Henderson)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10935 2018-03-28T20:10:39Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are currently working on the following list of extensions to ns-3 WiFi models:<br /> * WiFi channel scanning (Tom Henderson)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10873 2018-01-10T21:06:45Z

<p>Sderonne: /* WiFi models (other) */</p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * Adjacent channel modeling (Getachew Redieteab)<br /> * WiFi channel scanning (Tom Henderson)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10872 2018-01-08T20:26:18Z

<p>Sderonne: /* WiFi models (other) */</p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10871 2018-01-08T20:24:43Z

<p>Sderonne: /* WiFi models (other) */</p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> * Rohan Patidar and Tom Henderson are preparing for code review a new OFDM error model based on link-to-system mapping and fast fading channels (see WNS3 2017 paper on this topic for more information)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * Add support for PHY_RXSTART <br /> * Inter-channel interference modeling <br /> * 802.11n/ac PHY layer models (more sophisticated models other than look-up tables)<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10870 2018-01-08T07:52:42Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * Add support for PHY_RXSTART <br /> * Inter-channel interference modeling <br /> * 802.11n/ac PHY layer models (more sophisticated models other than look-up tables)<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10869 2018-01-08T07:51:06Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * Add support for PHY_RXSTART <br /> * Inter-channel interference modeling <br /> * 802.11n/ac PHY layer models (more sophisticated models other than look-up tables)<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === 802.11 model extensions ===<br /> <br /> There are several efforts ongoing to extend the ns-3 Wifi model.<br /> <br /> ==== Harmonization with ns-2 802.11 Ext models ====<br /> * ''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:<br /> ** Equalizing PHY models including capture effects, user-definable coding rates (e.g. 5.9 GHz from 802.11p)<br /> ** EDCA QoS extensions of 802.11e<br /> * Already finished features:<br /> ** Nakagami/Rayleigh propagation loss model<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-November/004936.html<br /> * ''code location'': http://idlebox.net/2008/ns-3-wifi/code/ns-3-wifiex/<br /> * ''status'': under current active development. Time frame till this is completed: 4-5 month.<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10868 2018-01-08T07:48:32Z

<p>Sderonne: </p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * Add support for PHY_RXSTART <br /> * Inter-channel interference modeling <br /> * 802.11n/ac PHY layer models (more sophisticated models other than look-up tables)<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === 802.11 model extensions ===<br /> <br /> There are several efforts ongoing to extend the ns-3 Wifi model.<br /> <br /> ==== Harmonization with ns-2 802.11 Ext models ====<br /> * ''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:<br /> ** Equalizing PHY models including capture effects, user-definable coding rates (e.g. 5.9 GHz from 802.11p)<br /> ** EDCA QoS extensions of 802.11e<br /> * Already finished features:<br /> ** Nakagami/Rayleigh propagation loss model<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-November/004936.html<br /> * ''code location'': http://idlebox.net/2008/ns-3-wifi/code/ns-3-wifiex/<br /> * ''status'': under current active development. Time frame till this is completed: 4-5 month.<br /> <br /> ==== 802.11n ====<br /> <br /> * ''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:<br /> ** Frame Aggregation<br /> ** Block ACK<br /> ** HCF (EDCA and support for HCCA)<br /> ** TXOP<br /> ** HT terminal (also with protection modes)<br /> ** MIMO<br /> Also interested to verify the 11n terminal throughput when are associated terminal of a/b/g standards.<br /> * Already finished features (in ns-3.5):<br /> ** HCF, TXOP, Frame Aggregation<br /> * Merged for ns-3.8:<br /> ** Block ACK<br /> * ''code location'': &lt;s&gt;http://code.nsnam.org/mirko/ns-3-80211n&lt;/s&gt; Repository has been removed.<br /> * ''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.<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne https://www.nsnam.org/mediawiki/index.php?title=Current_Development&diff=10864 2018-01-07T11:04:20Z

<p>Sderonne: /* WiFi models (other) */</p> <hr /> <div>{{TOC}}<br /> <br /> On this page, we will try to summarize current ns-3 development work. If you are interested in collaborating on one of these projects, or reviewing work by others, please do not hesitate to contact the individuals identified, or the [mailto:tomh@tomh.org page maintainer].<br /> <br /> There are a few other places to look for current activity on ns-3 development:<br /> * the current release page will list code under consideration for merging, and bugs being worked. The next release, [[Ns-3.28 | ns-3.28 release]], is not yet scheduled.<br /> * we should have entries for all of our known bugs in the [http://www.nsnam.org/bugzilla Bugzilla] bug tracker.<br /> * [[Related_Projects | Related projects]] list some active and past projects that are associated with ns-3.<br /> * We maintain a suggested [[Project_Ideas | project ideas]] page for people interested in trying to start something new, or finish off some existing work.<br /> * We conduct [https://groups.google.com/forum/?fromgroups#!forum/ns-3-reviews code review discussions] on the Google Group 'ns-3-reviews'<br /> <br /> = How to get involved =<br /> <br /> ns-3 always can use more time and assistance from contributors of all skill levels. One of the best ways to learn a tool is to try to get involved in its development processes, even if it is as simple as pointing out stale information or documentation on our web pages. Ideas on how to get started are on our [[Project_Ideas | project ideas]] page.<br /> <br /> If you are new to ns-3 and want to contribute code, please read these guidelines: [http://www.nsnam.org/developers/contributing-code/ Contributing to ns-3] and review the information on this page below. <br /> <br /> '''Note:''' ns-3 developers sometimes hang out on IRC at #ns-3 at irc.freenode.net. [http://colabti.org/irclogger/irclogger_logs/ns-3 IRC logs]<br /> <br /> Also, please check out the [[Nsnam:Current events | Current events]] page to learn of upcoming events for ns-3.<br /> <br /> = Code reviews = <br /> <br /> All new code (other than maintenance code committed directly by a module's maintainer) goes through a public code review. The process is described [http://www.nsnam.org/developers/contributing-code/code-reviews/ here]. This page is devoted to listing code reviews that have been publicly announced.<br /> <br /> Currently open code reviews should be also tagged in our bug tracker: https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;resolution=---&amp;short_desc=code%20review&amp;short_desc_type=allwordssubstr<br /> <br /> Some older code reviews can be found here (some of these have been included in ns-3, some are still pending):<br /> <br /> * '''Mobility service interface (revised)'''<br /> ** Code review: https://codereview.appspot.com/265730044/<br /> ** Wiki page: https://www.nsnam.org/wiki/RoutesMobilityModel<br /> ** Repo: https://bitbucket.org/TiagoCerqueira/routesmobilitymodel/overview<br /> <br /> * '''RRPAA WiFi power/rate control mechanism'''<br /> ** Code review: https://codereview.appspot.com/254440043<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012979.html<br /> <br /> * '''LR-WPAN Contiki MAC''' (and updated energy model code)<br /> ** Code review: https://codereview.appspot.com/254120043/<br /> <br /> * '''TCP SACK'''<br /> ** Code review: https://codereview.appspot.com/255020043/<br /> ** Announcement: http://mailman.isi.edu/pipermail/ns-developers/2015-July/012906.html<br /> <br /> * '''Lr-Wpan Energy Model'''<br /> ** Code review: &lt;s&gt;https://codereview.appspot.com/249560043/&lt;/s&gt; See above contiki mac review<br /> <br /> * '''SiFT'''<br /> ** Code review: https://codereview.appspot.com/246310044/<br /> <br /> * '''Minstrel_ht support'''<br /> ** Code review: https://codereview.appspot.com/254900043<br /> <br /> * '''Priority queue support'''<br /> ** Code review: https://codereview.appspot.com/244440043/<br /> <br /> * '''Collector classes for Data collection framework'''<br /> ** Code review: http://codereview.appspot.com/245260043<br /> <br /> * '''Ipv6 for LTE module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-April/012680.html<br /> ** Code review: https://codereview.appspot.com/234000043/<br /> <br /> * '''Propagation loss model for Teraherz channels'''<br /> ** Code review: https://codereview.appspot.com/197290043/ <br /> <br /> * '''Obstacle shadowing model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-February/012536.html<br /> ** Code review: https://codereview.appspot.com/201200043<br /> <br /> * ''' 802.15.4e TSCH model'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2015-January/012459.html<br /> ** Code review: https://codereview.appspot.com/194960043/ and https://codereview.appspot.com/192220043/<br /> <br /> * ''' WifiMac Weighted Fair Queue '''<br /> ** Announce: https://groups.google.com/forum/#!topic/ns-3-reviews/7LYDuv1d8ss<br /> ** Code review: https://codereview.appspot.com/180690043/<br /> <br /> * '''CSMA backoff improvements'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-July/012113.html<br /> ** Code review: https://codereview.appspot.com/109450044/<br /> <br /> * '''LEAR extension for DSR'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011933.html<br /> ** &lt;s&gt;Code review: https://codereview.appspot.com/85630046/&lt;/s&gt;<br /> ** Note: new code review issue posted 8 May: https://codereview.appspot.com/96130043/<br /> <br /> * '''TCP CUBIC'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-April/011939.html<br /> ** Code review: https://codereview.appspot.com/87740043<br /> <br /> * '''Next steps with Object Stop/Start'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011764.html<br /> ** Code review: http://codereview.appspot.com/66990047<br /> <br /> * '''NetSh (simulation helper)'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011742.html<br /> ** Code review: none yet.<br /> <br /> * '''WDM module'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-February/011758.html<br /> ** Code review: none yet.<br /> <br /> * '''DAMA environment'''<br /> ** Announce: http://mailman.isi.edu/pipermail/ns-developers/2014-January/011715.html<br /> <br /> * '''Energy model access via Config system'''<br /> ** Announce (January 3, 2014): http://mailman.isi.edu/pipermail/ns-developers/2014-January/011660.html<br /> ** Code review: https://codereview.appspot.com/39820045<br /> <br /> * '''DTN Bundle Protocol'''<br /> ** Announce (December 23, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-December/011616.html<br /> ** Code review: https://codereview.appspot.com/38130049/<br /> <br /> * '''PGBR routing protocol and extension of topology-read module'''<br /> ** Announce (Oct 21, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011455.html<br /> ** Code review: https://codereview.appspot.com/15530043/<br /> ** Status: Needs reviews<br /> <br /> * '''UAN WOSS'''<br /> ** Announce (Oct 14, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-October/011446.html<br /> ** Code review: https://codereview.appspot.com/14677043/<br /> ** Status: Needs reviews<br /> <br /> * '''Epidemic routing'''<br /> ** Announce (Sept 24, 2013): http://mailman.isi.edu/pipermail/ns-developers/2013-September/011426.html<br /> ** Code review: https://codereview.appspot.com/13831049/<br /> ** Status: Author responding to latest review comments.<br /> <br /> Some older code reviews can be found here: http://www.nsnam.org/wiki/Ns-3.18#additional_new_feature_reviews<br /> <br /> Also:<br /> * '''TDMA'''<br /> ** Code review: https://codereview.appspot.com/4747046/<br /> * '''Simple wireless'''<br /> ** Code review: https://codereview.appspot.com/1587041/show<br /> * '''Ipv4 Route Output refactoring'''<br /> ** Code review: https://codereview.appspot.com/5661044/ <br /> ** Bug tracker issue: https://www.nsnam.org/bugzilla/show_bug.cgi?id=1111<br /> <br /> = Roadmap =<br /> <br /> See the [[ns-3.28]] page for the current release planning and roadmap.<br /> <br /> = Current development for main trunk of ns-3 =<br /> <br /> This section is intended to list items that people are working on, to avoid duplicated efforts and to promote collaboration.<br /> <br /> == Wi-Fi 802.11ax support ==<br /> <br /> Sebastien Deronne has been adding 11ax rates and support for information elements (HeOperation, HeCapabilities).<br /> <br /> A team at UW is working on spatial reuse features (OBSS_PD, BSS color) and the PHY abstraction (RBIR) and plans to work on multi-user aspects. Contact Tom Henderson (tomh@tomh.org) if interested.<br /> <br /> Rediet (getachew.redieteab@orange.com) and colleages are working on modeling OFDMA for 11ax (based on the spec framework https://mentor.ieee.org/802.11/dcn/15/11-15-0132-17-00ax-spec-framework.docx).<br /> <br /> Others are welcome to list their work in progress here regarding 802.11ax, to reduce duplicated effort and encourage collaboration.<br /> <br /> == WiFi models (other) ==<br /> <br /> As of September 2015, Wi-Fi maintainer [mailto:sebastien.deronne@gmail.com Sebastien Deronne] and others are working on the following list of extensions to ns-3 WiFi models:<br /> * 802.11n/ac PHY layer error rate models for different MCS (Ghada Badawy and Sebastien)<br /> * 802.11 PCF (Sébastien Deronne)<br /> * Minstrel-Blues rate control (Matias Richart)<br /> * flow control between 802.11e queues and priority queuing layer (Stefano Avallone and Tom Henderson)<br /> * 802.11ad support (Hany Assasa)<br /> * 802.11ah support (Sébastien Deronne and Le Tian)<br /> * 802.11ax features (see above)<br /> <br /> The following additional work is recommended (contributions from others are recommended); contact Sebastien to coordinate:<br /> * Add support for PHY_RXSTART <br /> * Inter-channel interference modeling <br /> * 802.11n/ac PHY layer models (more sophisticated models other than look-up tables)<br /> * 802.11n/ac beamforming support<br /> * 802.11ac MU-MIMO support<br /> * 802.11 HCF/HCCA<br /> * Any other 802.11n/ac missing feature<br /> <br /> == AQM and ECN ==<br /> <br /> Last updated: Dec. 2017<br /> <br /> Stefano Avallone is working on:<br /> <br /> - introduce other qdiscs: fifo, prio and token bucket (Surya’s GSoC). Finish off HHF (the other qdisc Surya worked on).<br /> <br /> - merge a few pending code reviews which implement other qdiscs (REM, BLUE, PI, PI2) and add ECN support to CoDel and PIE.<br /> <br /> - help Pasquale and Tommaso to merge the netmap netdevice (SOCIS)<br /> <br /> - if time permits, implement the Diffserv to IEEE 802.11 mapping as defined by draft-ietf-tsvwg-ieee-802-11-09<br /> <br /> == CSMA model ==<br /> <br /> This was a feature goal for ns-3.23 release, but has slipped (further input wanted).<br /> <br /> There has been discussion in the June 2014 timeframe about improving this model:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012026.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2014-June/012093.html<br /> <br /> These improvements have been recommended:<br /> # Implement backoff counter decrement as a function of line state (''see this [https://codereview.appspot.com/109450044/ initial code review]'')<br /> # Divide CSMA implementation between CSMA/CD &amp; CSMA/CA (which are totally different)<br /> # Implement a distance system (not the same propagation delay for every nodes); see Vedran Miletić's work [https://codereview.appspot.com/5314055/#ps3002 code review issue] <br /> # Audit the ns-3 examples to find instances where CSMA is being used with inappropriate link delay (where multiple access may perform very suboptimally)<br /> <br /> = Past development efforts =<br /> &lt;pre style=&quot;color: red&quot;&gt;<br /> Most of these activities are now dormant or concluded and some of the information is stale. <br /> We are keeping here as a placeholder until this section can be cleaned up.<br /> &lt;/pre&gt;<br /> <br /> == ns-3 core ==<br /> <br /> === Multi-threaded simulation implementation for multicore ===<br /> <br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2009-July/006197.html<br /> * ''code location'': http://code.nsnam.org/guillaume/ns-3-multithreading/<br /> * ''status'': ns-3.11 merge?<br /> <br /> === Linux namespaces and ns-3 ===<br /> <br /> * ''summary'': Tom Goff has contributed code and documentation about how to use ns-3 with Linux namespaces.<br /> * ''code location'': See the below wiki page.<br /> * ''background'': [[HOWTO use Linux namespaces with ns-3]]<br /> * ''status'': A version of this was merged to the latest [http://cs.itd.nrl.navy.mil/work/core/ CORE network emulator] release.<br /> <br /> == Device and channel models ==<br /> === Optical network: WDM, PON and RoF ===<br /> See [[Optical network models]].<br /> <br /> === Miscellaneous wifi enhancements ===<br /> <br /> * ''code location'': http://codereview.appspot.com/65051<br /> * ''reviewer(s)'': Mathieu Lacage<br /> * ''status'': Some of these pieces made it into ns-3.5-- others are pending<br /> * ''background'': http://groups.google.com/group/ns-3-reviews/browse_thread/thread/f0b36d7373421a7d#<br /> <br /> === Patch to pause and resume an interface ===<br /> <br /> * ''code location'': http://codereview.appspot.com/62054<br /> * ''reviewer(s)'': TBD<br /> * ''status'': reimplemented in a more general way, see [[Object Start Stop Specification]]<br /> <br /> === 802.11 model extensions ===<br /> <br /> There are several efforts ongoing to extend the ns-3 Wifi model.<br /> <br /> ==== Harmonization with ns-2 802.11 Ext models ====<br /> * ''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:<br /> ** Equalizing PHY models including capture effects, user-definable coding rates (e.g. 5.9 GHz from 802.11p)<br /> ** EDCA QoS extensions of 802.11e<br /> * Already finished features:<br /> ** Nakagami/Rayleigh propagation loss model<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-November/004936.html<br /> * ''code location'': http://idlebox.net/2008/ns-3-wifi/code/ns-3-wifiex/<br /> * ''status'': under current active development. Time frame till this is completed: 4-5 month.<br /> <br /> ==== 802.11n ====<br /> <br /> * ''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:<br /> ** Frame Aggregation<br /> ** Block ACK<br /> ** HCF (EDCA and support for HCCA)<br /> ** TXOP<br /> ** HT terminal (also with protection modes)<br /> ** MIMO<br /> Also interested to verify the 11n terminal throughput when are associated terminal of a/b/g standards.<br /> * Already finished features (in ns-3.5):<br /> ** HCF, TXOP, Frame Aggregation<br /> * Merged for ns-3.8:<br /> ** Block ACK<br /> * ''code location'': &lt;s&gt;http://code.nsnam.org/mirko/ns-3-80211n&lt;/s&gt; Repository has been removed.<br /> * ''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.<br /> <br /> === Wireless Interference (Jamming) Model ===<br /> <br /> * ''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.<br /> * ''wiki page'': [[NS-3 wireless jamming model]]<br /> * ''code location'': http://codereview.appspot.com/1055041/show<br /> * ''status'': Public review.<br /> <br /> === Vehicular Ad Hoc Networks (VANET) ===<br /> <br /> * ''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.<br /> * ''code location'': None publicly posted at this time.<br /> <br /> === Wireless Sensor Networks (i.e., 802.15.4 + 6LoWPAN + RPL) ===<br /> <br /> Tommaso Pecorella announced his plans [http://mailman.isi.edu/pipermail/ns-developers/2010-August/008304.html here]<br /> <br /> Current status is:<br /> * RPL implementation (storing, multicast): 5th refactoring going on. Moving responsibility to ParentSet and MeasureCollectors for metrics other than HC.<br /> ** RPL is based on [http://tools.ietf.org/wg/roll/ ROLL RFCs and drafts]<br /> ** Objective functions implemented are of0 and minrank-hysteresis-of<br /> * 6LoWPAN has been merged in ns-3-dev and will be included in ns-3.19.<br /> * 802.15.4 will rely on the lr-wpan module (currently being implemented by Boeing).<br /> ** A patch to the lr-wpan code to enable its use with 6LoWPAN (and the full IPv6 stack) has been created. The patch adds a number of functionalities to the module and will be either included in lr-wpan or provided as a separate patch.<br /> <br /> A wiki page will be created before 3.19 release to explain in detail the current implemented functionalities, the models limitations, the work status and provide a guide to setup a simple simulation.<br /> <br /> Boeing is working on lr-wpan (IEEE 802.15.4-2006) support; details [[lr-wpan | here]].<br /> <br /> === LTE ===<br /> <br /> In addition to the LENA project above, several developers expressed their interest in enhancing the LTE code initially developed within the GSoC 2010:<br /> <br /> * Leo Razoumov [http://mailman.isi.edu/pipermail/ns-developers/2010-November/008467.html announced] possible interest in the following contributions:<br /> ** MIMO<br /> ** PHY model abstractions<br /> ** scheduling models<br /> ** mobility and traffic models <br /> * 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:<br /> ** RRM<br /> ** scheduling<br /> ** AMC<br /> * 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]:<br /> ** MAC layer<br /> ** mobility<br /> ** traffic modelization<br /> ** MIMO<br /> * 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<br /> ** GTPv1-U (for the user plane)<br /> ** GTPv2-C (for the control plane)<br /> ** Diameter: Supported use cases: default- and dedicated bearer establishment<br /> ** NAS (ESM, EMM) A combined initial attach with a default bearer establishment. Dedicated bearer establishment<br /> ** X2AP HO without SGW relocation. Endmarker messages are not supported<br /> ** PMIPv6: PBU/PBA, LMA, MAG<br /> <br /> == Link layer ==<br /> <br /> === 802.21 media independent handover ===<br /> <br /> * ''wiki page'': [[NS-3 MIH implementation]]<br /> * ''code location'': http://code.nsnam.org/salumu/ns-3-mih/<br /> * ''status'': Dormant-- no merge plans announced.<br /> <br /> == MPLS ==<br /> <br /> * ''Submitted by'': Andrey Churin<br /> * ''code location'': http://code.google.com/p/ns-3-shop/<br /> * ''reviewer(s)'': None<br /> * ''status'': Project has moved to Google hosting. <br /> <br /> == Network layer ==<br /> <br /> === API and functionality for marking TOS bytes in packets ===<br /> <br /> * ''Submitted by:'' Antti Makela<br /> * ''code location:'' http://www.nsnam.org/bugzilla/show_bug.cgi?id=897<br /> * ''reviewer(s):'' None<br /> * ''status:'' Need to consider whether this fits into the Linux netfilter support that is planned<br /> <br /> === DSR routing ===<br /> <br /> * ''Submitted by:'' Yufei Cheng<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> === DSDV routing ===<br /> <br /> * ''Submitted by:'' Hemanth Narra<br /> * ''code location:'' http://codereview.appspot.com/1668042/show<br /> * ''status:'' Announced here: http://mailman.isi.edu/pipermail/ns-developers/2010-December/008496.html<br /> <br /> == Transport layer ==<br /> <br /> === TCP Vegas ===<br /> <br /> * ''Submitted by:'' Juan Pablo Poujade<br /> * ''code location:'' http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html<br /> * ''reviewers:'' none officially<br /> * ''status:'' Waiting for guidance on how TCP congestion control variants will be implemented in general<br /> <br /> === Multipath TCP ===<br /> <br /> 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.<br /> A check of the compatibility with the latest version is needed.<br /> <br /> * ''Submitted by:'' Bachir CHIHANI<br /> * ''code location:'' http://code.google.com/p/mptcp-ns3/<br /> <br /> === Codel, fq_codel in ns-3 ===<br /> * ''Submitted by:'' Andrew Mcgregor<br /> * ''Code location:'' http://codereview.appspot.com/6463048<br /> * ''Mailing list post:'' http://mailman.isi.edu/pipermail/ns-developers/2012-August/010572.html<br /> * ''Reviewers:'' Tom Henderson and Mathieu Lacage<br /> <br /> == Application layer ==<br /> <br /> === Chord/DHash DHT ===<br /> <br /> * ''Submitted by'': Harjot Gill<br /> * ''code location:'' http://codereview.appspot.com/180107/show<br /> * ''reviewers:'' Mathieu Lacage, Tom Henderson<br /> * ''background:'' http://mailman.isi.edu/pipermail/ns-developers/2009-December/007222.html<br /> * ''status:'' Dormant for a while<br /> <br /> === Synchronous posix/sockets API ===<br /> <br /> * ''summary'': An ns-3 &quot;process&quot; environment<br /> * ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html<br /> * ''code location'': http://code.nsnam.org/mathieu/ns-3-simu<br /> * ''status'': still in development<br /> <br /> === real-world application integration ===<br /> <br /> * ''summary'': port of quagga routing to ns-3<br /> * ''wiki page'': [[Real World Application Integration]]<br /> * ''code location'': http://code.nsnam.org/lj/quagga-porting/<br /> * ''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.<br /> <br /> === ns-3-simu sockopt patches ===<br /> <br /> * ''code location'': Four patches listed in http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> * ''reviewer(s)'': TBD<br /> * ''status'': review requested on June 22<br /> * ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006144.html<br /> <br /> === Pastry ===<br /> <br /> * ''Summary:'' An implementation of [http://www.freepastry.org/ Pastry] within ns-3. Including some experimental key-based routing API.<br /> * ''Developers:'' Robert Nitsch and Dominic Scheurer ([https://www.tu-darmstadt.de/ Technische Universität Darmstadt]).<br /> * ''Code location:'' https://bitbucket.org/r_nitsch/ns-3-pastry/ (old repository: &lt;nowiki&gt;https://bitbucket.org/r_nitsch/libpastry/&lt;/nowiki&gt;)<br /> * ''Doxygen documentation:'' http://libpastry.robertnitsch.de<br /> * ''Status:''<br /> ** 2012-01-22: Re-integrated the code into ns-3 source tree (ns-3.13).<br /> ** Mostly finished.<br /> ** Node arrival process needs some tweaking.<br /> ** Review needed. (We're going to request one as soon as we're ready.)<br /> <br /> == Visualization ==<br /> <br /> Jeremy Norman and the iNSpect team have posted some plans for a visualization library for ns-3:<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-March/003777.html<br /> * http://mailman.isi.edu/pipermail/ns-developers/2008-November/004914.html<br /> <br /> George Riley has made a [[NetAnim | prototype animator]] for PointToPoint links.<br /> <br /> Joe Kopena is working on what he calls a &quot;decorator&quot; http://code.nsnam.org/tjkopena/<br /> <br /> Hagen Paul Pfeifer is working on a MANET visualizer http://nv.dev.jauu.net/<br /> <br /> === Graphical simulation builder ===<br /> <br /> Pierre Weiss and Sebastien Vincent have written an [[Ns3Generator| ns-3 scenario generator]] in Qt. <br /> * http://mailman.isi.edu/pipermail/ns-developers/2010-May/007998.html<br /> * Mercurial download: http://svnet.u-strasbg.fr/hg/ns-3-generator/<br /> <br /> === NetExplorer ===<br /> <br /> [http://code.google.com/p/ns-3-shop/wiki/NetExplorer | NetExplorer] is Gnome/Gtk network animation tool for NS-3. <br /> <br /> == Miscellaneous == <br /> <br /> === L2 Ethernet switch module ===<br /> <br /> * ''ns-developers post'': http://groups.google.com/group/ns-3-users/browse_thread/thread/0091ac611dde1928#<br /> * ''status'': No code yet, starting development.<br /> <br /> === Parallel simulations (2008) ===<br /> <br /> * ''summary'': ns-3 extensions for parallelization<br /> * ''wiki page'': [[Parallel Simulations]]<br /> * ''code location'': http://code.nsnam.org/pfeifer/ns-3-para/<br /> * ''status'': dormant since 2008 Google Summer of Code<br /> <br /> === Delay Box for ns-3 ===<br /> <br /> Matt Crinklaw is working on a port of ns-2 DelayBox to ns-3.<br /> * ''summary'': http://www.isi.edu/nsnam/ns/doc/node247.html (from ns-2 documentation)<br /> * ''code location'': http://freehg.org/u/mlaw<br /> * ''status'': No status update recently. Dormant.<br /> <br /> === Simulation Configuration and State Detection ===<br /> <br /> 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.<br /> <br /> [[SimulationConfiguration | Simulation Configuration]]<br /> <br /> = Build system and project infrastructure =<br /> <br /> == Modular build and package management ==<br /> <br /> This issue is being tracked (requirements and wish list) on [[App_Store_Technical_Requirements | this page]]<br /> <br /> == State of Doxygen ==<br /> <br /> Need to bring Doxygen into compliance (no errors, no warnings for missing documentation).<br /> <br /> == Buildbots ==<br /> <br /> * investigate hooking code coverage (lcov) into the report<br /> * investigate how the whole buildbot farm may be made available to a maintainer to test out a non-ns-3-dev repo. <br /> <br /> == Code contribution guidance ==<br /> <br /> Tom took action item to simplify and clarify the project code contribution guidelines (for people wishing to contribute new code to ns-3).<br /> <br /> == Samples directory ==<br /> <br /> Consider cleanup and move of samples/ directory to examples/?<br /> <br /> == Documentation ==<br /> <br /> 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 &quot;cookbook&quot; of howtos for common ns-3 tasks.<br /> <br /> == Website ==<br /> <br /> Status: INRIA is organizing some updates to the website.</div>

Sderonne