[Battlemesh] JSON data interchange format for networks

Juliusz Chroboczek jch at pps.univ-paris-diderot.fr
Fri Jan 16 15:15:28 UTC 2015


>> - there should be optional fields "neighbur_metric" and "neighbour_cost";
>> normally, metric = neighbour_metric + neighbour_cost, but that's not
>> necessarily the case if using a non-additive metric (such as Babel's Z3
>> metric);
>
> You mean costs both for links and for nodes?

I think so, although I'm not sure we're using the same terminology.

>> - there should be optional fields "rtt" and "channel".
>
> isn't "channel" redundant? you know the interface/device, so you can
> look this up in the other structure.

Uh-huh.  But the channel should be somewhere -- the monitoring interface
is not necessarily running on the node itself, so the JSON should be
self-contained.

-- Juliusz


More information about the Battlemesh mailing list