Re: Whitepaper on XML-based Network Management

[brett watson <brett@the-watsons.org>]

> Hi Phil,
> 
> I like where this is going. A few comments:
> 
> On Sat, Jul 28, 2001 at 02:57:14AM -0400, Phil Shafer wrote:
> > 3.3. Access Mechanisms
> > 
> >    The JUNOScript API needs only a connection-oriented data path, making
> >    it suitable for a number of transport protocols. An ssh, telnet, or
> >    serial console connection can easily carry a JUNOScript session. Once
> >    a connection is established, the client uses the 'junoscript' command
> >    to convert the CLI login into a JUNOScript session.  The client and
> >    server exchange the initial handshake described above, after which
> >    further communications are in JUNOScript RPCs.
> 
> - rather than "junoscript" can it be something vendor/product neutral?
> "xmlscript"?
> 
> - will the native configuration be stored in XML too? So restoring a failed
> machine can simply be copying the XML plaintext config to a new flash card and
> inserting it into a new unit?
> 
> - Ideally vendors could share a standard DTD/Schema for various subsystems of
> their products, ie. an Interfaces DTD which is a superset of IF-MIB but the
> tables are more structured. Do you have a JUNOScript DTD in mind/implemented?

i've been watching this thread and wondering when someone was going to
say "wait, i have multiple router vendors in my network" or "wait, i
have many different *types* of network elements in my network
(routers, switches, wdm systems, etc).  i guess i should have just
said it :)

i've been hoping for an xml framework along the lines of what carl
malamud and marshall rose started at www.invisibleworlds.net.   i
would like to see a generic framework that i can apply to more than
just routers.

ideally, i think we could all benefit from a vendor-neutral xml api
"thing" that we can customize within our own organizations.

-b