<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.nsnam.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tazaki</id>
	<title>Nsnam - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.nsnam.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tazaki"/>
	<link rel="alternate" type="text/html" href="https://www.nsnam.org/wiki/Special:Contributions/Tazaki"/>
	<updated>2026-04-05T20:42:56Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.8</generator>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=DevelMeetingMay2015&amp;diff=9515</id>
		<title>DevelMeetingMay2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=DevelMeetingMay2015&amp;diff=9515"/>
		<updated>2015-05-12T14:34:03Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Attendees */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{TOC}}&lt;br /&gt;
&lt;br /&gt;
= Location and Schedule =&lt;br /&gt;
&lt;br /&gt;
The meeting will occur Friday, May 15 at CTTC's facilities as part of the [https://www.nsnam.org/overview/wns3/wns3-2015/local-information/ ns-3 annual meeting].&lt;br /&gt;
&lt;br /&gt;
A more detailed schedule will be posted at a later date but the schedule will be primarily driven by who is attending and what everyone proposes to discuss.&lt;br /&gt;
&lt;br /&gt;
= Remote attendance =&lt;br /&gt;
&lt;br /&gt;
We will possibly run a Google Hangout; please email [mailto:tomh@tomh.org tomh@tomh.org] if interested to be invited.&lt;br /&gt;
&lt;br /&gt;
= Attendees =&lt;br /&gt;
&lt;br /&gt;
Please add your name here if you intend to attend, and which days.&lt;br /&gt;
&lt;br /&gt;
* Tom Henderson&lt;br /&gt;
* Peter Barnes&lt;br /&gt;
* Nicola Baldo&lt;br /&gt;
* Hajime Tazaki&lt;br /&gt;
&lt;br /&gt;
= Suggested agenda/topics =&lt;br /&gt;
&lt;br /&gt;
Please list suggested discussion topics below and we will build a schedule at a later date.  Please also suggest 'read-ahead' items as needed.&lt;br /&gt;
&lt;br /&gt;
# '''Packaging and distribution.'''  For a few release cycles now, there have been Debian/Ubuntu packages (most recently for ns-3.17:  http://packages.ubuntu.com/source/vivid/ns3).  &lt;br /&gt;
#* What should we do to help downstream maintainers?  &lt;br /&gt;
#* How to get bake/DCE into these?   &lt;br /&gt;
#* How to allow such distributions to evolve?  &lt;br /&gt;
#* What about Fedora/RHEL (which Vedran has raised in the past)?&lt;br /&gt;
#* What about distributing Docker containers and Live DVDs?&lt;br /&gt;
# '''Documenting the maintenance status of our modules.'''  We can do a better job documenting the scope and maintenance status (list of open bugs that users should be aware of) of our modules.  Recent work on this regarding wifi could be extended to other modules-- need to discuss further with other maintainers.&lt;br /&gt;
&lt;br /&gt;
= Meeting Notes =&lt;br /&gt;
&lt;br /&gt;
Will be posted at a later date.&lt;br /&gt;
&lt;br /&gt;
[[Category:DevelMeeting]]&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9512</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9512"/>
		<updated>2015-05-12T13:08:50Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Additional files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pptx pptx])'''(09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* '''[http://www.slideshare.net/hajimetazaki/wns3-15dcetutorial slides]'''(11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
* DCE tutorial&lt;br /&gt;
** The tutorial basically uses the same Live-CD, which is provided below, but also uses more code: if you want to try during the tutorial, you can prepare in advance, following the instruction below.&lt;br /&gt;
** 1. additional git repositories&lt;br /&gt;
*** Because the size of this additional code is large and you may not able to download to the root directory of Live-CD image, so you need to configure an additional (virtual) disk image, which can be mounted to /mnt, then download the code to the additional partition.&lt;br /&gt;
 git clone --depth=1 https://github.com/direct-code-execution/net-next-sim -b wns3-2015&lt;br /&gt;
 git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git&lt;br /&gt;
&lt;br /&gt;
:* 2. an additional ns-3 script&lt;br /&gt;
 wget  https://gist.githubusercontent.com/thehajime/5e9e05ea2df08141ae47/raw/a23387aa97b58bc13ccf96a1a208ddd387c9646f/nat-dce-tcp-ns3-nsc-comparison.cc&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;br /&gt;
&lt;br /&gt;
Notes collected from the Monday training.&lt;br /&gt;
&lt;br /&gt;
* How to use the 'subdir' in scratch/ is not well documented&lt;br /&gt;
&lt;br /&gt;
* How to use bake to manage other library dependencies is not well documented&lt;br /&gt;
&lt;br /&gt;
* RealtimeSimulatorImpl for the sample-simulator.cc program does not automatically stop anymore&lt;br /&gt;
&lt;br /&gt;
* Need better figure to document random variable stream/substream concepts.&lt;br /&gt;
&lt;br /&gt;
* RngRun documentation string needs fixing&lt;br /&gt;
&lt;br /&gt;
* What is the max run number?  It is a uint64_t.&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9511</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9511"/>
		<updated>2015-05-12T13:08:04Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Tuesday May 12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pptx pptx])'''(09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* '''[http://www.slideshare.net/hajimetazaki/wns3-15dcetutorial slides]'''(11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;br /&gt;
&lt;br /&gt;
Notes collected from the Monday training.&lt;br /&gt;
&lt;br /&gt;
* How to use the 'subdir' in scratch/ is not well documented&lt;br /&gt;
&lt;br /&gt;
* How to use bake to manage other library dependencies is not well documented&lt;br /&gt;
&lt;br /&gt;
* RealtimeSimulatorImpl for the sample-simulator.cc program does not automatically stop anymore&lt;br /&gt;
&lt;br /&gt;
* Need better figure to document random variable stream/substream concepts.&lt;br /&gt;
&lt;br /&gt;
* RngRun documentation string needs fixing&lt;br /&gt;
&lt;br /&gt;
* What is the max run number?  It is a uint64_t.&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9510</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9510"/>
		<updated>2015-05-12T12:11:45Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Tuesday May 12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pptx pptx])'''(09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* '''[http://www.slideshare.net/hajimetazaki/wns3-15dcetutorial slides]'''(11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
** The tutorial basically uses the same Live-CD, which is provided below, but also uses more code: if you want to try during the tutorial, you can prepare in advance, following the instruction below.&lt;br /&gt;
** 1. additional git repositories&lt;br /&gt;
*** Because the size of this additional code is large and you may not able to download to the root directory of Live-CD image, so you need to configure an additional (virtual) disk image, which can be mounted to /mnt, then download the code to the additional partition.&lt;br /&gt;
 git clone --depth=1 https://github.com/direct-code-execution/net-next-sim -b wns3-2015&lt;br /&gt;
 git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git&lt;br /&gt;
&lt;br /&gt;
:* 2. an additional ns-3 script&lt;br /&gt;
 wget  https://gist.githubusercontent.com/thehajime/5e9e05ea2df08141ae47/raw/a23387aa97b58bc13ccf96a1a208ddd387c9646f/nat-dce-tcp-ns3-nsc-comparison.cc&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;br /&gt;
&lt;br /&gt;
Notes collected from the Monday training.&lt;br /&gt;
&lt;br /&gt;
* How to use the 'subdir' in scratch/ is not well documented&lt;br /&gt;
&lt;br /&gt;
* How to use bake to manage other library dependencies is not well documented&lt;br /&gt;
&lt;br /&gt;
* RealtimeSimulatorImpl for the sample-simulator.cc program does not automatically stop anymore&lt;br /&gt;
&lt;br /&gt;
* Need better figure to document random variable stream/substream concepts.&lt;br /&gt;
&lt;br /&gt;
* RngRun documentation string needs fixing&lt;br /&gt;
&lt;br /&gt;
* What is the max run number?  It is a uint64_t.&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9506</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9506"/>
		<updated>2015-05-12T07:13:21Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Tuesday May 12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/WNS3-Distributed-Simulation-2015-05-13.pptx pptx])'''(09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* '''[https://www.nsnam.org/mediawiki/images/b/b1/Wns3-15-dce-tutorial.pdf slides]'''(11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
** The tutorial basically uses the same Live-CD, which is provided below, but also uses more code: if you want to try during the tutorial, you can prepare in advance, following the instruction below.&lt;br /&gt;
** 1. additional git repositories&lt;br /&gt;
*** Because the size of this additional code is large and you may not able to download to the root directory of Live-CD image, so you need to configure an additional (virtual) disk image, which can be mounted to /mnt, then download the code to the additional partition.&lt;br /&gt;
 git clone --depth=1 https://github.com/direct-code-execution/net-next-sim -b wns3-2015&lt;br /&gt;
 git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git&lt;br /&gt;
&lt;br /&gt;
:* 2. an additional ns-3 script&lt;br /&gt;
 wget  https://gist.githubusercontent.com/thehajime/5e9e05ea2df08141ae47/raw/a23387aa97b58bc13ccf96a1a208ddd387c9646f/nat-dce-tcp-ns3-nsc-comparison.cc&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=File:Wns3-15-dce-tutorial.pdf&amp;diff=9504</id>
		<title>File:Wns3-15-dce-tutorial.pdf</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=File:Wns3-15-dce-tutorial.pdf&amp;diff=9504"/>
		<updated>2015-05-12T07:10:21Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9502</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9502"/>
		<updated>2015-05-11T13:29:47Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Tuesday May 12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* (09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* (11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
** The tutorial basically uses the same Live-CD, which is provided below, but also uses more code: if you want to try during the tutorial, you can prepare in advance, following the instruction below.&lt;br /&gt;
** 1. additional git repositories&lt;br /&gt;
*** Because the size of this additional code is large and you may not able to download to the root directory of Live-CD image, so you need to configure an additional (virtual) disk image, which can be mounted to /mnt, then download the code to the additional partition.&lt;br /&gt;
 git clone --depth=1 https://github.com/direct-code-execution/net-next-sim -b wns3-2015&lt;br /&gt;
 git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git&lt;br /&gt;
&lt;br /&gt;
:* 2. an additional ns-3 script&lt;br /&gt;
 wget  https://gist.githubusercontent.com/thehajime/5e9e05ea2df08141ae47/raw/a23387aa97b58bc13ccf96a1a208ddd387c9646f/nat-dce-tcp-ns3-nsc-comparison.cc&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9501</id>
		<title>AnnualTraining2015</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=AnnualTraining2015&amp;diff=9501"/>
		<updated>2015-05-11T13:25:16Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Tuesday May 12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
This is the wiki page for the ns-3 training sessions being conducted from 11-12 May, 2015 in Barcelona.&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
The contacts are [mailto:tomh@tomh.org Tom Henderson] and [mailto:nbaldo@cttc.es Nicola Baldo]; email one of them if you have any questions.&lt;br /&gt;
&lt;br /&gt;
The flyer is posted here:  https://www.nsnam.org/wp-content/uploads/2015/04/ns-3-training-2015.pdf&lt;br /&gt;
&lt;br /&gt;
We plan to run from 0900-1800 each day.  Coffee will be provided; participants will need to go to the canteen and purchase their own lunch during the lunch break.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
Slides will be linked from these session descriptions as they become available.&lt;br /&gt;
&lt;br /&gt;
=== Monday May 11 ===&lt;br /&gt;
&lt;br /&gt;
The goal of this session is a comprehensive overview of the simulator (what we can fit into a day).  The instructors will be mainly Tom Henderson.&lt;br /&gt;
&lt;br /&gt;
Sessions will run from 0900-1030, 1100-1230, 1400-1600, 1630-1800.&lt;br /&gt;
&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part1.pptx pptx])''' ns-3 survey and overview tutorial, software organization, documentation, build system&lt;br /&gt;
* '''([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pdf pdf]) ([http://www.nsnam.org/tutorials/consortium15/ns-3-training-part2.pptx pptx])''' ns-3 software core, running of simulations, construction of a basic network simulation, construction of a new protocol model, and development practices using ns-3.  Extracting and visualizing data from ns-3 simulations, including the flow monitor,network animator NetAnim, Python-based visualizer, and the ns-3 tracing system.&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version1.cc program wns3-version1.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version2.cc program wns3-version2.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version3.cc program wns3-version3.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/wns3-version4.cc program wns3-version4.cc]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.h model file reorder-queue.h]&lt;br /&gt;
** [http://www.nsnam.org/tutorials/consortium15/reorder-queue.cc model file reorder-queue.cc]&lt;br /&gt;
&lt;br /&gt;
=== Tuesday May 12 ===&lt;br /&gt;
&lt;br /&gt;
This will consist of special topic tutorials taught by experts in each field.&lt;br /&gt;
* (09:00-10:30) Large-scale, distributed simulations with ns-3 (instructor:  Peter Barnes)&lt;br /&gt;
* (11:00-12:30)An introduction to the Direct Code Execution (DCE) environment, enabling users to use real application and Linux networking code in ns-3 (instructor:  Hajime Tazaki)&lt;br /&gt;
** The tutorial basically uses the same Live-CD, which is provided below, but also uses more code: if you want to try during the tutorial, you can prepare in advance, following the instruction below.&lt;br /&gt;
** 1. additional git repositories&lt;br /&gt;
*** Because the size of this additional code is large and you may not able to download to the root directory of Live-CD image, so you need to configure an additional (virtual) disk image, which can be mounted to /mnt, then download the code to the additional partition.&lt;br /&gt;
 git clone --depth=1 https://github.com/direct-code-execution/net-next-sim&lt;br /&gt;
 git clone --depth=1 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git&lt;br /&gt;
&lt;br /&gt;
:* 2. an additional ns-3 script&lt;br /&gt;
 wget  https://gist.githubusercontent.com/thehajime/5e9e05ea2df08141ae47/raw/a23387aa97b58bc13ccf96a1a208ddd387c9646f/nat-dce-tcp-ns3-nsc-comparison.cc&lt;br /&gt;
* Lunch break&lt;br /&gt;
* (14:00-16:00) A survey of the LTE models, including model architecture, propagation models, LTE Radio Protocol Stack and EPC model. (instructor:  Nicola Baldo)&lt;br /&gt;
* '''[http://www.nsnam.org/tutorials/consortium15/Vehicular-Comms.pptx slides]'''(16:30-18:00) A tutorial on vehicular communication simulations, including mobility, WiFi and WAVE models, and propagation.  (instructor:  Konstantinos Katsaros)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
Nothing is strictly required, but working through the [http://www.nsnam.org/docs/release/3.22/tutorial/html/index.html ns-3 tutorial] should be helpful, if you haven't already.&lt;br /&gt;
&lt;br /&gt;
You do not need to install anything to attend the training, but the below instructions are provided for those who may want to follow along.&lt;br /&gt;
&lt;br /&gt;
=== Installation of ns-3 to your local system ===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Installation]] page on our wiki for per-system package requirements if you want to install ns-3, and follow instructions at [https://www.nsnam.org/docs/release/3.22/tutorial/html/getting-started.html this tutorial link] on how to download ns-3.&lt;br /&gt;
&lt;br /&gt;
Note that the minimal requirements for working from the command line are a recent C++ compiler (g++ or clang), and a Python (version 2) installation.  The additional packages enable additional optional simulation features but can be skipped until needed.&lt;br /&gt;
&lt;br /&gt;
=== Trying ns-3 on a Live ISO image ===&lt;br /&gt;
&lt;br /&gt;
A 32-bit Ubuntu 14.04 Live DVD (ISO) is posted for download at [https://www.nsnam.org/tutorials/consortium15/ns-3-training-may-2015.iso this link] and will also be available on flash and DVD media at the training session.  The ISO has prerequisite packages pre-installed and a recent copy of ns-3 source code.&lt;br /&gt;
&lt;br /&gt;
You may want to use this ISO file with a virtual machine tool such as VMware or VirtualBox.&lt;br /&gt;
&lt;br /&gt;
* sha1 checksum of the ISO image: 47a1ca78803a0f31ad8c764b47fc244cf2a28f94&lt;br /&gt;
* file size of the download:  4 GB&lt;br /&gt;
* '''username:''' ns-3&lt;br /&gt;
* '''password:''' ns-3&lt;br /&gt;
* recommended virtual machine resources (if you install to a VM):  40 GB HDD, 3 GB memory&lt;br /&gt;
&lt;br /&gt;
This is a Live ISO image that can be booted repeatedly without saving state, or can be installed to a virtual or real drive.  The [https://launchpad.net/~nemh/+archive/ubuntu/systemback Systemback] utility was used to create the image, and can be used to install the system as well.  To install, select the green icon in the panel to bring up the below dialog box, fill in the account information (for the system to be created) and then hit Next and follow the instructions.&lt;br /&gt;
&lt;br /&gt;
[[File:Systemback-install.png]]&lt;br /&gt;
&lt;br /&gt;
Please read the README in the top level directory.&lt;br /&gt;
&lt;br /&gt;
== Additional files ==&lt;br /&gt;
&lt;br /&gt;
Links to any additional example files produced for the training (outside of the ns-3 release) will be posted here.&lt;br /&gt;
&lt;br /&gt;
== Questions and Answers ==&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.3&amp;diff=8376</id>
		<title>Dce-1.3</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.3&amp;diff=8376"/>
		<updated>2014-02-18T15:37:55Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.3 release =&lt;br /&gt;
* xxth April, 2014: dce-1.3 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Emilio&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* create jenkins test job for 1.3&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.3&amp;diff=8375</id>
		<title>Dce-1.3</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.3&amp;diff=8375"/>
		<updated>2014-02-18T15:37:40Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: Created page with &amp;quot;= Schedule for 1.3 release = * xxth April, 2014: dce-1.3 release  = Bugs being worked = * 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.3 release =&lt;br /&gt;
* xxth April, 2014: dce-1.3 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Emilio&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* create jenkins test job for 1.3&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;br /&gt;
&lt;br /&gt;
WikiEditorWikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8374</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8374"/>
		<updated>2014-02-18T15:34:35Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* future items */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* [[dce-1.1]] August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
* [[dce-1.3]] April 2014&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/daily-dce/ Jenkins] nigthly build, regression. valgrind will be implemented soon.&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/ns-3-dce-dev/ Code coverage]&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*&amp;lt;s&amp;gt;sctp (Bug 1827) &amp;lt;/s&amp;gt;&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*&amp;lt;s&amp;gt;ipv6 linux stack helper (Bug 1713)&amp;lt;/s&amp;gt;&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8373</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8373"/>
		<updated>2014-02-18T15:33:38Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Milestone */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* [[dce-1.1]] August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
* [[dce-1.3]] April 2014&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/daily-dce/ Jenkins] nigthly build, regression. valgrind will be implemented soon.&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/ns-3-dce-dev/ Code coverage]&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*sctp&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*ipv6 linux stack helper&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8372</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=8372"/>
		<updated>2014-02-18T15:33:08Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* [[dce-1.1]] August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
* [[dce-1.3]] April 2014&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/daily-dce/ Jenkins] nigthly build, regression. valgrind will be implemented soon.&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/ns-3-dce-dev/ Code coverage]&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*sctp&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*ipv6 linux stack helper&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7872</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7872"/>
		<updated>2013-09-01T12:52:57Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt;1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt; update jenkins test script &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; update doc at nsnam.org/docs/ &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; put stable versions/revisions to bakeconf.xml &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7871</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7871"/>
		<updated>2013-09-01T12:52:20Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt;1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7870</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7870"/>
		<updated>2013-09-01T12:51:38Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt;1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7869</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7869"/>
		<updated>2013-09-01T12:50:59Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs not merged in this release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt;1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7868</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7868"/>
		<updated>2013-09-01T12:50:42Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs being worked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt;1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
