⇤ ← Revision 1 as of 2012-03-13 06:33:36
Size: 197
Comment:
|
Size: 1086
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
* multi-interface nodes - Shall the whole mesh know about all interfaces and if so in what manner ? * multi-link optimization strategies - What's the best way to squeeze out more performance ? |
= Topics for Battletable = * multi-interface nodes - Shall the whole mesh know about all interfaces and if so in what manner? * multi-link optimization strategies - What's the best way to squeeze out more performance? * Multipath load balancing? * Channel interface mitigation? * How is multicast/broadcast done in the mesh based on the routing protocol? * Zeroconf/Bonjour support? * Support for multiple gateways? * Support for different kinds (and prioritizations) of gateways. * Has routing protocols some way to peer with other networks? Routing protocol interoperability? Peer over multiple wireless links? * Support for data/packet prioritization (QoS)? * IP conflict detection, mitigation? * Support for client roaming? * Node mobility. * Topology of the whole mesh at some moment is accessible? * Which data structures are used internally? Complexity? * Extensibility of protocols. * Routing cycles. * How routing protocol survives the reboot? Does it need flash/persistent storage? * Link measurements - only packet loss, other metrics? |
Topics for Battletable
- multi-interface nodes - Shall the whole mesh know about all interfaces and if so in what manner?
- multi-link optimization strategies - What's the best way to squeeze out more performance?
- Multipath load balancing?
- Channel interface mitigation?
- How is multicast/broadcast done in the mesh based on the routing protocol?
- Zeroconf/Bonjour support?
- Support for multiple gateways?
- Support for different kinds (and prioritizations) of gateways. * Has routing protocols some way to peer with other networks? Routing protocol interoperability? Peer over multiple wireless links?
- Support for data/packet prioritization (QoS)?
- IP conflict detection, mitigation?
- Support for client roaming?
- Node mobility.
- Topology of the whole mesh at some moment is accessible?
- Which data structures are used internally? Complexity?
- Extensibility of protocols.
- Routing cycles.
- How routing protocol survives the reboot? Does it need flash/persistent storage?
- Link measurements - only packet loss, other metrics?