Bug 1984

Summary: expose additional internet random variables to configuration system
Product: ns-3 Reporter: Tom Henderson <tomh>
Component: internetAssignee: Tom Henderson <tomh>
Status: CONFIRMED ---    
Severity: normal CC: ns-bugs
Priority: P5    
Version: pre-release   
Hardware: PC   
OS: Linux   

Description Tom Henderson 2014-09-11 14:18:12 UTC 
classes Ipv6Extension and Ipv4GlobalRouting use random variables that are not exposed to the config store system.

The ArpL3Protocol attribute is an example of how to do this:

    .AddAttribute ("RequestJitter", "The jitter in ms a node is allowed to wait before sending an ARP request. Some jitter aims to prevent collisions. By default, the model will wait for a duration in ms defined by a uniform random-variable between 0 and RequestJitter",
                   StringValue ("ns3::UniformRandomVariable[Min=0.0|Max=10.0]"),
                   MakePointerAccessor (&ArpL3Protocol::m_requestJitter),
                   MakePointerChecker<RandomVariableStream> ())

In addition, it would be useful to document the usage of randomness in the internet stack, in the Internet documentation (rst and documentation)... this is a cross-cutting issue (would be nice for all modules).

This bug is filed as a reminder to revisit this.