[Interop-dev] edge/endpoint/route weight/cost

[Nemesis]

Hi henning,

On 06/03/2015 01:31 PM, Henning Rogge wrote:
> Hi,
>
> another point came up during implementation.
>
> Olsrv2 use asymmetric link costs, which means it makes a difference to
> ask for incoming or outgoing cost.

Is this a novel feature?

I suppose normally cost means the cost to send a packet to a
destination, right?

> maybe we could rename the cost/weight keys so they make sure they mean
> the outgoing cost? Incoming cost could be put into the properties
> fields..

If it's a new feature and not many protocols have it, yes we should use
the properties object.

We can standardize it in the future if we feel the need.

What do you think?

Federico