[Interop-dev] OLSRd2 JSON APIs

[Baptiste Jonglez]

On Mon, Nov 10, 2014 at 07:48:20PM +0100, Henning Rogge wrote:
> On Mon, Nov 10, 2014 at 5:54 PM, Nemesis <(spam-protected)> wrote:
> > Thanks for this useful information.
> >
> > We should encourage more routing protocol devs to come here and share
> > news about what they are doing, especially JSON structures as we need
> > these structures in our libraries and web-apps to build useful features.
> >
> > And I think it would be awsome if we could define another simple JSON
> > structure with the lowest common denominator of a network topology.
> 
> I think the lowest common denominator would be a list of supplied
> routing entries together with some dimensionless "cost" value. And a
> list of known links/neighbors with their attached cost value.

Note that the notion of "neighbour" may vary with the routing protocol.

For instance, in Babel, a neighbour is a tuple "(link-local IPv6 address,
interface)".

Additionally, each router has a unique Router-ID, which identifies routes
originated by this router.  But if you have multiple interfaces, you may
well have multiple neighbourhood relations with the exact same router.

How is a neighbour defined in OLSR?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20141111/96d0eaab/attachment.sig>