[Interop-dev] JSON for Networks feedback

[Nemesis]

On 01/17/2015 02:24 PM, Henning Rogge wrote:
> On Sun, Jan 11, 2015 at 7:52 PM, Nemesis <(spam-protected)> wrote:
>> > Hi Thijs,
>> >
>> > On 01/11/2015 06:57 PM, Thijs van Veen wrote:
>> > ...
>>> >> 1) In the Route object, you suggest a Device field to reference the
>>> >> actual interface you're targeting.
>>> >> I suggest changing the name Device to Destination Interface or something
>>> >> similar to differentiate in terminology between devices (nodes) and
>>> >> their interfaces.
> Incoming/Outgoing interface maybe?
>
> Source/Destination sounds more like end-to-end information.
>
>>> >> 2.) You suggest a Source field for source-specific routing.
>>> >> I suggest adding a Source Interface field, this way (it seems to me) you
>>> >> can more easily handle multi-interface devices.
> We could add it as an optional field, not sure if the Linux kernel
> supports it at the moment.
>
> But it could be simulated by multiple routing tables...
>
> Yes, I think we should do this.

Henning, thank you for your help in this, especially in ther routing part.

I must find the time to collect all the feedback we got recently from
different sourcesso we candecide how to proceed.

Peraphs I could write it on a etherpador something similar.

The step after this one will be to start implementing itand get feedback
from real world scenarios.

Federico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150120/9a6b74fc/attachment.html>