Fix Markdown lint warnings (MD003)

MD003 - Header style
2024-10-18 13:58:11 +01:00
parent ac36eec08c
commit fdbcfa8f29
2 changed files with 111 additions and 222 deletions
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -1,5 +1,4 @@
-ns-3: API and model change history
-==================================
+# ns-3: API and model change history

 ns-3 is an evolving system and there will be API or behavioral changes from time to time. Users who try to use scripts or models across versions of ns-3 may encounter problems at compile time, run time, or may see the simulation output change.

@@ -13,8 +12,7 @@ Note that users who upgrade the simulator across versions, or who work directly

 This file is a best-effort approach to solving this issue; we will do our best but can guarantee that there will be things that fall through the cracks, unfortunately. If you, as a user, can suggest improvements to this file based on your experience, please contribute a patch or drop us a note on ns-developers mailing list.

-Changes from ns-3.43 to ns-3-dev
--------------------------------
+## Changes from ns-3.43 to ns-3-dev

 ### New API

@@ -24,8 +22,7 @@ Changes from ns-3.43 to ns-3-dev

 ### Changed behavior

-Changes from ns-3.42 to ns-3.43
-------------------------------
+## Changes from ns-3.42 to ns-3.43

 ### New API

@@ -67,8 +64,7 @@ Changes from ns-3.42 to ns-3.43
 * (lr-wpan) Upon a beacon request command, beacons are transmitted after a jitter to reduce the probability of collisions.
 * (tcp) TCP Proportional Rate Reduction (PRR) recovery has been aligned to the updates in draft-ietf-tcpm-prr-rfc6937bis

-Changes from ns-3.41 to ns-3.42
-------------------------------
+## Changes from ns-3.41 to ns-3.42

 ### New API
 * (antenna) Added `CircularApertureAntennaModel` class which characterizes the antenna gain pattern of the reflector antenna with circular aperture described in 3GPP TR 38.811 v15.4.0, Section 6.4.1
@@ -111,8 +107,7 @@ Changes from ns-3.41 to ns-3.42
 * (mobility) Fixed the corner rebound direction in `RandomWalk2d[Outdoor]MobilityModel` and the initial direction in case of node starting from a border or corner.
 * (tcp) TcpCubic and TcpLinuxReno will no longer grow their congestion window when application-limited, now matching Linux behavior

-Changes from ns-3.40 to ns-3.41
-------------------------------
+## Changes from ns-3.40 to ns-3.41

 ### New API

@@ -173,8 +168,7 @@ Changes from ns-3.40 to ns-3.41
 * (tcp) TCP Cubic (the default congestion control in ns-3) now supports TCP-friendliness by default (see RFC 9438 Section 4.3), making the congestion window growth somewhat more aggressive.  This follows the default Linux behavior.
 * (wifi) Increase the duration of the timer started when waiting for an ADDBA_RESPONSE from 1ms to 5ms to better account for the time required by the recipient to access the medium and complete the frame exchange (which may involve protection with (MU-)RTS/CTS).

-Changes from ns-3.39 to ns-3.40
-------------------------------
+## Changes from ns-3.39 to ns-3.40

 ### New API

@@ -203,8 +197,7 @@ Changes from ns-3.39 to ns-3.40
 * (wifi) Upon ML setup, a non-AP MLD updates the IDs of the setup links to match the IDs used by the AP MLD.
 * (wifi) Attribute **TrackSignalsFromInactiveInterfaces** in SpectrumWifiPhy has been defaulted to be enabled.

-Changes from ns-3.38 to ns-3.39
-------------------------------
+## Changes from ns-3.38 to ns-3.39

 ### New API

@@ -273,8 +266,7 @@ Changes from ns-3.38 to ns-3.39
 * (wifi) Protection mechanisms (e.g., RTS/CTS) are not used if destinations have already received (MU-)RTS in the current TXOP
 * (wifi) Protection mechanisms can be used for management frames as well (if needed)

-Changes from ns-3.37 to ns-3.38
-------------------------------
+## Changes from ns-3.37 to ns-3.38

 ### New API

@@ -318,8 +310,7 @@ Changes from ns-3.37 to ns-3.38
 * (wifi) Control frames (specifically, BlockAckRequest and MU-BAR Trigger Frames) are stored in the wifi MAC queue and no longer in a dedicated BlockAckManager queue
 * (wifi) BSSIDs are no longer hashed by the ApInfo comparator because it may lead to different results on different platforms

-Changes from ns-3.36 to ns-3.37
-------------------------------
+## Changes from ns-3.36 to ns-3.37

 ### New API

@@ -386,8 +377,7 @@ Changes from ns-3.36 to ns-3.37
 * (propagation) The O2I Low/High Building Penetration Losses will add losses in the pathloss calculation when buildings are present and a UE results to be in O2I state. In order to not consider these losses, they can be disabled by setting BuildingPenetrationLossesEnabled to false.
 * (wifi) The **Channel** attribute of `WifiNetDevice` is deprecated because it became ambiguous with the introduction of multiple links per device. The **Channel** attribute of `WifiPhy` can be used instead.

-Changes from ns-3.36 to ns-3.36.1
---------------------------------
+## Changes from ns-3.36 to ns-3.36.1

 ### New API

