Network Working Working Group                                 U. WarrierRequest for Comments: 1189                                       NetlabsObsoletes:  RFC 1095                                            L. Besaw                                                         Hewlett-Packard                                                              L. LaBarre                                                   The Mitre Corporation                                                          B. Handspicker                                           Digital Equipment Corporation                                                            October 1990              The Common Management Information Services                     and Protocols for the Internet                            (CMOT and CMIP)Status of this Memo   This memo defines a network management architecture that uses the   International Organization for Standardization's (ISO) Common   Management Information Services/Common Management Information   Protocol (CMIS/CMIP) in the Internet.  This RFC specifies an IAB   standards track protocol for the Internet community, and requests   discussion and suggestions for improvements.  Please refer to the   current edition of the "IAB Official Protocol Standards" for the   standardization state and status of this protocol.   Distribution of this memo is unlimited.Table of Contents   1. Overview ...................................................    2   2. Introduction ...............................................    3   3. Protocol Overview ..........................................    4   3.1. The CMOT Protocol Suite ..................................    5   3.2. The CMIP Protocol Suite ..................................    6   3.3. Conformance Requirements .................................    6   4. Common Management Information Service Element ..............    7   4.1. Association Policies .....................................    7   4.2. CMIS Services ............................................    9   4.2.1 General Agreements on Users of CMIS .....................    9   4.2.2 Specific Agreements on Users of CMIS ....................   10   4.3. CMIP Agreements ..........................................   10   5. Services Required by CMIP ..................................   10   6. Acknowledgements ...........................................   11   7. References .................................................   11   8. Security Considerations.....................................   14   9. Authors' Addresses..........................................   14Warrier, Besaw, LaBarre & Handspicker                           [Page 1]RFC 1189                     CMOT and CMIP                  October 19901.  Overview   This memo is a revision of RFC 1095 - "The Common Management   Information Services and Protocol over TCP/IP" [27].  It defines a   network management architecture that uses the International   Organization for Standardization's (ISO) Common Management   Information Services/Common Management Information Protocol   (CMIS/CMIP) in the Internet.  This architecture provides a means by   which control and monitoring information can be exchanged between a   manager and a remote network element.  In particular, this memo   defines the means for implementing the International Standard (IS)   version of CMIS/CMIP on top of both IP-based and OSI-based Internet   transport protocols for the purpose of carrying management   information defined in the Internet-standard management information   base.  Together with the relevant ISO standards and the companion   RFCs that describe the initial structure of management information   and management information base, these documents provide the basis   for a comprehensive architecture and system for managing both IP-   based and OSI-based internets, and in particular the Internet.   In creating this revision of RFC 1095, the following technical and   editorial changes were made:      1) The tutorial section on OSI Management included in RFC 1095         has been removed from this document.  After some revisions,         the tutorial material may be published as another RFC.      2) The sections in RFC 1095 which discussed the semantics of how         to interpret requests in the context of Internet MIBs has been         removed from this protocol document.  This topic is now         discussed in the OIM-MIB-II draft document.  This protocol         should be useable with MIB-I or MIB-II.  But, it will also be         able to exploit the new features of the OIM-MIB-II.      3) This document is based on the final International Standards         for CMIS/CMIP (ISO 9595/9596) rather than the Draft         International Standards.      4) Many of the original agreements defined in RFC 1095 have been         accepted and included in the OIW NMSIG implementers agreements.         Rather than duplicating these agreements, they have been removed         from this memo.  This document should be read in conjunction         with ISO 9595/9596 (CMIS/CMIP) and the OIW Stable Agreements         document.      5) The Association Negotiation describe in RFC 1095 has been         changed to align with current international and national         agreements.  But, it has retained backwards compatibility withWarrier, Besaw, LaBarre & Handspicker                           [Page 2]RFC 1189                     CMOT and CMIP                  October 1990         the assignment of an Application Context Name which is identical         to the Application Context Name specified in RFC 1095.2.  Introduction   This memo is the output of the OSI Internet Management Working Group   of the Internet Engineering Task Force (IETF).  As directed by the   Internet Activites Board (IAB) in RFC 1052, it addresses the need for   a long-term network management system based on ISO CMIS/CMIP.  This   memo contains a set of protocol agreements for implementing a network   management system based on these ISO Management standards.  Now that   CMIS/CMIP has been voted an International Standard (IS), it has   become a stable basis for product development.  This profile   specifies how to apply CMIP to management of both IP-based and OSI-   based Internet networks.  Network management using ISO CMIP to manage   IP-based networks will be refered to as "CMIP Over TCP/IP" (CMOT).   Network management using ISO CMIP to manage OSI-based networks will   be refered to as "CMIP".  This memo specifies the protocol agreements   necessary to implement CMIP and accompanying ISO protocols over OSI,   TCP and UDP transport protocols.   This memo must be read in conjunction with ISO and Internet documents   defining specific protocol standards.  Documents defining the   following ISO standards are required for the implementor: Abstract   Syntax Notation One (ASN.1) [5, 6], Association Control (ACSE) [7,   8], Remote Operations (ROSE) [9, 10], Common Management Information   Services (CMIS) [11] and Common Management Information Protocol   (CMIP) [12] with their addenda [32-35].  The specification of a   lightweight presentation layer protocol is required for use with the   CMOT section of this profile (see RFC 1085 [13]).  The SMI (see RFC   1065 [2]), the MIB-I (see RFC 1066 [3]), the MIB-II (see RFC 1156   [28]), and the OIM-MIB-II (see [29]) are used with this management   system.   This memo is divided into sections for each of the protocols for   which implementors' agreements are needed: CMISE, ACSE, ROSE, and,   for CMOT, the lightweight presentation protocol.  The protocol   profile defined in this memo draws on the technical work of the OSI   Network Management Forum [14] and the Network Management Special   Interest Group (NMSIG) of the National Institute of Standards and   Technology (NIST) (formerly the National Bureau of Standards) [30].   Wherever possible, an attempt has been made to either directly   reference or remain consistent with the protocol agreements reached   by these groups.Warrier, Besaw, LaBarre & Handspicker                           [Page 3]RFC 1189                     CMOT and CMIP                  October 19903.  Protocol Overview   This part of the document is a specification of the protocols of the   OIM architecture.  Contained herein are the agreements required to   implement interoperable network management systems using these   protocols.  The protocol suite defined by these implementors'   agreements will facilitate communication between equipment of   different vendors, suppliers, and networks.  This will allow the   emergence of powerful multivendor network management based on ISO   models and protocols.   The choice of a set of protocol standards together with further   agreements needed to implement those standards is commonly referred   to as a "profile."  The selection policy for this profile is to use   existing standards from the international standards community (ISO   and CCITT) and the Internet community.  Existing ISO standards and   draft standards in the area of OSI network management form the basis   of this profile.  Other ISO application layer standards (ROSE and   ACSE) are used to support the ISO management protocol (CMIP).  To   ensure interoperability, certain choices and restrictions are made   here concerning various options and parameters provided by these   standards.   Internet standards are used to provide the underlying   network transport.  These agreements provide a precise statement of   the implementation choices made for implementing ISO network   management standards in IP-based and OSI-based internets.   In addition to the OIM working group, there are at least two other   bodies actively engaged in defining profiles for interoperable OSI   network management: the OSI Implementors Workshop (OIW) and the OSI   Network Management Forum.  Both of these groups are similar to the   OIM working group in that they are each defining profiles for using   ISO standards for network management.  Both differ in that they are   specifying the use only of underlying ISO protocols, while the OIM   working group is concerned with using OSI management in both OSI and   TCP/IP networks.  In the interest of greater future compatibility,   the OIM working group has attempted to make this profile conform as   closely as possible to the ongoing work of these two bodies.   This section will describe the CMOT Protocol Suite, the CMIP Protocol   Suite and Conformance Requirements common to both CMOT and CMIP.   Later sections will specify the implementers agreements for specific   layer protocols that comprise the CMOT and CMIP Protocol Suites.Warrier, Besaw, LaBarre & Handspicker                           [Page 4]RFC 1189                     CMOT and CMIP                  October 19903.1.  The CMOT Protocol Suite   The following seven protocols compose the CMOT protocol suite: ISO   ACSE, ISO DIS ROSE, ISO CMIP, the lightweight presentation protocol   (LPP), UDP, TCP, and IP.  The relation of these protocols to each   other is briefly summarized in Figure 2.                 +----------------------------------------------+                         Management Application Processes                 +----------------------------------------------+                             +-------------------+                                     CMISE                                 ISO 9595/9596                             +-------------------+                 +------------------+       +--------------------+                          ACSE                       ROSE                   ISO IS 8649/8650           ISO DIS 9072-1/2                 +------------------+       +--------------------+                 +-----------------------------------------------+                       Lightweight Presentation Protocol (LPP)                                     RFC 1085                 +-----------------------------------------------+                 +------------------+       +--------------------+                         TCP                         UDP                       RFC 793                     RFC 768                 +------------------+       +--------------------+                 +-----------------------------------------------+                                       IP                                     RFC 791                 +-----------------------------------------------+                      Figure 2.  The CMOT Protocol Suite