Re: How does XML help Network Operators

[Ted Goddard <ted.goddard@windriver.com>]

Hi All,

I wanted to ask a few questions and make a few comments on
draft-lear-config-issues-00.txt.

I found the discussion on device-initiated and management-initiated 
modes
useful, and it was interesting to see which modes are popular with which
audiences. Part of the solution (for the cases that have a solution) 
would seem
to be a simple activation message combined with a protocol that would 
function
properly when initiated by either end.

It's important to accept that multiple sets of schemas will exist, and 
this is
probably the only feasible way to introduce a new management protocol
given so many devices already being managed by existing protocols.  
Devices
exist with data models from proprietary data structures, MIBs, and CIM
schemas.  There's no reason why a variety of data models can't all be
represented in XML, perhaps applied with a common set of operations, and
served over a variety of transports.  We need only standardize adjacent 
layers
in the stack.

What are the issues around efficiently representing alarms in XML?  Is
it inefficient to use SOAP over HTTP to deliver alarms?

Given all the effort going into SOAP it's hard to imagine not finding a 
large
audience for a SOAP-based management protocol.  It also seems natural to
define SOAP over BEEP, even if this does not find application in device
management.

Regards,
Ted.



On Wednesday, September 25, 2002, at 04:43 PM, Eliot Lear wrote:

> Bert,
>
> Along the lines of wanting things written down, I've done a little 
> writing of my own, with a WHOLE lot of input from many different 
> sources.  The following is provided merely for discussion purposes, 
> based on our world tours together and other customer interactions.  I 
> hope you find it useful.  This is a draft -00.  Your comments and 
> suggestions are welcome.  I have donned my flame retardant glasses and 
> gloves ;-)
>
> Eliot

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