[Ns-developers] NS3: Integrating routing protocols into ns-3
Mathieu Lacage
Mathieu.Lacage at sophia.inria.fr
Wed Jun 20 09:04:01 PDT 2007
a few comments below,
On Tue, 2007-06-19 at 19:28 +0100, Gustavo Carneiro wrote:
> My current concerns are:
> 1. Shouldn't the Add*Route methods return the route index, so that later
> I can retrieve it again with GetRoute?
>
> 2. Related tot the above question, why not instead of returning an
> 'index' return a unique numeric identifier? My concern here is that a route
> index is not stable, and becomes invalid as soon as routes are reordered,
> removed, or inserted.
That is the reason why the index is not returned from Add methods in 1)
> It would be nice to enhance the ns-3 routing table so that i won't need a
> duplicate olsr table. This is why I think it makes sense:
> a) lookup-by-address is a simple algorithm that is unlikely to change
> regardless of routing protocol, so it might as well be exposed as a public
> method;
> b) the olsr 'distance' field is equivalent to the 'metric' of e.g. a
> Linux routing table:
Maybe the "metric" is generic enough to be moved to the ip stack
forwarding table but, generally, I think that protocol-specific routing
table information should be kept separate from the ip stack forwarding
table.
Mathieu
More information about the Ns-developers
mailing list