ork Magazine, and filtering. SNMP, on the other hand, needs the name of the January. actual object instance being managed, except in the case of the Ben-Artizi, A., Chandna, A. and Warrier, U. (1990) Network man- GET-NEXT command which enables the application to re- agement of TCP/IP networks: present and future, IEEE Network trieve the next MIB object, relative to its current position. Magazine, July. 6. SNMP and CMIP both have three primitive operations, GET, Bush, Nick (1991) The importance of open standards for network SET and EVENT (or TRAP). CMIP has three further primitive- management, Telecommunications, May. S, CREATE, DELETE and ACTION, which provide it with a Caruso, R.E. (1990), Network management: a tutorial overview, powerful capability. IEEE Communications Magazine, March. 7. CMIP makes a clear distinction between objects and their Cassel, L.N., Partridge, C. and Westcott, J. (1989) Network man- attributes, an attribute being a condition or state of the device. agement architectures and protocols: problems and approaches, SNMP does not differentiate between an object and its attrib- IEEE Journal on Selected Areas in Communications, Septem- ute, and not being able to do SO means that re-use of attributes, or definitions, to represent generic information is not possible. Corsi, N. and Iorio, N. (1990) OSI structures for network manage- Therefore the management of novel objects is difficult with ment, CSELT Technical Reports, August. SNMP. In CMIP very different objects can have common Embry, J., Manson, P. and Milhan, D. (1990) An open network attributes, SO that it is not necessary to assign a unique descrip- management architecture: OSI/NM Forum architecture and tion to each object or operational state, as in SNMP. This means concepts, IEEE Network Magazine, July. that CMIP is much more extendible (future proof) since the Fleming, S. and Jakubson, J.E. (1989) Managing the multilevel boundary between the agent and an object can be designed such network, Telephony, May 1. Bibliography 16/25 Holter, R