[Interop-dev] Network Topology JSON [was: OLSRd2 JSON APIs]

[Henning Rogge]

On Sun, Nov 23, 2014 at 5:08 PM, Nemesis <(spam-protected)> wrote:
> Thank you for the correction.
>
> Peraphs each routing protocol should choose what to put inside the "cost"
> attribute?

Of course... but we still need to define what type of things should be
in the value, otherwise you cannot use the value later to trigger
other service-decisions.

But "number (hopefully integer) with smaller means better" is good
enough for this I think.

Henning