GSOC2016Projects - Revision history

Mohit: /* Test and extend our qdiscs! */

2016-02-19T07:22:25Z

Test and extend our qdiscs!

← Older revision		Revision as of 07:22, 19 February 2016
Line 198:		Line 198:
	==== Test and extend our qdiscs! ====		==== Test and extend our qdiscs! ====

	Mentors: [mailto:tomh@tomh.org Tom Henderson]		Mentors: [mailto:tomh@tomh.org Tom Henderson], [mailto:tahiliani.nitk@gmail.com Mohit P. Tahiliani]

	ns-3 is on the verge of adding a 'traffic control' layer modelled after Linux tc (see the code review issue [https://codereview.appspot.com/284530043/ here]. We have models of pfifo_fast, RED, adaptive RED, CoDel, and PIE either ready or nearly ready, but we could use more testing of them. We also need support for ECN added throughout, and could use some additional models such as [http://www.bufferbloat.net/projects/codel/wiki/Cake cake] and [https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04 fq_codel]. So there is a potentially a lot of interesting work to build on this new capability-- tell us how you might define a summer project to improve our support for modelling AQM and bufferbloat.		ns-3 is on the verge of adding a 'traffic control' layer modelled after Linux tc (see the code review issue [https://codereview.appspot.com/284530043/ here]. We have models of pfifo_fast, RED, adaptive RED, CoDel, and PIE either ready or nearly ready, but we could use more testing of them. We also need support for ECN added throughout, and could use some additional models such as [http://www.bufferbloat.net/projects/codel/wiki/Cake cake] and [https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04 fq_codel]. So there is a potentially a lot of interesting work to build on this new capability-- tell us how you might define a summer project to improve our support for modelling AQM and bufferbloat.

Tomh: /* Project Ideas */

2016-02-19T06:15:56Z

Project Ideas

@@ Line 195: / Line 195: @@
 ** [https://www.nsnam.org/doxygen/group__aodv.html AODV model in ns-3]
 ** [https://www.nsnam.org/docs/manual/html/new-modules.html Adding a new module to ns-3]
 [[Category:GSoC]]

Mohit: /* Project Ideas */

2016-02-18T19:02:40Z

Project Ideas

← Older revision		Revision as of 19:02, 18 February 2016
Line 178:		Line 178:
	** [http://www6.ietf.org/rfc/rfc4728.txt RFC 4728]		** [http://www6.ietf.org/rfc/rfc4728.txt RFC 4728]

			==== AODV version 2 (AODVv2) routing ====

			Mentors: [mailto:tahiliani.nitk@gmail.com Mohit P. Tahiliani]

			The Mobile Ad hoc Networks Working Group has worked on designing Ad hoc On-demand Distance Vector version 2 (AODVv2) for past three years. Details about AODVv2 are described in this internet draft:
			* https://datatracker.ietf.org/doc/draft-ietf-manet-aodvv2/

			AODVv2 is an important extension of AODV. Some of the mandatory features in AODV are made optional in AODVv2. Moreover, a mechanism to use multiple metric types is also incorporated in AODVv2. The goal of this project is to develop a AODVv2 model for ns-3. The pre-existing AODV model of ns-3 can be used as a reference to start this project. The project can be further extended to include support for IPv6.

			* ''Required Experience:'' C++
			* ''Bonus Experience:'' AODV standard
			* ''Interests:'' Ad-hoc routing
			* ''Difficulty:'' medium
			* ''Recommended reading:''
			** [https://tools.ietf.org/html/draft-ietf-manet-aodvv2-13 AODVv2 internet draft]
			** [https://www.nsnam.org/doxygen/group__aodv.html AODV model in ns-3]
			** [https://www.nsnam.org/docs/manual/html/new-modules.html Adding a new module to ns-3]

	[[Category:GSoC]]		[[Category:GSoC]]

Tommaso at 22:54, 11 February 2016

2016-02-11T22:54:16Z

@@ Line 163: / Line 163: @@
 * ''Recommended reading:''
 ** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]
 [[Category:GSoC]]

Tommaso: /* 802.15.4 Beacon-enabled mode */

2016-02-11T00:38:20Z

802.15.4 Beacon-enabled mode

← Older revision		Revision as of 00:38, 11 February 2016
Line 156:		Line 156:
	Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]		Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

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

Tommaso: /* 802.15.4 Bootstrap */

2016-02-11T00:38:07Z

802.15.4 Bootstrap

← Older revision		Revision as of 00:38, 11 February 2016
Line 144:		Line 144:
	Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]		Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]

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


	==== 802.15.4 Beacon-enabled mode ====		==== 802.15.4 Beacon-enabled mode ====

Tomh: /* ICCRG TCP Evaluation Suite port */

2016-02-10T22:40:51Z

ICCRG TCP Evaluation Suite port

← Older revision		Revision as of 22:40, 10 February 2016
Line 101:		Line 101:
	==== ICCRG TCP Evaluation Suite port ====		==== ICCRG TCP Evaluation Suite port ====

	Mentors: [mailto:tomh@tomh.org Tom Henderson]		Mentors: [mailto:tomh@tomh.org Tom Henderson], [mailto:tahiliani.nitk@gmail.com Mohit Tahiliani]

	The Internet Congestion Control (ICC) research group has worked on an ns-2-based TCP evaluation suite for several years. Details about this suite are described in this internet draft:		The Internet Congestion Control (ICC) research group has worked on an ns-2-based TCP evaluation suite for several years. Details about this suite are described in this internet draft:

Tommaso: /* Freshen ns-3/Click integration */

2016-02-09T22:49:05Z

Freshen ns-3/Click integration

@@ Line 79: / Line 79: @@
 Mentors: [mailto:tomh@tomh.org Tom Henderson]
-ns-3 and [https://github.com/kohler/click Click modular routing] were first integrated in an [https://www.nsnam.org/wiki/GSOC2010Click ns-3 GSoC project] from 2010.  We seek a student interested in the following tasks:  1) since 2010, Ipv4L3Protocol has continued to evolve, but Ipv4L3ClickProtocol has not kept pace with the changes.  Refactor Ipv4L3Protocol and Ipv4L3ClickProtocol so that the click-specific pieces are limited and can be maintained more easily.  2) There was an [https://www.nsnam.org/wiki/NSOC2011ClickMac/MidTermReport ns-3 2011 summer project] (not part of GSoC, but a follow-on project) to try to finish the integration with ClickMac.  We'd like to finish this off and merge it with ns-3-dev.  3) anything else that a student thinks would be useful to support regarding click and ns-3 integration.
+ns-3 and [https://github.com/kohler/click Click modular routing] were first integrated in an [https://www.nsnam.org/wiki/GSOC2010Click ns-3 GSoC project] from 2010.  We seek a student interested in the following tasks:
 ==== OpenStack and ns-3 ====

Tomh: /* Project Ideas */

2016-02-09T18:50:27Z

Project Ideas

← Older revision		Revision as of 18:50, 9 February 2016
Line 68:		Line 68:

	'''Note to students:''' These ideas are not listed in any priority order.		'''Note to students:''' These ideas are not listed in any priority order.

			==== Windows Visual Studio Community support ====

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

			ns-3 is primarily developed on Linux and OS X, and has had some unofficial Visual Studio support in the past: https://www.nsnam.org/wiki/Ns-3_on_Visual_Studio_2012. In this suggested project, the student will help ns-3 produce a maintainable Visual Studio version for the latest free version of Visual Studio (Visual Studio Community 2015). This will require not only working with the core maintainers on solving compiler compatibility issues, but also providing clear documentation for Windows users, support for [[NetAnim]] animator, support for standing up a Windows buildslave in our regression testbed, and any other things that the student feels will enhance the Windows ns-3 experience (time permitting). If you select this project idea, please tell us about your experience/ability to work with Visual Studio, and how you plan to take what has already been done for Visual Studio 2012 and improve it.

	==== Freshen ns-3/Click integration ====		==== Freshen ns-3/Click integration ====

Tomh: /* Project Ideas */

2016-02-08T17:51:16Z

Project Ideas

← Older revision		Revision as of 17:51, 8 February 2016
Line 68:		Line 68:

	'''Note to students:''' These ideas are not listed in any priority order.		'''Note to students:''' These ideas are not listed in any priority order.

			==== Freshen ns-3/Click integration ====

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

			ns-3 and [https://github.com/kohler/click Click modular routing] were first integrated in an [https://www.nsnam.org/wiki/GSOC2010Click ns-3 GSoC project] from 2010. We seek a student interested in the following tasks: 1) since 2010, Ipv4L3Protocol has continued to evolve, but Ipv4L3ClickProtocol has not kept pace with the changes. Refactor Ipv4L3Protocol and Ipv4L3ClickProtocol so that the click-specific pieces are limited and can be maintained more easily. 2) There was an [https://www.nsnam.org/wiki/NSOC2011ClickMac/MidTermReport ns-3 2011 summer project] (not part of GSoC, but a follow-on project) to try to finish the integration with ClickMac. We'd like to finish this off and merge it with ns-3-dev. 3) anything else that a student thinks would be useful to support regarding click and ns-3 integration.

			==== OpenStack and ns-3 ====

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

			OpenStack Neutron is the networking layer of [http://www.openstack.org OpenStack]. ns-3 does not have any integration yet with OpenStack. We invite project proposals that propose some level of integration of ns-3 with OpenStack. In your application, tell us why you think OpenStack should be integrated with ns-3 (what will be the useful use cases supported?) and what you think you can accomplish in a 10-week summer project.

	==== ICCRG TCP Evaluation Suite port ====		==== ICCRG TCP Evaluation Suite port ====