When control messages are passed via
send{Up,Down}stream{Packet,Control}, the emulator takes ownership of the
control message. Control messages are destroyed after the processing
thread associated with the receiving NEM layer completes its respective
callback: process{Up,Down}stream{Packet,Control}
This question will reveal that I am uncertain about the allocations and
deallocation of both packets and control messaging within the EMANE stack, in
terms of allocation and deallocation endpoints and conventions.
For the EMANE TimingAnalysis shim layer, when handling upstream and downstream
p