WikiEditor&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7776</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7776"/>
		<updated>2013-07-30T08:06:58Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7732</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7732"/>
		<updated>2013-07-18T00:53:52Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs being worked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime&lt;br /&gt;
* 1735 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1735 bittorrent example is not working] Hajime&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7731</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7731"/>
		<updated>2013-07-18T00:15:01Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs being worked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] (Only early version) Hajime&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7730</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7730"/>
		<updated>2013-07-18T00:14:44Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs not merged in this release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] Hajime&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7729</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7729"/>
		<updated>2013-07-18T00:14:11Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] Hajime&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7728</id>
		<title>Dce-1.1</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.1&amp;diff=7728"/>
		<updated>2013-07-18T00:13:45Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: Created page with &amp;quot;= Schedule for 1.1 release = * 31th July, 2013: new feature freeze * (2weeks before release, TBD): code freeze * ?? August, 2013: dce-1.1 release  = Supported/Unsupported feat...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.1 release =&lt;br /&gt;
* 31th July, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* ?? August, 2013: dce-1.1 release&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1598 - [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1598 include tracing system for kernel code] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* update jenkins test script&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* update doc at nsnam.org/docs/&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7727</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7727"/>
		<updated>2013-07-18T00:07:48Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Milestone */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* [[dce-1.1]] August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/daily-dce/ Jenkins] nigthly build, regression. valgrind will be implemented soon.&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/ns-3-dce-dev/ Code coverage]&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*sctp&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*ipv6 linux stack helper&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7596</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7596"/>
		<updated>2013-05-15T05:36:14Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;14th May, 2013: dce-1.0 release&amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1449: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1449 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1449:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;nsnam.org/doc/dce&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;put stable versions/revisions to bakeconf.xml&amp;lt;/s&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7595</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7595"/>
		<updated>2013-05-15T05:35:57Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Schedule for 1.0 release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;14th May, 2013: dce-1.0 release&amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1449: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1449 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1449:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* &amp;lt;s&amp;gt;put stable versions/revisions to bakeconf.xml&amp;lt;/s&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7575</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7575"/>
		<updated>2013-05-08T05:16:43Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* development support features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* dce-1.1 August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/daily-dce/ Jenkins] nigthly build, regression. valgrind will be implemented soon.&lt;br /&gt;
* [http://ns-3-dce.cloud.wide.ad.jp/jenkins/job/ns-3-dce-dev/ Code coverage]&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*sctp&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*ipv6 linux stack helper&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7574</id>
		<title>Dce release schedule</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce_release_schedule&amp;diff=7574"/>
		<updated>2013-05-08T05:13:26Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* future items */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page describes the basic information of the release process of ns-3-dce module.&lt;br /&gt;
&lt;br /&gt;
= Release Policy =&lt;br /&gt;
== Release Decision ==&lt;br /&gt;
Each DCE release satisfies the following requirements.&lt;br /&gt;
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&amp;amp;bug_status=NEW&amp;amp;bug_status=ASSIGNED&amp;amp;bug_status=REOPENED&amp;amp;product=dce&amp;amp;list_id=3826 bugzilla (dce)]&lt;br /&gt;
* Pass all tests by test.py&lt;br /&gt;
* (Optional) Pass all tests with valrgrind (test.py -g)&lt;br /&gt;
&lt;br /&gt;
== Release Cycle ==&lt;br /&gt;
&lt;br /&gt;
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.&lt;br /&gt;
&lt;br /&gt;
== Numbering (versioning) ==&lt;br /&gt;
DCE will have its own version number, tagged at release points into ns-3-dce repository. &lt;br /&gt;
* tag manner:  dce-x.y(-RCz)&lt;br /&gt;
&lt;br /&gt;
== Release style ==&lt;br /&gt;
The version of DCE release is handled by using bake.&lt;br /&gt;
&lt;br /&gt;
== Sub-modules (quagga/umip) operations ==&lt;br /&gt;
DCE is also able to have extensions, so-called &amp;quot;sub-modules&amp;quot;. The sub-modules are located under &amp;quot;myscripts&amp;quot; directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.&lt;br /&gt;
&lt;br /&gt;
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.&lt;br /&gt;
&lt;br /&gt;
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.&lt;br /&gt;
&lt;br /&gt;
== Supported platform ==&lt;br /&gt;
(TBD)&lt;br /&gt;
&lt;br /&gt;
= Code =&lt;br /&gt;
* DCE core module: http://code.nsnam.org/ns-3-dce&lt;br /&gt;
* DCE Linux module: http://github.com/thehajime/net-next-sim&lt;br /&gt;
&lt;br /&gt;
= Milestone =&lt;br /&gt;
* [[dce-1.0]] April 2013&lt;br /&gt;
* dce-1.1 August 2013&lt;br /&gt;
* dce-1.2 December 2013&lt;br /&gt;
&lt;br /&gt;
= development support features =&lt;br /&gt;
* jenkins (regression/valgrind)&lt;br /&gt;
* coverage (with Linux)&lt;br /&gt;
&lt;br /&gt;
= future items =&lt;br /&gt;
*&amp;lt;s&amp;gt;DCE cradle (Bug 1499) &amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*Elf-loader issue (Bug 1513)&lt;br /&gt;
*&amp;lt;s&amp;gt;mptcp&amp;lt;/s&amp;gt; dce-1.0&lt;br /&gt;
*sctp&lt;br /&gt;
*Linux 802.15.4&lt;br /&gt;
*ipv6 linux stack helper&lt;br /&gt;
*traces for arbitrary code (Bug 1598)&lt;br /&gt;
*python binding (Bug 1455)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7573</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7573"/>
		<updated>2013-05-08T05:12:05Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1449: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1449 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1449:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* &amp;lt;s&amp;gt;put stable versions/revisions to bakeconf.xml&amp;lt;/s&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7572</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7572"/>
		<updated>2013-05-08T05:11:24Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Pending code review */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1449: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1449 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1449:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7571</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7571"/>
		<updated>2013-05-08T05:10:39Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs being worked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1449: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1449 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7549</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7549"/>
		<updated>2013-04-22T05:00:47Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
