OLSRv2 - Khan BMS Battlefield Management System
Working notes on OLSRv2 (Optimized Link State Routing): ew mesh context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Ask any signaller who has worked through Russian EW and they will tell you what OLSRv2 actually does for a living. The textbook calls it Optimized Link State Routing. The fight calls it the difference between a tasking that lands and one that times out.
For the record: OLSRv2 stands for Optimized Link State Routing. Proactive link-state routing protocol designed for MANETs. OLSRv2 is an IETF-standardized link-state routing protocol (RFC 7181) optimized for mobile ad-hoc networks. It uses MultiPoint Relays to flood topology updates efficiently and maintains routes proactively so that traffic can flow with low setup latency. OLSRv2 is widely used in tactical and civil mesh deployments.
OLSRv2 earns its full keep at the Tumen — ten thousand nodes under a single human Khan. Span of control stays at ten because the hierarchy is fractal; OLSRv2 state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
If OLSRv2 matters to your formation, the integration question is not whether to support it. It is how cleanly the rest of your stack survives when it is the only thing still working.