[Battlemesh] JSON data interchange format for networks

Henning Rogge hrogge at gmail.com
Fri Jan 16 09:10:50 CET 2015


On Thu, Jan 15, 2015 at 4:07 PM, Juliusz Chroboczek
<jch at pps.univ-paris-diderot.fr> wrote:
>> https://github.com/interop-dev/json-for-networks
>
> A few comments, from a Babel perspective:
>
>  - the name of the metric is "routing_metric" and "metric", depending on
>    the object; it should be "metric_type" in both cases;
>
>  - the value of the metric is "cost", it should be "metric";
>
>  - 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?

>  - 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.

Channel doesn't change that often... ;)

Henning Rogge



More information about the Battlemesh mailing list