Re: Deja vu Again

[Randy Presuhn <rpresuhn@dorothy.bmc.com>]

Hi -

> Message-Id: <5.1.0.14.2.20020626164634.0347cb20@127.0.0.1>
> Date: Wed, 26 Jun 2002 17:04:36 -0700
> To: xmlconf@ops.ietf.org
> From: "David T. Perkins" <dperkins@dsperkins.com>
> Subject: Re: Deja vu Again
> In-Reply-To: <200206262324.QAA05251@dorothy.bmc.com>
> X-Spam-Status: No, hits=-0.8 required=5.0
> 	tests=IN_REP_TO,DOUBLE_CAPSWORD,PORN_3,RCVD_IN_MULTIHOP_DSBL,
> 	      X_RCVD_IN_UNCONFIRMED_DSBL,FUDGE_MULTIHOP_RELAY
> 	version=2.30
...
> The format of an XML "flat file" that contains configuration is
> totally different from how you get those from devices, and
> how you apply them to devices. From an earlier message:
...

This is the point.  (Actually, this is several of the points.)

  1) One of the nice things about XML is that it's fairly simple
     to transform into other representations, and that there is
     a toolset for describing these transformations.

  2) To do real configuration management, file formats (and the
     ability to "diff" them) do matter.

  3) One can use XML to describe the operation syntax, and

  4) one can also use XML to describe operand syntax, but

  5) to get to the kind of transactional stuff needed to
     support *network* configuration, one needs to look
     at things like WSDL and beyond.  (Actually, LU6.2
     would be just about right.  :-)

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>