* fix valgrind errors (due to so many errors; postponed to future development)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7548</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7548"/>
		<updated>2013-04-22T04:59:41Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* &amp;lt;s&amp;gt;test with document (quick start guide, user's guide)&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;update web page (http://www.nsnam.org/projects/direct-code-execution/)&amp;lt;/s&amp;gt;&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7547</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7547"/>
		<updated>2013-04-22T04:58:57Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Schedule for 1.0 release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;30th March, 2013: new feature freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;(2weeks before release, TBD): code freeze&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;22nd, April, 2013: RC-1 &amp;lt;/s&amp;gt;&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7499</id>
		<title>GSOC2013Projects</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7499"/>
		<updated>2013-04-09T01:25:50Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* High performance ns-3 emulation with Direct NIC Access (2) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]&lt;br /&gt;
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]&lt;br /&gt;
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]&lt;br /&gt;
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]&lt;br /&gt;
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]&lt;br /&gt;
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]&lt;br /&gt;
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]&lt;br /&gt;
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]&lt;br /&gt;
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]&lt;br /&gt;
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net&lt;br /&gt;
&lt;br /&gt;
= GSoC 2013 Ideas =&lt;br /&gt;
&lt;br /&gt;
This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.&lt;br /&gt;
&lt;br /&gt;
GSOC 2012 Timeline is:&lt;br /&gt;
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.&lt;br /&gt;
* March 29 - 19:00 UTC: Mentoring organization application deadline.&lt;br /&gt;
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.&lt;br /&gt;
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.&lt;br /&gt;
* April 22 - 19:00 UTC: Student application period opens.&lt;br /&gt;
* May 3 - 19:00 UTC: Student application deadline.&lt;br /&gt;
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013&lt;br /&gt;
&lt;br /&gt;
While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8. &lt;br /&gt;
&lt;br /&gt;
== About the ns-3 project ==&lt;br /&gt;
&lt;br /&gt;
ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011).  ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained.  The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.&lt;br /&gt;
&lt;br /&gt;
Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson].  The project has participated in past GSoCs during 2008-10 and 2012.&lt;br /&gt;
&lt;br /&gt;
Mentors will be paired with students based on the projects that are selected.  Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring.  Prospective mentors should notify Lalith Suresh of interest.  Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
For students interested in applying to ns-3 for GSOC, go through the following list to get started:&lt;br /&gt;
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].&lt;br /&gt;
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].&lt;br /&gt;
* Look through our ideas list below to see if you find a project that interests you.&lt;br /&gt;
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.&lt;br /&gt;
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.&lt;br /&gt;
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Each project idea within a particular priority has been tagged with the following properties:&lt;br /&gt;
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.&lt;br /&gt;
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.&lt;br /&gt;
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.&lt;br /&gt;
* ''Difficulty:'' easy, medium or difficult&lt;br /&gt;
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Guidelines for project ideas =&lt;br /&gt;
&lt;br /&gt;
For mentors who're adding project ideas to the list below, please ensure that:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.&lt;br /&gt;
&lt;br /&gt;
= Project Ideas =&lt;br /&gt;
&lt;br /&gt;
=== Vehicular Ad-hoc Networks ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]&lt;br /&gt;
&lt;br /&gt;
* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:&lt;br /&gt;
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.&lt;br /&gt;
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)&lt;br /&gt;
# higher layers: nothing specific to WAVE is currently available.&lt;br /&gt;
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).&lt;br /&gt;
** ''Required experience:'' C++.&lt;br /&gt;
** ''Bonus experience:'' Wireless networking, WAVE.&lt;br /&gt;
** ''Interests:'' Wireless networking, VANETs.&lt;br /&gt;
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.&lt;br /&gt;
** ''Recommended reading''&lt;br /&gt;
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11&lt;br /&gt;
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945&lt;br /&gt;
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16&lt;br /&gt;
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968&lt;br /&gt;
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Energy Model ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' ns-3 Energy model&lt;br /&gt;
** ''Interests:'' WSN, Battery discharge&lt;br /&gt;
** ''Difficulty:'' easy&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes] &lt;br /&gt;
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Bootstrap ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Beacon-enabled mode ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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. &lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Simulating the Internet of Things in NS-3 === &lt;br /&gt;
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]&lt;br /&gt;
&lt;br /&gt;
In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.&lt;br /&gt;
** ''Required experience'' : C++&lt;br /&gt;
** ''Bonus experience'' : NS-2, WSN, Matlab&lt;br /&gt;
** ''Interests'' : ZB, embedded, wireless, sensor networks&lt;br /&gt;
** ''Difficulty'' : medium&lt;br /&gt;
** ''Recommended reading'' :&lt;br /&gt;
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]&lt;br /&gt;
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]&lt;br /&gt;
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3&lt;br /&gt;
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3&lt;br /&gt;
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)&lt;br /&gt;
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY&lt;br /&gt;
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested. &lt;br /&gt;
** ''Required Experience:'' C++, IPv6, RPL&lt;br /&gt;
** ''Bonus Experience:'' WSN networking&lt;br /&gt;
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression &lt;br /&gt;
** ''Difficulty:'' hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals&lt;br /&gt;
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== RPL protocol Metric and Constraints ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' RPL protocol&lt;br /&gt;
** ''Interests:'' WSN, routing &lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPv6 stack validation and improvements ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):&lt;br /&gt;
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].&lt;br /&gt;
*# Flow Monitor module does not work on the IPv6 stack&lt;br /&gt;
*# FlowLabel header field is not currenly used&lt;br /&gt;
*# IPSec is not supported&lt;br /&gt;
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.&lt;br /&gt;
** ''Required Experience:'' C++, TCP/IP networking&lt;br /&gt;
** ''Bonus Experience:'' IPv6 protocols&lt;br /&gt;
** ''Interests:'' IPv6 internetworking&lt;br /&gt;
** ''Difficulty:'' easy / medium, depending on the features implemented&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]&lt;br /&gt;
*** ns-3 Flowmon module documentation&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Multicast IPv6 traffic support ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)&lt;br /&gt;
** ''Interests:'' routing, multicast&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]&lt;br /&gt;
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]&lt;br /&gt;
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  High performance ns-3 emulation with Direct NIC Access   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets. &lt;br /&gt;
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.&lt;br /&gt;
* ''Required Experience:'' C++, Linux &lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** http://www.ntop.org/products/pf_ring/libzero-for-dna/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  LTE Idle Mode Procedures   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]&lt;br /&gt;
&lt;br /&gt;
* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.&lt;br /&gt;
* ''Required Experience:'' C++, LTE&lt;br /&gt;
* ''Interests:'' mobility management&lt;br /&gt;
* ''Difficulty:'' medium/hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** 3GPP TS 36.300 &amp;quot;E-UTRA and E-UTRAN overall description&amp;quot;, section 10.1.1 &amp;quot;Mobility Management in ECM-IDLE&amp;quot;&lt;br /&gt;
** 3GPP TS 36.304 &amp;quot;User Equipment (UE) procedures in idle mode&amp;quot;&lt;br /&gt;
** 3GPP TS 24.301 &amp;quot;Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  Decouple traffic generators from sockets   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* ns-3 uses applications that are part traffic generator, part socket-based application.  The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks.  This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.&lt;br /&gt;
* ''Required Experience:'' C++, sockets API&lt;br /&gt;
* ''Interests:'' &lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** Unix Network Programming (Stevens) or equivalent&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  ARP and NDisc cache visibility   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches.  Something similar to how PrintRoutes is done for IPv4 would be useful.  Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).&lt;br /&gt;
* ''Required Experience:'' C++&lt;br /&gt;
* ''Interests:'' IPv4 and Ipv6&lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** source code in src/internet, and the bugs mentioned above&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== INSTOOLS for ns-3 ===&lt;br /&gt;
&lt;br /&gt;
Mentors:  [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''INSTOOLS for ns-3:''' [http://groups.geni.net/geni/wiki/InstrumentationTools INSTOOLS] is a software instrumentation package for GENI experiments.  It logs a lot of artifacts of experiments, such as ARP and IP routing tables, Netflow graphs, etc, to databases.  The aim of this project is to instrument ns-3 nodes to capture as much of this data as is applicable.  A bonus is to try to integrate further with ProtoGENI and INSTOOLS such as making the ns-3 data archived just like it was a GENI experiment.&lt;br /&gt;
* ''Required Experience:'' Familiarity with Linux networking and with C++ programming.  &lt;br /&gt;
* ''Bonus Experience:'' Experience with GENI and/or Emulab&lt;br /&gt;
* ''Interests:'' Simulator tool development, integration with testbed experiments&lt;br /&gt;
* ''Difficulty:'' Medium&lt;br /&gt;
* ''Recommended Reading:'' http://groups.geni.net/geni/wiki/InstrumentationTools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== bufferbloat-related models ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''bufferbloat models:''' [https://www.youtube.com/watch?v=-D-cJNtKwuw Bufferbloat] is an interesting contemporary research topic. &lt;br /&gt;
This project proposal is to develop models, examples, and visualizations around the bufferbloat problem.  Some technical solutions include Linux Byte Queue Limits (BQL) and active queue management (AQM) techniques (we just have RED queues in ns-3-dev but no models yet for the others).&lt;br /&gt;
Note:  There is already some ns-3 code available (see below) but the authors have not&lt;br /&gt;
updated it for a while; this could be a starting point.  Also, work could&lt;br /&gt;
be done on using actual Linux code in the ns-3 Direct Code Execution (DCE)&lt;br /&gt;
project.&lt;br /&gt;
* ''Interests:'' Internet performance, linux kernel networking  &lt;br /&gt;
* ''Difficulty:'' easy to hard, depending on the depth of the project&lt;br /&gt;
* ''Recommended reading:'' &lt;br /&gt;
** http://gettys.wordpress.com/category/bufferbloat/&lt;br /&gt;
** [http://www.bufferbloat.net/projects/cerowrt CeroWrt]&lt;br /&gt;
** [http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf ICCRG presentation]&lt;br /&gt;
** [http://pollere.net/CoDel.html ns-2 code]&lt;br /&gt;
** [https://codereview.appspot.com/6463048/ ns-3 code review]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== High performance ns-3 emulation with Direct NIC Access (2) ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of netmap packet I/O.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Identifying the bottle of ns-3. Using profiler (oprofile etc) would be the start point.&lt;br /&gt;
# Introducing netmap interface as a FdNetDeviceHelper.&lt;br /&gt;
# Performance comparison between existing one (i.e., EmuNetDevice) with the netmap one.&lt;br /&gt;
# Creating a patch for fdnetdevice module (and ask reviews).&lt;br /&gt;
# Documentation including how netmap should be installed/configured. Though netmap supports FreeBSD platform, it is fine to start only with Linux version in this project.&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C++, Linux, Profiling (e.g., gprof/oprofile)&lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** [http://info.iet.unipi.it/~luigi/netmap/ netmap]&lt;br /&gt;
** Luigi Rizzo, [http://info.iet.unipi.it/~luigi/papers/20120503-netmap-atc12.pdf netmap: a novel framework for fast packet I/O], Usenix ATC'12, June 2012&lt;br /&gt;
** Luigi Rizzo, [http://queue.acm.org/detail.cfm?id=2103536 Revisiting network I/O APIs: The netmap Framework], Communications of the ACM, March 2012&lt;br /&gt;
** [http://nepi.inria.fr/wiki/FdNetDevice FdNetDevice] (will be merged at ns-3.17)&lt;br /&gt;
&lt;br /&gt;
=== Linux SCTP support over DCE ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
Stream Control Transmission Protocol (SCTP) is an alternate transport protocol rather than traditional TCP and UDP. It covers a broad feature for application messaging, but one of interesting feature is using multiple streams in a single session. Almost none of applications are using SCTP at this moment in fact, but it is used in the back-end of LTE.&lt;br /&gt;
&lt;br /&gt;
In this project, instead of implementing huge amount of specification of SCTP (134 pages in RFC 2960), we reuse existing Linux implementation over Direct Code Execution (DCE). DCE allows us to simulate existing implementation over ns-3 without (ideally) modifying original code.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Modifying DCE Linux module to support SCTP&lt;br /&gt;
## enabling CONFIG_IP_SCTP option (and related one) and build it (I have incomplete patch)&lt;br /&gt;
## writing simple SCTP program (I also have)&lt;br /&gt;
## writing sample scenario script using above SCTP program (I also have)&lt;br /&gt;
# Implement missing part of DCE Linux module to run SCTP code over ns-3&lt;br /&gt;
# Implement DCE Cradle wrapper socket for SCTP (optional)&lt;br /&gt;
# Create patch for ns-3-dce (and code review)&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C/C++, Linux, Kernel&lt;br /&gt;
* ''Interests:'' transport protocol, Direct Code Execution&lt;br /&gt;
* ''Difficulty:'' medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** [http://tools.ietf.org/html/rfc3286 RFC 3286] An Introduction to the Stream Control Transmission Protocol]&lt;br /&gt;
** [http://lksctp.sourceforge.net Linux Kernel Stream Control Transmission Protocol Tools (lksctp-tools)]&lt;br /&gt;
** [http://linux.die.net/man/7/sctp sctp(7) - Linux man page]&lt;br /&gt;
** [http://code.nsnam.org/ns-3-dce/file/456bb670b7d2/example/dce-dccp.cc DCE DCCP protocol example simulation scenario]&lt;br /&gt;
** [http://www.nsnam.org/projects/direct-code-execution/ Direct Code Execution]&lt;br /&gt;
** [https://github.com/thehajime/net-next-sim DCE Linux module]&lt;br /&gt;
** [https://sites.google.com/site/thehajime/Home/wns3-2013-tazaki.pdf?attredirects=0 DCE Cradle]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Road Topology Model ===&lt;br /&gt;
Mentors:   [mailto:loulloudes.n@cs.ucy.ac.cy Nicholas Loulloudes]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Envisioned protocols, services and applications that will be developed and deployed on VANET-enabled vehicles, will require knowledge of the underlying road topology. Since the ns-3 community aims at supporting network simulations for the vehicular environments, it is important to develop a road-topology model in ns-3. Currently, vehicle movement in ns-3 is simulated by utilizing traces in the ns-2 mobility format. These traces can be generated and exported using a number of traffic simulators such as SUMO[1], VanetMobiSim[2], etc. However, given the simplicity of the ns-2 mobility format (x-y-z coordinates),  nodes in the simulation are agnostic of the underlying road topology map, and hence they cannot evaluate if for example they are moving on an arterial road, or a city road or they are stopped at an intersection. A solution to this, is to provide the ability to import in ns-3 a map of the simulated area either from a public repository such as OpenStreetMap.org [3], or TigerMaps[4] or from a traffic simulator such as SUMO[3]. By parsing the map file before the simulation start, the road topology model can be populated with information such as: the structure of the road network (roads and junctions), speed limits / one-way streets, number of lanes, traffic lights etc. In addition, the necessary mechanisms should be developed, to enable each node in the simulation (i.e a vehicle) , to identify its whereabouts on the road-topology based on its current geographic coordinates. &lt;br /&gt;
* Interests: VANETs. realistic simulations&lt;br /&gt;
* Required experience: C++, XML, Python&lt;br /&gt;
* Bonus experience: Python, Perl, Graph theory &lt;br /&gt;
* Difficulty: medium &lt;br /&gt;
* Recommended reading:&lt;br /&gt;
** [1] http://sumo.sourceforge.net/ &lt;br /&gt;
** [2] http://vanet.eurecom.fr/ &lt;br /&gt;
** [3] http://www.openstreetmap.org/ &lt;br /&gt;
** [4] http://www.census.gov/geo/maps-data/data/tiger.html&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7498</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7498"/>
		<updated>2013-04-09T01:23:56Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Bugs not merged in this release =&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7487</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7487"/>
		<updated>2013-03-31T15:06:52Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;create jenkins test suite&amp;lt;/s&amp;gt;&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7482</id>
		<title>GSOC2013Projects</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7482"/>
		<updated>2013-03-29T02:40:49Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Linux SCTP support over DCE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]&lt;br /&gt;
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]&lt;br /&gt;
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]&lt;br /&gt;
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]&lt;br /&gt;
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]&lt;br /&gt;
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]&lt;br /&gt;
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]&lt;br /&gt;
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]&lt;br /&gt;
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]&lt;br /&gt;
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net&lt;br /&gt;
&lt;br /&gt;
= GSoC 2013 Ideas =&lt;br /&gt;
&lt;br /&gt;
This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.&lt;br /&gt;
&lt;br /&gt;
GSOC 2012 Timeline is:&lt;br /&gt;
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.&lt;br /&gt;
* March 29 - 19:00 UTC: Mentoring organization application deadline.&lt;br /&gt;
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.&lt;br /&gt;
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.&lt;br /&gt;
* April 22 - 19:00 UTC: Student application period opens.&lt;br /&gt;
* May 3 - 19:00 UTC: Student application deadline.&lt;br /&gt;
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013&lt;br /&gt;
&lt;br /&gt;
While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8. &lt;br /&gt;
&lt;br /&gt;
== About the ns-3 project ==&lt;br /&gt;
&lt;br /&gt;
ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011).  ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained.  The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.&lt;br /&gt;
&lt;br /&gt;
Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson].  The project has participated in past GSoCs during 2008-10 and 2012.&lt;br /&gt;
&lt;br /&gt;
Mentors will be paired with students based on the projects that are selected.  Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring.  Prospective mentors should notify Lalith Suresh of interest.  Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
For students interested in applying to ns-3 for GSOC, go through the following list to get started:&lt;br /&gt;
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].&lt;br /&gt;
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].&lt;br /&gt;
* Look through our ideas list below to see if you find a project that interests you.&lt;br /&gt;
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.&lt;br /&gt;
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.&lt;br /&gt;
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Each project idea within a particular priority has been tagged with the following properties:&lt;br /&gt;
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.&lt;br /&gt;
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.&lt;br /&gt;
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.&lt;br /&gt;
* ''Difficulty:'' easy, medium or difficult&lt;br /&gt;
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Guidelines for project ideas =&lt;br /&gt;
&lt;br /&gt;
For mentors who're adding project ideas to the list below, please ensure that:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.&lt;br /&gt;
&lt;br /&gt;
= Project Ideas =&lt;br /&gt;
&lt;br /&gt;
=== Vehicular Ad-hoc Networks ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]&lt;br /&gt;
&lt;br /&gt;
* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:&lt;br /&gt;
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.&lt;br /&gt;
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)&lt;br /&gt;
# higher layers: nothing specific to WAVE is currently available.&lt;br /&gt;
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).&lt;br /&gt;
** ''Required experience:'' C++.&lt;br /&gt;
** ''Bonus experience:'' Wireless networking, WAVE.&lt;br /&gt;
** ''Interests:'' Wireless networking, VANETs.&lt;br /&gt;
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.&lt;br /&gt;
** ''Recommended reading''&lt;br /&gt;
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11&lt;br /&gt;
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945&lt;br /&gt;
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16&lt;br /&gt;
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968&lt;br /&gt;
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Energy Model ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' ns-3 Energy model&lt;br /&gt;
** ''Interests:'' WSN, Battery discharge&lt;br /&gt;
** ''Difficulty:'' easy&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes] &lt;br /&gt;
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Bootstrap ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Beacon-enabled mode ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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. &lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Simulating the Internet of Things in NS-3 === &lt;br /&gt;
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]&lt;br /&gt;
&lt;br /&gt;
In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.&lt;br /&gt;
** ''Required experience'' : C++&lt;br /&gt;
** ''Bonus experience'' : NS-2, WSN, Matlab&lt;br /&gt;
** ''Interests'' : ZB, embedded, wireless, sensor networks&lt;br /&gt;
** ''Difficulty'' : medium&lt;br /&gt;
** ''Recommended reading'' :&lt;br /&gt;
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]&lt;br /&gt;
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]&lt;br /&gt;
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3&lt;br /&gt;
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3&lt;br /&gt;
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)&lt;br /&gt;
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY&lt;br /&gt;
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested. &lt;br /&gt;
** ''Required Experience:'' C++, IPv6, RPL&lt;br /&gt;
** ''Bonus Experience:'' WSN networking&lt;br /&gt;
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression &lt;br /&gt;
** ''Difficulty:'' hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals&lt;br /&gt;
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== RPL protocol Metric and Constraints ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' RPL protocol&lt;br /&gt;
** ''Interests:'' WSN, routing &lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPv6 stack validation and improvements ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):&lt;br /&gt;
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].&lt;br /&gt;
*# Flow Monitor module does not work on the IPv6 stack&lt;br /&gt;
*# FlowLabel header field is not currenly used&lt;br /&gt;
*# IPSec is not supported&lt;br /&gt;
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.&lt;br /&gt;
** ''Required Experience:'' C++, TCP/IP networking&lt;br /&gt;
** ''Bonus Experience:'' IPv6 protocols&lt;br /&gt;
** ''Interests:'' IPv6 internetworking&lt;br /&gt;
** ''Difficulty:'' easy / medium, depending on the features implemented&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]&lt;br /&gt;
*** ns-3 Flowmon module documentation&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Multicast IPv6 traffic support ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)&lt;br /&gt;
** ''Interests:'' routing, multicast&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]&lt;br /&gt;
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]&lt;br /&gt;
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  High performance ns-3 emulation with Direct NIC Access   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets. &lt;br /&gt;
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.&lt;br /&gt;
* ''Required Experience:'' C++, Linux &lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** http://www.ntop.org/products/pf_ring/libzero-for-dna/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  LTE Idle Mode Procedures   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]&lt;br /&gt;
&lt;br /&gt;
* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.&lt;br /&gt;
* ''Required Experience:'' C++, LTE&lt;br /&gt;
* ''Interests:'' mobility management&lt;br /&gt;
* ''Difficulty:'' medium/hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** 3GPP TS 36.300 &amp;quot;E-UTRA and E-UTRAN overall description&amp;quot;, section 10.1.1 &amp;quot;Mobility Management in ECM-IDLE&amp;quot;&lt;br /&gt;
** 3GPP TS 36.304 &amp;quot;User Equipment (UE) procedures in idle mode&amp;quot;&lt;br /&gt;
** 3GPP TS 24.301 &amp;quot;Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===  Decouple traffic generators from sockets   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* ns-3 uses applications that are part traffic generator, part socket-based application.  The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks.  This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.&lt;br /&gt;
* ''Required Experience:'' C++, sockets API&lt;br /&gt;
* ''Interests:'' &lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** Unix Network Programming (Stevens) or equivalent&lt;br /&gt;
&lt;br /&gt;
===  ARP and NDisc cache visibility   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches.  Something similar to how PrintRoutes is done for IPv4 would be useful.  Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).&lt;br /&gt;
* ''Required Experience:'' C++&lt;br /&gt;
* ''Interests:'' IPv4 and Ipv6&lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** source code in src/internet, and the bugs mentioned above&lt;br /&gt;
&lt;br /&gt;
=== INSTOOLS for ns-3 ===&lt;br /&gt;
&lt;br /&gt;
Mentors:  [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''INSTOOLS for ns-3:''' [http://groups.geni.net/geni/wiki/InstrumentationTools INSTOOLS] is a software instrumentation package for GENI experiments.  It logs a lot of artifacts of experiments, such as ARP and IP routing tables, Netflow graphs, etc, to databases.  The aim of this project is to instrument ns-3 nodes to capture as much of this data as is applicable.  A bonus is to try to integrate further with ProtoGENI and INSTOOLS such as making the ns-3 data archived just like it was a GENI experiment.&lt;br /&gt;
* ''Required Experience:'' Familiarity with Linux networking and with C++ programming.  &lt;br /&gt;
* ''Bonus Experience:'' Experience with GENI and/or Emulab&lt;br /&gt;
* ''Interests:'' Simulator tool development, integration with testbed experiments&lt;br /&gt;
* ''Difficulty:'' Medium&lt;br /&gt;
* ''Recommended Reading:'' http://groups.geni.net/geni/wiki/InstrumentationTools&lt;br /&gt;
&lt;br /&gt;
=== bufferbloat-related models ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''bufferbloat models:''' [https://www.youtube.com/watch?v=-D-cJNtKwuw Bufferbloat] is an interesting contemporary research topic. &lt;br /&gt;
This project proposal is to develop models, examples, and visualizations around the bufferbloat problem.  Some technical solutions include Linux Byte Queue Limits (BQL) and active queue management (AQM) techniques (we just have RED queues in ns-3-dev but no models yet for the others).&lt;br /&gt;
Note:  There is already some ns-3 code available (see below) but the authors have not&lt;br /&gt;
updated it for a while; this could be a starting point.  Also, work could&lt;br /&gt;
be done on using actual Linux code in the ns-3 Direct Code Execution (DCE)&lt;br /&gt;
project.&lt;br /&gt;
* ''Interests:'' Internet performance, linux kernel networking  &lt;br /&gt;
* ''Difficulty:'' easy to hard, depending on the depth of the project&lt;br /&gt;
* ''Recommended reading:'' &lt;br /&gt;
** http://gettys.wordpress.com/category/bufferbloat/&lt;br /&gt;
** [http://www.bufferbloat.net/projects/cerowrt CeroWrt]&lt;br /&gt;
** [http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf ICCRG presentation]&lt;br /&gt;
** [http://pollere.net/CoDel.html ns-2 code]&lt;br /&gt;
** [https://codereview.appspot.com/6463048/ ns-3 code review]&lt;br /&gt;
&lt;br /&gt;
=== High performance ns-3 emulation with Direct NIC Access (2) ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of netmap packet I/O.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Introducing netmap interface as a FdNetDeviceHelper.&lt;br /&gt;
# Performance comparison between existing one (i.e., EmuNetDevice) with the netmap one.&lt;br /&gt;
# Creating a patch for fdnetdevice module (and ask reviews).&lt;br /&gt;
# Documentation including how netmap should be installed/configured.Though netmap supports FreeBSD platform, it is fine to start only with Linux version in this project.&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C++, Linux, Profiling (e.g., gprof/oprofile)&lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** [http://info.iet.unipi.it/~luigi/netmap/ netmap]&lt;br /&gt;
** Luigi Rizzo, [http://info.iet.unipi.it/~luigi/papers/20120503-netmap-atc12.pdf netmap: a novel framework for fast packet I/O], Usenix ATC'12, June 2012&lt;br /&gt;
** Luigi Rizzo, [http://queue.acm.org/detail.cfm?id=2103536 Revisiting network I/O APIs: The netmap Framework], Communications of the ACM, March 2012&lt;br /&gt;
** [http://nepi.inria.fr/wiki/FdNetDevice FdNetDevice] (will be merged at ns-3.17)&lt;br /&gt;
&lt;br /&gt;
=== Linux SCTP support over DCE ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
Stream Control Transmission Protocol (SCTP) is an alternate transport protocol rather than traditional TCP and UDP. It covers a broad feature for application messaging, but one of interesting feature is using multiple streams in a single session. Almost none of applications are using SCTP at this moment in fact, but it is used in the back-end of LTE.&lt;br /&gt;
&lt;br /&gt;
In this project, instead of implementing huge amount of specification of SCTP (134 pages in RFC 2960), we reuse existing Linux implementation over Direct Code Execution (DCE). DCE allows us to simulate existing implementation over ns-3 without (ideally) modifying original code.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Modifying DCE Linux module to support SCTP&lt;br /&gt;
## enabling CONFIG_IP_SCTP option (and related one) and build it (I have incomplete patch)&lt;br /&gt;
## writing simple SCTP program (I also have)&lt;br /&gt;
## writing sample scenario script using above SCTP program (I also have)&lt;br /&gt;
# Implement missing part of DCE Linux module to run SCTP code over ns-3&lt;br /&gt;
# Implement DCE Cradle wrapper socket for SCTP (optional)&lt;br /&gt;
# Create patch for ns-3-dce (and code review)&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C/C++, Linux, Kernel&lt;br /&gt;
* ''Interests:'' transport protocol, Direct Code Execution&lt;br /&gt;
* ''Difficulty:'' medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** [http://tools.ietf.org/html/rfc3286 RFC 3286] An Introduction to the Stream Control Transmission Protocol]&lt;br /&gt;
** [http://lksctp.sourceforge.net Linux Kernel Stream Control Transmission Protocol Tools (lksctp-tools)]&lt;br /&gt;
** [http://linux.die.net/man/7/sctp sctp(7) - Linux man page]&lt;br /&gt;
** [http://code.nsnam.org/ns-3-dce/file/456bb670b7d2/example/dce-dccp.cc DCE DCCP protocol example simulation scenario]&lt;br /&gt;
** [http://www.nsnam.org/projects/direct-code-execution/ Direct Code Execution]&lt;br /&gt;
** [https://github.com/thehajime/net-next-sim DCE Linux module]&lt;br /&gt;
** [https://sites.google.com/site/thehajime/Home/wns3-2013-tazaki.pdf?attredirects=0 DCE Cradle]&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7481</id>
		<title>GSOC2013Projects</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7481"/>
		<updated>2013-03-29T02:40:23Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* High performance ns-3 emulation with Direct NIC Access (2) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]&lt;br /&gt;
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]&lt;br /&gt;
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]&lt;br /&gt;
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]&lt;br /&gt;
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]&lt;br /&gt;
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]&lt;br /&gt;
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]&lt;br /&gt;
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]&lt;br /&gt;
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]&lt;br /&gt;
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net&lt;br /&gt;
&lt;br /&gt;
= GSoC 2013 Ideas =&lt;br /&gt;
&lt;br /&gt;
This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.&lt;br /&gt;
&lt;br /&gt;
GSOC 2012 Timeline is:&lt;br /&gt;
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.&lt;br /&gt;
* March 29 - 19:00 UTC: Mentoring organization application deadline.&lt;br /&gt;
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.&lt;br /&gt;
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.&lt;br /&gt;
* April 22 - 19:00 UTC: Student application period opens.&lt;br /&gt;
* May 3 - 19:00 UTC: Student application deadline.&lt;br /&gt;
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013&lt;br /&gt;
&lt;br /&gt;
While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8. &lt;br /&gt;
&lt;br /&gt;
== About the ns-3 project ==&lt;br /&gt;
&lt;br /&gt;
ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011).  ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained.  The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.&lt;br /&gt;
&lt;br /&gt;
Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson].  The project has participated in past GSoCs during 2008-10 and 2012.&lt;br /&gt;
&lt;br /&gt;
Mentors will be paired with students based on the projects that are selected.  Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring.  Prospective mentors should notify Lalith Suresh of interest.  Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
For students interested in applying to ns-3 for GSOC, go through the following list to get started:&lt;br /&gt;
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].&lt;br /&gt;
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].&lt;br /&gt;
* Look through our ideas list below to see if you find a project that interests you.&lt;br /&gt;
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.&lt;br /&gt;
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.&lt;br /&gt;
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Each project idea within a particular priority has been tagged with the following properties:&lt;br /&gt;
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.&lt;br /&gt;
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.&lt;br /&gt;
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.&lt;br /&gt;
* ''Difficulty:'' easy, medium or difficult&lt;br /&gt;
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Guidelines for project ideas =&lt;br /&gt;
&lt;br /&gt;
For mentors who're adding project ideas to the list below, please ensure that:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.&lt;br /&gt;
&lt;br /&gt;
= Project Ideas =&lt;br /&gt;
&lt;br /&gt;
=== Vehicular Ad-hoc Networks ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]&lt;br /&gt;
&lt;br /&gt;
* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:&lt;br /&gt;
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.&lt;br /&gt;
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)&lt;br /&gt;
# higher layers: nothing specific to WAVE is currently available.&lt;br /&gt;
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).&lt;br /&gt;
** ''Required experience:'' C++.&lt;br /&gt;
** ''Bonus experience:'' Wireless networking, WAVE.&lt;br /&gt;
** ''Interests:'' Wireless networking, VANETs.&lt;br /&gt;
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.&lt;br /&gt;
** ''Recommended reading''&lt;br /&gt;
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11&lt;br /&gt;
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945&lt;br /&gt;
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16&lt;br /&gt;
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968&lt;br /&gt;
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Energy Model ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' ns-3 Energy model&lt;br /&gt;
** ''Interests:'' WSN, Battery discharge&lt;br /&gt;
** ''Difficulty:'' easy&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes] &lt;br /&gt;
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Bootstrap ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Beacon-enabled mode ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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. &lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Simulating the Internet of Things in NS-3 === &lt;br /&gt;
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]&lt;br /&gt;
&lt;br /&gt;
In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.&lt;br /&gt;
** ''Required experience'' : C++&lt;br /&gt;
** ''Bonus experience'' : NS-2, WSN, Matlab&lt;br /&gt;
** ''Interests'' : ZB, embedded, wireless, sensor networks&lt;br /&gt;
** ''Difficulty'' : medium&lt;br /&gt;
** ''Recommended reading'' :&lt;br /&gt;
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]&lt;br /&gt;
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]&lt;br /&gt;
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3&lt;br /&gt;
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3&lt;br /&gt;
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)&lt;br /&gt;
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY&lt;br /&gt;
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested. &lt;br /&gt;
** ''Required Experience:'' C++, IPv6, RPL&lt;br /&gt;
** ''Bonus Experience:'' WSN networking&lt;br /&gt;
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression &lt;br /&gt;
** ''Difficulty:'' hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals&lt;br /&gt;
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== RPL protocol Metric and Constraints ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' RPL protocol&lt;br /&gt;
** ''Interests:'' WSN, routing &lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPv6 stack validation and improvements ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):&lt;br /&gt;
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].&lt;br /&gt;
*# Flow Monitor module does not work on the IPv6 stack&lt;br /&gt;
*# FlowLabel header field is not currenly used&lt;br /&gt;
*# IPSec is not supported&lt;br /&gt;
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.&lt;br /&gt;
** ''Required Experience:'' C++, TCP/IP networking&lt;br /&gt;
** ''Bonus Experience:'' IPv6 protocols&lt;br /&gt;
** ''Interests:'' IPv6 internetworking&lt;br /&gt;
** ''Difficulty:'' easy / medium, depending on the features implemented&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]&lt;br /&gt;
*** ns-3 Flowmon module documentation&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Multicast IPv6 traffic support ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)&lt;br /&gt;
** ''Interests:'' routing, multicast&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]&lt;br /&gt;
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]&lt;br /&gt;
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  High performance ns-3 emulation with Direct NIC Access   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets. &lt;br /&gt;
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.&lt;br /&gt;
* ''Required Experience:'' C++, Linux &lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** http://www.ntop.org/products/pf_ring/libzero-for-dna/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  LTE Idle Mode Procedures   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]&lt;br /&gt;
&lt;br /&gt;
* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.&lt;br /&gt;
* ''Required Experience:'' C++, LTE&lt;br /&gt;
* ''Interests:'' mobility management&lt;br /&gt;
* ''Difficulty:'' medium/hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** 3GPP TS 36.300 &amp;quot;E-UTRA and E-UTRAN overall description&amp;quot;, section 10.1.1 &amp;quot;Mobility Management in ECM-IDLE&amp;quot;&lt;br /&gt;
** 3GPP TS 36.304 &amp;quot;User Equipment (UE) procedures in idle mode&amp;quot;&lt;br /&gt;
** 3GPP TS 24.301 &amp;quot;Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===  Decouple traffic generators from sockets   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* ns-3 uses applications that are part traffic generator, part socket-based application.  The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks.  This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.&lt;br /&gt;
* ''Required Experience:'' C++, sockets API&lt;br /&gt;
* ''Interests:'' &lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** Unix Network Programming (Stevens) or equivalent&lt;br /&gt;
&lt;br /&gt;
===  ARP and NDisc cache visibility   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches.  Something similar to how PrintRoutes is done for IPv4 would be useful.  Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).&lt;br /&gt;
* ''Required Experience:'' C++&lt;br /&gt;
* ''Interests:'' IPv4 and Ipv6&lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** source code in src/internet, and the bugs mentioned above&lt;br /&gt;
&lt;br /&gt;
=== INSTOOLS for ns-3 ===&lt;br /&gt;
&lt;br /&gt;
Mentors:  [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''INSTOOLS for ns-3:''' [http://groups.geni.net/geni/wiki/InstrumentationTools INSTOOLS] is a software instrumentation package for GENI experiments.  It logs a lot of artifacts of experiments, such as ARP and IP routing tables, Netflow graphs, etc, to databases.  The aim of this project is to instrument ns-3 nodes to capture as much of this data as is applicable.  A bonus is to try to integrate further with ProtoGENI and INSTOOLS such as making the ns-3 data archived just like it was a GENI experiment.&lt;br /&gt;
* ''Required Experience:'' Familiarity with Linux networking and with C++ programming.  &lt;br /&gt;
* ''Bonus Experience:'' Experience with GENI and/or Emulab&lt;br /&gt;
* ''Interests:'' Simulator tool development, integration with testbed experiments&lt;br /&gt;
* ''Difficulty:'' Medium&lt;br /&gt;
* ''Recommended Reading:'' http://groups.geni.net/geni/wiki/InstrumentationTools&lt;br /&gt;
&lt;br /&gt;
=== bufferbloat-related models ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''bufferbloat models:''' [https://www.youtube.com/watch?v=-D-cJNtKwuw Bufferbloat] is an interesting contemporary research topic. &lt;br /&gt;
This project proposal is to develop models, examples, and visualizations around the bufferbloat problem.  Some technical solutions include Linux Byte Queue Limits (BQL) and active queue management (AQM) techniques (we just have RED queues in ns-3-dev but no models yet for the others).&lt;br /&gt;
Note:  There is already some ns-3 code available (see below) but the authors have not&lt;br /&gt;
updated it for a while; this could be a starting point.  Also, work could&lt;br /&gt;
be done on using actual Linux code in the ns-3 Direct Code Execution (DCE)&lt;br /&gt;
project.&lt;br /&gt;
* ''Interests:'' Internet performance, linux kernel networking  &lt;br /&gt;
* ''Difficulty:'' easy to hard, depending on the depth of the project&lt;br /&gt;
* ''Recommended reading:'' &lt;br /&gt;
** http://gettys.wordpress.com/category/bufferbloat/&lt;br /&gt;
** [http://www.bufferbloat.net/projects/cerowrt CeroWrt]&lt;br /&gt;
** [http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf ICCRG presentation]&lt;br /&gt;
** [http://pollere.net/CoDel.html ns-2 code]&lt;br /&gt;
** [https://codereview.appspot.com/6463048/ ns-3 code review]&lt;br /&gt;
&lt;br /&gt;
=== High performance ns-3 emulation with Direct NIC Access (2) ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of netmap packet I/O.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Introducing netmap interface as a FdNetDeviceHelper.&lt;br /&gt;
# Performance comparison between existing one (i.e., EmuNetDevice) with the netmap one.&lt;br /&gt;
# Creating a patch for fdnetdevice module (and ask reviews).&lt;br /&gt;
# Documentation including how netmap should be installed/configured.Though netmap supports FreeBSD platform, it is fine to start only with Linux version in this project.&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C++, Linux, Profiling (e.g., gprof/oprofile)&lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** [http://info.iet.unipi.it/~luigi/netmap/ netmap]&lt;br /&gt;
** Luigi Rizzo, [http://info.iet.unipi.it/~luigi/papers/20120503-netmap-atc12.pdf netmap: a novel framework for fast packet I/O], Usenix ATC'12, June 2012&lt;br /&gt;
** Luigi Rizzo, [http://queue.acm.org/detail.cfm?id=2103536 Revisiting network I/O APIs: The netmap Framework], Communications of the ACM, March 2012&lt;br /&gt;
** [http://nepi.inria.fr/wiki/FdNetDevice FdNetDevice] (will be merged at ns-3.17)&lt;br /&gt;
&lt;br /&gt;
=== Linux SCTP support over DCE ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
Stream Control Transmission Protocol (SCTP) is an alternate transport protocol rather than traditional TCP and UDP. It covers a broad feature for application messaging, but one of interesting feature is using multiple streams in a single session. Almost none of applications are using SCTP at this moment in fact, but it is used in the back-end of LTE.&lt;br /&gt;
&lt;br /&gt;
In this project, instead of implementing huge amount of specification of SCTP (134 pages in RFC 2960), we reuse existing Linux implementation over Direct Code Execution (DCE). DCE allows us to simulate existing implementation over ns-3 without (ideally) modifying original code.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Modifying DCE Linux module to support SCTP&lt;br /&gt;
## enabling CONFIG_IP_SCTP option (and related one) and build it (I have incomplete patch)&lt;br /&gt;
## writing simple SCTP program (I also have)&lt;br /&gt;
## writing sample scenario script using above SCTP program (I also have)&lt;br /&gt;
# Implement missing part of DCE Linux module to run SCTP code over ns-3&lt;br /&gt;
# Implement DCE Cradle wrapper socket for SCTP (optional)&lt;br /&gt;
# Create patch for ns-3-dce (and code review)&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C/C++, Linux, Kernel&lt;br /&gt;
* ''Interests:'' transport protocol, Direct Code Execution&lt;br /&gt;
* ''Difficulty:'' medium* ''Recommended reading:''&lt;br /&gt;
** [http://tools.ietf.org/html/rfc3286 RFC 3286] An Introduction to the Stream Control Transmission Protocol]&lt;br /&gt;
** [http://lksctp.sourceforge.net Linux Kernel Stream Control Transmission Protocol Tools (lksctp-tools)]&lt;br /&gt;
** [http://linux.die.net/man/7/sctp sctp(7) - Linux man page]&lt;br /&gt;
** [http://code.nsnam.org/ns-3-dce/file/456bb670b7d2/example/dce-dccp.cc DCE DCCP protocol example simulation scenario]&lt;br /&gt;
** [http://www.nsnam.org/projects/direct-code-execution/ Direct Code Execution]&lt;br /&gt;
** [https://github.com/thehajime/net-next-sim DCE Linux module]&lt;br /&gt;
** [https://sites.google.com/site/thehajime/Home/wns3-2013-tazaki.pdf?attredirects=0 DCE Cradle]&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7480</id>
		<title>GSOC2013Projects</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=GSOC2013Projects&amp;diff=7480"/>
		<updated>2013-03-29T02:39:47Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions]&lt;br /&gt;
* [http://en.flossmanuals.net/gsocmentoring/ GSoC Mentor guide]&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide]&lt;br /&gt;
* [[GSOC2013StudentGuide |ns-3's GSoC Student guide]]&lt;br /&gt;
* [[GSOCMentorGuide | ns-3's GSoC Mentor guide]]&lt;br /&gt;
* [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]&lt;br /&gt;
* [[GSOC2013StudentApplicationTemplate |GSoC Student application template]]&lt;br /&gt;
* [[GSOC2012Projects |GSoC 2012 page]] | [[GSOC2012AcceptedProjects |GSoC 2012 Accepted Projects]]&lt;br /&gt;
* [[GSOC2011Projects |NSoC 2011 Ideas page]] | [[NSOC2011AcceptedProjects |NSoC 2011 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010Projects |GSoC 2010 Ideas page]] | [[GSOC2010AcceptedProjects |GSoC 2010 Accepted Projects]]&lt;br /&gt;
* [[GSOC2009Projects |GSoC 2009 Ideas page]] | [[GSOC2009AcceptedProjects |GSoC 2009 Accepted Projects]]&lt;br /&gt;
* [[GSOC2010OAReport |GSoC Organization Administrator guide]]&lt;br /&gt;
* ''Get in contact with the ns-3 team'': [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers mailing list] | ''IRC'' #ns-3 on freenode.net&lt;br /&gt;
&lt;br /&gt;
= GSoC 2013 Ideas =&lt;br /&gt;
&lt;br /&gt;
This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.&lt;br /&gt;
&lt;br /&gt;
GSOC 2012 Timeline is:&lt;br /&gt;
* March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.&lt;br /&gt;
* March 29 - 19:00 UTC: Mentoring organization application deadline.&lt;br /&gt;
* April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.&lt;br /&gt;
* April 9-21: Would-be student participants discuss application ideas with mentoring organizations.&lt;br /&gt;
* April 22 - 19:00 UTC: Student application period opens.&lt;br /&gt;
* May 3 - 19:00 UTC: Student application deadline.&lt;br /&gt;
Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013&lt;br /&gt;
&lt;br /&gt;
While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8. &lt;br /&gt;
&lt;br /&gt;
== About the ns-3 project ==&lt;br /&gt;
&lt;br /&gt;
ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011).  ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained.  The tool is coming into wide use; our web server logged almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.&lt;br /&gt;
&lt;br /&gt;
Our GSoC organizational admin is [mailto:suresh.lalith@gmail.com Lalith Suresh] and our backup org admin is [mailto:tomhend@u.washington.edu Tom Henderson].  The project has participated in past GSoCs during 2008-10 and 2012.&lt;br /&gt;
&lt;br /&gt;
Mentors will be paired with students based on the projects that are selected.  Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring.  Prospective mentors should notify Lalith Suresh of interest.  Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
For students interested in applying to ns-3 for GSOC, go through the following list to get started:&lt;br /&gt;
* Read the official [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC student guide].&lt;br /&gt;
* Read [[GSOC2013StudentGuide |ns-3's GSoC Student guide]].&lt;br /&gt;
* Look through our ideas list below to see if you find a project that interests you.&lt;br /&gt;
* Look through the [[GSOC2013StudentApplicationTemplate |GSoC Student application template]] to start preparing your proposal.&lt;br /&gt;
* Next, proceed to get in touch with the developers on the mailing list and refine your proposal.&lt;br /&gt;
* In parallel, make sure you prepare a patch as per the [[GSOC2013PatchRequirement | Patch Requirement Guidelines]]. Your application to ns-3 will not be considered if you do not fulfill this requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project Ideas ==&lt;br /&gt;
&lt;br /&gt;
The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Each project idea within a particular priority has been tagged with the following properties:&lt;br /&gt;
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.&lt;br /&gt;
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.&lt;br /&gt;
* ''Interests:'' Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.&lt;br /&gt;
* ''Difficulty:'' easy, medium or difficult&lt;br /&gt;
* ''Recommended reading:'' pointers to documentation, papers, specific bugs, etc.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Guidelines for project ideas =&lt;br /&gt;
&lt;br /&gt;
For mentors who're adding project ideas to the list below, please ensure that:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.&lt;br /&gt;
&lt;br /&gt;
= Project Ideas =&lt;br /&gt;
&lt;br /&gt;
=== Vehicular Ad-hoc Networks ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:guillaume.remy@ieee.org Guillaume Rémy]&lt;br /&gt;
&lt;br /&gt;
* '''Wireless Access in Vehicular Environments (WAVE)''' The IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE) defines the architecture, communications model, management structure, security mechanisms, and physical access for wireless communications in the vehicular environment. Some components of this specification has already been implemented for ns-3. However, we are still far from the simulation of WAVE on ns-3. The current status is as follows and it is up to the student to decide how much he/she wants to implement:&lt;br /&gt;
# The PHY is ready as-is: the 5 MHz and 10 Mhz channel options (i.e., 802.11p) are already implemented, with a corresponding error model. However, there is an alternative solution that implements 802.11 layers: PhySim [4], that does a more accurate job and is more appropriate for vehicular network simulations. Depending on the skills of the student, it could be possible to properly integrate PhySim in the latest NS-3 version, and start WAVE implementation on top of it.&lt;br /&gt;
# The MAC needs to be modified. First, some trivial reworking is needed [1], and the rest depends on what the student wishes to implement. One possible approach is to use [2] as a guideline for implementing what is discussed in [3]. The most complex piece to implement are the channel switch logic (the execution of the channel switch command is already implemented)&lt;br /&gt;
# higher layers: nothing specific to WAVE is currently available.&lt;br /&gt;
# mobility models: no mobility model specific for vehicular scenarios is included in ns-3. But given that ns-3 can work with ns-2 mobility traces, it should be possible to find a mobility trace generator for vehicular scenarios that can be reused with ns-3 (e.g. SUMO).&lt;br /&gt;
** ''Required experience:'' C++.&lt;br /&gt;
** ''Bonus experience:'' Wireless networking, WAVE.&lt;br /&gt;
** ''Interests:'' Wireless networking, VANETs.&lt;br /&gt;
** ''Difficulty:'' medium to hard, depending on what the student proposes to implement.&lt;br /&gt;
** ''Recommended reading''&lt;br /&gt;
*** [0] http://www.nsnam.org/bugzilla/show_bug.cgi?id=700#c11&lt;br /&gt;
*** [1] http://www.nsnam.org/bugzilla/show_bug.cgi?id=945&lt;br /&gt;
*** [2] http://www.nsnam.org/bugzilla/show_bug.cgi?id=978#c16&lt;br /&gt;
*** [3] http://www.nsnam.org/bugzilla/attachment.cgi?id=968&lt;br /&gt;
*** [4] http://dsn.tm.kit.edu/english/ns3-physim.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Energy Model ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''802.15.4 Energy Model:''' The lr-wpan model is an 802.15.4 PHY and MAC model currently in development. The model is not actually linked with the energy model. Hence it is not possible to simulate correctly the energy discharge of a Wireless Sensor Node correctly. The goal is to develop the missing classes needed to link the two modules, and to validate the results against the literature models.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' ns-3 Energy model&lt;br /&gt;
** ''Interests:'' WSN, Battery discharge&lt;br /&gt;
** ''Difficulty:'' easy&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.sics.se/~adam/dunkels07softwarebased.pdf Software-based On-line Energy Estimation for Sensor Nodes] &lt;br /&gt;
*** [http://cds.unibe.ch/research/pub_files/HBNH11.pdf On the Accuracy of Software-based Energy Estimation Techniques]&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Bootstrap ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 802.15.4 Beacon-enabled mode ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''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. &lt;br /&gt;
** ''Required Experience:'' C++, WSN&lt;br /&gt;
** ''Bonus Experience:'' 802.15.4 standard&lt;br /&gt;
** ''Interests:'' WSN&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf 802.15.4 Standard]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Simulating the Internet of Things in NS-3 === &lt;br /&gt;
Mentors: [mailto:peter.kourzanov@gmail.com Peter Kourzanov], [mailto:hong.r.li@nxp.com Hong.R. Li]&lt;br /&gt;
&lt;br /&gt;
In this project we hope to improve the Wireless Personal Area Network (WPAN) support in NS-3. In particular, the aim is to bring higher-level ZB models [7] and the underlying 802.15.4 Low-Rate WPAN (LR-WPAN) models [6] in NS-3 to the level at which large-scale simulations can be validated against real-system test-beds. In particular, current NS-3 work mentions missing support for the beaconing (i.e., slotted) mode [2], no support for ZB and ZBP standards [1], as well as lack of validation against real Hardware (HW) [2]. Older, but mature ZB 2003 code from NS-2 [5] can be taken as a starting point, although we expect that a significant effort shall be spent on porting it to NS-3 and upgrading it from ZB 2003 to ZBP 2007/2012 compliance. Alternatively, a new implementation of ZBP and/or extensions for ZBP 2012 and ZBGP might need to be developed for NS-3. This project can be executed on the premises of NXP Semiconductors Research in Eindhoven (Netherlands), Sheffield (United Kingdom) and/or in Singapore which in this case will donate a WSN test-bed for experimentation and validation. The work can be partially (excluding validation) executed remotely, with no access to the test-bed.The resulting code shall be contributed to the NS-3 community.&lt;br /&gt;
** ''Required experience'' : C++&lt;br /&gt;
** ''Bonus experience'' : NS-2, WSN, Matlab&lt;br /&gt;
** ''Interests'' : ZB, embedded, wireless, sensor networks&lt;br /&gt;
** ''Difficulty'' : medium&lt;br /&gt;
** ''Recommended reading'' :&lt;br /&gt;
**# LR-WPAN [http://www.nsnam.org/wiki/index.php/Lr-wpan status page]&lt;br /&gt;
**# LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan/file/735b14afde8e/lr-wpan-documentation.pdf model-library document]&lt;br /&gt;
**# Preliminary LR-WPAN [http://code.nsnam.org/tomh/ns-3-lr-wpan code] for NS-3&lt;br /&gt;
**# Preliminary IPv6 over Low-power WPAN (6LoWPAN) [http://code.nsnam.org/tpecorella/ns-3-6LoWPAN code] for NS-3&lt;br /&gt;
**# Mature [http://cint.ccny.cuny.edu/awnl/Software implementation] of ZB 2003 in [http://www.isi.edu/nsnam/ns NS-2] (included in version 2.35)&lt;br /&gt;
**#* original [http://cint.ccny.cuny.edu/awnl/Software/WPAN_ZBR_pub.pdf presentation] from CUNY&lt;br /&gt;
**#* adaptation and bug-fixes from [http://www.ee.washington.edu/research/funlab/802_15_4 Funlab]&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/IEEE_802.15.4 LR-WPAN] page on Wikipedia&lt;br /&gt;
**# [http://en.wikipedia.org/wiki/ZigBee ZB] page on Wikipedia&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Neighbor Discovery Optimization for Low Power and Lossy Networks (6LoWPAN-nd) ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''6LoWPAN-nd implementation and testing:''' [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] is novel draft protocol from IETF's [http://tools.ietf.org/wg/6lowpan/ LoWPAN WG]. The protocol aims at defining new and optimized methods to perform Neighbor Discovery and Node Bootstrap for Wireless Sensor Networks and it will be the counterpart of the 6LoWPAN IPv6 header compression strandard. 6LoWPAN-nd is not currently implemented in ns-3, while 6LoWPAN compression and 802.15.4 stacks are in advanced development status. In order to simulate a real Wireless Sensor Network 6LoWPAN-nd should be developed and tested. &lt;br /&gt;
** ''Required Experience:'' C++, IPv6, RPL&lt;br /&gt;
** ''Bonus Experience:'' WSN networking&lt;br /&gt;
** ''Interests:'' WSN, IPv6, node bootstrap, efficient packet compression &lt;br /&gt;
** ''Difficulty:'' hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4919 RFC 4919] IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals&lt;br /&gt;
*** [http://tools.ietf.org/html/draft-ietf-6lowpan-nd-18 6LoWPAN-nd] Neighbor Discovery Optimization for Low Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== RPL protocol Metric and Constraints ===&lt;br /&gt;
&lt;br /&gt;
Mentors:   [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''RPL protocol Metric and Constraints:''' The [http://tools.ietf.org/wg/roll/ RPL protocol] is a flexible routing protocol for Wireless Sensor Networks. The actual ns-3 module is implementing only some basic metrics such as Hop Count and ETX.The RPL module is in active development and it is not publicly available, however the code will be provided to the student before the program start.The goal of the idea is to extend the actual implementation so to support other metric kinds and options (additive, min-max, etc.).&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' RPL protocol&lt;br /&gt;
** ''Interests:'' WSN, routing &lt;br /&gt;
** ''Difficulty:'' medium&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6550 RFC 6550] RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6551 RFC 6551] Routing Metrics Used for Path alculation in Low-Power and Lossy Networks&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== IPv6 stack validation and improvements ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''IPv6 stack validation and improvements:''' IPv6 use is going to increase dramatically in the next years. Various international projects are required to use IPv6 (e.g., EU FP7, EU 2020, etc.). Hence, simulations should be run on IPv6 rather than IPv4, and it is becoming an imperative action to have a reliable, full-featured IPv6 stack for ns-3. IPv6 stack for ns-3 works, but it lacks a number of interesting and useful features. A few missing features are (the list is not exhaustive):&lt;br /&gt;
*# There is no [http://en.wikipedia.org/wiki/Path_MTU_discovery path MTU discovery] see also [http://tools.ietf.org/html/rfc1981 RFC 1981].&lt;br /&gt;
*# Flow Monitor module does not work on the IPv6 stack&lt;br /&gt;
*# FlowLabel header field is not currenly used&lt;br /&gt;
*# IPSec is not supported&lt;br /&gt;
* The candidate should check the missing features and select a set to develop and test. A general test of the IPv6 stack to be done against a reference Linux implementation is a premium.&lt;br /&gt;
** ''Required Experience:'' C++, TCP/IP networking&lt;br /&gt;
** ''Bonus Experience:'' IPv6 protocols&lt;br /&gt;
** ''Interests:'' IPv6 internetworking&lt;br /&gt;
** ''Difficulty:'' easy / medium, depending on the features implemented&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.ietf.org/rfc/rfc4294.txt RFC 4294 - IPv6 Node Requirements]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc1981 RFC 1981 - Path MTU Discovery for IP version 6]&lt;br /&gt;
*** ns-3 Flowmon module documentation&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc6437 RFC 6437 - IPv6 Flow Label Specification]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4302 RFC 4302 - IP Authentication Header]&lt;br /&gt;
*** [http://tools.ietf.org/html/rfc4303 RFC 4303 - IP Encapsulating Security Payload (ESP)]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Multicast IPv6 traffic support ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tommaso.pecorella@unifi.it Tommaso Pecorella]&lt;br /&gt;
&lt;br /&gt;
* '''Multicast IPv6 traffic:''' Multicast traffic support is of paramount importance for IPv6 networks. While Multicast traffic is used everyday with local addresses, and ns-3 is supporting it, MLDv2 and PIM are missing. As a consequence global multicast routes must be manually set in routers, which is cumbersome, error-prone and not suitable for realistic scenarios, where the users are joining/leaving multicast groups on the fly. The implementor will have to both modify the actual routing protocols so to enable dynamic multicast routes support and to actually develop the MLDv2 and/or the PIM protocol modules.&lt;br /&gt;
** ''Required Experience:'' C++, IPv6,&lt;br /&gt;
** ''Bonus Experience:'' Multicast routing protocols (MLDv2/IGMPv3 and PIM)&lt;br /&gt;
** ''Interests:'' routing, multicast&lt;br /&gt;
** ''Difficulty:'' medium/hard&lt;br /&gt;
** ''Recommended reading:''&lt;br /&gt;
*** [http://www.h3c.com/portal/Products___Solutions/Products/Switches/H3C_S5500-SI_Series_Switches/White_Paper/200806/688942_57_0.htm Multicast Technology White Paper]&lt;br /&gt;
*** [http://www.alliedtelesis.co.nz/documentation/at9800/291/pdf/ipv6mu.pdf IPv6 Multicasting]&lt;br /&gt;
*** All the relevant RFCs (search in [http://www.rfc-editor.org/search/rfc_search.php RFC Editor search engine])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  High performance ns-3 emulation with Direct NIC Access   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jose.nunez@cttc.cat José Nuñez]&lt;br /&gt;
&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of PF_RING sockets. &lt;br /&gt;
As part of this project, the student shall integrate the use of PF_RING sockets into the ns-3 emulation framework. For example, the student could create a new class HighSpeedEmuNetDevice using PF_RING sockets, and then do some profiling to verify the improvement in performance with respect to the existing ns-3 EmuNetDevice.&lt;br /&gt;
* ''Required Experience:'' C++, Linux &lt;br /&gt;
* ''Interests:'' network performance, emulation&lt;br /&gt;
* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** http://www.ntop.org/products/pf_ring/libzero-for-dna/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===  LTE Idle Mode Procedures   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:jaime.ferragut@cttc.es Jaime Ferragut] [mailto:nicola.baldo@cttc.es Nicola Baldo]&lt;br /&gt;
&lt;br /&gt;
* The current ns-3 LTE module does not support idle mode procedures. As part of the GSoC, a student could consider implementing one or more of the following procedures: Cell selection and reselection, Paging, Tracking Area Update.&lt;br /&gt;
* ''Required Experience:'' C++, LTE&lt;br /&gt;
* ''Interests:'' mobility management&lt;br /&gt;
* ''Difficulty:'' medium/hard&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** 3GPP TS 36.300 &amp;quot;E-UTRA and E-UTRAN overall description&amp;quot;, section 10.1.1 &amp;quot;Mobility Management in ECM-IDLE&amp;quot;&lt;br /&gt;
** 3GPP TS 36.304 &amp;quot;User Equipment (UE) procedures in idle mode&amp;quot;&lt;br /&gt;
** 3GPP TS 24.301 &amp;quot;Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===  Decouple traffic generators from sockets   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* ns-3 uses applications that are part traffic generator, part socket-based application.  The traffic generation part is not decoupled from the sockets API, making it hard to use applications over non-socket APIs such as future sensor networks.  This project would work on a cleaner separation between traffic generator (OnOffApplication) and sockets.&lt;br /&gt;
* ''Required Experience:'' C++, sockets API&lt;br /&gt;
* ''Interests:'' &lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** Unix Network Programming (Stevens) or equivalent&lt;br /&gt;
&lt;br /&gt;
===  ARP and NDisc cache visibility   ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson] [mailto:rivanvx@gmail.com Vedran Miletić]&lt;br /&gt;
&lt;br /&gt;
* There is no API for reading and manipulating the IPv4 ARP and IPv6 Neighbor Discovery caches.  Something similar to how PrintRoutes is done for IPv4 would be useful.  Additional work on this project could focus on IP address handling for interfaces (bugs 757 and 760), and bug 187 (enabling perfect ARP).&lt;br /&gt;
* ''Required Experience:'' C++&lt;br /&gt;
* ''Interests:'' IPv4 and Ipv6&lt;br /&gt;
* ''Difficulty:'' easy/medium&lt;br /&gt;
* ''Recommended reading:''&lt;br /&gt;
** source code in src/internet, and the bugs mentioned above&lt;br /&gt;
&lt;br /&gt;
=== INSTOOLS for ns-3 ===&lt;br /&gt;
&lt;br /&gt;
Mentors:  [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''INSTOOLS for ns-3:''' [http://groups.geni.net/geni/wiki/InstrumentationTools INSTOOLS] is a software instrumentation package for GENI experiments.  It logs a lot of artifacts of experiments, such as ARP and IP routing tables, Netflow graphs, etc, to databases.  The aim of this project is to instrument ns-3 nodes to capture as much of this data as is applicable.  A bonus is to try to integrate further with ProtoGENI and INSTOOLS such as making the ns-3 data archived just like it was a GENI experiment.&lt;br /&gt;
* ''Required Experience:'' Familiarity with Linux networking and with C++ programming.  &lt;br /&gt;
* ''Bonus Experience:'' Experience with GENI and/or Emulab&lt;br /&gt;
* ''Interests:'' Simulator tool development, integration with testbed experiments&lt;br /&gt;
* ''Difficulty:'' Medium&lt;br /&gt;
* ''Recommended Reading:'' http://groups.geni.net/geni/wiki/InstrumentationTools&lt;br /&gt;
&lt;br /&gt;
=== bufferbloat-related models ===&lt;br /&gt;
&lt;br /&gt;
Mentors: [mailto:tomh@tomh.org Tom Henderson]&lt;br /&gt;
&lt;br /&gt;
'''bufferbloat models:''' [https://www.youtube.com/watch?v=-D-cJNtKwuw Bufferbloat] is an interesting contemporary research topic. &lt;br /&gt;
This project proposal is to develop models, examples, and visualizations around the bufferbloat problem.  Some technical solutions include Linux Byte Queue Limits (BQL) and active queue management (AQM) techniques (we just have RED queues in ns-3-dev but no models yet for the others).&lt;br /&gt;
Note:  There is already some ns-3 code available (see below) but the authors have not&lt;br /&gt;
updated it for a while; this could be a starting point.  Also, work could&lt;br /&gt;
be done on using actual Linux code in the ns-3 Direct Code Execution (DCE)&lt;br /&gt;
project.&lt;br /&gt;
* ''Interests:'' Internet performance, linux kernel networking  &lt;br /&gt;
* ''Difficulty:'' easy to hard, depending on the depth of the project&lt;br /&gt;
* ''Recommended reading:'' &lt;br /&gt;
** http://gettys.wordpress.com/category/bufferbloat/&lt;br /&gt;
** [http://www.bufferbloat.net/projects/cerowrt CeroWrt]&lt;br /&gt;
** [http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf ICCRG presentation]&lt;br /&gt;
** [http://pollere.net/CoDel.html ns-2 code]&lt;br /&gt;
** [https://codereview.appspot.com/6463048/ ns-3 code review]&lt;br /&gt;
&lt;br /&gt;
=== High performance ns-3 emulation with Direct NIC Access (2) ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
The current ns-3 emulation framework has certain limitations in terms of throughput performance, due to the computationally intensive polling between the user space ns-3 instance and the kernel. One reason for this limitation is the use of PF_INET sockets. An alternative that is expected to yield better performance is the use of netmap packet I/O.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Introducing netmap interface as a FdNetDeviceHelper.&lt;br /&gt;
# Performance comparison between existing one (i.e., EmuNetDevice) with the netmap one.&lt;br /&gt;
# Creating a patch for fdnetdevice module (and ask reviews).&lt;br /&gt;
# Documentation including how netmap should be installed/configured.Though netmap supports FreeBSD platform, it is fine to start only with Linux version in this project.&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C++, Linux, Profiling (e.g., gprof/oprofile)&lt;br /&gt;
* ''Interests:'' network performance, emulation* ''Difficulty:'' hard&lt;br /&gt;
* ''Recommended reading:''** [http://info.iet.unipi.it/~luigi/netmap/ netmap]&lt;br /&gt;
** Luigi Rizzo, [http://info.iet.unipi.it/~luigi/papers/20120503-netmap-atc12.pdf netmap: a novel framework for fast packet I/O], Usenix ATC'12, June 2012&lt;br /&gt;
** Luigi Rizzo, [http://queue.acm.org/detail.cfm?id=2103536 Revisiting network I/O APIs: The netmap Framework], Communications of the ACM, March 2012&lt;br /&gt;
** [http://nepi.inria.fr/wiki/FdNetDevice FdNetDevice] (will be merged at ns-3.17)&lt;br /&gt;
&lt;br /&gt;
=== Linux SCTP support over DCE ===&lt;br /&gt;
Mentors: [mailto:tazaki@sfc.wide.ad.jp Hajime Tazaki]&lt;br /&gt;
&lt;br /&gt;
Stream Control Transmission Protocol (SCTP) is an alternate transport protocol rather than traditional TCP and UDP. It covers a broad feature for application messaging, but one of interesting feature is using multiple streams in a single session. Almost none of applications are using SCTP at this moment in fact, but it is used in the back-end of LTE.&lt;br /&gt;
&lt;br /&gt;
In this project, instead of implementing huge amount of specification of SCTP (134 pages in RFC 2960), we reuse existing Linux implementation over Direct Code Execution (DCE). DCE allows us to simulate existing implementation over ns-3 without (ideally) modifying original code.&lt;br /&gt;
&lt;br /&gt;
The target of this project would be:&lt;br /&gt;
&lt;br /&gt;
# Modifying DCE Linux module to support SCTP&lt;br /&gt;
## enabling CONFIG_IP_SCTP option (and related one) and build it (I have incomplete patch)&lt;br /&gt;
## writing simple SCTP program (I also have)&lt;br /&gt;
## writing sample scenario script using above SCTP program (I also have)&lt;br /&gt;
# Implement missing part of DCE Linux module to run SCTP code over ns-3&lt;br /&gt;
# Implement DCE Cradle wrapper socket for SCTP (optional)&lt;br /&gt;
# Create patch for ns-3-dce (and code review)&lt;br /&gt;
&lt;br /&gt;
* ''Required Experience:'' C/C++, Linux, Kernel&lt;br /&gt;
* ''Interests:'' transport protocol, Direct Code Execution&lt;br /&gt;
* ''Difficulty:'' medium* ''Recommended reading:''&lt;br /&gt;
** [http://tools.ietf.org/html/rfc3286 RFC 3286] An Introduction to the Stream Control Transmission Protocol]&lt;br /&gt;
** [http://lksctp.sourceforge.net Linux Kernel Stream Control Transmission Protocol Tools (lksctp-tools)]&lt;br /&gt;
** [http://linux.die.net/man/7/sctp sctp(7) - Linux man page]&lt;br /&gt;
** [http://code.nsnam.org/ns-3-dce/file/456bb670b7d2/example/dce-dccp.cc DCE DCCP protocol example simulation scenario]&lt;br /&gt;
** [http://www.nsnam.org/projects/direct-code-execution/ Direct Code Execution]&lt;br /&gt;
** [https://github.com/thehajime/net-next-sim DCE Linux module]&lt;br /&gt;
** [https://sites.google.com/site/thehajime/Home/wns3-2013-tazaki.pdf?attredirects=0 DCE Cradle]&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7470</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7470"/>
		<updated>2013-03-28T06:55:57Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Bugs being worked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7469</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7469"/>
		<updated>2013-03-28T06:55:20Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Schedule for 1.0 release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* &amp;lt;s&amp;gt;15th March, 2013: call for voluntary to walk through tutorial document and testing&amp;lt;/s&amp;gt;&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7464</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7464"/>
		<updated>2013-03-24T14:00:21Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;br /&gt;
* put stable versions/revisions to bakeconf.xml&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7459</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7459"/>
		<updated>2013-03-22T13:50:07Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Things to do */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate ns-3-linux and ns-3-linux-3 repository to github's one.&amp;lt;/s&amp;gt;&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7458</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7458"/>
		<updated>2013-03-22T01:34:52Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Test Instruction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# (If possible) Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* migrate ns-3-linux and ns-3-linux-3 repository to github's one.&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce (ask Tom?)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7457</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7457"/>
		<updated>2013-03-22T01:34:19Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release the first version of DCE with coming April release of ns-3. We would like to ask your help for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* migrate ns-3-linux and ns-3-linux-3 repository to github's one.&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce (ask Tom?)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7406</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7406"/>
		<updated>2013-03-14T13:13:56Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release first version of DCE with coming April release of ns-3. We'd like to ask your volunteer for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
We're grateful for your volunteer to review release document and test with the document.&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
==Document for Review==&lt;br /&gt;
* Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
* User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* migrate ns-3-linux and ns-3-linux-3 repository to github's one.&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce (ask Tom?)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7405</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7405"/>
		<updated>2013-03-14T13:12:30Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: /* Call for volunteer of Testing, Reviewing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteers of Testing, Reviewing =&lt;br /&gt;
Dear folks,&lt;br /&gt;
&lt;br /&gt;
We, Direct Code Execution (DCE) project, are going to release first version of DCE with coming April release of ns-3. We'd like to ask your volunteer for document reviews and tests.&lt;br /&gt;
&lt;br /&gt;
We're grateful for your volunteer to review release document and test with the document.&lt;br /&gt;
The followings are the instruction to the test.&lt;br /&gt;
If you have any question, please drop an email to me (Hajime Tazaki: tazaki at sfc.wide.ad.jp).&lt;br /&gt;
&lt;br /&gt;
*Document for Review&lt;br /&gt;
** Quick Start Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html&lt;br /&gt;
** User's Guide: http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html&lt;br /&gt;
&lt;br /&gt;
==Test Instruction==&lt;br /&gt;
&lt;br /&gt;
# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/index.html Quick Start Guide] and check whether contents are correct and able to finish without any issues.# Follow [http://www.nsnam.org/~thehajime/ns-3-dce-next-doc/doc/build/html/dce-user-doc.html User's Guide] and check whether contents are correct and able to finish without any issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Report Template==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
OS: (Distribution, e.g. Ubuntu 12.04 64bits)&lt;br /&gt;
Result:&lt;br /&gt;
1 (Quick Start Guide): Success/Fail/Other&lt;br /&gt;
&lt;br /&gt;
2 (User's Guide): Success/Fail/Other&lt;br /&gt;
Comments:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* migrate ns-3-linux and ns-3-linux-3 repository to github's one.&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce (ask Tom?)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7404</id>
		<title>Dce-1.0</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Dce-1.0&amp;diff=7404"/>
		<updated>2013-03-13T08:23:41Z</updated>

		<summary type="html">&lt;p&gt;Tazaki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Schedule for 1.0 release =&lt;br /&gt;
* 15th March, 2013: call for voluntary to walk through tutorial document and testing&lt;br /&gt;
* 30th March, 2013: new feature freeze&lt;br /&gt;
* (2weeks before release, TBD): code freeze&lt;br /&gt;
* (TBD): RC-1&lt;br /&gt;
&lt;br /&gt;
* (TBD): dce-1.0 release&lt;br /&gt;
&lt;br /&gt;
= Call for volunteer of Testing, Reviewing =&lt;br /&gt;
* (with Instruction)&lt;br /&gt;
* Test patterns&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
../bake.py configure -c ../bakeconf.xml -e dce-ns3&lt;br /&gt;
../bake.py configure -c ../bakeconf.xml -e dce-quagga&lt;br /&gt;
&lt;br /&gt;
../bake.py configure -c ../bakeconf.xml -e dce-linux&lt;br /&gt;
../bake.py configure -c ../bakeconf.xml -e dce-quagga&lt;br /&gt;
../bake.py configure -c ../bakeconf.xml -e dce-umip &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Supported/Unsupported features =&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! UcontextFiberManager !! PthreadFiberManager&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory || Supported || Supported&lt;br /&gt;
|-&lt;br /&gt;
| CoojaLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|-&lt;br /&gt;
| DlmLoaderFactory with elf-loader || Should work, but won't support || Unsupported ([https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Bug1513])&lt;br /&gt;
|}&lt;br /&gt;
= Bugs being worked =&lt;br /&gt;
* &amp;lt;s&amp;gt; 1580: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1580 doxygen description] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1594: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1594 gcov coverage test support for applications over DCE] Hajime&lt;br /&gt;
* &amp;lt;s&amp;gt; 1593: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1593 support DCE sub-module under myscripts directory] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;1448: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1448 DCE Kernel mode. Create a helper in order to create automatically the static routes.] Hajime &amp;lt;/s&amp;gt;&lt;br /&gt;
* 1513: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1513 Use Linux kernel stack for ns-3 applications] Hajime&lt;br /&gt;
* 1455: [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1455 Support the python binding of DCE] Hajime&lt;br /&gt;
&lt;br /&gt;
= Pending code review =&lt;br /&gt;
* [https://codereview.appspot.com/6856090/ Bug1513:   Use Linux kernel stack for ns-3 applications]&lt;br /&gt;
* [https://codereview.appspot.com/7635043/ Change Scheduling of event according to NS-3 requisite: ie use only the main thread to]&lt;br /&gt;
&lt;br /&gt;
= Things to do =&lt;br /&gt;
* &amp;lt;s&amp;gt;migrate repository from 'furbani' to 'code'&amp;lt;/s&amp;gt;&lt;br /&gt;
* migrate ns-3-linux and ns-3-linux-3 repository to github's one.&lt;br /&gt;
* create jenkins test suite&lt;br /&gt;
* fix valgrind errors (so many)&lt;br /&gt;
* test with document (quick start guide, user's guide)&lt;br /&gt;
* update web page (http://www.nsnam.org/projects/direct-code-execution/)&lt;br /&gt;
* nsnam.org/doc/dce (ask Tom?)&lt;/div&gt;</summary>
		<author><name>Tazaki</name></author>
	</entry>
</feed>