Specification and verification of network managers for large internets

ABSTRACT

Large internet environments are increasing the difficulty of network management. Integrating increasing numbers of autonomous subnetworks (each with an increasing number of hosts) makes it more difficult to determine if the network managers of the subnetworks will interoperate correctly. We propose a high level, formal specification language, NMSL, as an aid in solving this problem. NMSL has two aspects of operation, a descriptive aspect and a prescriptive aspect. In its descriptive aspect, NMSL specifies abstractions of the network components and their instantiations, and verifies the consistency of such a specification. The abstractions include the data objects and processes in a network management system. These abstractions are instantiated on network elements. Network elements are grouped together in the specification of domains of administration. An extension mechanism is provided to allow for the specification of new management characteristics that the basic language cannot express. In its prescriptive aspect, NMSL generates configuration information directly from a consistent specification. This information is used to configure network management processes to make their operation consistent with their specifications. Standard management protocols (such as the emerging ISO or IETF standards) can be used to incorporate the configuration information into running management processes.

REFERENCES

• 1: "Network Management," IBM Systems Journal 27(1) pp. 1-85 (1988).
• 2: N. Heintze, et al, The CLP(R) Programmer's Manual, Dept. of Computer Science, Monash University, Clayton, Victoria, Australia (1987).
• 3: J.A. Barehanski, "Expert Systems for Local Computer Network Software Debugging," Proceedings of the 1987 IEEE 12th Conference on Local Computer Networks, pp. 154-159 Minneapolis, MN, (October 1987).
• 4: Daniel M. Berry, Towards a formal basis for the formal development method and the Ina Jo specification language, IEEE Transactions on Software Engineering, v.13 n.2, p.184-201, Feb. 1987 [doi>10.1109/TSE.1987.232891]
• 5: J. Case, M. Fedor, M. Schoffstall, and J. Davin, "A Simple Network Management ProtocoL" RFC 1067, iETF Network Working Group (August 1988).
• 6: L.J. Cole, "Network Management as Described in Systems Network Architecture," IEEE Infocom 86, pp. 364- 376 Miami, FL, (April 1986).
• 7: Martin S. Feather, Language support for the specification and development of composite systems, ACM Transactions on Programming Languages and Systems (TOPLAS), v.9 n.2, p.198-234, April 1987 [doi>10.1145/22719.22947]
• 8: F. Fluekiger and C. Piney, "Principles of Comrol in a Distributed Network," Networks 80, Online, pp. 159-171 London, England, (June 1980).
• 9: Information Processing Systems -Open Systems Interconnection, "LOTOS (Formal description technique based on the temporal ordering of obervational behavior)," ISO 8807, International Organization for Standardization (August 1987).
• 10: Information Processing Systems - Open Systems Interconnection, "Specification of Abstract Syntax Notation One (ASN.1)," ISO 8824, International Organization for Standardization (~mber 1987).
• 11: S.M. Klerer, "The OSI Management Architecture: an Overview," IEEE Network 2(2) pp. 20-29 (March 1988).
• 12: W. M. Loucks , W. I. Kwak , Z. G. Vranesic, Implementation of a dynamic address assignment protocol in a local area network, Computer Networks and ISDN Systems, v.11 n.2, p.133-146, Feb. 1986 [doi>10.1016/0169-7552(86)90013-9]
• 13: D, C. Luckham and F. W. Henke, "An Overview of Anna, a Specification Language for Ada," IEEE Software 2(2) pp. 99-22 (March 1985).
• 14: K. MeCloghrie and M. Rose, "Management Information Base for Network Management of TCP/IP-based Internets," RFC 1066, IETF Network Working Group (August 1988).
• 15: R. E. Moore, "Problem Detection, Isolation, and Notification in Systems Network Architecture," IEEE Infocom 86, pp. 377-381 Miami, FL, (April 1986).
• 16: Robert B. Terwilliger , Roy H. Campbell, PLEASE:Predictable Logic based ExecutAble SpeCifications, Proceedings of the 1986 ACM fourteenth annual conference on Computer science, p.349-358, February 1986, Cincinnati, Ohio, United States [doi>10.1145/324634.325453]
• 17: U. Warrier , P. Relan , O. Berry , J. Bannister, A network management language for OSI networks, Symposium proceedings on Communications architectures and protocols, p.98-105, August 16-18, 1988, Stanford, California, United States
• 18: J. Westcott, J. Buress, and V. Begg, "Automated Network Management," IEEE Infocom '85, pp. 43-50 Washington, IX:, (March 1985).
• 19: Steve Wilbur, Local area network management for distributed applications, Computer Communications, v.9 n.2, p.100-104, April 1986 [doi>10.1016/0140-3664(86)90010-1]
• 20: Jeannette M. Wing, Writing Larch interface language specifications, ACM Transactions on Programming Languages and Systems (TOPLAS), v.9 n.1, p.1-24, Jan. 1987 [doi>10.1145/9758.10500]
• 21: P. Zave, "An Operational Approach to Requirements Specification for Embedded Systems," IEEE Transactions on Software Engineering 8(3)pp. 250-269 (May 1982).

INDEX TERMS

Primary Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.1 Network Architecture and Design
          Subjects: Network communications

Additional Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.0 General
          Subjects: Open Systems Interconnection reference model (OSI)
      C.2.1 Network Architecture and Design
          Subjects: Distributed networks

  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Languages

General Terms:
Design, Languages