Statistics page), but in summary, we have a users mailing list of about 4603 members as of February 2015 (an increase of about 1200 in the past year) averaging roughly 900 posts per month. Our developers' list has 1480 subscribers, and the code base has a total of 175 authors and about 10 active maintainers. ns-3 is operated as an open source project with some financial backing from three NSF grants and funding from the French government (and via help from Google Summer of Code) but with most current contributions coming from interested researchers and students worldwide. We use a GPLv2 licensing model and heavily use mailing lists, and IRC for code springs, but typically not other social media.

Projects

802.15.4 realistic MAC and Energy Model The current 802.15.4 MAC implementation in ns-3, lacks sleep features. The radio is assumed to be always active, which is not true for nodes deployed in the field which usually employ some sort of sleep/wake mechanism in order to conserve energy. The goal of this project is to develop a realistic MAC model and link it with the energy model in order to simulate realistic scenarios where a node’s energy can get depleted resulting in changes in the network topology.
Carrier Aggregation support for the LTE module 3GPP standardizes, in release R10, the Carrier Aggregation (CA) technology. This consists of the possibility, for a single user equipment (UE), to aggregate Radio Resources belonging to different carriers, in order to have more bandwidth available, and a higher potential throughput. The idea is to improve the current LENA implementation, with CA functionalities, by implementing a sort of “proxy” between the RLC/RRC layer and MAC/Scheduler layers, associated to the multiple carriers.
Implementing multipath TCP (MPTCP) in ns3 I have a working version of multipath TCP for ns3.19 that I can't share publicly yet (I can with the ns3 admins). My idea is - during the first 6 weeks - to add more features, refactor a few things so that it can be upstreamed. During the last 4 weeks I would like to implement per node clock to be able to simulate time distribution protocols. This proposition is a follow up of my email: http://network-simulator-ns-2.7690.n7.nabble.com/Addition-of-per-node-clocks-in-ns3-td29301.html
TCP layer refactoring with automated test on RFC-compliance and validation A step-by-step refactoring of the TCP layer, which should lead to a more easy way to test congestion control and RFC compliancy of its state machine. Four steps are needed, and they will be detailed below.