[Interop-dev] Topology JSON

[Nemesis]

On 02/05/2015 08:39 AM, Henning Rogge wrote:
> On Wed, Feb 4, 2015 at 9:48 PM, Nemesis <(spam-protected)> wrote:
>> > [MEGACUT]
>> >
>> > Sorry friends, I'm getting confused.
>> >
>> > Let's go back on the goal. What do we want from NetworkTopology JSON and
>> > NetworkRoutes JSON?
> I think NetworkRoutes is the representation of the routing table
> created by a routing agent. Doesn't matter how it was calculated, just
> a bunch of destinations, next-hops, interfaces and "costs" to give you
> an idea how far the destination is away compared to other routes.
>
> NetworkTopology is the knowledge of the links in the whole mesh...
> maybe we should split this into two "subgroups".
>
> The "neighborhood" should contain knowledge about other routers you
> can directly communicate to (and maybe data you directly got from them
> for two-hop knowledge?). This is something the local router collected
> itself and has a very accurate knowledge about. I think both
> distance-vector and linkstate protocols collect this information.
>
> The "topology" is knowledge about the whole network graph, most likely
> based on information you got from other routers. Linkstate protocols
> need this data to do their job, distance-vector protocols don't (but
> might deliver it through some optional query mechanism).

Do you think something like this would suffice?

http://pad.eigenlab.org/p/netjson-topology

Or do you think something is missing?

Federico