[Interop-dev] Next issue: endpoints

[Nemesis]

I hope there will be a chance to have a constructive discussion at the
battlemesh about the remaining open issues and hopefully open a few more
ones to do even more cleanup.

Federico


On 07/06/2015 07:08 PM, Henning Rogge wrote:
> Please don't forget that "endpoints" still have a link-cost in olsrd2...
>
> about the name...
>
> olsrd2 calles them "attached networks", olsrd1 calls them HNA (which
> don't have a link-cost).
>
> Not sure if this helps.
>
> Henning
>
> On Mon, Jul 6, 2015 at 6:57 PM, Nemesis <(spam-protected)> wrote:
>> The next issue I'd like to work on is "endpoints in NetworkGraph"
>> https://github.com/interop-dev/netjson/issues/10
>>
>> I'd like to do a couple of things:
>>
>> improve the description of the issue, including a full example
>> propose a definition
>> request feedback from other parties
>>
>> If I understand correctly, "endpoints" would be another list like "links",
>> but indicating links between nodes and external networks.
>>
>> I think the example was something like this:
>>
>> "endpoints": [
>>     {
>>         "source": "192.168.0.1",
>>         "target": "150.1.1.0/24"
>>     }
>> ]
>>
>> Or in case we wanted to use "prefix" (not very convincing):
>>
>> "endpoints": [
>>     {
>>         "source": "192.168.0.1",
>>         "prefix": "150.1.1.0/24"
>>     }
>> ]
>>
>> I am also not very convinced of the name "endpoints". Is there any other
>> self evident keyword that comes into our mind?
>>
>> Federico
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>