Gsoc2009 - Revision history

Tomh: add project concerning queues

2009-03-10T16:51:24Z

add project concerning queues

← Older revision		Revision as of 16:51, 10 March 2009
Line 67:		Line 67:
	* Mentor or proposer: Tom Henderson		* Mentor or proposer: Tom Henderson
	* Description:		* Description:

			== Advanced queues for ns-3 ==

			* Mentor or proposer: Tom Henderson
			* Description: Presently, ns-3 implements only a basic FIFO queue. We would like a student interested in different queuing disciplines and implementations to add support for more sophisticated queues, such as fair queuing, RED, RIO, etc. The first step may be to port the [http://www.isi.edu/nsnam/ns/doc/node69.html ns-2 implementations], or possibly the implementations from the [http://lartc.org/howto/ Linux routing and traffic control] project.

Craigdo at 01:18, 8 March 2009

2009-03-08T01:18:08Z

← Older revision		Revision as of 01:18, 8 March 2009
Line 3:		Line 3:
	This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

	The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave ~~amay~~ be found [http://www.nsnam.org/docs/gsoc.ppt here].		The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave may be found [http://www.nsnam.org/docs/gsoc.ppt here].

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Craigdo at 01:17, 8 March 2009

2009-03-08T01:17:45Z

← Older revision		Revision as of 01:17, 8 March 2009
Line 3:		Line 3:
	This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

	The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave amay be found [[http://www.nsnam.org/docs/gsoc.ppt \| here]].		The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave amay be found [http://www.nsnam.org/docs/gsoc.ppt here].

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Craigdo at 01:16, 8 March 2009

2009-03-08T01:16:11Z

← Older revision		Revision as of 01:16, 8 March 2009
Line 3:		Line 3:
	This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

	The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave amay be found [[~~GsocSlides~~ \| here]].		The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave amay be found [[http://www.nsnam.org/docs/gsoc.ppt \| here]].

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Craigdo at 00:57, 8 March 2009

2009-03-08T00:57:23Z

← Older revision		Revision as of 00:57, 8 March 2009
Line 3:		Line 3:
	This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

	The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave ~~are~~ [[GsocSlides \| here]]		The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave amay be found [[GsocSlides \| here]].

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Craigdo at 00:56, 8 March 2009

2009-03-08T00:56:15Z

← Older revision		Revision as of 00:56, 8 March 2009
Line 2:		Line 2:

	This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

			The ns-3 project presented at a GSoC Infosession at the University of Washington on March 5th, 2009. Slides for the short talk we gave are [[GsocSlides \| here]]

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Craigdo at 00:52, 8 March 2009

2009-03-08T00:52:40Z

← Older revision		Revision as of 00:52, 8 March 2009
Line 1:		Line 1:
	{{TOC}}		{{TOC}}

	This is the webpage for planning [http://code.google.com/soc~~/2008~~ Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.		This is the webpage for planning [http://code.google.com/soc Google Summer of Code] 2009 projects and mentors. ns-3 plans to apply for a spot in the Google Summer of Code again this year. Please list project ideas and identify possible mentors below.

	'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.		'''Disclaimer:''' There is no guarantee that ns-3 will be accepted again in GSoC 2009. We have to re-apply.

Tomh: updated GSOC ideas

2009-03-01T20:56:03Z

updated GSOC ideas

← Older revision		Revision as of 20:56, 1 March 2009
Line 43:		Line 43:
	* Mentor or proposer: Mathieu Lacage		* Mentor or proposer: Mathieu Lacage
	* Description: run multiple instances of ns-3 on multiple physical machines interconnected by an ip network, each instance is running a realtime simulation, and they can all send and receive packets to each other through UDP-based tunnels over the physical interconnection between each machine. This project requires the implementation of a UDP-based (a TCP option would be nice) tunneling mechanism implemented in a RtTunnelNetDevice which performs UDP encapsulation of outgoing packets and UDP decapsulation of incoming packets. Each simulator instance will require a map from simulated IP addresses to physical IP+port numbers. Simulation setup, initialization, and configuration should be done with RPYC (http://rpyc.wikidot.com/). The initial implementation should be able to run on a single physical host with multiple instances of the RPYC daemon to control the multiple instances of the simulator on this single host. The student will be given access to a cluster to test and implement deployment on multiple physical hosts.		* Description: run multiple instances of ns-3 on multiple physical machines interconnected by an ip network, each instance is running a realtime simulation, and they can all send and receive packets to each other through UDP-based tunnels over the physical interconnection between each machine. This project requires the implementation of a UDP-based (a TCP option would be nice) tunneling mechanism implemented in a RtTunnelNetDevice which performs UDP encapsulation of outgoing packets and UDP decapsulation of incoming packets. Each simulator instance will require a map from simulated IP addresses to physical IP+port numbers. Simulation setup, initialization, and configuration should be done with RPYC (http://rpyc.wikidot.com/). The initial implementation should be able to run on a single physical host with multiple instances of the RPYC daemon to control the multiple instances of the simulator on this single host. The student will be given access to a cluster to test and implement deployment on multiple physical hosts.

			== Router model for ns-3 ==

			* Mentor or proposer: Tom Henderson
			* Description: Many simulators including ns-3 fail to provide high fidelity models of Internet routers. For instance, intra-device latencies and input queuing behavior are not modeled. This project would work to adapt some results on empirical router testing into a new Router node type for ns-3. For more details of the basic idea, see [http://www.cs.ucsb.edu/~rchertov/papers/infocom08.pdf].

			== Click modular router for ns-3 ==

			* Mentor or proposer: Tom Henderson
			* Description: The Click modular router is a popular router implementation for routing research. This project would port and enable ns-3 simulations to use the Click modular router [http://read.cs.ucla.edu/click/]. There is previous experience in doing this for ns-2.

			== Large scale topology for ns-3 ==

			* Mentor or proposer: Tom Henderson
			* Description: ns-2 has previously incorporated support for various topology generators (see http://www.isi.edu/nsnam/ns/ns-topogen.html), but these are not supported in ns-3 yet. The basic idea is to write scripts that turn the output of these generators into simulation scripts. In addition, this project could look at the problem of assigning IP addresses coherently to such topologies. [http://www.cs.utah.edu/flux/papers/ipassign-ftn2005-04-base.html Recent work] by the Emulab project may be portable.

			== Emulab/ns-3 integration ==

			* Mentor or proposer: Tom Henderson
			* Description: [http://www.emulab.net Emulab] is a leading testbed for Internet research. Emulab experiments are described in tcl like ns-2 scripts. Emulab also uses ns-2 emulation. This project would attempt to integrate Emulab with ns-3. There would be two main goals. 1) Test and document how ns-3 emulation mode could be used in emulab instead of ns-2. Compare its features and performance. 2) Investigate whether Emulab scripting could be cut over to Python/ns-3 or whether ns-3 needs to generate Tcl for Emulab; attempt to do this integration.
			* Mentor or proposer: Tom Henderson
			* Description:

Mathieu.lacage at 12:25, 23 February 2009

2009-02-23T12:25:43Z

← Older revision		Revision as of 12:25, 23 February 2009
Line 38:		Line 38:
	* Mentor or proposer: Tom Henderson (the SNS author Kevin Walsh will help if needed)		* Mentor or proposer: Tom Henderson (the SNS author Kevin Walsh will help if needed)
	* Description: Several years ago, [http://www.cs.cornell.edu/people/egs/sns/ staged network simulations (SNS)] were introduced to ns-2, via a patch of the wireless models. This yielded a dramatic improvement in ns-2 wireless simulations. This project suggests to try to incorporate these techniques into the Wifi model. The student doing this will probably learn a lot about Wifi and about profiling code performance.		* Description: Several years ago, [http://www.cs.cornell.edu/people/egs/sns/ staged network simulations (SNS)] were introduced to ns-2, via a patch of the wireless models. This yielded a dramatic improvement in ns-2 wireless simulations. This project suggests to try to incorporate these techniques into the Wifi model. The student doing this will probably learn a lot about Wifi and about profiling code performance.

			== Realtime Distributed simulation ==

			* Mentor or proposer: Mathieu Lacage
			* Description: run multiple instances of ns-3 on multiple physical machines interconnected by an ip network, each instance is running a realtime simulation, and they can all send and receive packets to each other through UDP-based tunnels over the physical interconnection between each machine. This project requires the implementation of a UDP-based (a TCP option would be nice) tunneling mechanism implemented in a RtTunnelNetDevice which performs UDP encapsulation of outgoing packets and UDP decapsulation of incoming packets. Each simulator instance will require a map from simulated IP addresses to physical IP+port numbers. Simulation setup, initialization, and configuration should be done with RPYC (http://rpyc.wikidot.com/). The initial implementation should be able to run on a single physical host with multiple instances of the RPYC daemon to control the multiple instances of the simulator on this single host. The student will be given access to a cluster to test and implement deployment on multiple physical hosts.

Fw: /* Network Simulation Cradle for IPv4 */

2009-02-21T00:07:35Z

Network Simulation Cradle for IPv4

← Older revision		Revision as of 00:07, 21 February 2009
Line 24:		Line 24:
	== Network Simulation Cradle for IPv4 ==		== Network Simulation Cradle for IPv4 ==

	* Mentor or proposer: Tom Henderson		* Mentor or proposer: Tom Henderson, Florian Westphal
	* Description: As part of last year's Google Summer of Code, Florian Westphal ported Sam Jansen's [http://research.wand.net.nz/software/nsc.php Network Simulation Cradle] to ns-3. This provides the ability to run Linux TCP code over ns-3's IPv4 stack. However, the port could be made more complete by extending it to totally cover the Linux TCP/IPv4 stack. A good summer project would be to add IPv4 support to NSC, and we have the benefit of a few mentors in this area for any such work.		* Description: As part of last year's Google Summer of Code, Florian Westphal ported Sam Jansen's [http://research.wand.net.nz/software/nsc.php Network Simulation Cradle] to ns-3. This provides the ability to run Linux TCP code over ns-3's IPv4 stack. However, the port could be made more complete by extending it to totally cover the Linux TCP/IPv4 stack. A good summer project would be to add IPv4 support to NSC, and we have the benefit of a few mentors in this area for any such work. The two main areas here are:
			* enable nsc to create multiple interfaces, assign addresses, set up routing table, etc.
			* extend/rework ns-3 to use these features.

	== Protolib and Agent-J for ns-3 ==		== Protolib and Agent-J for ns-3 ==