[Battlemesh] JSON data interchange format for networks

[Dave Taht]

On Thu, Jan 15, 2015 at 7:07 AM, 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);
>
>  - there should be optional fields "rtt" and "channel".
>
> For an example of the cool things that can be done with the additional
> fields, please see
>
>    http://babelweb.wifi.pps.univ-paris-diderot.fr:8080

There is a feature I would dearly like in that, which would be a way
to associate persistent names with the ids in that table.

>
> -- Juliusz
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks