Ns-3.34

From Nsnam
Revision as of 18:17, 28 April 2021 by Tomh (talk | contribs) (update based on maintainers call)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This page was used to summarize the release planning for ns-3.34. The ns-3 release process is listed here and here.

Release goals

This page highlights some features and issues that ns-3 maintainers have mentioned as goals for ns-3.34. For a more current look at what is being actively worked on, search for the 'ns-3.34' milestone in the issue tracker and merge request tracker:

The following goals have been listed by various ns-3 maintainers, with notes about progress towards them.

  • Finish 2020 Google Summer of Code and ns-3 Summer of Code merges
    • Status: App Store and most of queue code have been merged. TCP Prague and NetDeviceState is still unmerged (will slip to future release).
  • Wi-Fi: Merge the pending 802.11ax support (see the Merge Request tracker), PHY layer rework, possibly 11be and NR-U
    • Status: Stefano has one more patch (round robin scheduler) to post and merge, and then we can declare
  • Traffic control: Remaining CAKE support (ACK filtering)
    • Status: Postponed to future release.
  • TCP: Add BBRv1 and BBRv2 models, and other lingering TCP patches (FACK, DSACK, RACK, AccECN, ECN++); path MTU discovery?
    • Status: BBRv1 is still in the ns-3.34 plan; other feature for
  • core: Additional support for newer C++ language features
    • Status: Can add up to C++14 to the extent that changes do not impact our Python bindings
  • underwater acoustic networks: integration with world ocean simulation system (WOSS)
    • Status: TBD
  • full-duplex CSMA
    • Status: Probably slipping to future release
  • phased array antenna
    • Status: Merged
  • hexagonal position allocator
    • Status: Probably slipping to future release.
  • 6LoWPAN neighbor discovery and RFC alignment, possibly RPL
    • Status: Probably slipping to future release.