[Xorp-hackers] Questions on next release, puzzles and mysteries

[Pavlin Radoslavov]

> First off, any idea when the next release is likely to
> be? The roadmap (as all roadmaps are wont to be) is
> off, but would I be right in assuming it'll be
> reasonably soon?

Hopefully very soon there will be a release candidate.
Typically, two weeks after the release candidate is the release
itself.

> Second, the more I look at network routing protocols,
> the more protocols I find. It would be handy if there
> was a page listing existant protocols, their
> real-world scope, and their priority for being
> implemented (NIN being for protocols that won't be
> implemented in this lifetime, even if threatened with
> a Tandy TRS-80.)

This is outside the scope of XORP. Implementing even a single
protocol is very time consuming so for the time being we have our
hands tied with the must-have protocols like OSPF, etc.

> Finally, there is MIT's Click project, which (I seem
> to remember) can interact with Xorp. Neither site
> seems to list how such interactions occur or, indeed,
> why. (I really like to know what I'm doing! :) More
> documentation on what Xorp can interoperate with would
> be wonderful.

>From XORP's perspective, Click can be used as a very powerful
forwarding plane (though, you can use Click for more than this).

The FEA knows how to interact with Click so you could enable the Click
forwarding path and the rest of XORP will continue to work as-is.
The xorp/rtrmgr/config.boot.sample file contains the Click-related
configuration statements that can be used to enable Click.
If you are familiar with Click, there is not much more you need to
know from XORP perspective.
Unfortunately, the XORP documentation doesn't describe the
Click-related configuration, but it should be included in the 1.2
release.
If you have any specific questions feel free to ask them now.
Those questions can be helpful when it comes to writing the
documentation itself :)

Pavlin