[riot-devel] Routing table implementation

Emmanuel Baccelli Emmanuel.Baccelli at inria.fr
Mon Jan 27 09:36:29 CET 2014

Lots of good points in this thread indeed.

We do need a distinction between routing protocols and the forwarding table
(actually I prefer this terminology rather than the term "routing table"
which is sometimes confusing for exactly that reason).

I am also of the opinion that

1. routing protocols *must* feed an external forwarding table that is
unique for the whole system, which provides a nice consistent API,

2. routing protocols *may* keep their own routing information base (i.e.
whatever data from which they derive appropriate forwarding table entries).



On Mon, Jan 27, 2014 at 6:19 AM, Ludwig Ortmann <ludwig.ortmann at fu-berlin.de
> wrote:

> Hi,
> this thread might be an interesting starting point for people looking into
> the implementation of a global routing table for riot. It's only just begun:
> http://mailman.isi.edu/pipermail/ns-developers/2014-January/011709.html
> Cheers, Ludwig
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20140127/3d4de324/attachment.html>

More information about the devel mailing list