<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Helvetica, Arial, sans-serif">Hi everybody,<br>
<br>
<font face="Helvetica, Arial, sans-serif">in the past 2<font
face="Helvetica, Arial, sans-serif"> months <font
face="Helvetica, Arial, sans-serif">some people have been
working on a simple idea, which would bring <font
face="Helvetica, Arial, sans-serif">a lot of <font
face="Helvetica, Arial, sans-serif">benefits to many
people<font face="Helvetica, Arial, sans-serif"> and</font></font></font>
that <font face="Helvetica, Arial, sans-serif">for <font
face="Helvetica, Arial, sans-serif">some strange <font
face="Helvetica, Arial, sans-serif">reason has not
been implemented yet</font></font></font></font></font>,
probably because the effort is more "human" than technical, as
many different people have to <font face="Helvetica, Arial,
sans-serif">work together and come to agreements.<br>
<br>
<font face="Helvetica, Arial, sans-serif">But here's the ide<font
face="Helvetica, Arial, sans-serif">a:<br>
<br>
<font face="Helvetica, Arial, sans-serif">Immagine you co<font
face="Helvetica, Arial, sans-serif">uld export a<font
face="Helvetica, Arial, sans-serif"> device
configuration in JSON format <font face="Helvetica,
Arial, sans-serif">a<font face="Helvetica, Arial,
sans-serif">nd reimport that somewhere <font
face="Helvetica, Arial, sans-serif">else,<font
face="Helvetica, Arial, sans-serif"> like <font
face="Helvetica, Arial, sans-serif">monitoring
software, node database, or whatever you
need<font face="Helvetica, Arial,
sans-serif">.</font></font></font></font></font></font></font></font></font><br>
<font face="Helvetica, Arial, sans-serif">Something like
this: </font></font></font></font></font></font><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><a class="moz-txt-link-freetext" href="https://github.com/interop-dev/json-for-networks/blob/master/examples/device-configuration.json">https://github.com/interop-dev/json-for-networks/blob/master/examples/device-configuration.json</a></font><br>
<br>
</font></font></font></font></font><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font face="Helvetica,
Arial, sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif">Immagine you
could extract monitoring
data <font
face="Helvetica,
Arial, sans-serif">with
a simple JSON<font
face="Helvetica,
Arial, sans-serif">
that has a similar
structure to the de<font
face="Helvetica,
Arial, sans-serif">vice
configuration<font
face="Helvetica,
Arial,
sans-serif">,
that would
enable different
software to play
well</font> with
one another,
instead of
building silos
that don't talk to
each other.<br>
<font
face="Helvetica,
Arial,
sans-serif">Something
like this: </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font face="Helvetica,
Arial, sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica, Arial,
sans-serif"><font
face="Helvetica,
Arial, sans-serif"><font
face="Helvetica,
Arial, sans-serif"><font
face="Helvetica,
Arial, sans-serif"><font
face="Helvetica,
Arial,
sans-serif"><a class="moz-txt-link-freetext" href="https://github.com/interop-dev/json-for-networks/blob/master/examples/monitoring-data.json">https://github.com/interop-dev/json-for-networks/blob/master/examples/monitoring-data.json</a></font><br>
<br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><font
face="Helvetica, Arial, sans-serif">Immagine the olsr
json info plugin, or the json out<font face="Helvetica,
Arial, sans-serif">put by batman, <font
face="Helvetica, Arial, sans-serif">but instead of
being all different,<font face="Helvetica, Arial,
sans-serif"> they s<font face="Helvetica, Arial,
sans-serif">hared a common structure, and
differed only in the <font face="Helvetica,
Arial, sans-serif">key<font face="Helvetica,
Arial, sans-serif">/value pairs that are
specific to their protocol.<br>
<font face="Helvetica, Arial, sans-serif">T<font
face="Helvetica, Arial, sans-serif">hat
would be easier to parse for who d<font
face="Helvetica, Arial, sans-serif">evelops
software to r<font face="Helvetica,
Arial, sans-serif">epresent those
topologies visually.<br>
<font face="Helvetica, Arial,
sans-serif">Something like this: </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial,
sans-serif"><a class="moz-txt-link-freetext" href="https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json">https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json</a></font><br>
<br>
Now, this <font face="Helvetica,
Arial, sans-serif">is not some
weird utopic idea. <font
face="Helvetica, Arial,
sans-serif">A similar thing has
been done in the GIS field<font
face="Helvetica, Arial,
sans-serif">: <b>GeoJSON</b><font
face="Helvetica, Arial,
sans-serif">.<br>
<font face="Helvetica,
Arial, sans-serif">You can
pass <font
face="Helvetica, Arial,
sans-serif">G<font
face="Helvetica,
Arial, sans-serif">eoJSO<font
face="Helvetica,
Arial, sans-serif">N
to any GIS library<font
face="Helvetica,
Arial, sans-serif">,
written <font
face="Helvetica,
Arial,
sans-serif">in
any language,
and it will
understand what
is that you are
passing. You can
visualize that
GeoJSON on a map
with leaflet or
openlay<font
face="Helvetica,
Arial,
sans-serif">ers</font>,
you can use<font
face="Helvetica,
Arial,
sans-serif">
it to
calculate
distances and
stuff on the
server side,
you can output
on an HTTP API</font></font></font></font></font></font></font>,
or <font face="Helvetica,
Arial, sans-serif">whatever.<br>
<br>
<font face="Helvetica,
Arial, sans-serif">Here
<font face="Helvetica,
Arial, sans-serif">there's
a very <font
face="Helvetica,
Arial, sans-serif">early
draft of the spec:</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><br>
<a class="moz-txt-link-freetext" href="https://github.com/interop-dev/json-for-networks">https://github.com/interop-dev/json-for-networks</a><br>
<br>
Before we start implementing it in softwares like node databases,
monitoring systems and firmwares, we would love to have some
feedback from the battlemesh community, especially the routing
protocol developers.<br>
<br>
We would like to know if anyone else has been working on a similar
idea and we would like to have constructive critical feedback and
improve our early spec before starting to prototype.<br>
<br>
If anybody will be at Fosdem we can also discuss in person there.<br>
<br>
Cheers to all and hope to see many of you at the next battlemesh in
Slovenia.<br>
<br>
Federico Capoano (aka Nemesis)<br>
Ninux.org<br>
</body>
</html>