[Interop-dev] NetJSON: clarify what an ID is

[Henning Rogge]

On Thu, Aug 13, 2015 at 12:36 PM, Jernej Kos <(spam-protected)> wrote:
> Hello!
>
> On 13. 08. 2015 11:39, Juliusz Chroboczek wrote:
>> I'll repeat this, because it's important.  If a Babel node sees two
>> neighbouring interfaces A and B, it cannot tell if A and B belong to the
>> same node or not.
>
> Indeed, there is no information in the protocol messages that could be
> used to determine this. It would require having the Router ID in there.
> So what Juliusz is saying is that the Babel daemon just can't provide
> this information that you would like to have. It can only determine the
> local interface and the peer link-local address of a link.

Maybe we can use this proposal that I also need for olsrd2?
https://github.com/interop-dev/netjson/issues/10

the idea about endpoints is that they connect a known node (known by
router_id) with a prefix which also might have a router_id but we do
not know.

Maybe "endpoint" is the wrong name, but I think the concept fits.

I need them for olsrd2 because if a neighbor has more than one
routable interface address, these addresses appear in their neighbors
TCs without any chance to see to which node they belong. You just have
link_costs and the prefix.

Henning