MaintainersOct2023
Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects
Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers
Date/Time/Venue
Topic: ns-3.41 and future plans
Zoom meeting.
- October 10, 2023 08:00 AM Pacific Time (US and Canada), 15h00 UTC
Join Zoom Meeting https://washington.zoom.us/j/95127092879?pwd=dUlsUEdYQks1OXBhRkpLcTRJb3F2Zz09
Meeting ID: 951 2709 2879 Passcode: 580883
Agenda
1) Introductions; what we are working on (5-10 minutes)
2) ns-3.41 January release goals and plans from anyone? (15-20 minutes)
- Plan to start supporting C++-20
- Tutorial replacement is underway
- Distributing via Docker (Eduardo)
- ns-3-allinone and contrib mobules
3) WNS3 2024 plans, and feedback from WNS3 2023 (15 minutes)
- Discuss this meeting summary document
4) Longer term goals and plans, including the future of the UW ns-3 consortium (10 minutes)
Materials
Minutes
Attendees: Tom Henderson, Tommaso Pecorella, Gabriel Ferreira, Alberto Gallegos, Stefano Avallone, Eduardo Almeida, Biljana Bojovic, Katerina Koutlia, Mohit Tahiliani
1. Introduction
Tom mentioned that he is working on a few ns-3-related work projects over the next 12 months: 5G NR sidelink, multi-BSS Wi-Fi, and L4s over Wi-Fi. Stefano shared that he continues to work on EMLSR and 802.11be features.
2. ns-3.41
Gabriel gave a brief C++20 update, stating that it has been a pain since each compiler has different implementation support, and many of our dependencies like GTK have issues. Tom mentioned that the move to C++20 has a lot of support and we may move more aggressively to newer compilers than typical. We had some discussion about trying to break apart the existing MR into pieces that can be merged immediately. Stefano pointed out the danger of not moving to C++20 fast enough-- having to constantly fix small incompatibilities in new code that goes into the mainline. Anyway, this is a big change and will likely be a process.
Biljana mentioned the need for some expertise on antenna arrays to review a pending MR, and the need to have some discussions with Wi-Fi maintainers about aligning how antenna arrays are handled and different aspects of spectrum module (in support of NR-U coexistence studies on the shared spectrum channel). This can be done in a separate meeting.
Tom pointed out the ongoing development (see the link in the slides) of a new tutorial (see Mohit's presentation from last September). This is being done out of tree and will move to an ns-3-dev MR when ready.
Eduardo talked a bit about Docker and the implications for our CI system, and will follow up with more details later. He suggested to relax some of the Linux platform testing (C++ compilers should be enough). Tommaso also mentioned that Docker would help the CI system but we need to still support native builds because they are faster. Tom would like to release DCE on Docker also, to simplify the install experience.
Tommaso mentioned that a lot of work is coming in lr-wpan and 6lowpan, and Alberto (in separate mail) outlined some activities. Much of this may land in the ns-3.42 release.
Tom expressed interest in making a different ns-3-allinone that contained contributed modules. Further testing of these modules and dependencies may cause some additional load on the CI system.
3. WNS3 2023
Tom reported on WNS3 2023 highlights (see slides) and noted that WNS3 2024 will be in May or early June next year, hosted by CTTC. The next step will be selection of a week to hold it. He mentioned his continued interest in having a remote attendance option but that we may need to adjust to make the experience smoother.
Tom mentioned five possible initiatives (see slides) that were discussed at WNS3 2023, and that he was soliciting collaborators or leaders on those topics, but volunteers were lacking.
4. Longer term plans
Tom mentioned that the UW ns-3 consortium will likely wrap up in 2024 due to lack of industrial participation. About $10K is available to fund some projects between now and next year. The project will need to migrate to using the SPI bank account. He is exploring options for a new project governance model and steering committee, and will need to consider what are the infrastructure (hosting) needs.
