1. Internet Management Status Jeff Case Founder and CTO SNMP Research, Inc. +1 865 573 1434 case@snmp.com

2. 2 Status:

3. 3 Vendor View:  Vendors by default are not motivated to comply with standards by default Implementing standard MIB objects more difficult than implementing proprietary CLI Cost higher Proprietary CLIs lock in customers whereas standards free customers Benefit lower Cost/Benefit ratio not in favor of standards, unless …  Vendors will invest in implementing standards completely and correctly if and only if the market requires it, i.e., customers demand it

4. 4 Victim (Customer) View:  Customers are best served when their management tool sets are open multi-vendor / multi-platform multi-dimensional (fault, configuration, accounting, …) multi-layer (network, system, application, service, …) integrated secure extensible scalable … etc …  That is, standards-based  Proprietary CLI over SSH/Telnet doesn’t cut it

5. 5 Standards View  Need standard protocols and standards for management information, such as SNMP and standard MIB definitions  Standard MIB definitions for configuration management delayed by lack of prerequisite security  Security now available, now need to develop standard MIB definitions for configuration mgmt  Vendors aren’t completely and correctly implementing and users aren’t deploying the standards they have now, so what’s the point in making more?  Cynic: we should standardize CLI commands?