[Battlemesh] JSON data interchange format for networks

[Simon Wunderlich]

Hey Federico,

On Saturday 10 January 2015 13:49:43 Nemesis wrote:
> Hi everybody,
> 
> in the past 2months some people have been working on a simple idea,
> which would bring a lot of benefits to many peopleand that for some
> strange reason has not been implemented yet, probably because the effort
> is more "human" than technical, as many different people have to work
> together and come to agreements.
> 
> But here's the idea:
> 
> Immagine you could export adevice configuration in JSON format and
> reimport that somewhere else,like monitoring software, node database, or
> whatever you need.
> Something like this:
> https://github.com/interop-dev/json-for-networks/blob/master/examples/device
> -configuration.json
> 
> Immagine you could extract monitoring data with a simple JSONthat has a
> similar structure to the device configuration, that would enable
> different software to play well with one another, instead of building
> silos that don't talk to each other.
> Something like this:
> https://github.com/interop-dev/json-for-networks/blob/master/examples/monito
> ring-data.json
> 
> Immagine the olsr json info plugin, or the json output by batman, but
> instead of being all different,they shared a common structure, and
> differed only in the key/value pairs that are specific to their protocol.
> That would be easier to parse for who develops software to represent
> those topologies visually.
> Something like this:
> https://github.com/interop-dev/json-for-networks/blob/master/examples/networ
> k-routes.json
> 

It may be interesting to track neighbors per interface for multi-radio nodes 
as well, and track primary/secondary interfaces - at least this is what 
alfred/vis in batman-adv can do (check the illustrations):

http://www.open-mesh.org/projects/open-mesh/wiki/Alfred#batadv-vis

In general it sounds like a good idea to have a single format to feed different 
drawing applications, although I'm not enough involved in these kind of things 
to judge the usefulness. :) For alfred-vis we have two formats, one is the 
classic graphviz-compatible output which is similar to the old OLSR output, 
and another JSON output.

Cheers,
    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20150113/ea58c8f9/attachment.pgp>