@@ -410,8 +400,7 @@ The build system API has not changed since ns-3.36.  Several bugs were fixed and

 Apart from the bugs fixed (listed in the RELEASE_NOTES), the simulation model behavior should not have changed since ns-3.36.

-Changes from ns-3.35 to ns-3.36
-------------------------------
+## Changes from ns-3.35 to ns-3.36

 ### New API

@@ -449,8 +438,7 @@ Changes from ns-3.35 to ns-3.36
 * NixVectorRouting: `NixVectorRouting` can now better cope with topology changes. In-flight packets are not anymore causing crashes, and the path is dynamically rebuilt by intermediate routers (this happens only to packets in-flight during the topology change).
 * Mesh (Wi-Fi) forwarding hops now have a configurable random variable-based forwarding delay model, with a default mean of 350 us.

-Changes from ns-3.34 to ns-3.35
-------------------------------
+## Changes from ns-3.34 to ns-3.35

 ### New API

@@ -481,8 +469,7 @@ Changes from ns-3.34 to ns-3.35
 * Wi-Fi: A-MSDU aggregation now implies that constituent MSDUs are immediately dequeued from the EDCA queue and replaced by an MPDU containing the A-MSDU. Thus, aggregating N MSDUs triggers N dequeue operations and 1 enqueue operation on the EDCA queue.
 * Wi-Fi: MPDUs being passed to the PHY layer for transmission are not dequeued, but are kept in the EDCA queue until they are acknowledged or discarded. Consequently, the BlockAckManager retransmit queue has been removed.

-Changes from ns-3.33 to ns-3.34
-------------------------------
+## Changes from ns-3.33 to ns-3.34

 ### New features and API

@@ -522,8 +509,7 @@ Changes from ns-3.33 to ns-3.34
 * The **LTE RLC Acknowledged Mode (AM) transmit buffer** is now limited by default to a size of (`1024 * 10`) bytes. Configuration of unlimited behavior can still be made by passing the value of zero to the new attribute `MaxTxBufferSize`.
 * A **non-AP MLD loses association** when receiving no beacon an any link link for an interval of duration equal to the maximum number of missed beacons times the interval between two consecutive Beacon frames.

-Changes from ns-3.32 to ns-3.33
-------------------------------
+## Changes from ns-3.32 to ns-3.33

 ### New API

@@ -558,8 +544,7 @@ Changes from ns-3.32 to ns-3.33
 * TCP now implements the Linux-like **congestion window reduced (CWR)** state when explicit congestion notification (ECN) is enabled.
 * `TcpDctcp` now inherits from `TcpLinuxReno`, making its congestion avoidance track more closely to that of Linux.

-Changes from ns-3.31 to ns-3.32
-------------------------------
+## Changes from ns-3.31 to ns-3.32

 ### New API

@@ -598,8 +583,7 @@ Changes from ns-3.31 to ns-3.32
 * WifiPhy forwards up MPDUs from an A-MPDU under reception as long as they arrive at the PHY, instead of forwarding up the whole A-MPDU once its reception is completed.
 * The ns-3 TCP model was changed to set the initial congestion window to 10 segments instead of 1 segment (to align with default Linux configuration).

-Changes from ns-3.30 to ns-3.31
-------------------------------
+## Changes from ns-3.30 to ns-3.31

 ### New API

@@ -653,8 +637,7 @@ Changes from ns-3.30 to ns-3.31
 * The implementation of the **Wi-Fi channel access** functions has been improved to make them more conformant to the IEEE 802.11-2016 standard. Concerning the DCF, the backoff procedure is no longer invoked when a packet is queued for transmission and the medium has not been idle for a DIFS, but it is invoked if the medium is busy or does not remain idle for a DIFS after the packet has been queued. Concerning the EDCAF, transmissions are now correctly aligned at slot boundaries.
 * Various wifi physical layer behavior around channel occupancy calculation, phy state calculation, and handling different channel widths has been updated.

-Changes from ns-3.29 to ns-3.30
-------------------------------
+## Changes from ns-3.29 to ns-3.30

 ### New API

@@ -725,8 +708,7 @@ Changes from ns-3.29 to ns-3.30
  * The RachConfigCommon structure in LteRrcSap API has been extended to include `TxFailParam`. This new field would enable an eNB to indicate how many times T300 timer can expire at the UE. Upon reaching this count, the UE aborts the connection establishment, and performs the cell selection again. See TS 36.331 5.3.3.6.
 * The timer T300 in LteUeRrc class is now bounded by the standard min and max values defined in 3GPP TS 36.331.

-Changes from ns-3.28 to ns-3.29
-------------------------------
+## Changes from ns-3.28 to ns-3.29

 ### New API

@@ -803,8 +785,7 @@ Changes from ns-3.28 to ns-3.29
 * The maximum size UDP packet of the UdpClient application is no longer limited to 1500 bytes.
 * The default values of the `MaxSlrc` and `FragmentationThreshold` attributes in WifiRemoteStationManager were changed from 7 to 4 and from 2346 to 65535, respectively.

-Changes from ns-3.27 to ns-3.28
-------------------------------
+## Changes from ns-3.27 to ns-3.28

 ### New API

