3.2.1 Abstract Data Model
This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This specification does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this specification.
Note that it is possible to implement the conceptual data defined in this section using a variety of techniques. An implementation is at liberty to implement such data in any way it pleases.
The Management Client role MUST extend the common Abstract Data Model specified in section 3.1.1 and the Management Server Role Abstract Data Model registry keys specified in section 3.3.1.2 to include the following data elements:
Management Client Name: A Name Object used to identify the Management Client with the underlying OleTx Transports Protocol [MS-CMPO] transport infrastructure.
Management Server Name: A Name Object used to identify the Management Server with which the Management Client communicates.
Management Connection: A Connection that is established with the Management Server.
Management Server Cluster Resource ID: The Cluster Resource ID used to identify the cluster resource on the Management Server.