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

[Henning Rogge]

On Sat, Nov 22, 2014 at 4:39 AM, Mitar <(spam-protected)> wrote:
> Hi!
>
> What about "weight" if people don't like metric and cost?

I would prefer both cost and metric over "weight".

> Also, should the value be normalized in some way?

unless the designers of the metric cooperate this will be a very hard
thing to do. The only thing I would like is to restrict the values to
integer values...

> What about routing protocols which use multiple metrics together? Like
> ETX + bitrate?

In the end you just have one metric...

the combination of packet loss (ETX) and bitrate is called ETT, which
gives you a similar value than the throughput of the link.

So whatever the combination of input data is, we should get a single value out.

Henning Rogge

> Mitar
>
>> On Fri, Nov 21, 2014 at 7:23 PM, Nemesis <(spam-protected)> wrote:
>>> So, if using the positive/negative flip, would this be ok:
>>>
>>> {
>>>     destination: "<id>",
>>>     next: "<id>",
>>>     source: "<id>",
>>>     device: "<device>",
>>>     metric: "<metric value>",
>>>     metric_type: "<name of algorithm>"
>>> }
>>
>> I think this is okay if we define what is the definition of "metric" somewhere.
>>
>> Henning
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>
>
> --
> http://mitar.tnode.com/
> https://twitter.com/mitar_m