[quagga-dev 4147] Re: example libzebra zclient utility

Paul Jakma paul at clubi.ie
Wed May 17 05:55:18 BST 2006


On Mon, 15 May 2006, Alexander Gall wrote:

> How about netconf
> <http://www.ietf.org/html.charters/netconf-charter.html>? The protocol
> is basically finished (most drafts are in the RFC editors queue).
> This is supposed to be the future standard for this type of thing.
> It's basically RPC on top of XML.

Interesting. Thanks.

Another factor in this will be emerging "network auto-magic" 
configuration stuff[3] driven by a combination of "distributions"[1] 
and desktop environments[2].

That mightn't sound in any relevant to Quagga, however it will be in 
the sense that these config-systems likely will become configuration 
mechanisms for non-desktop systems too.

It would be nice to figure out what is needed to allow such 
mechanisms to co-exist peacefully with Quagga, at least. Ideally, 
figure out what is lacking in 'zebra' that would lead to those 
external projects re-implementing functionality in Quagga.

(E.g. it's becoming clear, at least from discussion on the 
OpenSolaris NWAM list, that they need a "RIB" to manage/pick 
different kinds of routes, like DHCP-learnt, user-specified statics, 
etc. Without engagement, that kind of thing could be annoying to run 
in combination with Quagga's RIB (in zebra)).

The point being: A factor in choosing this protocol is picking the 
one that would be the most attractive to external (possibly 
desktop-environment centric) 'network configuration' projects :).

regards,

--paulj

1. Used in the sense of "distinct Unix core systems" generally, e.g.
    Fedora, Debian, OpenSolaris

2. e.g. GNOME

3. E.g. the 'NWAM' community on opensolaris.org for one example,
    GNOME's "NetworkManager", HAL, etc.

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
DPRINTK("strange things happen ...\n");
         linux-2.6.6/drivers/atm/eni.c



More information about the Quagga-dev mailing list