[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Incomplete XML Draft

On Tuesday, June 25, 2002, at 12:30 , Ted Goddard wrote:

Here's a possible interpretation of the phased approach:

1. SOAP/WSDL definitions supporting SNMP semantics
   (perhaps leaning more towards GetBulkRequest than GetNextRequest)

I'm not at all convinced that I want SNMP semantics in the
protocol used for configuring network equipment.


2. XML encoding of MIB modeled data to be used in 1. and other
   protocols.

Other than the DOCSIS MIBs, most MIBs are not tremendously useful
for configuring boxes (too many needed but missing objects),
IMHO.  So this doesn't help my box configuration problem much.


3. Extend the "SOAP API" from 1. to support desired semantics and
   a richer (than 2.) XML encoding; define this encoding.

Not sure that I want SOAP in the first place.  Maybe I do,
but maybe I don't.


4. Proceed with modeling work (XML schema definition?) that
   takes advantage of 3.

At least some prior work at a now defunct startup tends to indicate
that different operators have significantly different models in
their heads.  So I'm not convinced yet that there is a "one true model"
that will work for all of the operators.  Maybe there is,
but evidence for that isn't obviously in sight.

IMHO,

Ran


--
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/>