Re: Incomplete XML Draft

[RJ Atkinson <rja@extremenetworks.com>]

On Tuesday, June 25, 2002, at 03:15 , Chen, Weijing wrote:
>  Yes, SNMP is good for monitoring (Simple Network Monitoring
> Protocol). But as a service provider, we have more work than simply
> monitoring the network. We have installation, configuration, service
> provisioning, service activation, fault monitoring, fault analysis,
> performance data collection, SLA threshold monitoring, trend analysis,
> traffic engineering, traffic forecasting, etc. No new equipment or new
> service can be rollout or deployed until there is complete management 
> and
> operation solution in place. We all want a quick solution, but we also 
> want
> an extensible if not complete solution initially.
I really seriously believe that there will be multiple protocols that
every service provider will have to deal with -- never a single solution.

The current XML effort *might* be useful for your configuration and 
service
provisioning and (if different) service activation tasks -- if it has any
success at all.

For fault monitoring, performance data collection, SLA threshold 
monitoring,
and such the data collection answer is likely to remain SNMP.

I don't understand what you mean by "installation" and how that is 
different
than "configuration".

Fault analysis is probably an expert system using data collected via 
SNMP.
Same for trend analysis and traffic forecasting.

Traffic engineering looks a lot like routing protocol territory to me.
(e.g. OSPF-TE, ISIS-TE, maybe MPLS).

I don't think XML will ever solve all the problems you listed for any 
operator.
Terribly sorry, but I just don't think other tools like SNMP and routing
protocols will ever go away in those areas.  Maybe I'm just confused.

Cheers,

Ran
rja@extremenetworks.com


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