> 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. [Chen, Weijing] No, we are not asking a single protocol to accomplish above tasks. What we ask is a single protocol to provide enough information from box to help our NMS system to accomplish the job. At least initially, this protocol and XML DDL should be able to carry all existing SNMP MIB and function with the improvement that Andy mentioned in his ID "draft-bierman-nm-observations-00.txt". Maybe this initial XML DDL also is able to carry proprietary configuration data around. Later on we can come back to enhance DDL/add XML MIB, etc.
<<application/ms-tnef>>