@@ -835,8 +816,7 @@ Changes from ns-3.27 to ns-3.28
 * The CsmaNetDevice::PhyTxBeginTrace will trace all attempts to transmit, even those that result in drops. Previously, eventual channel drops were excluded from this trace.
 * The TCP congestion window trace now does not report on window inflation during fast recovery phase because it is no longer internally maintained as an inflated value (a separate trace called CongestionWindowInflated can be used to recover the old trace behavior).

-Changes from ns-3.26 to ns-3.27
-------------------------------
+## Changes from ns-3.26 to ns-3.27

 ### New API

@@ -912,8 +892,7 @@ Changes from ns-3.26 to ns-3.27
 * The default value of the `EnableBeaconJitter` attribute in ApWifiMac was changed from false to true.
 * The NormalClose() callback of a TcpSocket object used to fire upon leaving `TIME_WAIT` state (`2*MSL` after FINs have been exchanged). It now fires upon entering `TIME_WAIT` state. Timing of the callback for the other path to state CLOSED (through `LAST_ACK`) has not been changed.

-Changes from ns-3.25 to ns-3.26
-------------------------------
+## Changes from ns-3.25 to ns-3.26

 ### New API

@@ -948,8 +927,7 @@ This section is for behavioral changes to the models that were not due to a bug
 * The relationship between Wi-Fi channel number, frequency, channel width, and Wi-Fi standard has been revised (see bug 2412). Previously, ChannelNumber and Frequency were attributes of class YansWifiPhy, and the frequency was defined as the start of the band. Now, Frequency has been redefined to be the center frequency of the channel, and the underlying device relies on the pair of frequency and channel width to control behavior; the channel number and Wi-Fi standard are used as attributes to configure frequency and channel width. The wifi module documentation discusses this change and the new behavior.
 * AODV now honors the TTL in RREQ/RREP and it uses a method compliant with [RFC 3561](http://www.ietf.org/rfc/rfc3561.txt). The node search radius is increased progressively. This could increase slightly the node search time, but it also decreases the network congestion.

-Changes from ns-3.24 to ns-3.25
-------------------------------
+## Changes from ns-3.24 to ns-3.25

 ### New API

@@ -999,8 +977,7 @@ This section is for behavioral changes to the models that were not due to a bug
 * 802.11n/ac MPDU aggregation is now enabled by default for both `AC_BE` and `AC_VI`.
 * The introduction of the traffic control layer leads to some additional buffering by default in the stack; when a device queue fills up, additional packets become enqueued at the traffic control layer.

-Changes from ns-3.23 to ns-3.24
-------------------------------
+## Changes from ns-3.23 to ns-3.24

 ### New API

@@ -1032,8 +1009,7 @@ Changes from ns-3.23 to ns-3.24

 This section is for behavioral changes to the models that were not due to a bug fix.

-Changes from ns-3.22 to ns-3.23
-------------------------------
+## Changes from ns-3.22 to ns-3.23

 ### New API

@@ -1057,8 +1033,7 @@ This section is for behavioral changes to the models that were not due to a bug
 * In Wi-Fi, HT stations (802.11n) now support two-level aggregation. The InterferenceHelper now distinguishes between the PLCP and regular payload reception, for higher fidelity modeling. ACKs are now sent using legacy rates and preambles. Access points now establish BSSBasicRateSet for control frame transmissions. PLCP header and PLCP payload reception have been decoupled to improve PHY layer modeling accuracy. RTS/CTS with A-MPDU is now fully supported.
 * The mesh module was made more compliant to the IEEE 802.11s-2012 standard and packet traces are now parseable by Wireshark.

-Changes from ns-3.21 to ns-3.22
-------------------------------
+## Changes from ns-3.21 to ns-3.22

 ### New API

@@ -1094,8 +1069,7 @@ This section is for behavioral changes to the models that were not due to a bug
 * The `LrWpanHelper` object was previously instantiating only a `LogDistancePropagationLossModel` on a `SingleModelSpectrumChannel`, but no `PropagationDelayModel`. The constructor now adds by default a `ConstantSpeedPropagationDelayModel`.
 * The Nix-vector routing implementation now uses a lazy flush mechanism, which dramatically speeds up the creation of large topologies.

-Changes from ns-3.20 to ns-3.21
-------------------------------
+## Changes from ns-3.20 to ns-3.21

 ### New API

@@ -1143,8 +1117,7 @@ Changes from ns-3.20 to ns-3.21

 * Behavior will be changed due to the list of bugs fixed (listed in [RELEASE_NOTES.md](RELEASE_NOTES.md)); users are requested to review that list as well.

-Changes from ns-3.19 to ns-3.20
-------------------------------
+## Changes from ns-3.19 to ns-3.20

 ### New API

@@ -1174,8 +1147,7 @@ Changes from ns-3.19 to ns-3.20
 * IPv4 identification field value is now dependent on the protocol field.
 * Point-to-point trace sources now contain PPP headers

-Changes from ns-3.18.1 to ns-3.19
---------------------------------
+## Changes from ns-3.18.1 to ns-3.19

 ### New API

@@ -1214,8 +1186,7 @@ Changes from ns-3.18.1 to ns-3.19
 * IPv6 addresses and routing tables are printed like in Linux `route -A inet6` command.
 * A change in `Ipv[4,6]Interface` enforces the correct behaviour of IP when a device do not support the minimum MTU requirements. This is set to 68 and 1280 octets respectively. IP simulations that may have run over devices with smaller MTUs than 68 or 1280, respectively, will no longer be able to use such devices.

-Changes from ns-3.18 to ns-3.18.1
---------------------------------
+## Changes from ns-3.18 to ns-3.18.1

 ### New API

@@ -1237,8 +1208,7 @@ Changes from ns-3.18 to ns-3.18.1

 * Wifi simulations have additional jitter on AP beaconing (see above) and some bug fixes have been applied to wifi module (see [RELEASE_NOTES.md](RELEASE_NOTES.md))

-Changes from ns-3.17 to ns-3.18
-------------------------------
+## Changes from ns-3.17 to ns-3.18

 ### New API

@@ -1296,8 +1266,7 @@ Changes from ns-3.17 to ns-3.18
 * IPv4's ARP Request and IPv6's NS/RS are now transmitted with a random delay. The delay is, by default, a uniform random variable in time between 0 and 10ms. This is aimed at preventing reception errors due to collisions during wifi broadcasts when the sending behavior is synchronized (e.g. due to applications starting at the same time on several different nodes). This behaviour can be modified by using ArpL3Protocol's `RequestJitter` and Icmpv6L4Protocol's `SolicitationJitter` attributes or by using the new `InternetStackHelper` functions.
 * AODV Hellos are disabled by default. The performance with Hellos enabled and disabled are almost identical. With Hellos enabled, AODV will suppress hellos from transmission, if any recent broadcast such as RREQ was transmitted. The attribute n`s3::aodv::RoutingProtocol::EnableHello` can be used to enable/disable Hellos.

-Changes from ns-3.16 to ns-3.17
-------------------------------
+## Changes from ns-3.16 to ns-3.17

 ### New API

@@ -1387,8 +1356,7 @@ Changes from ns-3.16 to ns-3.17

 * DSR link layer notification has changed. The model originally used `TxErrHeader` in Ptr to indicate the transmission error of a specific packet in link layer; however, it was not working correctly. The model now uses a different path to implement the link layer notification mechanism; specifically, looking into the trace file to find packet receive events. If the model finds one receive event for the data packet, it is used as the indicator for successful data delivery.

-Changes from ns-3.15 to ns-3.16
-------------------------------
+## Changes from ns-3.15 to ns-3.16

 ### New API

@@ -1415,8 +1383,7 @@ Changes from ns-3.15 to ns-3.16
 * Sending a packet through Ipv4RawSocket now supports checksum in the Ipv4Header. It is still not possible to manually put in arbitrary checksum as the checksum is automatically calculated at Ipv4L3Protocol. The user has to enable checksum globally for this to work. Simply calling Ipv4Header::EnableChecksum() for a single Ipv4Header will not work.
 * Now MultiModelSpectrumChannel allows a SpectrumPhy instance to change SpectrumModel at runtime by issuing a call to MultiModelSpectrumChannel::AddRx (). Previously, MultiModelSpectrumChannel required each SpectrumPhy instance to stick with the same SpectrumModel for the whole simulation.

-Changes from ns-3.14 to ns-3.15
-------------------------------
+## Changes from ns-3.14 to ns-3.15

 ### New API

@@ -1435,8 +1402,7 @@ Changes from ns-3.14 to ns-3.15

 * Programs using random variables or models that include random variables may exhibit changed output for a given run number or seed, due to a possible change in the order in which random variables are assigned to underlying pseudo-random sequences. Consult the manual for more information regarding this.

-Changes from ns-3.13 to ns-3.14
-------------------------------
+## Changes from ns-3.13 to ns-3.14

 ### New API

@@ -1503,8 +1469,7 @@ Changes from ns-3.13 to ns-3.14
  [*] Added --useIpv6 flag to switch between IPv4 and IPv6
  ```

-Changes from ns-3.12 to ns-3.13
-------------------------------
+## Changes from ns-3.12 to ns-3.13

 ### Changes to build system

@@ -1561,8 +1526,7 @@ Changes from ns-3.12 to ns-3.13
  * TcpNewReno supports limited transmit (RFC3042) if asserting boolean attribute `ns3::TcpNewReno::LimitedTransmit`
  * Nagle's algorithm supported. Default off, turn on by calling `TcpSocket::SetTcpNoDelay(true)`

-Changes from ns-3.11 to ns-3.12
-------------------------------
+## Changes from ns-3.11 to ns-3.12

 ### Changes to build system

@@ -1583,8 +1547,7 @@ Changes from ns-3.11 to ns-3.12

 * IPv4 fragmentation is now supported.

-Changes from ns-3.10 to ns-3.11
-------------------------------
+## Changes from ns-3.10 to ns-3.11

 ### Changes to build system

@@ -1661,8 +1624,7 @@ Changes from ns-3.10 to ns-3.11
 * If the data inside the TCP buffer is less than the available window, TCP tries to ask for more data to the application, in the hope of filling the usable transmission window. In some cases, this change allows sending bigger packets than the previous versions, optimizing the transmission.
 * In TCP, the ACK is now processed before invoking any routine that deals with the segment sending, except in case of retransmissions.

-Changes from ns-3.9 to ns-3.10
------------------------------
+## Changes from ns-3.9 to ns-3.10

 ### Changes to build system

@@ -1732,8 +1694,7 @@ Changes from ns-3.9 to ns-3.10

  As part of the TCP socket refactoring, a new TCP implementation provides slightly different behavior than the previous TcpSocketImpl that provided only fast retransmit. The default behavior now is NewReno which provides fast retransmit and fast recovery with window inflation during recovery.

-Changes from ns-3.8 to ns-3.9
-----------------------------
+## Changes from ns-3.8 to ns-3.9

 ### Changes to build system

@@ -1805,8 +1766,7 @@ Changes from ns-3.8 to ns-3.9
 * **Drop trace logged for Ipv4/6 forwarding failure:** Fixed bug 861; this will add ascii traces (drops) in Ipv4 and Ipv6 traces for forwarding failures
 * **Changed default WiFi error rate model for OFDM modulation types:** Adopted more conservative ErrorRateModel for OFDM modulation types (a/g). This will require 4 to 5 more dB of received power to get similar results as before, so users may observe a reduced WiFi range when using the defaults. See tracker issue 944 for more details.

-Changes from ns-3.7 to ns-3.8
-----------------------------
+## Changes from ns-3.7 to ns-3.8

 ### Changes to build system

@@ -1912,8 +1872,7 @@ Changes from ns-3.7 to ns-3.8

 * None for this release.

-Changes from ns-3.6 to ns-3.7
-----------------------------
+## Changes from ns-3.6 to ns-3.7

 ### Changes to build system

@@ -2047,8 +2006,7 @@ Changes from ns-3.6 to ns-3.7
 * Default TTL of IPv4 broadcast datagrams changed from 1 to 64.
 * Changed DcfManager::UpdateBackoff (): using flooring instead of rounding in calculation of remaining slots. [See bug 695.](http://www.nsnam.org/bugzilla/show_bug.cgi?id=695)

-Changes from ns-3.5 to ns-3.6
-----------------------------
+## Changes from ns-3.5 to ns-3.6

 ### Changes to build system

@@ -2138,8 +2096,7 @@ Changes from ns-3.5 to ns-3.6

  Now each NetDevice subclasses have a `TracedCallback<>` object (list of callbacks) instead of `Callback<void>` ones.

-Changes from ns-3.4 to ns-3.5
-----------------------------
+## Changes from ns-3.4 to ns-3.5

 ### Changes to build system

@@ -2397,8 +2354,7 @@ Changes from ns-3.4 to ns-3.5

 * None for this release.

-Changes from ns-3.3 to ns-3.4
-----------------------------
+## Changes from ns-3.3 to ns-3.4

 ### Changes to build system

@@ -2430,8 +2386,7 @@ Changes from ns-3.3 to ns-3.4

 * The tracing system rework has introduced some significant changes in the behavior of some trace sources, specifically in the positioning of trace sources in the device code. For example, there were cases where the packet transmit trace source was hit before the packet was enqueued on the device transmit quueue. This now happens just before the packet is transmitted over the channel medium. The scope of the changes is too large to be included here. If you have concerns regarding trace semantics, please consult the net device documentation for details. As is usual, the ultimate source for documentation is the net device source code.

-Changes from ns-3.2 to ns-3.3
-----------------------------
+## Changes from ns-3.2 to ns-3.3

 ### New API

@@ -2471,8 +2426,7 @@ Changes from ns-3.2 to ns-3.3
 * 17-11-2008; changeset [756887a9bbea](http://code.nsnam.org/ns-3-dev/rev/756887a9bbea)
 * Global routing supports bridge devices.

-Changes from ns-3.1 to ns-3.2
-----------------------------
+## Changes from ns-3.1 to ns-3.2

 ### New API

--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,5 +1,4 @@
-ns-3 Release Notes
-==================
+# ns-3 Release Notes

 This file contains ns-3 release notes (most recent releases first).

@@ -13,8 +12,7 @@ a [GitLab.com issue tracker](https://gitlab.com/nsnam/ns-3-dev/-/issues) number,
 and references prefixed by '!' refer to a
 [GitLab.com merge request](https://gitlab.com/nsnam/ns-3-dev/-/merge_requests) number.

-Release 3-dev
-------------
+## Release 3-dev

 ### Supported platforms

@@ -36,8 +34,7 @@ The required Doxygen version for documentation generation is version 1.11.

 ### Bugs fixed

-Release 3.43
------------
+## Release 3.43

 This release is mainly a maintenance release and the API is generally
 consistent with the previous ns-3.42 release.  See the file CHANGES.md
@@ -117,8 +114,7 @@ per device, or a PCAP file per PHY, or a PCAP file per link. By default, a singl
 - (wifi) Fix incorrect configuration of wifi-spectrum-saturation-example.cc
 - (wifi) Fix output formatting for wifi-spectrum-per-example.cc

-Release 3.42
------------
+## Release 3.42

 In this release, we have introduced pedantic compiler warnings to enhance C++ standard conformance and improve portability.  Also, model library code in the lr-wpan and energy modules has been moved into a nested C++ namespace.

@@ -178,8 +174,7 @@ been tested on Linux. As of this release, the latest known version to work with
 - (wifi) - Fix operation in 6 GHz band (added support for FILS Discovery frames and HE 6GHz Band Capabilities information element, fixed HE Operation information element, fixed NSS selection, fixed HT and VHT not supported on 6GHz links).
 - (wifi, spectrum) - Fix negative power when channel is switched during the propagation delay period (after TX started but before the signal reached RX).

-Release 3.41
------------
+## Release 3.41

 ### Availability

@@ -232,8 +227,7 @@ Python API requires [Cppyy](https://cppyy.readthedocs.io/en/latest/installation.
 - (wifi) - ReportAmpduTxStatus called twice when sending explicit BAR upon missed BlockAck
 - (wifi) - Fix regression causing BlockAckReq frames to be sent with data rates instead of control rates

-Release 3.40
------------
+## Release 3.40

 ### Availability

@@ -281,8 +275,7 @@ Python API requires [Cppyy](https://cppyy.readthedocs.io/en/latest/installation.
 - (wifi) #942 - Trace expired MPDUs before removing them from the queue to avoid blocking the recipient buffer
 - (wifi) - Fix wrong condition preventing PHY from aborting RX when starting TX

-Release 3.39
------------
+## Release 3.39

 ### Availability

@@ -341,8 +334,7 @@ release but should also be aware of a number of issues that arose and can be fou
 - (wifi) #917 - Add missing STA-ID in GetMode() call from YansErrorRateModel
 - (wifi) - Fix wifi-rate-adaptation-distance.cc example issues with CCA threshold

-Release 3.38
------------
+## Release 3.38

 ### Availability

@@ -406,8 +398,7 @@ This release has discontinued support for g++-8 compilers.
 - (wifi) Prevent extraction of in-flight MPDUs due to lifetime expired
 - (wifi) Fixed getting the primary 80 MHz channel number in the 6 GHz band

-Release 3.37
------------
+## Release 3.37

 ### Availability

@@ -479,8 +470,7 @@ Python API requires [Cppyy](https://cppyy.readthedocs.io/en/latest/installation.
 - (wifi) Fix acknowledgment in SU format for DL MU PPDUs including PSDUs of different TIDs
 - (wifi) Fix the TID of QoS Null frames in response to BSRP TF

-Release 3.36.1
--------------
+## Release 3.36.1

 ### Availability

@@ -519,8 +509,7 @@ has not been completely tested.
 - (wifi) - Do not change protection when aggregating MSDU to DL MU PPDU
 - (wifi) - IdealWifiManager was not using the appropriate default mode

-Release 3.36
------------
+## Release 3.36

 ### Availability

@@ -609,8 +598,7 @@ This release has discontinued support for g++-7 compilers.
 - (wifi) #609 - STA checks that a Multi-STA BA is sent by the AP it is associated with
 - (lr-wpan) #742 - Add default values to non-initialized structs with primitive variables in ``LrWpanPhy``

-Release 3.35
------------
+## Release 3.35

 ### Availability

@@ -681,8 +669,7 @@ to stay compatible with the Python API scanning framework.
 - (traffic-control) !706 - Fix FqPIE qdisc not using attributes
 - (wifi) - Always track interference when not locking on PPDU

-Release 3.34
-------------
+## Release 3.34

 ### Availability

@@ -763,8 +750,7 @@ This release has been tested on the following systems:
 - (wifi) #418 - Fix HE A-MPDU Max Size Upper Bound
 - (wifi) - Compare received power per MHz to normalized RX sensitivity

-Release 3.33
------------
+## Release 3.33

 ### Availability

@@ -831,8 +817,7 @@ This release has been tested on the following systems:
 - (wifi) Report reception of BAR to WifiRemoteStationManager
 - (wifi) TXOP durations were not always being traced

-Release 3.32
------------
+## Release 3.32

 ### Availability

@@ -909,8 +894,7 @@ This release has been tested on the following systems:
 - (wifi) - Do not send VHT capabilities when operating in 2.4 GHz band
 - (wifi) #252 - Correctly handle multicast frames

-Release 3.31
------------
+## Release 3.31

 ### Availability

@@ -1013,8 +997,7 @@ issue number (prefixed by '#'), or GitLab merge request number (prefixed by '!')
 In general, known issues are tracked on the project tracker available
 at <https://gitlab.com/nsnam/ns-3-dev/issues>

-Release 3.30.1
--------------
+## Release 3.30.1

 Release 3.30.1 is a maintenance release that fixes the following issues from
 the ns-3.30 release:
@@ -1049,8 +1032,7 @@ Features are identical to release 3.30.
 - Example program tap-wifi-virtual-machine.py had a syntax error
 - Issue #80 - Indoor/outdoor status is not updated when the node moves

-Release 3.30
------------
+## Release 3.30

 ### Availability

@@ -1175,8 +1157,7 @@ Other issues fixed:
 In general, known issues are tracked on the project tracker available
 at <https://gitlab.com/nsnam/ns-3-dev/issues>

-Release 3.29
------------
+## Release 3.29

 This release is dedicated to the memory of project co-founder George Riley.

@@ -1261,8 +1242,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.28
------------
+## Release 3.28

 ### Availability

@@ -1363,8 +1343,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.27
------------
+## Release 3.27

 ### Availability

@@ -1544,8 +1523,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.26
------------
+## Release 3.26

 ### Availability

@@ -1681,8 +1659,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.25
------------
+## Release 3.25

 ### Availability

@@ -1871,8 +1848,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.24.1
--------------
+## Release 3.24.1

 Release 3.24.1 is a maintenance release that fixes three issues:

@@ -1913,8 +1889,7 @@ Features are identical to release 3.24.
 - Bug 2182 - pybindgen required version is now a string literal
 - Bug 2184 - integer overflow in MacLow

-Release 3.24
------------
+## Release 3.24

 ### Availability

@@ -1992,8 +1967,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.23
------------
+## Release 3.23

 ### Availability

@@ -2059,8 +2033,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.22
------------
+## Release 3.22

 ### Availability

@@ -2168,8 +2141,7 @@ This release has been tested on the following platforms:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.21
------------
+## Release 3.21

 ### Availability

@@ -2254,8 +2226,7 @@ This release is available from:
 in optimized mode, on a 32-bit Linux machine.  Lowering the optimization
 level to -O1 in this case can be used as a workaround.

-Release 3.20
------------
+## Release 3.20

 ### Availability

@@ -2362,8 +2333,7 @@ This release is available from:
 in optimized mode, on a 32-bit Linux machine.  Lowering the optimization
 level to -O1 in this case can be used as a workaround.

-Release 3.19
------------
+## Release 3.19

 ### Availability

@@ -2471,15 +2441,13 @@ These platforms have been tested; others may work also:
 - Bug 1816 - IPv4 fragmentation loses Packet tags
 - Bug 1877 - constructor missing for `<something>PropagationLossModels`

-Release 3.18.2
--------------
+## Release 3.18.2

 ns-allinone-3.18.2 was released to include a bake configuration file update
 for Direct Code Execution.  The ns-3 code in this release was unchanged
 from that of ns-3.18.1.

-Release 3.18.1
--------------
+## Release 3.18.1

 This release is mainly to provide updated compiler support (clang/LLVM)
 and fix the Python API scanning facility.  A few additional bug fixes
@@ -2531,8 +2499,7 @@ These platforms have been tested; others may work also:
 - Fix compilation with Clang 3.2 and newer versions, including Apple Xcode 5
 - Miscellaneous NetAnim fixes

-Release 3.18
------------
+## Release 3.18

 ### Availability

@@ -2625,8 +2592,7 @@ These platforms have been tested; others may work also:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.17
------------
+## Release 3.17

 ### Availability

@@ -2726,8 +2692,7 @@ These platforms have been tested; others may work also:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.16
------------
+## Release 3.16

 ### Availability

@@ -2798,8 +2763,7 @@ This release is available from:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.15
------------
+## Release 3.15

 ### Availability

@@ -2856,8 +2820,7 @@ This release is available from:
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.14.1
--------------
+## Release 3.14.1

 ### Availability

@@ -2870,8 +2833,7 @@ This hotfix release contains a fix for the PyViz visualizer and makes it
 easier to add PyViz support to examples; otherwise it is the same as the
 ns-3.14 release.

-Release 3.14
------------
+## Release 3.14

 ### Availability

@@ -2978,8 +2940,7 @@ available on all platforms; check the Installation page on the project wiki.
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.13
------------
+## Release 3.13

 ### Availability

@@ -3053,8 +3014,7 @@ available on all platforms; check the Installation page on the project wiki.
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.12.1
--------------
+## Release 3.12.1

 ### Availability

@@ -3066,8 +3026,7 @@ This release is available from:
 This release fixes PyViz visualizer's python bindings; otherwise, it
 is the same as the ns-3.12 release.

-Release 3.12
------------
+## Release 3.12

 ### Availability

@@ -3150,8 +3109,7 @@ available on all platforms; check the Installation page on the project wiki.
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.11
------------
+## Release 3.11

 ### Availability

@@ -3290,8 +3248,7 @@ since ns-3.10, in many cases referencing the Bugzilla bug number.
 In general, known issues are tracked on the project tracker available
 at <http://www.nsnam.org/bugzilla/>

-Release 3.10
------------
+## Release 3.10

 ### Availability

@@ -3454,8 +3411,7 @@ at <http://www.nsnam.org/bugzilla/>
 Windows XP 32 bit Cygwin 1.7.7 does not seem to work because of a
 problem (reported elsewhere) in linking large libraries.

-Release 3.9
-----------
+## Release 3.9

 ### Availability

@@ -3613,8 +3569,7 @@ since ns-3.8, in many cases referencing the Bugzilla bug number

 ### Known issues

-Release 3.8
-----------
+## Release 3.8

 ### Availability

@@ -3754,8 +3709,7 @@ ns-3 builds have been known to fail on the following platforms:
 - optimized builds on gcc 3.4.4 and 3.4.5
 - optimized builds on linux x86 gcc 4.0.x

-Release 3.7
-----------
+## Release 3.7

 ### Availability

@@ -3866,8 +3820,7 @@ ns-3 builds have been known to fail on the following platforms:
 - optimized builds on gcc 3.4.4 and 3.4.5
 - optimized builds on linux x86 gcc 4.0.x

-Release 3.6
-----------
+## Release 3.6

 ### Availability

@@ -3943,8 +3896,7 @@ ns-3.6 build is known to fail on the following platforms:
 - optimized builds on gcc 3.4.4 and 3.4.5
 - optimized builds on linux x86 gcc 4.0.x

-Release 3.5
-----------
+## Release 3.5

 ### Availability

@@ -4003,8 +3955,7 @@ feature the merging of some of our projects currently in development including
 fuller IPv6 support, some smaller features such as a new Global ARP
 package, and possibly a new Testing and Validation suite.

-Release 3.4
-----------
+## Release 3.4

 ### Availability

@@ -4064,8 +4015,7 @@ fuller IPv6 support, and IPv4 and routing protocol refactoring, and some smaller
 features such as a new Global ARP package and possibly a new Testing and Validation
 suite,

-Release 3.3
-----------
+## Release 3.3

 ### Availability

@@ -4127,8 +4077,7 @@ feature the merging of some of our projects currently in development including
 fuller IPv6 support, and IPv4 and routing protocol refactoring, and some smaller
 features such as an object naming facility and a new Global ARP package.

-Release 3.2
-----------
+## Release 3.2

 ### Availability

@@ -4199,8 +4148,7 @@ Our next release, which is expected to happen in 2 to 4 months from now, will
 feature the merging of some of our projects currently in development: IPv6,
 emulation, and synchronous posix sockets.

-Release 3.1 (2008/06/30)
------------------------
+## Release 3.1 (2008/06/30)

 ### The first ns-3 stable release

@@ -4257,8 +4205,7 @@ feature the merging of some of our projects currently in development: python
 scripting, IPv6, emulation, a statistics framework and synchronous posix
 sockets.

-Release 3.0.13 (2008/06/02)
---------------------------
+## Release 3.0.13 (2008/06/02)

 - point to point links generate ppp pcap traces
 - point to point links support asymmetrical data rates.
@@ -4278,8 +4225,7 @@ The API of Simulator::StopAt (time) has also changed.  Now it is
 called Simulator::Stop (time), and takes a relative time, instead of
 absolute.

-Release 3.0.12 (2008/04/07)
---------------------------
+## Release 3.0.12 (2008/04/07)

 - Add Attribute support to the TypeId metadata system and add
  attribute support to all in-tree models
@@ -4292,8 +4238,7 @@ Release 3.0.12 (2008/04/07)
 - regression test framework added
 - TCP delayed acknowledgements and multitasking server

-Release 3.0.11 (2008/02/15)
---------------------------
+## Release 3.0.11 (2008/02/15)

 - Initial port of GTNetS TCP implementation (initial version
  that does not support multitasking or delayed acknowledgments yet,
@@ -4303,15 +4248,13 @@ Release 3.0.11 (2008/02/15)
 - lots of bug fixes throughout the system
 - tutorial updates

-Release 3.0.10 (2008/01/15)
---------------------------
+## Release 3.0.10 (2008/01/15)

 - Add tutorial document content;
 - Valgrind option for "waf" tool;
 - Doxygen organization changes.

-Release 3.0.9 (2007/12/15)
--------------------------
+## Release 3.0.9 (2007/12/15)

 - A 802.11 model ported from Yans. This model supports:
  - a rather extensive PHY model
@@ -4325,30 +4268,26 @@ Release 3.0.9 (2007/12/15)
 - Tracing support for Applications
 - many bugs fixed

-Release 3.0.8 (2007/11/15)
--------------------------
+## Release 3.0.8 (2007/11/15)

 - A simple error model
 - Source files for ns-3 tutorial

-Release 3.0.7 (2007/10/15)
--------------------------
+## Release 3.0.7 (2007/10/15)

 - OLSR routing protocol
 - A timer class
 - Additional mobility models (random waypoint, random 2D walk)
 - A mobility visualization tool

-Release 3.0.6 (2007/09/15)
--------------------------
+## Release 3.0.6 (2007/09/15)

 - Static multicast IPv4 routing
 - Logging overhaul (NS_LOG macros)
 - Refactoring of tracing subsystem
 - Tutorial document started

-Release 3.0.5 (2007/08/15)
--------------------------
+## Release 3.0.5 (2007/08/15)

 - Refactoring to support win32-based unix environments (Cygwin, mingw)
 - "Packet socket" for allowing applications to access NetDevices directly
@@ -4358,16 +4297,14 @@ Release 3.0.5 (2007/08/15)
 - Add mobility framework and basic mobility models
 - Global unicast centralized routing

-Release 3.0.4 (2007/07/15)
--------------------------
+## Release 3.0.4 (2007/07/15)

 - Enable waf as the default build system.
 - Per-packet metadata:  a system to track which headers and trailers
  are added to a packet
 - Simplifications to point-to-point devices and channel

-Release 3.0.3 (2007/06/15)
--------------------------
+## Release 3.0.3 (2007/06/15)

 - Enable Waf for release tarballs: users can now build ns-3
  with the "waf" tool. See doc/build-waf.txt.
@@ -4379,8 +4316,7 @@ Release 3.0.3 (2007/06/15)
  manager
 - Many small API cleanups

-Release 3.0.2 (2007/05/18)
--------------------------
+## Release 3.0.2 (2007/05/18)

 - Implement a new memory management infrastructure based
  on reference counting and smart pointers (the latter being
@@ -4389,8 +4325,7 @@ Release 3.0.2 (2007/05/18)
  to provide object extensibility
 - Add support for a BSD-style socket API for user applications

-Release 3.0.1 (2007/03/31)
--------------------------
+## Release 3.0.1 (2007/03/31)

 - First public release; not yet pre-alpha.
 - Simple UDP-based simulation script (examples/simple-p2p.cc)