DSP2033_1.5.0 (DMTF Glossary)

DMTF Glossary

Document Identifier: DSP2033

Date: 2019-07-02

Version: 1.5.0

Document Class: Informative

1. Scope

This document is an informative collection of terms and abbreviations. The information in this document should not be taken normatively.

Click a letter below to see terms that begin with that letter. Click a term to open the PDF page of the document that contains the definition.

Where multiple definitions appear for a single term, the specification number that contains the preferred definition is identified in bold face.

Note that the links in this document work best with Google Chrome or Mozilla Firefox browsers.

A B C D E F G H I J K L M N O P Q R S T U V W X

Abbreviations

2. Terms

A

Absolute Target Address:

A designation of target address that begins at the root of the containment hierarchy. Server Management Command Line Protocol Specification (SM CLP)

abstract:

A possible implementation type of class adaptations. Management Profile Usage Guide

abstract class adaptation:

A class adaptation with an implementation type of "abstract". The requirements of abstract class adaptations apply only in the context of other class adaptations that use them as base adaptations. Management Profile Usage Guide

abstract profile:

A special kind of profile specifying common elements and behavior as a base for derived profiles. Management Profile Usage Guide

AC power cycle:

A process whereby a complete removal of power to the firmware device is performed. A common example is a power supply AC cord removed from the system. This will cause all power inputs to the firmware device (including any auxiliary voltage inputs) to be removed. Platform Level Data Model (PDLM) for Firmware Update Specification

AC power cycle activation:

A process whereby a firmware device activates any pending firmware component images which indicated an AC power cycle as its activation method. Platform Level Data Model (PDLM) for Firmware Update Specification

Academic Alliance Member:

An individual belonging to an accredited institution of higher learning that has been assigned by the DMTF Board of Directors to a single Working Group or Subcommittee as a non-voting member. DMTF Process for Working Bodies

account identity:

The security principal that represents an authenticated Account. Simple Identity Management Profile

activation:

A process in which the firmware device prepares the newly transferred component images to become the active running firmware components. Platform Level Data Model (PDLM) for Firmware Update Specification

Actual Event:

Anything that happens, or is contemplated as happening[EPTS Glossary]. This definition encompasses events taking place within or outside computing domains, and has nothing to do with any description of the actual event. In common usage and where the meaning is clear in context, we will sometimes use simply “Event” when discussing “Actual Events. Cloud Auditing Data Federation-Data Format and Interface Definitions Specification

adaptation:

Short form for class adaptation. Management Profile Usage Guide

adaptation instance:

An instance of an adapted class that complies with all requirements of the class adaptation. Management Profile Usage Guide

adapted class:

A class that is the subject of a class adaptation. Management Profile Usage Guide

address:

The general concept of a location reference to a CIM object that is accessible through a CIM server, not implying any particular format or protocol.
More specific kinds of addresses are object paths.
Embedded objects are not addressable; they may be accessible indirectly through their embedding instance. Instances of an indication class are not addressable since they only exist while being delivered. Common Information Model (CIM) Infrastructure

addressing:

The use of a web service specification to specify the address of a managed resource In this specification, two different versions of web service addressing may be used, depending on context and interoperability requirements. The general term "addressing" may be used to refer to Addressing defined in WS-Management 1.1 Clause 5 or to W3C Web Services Addressing 1.0. WS-Management CIM Binding Specification,

Addressing Associations:

An association instance that is used by the MAP to construct the UFiP to an instance referenced by the association instance. Server Management Command Line Protocol Specification (SM CLP)

Address Resolution Protocol (ARP):

Refers to the procedure used to dynamically determine the addresses of devices on a shared communication medium. MCTP Base Specification

Admin Domain:

The set of Managed Elements, Logical Devices, and Services for which the MAP has management responsibilities. Server Management Command Line Protocol Specification (SM CLP)

agreement:

This (Conformance Program) document when accepted and signed by the Applicant, the DMTF, and the DMTF Conformance Program Administrator. DASH 2.0 Conformance Program Policies and Procedures

aggregation:

The combination within a single event of two or more other events (or references to those events). Aggregation is typically a bundling of separate events that preserves and keeps the original events accessible. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

A strong form of association that expresses a whole-part relationship between each instance on the aggregating end and the instances on the other ends, where the instances on the other ends can exist independently from the aggregating instance. For example, the containment relationship between a physical server and its physical components can be considered an aggregation, since the physical components can exist if the server is dismantled. A stronger form of aggregation is a composition. Common Information Model (CIM) Infrastructure

aggregation metric:

a type of metric that is derived by applying a formula or filter to a set of base metric values. Base Metrics Profile

alert indication:

An indication that indicates an event related to the managed environment. For details, see 6.1.2.2 in Indications Profile

allocated resource:

The result of a resource allocation request—the assigned, separated, reserved, or shared part of the resource or emulated resource allocated to the consumer based on the resource allocation request. Resource Allocation Profile

Alternate Voter:

Any person eligible to vote in a particular Body who is not identified in the roster of that Body as the Primary Voter. DMTF Process for Working Bodies

ancestor:

The ancestor of a schema element is for a class, its direct superclass (if any); for a property or method, its overridden property or method (if any); and for a parameter of a method, the like-named parameter of the overridden method (if any)

The ancestor of a schema element plays a role for propagating qualifier values to that schema element for qualifiers with flavor ToSubclass. Common Information Model (CIM) Infrastructure

ancestry:

The ancestry of a schema element is the set of schema elements that results from recursively determining its ancestor schema elements

A schema element is not considered part of its ancestry. Common Information Model (CIM) Infrastructure

appliance:
See virtual appliance

applicant:

A company applying for validation of Conformance Test Results. Common Diagnostics Model 1.0 Conformance Policy; DASH 2.0 Conformance Program Policies and Procedures

application:

Software that provides functions that are required by an IT Service

Each application may be part of more than one IT Service. An application instance can run on one or more computing systems. Use Cases and Interactions for Managing Clouds

application agreement, agreement:

The Application Agreement states the legal commitment to the terms and conditions of this Conformance Program. The Agreement must be signed by both the Applicant and the DMTF. Common Diagnostics Model 1.0 Conformance Policy

application state:

The state that indicates where an application is in completing a task. In a RESTful system, the client is solely responsible for application or session state. The server is only responsible for resource state, the state of the resources managed by the service. An example of resource state is the account balance in a banking service, which would be maintained by the server. An example of application state is a specific client that has posted a deposit and is waiting for it to clear. Only the client would track the fact that it has posted a deposit request. CIM-RS White Paper

arity:

The number of references exposed by an association class. Common Information Model (CIM) Infrastructure

Associated Privilege Management Capability:

An instance of CIM_RoleBasedManagementCapabilities describing the capabilities of the mentioned instance of CIM_Privilege as described in subclause 6.3.4. Role Based Authorization Profile

Associated Role Management Capability:

An instance of CIM_RoleBasedManagementCapabilities, which is associated with the instance of CIM_RoleBasedAuthorizationService through the CIM_ElementCapabilities association, which in turn is a ssociated with the mentioned instance of CIM_Role through the CIM_ServiceAffectsElement association. Role Based Authorization Profile

Association:

A relationship between two Managed Elements, which is itself a manageable entity within the Admin Domain. Filter Query Language

association, CIM association:

A special kind of class that expresses the relationship between two or more other classes

The relationship is established by two or more references defined in the association that are typed to these other classes.

For example, an association ACME_SystemDevice may relate the classes ACME_System and ACME_Device by defining references to those classes.

A CIM association is a UML association class. Each has the aspects of both a UML association and a UML class, which may expose ordinary properties and methods and may be part of a class inheritance hierarchy. The references belonging to a CIM association belong to it and are also exposed as part of the association and not as parts of the associated classes. The term "association class" is sometimes used instead of the term "association" when the class aspects of the element are being emphasized.

Aggregations and compositions are special kinds of associations.

In a CIM server, associations are special kinds of objects. The term "association object" (i.e., object of association type) is sometimes used to emphasize that. The address of such association objects is termed "class path", since associations are special classes. Similarly, association instances are a special kind of instances and are also addressable objects. Associations may also be represented as embedded instances, in which case they are not independently addressable.

In a schema, associations are special kinds of schema elements.

In the CIM meta-model, associations are represented by the meta-element named "Association". Common Information Model (CIM) Infrastructure

Association Class:

Identifies the CIM Class of an Association. Server Management Command Line Protocol Specification (SM CLP)

association end:

A synonym for the reference defined in an association. Common Information Model (CIM) Infrastructure

Asymmetric Key Pair:

Public/private key pair represented by CIM_UnsignedCredential. Certificate Management Profile

asynchronous event notification:

Control packet sent by the Network Controller to the Management Controller as an explicit notification of the occurrence of an event of interest to the Management Controller. Network Controller Sideband Interface (NC-SI) Specification

Audit:

A survey of a set of systems to determine if they are complying with stated policy objectives.

Systematic, independent and documented process for obtaining audit evidence and evaluating it objectively to determine the extent to which audit criteria are fulfilled. [ISO 14001:2004]

Within the scope of this specification, the definition of "audit" is restricted to the representation, collection, storage and evaluation of CADF Event Records. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Audit Event:

An audit event is any event record that reports activity that may be used for the purposes of an audit. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Audit Trail:

A chronological record that reconstructs and examines the sequence of activities surrounding or leading to a specific operation, procedure, or event in a security relevant transaction from inception to final result. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

authentication:

The process of verifying the credentials provided by an entity for the purpose of resolving to a security principal.

A process used to achieve sufficient confidence in the binding between the entity and the presented identity. NOTE: Use of the term authentication in an Identity Management (IdM) context is taken to mean entity authentication. [ITU X.1252] Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

The process of verifying a claim, made by a subject, that it should be allowed to act on behalf of a given principal (person, service, etc.). Typical authentication mechanisms involved the use of username/password combination or public/private key pairs. Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP

authorization:

The process of verifying that an authenticated principal (person, service, etc.) has permission to perform certain operations (e.g., read, update) on specific resources. Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP

(Also known as Access Control) The process of determining, by evaluating applicable access control information, whether a subject is allowed to have the specified types of access to a particular resource. [SAML-Gloss-2.0]; a prescription that a particular behavior shall not be prevented [ISO 15414:2006]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Authorized Contact:

The person in the Participant company who is authorized by the company to make Program-related decisions for the company. The Program Administrator accepts Program-related information and decisions from these persons only. DASH 2.0 Conformance Program Policies and Procedures

auto-apply:

A firmware device procedure that is implemented if the component image was being directly placed into the final memory destination in parallel while the component image was being transferred. Platform Level Data Model (PDLM) for Firmware Update Specification

automatic activation:

A process whereby the firmware device automatically activates a transferred component image during the apply stage of the firmware update process. Platform Level Data Model (PDLM) for Firmware Update Specification

autonomous profile:

A profile that defines (addresses) an autonomous and self-contained management domain. An autonomous profile may be used alone. An autonomous profile may optionally reference other profiles, including component profiles and other autonomous profiles. Management Profile Usage Guide ,

DSP1001 defines that in autonomous profiles, the central class adaptation and scoping class adaptation are the same. Thus, autonomous profiles cannot be scoped by other profiles. With the exception of this profile, autonomous profiles do not need to be referenced in order to be implemented, and can therefore be implemented alone. Autonomous profiles may reference component profiles and autonomous profiles (including itself) and may scope component profiles. Profile Registration Profile

available software:

Software that the management infrastructure has determined is available, either locally or at a remote location, for installation on the managed system and may be appropriate to install without any assertion about the ability to perform the installation through the management infrastructure. Software Inventory Profile

Back to Top

B

backward compatibility:

Characteristic of profiles enabling clients written against prior minor versions of a profile to use the functionality specified by that version in the context of a profile implementation of a later minor version, without requiring modifications of the client. Management Profile Usage Guide

Ballot:

A vote by any means. DMTF Process for Working Bodies

base adaptation:

A class adaptation of a referenced profile whose requirements and constraints are adopted by a class adaptation of a referencing profile. Management Profile Usage Guide

A class adaptation that is used as the base for another class adaptation. Management Profile Specification Usage Guide

baseboard management controller (BMC):

A term coined by the IPMI specifications for the main management controller in an IPMI-based platform management subsystem. Also sometimes used as a generic name for a motherboard resident management controller that provides motherboard-specific hardware monitoring and control functions for the platform management subsystem. MCTP Base Specification

An embedded device or service, typically an independent microprocessor or System-on-Chip with associated firmware, within a Computer System used to perform systems monitoring and management related tasks, which are commonly performed out-of-band. Redfish Scalable Platforms Management API Specification

base class:

A class that is defined in a CIM schema and from which other classes are derived which may contain other properties or other CIM named elements.

These additional named elements are extensions to the base class. WS-Management CIM Binding Specification

Basic I/O System (BIOS):

The name for system firmware typically used for initialization and launching the boot of an ISA (Industry Standard Architecture), or 'x86' or 'PC', architecture-based computer system. Redfish Host Interface Specification

baseline transmission unit:

The required common denominator size of a transmission unit for packet payloads that are carried in an MCTP packet. Baseline Transmission Unit-sized packets are guaranteed to be routable within an MCTP network. MCTP Base Specification

base metric:

A metric provided directly without a dependency on other metric values. Base Metrics Profile

base profile:

referenced profile that is used as the base for another profile. Management Profile Usage Guide

binary-coded decimal (BCD):

Indicates a particular binary encoding for decimal numbers where each four bits (nibble) in a binary number is used to represent a single decimal digit, and with the least significant four bits of the binary number corresponding to the least significant decimal digit. The binary values 0000b through 1001b represent decimal values 0 through 9, respectively. For example, with BCD encoding a byte can represent a two-digit decimal number where the most significant nibble (bits 7:4) of the byte contains the encoding for the most significant decimal digit and the least significant nibble (bits 3:0) contains the encoding for the least significant decimal digit (for example, 0010_1001b in BCD encoding corresponds to the decimal number 29). MCTP Base Specification

binary encoded JSON (BEJ):

A compressed binary format for encoding JSON data. Platform Level Data Model (PLDM) for Redfish Device Enablement

BIOS attribute:

A BIOS element that provides information, a control surface, or both for basic hardware setup and configuration in a computer system

BIOS attributes are typically accessible in the computer’s system and option ROM setup screens. BIOS Management Profile

blade:

A physical package that contains one or more operational aspects of a data center, such as storage, network, or computational functionality, while relying on the containing modular system for infrastructure, such as power and cooling. Modular Systems Profile

blade expansion:

A physical package that provides additional operational aspects of a computer system to a blade, yet contains insufficient functionality to support an operating system on its own. Modular Systems Profile

Board of Directors (Board):

Member Companies who are Voting Members and are elected by Voting Members to serve on the Board of Directors. Board Member companies appoint persons as representative directors to the Board. DMTF Process for Working Bodies

Board Support Package (BSP):

The name for system firmware typically used for initialization and launching the boot of Linux in a computer system that uses a non-ISA architecture, but may be used for booting other types of operating systems or runtime software. Redfish Host Interface Specification

Body:

This term is used as a substitution for Committee, Subcommittee, Forum, Chapter or Working Group that is the focus of the text in question.

A substitution for Committee, Subcommittee, Forum, Chapter, or Working Group. DMTF Process for Working Bodies

boot configurable system:

An instance of CIM_ComputerSystem whose boot configurations are being managed. Boot Control Profile

boot configurable representation:

The CIM representation of a boot configuration, which consists of an instance of class CIM_BootConfigSetting and, optionally, all of the instances of classes CIM_BootSourceSetting, CIM_BootSettingData and CIM_SettingData that it directly or indirectly aggregates. Boot Control Profile

Boot Control Vector (BCV):

See the BIOS Boot Specification for additional information. Boot Control Profile

bridge:

Generically, the circuitry and logic that connects one computer bus or interconnect to another, allowing an agent on one to access the other. Within this document, the term bridge shall refer to MCTP bridge, unless otherwise indicated. MCTP Base Specification

bulk subscription:

An indication subscription to a filter collection that includes more than one indication filter. Indications Profile

burst:

A number of consecutive baseline transmission unit packets that the transmitter endpoint sends with minimal delay between those baseline transmission unit packets. MCTP Base Specification

bus:

A physical addressing domain shared between one or more platform components that share a common physical layer address space. MCTP Base Specification

bus owner:

The party responsible for managing address assignments (can be logical or physical addresses) on a bus (for example, in MCTP, the bus owner is the party responsible for managing EID assignments for a given bus). A bus owner may also have additional media-specific responsibilities, such as assignment of physical addresses. MCTP Base Specification

byte:

An 8-bit quantity. Also referred to as an octet. NOTE PMCI specifications shall use the term byte, not octet. MCTP Base Specification

Back to Top

C

cache memory:

Indicates the instance of CIM_Memory that represents the cache memory for the processor. CPU Profile

can:

Used for statements of possibility and capability, whether material, physical, or causal. Profile Registration

cannot:

Used for statements of possibility and capability, whether material, physical, or causal. Profile Registration

capabilities collection:

CIM_ConcreteCollection instance for instances of the CIM_Capabilities class. SMASH Collections Profile

capabilities set:

A set of instances of class CIM_SettingData associated with the association CIM_SettingsDefineCapabilities to a CIM_Capabilities instance, and the associated CIM_Capabilities instance. Allocation Capabilities Profile

capacities collection:

CIM_ConcreteCollection instance for instances of the CIM_ConfigurationCapacity class. SMASH Collections Profile

cardinality:

the number of elements; the number of instances in a set. Common Information Model (CIM) Infrastructure

central class:

A class defined in a profile and identified as the focal point for identifying conformance with that profile. Profile Registration

central class adaptation:

A class adaptation whose instances act as an algorithmic focal point for advertising conformance of an implementation to a profile. For a more general definition, see DSP1001. adaptation". Management Profile Usage Guide
See also scoping class adaptation.

A specifically designated class adaptation in a profile. The central class adaptation is the focal point of the profile. Profile Registration Profile
See also scoping class adaptation.

central class methodology:

An algorithm for advertising profile conformance that uses the central instances of the registered profile as an algorithmic focal point. For a complete definition, see 6.2.2. Profile Registration Profile
See also scoping class methodology

central element:

The managed object type modeled by a central class adaptation. Profile Registration Profile
See also scoping element

Central Instance:

An instance of the Central Class that is the focal point for an implementation of the profile.

An instance of the central class adaptation. Profile Registration Profile
See also scoping instance

certification:

The acknowledgment by the Conformance Program Administrator that a validation has been completed for a Conformance Test Result Submission, and that the Conformance Requirements, including the Application and applicable fees, have been met. Common Diagnostics Model 1.0 Conformance Policy

Certification Registry (CR):

The formal record of DMTF Conformance Programs and Certified Conformance Test Results Submissions by the DMTF, made publicly available at the DMTF Web site: http://www.dmtf.org. Common Diagnostics Model 1.0 Conformance Policy

Certification Revocation List (CRL)

certified implementation:

A Submission for which the Program Administrator has issued written notice to the Applicant of successful validation of Conformance Testing Results. Common Diagnostics Model 1.0 Conformance Policy

Certified Submission:

A Submission for which the Program Administrator has validated, evaluated, and certified Conformance Test Results and issued written notice to the Applicant of successful Conformance Testing completion. DASH 2.0 Conformance Program Policies and Procedures

Change Request (CR):

The form used to request a change to the MOF Schema (CIM schema) or a DMTF Document. DMTF Process for Working Bodies

channel:

The control logic and data paths that support NC-SI Pass-through operations through a single network interface (port).

A Network Controller that has multiple network interface ports can support an equivalent number of NC-SI channels. Network Controller Sideband Interface (NC-SI) Specification

chassis:

A placement policy as defined in the class CIM_Chassis. Open Virtualization Format Specification

child pool:

Pool whose resources are backed by other resource pools; consumer of resources from its parent resource pools; contains no host resources, instead draws resources from parent pools through resource allocations. Resource Allocation Profile

CIM client:

A role responsible for originating CIM operations for processing by a CIM server.

This definition does not imply any particular implementation architecture or scope, such as a client library component or an entire management application. Common Information Model (CIM) Infrastructure

CIM element:

One of the following components of the CIM metamodel used to define a schema: Class, instance, property, method, parameter, or qualifier. CIM Operations over HTTP

One of the following components of the CIM metamodel: Namespace, Class, Property, Method, or Qualifier.

CIM_ElementSettingData (ESD)

CIM_EthernetPortAllocationSettingData (EPASD)

CIM_EthernetPortAllocationSettingData that represents settings specifically related to allocation of an Ethernet port resource. Profile to Enable Automated Deployment of OVF Packages

CIM export message:

A CIM message used to communicate information about a CIM namespace or element that is foreign to the target. CIM Operations over HTTP

CIM listener:

A role responsible for processing CIM indications originated by a CIM server.

This definition does not imply any particular implementation architecture or scope, such as a standalone demon component or an entire management application. Common Information Model (CIM) Infrastructure

CIM message:

A well-defined request or response data packet used to exchange information among CIM products. CIM Operations over HTTP

CIM metamodel:

The metamodel described in this document, defining the semantics for the construction of schemas that conform to the metamodel. CIM Infrastructure Specification

CIM object:

A class, instance, qualifier type or namespace that is accessible through a CIM server. Generic Operations Specification

An object may be addressable, i.e., have an object path. Embedded objects are objects that are not addressable; they are accessible indirectly through their embedding property, parameter or method return value. Instances of indications are objects that are not addressable either, as they are not accessible through a CIM server at all and only exist in the protocol message in which they are being delivered. Common Information Model (CIM) Infrastructure

A namespace, class, instance, or qualifier that is defined in a CIM-XML declaration or accessible in a WBEM server. CIM Operations over HTTP

CIM operation:

An interaction within a CIM protocol that is originated by a CIM client and processed by a CIM server. Common Information Model (CIM) Infrastructure

CIM protocol:

A protocol that is used between CIM client, CIM server and CIM listener This definition does not imply any particular communication protocol stack, or even that the protocol performs a remote communication. Common Information Model (CIM) Infrastructure

CIM-RS operation:

An interaction in the CIM-RS protocol where a WBEM client invokes an action in a WBEM server, or a WBEM server invokes an action in a WBEM listener. For a full definition, see 5.1. CIM-RS Operation

CIM-RS payload element:

Type of content of the entity body of the HTTP messages used by the CIM-RS protocol. Payload elements are abstractly defined in CIM-RS Operation and concretely in CIM-RS payload representation specifications, such as this document. CIM-RS Payload Representation in JSON

CIM-RS payload representation:

An encoding format that defines how the abstract payload elements defined in CIM-RS Operation are encoded in the entity body of the HTTP messages used by the CIM-RS protocol. This includes resource representations. CIM-RS Payload Representation in JSON

CIM-RS payload representation specification:

A specification that defines a CIM-RS payload representation, such as this document. CIM-RS Payload Representation in JSON

CIM-RS protocol:

The RESTful protocol defined in CIM-RS Protocol Specification, for which this document describes a payload representation in JSON. CIM-RS Payload Representation in JSON

CIM-RS resource:

An entity in a WBEM server or WBEM listener that can be referenced using a CIM-RS resource identifier and thus can be the target of an HTTP method in the CIM-RS protocol. Also called "resource" in CIM-RS Payload Representation in JSON

CIM-RS resource identifier:

A URI that is a reference to a CIM-RS resource in a WBEM server or WBEM listener, as defined in CIM-RS Protocol Specification. Also called "resource identifier" in CIM-RS Payload Representation in JSON

CIM Schema:

The schema published by the DMTF that defines the Common Information Model. It is divided into a core model and a common model. Extension schemas are defined outside of the DMTF and are not considered part of the CIM Schema. CIMI-CIM Specification

A formal language representation of a model, (including but not limited to CIM Schema), that is conformant to the CIM Metamodel. DMTF Process for Working Bodies

CIM server:

A role responsible for processing CIM operations originated by a CIM client and for originating CIM indications for processing by a CIM listener.

This definition does not imply any particular implementation architecture, such as a separation into a CIMOM and provider components. Common Information Model (CIM) Infrastructure

CIM_SettingsDefineCapabilities (SDC)

CIM_SettingsDefineState (SDS)

CIM-XML consumer:

A WBEM server, client or listener that receives a CIM-XML message, or a program that consumes a CIM-XML declaration. Representation of CIM in XML

CIM-XML declaration:

A declaration of CIM objects (classes, instances and qualifiers), using the DECLARATION element defined in this specification. Note that "CIM declaration" was used for this term before version 2.4 of this specification. Representation of CIM in XML

CIM-XML message:

A request or response message in the CIM-XML protocol, using the MESSAGE element defined in this specification. Note that "CIM message" was used for this term before version 2.4 of this specification. Representation of CIM in XML

CIM-XML producer:

A WBEM server, client or listener that sends a CIM-XML message, or a program that produces a CIM- XML declaration. Representation of CIM in XML

CIM-XML protocol:

The WBEM protocol that uses the CIM operations over HTTP defined in this document and the representation of CIM in XML defined in Representation of CIM in XML

CIM-XML schema:

The XML schema for representing CIM in XML, defined by this specification. Representation of CIM in XML

class:

If used without qualification this term refers to a CIM class that may also be an association class or an indication class. To refer to a CIM class that is not an association class or an indication class, use the term "ordinary class". Common Information Model (CIM) Infrastructure

class adaptation:

A named profile element that defines requirements and constraints on a class. A class adaptation adapts a class definition from a schema for a particular purpose and may be based on other class adaptations. Management Profile Usage Guide

class declaration:

The definition (or specification) of a class. For example, a class that is accessible through a CIM server can be retrieved by a CIM client. What the CIM client receives as a result is actually the class declaration. Although unlikely, the class accessible through the CIM server may already have changed its definition by the time the CIM client receives the class declaration. Similarly, when a class accessible through a CIM server is being modified through a CIM operation, one input parameter might be a class declaration that is used during the processing of the CIM operation to change the class. Common Information Model (CIM) Infrastructure

class origin:

The class origin of a feature is the class defining the feature. Common Information Model (CIM) Infrastructure

class path:

A special kind of object path addressing a class that is accessible through a CIM server. Common Information Model (CIM) Infrastructure

A special kind of object path addressing a class that is accessible through a WBEM server. Generic Operations Specification

client:

Any system that acts in the role of a client to a MAP. System Management Architecture for Server Hardware Whitepaper

A WBEM client that exploits applicable portions of this profile. Management Profile Usage Guide

An application that exploits facilities specified by the profiles in this standard. Virtual Ethernet Switch Profile

The application that uses the Web services defined in this document to access the management service. Web Services for Management (WS- Management) Specification

Any agent that communicates with a management controller to enable a user to manage Redfish-compliant systems and RDE Devices. Platform Level Data Model (PLDM) for Redfish Device Enablement

client software:

The part of a client-server application that the user directly interfaces with, for example: an email client. Software Identification and Entitlement Usage Metrics

cloud:

Synonymous with “cloud computing” as defined in section 2 of the NIST Definition of Cloud Computing [SP800-145]. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

Cloud Auditing Data Federation (CADF):

An open standard that addresses the need for cloud security policies by enabling cross-vendor information sharing via its data format and interface definitions. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Cloud Computing:

A model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Software Identification and Entitlement Usage Metrics

Cloud Management Working Group (CMWG):

Models the management of cloud services and the operations and attributes of the cloud service lifecycle through its work on the Cloud Infrastructure Management Interface (CIMI). Cloud Management Working Group (CMWG)

Cloud Service Consumer or Cloud Consumer Administrator:

A category of actors that includes the Consumer Business Manager (who approves business and financial expenditures for consumed services, accounts for used service instances, establishes business relationships; sets up accounts, budget, and terms; etc.), the Consumer Service Administrator (who requests service instances and changes to service instances, purchase services within the business relationship; create Service Users (including policies), allocate resources, such as compute and storage, generate reports (usage), etc.), and Service Users (who uses service instances provided by a Cloud Service Provider)

The term “Consumer” is used when the indicated action or activity could involve one or more of the above actors. In cases where the distinction between the actors in this category is relevant, the more detailed term will be used. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

Cloud Service Provider:

CA category of actors that includes the Service Operations Manager (who manages the technical infrastructure required for providing cloud services, monitors and measures performance and utilization against SLAs, provides reports from monitoring and measurement, etc.), Service Business Manager (who offers all types of services developed by cloud service developers, accounts for services potentially offered by service providers themselves and services offered on behalf of cloud service developers, establishes a portfolio of business relationships, and sets up accounts and terms for Consumers, etc.), and Service Transition Manager (who enables a customer to use the cloud service, including "onboarding", integration, and process adoption, defines and creates service offerings based on Templates and Configurations that can be used by Consumers and are populated into the catalog, etc.)

The term “Provider” is used when the indicated action or activity could involve one or more of the above actors. In cases where the distinction between the actors in the category is relevant, the more detailed term will be used.

For purposes of comparison and alignment, it should be noted that a Cloud Service Provider is equivalent to the “Cloud Provider” actor defined in the NIST Reference Architecture [SP500-292]. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

CLP Service:

The logical entity within a MAP that implements the CLP. Server Management Command Line Protocol Specification (SM CLP)

CLP Target:

A Managed Element or Association whose properties, behavior, UFcT, and so on are wholly defined by the profiles approved for use with the CLP. Server Management Command Line Protocol Specification (SM CLP)

code image:

A collection of bytes typically executed on a processor to perform a function, and may also include non-executable data. Platform Level Data Model (PDLM) for Firmware Update Specification

collaboration structure diagram (CSD)

Collection:

A particular kind of Resource that contains a collection of other Resources and has a representation and serialization defined in this specification. Synonym for “CIMI collection”. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

A Collection is a resource that acts as a container of other Resources. The members of a collection usually have similar characteristics. The container processes messages sent to the container. The members of the container process messages sent only to that member without affecting other members of the container. Redfish Scalable Platforms Management API Specification

Collector:

A Redfish container holding an array of independent Redfish resource Members that in turn are typically represented by a schema external to the one that contains the collection itself. Platform Level Data Model (PLDM) for Redfish Device Enablement

command:

Control packet sent by the Management Controller to the Network Controller to request the Network Controller to perform an action, and/or return data. Network Controller Sideband Interface (NC-SI) Specification

Command Line:

A text message containing the complete expression of a management action, including a command verb, an optional command target, options and option arguments, and properties and values. Server Management Command Line Protocol Specification (SM CLP)

Command Processor:

The logical entity within a MAP responsible for parsing, interpreting, and executing incoming commands and returning responses. Server Management Command Line Protocol Specification (SM CLP)

Command Line Protocol (CLP):

The human-oriented command line protocol defined by the System Management Architecture for Server Hardware, used for managing systems. Server Management Command Line Protocol Specification (SM CLP)

Command Response:

Response returned by the CLP Service to a Client when a Command is issued The Command Response consists of Command Status and Command Results. Server Management Command Line Protocol Specification (SM CLP)

Command Results:

The actual results of a successful command returned as part of the Command Response. Server Management Command Line Protocol Specification (SM CLP)

Command Status:

Information returned by the CLP Service to a client describing the overall status of a command. Server Management Command Line Protocol Specification (SM CLP)

Command Status Data:

Detailed information returned by the CLP Service to a client describing the status of the command as part of the command response. Server Management Command Line Protocol Specification (SM CLP)

Common Diagnostic Model (CDM)

Common Information Model (CIM):

  1. The name of the meta-model used to define schemas (e.g., the CIM schema or extension schemas).
  2. The name of the schema published by the DMTF (i.e., the CIM schema).
  3. CIMI-CIM Specification

common model:

The subset of the CIM Schema that is specific to particular domains It is derived from the core model and is actually a collection of models, including (but not limited to) the System model, the Application model, the Network model, and the Device model. CIM Infrastructure Specification

Common Transport (CT)

Compliance Event:

A compliance event is any event record that reports activity that is required to show compliance to a policy or requirement which are often described by compliance standards. Note: Security compliance events are specialized compliance events that record activity related to authorization and enforcement of security policies in accessing system resources. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

component classification:

The general type of component. Values for this field are aligned with the Value Map from CIM_SoftwareIdentify.Classifications. Platform Level Data Model (PDLM) for Firmware Update Specification

component comparison stamp:

A value that can be used to determine if a given component is a higher or lower version than another value using an unsigned integer comparison. Platform Level Data Model (PDLM) for Firmware Update Specification

component identifier:

A vendor-defined value that distinguishes between firmware components that may have identical classifications but require different component images. Platform Level Data Model (PDLM) for Firmware Update Specification

component image:

A code image contained in a PLDM firmware update package associated with a firmware component of a firmware device.

The component image is transferred to the firmware device using PLDM commands and placed (perhaps in a modified form) into local storage used by the firmware component. Platform Level Data Model (PDLM) for Firmware Update Specification

component image set:

One or more component images contained in a firmware update package that are associated with a particular firmware device. Platform Level Data Model (PDLM) for Firmware Update Specification

component profile:

A profile that describes (addresses) a subset of a management domain. The profile specification of a component profile includes CIM elements that are scoped within an autonomous profile (or in some cases, another component profile). Management Profile Usage Guide

Management Profile Usage Guide (DSP1001) defines that in component profiles, the central class adaptation and scoping class adaptation are not the same. Component profiles need to be scoped by one or more scoping profiles in order to be implemented, and can be implemented only together with one if its scoping profiles. Component profiles may reference autonomous profiles and component profiles (including itself) and may scope other component profiles. Profile Registration Profile

composition:

A strong form of association that expresses a whole-part relationship between each instance on the aggregating end and the instances on the other ends, where the instances on the other ends cannot exist independently from the aggregating instance.

For example, the containment relationship between a running operating system and its logical devices can be considered a composition, since the logical devices cannot exist if the operating system does not exist. A composition is also a strong form of aggregation. Common Information Model (CIM) Infrastructure

computing device:

The hardware technology upon which the software is installed or executed. Software Identification and Entitlement Usage Metrics

computing system:

One or more virtual or physical computing devices including applicable operating system or firmware that support installation and execution of applications. Software Identification and Entitlement Usage Metrics

concrete class adaptation:

Any class adaptation that is not an abstract class adaptation. Management Profile Usage Guide

concrete memory resource pool:

A resource pool that subdivides the capacity of its (primordial or concrete) parent resource pool. Memory Resource Virtualization Profile

concrete profile:

Any profile that is not an abstract profile. Management Profile Usage Guide

concrete storage resource pool:

A storage resource pool that subdivides the capacity of its (primordial or concrete) parent resource pool. Memory Resource Virtualization Profile

condition:

A specification mechanism in profiles that determines whether conditional or conditional exclusive profile elements shall be implemented. Management Profile Usage Guide

conditional:

A requirement level indicating that the subject profile requires the implementation of the designated profile element only under certain conditions, and otherwise leaves the decision to implement the designated profile element to the implementation. Management Profile Usage Guide

Indicates requirements to be followed strictly to conform to the document when the specified conditions are met. IP Interface Profile

conditional exclusive:

A requirement level indicating that the subject profile requires the implementation of the designated profile element only under certain conditions, and otherwise prohibits the implementation of the designated profile element. Management Profile Usage Guide

conditional exclusive profile:

A profile referenced with the conditional exclusive requirement level. Management Profile Usage Guide, version 1.2.0

A used profile that is referenced by a profile reference with the conditional exclusive requirement level. Management Profile Usage Guide, version 1.1.1

conditional profile:

A used profile that is referenced by a profile reference with the conditional requirement level. Management Profile Usage Guide

configuration:

A set of metadata, the values of which serve as the parameters of a discrete conformation of a specific type of virtual resource.

For example, a Machine Configuration may define a Machine with the equivalent of a 2.66 GHz processor, 4 GB of memory, and 320 GB of local disk storage. Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP Specification

conformance or conformant:

The fulfillment of a product, process, or service of specified requirements. Common Diagnostics Model 1.0 Conformance Policy

Conformance Program, Program (CP):

This DMTF Conformance Program: The CDM Conformance Program. Common Diagnostics Model 1.0 Conformance Policy

The DMTF DASH Conformance Program 2.0. DASH 2.0 Conformance Program Policies and Procedures

Conformance Program Administrator, Program Administrator (PA):

The Participant's DMTF contact for the CDM Conformance Program for all applications, Submissions, questions, and general administration. Common Diagnostics Model 1.0 Conformance Policy

Conformance Program Deficiency (CPD):

An acknowledged issue or error in the Conformance Program that inhibits the Certification process. The Conformance Program includes both the certification process and information about how to begin conformance testing. A Conformance Program Deficiency is one possible outcome of an Issue Report. Common Diagnostics Model 1.0 Conformance Policy; DASH 2.0 Conformance Program Policies and Procedures

Conformance Program Guide:

The document that describes the processes for how an Applicant achieves Certification in this Program. The guide is used in conjunction with this policy document. The Conformance Program Guide provides detailed instructions for an Applicant to get a Submission validated to achieve Certification. It also includes references to other relevant documentation. Common Diagnostics Model 1.0 Conformance Policy

conformance requirements:

A definition of the mandatory and optional behavior a Submission must implement to be considered Conformant. The Conformance Requirements can be found in CDM Implementation Requirements (DSP0255). Common Diagnostics Model 1.0 Conformance Policy

A definition of the mandatory and optional behavior a Submission shall implement in order to be considered conformant. The Conformance Requirements are included in in DSP0232, DASH Implementation Requirements 1.0; DSP0232, DASH Implementation Requirements 1.1; DSP0232, DASH Implementation Requirements 1.2. DASH 2.0 Conformance Program Policies and Procedures

conformance statement:

The Applicant’s set of claims describing precisely the way in which the Submission meets the Conformance Requirements, including which optional features are supported. Common Diagnostics Model 1.0 Conformance Policy

Conformance Test Package:

A binary image or archive file that contains executable tests and other files for configuring, running, and interpreting those tests. The Conformance Test Package contains the Conformance Test Suite. DASH 2.0 Conformance Program Policies and Procedures

Conformance Test Results, Submission:

A file generated by the Conformance Test Suite indicating Conformance. The Applicant sends this file to the DMTF for Certification. It should also be accompanied by details describing precisely the methodology and the environment in which the Conformance Requirements were tested. Common Diagnostics Model 1.0 Conformance Policy; DASH 2.0 Conformance Program Policies and Procedures

Conformance Test Suite (CTS):

A software tool licensed to the Applicant under the DMTF Conformance Program for use in testing a Product and generating a Submission. Common Diagnostics Model 1.0 Conformance Policy; DASH 2.0 Conformance Program Policies and Procedures

conformant:

In agreement with the requirements and constraints of a specification. Common Information Model (CIM) Metamodel

consoles collection:

CIM_ConcreteCollection instance for instances of the CIM_TextRedirectionSAP class. SMASH Collections Profile

consumer:

Consumer is a legal entity that purchases, installs, deploys, or uses a product. Software Identification and Entitlement Usage Metrics

The Web service that is requesting the data enumeration from the data. Web Services for Management (WS-Management) Specification

contained entity:

An entity that is contained within a container entity. PLDM for Platform Monitoring and Control Specification

Container Credential Store:

An instance of CIM_CredentialStore associated to the given Credential Instance through CIM_MemberOfCollection association. PLDM for Platform Monitoring and Control Specification

container entity:

An entity that is identified as containing or comprising one or more other entities. PLDM for Platform Monitoring and Control Specification

container ID:

A numeric value that is used within Platform Descriptor Records (PDRs) to uniquely identify a container entity. PLDM for Platform Monitoring and Control Specification

Container Keystore:

The single instance of CIM_Keystore that contains a given PKI Credential Instance. The instance of CIM_Keystore is associated to the PKI Credential Instance through the CIM_MemberOfCollection association. Certificate of Management Profile

containing entity:

An alternative way of referring to the container entity for a given entity. PLDM for Platform Monitoring and Control Specification

Control Objective:

A compliance related requirement or practice. These control objectives are often described by policies and enforcement proven by compliance audits.

In the context of this specification, control objectives are typically requirements on cloud providers that are expected to supply audit compliance data in the form of event records, logs and reports. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Control traffic; Control packets:

Command, response, and asynchronous event notification packets transmitted between the Management Controller and Network Controllers for the purpose of managing the NC-SI. Network Controller Sideband Interface (NC-SI) Specification

cooling domain:

The set of systems and components that share a given cooling source that consists of one or more cooling devices. Modular Systems Profile

core model:

The subset of the CIM Schema that is not specific to any particular domain.

The core model establishes a basis for derived models such as the common model or extension schemas. CIM Infrastructure Specification

Core Properties:

Properties for which the profile that owns the definition of the class does not stipulate any behavioral requirements. However, the properties are defined in the MOF. Server Management Command Line Protocol Specification(SM CLP)

Correlated Event:

Any Event that is associated with some other set of Event s by some relationship, possibly causal. For example, a “throw” event may be associated with a corresponding “catch” event, with the implication that the same resource that was thrown was then caught. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

coverage:

The set of indications that can pass an indication gate. Indications Profile

creation class:

The creation class of an instance is the most derived class of the instance.

The creation class of an instance can also be considered the factory of the instance (although in CIM, instances may come into existence through other means than issuing an instance creation operation against the creation class). CIM Infrastructure Specification

Credential Instance:

An instance of a subclass of CIM_Credential. Credential Management Profile

CRUD:

Basic intrinsic operations used by any interface: Create, Read, Update and Delete. Redfish Scalable Platforms Management API Specification

Cumulative Privilege:

A conceptual instance of CIM_Privilege that represents rights granted. Role Based Authorization Profile

Cumulative Role Privilege:

An instance of CIM_Privilege that is the conceptual representation of all the Granted Privileges and Denied Privileges that are associated with a particular instance of CIM_Role. Role Based Authorization Profile

current boot configuration:

The instance of CIM_BootConfigSetting that was used the last time the managed system was successfully booted. Boot Control Profile

current data:

The most current data available for a given metric. Online monitoring and snapshot monitoring are types of current data access. Base Metrics Profile

Current Default Target (CDT)

The CLP session environment setting that establishes a default base address for all command targets that are expressed as a Relative Target Address and is used as the command target if a target term is not specified in a command entered. Server Management Command Line Protocol Specification(SM CLP)

current resource allocation setting data:

Resource allocation setting data that describes an allocated resource; differs from defined resource allocation setting data if the host system supports the dynamic modification of a resource allocation. Resource Allocation Profile

current setting data:

The virtual setting data associated with the current allocation state of a virtual resource or system. Allocation Capabilities Profile

customer network:

The customer network in an overlay is the network as seen by a virtual machines or a physical server. In an overlay network, the customer network traffic is the encapsulated payload in a packet on the provider network. Network Management - Tunnel Management Profile

Back to Top

D

data center:

A physical location that provides computing resources and may contain physical and virtual systems, storage and networking. Software Identification and Entitlement Usage Metrics

Data Federation:

Any means in which two or more domains enable sharing and exchange of information, such as audit data, for service or content composition, consumption or delivery and coordination with each other. [Kobielus:2006], [Navajo:2009]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

data source:

A Web service that supports traversal using enumeration contexts via the Enumerate operation defined in this specification. Web Services for Management (WS- Management) Specification

DC power cycle:

A process whereby the firmware device has its non-auxiliary power input removed. As most PLDM termini are contained within a solid state device such as an ASIC or FPGA, those devices may contain an auxiliary and non-auxiliary power inputs. Auxiliary voltage inputs are typically not affected by a DC power cycle and may continue to be energized during the activation process. Platform Level Data Model (PDLM) for Firmware Update Specification

DC power cycle activation:

A process whereby the firmware device activates any pending firmware component images which indicated a DC power cycle as its activation method. Platform Level Data Model (PDLM) for Firmware Update Specification

dedicated virtual resource:

Virtual resource that has been given exclusive use of one or more host resources (the host resources are not shared with any other consumer). Resource Allocation Profile

default boot configuration:

The instance of CIM_BootConfigSetting that the computer system manufacturer or a client has informatively tagged as its default boot configuration. Boot Control Profile

defined coverage:

The coverage specified by a profile for static filter collections through normative statements. Indications Profile

defined resource allocation setting data:

Resource allocation setting data that describes a resource allocation request. Resource Allocation Profile

delimited substring:

A substring element of the VendorCompatibilityStrings property of a Physical Element or an instance of CIM_ConfigurationCapacity.

The substring starts at the beginning of the string (representing an element in the array of the VendorCompatibilityStrings property) and terminates at the end of the string, or at a character that precedes a colon (:). Physical Asset Profile

delivery mode:

The mechanism by which notification messages are delivered from the source to the sink. Web Services for Management (WS- Management) Specification

Denied Privilege:

An instance of CIM_Privilege with the PrivilegeGranted property set to FALSE that represents the denied privilege of associated roles. Role Based Authorization Profile

deployment:

The process of installing a service instance in a reserved or prepared environment. Software Identification and Entitlement Usage Metrics

deployment function:

A function the result of which is a prepared virtual system. Open Virtualization Format Specification

deployment platform:

The product that installs an OVF package. Open Virtualization Format Specification

deployment system:

The system that installs a software package or appliance. Software Identification and Entitlement Usage Metrics

deprecated:

Keyword indicating that a profile element or profile defined behavior is outdated and has been replaced by newer constructs. Management Profile Specification Usage Guide

derivation:

A requirement level indicating that the referencing profile is based on and substitutable for the specified referenced profile. Management Profile Specification Usage Guide

derived profile:

A profile that is based on a referenced profile. Management Profile Specification Usage Guide

device component:

A top-level entry point into the schema hierarchy presented by an RDE device. Platform Level Data Model (PDLM) for Firmware Update Specification

device identifier record:

A set of descriptors used to identify a type of firmware device. Platform Level Data Model (PDLM) for Redfish Device Enablement

dictionary:

A binary lookup table containing translation information that allows conversion between BEJ and JSON formats of data for a given resource. Platform Level Data Model (PLDM) for Redfish Device Enablement

direct I/O:

A virtual system is directly connected to a non-virtualized host. Virtual Ethernet Switch Profile

discovery:

The process by which an MC determines that an RDE device supports PLDM for Redfish Device Enablement. Platform Level Data Model (PLDM) for Redfish Device Enablement

discovery mechanism:

A CIM based mechanism yielding a Boolean result that enables clients to discover whether optional, conditional or conditional exclusive profile elements are implemented or available. Management Profile Specification Usage Guide

DMTF Document:

Any published material released by the DMTF except for press releases, web page material, or marketing collateral. DMTF Process for Working Bodies

DMTF Draft Standard:

Any normative DMTF document that has not been approved by the DMTF Board for publication. DMTF Process for Working Bodies

DMTF Informational document:

Any non-normative DMTF document. DMTF Process for Working Bodies

DMTF Informational Specification:

An Informational document produced by a DMTF Incubator that may become a DMTF standard after the incubator transitions to a regular DMTF working group. These documents proceed through a process similar to DMTF Specifications rather than DMTF Informational documents; however, they are not DMTF Standards. DMTF Process for Working Bodies

DMTF Member Review:

For specifications, the period that precedes release as a DMTF Standard. This period is used to meet intellectual property review requirements and to allow time to receive any final input from the DMTF members at large. DMTF Process for Working Bodies

DMTF Standard:

A DMTF document of a normative nature that addresses a specific problem domain and has been released by the DMTF. DMTF Process for Working Bodies

DMTF Standard Publication Identifier (DSP identifier):

An identifier assigned to all DMTF documents. DMTF Process for Working Bodies

Document Request (DR):

The template that is used to obtain, take ownership or return DSP identifiers. DMTF Process for Working Bodies

Document State:

The state of the document which is kept external to the document, such as in metadata on the website. DMTF Process for Working Bodies

Document Status:

The status of the document which is kept internal to the document. This is usually on the first page and limited to the status values defined in subclause 5.3. DMTF Process for Working Bodies

Document Type:

The type of the document which is kept internal to the document. This is usually on the first page and limited to the status values defined in subclause 6.2.1. DMTF Process for Working Bodies

domain:

An area of management or expertise. Common Information Model (CIM) Infrastructure

duplicate object:

Objects in a result set that have duplicate object paths. Generic Operations Specification

duplicate object path:

Object paths in a result set that reference the same CIM object accessible through the WBEM server. Generic Operations Specification

dynamic ethernet connection allocation:

An Ethernet connection in which a default Ethernet switch port is instantiated as part of an Ethernet connection allocation. Ethernet Port Resource Virtualization Profile

dynamic filter:

An instance of CIM_IndicationFilter whose life cycle is controlled by a client. Indications Profile

dynamic indication filter:

An indication filter whose life cycle is controlled by a client. Indications Profile

dynamic power savings mode:

Power savings mode that relies on internal feedback to limit power consumption. Power Utilization Management Profile

Back to Top

E

CIM_EthernetPortAllocationSettingData (EASD)

Editing Body:

Committee, Subcommittee, or Working Group assigned editorial responsibility for any given document. DMTF Process for Working Bodies

effective qualifier value:

For every schema element, an effective qualifier value can be determined for each qualifier scoped to the element. The effective qualifier value on an element is the value that determines the qualifier behavior for the element.

For example, qualifier Counter is defined with flavor ToSubclass and a default value of False. If a value of True is specified for Counter on a property NumErrors in a class ACME_Device, then the effective value of qualifier Counter on that property is True. If an ACME_Modem subclass of class ACME_Device overrides NumErrors without specifying the Counter qualifier again, then the effective value of qualifier Counter on that property is also True since its flavor ToSubclass defines that the effective value of qualifier Counter is determined from the next ancestor element of the element that has the qualifier specified. CIM Infrastructure Specification

The effective value of a qualifier specified on a schema element is the value that determines the qualifier behavior for the schema element, taking the qualifier propagation rules into account. For a complete definition, see Common Information Model (CIM) Infrastructure. Generic Operations Specification

element:

A synonym for schema element. CIM Infrastructure Specification

Electronic Ballot:

A Ballot conducted electronically following the procedures defined in DMTF Process for Working Bodies

eligibility requirements:

The set of requirements that a company shall meet in order to register and participate in the Conformance Program. Companies that meet the Eligibility Requirements are referred to as Eligible Participants. DASH 2.0 Conformance Program Policies and Procedures

eligible participants:

Any company wanting to participate in this Program under the terms stated in the Application Agreement. Common Diagnostics Model 1.0 Conformance Policy

embedded class:

A class declaration that is embedded in the value of a property, parameter or method return value. CIM Infrastructure Specification

embedded instance:

An instance declaration that is embedded in the value of a property, parameter or method return value. CIM Infrastructure Specification

embedded object:

An embedded class or embedded instance. CIM Infrastructure Specification

emulated media device:

The Media device locally emulated on the managed system, which can be redirected to a remote system that contains the physical Media device. Media Redirection Profile

emulated USB device:

The USB device locally emulated on the managed system, which can be redirected to a remote system that contains the physical USB device. USB Redirection Profile

enabled logical element:

Logical managed element that has a concept of enabled state associated with it. Enabled Logical Element Profile

endpoint
See MTCP endpoint

endpoint ID
See MTCP endpoint ID

entitlement (software):

Legal ownership of software license use rights as defined through agreements between a software purchaser and the software copyright holder. Software Identification and Entitlement Usage Metrics

entity:

A particular physical or logical entity that is identified using PLDM monitoring and control data structures for the purpose of monitoring, controlling, or identifying that entity within the platform management subsystem, or for identifying the relationship of that entity to other entities that are monitored or controlled using PLDM monitoring and control

Examples of physical entities include processors, fans, power supplies, and memory chips. Examples of logical entities include a logical power supply (which may comprise multiple physical power supplies) and a logical cooling unit (which may comprise multiple fans or cooling devices). PLDM for Platform Monitoring and Control Specification

Entity ID:

A numeric value that is used to identify a particular type of entity, but without designating whether that entity is a physical or logical entity. PLDM for Platform Monitoring and Control Specification

Entity Instance Number:

A numeric value that is used to differentiate among instances of the same type

For example, if two processor entities exist, one of them can be designated with instance number 1 and the other with instance number 2. PLDM for Platform Monitoring and Control Specification

Entity Type:

A numeric value that identifies both the particular type of entity and whether the entity is a physical or logical entity.

The Entity ID is a sub-field of the Entity Type. PLDM for Platform Monitoring and Control Specification

Entry Point Structure (EPS)

enumeration context:

A session context that represents a specific traversal through a logical sequence of XML element information items using the Pull operation defined in this specification. Web Services for Management (WS-Management) Specification

error reporting requirement:

A requirement stated as part of a method requirement or operation requirement to report an error situation. Management Profile Usage Guide

ethernet adapter:

An EthernetPort, its associated LAN Endpoint(s) and, optionally, a VLAN Endpoint that models the Ethernet device on a virtual or host system. Ethernet Port Resource Virtualization Profile

ethernet adapter allocation request:

A request for an Ethernet adapter resource allocation to a virtual machine; represented as instance of CIM_EthernetPortAllocationSettingData. Ethernet Port Resource Virtualization Profile

ethernet adapter resource allocation:

The allocation of an Ethernet port to a virtual system. Ethernet Port Resource Virtualization Profile

ethernet adapter resource pool:

A resource pool that represents Ethernet adapters available as resources for a virtual computer system resource allocation. Ethernet Port Resource Virtualization Profile

ethernet connection:

The connection of two LAN endpoints where one LAN endpoint is implemented by an Ethernet adapter, and the other LAN endpoint is implemented by an Ethernet switch port, resulting in the connection of a virtual or host system Ethernet adapter to an Ethernet switch port. Ethernet Port Resource Virtualization Profile

ethernet connection allocation:

An allocation request for a connection between a LAN Endpoint on an Ethernet adapter and a LAN Endpoint on an Ethernet switch port.

An Ethernet connection allocation request may cause the implicit allocation of the entities that it connects, such as virtual Ethernet adapters and virtual switch ports. Ethernet connection allocation request is represented as instance of CIM_EthernetPortAllocationSettingData. Ethernet Port Resource Virtualization Profile

ethernet connection allocation request:

The allocation of an Ethernet connection between the LAN Endpoints of an Ethernet adapter and an Ethernet switch port. Ethernet Port Resource Virtualization Profile

ethernet connection resource pool:

A resource pool that represents available Ethernet connections on a virtual Ethernet switch for a virtual computer system. Ethernet Port Resource Virtualization Profile

ethernet switch port:

An EthernetPort, its associated LAN Endpoint(s) and, optionally, a VLAN Endpoint that models the Ethernet port on an Ethernet switch. Ethernet Port Resource Virtualization Profile

ethernet switch port allocation request:

A request for an Ethernet switch port resource allocation; represented as instance of CIM_EthernetPortAllocationSettingData. Ethernet Port Resource Virtualization Profile

switch port resource allocation:

The allocation of an Ethernet port to a virtual Ethernet switch. Ethernet Port Resource Virtualization Profile

ethernet switch port resource pool:

A resource pool that represents Ethernet switch ports available as resources for a virtual Ethernet switch port resource allocation. Ethernet Port Resource Virtualization Profile

event:

The occurrence of a phenomenon of interest to a management application.

Events are not published in CIM directly but may be represented by a model change or the instantiation of a CIM_Indication subclass.

1. An “Actual Event.”

2. An “Event Record.”

In common usage we will use the simpler term “Event” to refer to either “Actual Events” or “Event Records,” with the expectation that the correct definition will be clear in context. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

An observable occurrence of a phenomenon of interest Management Profile Usage Guide

A record that corresponds to an individual alert. Redfish Scalable Platforms Management API Specification

Event Action:

The action (verb) performed by the event initiator (a resource) against the event target resource or resources. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

event-based monitoring:

The process in which threshold values for metrics are used to trigger asynchronous notification. Base Metrics Profile

event consumer | consumer:

A consumer of events is an entity that needs to process, report on, or otherwise use CADF events. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Import and Export:

Support the import and export of logs containing auditable event records with similar contextual information to and from a cloud provider.

Support transforms that can be used for converting domain specific values (e.g., identifiers, classification values, etc.) to values that permit federation and conform to this specification (or vice-versa). Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Initiator:

The resource that initiated, originated or instigated the event action. Typically, the initiating resource is either a user or service that can be identified or described by the system in which the event occurs [TOG-XDAS1]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Log:

A persistent collection of event records. In context, this term may be expressed simply as Log. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Observer:

The resource that observed the actual event and generated an event record to describe it. The observer may or may not itself have been the event initiator or event target.

Please note that in the [EPTS Glossary], this resource is referred to as an event source for the event record. In this specification, we avoid use of the term "source" to prevent ambiguity between event observer and event initiator. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

event provider:

An entity that is able to produce or deliver CADF Event Records. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Query:

A request initiated, for example by a consumer to a provider, asking for a particular set of persisted event records that match some selection criteria. The returned set is typically a bounded set, in that it is returned as part of a discrete transaction and returns only the event records that are currently available at the time of the query. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification - General terms

Support for a standard means to query event records that match specific criteria such as date/time ranges, event taxonomy classifications, domain specific identifiers and tags, occurrences of specific resource types, etc. Support filters used for selecting audit event data sets (for example in the form of logs or reports) that clearly match/identify events that contain specific resource types and/or classification values either defined by this specification or associated with specific domains. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification - Interface definitions

Event Record:

A record or object that represents, encodes, or records an event, generally for the purpose of computer processing.

In common usage and where the meaning is clear in context, we will sometimes use simply “Event” when discussing “Event Records”.

The term "CADF Event Record" is used specifically to reference an event record that conforms to the CADF specification. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

event sink:

A Web service that receives notifications. Web Services for Management (WS-Management) Specification

event source:

Is a term often used in different ways in other domains, such as the [EPTS Glossary], when modeling events and could lead to ambiguity. Therefore, the CADF specification will prefer the more precise terms “Event Initiator” and “Event Observer” and avoid the use of this term. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Stream:

A non-persistent, linearly ordered sequence of events [EPTS Glossary].

Typically an event stream:

- may be ordered by time.

- may be bounded by a certain time interval or other criteria (content, space, source), or be open ended and unbounded. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Submission:

Support message-level submission of one or more events from federated sources (or services) to a cloud provider.

Support information about the source that submitted the event in order to provide domain specific context to resources that could be used to additionally classify or augment the event data. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Subscription:

Support cloud provider management platforms that wish to support persistent queries that could be used to generate periodic logs and reports.

Support data to describe event, report or log generation frequency (with associated filters) and possible storage or transmission destination(s). This includes subscription to real-time event feeds. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Event Target:

The resource or resources that were the intended targets of the event action [TOG-XDAS1]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

explicit qualifier:

A qualifier type declared separately from its usage on schema elements. CIM Infrastructure Specification
See also implicit qualifier

exposed elements of a class:

The set of schema elements exposed by a class (i.e., properties and methods) is the union of the set of elements defined in the class and the set of inherited elements that are not overridden in the class. Generic Operations Specification

exposed property or method:

A property or method that is available to clients using an adaptation. The set of properties or methods exposed by an adaptation is the union of all properties or methods defined in the adapted class and its superclasses. In the case where a property or method overrides a property or method defined in a superclass, the combined effects are exposed as a single property or method. Management Profile Specification Usage Guide

extension schema:

A schema not owned by the DMTF whose classes are derived from the classes in the CIM Schema. Common Information Model (CIM) Infrastructure

External Network Interface:

The interface of the Network Controller that provides connectivity to the external network infrastructure; also known as port. Network Controller Sideband Interface (NC-SI) Specification

Back to Top

F

feature (software):

A collection of software elements that performs a particular function or role of a software product. This level of granularity is intended to be meaningful to a consumer or user of the application to choose. This concept allows software products or application systems to be decomposed into units that have a meaning to users rather than units that reflect how the product or application was built (i.e., software elements). Software Identification and Entitlement Usage Metrics

feature:

A profile element that groups the decisions for the implementation of one or more profile elements into a single decision. This grouping is established by defining the implementation of other profile elements dependent on the implementation feature. Management Profile Specification Usage Guide

A property or method defined in a class.

A feature is exposed if it is available to consumers of a class. The set of features exposed by a class is the union of all features defined in the class and its ancestry. In the case where a feature overrides a feature, the combined effects are exposed as a single feature. Common Information Model (CIM) Infrastructure

fee schedule:

The Schedule of Fees contained in the Application Agreement. Common Diagnostics Model 1.0 Conformance Policy

filter collection:

An indication gate that may contain other indication gates such as indication filters or other filter collections. Indications Profile

filter query:

An expression that can be applied to a CIM instance. Filter Query Language

Filtering:

The process of selecting a subset of event records to be returned as the result of a query and is typically performed based upon selection criteria within the query. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

firmware:

One or more code images stored within a local memory structure (such as a Flash NVRAM) and accessible by a firmware device. Platform Level Data Model (PDLM) for Firmware Update Specification

firmware component:

A logical entity representing a functional portion of a firmware device. A firmware device may contain one or more firmware components each of which contains a code image that is represented by a component classification, component identifier, and version information. A firmware component may contain both an active and pending code image. Platform Level Data Model (PDLM) for Firmware Update Specification

firmware device (FD):

A PLDM endpoint (terminus) that contains one or more processor elements which execute firmware. The firmware device interacts with the update agent to perform firmware updates of its resident firmware components. Typically this may be a PCI I/O device. Platform Level Data Model (PDLM) for Firmware Update Specification

firmware package header:

A collection of fields that describe the contents of a firmware update package and for which firmware devices the firmware update package is applicable. Platform Level Data Model (PDLM) for Firmware Update Specification

firmware update baseline transfer size:

The minimum amount of data that can be requested by a firmware device in an individual command when transferring a component image. Platform Level Data Model (PDLM) for Firmware Update Specification

firmware update package:

A firmware package header describing the contents concatenated with one or more component images for one or more firmware devices. Platform Level Data Model (PDLM) for Firmware Update Specification

first-party authentication:

Authentication that is performed using services that execute local to the relying party. Simple Identity Management Profile

flavor:

Meta-data on a qualifier type that defines the rules for propagation, overriding and translatability of qualifiers For example, the Key qualifier has the flavors ToSubclass and DisableOverride, meaning that the qualifier value gets propagated to subclasses and these subclasses cannot override it. Common Information Model (CIM) Infrastructure

frame:

A data packet of fixed or variable length that has been encoded for digital transmission over a node-to-node link. Frame is used in references to IEEE 802.3 Frames. Packet is used in all other references. Network Controller Sideband Interface (NC-SI) Specification

Back to Top

G

gateway:

Interconnects networks with different network protocol technologies or separate IP address networks by performing the required protocol or IP address mapping conversions. Network Management - Tunnel Management Profile

generic operation:

Certain operations and semantics that are common among WBEM protocols. Generic Operations Specification

generic operations mapping:

A mapping of generic operations to the operations of some other protocol (e.g., WBEM operations) or to the calls of some API. Generic Operations Specification

geographic:

A placement policy referring to a geographic location (e.g., a country, a state, a province, a latlong). Open Virtualization Format Specification

geolocation | geo-location:

Refers to the identification of the geographical location of a resource or entity related to an event.

The identification of the physical location of a resource or player is important from a legal compliance perspective to ensure or audit compliance with the laws of various countries, regions, or logical boundaries that dictate where information must be stored. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

georouting | geo-routing:

Refers to the geographical tracking of an event from its origin through the various resources that participated in the event or the handling an event. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Global Element Declaration:

Element declaration in an XML Schema that places the element as an immediate child of the root element of the schema. WS-CIM Mapping Specification

global filter collection:

A filter collection that covers large sets of indications, such as all life cycle indications. Indications Profile

global indication filter:

An indication filter that covers large sets of indications, such as all alert indications. Indications Profile

Granted Privilege:

An instance of CIM_Privilege with the PrivilegeGranted property set to TRUE that represents the granted privilege of associated roles. Role Based Authorization Profile

guest software:

The software that runs inside a virtual system. Open Virtualization Format Specification

The software running on a virtual machine, stored on the virtual disks, that runs when a virtual machine is powered on. The guest is typically an operating system and some user-level applications and services. Software Identification and Entitlement Usage Metrics

Back to Top

H

host:

The computer system that is managed by a Redfish Service. Redfish Host Interface Specification

host interface:

A hardware interface and associated protocols that is used by software running locally on the host processors to access the hardware of a management subsystem within a managed system. MCTP Base Specification

host memory:

A contiguous extent of memory contained by the host system that may be allocated with either exclusive or shared access to a memory resource pool. Memory Resource Virtualization Profile

host processor:

Indicates the instance of CIM_Processor that represents the processor that hosts the processor core. CPU Profile

host processor resource:

Host processor resources are processor devices or computing resource contained by the host system that may be allocated with either exclusive or shared access to provide processing resources to a processor resource pool or a virtual system. Processor Resource Virtualization Profile

host resource:

A device or computing resource contained by the host system that may be allocated with either exclusive or shared access through the host system to provide resources to a resource pool or consumer. CPU Profile

host software:

The software running on the host computer system, include the operating system and its software components (such as drivers or applications), as well as preboot software, such as UEFI or BIOS drivers and applications. Redfish Host Interface Specification

host storage resource:

A storage resource that exists in scope of or is accessible by a host system. A host system may contain or have access to one or more storage resources that may be as a whole or partially allocated to virtual systems. Storage Resource Virtualization Profile

host system:

The system that contains the host resources that are subject to resource allocation. Memory Resource Virtualization Profile

The scoping system that contains Ethernet resources that may be allocated, virtualized, or both. Ethernet Port Resource Virtualization Profile ,

A system that contains resources that may be allocated or virtualized. CIM System Virtualization Model White Paper

HTTP basic authentication:

A simple authentication scheme for use by HTTP and HTTPS that is based on providing credentials in HTTP header fields. It is defined in RFC2617. CIM-RS Protocol Specification

HTTP content negotiation:

Negotiation between HTTP clients and HTTP servers to determine the format of the content transferred. When a client makes a request, they list acceptable response formats by specifying media types in an Accept header. Thus, the server is able to supply different representations of the same resource identified with the same resource identifier. A common example is GIF and PNG images. A browser that cannot display PNGs can be served GIFs based on the Accept header. In a RESTful system, the choice is more often between XML and JSON. For details, see RFC2616. Its use in CIM-RS is described in CIM-RS Protocol. CIM-RS White Paper

Method for selecting a representation of content in an HTTP response message when there are multiple representations available. It is defined in section 12 of RFC2616. CIM-RS Protocol

HTTP digest authentication:

An authentication scheme for use by HTTP and HTTPS that is based on verifying shared secrets that are not exchanged. It is defined in RFC2617. CIM-RS Protocol

HTTP entity body:

The payload within an HTTP message, as defined in section 7.2 of RFC2626. CIM-RS Protocol

HTTP entity-header field:

A header field that may be used in HTTP requests and HTTP response messages, specifying information that applies to the data in the entity body. Also called "HTTP entity-header". CIM-RS Protocol

HTTP extension-header field:

An entity-header field used for custom extensions to the standard set of header fields defined in RFC2616. Also called "HTTP extension-header". CIM-RS Protocol

HTTP general-header field:

A header field that may be used in HTTP requests and HTTP response messages, specifying information that applies to the HTTP message. Also called "HTTP general-header". CIM-RS Protocol

HTTP header field:

A named value used in the header of HTTP messages, as defined in section 4.2 of RFC2616. Also called "HTTP header". The specific types of header fields are general-header field, request-header field, response-header field, entity-header field, and extension-header field. CIM-RS Protocol

HTTP message:

An interaction between an HTTP client and an HTTP server (in any direction), as defined in section 4 of RFC2616. CIM-RS Protocol

HTTP method:

The type of interaction stated in HTTP requests, as defined in section 5.1.1 of RFC2616. CIM-RS Protocol

HTTP request message:

An HTTP message sent from an HTTP client to an HTTP server as defined in section 5 of RFC2616. Also called "HTTP request". CIM-RS Protocol

HTTP request-header field:

A header field that may be used in HTTP requests, specifying information that applies to the HTTP message. Also called "HTTP request-header". CIM-RS Protocol

HTTP response message:

An HTTP message sent from an HTTP server to an HTTP client, as defined in section 6 of RFC2616. Also called "HTTP response". CIM-RS Protocol

HTTP response-header field:

A header field that may be used in HTTP response messages, specifying information that applies to the HTTP message. Also called "HTTP response-header". CIM-RS Protocol

hypermedia API:

API that you navigate through URIs that a service returns. Redfish Specification

Back to Top

I

I2C:

The name of a multi-master, two-wire, serial bus originally developed by Philips Semiconductor. MCTP Packets and NC-SI over MCTP Overview

idempotent HTTP method:

An HTTP method with the behavior that (aside from error or expiration issues) the side-effects of N consecutive identical requests are the same as for a single one of those requests. RFC2616 requires the HTTP methods GET, HEAD, PUT and DELETE to be idempotent. HTTP methods that have no side effects (that is, safe methods) are inherently idempotent. For details, see RFC2616. CIM-RS White Paper

identity:

A name that is used to uniquely identify a user or person for the purposes of granting/assigning software use rights. Example might be the username “SmithJ”. Software Identification and Entitlement Usage Metrics

image:

Exact copy of the storage (disk) contents of a computing device for the purposes of recovery or provisioning of a duplicate system.

This encompasses the full instantiation of a deployed operating environment, all applications, data and configuration settings. Software Identification and Entitlement Usage Metrics

Immediate Power State Change:

Indicates the power state transition that will be initiated immediately. Power State Management Profile

implementation:

A realization of a model or metamodel. CIM Infrastructure Specification

A WBEM server that implements applicable portions of one or more profiles.

For example, in server-side infrastructures using CIM providers, implementation refers to the WBEM server and the set of providers that implement applicable portions of the set of profiles, that is, the implementation adaptation set. Management Profile Usage Guide

implementation adaptation:

An implementation-required adaptation that merges the requirements of its base adaptations and of other sources such as the schema definition of the adapted class, the operations specification or registry elements. Management Profile Usage Guide

implementation adaptation set:

The set of implementation adaptations required to be implemented as part of an implementation. Management Profile Usage Guide

Implementation Namespace:

A namespace in which the classes and instances that compose the advertised profile conformance are implemented. Profile Registration

A role of a CIM Namespace for the purpose of providing a place for CIM objects for which no specific namespace requirements are defined. The term is also used for namespaces that assume that role. Profile Registration Profile

A CIM Namespace for the main part of the implementation. Management Initiative Registration Profile

implementation-required:

A phrase indicating that the implementation of a profile or profile element is required within an implementation, including the case where an optional profile or profile element was selected to be implemented. Management Profile Usage Guide

implementation type:

A type assigned to an adaptation that details how the adaptation is to be implemented. Management Profile Usage Guide

Implicit Command Target:

Target acted upon that is inherent to the command being executed.

The command does not act upon either the Current Default Target or a target specified as part of the command. The cd command is an example of a command that acts upon an Implicit Command Target. Server Management Command Line Protocol Specification (SM CLP)

implicit qualifier:

A qualifier type declared as part of the declaration of a schema element. CIM Infrastructure Specification
See also explicit qualifier.

incompatibility:

A change that breaks backward compatibility. Management Profile Usage Guide

In Development:

Period during which a document is being crafted by the Editing Body. DMTF Process for Working Bodies

indication:

A special kind of class that expresses the notification about an event that occurred For a complete definition, see CIM Infrastructure Specification. In addition, the indication may only represent an aspect of the event and not the entire event. Multiple indications may be communicated for a specific event. Indications Profile

indication adaptation:

An adaptation of an indication class. Management Profile Usage Guide

indication delivery:

The process of delivering indications from an implementation to a listener. Indications Profile

indication filter:

A logical construct that specifies a filter on indications, used to control whether indications are delivered to a subscriber.

An indication gate whose coverage is defined through a query statement. Indications Profile

indication gate:

A managed element that filters indications such that only indications within its coverage pass. Indication gates can serve as targets for subscriptions, and control which indications are delivered to subscribed listeners. Indications Profile

indication generation:

The process of creating an indication as the event that the indication is designed to report occurs. Indications Profile

indication-generation requirement:

A requirement that states one or more events, each of which individually requires the generation of a particular indication. Management Profile Usage Guide

indication origin:

The namespace out of that the indication originates. Indications Profile

indication service:

A functionality of a WBEM server for indication related processing, including handling of subscriptions and delivery of indications to a WBEM listener. Indications Profile

indication-specific indication filter:

A static indication filter that covers a particular indication specified in a profile. Indications Profile

indication system:

A system that hosts a WBEM server with one or more indication services. Indications Profile

Infrastructure as a Service (IaaS):

A cloud computing service model defined in section 2 of the NIST Definition of Cloud Computing [SP800-145]. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

inheritance:

A relationship between a more general class and a more specific class.

An instance of the specific class is also an instance of the general class. The specific class inherits the features of the general class. In an inheritance relationship, the specific class is termed "subclass" and the general class is termed "superclass".

For example, if a class ACME_Modem is a subclass of a class ACME_Device, any ACME_Modem instance is also an ACME_Device instance. CIM Infrastructure Specification

initiative, management initiative:

A named and versioned amount of management functionality with conformance requirements. The conformance requirements for implementing a management initiative are described in an initiative specification, based on management profiles and other specifications. Initiatives may be defined by DMTF, other standards organizations, or vendors. An example for a management initiative defined by DMTF is DASH. Management Initiative Registration Profile

initiative specification:

A specification defining conformance requirements for implementing an initiative. Also called "initiative wrapper specification". An example for an initiative specification is DSP0232, defining conformance requirements for the DASH management initiative. Management Initiative Registration Profile

initiator port:

A port that acts as the source for a data exchange operation. Storage Resource Virtualization Profile

input value requirement:

A requirement, stated as part of a property requirement, or part of a parameter requirement within a method requirement, that the implementation accept a specific input value. Management Profile Usage Guide

installation dependency:

A software image that needs to be installed before installing the target Software Identity. Software Inventory Profile

installed software:

Software that is installed on any managed element in the scope of a system. Software Inventory Profile

instance:

The run-time realization of a class from a model. CIM Infrastructure Specification

instance declaration:

The definition (or specification) of an instance by means of specifying a creation class for the instance and a set of property values.

For example, an instance that is accessible through a CIM server can be retrieved by a CIM client. What the CIM client receives as a result, is actually an instance declaration. The instance itself may already have changed its property values by the time the CIM client receives the instance declaration. Similarly, when an instance that is accessible through a CIM server is being modified through a CIM operation, one input parameter might be an instance declaration that specifies the intended new property values for the instance. CIM Infrastructure Specification

instance path:

A special kind of object path addressing an instance that is accessible through a CIM server. CIM Infrastructure Specification ,

A special kind of object path addressing an instance that is accessible through a WBEM server. Generic Operations Specification

instance requirement:

A requirement that defines how (and in some cases also under which conditions) managed objects are to be represented by adaptation instances. Management Profile Usage Guide

instance (software):

An installed copy of a software product or application whose presence can be identified through manual or automated means. Software Identification and Entitlement Usage Metrics

instantaneous metrics:

Metrics that apply to a particular point in time.

An example of an instantaneous metric is the amount of memory currently allocated to a virtual server. Base Metrics Profile

integrated controller:

A Network Controller device that supports two or more channels for the NC-SI that share a common NC-SI physical interface (for example, a Network Controller that has two or more physical network ports and a single NC-SI bus connection). Network Controller Sideband Interface (NC-SI) Specification

Intelligent Platform Management Bus (IPMB):

Name for the architecture, protocol, and implementation of an I2C bus that provides a communications path between "management controllers" in IPMI -based systems. MCTP Base Specification

Intelligent Platform Management Interface (IPMI):

A set of specifications defining interfaces and protocols originally developed for server platform management by the IPMI Promoters Group: Intel, Dell, HP, and NEC. MCTP Base Specification

interface:

An abstract element of virtual hardware that enables connection to a Network via Endpoints. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

Intermediate Entry Point Structure (IEPS)

Internal Host Interface:

The interface of the Network Controller that provides connectivity to the host operating system running on the platform. Network Controller Sideband Interface (NC-SI) Specification

Internet media type:

A string identification for representation formats in Internet protocols. Originally defined for email attachments and termed "MIME type". Because the CIM-RS protocol is based on HTTP, it uses the definition of media types from section 3.7 of RFC2616. CIM-RS White Paper

Interoperability:

ISO/TR 16056-1:2004

The ability of two or more systems (computers, communication devices, networks, software, and other information technology components) to interact with one another and exchange information according to a prescribed method in order to achieve predictable results. Profile to Enable Automated Deployment of OVF Packages

Interop Namespace:

A namespace in which the CIM_RegisteredProfile instances are instantiated in order to advertise the availability of a conformant implementation of a profile.

A role of a CIM namespace for the purpose of providing a common and well-known place for clients to discover modeled entities, such as the profiles to which an implementation advertises conformance. The term is also used for namespaces that assume that role. Profile Registration Profile
See also Implementation Namespace.

interpretation (INT):

Decision made by the DMTF that elaborates or refines the meaning of a Conformance Requirement. An Interpretation is one possible outcome of an Issue Report. Common Diagnostics Model 1.0 Conformance Policy

interval metrics:

Metrics that apply to a time interval. An example of an interval metric is the average CPU utilization of a server over the past hour. Base Metrics Profile

IP encapsulation:

A method of creating IP packets in which logically separate networks are abstracted from their underlying structures by inclusion of an inside network packet within a higher level network packet. Network Management - Tunnel Management Profile

IP gateway:

Uses the IP protocol as an underlay protocol to tunnel non-routable network segments, allowing the traffic to be routed on an IP network. Network Management - Tunnel Management Profile

IP Solicitation:

A notification to membership, consistent with the DMTF Patent Policy that solicits response of essential patent claims that relate to the subject document. DMTF Process for Working Bodies

isolation:

The set of behaviors that describe how the execution of an operation affects the execution of another, concurrent operation. Generic Operations Specification

Issue Report (IR):

A formal written report requesting clarification of or asking questions about the intent or correctness of a Conformance Requirement, the Conformance Test Suite, or the Conformance Program itself. A written question along with any supporting details and/or documents addressed to the Program Administrator requesting clarification, intent, or correctness of a Specification, a Test Suite, or the Conformance Program Policies and Procedures. Common Diagnostics Model 1.0 Conformance Policy ; DASH 2.0 Conformance Program Policies and Procedures

IT service:

A set of related functions provided by IT systems in support of one or more business areas, which in turn may be made up of software, hardware and communications facilities, perceived by the customer as a coherent and self-contained entity.

An IT service may range from access to a single application, such as a general ledger system, to a complex set of facilities including many applications, as well as office automation that might be spread across a number of hardware and software platforms. Software Identification and Entitlement Usage Metrics

Back to Top

J

job:

A task that takes some time to execute. Job Control Profile

Back to Top

K

key, key property:

A property whose value uniquely identifies an instance within some scope of uniqueness.

The key of an instance is synonymous with the model path of the instance (class name, plus set of key property name/value pairs). The key of a non-embedded instance is required to be unique in the namespace in which it is registered. The key properties of a class are indicated by the Key qualifier. Also, shorthand for the term "key property". CIM Infrastructure Specification

keyword:

A text-string token that is recognized and reserved by the CLP to have a specified meaning when used in command output and input. Server Management Command Line Protocol Specification (SM CLP)

KVM console flow:

A KVM console flow is the bidirectional KVM console stream which original flows to the Original Destination. The KVM console flow may be redirected to a new KVM Console Flow destination, which modeled as an instance of CIM_ProtocolEndpoint. KVM Redirection Profile

KVM redirection:

Composed of an instance of CIM_RedirectionService, an instance of CIM_KVMRedirectionSAP and the instance of the CIM_ServiceAccessBySAP between the two. KVM Redirection Profile

KVM redirection session:

The instance of CIM_KVMRedirectionSAP which is part of a KVM Redirection. KVM Redirection Profile

KVM redirection service:

The instance of CIM_RedirectionService which is part of a KVM Redirection. KVM Redirection Profile

Back to Top

L

launch in context:

The act of invoking a service with contextual information. Launch in Context Profile

launch point:

Information within a managed system that provides information about a service that can be invoked. Launch in Context Profile

license (software):

Legal rights to use software in accordance with terms and conditions specified by the software copyright owner. Software Identification and Entitlement Usage Metrics

licensee (software):

Legal entity, typically a person or organization, contractually bound to a given software license agreement that provides rights to use the associated software in accordance with the terms and conditions as specified by the copyright owner. Software Identification and Entitlement Usage Metrics

lifecycle indication:

An indication indicating an event related to the lifecycle of CIM instances or CIM classes. Indications Profile

listener:

A WBEM listener that implements applicable portions of this profile. Indications Profile

listener destination:

An entity that maintains a reference to a listener within an implementation. Indications Profile

listening port:

A TCP/IP port that the telnet service is bound to and listening for incoming connection requests. Telnet Service Profile

Local Addressing Service:

The entity responsible for discovering, enumerating, and determining the addresses of Managed Elements and Associations within the Admin Domain. Server Management Command Line Protocol Specification (SM CLP)

Log:

See definition for Event Log. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

logical disk:

The instantiation of allocated host resources that is exposed to a virtual system through a storage device; the result of a storage resource allocation based on a storage resource allocation request. Storage Resource Virtualization Profile

logical PCI device:

Indicates a PCI device that is represented by a PCI bus number, PCI device number, and PCI function number. PCI Device Profile

logs collection:

CIM_ConcreteCollection instance for instances of the CIM_RecordLog class. SMASH Collections Profile

long-term monitoring:

The process in which metric values are captured during an interval. Base Metrics Profile

Back to Top

M

MAC:

Link layer of the OSI protocol model. Ethernet NIC Diagnostics Profile

Major Schema:

The primary schema defining the format of a collection of data, usually a published standard Redfish schema. Platform Level Data Model (PLDM) for Redfish Device Enablement

Manageability Access Point (MAP):

A service of a system that provides management in accordance with specifications of the DMTF System Management Architecture for Server Hardware. System Management Architecture for Server Hardware Whitepaper

managed device:

Refers to a device that is typically implemented using a microcontroller and accessed through a messaging protocol and is used for accessing one or more management parameters. Management parameter access provided by a managed device is typically accomplished using an abstracted interface and data model rather than through direct "register level" accesses. A managed device responds to management requests, but does not initiate or aggregate management operations except in conjunction with a management controller (that is, it is a satellite device that is subsidiary to one or more management controllers). MCTP Base Specification

managed element (ME):

An instance of CIM_ManagedElement that represents a managed element in the scope of a system.

The finest granularity of addressing, which can be the target of commands or messages, or a collection thereof. System Management Architecture for Server Hardware Whitepaper

Managed Element Access Method:

The method by which a Managed Element performs a unit of work. System Management Architecture for Server Hardware Whitepaper

managed entity:

The physical or logical entity that is being managed through management parameters. Examples of physical entities include fans, processors, power supplies, circuit cards, chassis, and so on. Examples of logical entities include virtual processors, cooling domains, system security states, and so on. Management Component Transport Protocol (MCTP) Base Specification

managed environment:

A concrete occurrence of the management domain. A managed environment is composed of managed objects. Management Profile Usage Guide

managed object:

A physical entity, a service, or other kind of resource that exists independently of its use in management. Managed objects exist in managed environments. Management Profile Usage Guide

A resource in the managed environment of which an aspect is modeled by a class. An instance of that class represents that aspect of the represented resource. For example, a network interface card is a managed object whose logical function may be modeled as a class ACME_NetworkPort. Common Information Model (CIM) Infrastructure

Managed Object Format (MOF):

A schema description language used for specifying the interface of managed resources (storage, networking, compute, software) conformant with the CIM meta-model defined in DSP0004. DMTF Process for Working Bodies

An IDL based language, defined by the DMTF, expressing the structure, behavior, and semantics of a CIM class and its instances. WS-CIM Mapping Specification

A DMTF defined language used to create CIM metamodel conformant representations of model elements. The Managed Object Format (MOF) is an Interface Definition Language (IDL) based on ISO/IEC 14750:1999. ANNEX A of the CIM Infrastructure specification provides a complete description, of the MOF language. CIMI-CIM Specification

managed object type:

A conceptual generalization or type of managed object. Management Profile Usage Guide

managed resource:

A resource in the managed environment. NOTE This was called “managed object” in CIM v2. Common Information Model (CIM) Metamodel

An entity that can be of interest to an administrator. It may be a physical object, such as a laptop computer or a printer, or an abstract entity, such as a service. Web Services for Management (WS Management)

managed system:

A collection of Managed Elements that compose a computer system for which the MAP has management responsibilities. System Management Architecture for Server Hardware Whitepaper

In the context of this specification, a managed system is a system that provides information or status, or is controllable, via a Redfish-defined interface. Redfish Scalable Platforms Management API Specification

Management Component Transport Protocol (MCTP):

See Management Component Transport Protocol (MCTP) Base Specification

Management Controller (MC):

A microcontroller or processor that aggregates management parameters from one or more management devices and makes access to those parameters available to local or remote software, or to other management controllers, through one or more management data models. Management controllers may also interpret and process management-related data, and initiate management-related actions on management devices. While a native data model is defined for PMCI, it is designed to be capable of supporting other data models, such as CIM, IPMI, and vendor-specific data models. The microcontroller or processor that serves as a management controller can also incorporate the functions of a management device. Management Component Transport Protocol (MCTP) Base Specification

management device:

Any physical device that provides protocol terminus for accessing one or more management parameters. A management device responds to management requests, but does not initiate or aggregate management operations except in conjunction with a management controller (that is, it is a satellite device that is subsidiary to one or more management controllers). An example of a simple management device would be a temperature sensor chip. A management controller that has I/O pins or built-in analog-to-digital converters that monitor state and voltages for a managed entity would also be a management device. Management Component Transport Protocol (MCTP) Base Specification

management domain:

Area of work or field of activity with common management requirements, common terminology, and related management functionality. Management Profile Specification Usage Guide

management initiative, initiative:

A named and versioned amount of management functionality with conformance requirements. The conformance requirements for implementing a management initiative are described in an initiative specification, based on management profiles and other specifications. Initiatives may be defined by DMTF, other standards organizations, or vendors. An example for a management initiative defined by DMTF is DASH. Management Initiative Registration Profile

management parameter:

A particular datum representing a characteristic, capability, status, or control point associated with a managed entity. Example management parameters include temperature, speed, volts, on/off, link state, uncorrectable error count, device power state, and so on. Management Component Transport Protocol (MCTP) Base Specification

management profile:

A profile referenced with the mandatory requirement level definition of a management interface between a WBEM server and a WBEM client or a WBEM listener. Management Profile Usage Guide

management profile specification:

A specification document that contains the textual specification of one or more management profiles and, optionally, content that does not represent a management. Management Profile Usage Guide

Management Service Core:

The logical entity that contains the core services set of the MAP. Server Management Command Line Protocol Specification (SM CLP)

Managing Service:

The instance of CIM_CertificateManagementService that is managing a given PKI Credential Instance The instance of CIM_CertificateManagementService is associated to the Container Keystore of the given PKI Credential Instance through the CIM_ServiceAffectsElement association. Certificate Management Profile

mandatory:

A requirement level indicating that the subject profile unconditionally requires the implementation of the designated profile element. Management Profile Usage Guide

Indicates requirements to be followed strictly to conform to the document and from which no deviation is permitted. Management Component Transport Protocol (MCTP) Base Specification

mandatory profile:

A profile referenced with the mandatory requirement level. Management Profile Usage Guide

Mantis:

A comment-tracking tool provided by the DMTF for the use of its members in tracking changes to specific documents. DMTF Process for Working Bodies

match:

A keyword indicating that the values of a property or parameter match the values specified by a pattern. Management Profile Usage Guide

may:

Indicates a course of action permissible within the limits of the document. Profile Registration

MCTP bridge:

An MCTP endpoint that can route MCTP messages not destined for itself that it receives on one interconnect onto another without interpreting them. The ingress and egress media at the bridge may be either homogeneous or heterogeneous. Also referred to as a "bridge". MCTP Base Specification

MCTP bus owner:

Responsible for EID assignment for MCTP or translation on the buses that it is a master of. The MCTP bus owner may also be responsible for physical address assignment. For example, for SMBus bus segments, the MCTP bus owner is also the ARP master. This means the bus owner assigns dynamic SMBus addresses to those devices requiring it. MCTP Base Specification

MCTP control command:

Commands defined under the MCTP control message type that are used for the initialization and management of MCTP communications (for example, commands to assign EIDs, discover device MCTP capabilities, and so on). MCTP Base Specification

MCTP endpoint:

An MCTP communication terminus. An MCTP endpoint is a terminus or origin of MCTP packets or messages. That is, the combined functionality within a physical device that communicates using the MCTP transport protocol and handles MCTP control commands. This includes MCTP-capable management controllers and management devices. Also referred to as endpoint. MCTP Base Specification

MCTP endpoint ID:

The logical address used to route MCTP messages to a specific MCTP endpoint. A numeric handle (logical address) that uniquely identifies a particular MCTP endpoint within a system for MCTP communication and message routing purposes. Endpoint IDs are unique among MCTP endpoints that comprise an MCTP communication network within a system. MCTP EIDs are only unique within a particular MCTP network. That is, they can be duplicated or overlap from one MCTP network to the next. Also referred to as endpoint ID and abbreviated EID. MCTP Base Specification

MCTP host interface:

A host interface that enables host software to locally access an MCTP Network in the managed system. MCTP Base Specification

MCTP managed device:

A managed device that is an MCTP endpoint. Unless otherwise indicated, the term "managed device" refers to an "MCTP managed device" in this document. Management Component Transport Protocol (MCTP) Base Specification

MCTP management controller:

A management controller that is an MCTP endpoint. MCTP Base Specification

MCTP management device:

A management device that is an MCTP endpoint. MCTP Base Specification

MCTP message:

A unit of communication based on the message type that is relayed through the MCTP Network using one or more MCTP packets. MCTP Base Specification

MCTP network:

A collection of MCTP endpoints that communicate using MCTP and share a common MCTP endpoint ID space. MCTP Base Specification

MCTP network ID:

A unique identifier to distinguish each independent MCTP network within a platform. MCTP Base Specification

MCTP packet:

The unit of data transfer used for MCTP communication on a given physical medium. MCTP Base Specification

MCTP PCIe Endpoint:

A PCIe endpoint on which MCTP PCIe VDM communication is supported. MCTP Base Specification

MCTP packet payload:

Refers to the portion of the message body of an MCTP message that is carried in a single MCTP packet. MCTP Base Specification

measured resource:

A managed object being measured, which is the resource to which base metric value instances are associated. Base Metrics Profile

media redirection:

An arrangement that encompasses an instance of CIM_RedirectionService and an instance of CIM_MediaRedirectionSAP that are joined by a CIM_ServiceAccessBySAP association. Media Redirection Profile

media redirection SAP:

The Service Access Point for a Media Redirection Sesson as modeled by an instance of CIM_MediaRedirectionSAP that is part of a Media Redirection. Media Redirection Profile

media redirection service:

The instance of CIM_RedirectionServiceRedirectionService that is part of a Media Redirection. Media Redirection Profile

media redirection session:

The context and elements of a particular Media Redirection SAP as modeled by an instance of CIM_MediaRedirectionSAP. Media Redirection Profile

Media Storage Device (MSD)

medium-specific reset:

A process whereby a firmware device is reset via the specific type of interface that the PLDM terminus within the firmware device uses to communicate. For example, a PCI device would have a medium-specific reset via a PCI-reset signal. The firmware device will activate any pending firmware component images which indicated a medium-specific reset as its activation method. Platform Level Data Model (PDLM) for Firmware Update Specification

member:

A Member is a single resource instance contained in a Resource Collection. Redfish Scalable Platforms Management API Specification

Member Company:

A corporation or association that allows its employees or representatives to subscribe to the email lists, participate in list discussions, attend and participate in meetings, and make contributions to the DMTF. The process for becoming a Member Company can be found at http://www.dmtf.org/join/company. DMTF Process for Working Bodies

memory composition:

The aggregation of memory extents into an encompassing memory extent. Memory Resource Virtualization Profile

memory extent:

Used generically to indicate a range of memory addresses that can participate in management operations. Multi-type System Memory Profile

memory module:

Non-technology specific term for a circuit board hosting memory integrated circuits. Multi-type System Memory Profile

memory resource allocation:

The allocation of memory from a memory resource pool to a virtual system. Memory Resource Virtualization Profile

memory resource allocation request:

A request for a memory resource allocation. Memory Resource Virtualization Profile

memory resource pool:

A resource pool that represents memory available for memory resource allocation. Memory Resource Virtualization Profile

memory resource pool configuration service:

A configuration service that supports the addition or removal of host memory to or from a memory resource pool, and the creation or deletion of concrete subpools of a memory resource pool. Memory Resource Virtualization Profile

message:

See MCTP message.

A complete request or response, formatted in HTTP/HTTPS. The protocol, based on REST, is a request/response protocol where every Request should result in a Response. Redfish Scalable Platforms Management API Specification

message assembly:

The process of receiving and linking together two or more MCTP packets that belong to a given MCTP message to allow the entire message header and message data (payload) to be extracted. Management Component Transport Protocol (MCTP) Base Specification

message body:

The portion of an MCTP message that carries the message type field and any message type-specific data associated with the message. An MCTP message spans multiple MCTP packets when the message body needs is larger than what can fit in a single MCTP packet. Thus, the message body portion of an MCTP message can span multiple MCTP packets. Management Component Transport Protocol (MCTP) Base Specification

message confidentiality:

A quality of a message that prevents anyone but the intended receiver(s) from viewing its contents. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

message disassembly:

The process of taking an MCTP message where the message's header and data (payload) cannot be carried in a single MCTP packet and generating the sequence of two or more packets required to deliver that message content within the MCTP network. Management Component Transport Protocol (MCTP) Base Specification

message integrity:

A quality of a message that allows a receiver of that message to determine whether the contents of the message have been altered since its creation. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

message originator:

The original transmitter (source) of a message targeted to a particular message terminus. Management Component Transport Protocol (MCTP) Base Specification

message registry:

A published registry of messages formatted as defined in Message Registry XML Schema. Management Profile Usage Guide

message terminus:

The name for a triplet of fields called the MCTP Source Endpoint ID, Tag Owner bit value, and Message Tag value. Together, these fields identify the packets for an MCTP message within an MCTP network for the purpose of message assembly. The message terminus itself can be thought of as identifying a set of resources within the recipient endpoint that is handling the assembly of a particular message. Management Component Transport Protocol (MCTP) Base Specification

metadata:

Information that describes data of interest, such as its type format, length in bytes, or encoding method. Platform Level Data Model (PLDM) for Redfish Device Enablement

meta-element:

An entity in a meta-model.

For example, the CIM meta-model defines a meta-element named "Property" that defines the concept of a structural data item in an object. Specific properties (e.g., property P1) can be thought of as being instances of the meta-element named "Property". CIM Infrastructure Specification

meta-model:

A set of meta-elements and their meta-relationships that expresses the types of things that can be defined in a schema.

For example, the CIM meta-model includes the meta-elements named "Property" and "Class" which have a meta-relationship such that a Class owns zero or more Properties. CIM Infrastructure Specification

meta-relationship:

A relationship between two entities in a meta-model

For example, the CIM meta-model defines a meta-relationship by which the meta-element named "Property" is aggregated into the meta-element named "Class". CIM Infrastructure Specification

meta-schema:

A synonym for meta-model. CIM Infrastructure Specification

method, CIM method:

A behavioral feature of a class.

Methods can be invoked to produce the associated behavior.

In a schema, methods are special kinds of schema elements. Method name, return value, parameters and other information about the method are defined in the class declaration.

In the CIM meta-model, methods are represented by the meta-element named "Method". CIM Infrastructure Specification

method invocation link:

The resource identifier of a (static or instance) method invocation resource. CIM-RS Protocol

method requirement:

A requirement stated as part of a class adaptation that defines requirements and constraints on a metric defined in a metric registry. Management Profile Usage Guide

metric registry:

A published registry of metric definitions, and optionally statistics definitions, formatted as defined in Standard Metrics Schema. Management Profile Usage Guide

metric requirement:

A requirement stated as part of a class adaptation that defines requirements and constraints on a metric defined in a metric registry. Management Profile Usage Guide

Model:

A set of conceptual elements and the relationships between them that collectively define the semantics, behavior and state of some thing. DMTF Process for Working Bodies

A set of entities and the relationships between them that define the semantics, behavior and state of that set. CIM Infrastructure Specification

model path:

The part of an object path that identifies the object within the namespace. CIM Infrastructure Specification

Modified Role:

An instance of CIM_Role that is referenced by the Role parameter of the ModifyRole( ) method. Role Based Authorization Profile

modular enclosure:

The physical packaging of a modular system. Modular Systems Profile

MOF compilation unit:

Refers to a set of MOF files, which includes the files explicitly listed as the input to the MOF compiler and the files directly or transitively included from those input files using the include pragma compiler directive. Modular Systems Profile

MOF compiler:

A MOF compiler takes as input a compilation unit, and in addition can also accept as input a representation of previously compiled types and qualifiers.

A MOF compiler transforms types defined in the compilation unit into another representation, like schema repository entries or provider skeletons.

A MOF compiler shall verify the consistency of its input; the compiler input shall include definitions of all types that are used by other types, and all super-types of the defined and used types. Managed Object Format (MOF)

MOF file:

Refers to a document with the content that conforms to the MOF syntax described by this specification. Managed Object Format (MOF)

MOF grammar:

Refers to the MOF language syntax description included in this document. The MOF grammar is specified using the ABNF. Managed Object Format (MOF)

MOF Schema:

A Schema based or derived from a MOF definition. This includes the CIM Schema, PRS Schema and any additional Schema based or derived from MOF created by the DMTF or Alliance Partners. DMTF Process for Working Bodies

Monitoring Member:

Member Company that has access to content and communications on the member-only section of the DMTF web site but does not participate on any Committees, Subcommittees or Working Groups. DMTF Process for Working Bodies

Multi-drop:

Refers to the situation in which multiple physical communication devices share an electrically common bus and a single device acts as the master of the bus and communicates with multiple “slave” or “target” devices.

Related to NC-SI, a Management Controller serves the role of the master, and the Network Controllers are the target devices. Network Controller Sideband Interface (NC-SI) Specification

multiplicity:

The allowable range for the number of instances that may be associated to an instance.

The multiplicity of an association end is the allowable range for the number of instances that may be associated to each instance referenced by each of the other ends of the association. The multiplicity is defined on a reference using the Min and Max qualifiers. CIM Infrastructure Specification

Back to Top

N

name:

An identifier that each element or meta-element has in order to identify it in some scope. CIM Infrastructure Specification

named profile element:

A profile element that is assigned a name with profile name scope. Management Profile Usage Guide

namespace, CIM namespace:

A special kind of object that is accessible through a CIM server that represents a naming space for classes, instances and qualifier types. CIM Infrastructure Specification

namespace path:

A special kind of object path addressing a namespace that is accessible through a CIM server.

Also, the part of an instance path, class path and qualifier type path that addresses the namespace.

A special kind of object path addressing a CIM namespace that is accessible through a WBEM server. CIM Infrastructure Specification

navigation property:

A property in the REST representation of an instance that is not declared in its class but is included in the representation to provide for navigation to related instances. CIM-RS Protocol

NC-SI RX:

The direction of traffic on the NC-SI from the Network Controller to the Management Controller. Network Controller Sideband Interface (NC-SI) Specification

NC-SI TX:

The direction of traffic on the NC-SI to the Network Controller from the Management Controller. Network Controller Sideband Interface (NC-SI) Specification

network:

A construct that supports communications between elements within a Cloud using one or more protocol specific Segments that support addressable Endpoints. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

Network Controller (NC):

The component within a system that is responsible for providing connectivity to an external Ethernet network. Network Controller Sideband Interface (NC-SI) Specification

Network Controller Sideband Interface (NC-SI):

The interface of the Network Controller that provides network connectivity to a Management Controller; also shown as Sideband Interface or NC-SI as appropriate in the context. Network Controller Sideband Interface (NC-SI) Specification

network overlay/underlay:

Network overlay/underlay allows encapsulation of one packet into another using a "packet-in-a-packet" technique. The encapsulated packet is forwarded to an endpoint where it is decapsulated. Network overlay/underlay is commonly used to (a) support secure multitenancy, and (b) extend one network across another. Network Management - Tunnel Management Profile

next boot configuration:

The instance of CIM_BootConfigSetting that will be used during the next boot of the Boot Configurable System. Boot Control Profile

next single use boot configuration:

The instance of CIM_BootConfigSetting that will only be used during the next boot of the Boot Configurable System and then not used again. Boot Control Profile

nibble:

The computer term for a four-bit aggregation, or half of a byte. MCTP Base Specification

Non-addressing Association:

An association instance that is not used by the MAP in constructing the UFiP to any instances referenced by the association instance. Server Management Command Line Protocol Specification (SM CLP)

Normalization Form C:

A normalization form for UCS characters that avoids the use of combining marks where possible and that allows comparing UCS character strings on a per-code-point basis. It is defined in The Unicode Standard, Annex #15. CIM-RS Protocol

not next boot configuration:

An instance of CIM_BootConfigSetting that will not be used during the next boot. Boot Control Profile

not recommended:

Indicates that valid reasons may exist in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and carefully weighed before implementing any behavior described with this label. Management Component Transport Protocol (MCTP) Base Specification

Null:

A state of a typed element that does not have a value. Common Information Model (CIM) Metamodel

numeric character reference:

An escaped UCS character, as defined in clause 4.1 of the W3C XML specification as character reference, using the hexadecimal or decimal representation of its UCS code point. Examples are " " for the carriage return character or "A" for the character "A". Representation of CIM in XML

Back to Top

O

object path:

The address of an object that is accessible through a CIM server. Generic Operations Specification

obsolete:

Indicates that an item was defined in prior specifications but has been removed from this specification. Management Component Transport Protocol (MCTP) Base Specification

OData:

The Open Data Protocol, as defined in OData-Protocol. Redfish Scalable Platforms Management API Specification

The Open Data protocol, a source of annotations in Redfish, as defined by OASIS. Platform Level Data Model (PLDM) for Redfish Device Enablement

OData Service Document:

The name for a resource that provides information about the Service Root. The Service Document provides a standard format for enumerating the resources exposed by the service that enables generic hypermedia-driven OData clients to navigate to the resources of the Redfish Service. Redfish Scalable Platforms Management API Specification

OEM extension:

Any manufacturer-specific addition to major schema. Platform Level Data Model (PLDM) for Redfish Device Enablement

OEM Properties:

Properties added to instances of a class by an OEM vendor. Server Management Command Line Protocol Specification (SM CLP)

OEM Target:

A Managed Element or Association whose properties, behavior, UFcT, and so on are outside the scope of this specification and are vendor dependent. Server Management Command Line Protocol Specification (SM CLP)

OEM Verbs:

Verbs defined by an OEM vendor that are outside the scope of this specification. Server Management Command Line Protocol Specification (SM CLP)

online monitoring:

The process in which metric values (typically interval metrics) are gathered asynchronously to a request from the instrumentation or reporting layer. Base Metrics Profile

Open Virtualization Format (OVF)

Operation:

An identifiable activity of a MAP. Server Management Command Line Protocol Specification (SM CLP)

The HTTP request methods that map generic CRUD operations. These are POST, GET, PUT/PATCH, HEAD and DELETE. Redfish Scalable Platforms Management API Specification

Operation Request Message:

An XML document that is loosely valid with respect to the CIM XML DTD and that contains a subelement under the root node that has a or subelement under this subelement. CIM Operations over HTTP

operation requirement:

A requirement stated as part of a class adaptation that defines requirements and constraints on an operation defined in an operations specification. Management Profile Usage Guide

operations specification:

A specification that specifies operations, their semantics and the model and behavior associated to them. Management Profile Usage Guide

option:

A term of the Command Line that selects a particular behavior of a command verb. Server Management Command Line Protocol Specification (SM CLP)

option argument:

Input data passed to the command verb in relation to an option that selects a particular value for that option. Server Management Command Line Protocol Specification (SM CLP)

optional:

Indicates a course of action permissible within the limits of the document.

A requirement level indicating that the subject profile leaves the decision to implement the designated profile element to the implementation. Management Profile Specification Usage Guide

optional profile:

A used profile that is referenced by a profile reference with the optional requirement level. Management Profile Specification Usage Guide

ordinary class:

A class that is not an association class or an indication class. Management Profile Specification Usage Guide

A class that is neither an association class nor an indication class. CIMI-CIM Specification

organization:

Refers to a consortium, standards group, company, or business entity creating a management profile. Management Profile Specification Usage Guide

Consortium, standards group, or company creating a DMTF profile specification. Job Control Profile

original destination:

The destination of a Text Console Flow before being redirected, modeled as an instance of CIM_LogicalDevice, such as a serial port. Text Console Redirection Profile

The destination of a KVM console flow prior to it being redirected.

The Original Destination is modeled as instances of CIM_Keyboard, CIM_DisplayController and CIM_PointingDevice in this document but could be potentially another type of logical device. KVM Redirection Profile

Out-of-Band:

Manageability capabilities that operate with hardware resources and components that are independent of operating systems control. MCTP Packets and NC-SI over MCTP Overview

overlay network/customer:

A network containing non-encapsulated network traffic from the perspective of the encapsulation gateways specified in this profile. Network Management - Tunnel Management Profile

override:

A relationship between like-named elements of the same type of meta-element in an inheritance hierarchy, where the overriding element in a subclass redefines the overridden element in a superclass.

The purpose of an override relationship is to refine the definition of an element in a subclass.

For example, a class ACME_Device may define a string typed property Status that may have the values "powersave", "on", or "off". A class ACME_Modem, subclass of ACME_Device, may override the Status property to have only the values "on" or "off", but not "powersave". Common Information Model (CIM) Infrastructure

OVF descriptor:

An XML file that validates to DSP8023 and provides the information needed to deploy the OVF package. Open Virtualization Format Specification

OVF package:

A single compressed file or a set of files that contains the OVF descriptor file and may contain associated virtual disks, operational metadata, and other files. Open Virtualization Format Specification

OVF Portability:

The ability to export a virtual system from one author function to be imported into another author function. Profile to Enable Automated Deployment of OVF Packages

Owned Credential Store:

A credential store supported by a service that stores credentials used by the service to identify itself to clients.

Such a credential store is represented by CIM_CredentialStore with the Usage property set to 2 (Owned). Credential Management Profile

owning system:

An instance of CIM_ComputerSystem that represents the system that owns the shared resource. Shared Device Management Profile

Back to Top

P

package:

One or more NC-SI channels in a Network Controller that share a common set of electrical buffers and common electrical buffer controls for the NC-SI bus.

Typically, a single, logical NC-SI package exists for a single physical Network Controller package (chip or module). However, this specification allows a single physical chip or module to hold multiple NC-SI logical packages. Network Controller Sideband Interface (NC-SI) Specification

packet:

A formatted block of information carried by a computer network. Frame is used in references to IEEE 802.3 Frames. Packet is used in all other references. Network Controller Sideband Interface (NC-SI) Specification

packet payload:

See MCTP packet payload.

parameter, CIM parameter:

A named and typed argument passed in and out of methods.

The return value of a method is not considered a parameter; instead it is considered part of the method.

In a schema, parameters are special kinds of schema elements.

In the CIM meta-model, parameters are represented by the meta-element named "Parameter". Common Information Model (CIM) Infrastructure

Parent Body:

DMTF Body immediately above the current body in the hierarchy of DMTF Bodies. DMTF Process for Working Bodies

participant:

An Applicant that has been approved to participate in the Conformance Program. Common Diagnostics Model 1.0 Conformance Policy

Participating Member:

Member Company that has full access to DMTF specifications and standards. Participating Members may join and participate in multiple Bodies except Committees. Participating Members may vote in Working Groups, Forums and Chapters in which they have joined and participate. DMTF Process for Working Bodies

pass-through traffic/message/packets:

Non-control packets passed between the external network and the management controller through the network controller. Network Controller Sideband Interface (NC-SI) Specification

pattern:

Specification of the permissible values for a property or parameter; see also the term match. Management Profile Usage Guide
See also match.

pattern profile:

A design pattern consisting of some number of adaptations that is useful in the specification of referencing profiles. Management Profile Usage Guide

payload:

Refers to the information bearing fields of a message. This is separate from those fields and elements that are used to transport the message from one point to another, such as address fields, framing bits, checksums, and so on. In some instances, a given field may be both a payload field and a transport field. MCTP Base Specification

PCI bridge:

Indicates a PCI device that provides the capability to connect two PCI busses. PCI Device Profile

PCI bus:

Indicates a bus subsystem that provides the capability to connect multiple PCI devices. PCI Device Profile

PCI device:

Indicates a logical Peripheral Component Interconnect or Peripheral Component Interconnect Express device. PCI Device Profile

PCI port:

Indicates a PCI device port used to describe the connection between PCI devices. PCI Device Profile

PCIe Requester ID (Bus/Device Function) RID

PCIe switch:

Indicates a PCI Express switch device that provides the capability to connect multiple PCI Express devices. PCI Device Profile

pending configuration:

Indicates the configuration that will be applied to an IP interface the next time the interface accepts a configuration. Host LAN Network Port Profile ,

Indicates the configuration that will be applied to an IP network connection the next time the IP network connection accepts a configuration. IP Configuration Profile

pending firmware component:

A newly transferred component image has been fully delivered to the firmware device, but is not the actively running code image. The firmware component will report details on the pending image (such as version, date, and its activation methods). The applicable activation method shall be performed for the pending image to become the actively running image. Platform Level Data Model (PDLM) for Firmware Update Specification

pending power state change:

Indicates the power state transition that will be initiated sometime in the future. Power State Management Profile

persistent memory:

Byte addressable memory that retains its contents across system power cycles. Multi-type System Memory Profile

PHY:

Physical layer of the OSI protocol model. Ethernet NIC Diagnostics Profile

physical element:

An instance of a CIM_PhysicalElement subclass (such as CIM_PhysicalConnector, CIM_Slot, CIM_PhysicalComponent, CIM_Chip, CIM_PhysicalMemory, CIM_PhysicalPackage, CIM_PhysicalFrame, CIM_Chassis, CIM_Rack, and CIM_Card) that represents a physical element. Physical Asset Profile

physical location:

Physical place associated with a specific geographical reference. Software Identification and Entitlement Usage Metrics

physical package:

An instance of a CIM_PhysicalPackage or a CIM_PhysicalPackage subclass (such as CIM_PhysicalFrame, CIM_Chassis, CIM_Rack, and CIM_Card) or CIM_PhysicalComponent or CIM_PhysicalComponent subclass (such as CIM_Chip or CIM_PhysicalMemory) that represents a package. Physical Asset Profile

physical transport binding

Refers to specifications that define how the MCTP base protocol and MCTP control commands are implemented on a particular physical transport type and medium, such as SMBus/I2C, PCI Express™ Vendor Defined Messaging, and so on. MCTP Base Specification

PKI Credential Instance:

An instance of CIM_UnsignedCredential, CIM_X509Certificate, or CIM_X509CRL representing a PKI credential. Certificate Management Profile

platform:

Combination of hardware and software operating environment upon which applications can be installed and operate. Software Identification and Entitlement Usage Metrics

Platform Descriptor Record (PDR):

A set of data that is used to provide semantic information about sensors, effecters, monitored or controller entities, and functions and services within a PLDM implementation.

PDRs are mostly used to support PLDM monitoring and control and platform events. This information also describes the relationships (associations) between sensor and control functions, the physical or logical entities that are being monitored or controlled, and the semantic information associated with those elements. PLDM for Platform Monitoring and Control Specification

Platform Management Component Intercommunications (PMCI):

Name for a working group under the Distributed Management Task Force's Pre-OS Workgroup that is chartered to define standardized communication protocols, low level data models, and transport definitions that support communications with and between management controllers and management devices that form a platform management subsystem within a managed computer system. MCTP Base Specification

point-to-point:

Refers to the case where only two physical communication devices are interconnected through a physical communication medium. The devices may be in a master/slave relationship, or could be peers. Network Controller Sideband Interface (NC-SI) Specification ,

Refers to the situation in which only a single Management Controller and single Network Controller package are used on the bus in a master/slave relationship, where the Management Controller is the master. MCTP Base Specification

polymorphism:

The ability of an instance to be of a class and all of its subclasses

For example, a CIM operation may enumerate all instances of class ACME_Device. If the instances returned may include instances of subclasses of ACME_Device, then that CIM operation is said to implement polymorphic behavior. CIM Infrastructure Specification

port:

Communication endpoint for systems or storage devices. A port enables the exchange of data according to one or more protocols. Storage Resource Virtualization Profile

power capping:

System function that is active power management based on dynamic and static configuration of system operation for a well-defined goal: the system's power capping level. Power Utilization Management Profile

power domain:

The set of systems and components that receive power from a given power source that consists of one or more power supplies. Modular Systems Profile

power managed element:

The computer system whose power utilization is being managed. Power Utilization Management Profile

preboot:

Non-production OS/diagnostic environment running on system hardware. Ethernet NIC Diagnostics Profile

primary contact:

The person in the employ of the Applicant company who is authorized by the company to make Program-related decisions. The Program Administrator accepts Program-related information and decisions from this contact only. Common Diagnostics Model 1.0 Conformance Policy

Primary Voter:

The person eligible to vote in a Body that has been identified in the roster of that Body as the primary voter. There may only be one Primary Voter representing any Member. A Member may elect to identify different persons as the Primary Voter in each Body in which it may vote. DMTF Process for Working Bodies

primordial storage resource pool:

A storage resource pool that aggregates storage resources available for or used by storage resource allocations. Storage Resource Virtualization Profile

principal:

An entity that can be positively identified and verified through an authentication mechanism. Simple Identity Management Profile

Process Document:

Any document produced by the DMTF that defines the policies and procedures that apply to the DMTF. DMTF Process for Working Bodies

processor:

Set of logic circuitry within a CPU that responds to and processes the basic instructions that perform the intended functions of a computing device

Modern processors may contain more than one core and/or have multithread capabilities that allow for execution of multiple instructions. Software Identification and Entitlement Usage Metrics

processor blade:

A specific type of blade designed to provide processing capability in support of an operating system. Modular Systems Profile

processor resource:

A processor device or computing resource as seen by a consumer. Processor Resource Virtualization Profile

processor resource allocation:

The allocation of a processor resource from a processor resource pool to a virtual system. Processor Resource Virtualization Profile

processor resource allocation request:

A request for a processor resource allocation. Processor Resource Virtualization Profile

processor resource pool:

A resource pool that represents processor resources available for processor resource allocation. Processor Resource Virtualization Profile

processor resource pool configuration service:

A configuration service that supports the addition or removal of host storage processor resources to or from a processor resource pool, and the creation or deletion of concrete subpools of a processor resource pool. Processor Resource Virtualization Profile

product:

A Certified Implementation. Common Diagnostics Model 1.0 Conformance Policy

Any desktop or mobile system sold by the Applicant that qualifies for Conformance Testing and Conformance Test Result Certification per the Conformance Program Policies and Procedures. Applicant’s Products being tested pursuant to this Application Agreement are identified in “Applicant Submission Information”. DASH 2.0 Conformance Program Policies and Procedures

product activation:

Activation associates an event that recognizes the intended use of a software product with a specific device or system. Software Identification and Entitlement Usage Metrics

product edition:

A specific edition (i.e., a SKU variation) related to a specific version of a licensed software product. Software Identification and Entitlement Usage Metrics

product version:

A specific release of a licensed software product. Software Identification and Entitlement Usage Metrics

profile:

A management profile, as defined in Management Profile Usage Guide(DSP1001).

A synonym for management profile. Management Profile Specification Usage Guide

profile conformance:

Conformance of an implementation to one or more profiles, such that the implementation satisfies the rule for full implementation conformance defined in subclause 5.2.2 of Management Profile Usage Guide (DSP1001). Profile Registration Profile

profile defined model:

A model of a management domain (or a subset of a management domain) defined by a profile that is composed of class adaptations. Management Profile Usage Guide

profile derivation:

A use of a referenced profile as the base profile.

A profile derivation establishes a referenced profile as the base profile of the referencing profile. Management Profile Usage Guide

profile element:

Formal elements that Management Profile Usage Guide (DSP1001) establishes to be specified by profiles. Management Profile Usage Guide

profile implementation:

A subset of an implementation that realizes the requirements of a particular profile in a particular profile implementation context. Management Profile Usage Guide

profile implementation context:

A context in which a profile or an adaptation is implemented. Management Profile Usage Guide

profile reference:

A named profile element that references another profile. Management Profile Usage Guide

profile-specific filter collection:

A static filter collection that covers all indications of a particular type defined in a profile. Indications Profile

profile specification:

Synonym for management profile specification. Management Profile Usage Guide

profile usage:

A use, (other than for derivation), of a referenced profile.

A use of the referenced profile established by a referencing profile. Management Profile Usage Guide

Program Administrator (PA):

The DMTF-appointed entity for administering the conformance program. DASH 2.0 Conformance Program Policies and Procedures

program sponsor, Conformance Program Sponsor:

The entity responsible for the creation and maintenance of the Conformance Program. The Program Sponsor for this Program is the CDM Forum of the DMTF. Common Diagnostics Model (CDM) Conformance Program Policies

prohibited:

A requirement level indicating that the subject profile prohibits the implementation of the designated profile element. Management Profile Usage Guide

propagation:

The ability to derive a value of one property from the value of another property.

CIM supports propagation via either PropertyConstraint qualifiers utilizing a derivation constraint or via weak associations. Common Information Model (CIM) Infrastructure

property:

An attribute of the command target. Management Profile Usage Guide

A name/value pair included in a Redfish-defined resource as part of a request or response. A property may be defined as any valid JSON data type. Redfish Scalable Platform Management API Specification

An individual datum contained within a Resource. Platform Level Data Model (PLDM) for Redfish Device Enablement

property, CIM property:

A named and typed structural feature of a class.

Name, data type, default value and other information about the property are defined in a class. Properties have values that are available in the instances of a class. The values of its properties may be used to characterize an instance.

For example, a class ACME_Device may define a string typed property named "Status". In an instance of class ACME_Device, the Status property may have a value "on".

Special kinds of properties are ordinary properties and references.

In a schema, properties are special kinds of schema elements.

In the CIM meta-model, properties are represented by the meta-element named "Property". Common Information Model (CIM) Infrastructure

property requirement:

A requirement stated as part of a class adaptation that defines requirements and constraints on a property exposed by the adapted class. Management Profile Usage Guide

provider network:

The underlay network of a tunnel. The network containing the encapsulated network traffic from the perspective of the encapsulation gateways specified in this profile. Network Management - Tunnel Management Profile

provisioning (software):

The process of selecting, reserving resources, or creating an instance of a service offering. Software Identification and Entitlement Usage Metrics

push mode:

A delivery mechanism where the source sends event messages to the sink as individual, unsolicited SOAP messages. Web Services for Management (WS-Management) Specification

Back to Top

Q

qualified element:

A schema element that has a qualifier specified in the declaration of the element

For example, the term "qualified element" in the description of the Counter qualifier refers to any property (or other kind of schema element) that has the Counter qualifier specified on it. CIM Infrastructure Specification

qualifier, CIM qualifier:

A named value used to characterize schema elements

Qualifier values may change the behavior or semantics of the qualified schema element. Qualifiers can be regarded as metadata that is attached to the schema elements. The scope of a qualifier determines on which kinds of schema elements a specific qualifier can be specified.

For example, if property ACME_Modem.Speed has the Key qualifier specified with a value of True, this characterizes the property as a key property for the class. CIM Infrastructure Specification

qualifier type:

A common type for a set of qualifiers

In a CIM server, qualifier types are special kinds of objects. The address of qualifier type objects is termed "qualifier type path".

In a schema, qualifier types are special kinds of schema elements.

In the CIM meta-model, qualifier types are represented by the meta-element named "QualifierType". CIM Infrastructure Specification

qualifier type declaration:

The definition (or specification) of a qualifier type

For example, a qualifier type object that is accessible through a CIM server can be retrieved by a CIM client. What the CIM client receives as a result, is actually a qualifier type declaration. Although unlikely, the qualifier type itself may already have changed its definition by the time the CIM client receives the qualifier type declaration. Similarly, when a qualifier type that is accessible through a CIM server is being modified through a CIM operation, one input parameter might be a qualifier type declaration that is used during the processing of the operation to change the qualifier type. CIM Infrastructure Specification

qualifier type path:

A special kind of object path addressing a qualifier type that is accessible through a CIM server. CIM Infrastructure Specification,

A special kind of object path addressing a CIM qualifier type that is accessible through a WBEM server. Generic Operations Specification

qualifier value:

The value of a qualifier in a general sense, without implying whether it is the specified value, the effective value, or the default value. CIM Infrastructure Specification

query:

A filter to constrain the events for which indications are generated. Indications Profile

query statement:

A statement expressed in a query language used to describe either (a part of) an event or the coverage of an indication filter. Indications Profile

Back to Top

R

rack:

A placement policy as defined in the class CIM_Rack. Open Virtualization Format Specification

Rate Limiting:

A method for limiting the data rate sent from an MCTP endpoint to another MCTP endpoint. MCTP Base Specification

real logical device:

The instance of CIM_LogicalDevice that represents the underlying shared device. Shared Device Management Profile

recommended:

Indicates that valid reasons may exist in particular circumstances to ignore a particular item, but the full implications should be understood and carefully weighed before choosing a different course. MCTP Base Specification

record data format:

Refers to a log entry where the LogEntry data is contained in RecordData property whose data structure is described by RecordFormat property. Record Log Profile

RDE device:

Any PLDM terminus containing an RDE provider that requires the intervention of an MC to receive Redfish communications. Platform Level Data Model (PLDM) for Redfish Device Enablement

RDE operation:

The sequence of PLDM messages and operations that represent a Redfish operation being executed by an MC and/or an RDE device on behalf of a client. Platform Level Data Model (PLDM) for Redfish Device Enablement
See also Redfish operation

RDE provider:

Any RDE device that responds to RDE operations. Platform Level Data Model (PLDM) for Redfish Device Enablement
See also Redfish Provider.

Redfish Alert Receiver:

The name for the functionality that receives alerts from a Redfish Service. This functionality is typically software running on a remote system that is separate from the managed system. Redfish Scalable Platforms Management API Specification

Redfish Client:

The name for the functionality that communicates with a Redfish Service and accesses one or more resources or functions of the Service. Redfish Scalable Platforms Management API Specification

Redfish event receiver:

Communicates with a Redfish service and accesses one or more of the service’s resources or functions. Redfish Specification

Redfish Manager:

Also referred to as "Manager." The entity that manages a computer system and other peripherals through a Redfish Service. Redfish Host Interface Specification

Redfish operation:

Any Redfish operation transmitted via HTTP or HTTPS from a client to an MC for execution. Platform Level Data Model (PLDM) for Redfish Device Enablement
See also RDE operation.

Redfish Protocol:

The set of protocols that are used to discover, connect to, and inter-communicate with a Redfish Service. Redfish Scalable Platforms Management API Specification

Redfish Provider:

A Redfish provider interacts with the Redfish Service to contribute resources to the Redfish resource tree and reacts to changes in its owned resources. There are two types of Redfish providers: internal providers and external providers. A internal provider is the Redfish Service itself that has a data model and can react to RESTful operations from a client. An external provider is an architected means for agents external to the Redfish Service to augment the Redfish resource tree. The interaction between a Redfish provider and a Redfish Service is not covered by this specification. Redfish Scalable Platforms Management API Specification

Redfish Schema:

The Schema definitions for Redfish resources. It is defined according to OData Schema representation that can be directly translated to a JSON Schema representation. Redfish Scalable Platforms Management API Specification

Redfish Service:

Also referred to as the "Service". The collection of functionality that implements the protocols, resources, and functions that deliver the interface defined by this specification and its associated behaviors for one or more managed systems. Redfish Scalable Platforms Management API Specification

Redfish Service Entry Point:

Also referred to as "Service Entry Point". The interface through which a particular instance of a Redfish Service is accessed. A Redfish Service may have more than one Service Entry Point. Redfish Scalable Platforms Management API Specification

Reduced Media Independent Interface (RMII):

A reduced signal count MAC to PHY interface, based on the IEEE Media Independent Interface (MII), which was specified by the RMII Consortium (3Com Corporation; AMD Inc.; Bay Networks, Inc.; Broadcom Corp.; National Semiconductor Corp.; and Texas Instruments Inc.). MCTP Base Specification

reference, CIM reference:

An association end.

References are special kinds of properties that reference an instance.

The value of a reference is an instance path. The type of a reference is a class of the referenced instance. The referenced instance may be of a subclass of the class specified as the type of the reference.

In a schema, references are special kinds of schema elements.

In the CIM meta-model, references are represented by the meta-element named "Reference". Common Information Model (CIM) Infrastructure

referenced profile:

A profile that is included in another profile's “Related profiles” subclause.

A profile that is referenced by another profile.

A profile that is referenced by another profile, establishing either profile derivation or a profile usage. Management Profile Usage Guide ,

A profile that is referenced by a profile that lists it in its profile references table. Profile Registration Profile

reference property:

A general term for reference-typed properties and reference-qualified properties. CIM-RS Protocol

reference-qualified property:

A string-typed CIM property qualified with the Reference qualifier. CIM-RS Protocol

reference-typed parameter:

A CIM method parameter declared with a CIM datatype that is a reference to a specific class. CIM-RS Protocol

reference-typed property:

A CIM property declared with a CIM datatype that is a reference to a specific class.

DSP0004 defines the term "reference" for such properties; this document uses the more specific term "reference-typed property", instead. CIM-RS Protocol

referencing profile:

A profile referencing this profile. Note that DSP1001 requires each profile that defines indications to reference this profile.

A profile that includes a reference to another profile in its “Related profiles” subclause.

A profile that owns the definition of this class and can include a reference to this profile in its “Referenced Profiles” table.

A profile that references a profile by listing it in its profile references table.

Profile that references another profile, establishing either profile derivation or a profile usage. Shared Device Management Profile

registered profile:

A profile to which an implementation advertises conformance. Before version 1.1 of this profile, registered profiles were termed "subject profiles" (that term is now deprecated). Profile Registration Profile

registration:

The process of enabling a compliant RDE device with an MC to be an RDE provider.Platform Level Data Model (PLDM) for Redfish Device Enablement

registry reference:

A named profile element referencing a message registry or a metric registry. Management Profile Usage Guide

related profile:

Deprecated synonym for referenced profile.\

relationship (software):

A connection or interaction between one or more products, solutions, software components, applications or IT Service

Suites and bundles are clear examples of where knowledge of the relationships involved is important to properly manage a product or solution during packaging, provisioning, or addressing license compliance.

A more complex example is an IT Service and its requisite applications, where documenting and maintaining the relationships between all the various elements involved is crucial for proper change and performance management. Software Identification and Entitlement Usage Metrics

Relative Target Address:

A designation of target address in relation to the Current Default Target as opposed to an Absolute Target Address. Server Management Command Line Protocol (SM CLP) Specification

reliable indication:

An indication containing a sequence identifier enabling listeners to detect duplicate, missing, or out-of-order indications. Indications Profile

Remote Media:

A manageability feature that enables remote media devices to appear as if they are attached locally to the host. Network Controller Sideband Interface (NC-SI) Specification

Remote Procedure Call (RPC):

An RPC is an implementation of a function in which a call to the function occurs in one process and the function is executed in a different process, often in a remote location linked by a network. RPC-based systems are often contrasted with RESTful systems. In a RESTful system, the interactions between client and server follow the REST constraints and the design focus is on the resources. In an RPC-based system, the design focus is on the functions invoked, and there is not necessarily even the notion of well-defined resources. CIM-RS White Paper

remote system:

The system that contains the physical USB or Media device, to which the managed system can establish a network connection for an Emulated USB or Media Device. USB Redirection Profile

repeated indication:

An indication that reports the same event as a previous indication. Indications Profile

repeated indication delivery:

The delivery of repeated indications.

Repeated indication delivery typically occurs if the reported event describes a persistent situation such as exceeding a threshold value. Indications Profile

Representational State Transfer (REST):

A style of software architecture for distributed systems that is based on addressable resources, a uniform constrained interface, representation orientation, stateless communication, and state transitions driven by data formats. Usually REST architectures use the HTTP protocol, although other protocols are possible. See Architectural Styles and the Design of Network-based Software Architectures for the original description of the REST architectural style. CIM-RS White Paper

required:

Indicates that the item is an absolute requirement of the specification. MCTP Base Specification

request:

A message from a Client to a Server. It consists of a request line (which includes the Operation), request headers, an empty line and an optional message body. Redfish Scalable Platforms Management API Specification

Required Properties:

Properties for which the profile that owns the definition of the class requires that instances of the class have values. Server Management Command Line Protocol Specification (SM CLP)

requirement level:

Designator that indicates the requirement for implementing profile elements or referenced profiles. Management Profile Usage Guide

Reserved String:

A text-string token that is recognized and reserved by the CLP to have a specified meaning when used as an option argument, argument value, or property value. Server Management Command Line Protocol Specification (SM CLP)

Reserved Target:

A valid value for a target term that has a special meaning defined by this specification.

The meaning of a Reserved Target cannot be changed by a user nor can additional Reserved Targets be created. Server Management Command Line Protocol Specification (SM CLP)

resource:

A Web service that is addressable by an endpoint reference and accessed using the operations defined in this specification. This resource can be represented by an XML document. The XML document may be a representation of managed resource. Web Services for Management (WS- Management) Specification ,

A representation of an entity managed by the [Cloud Service] Provider that is generally available to the [Cloud Service] Consumer to access or operate on by the way of the interface described in this specification. Synonym for “CIMI resource”. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

A Resource is addressable by a URI and is able to receive and process messages. A Resource can be either an individual entity, or a collection that acts as a container for several other entities. Redfish Scalable Platforms Management API Specification

A hierarchical set of data organized in the format specified in a Redfish Schema. Platform Level Data Model (PLDM) for Redfish Device Enablement

resource allocation:

Process of assigning, separating, reserving, granting share of, or emulating resour¬ces for use by a consumer. Resource Allocation Profile

resource allocation request:

Request for resources to be allocated. Resource Allocation Profile

resource class:

An abstract representation (type) of a managed resource

A resource class defines the representation of management-related operations and properties. An example of a resource class is the description of operations and properties for a set of laptop computers. Web Services for Management (WS- Management) Specification

Resource Collection:

A Resource Collection is a Resource that acts as a container of other Resources. The Members of a Resource Collection usually have similar characteristics. The container processes messages sent to the container. The Members of the container process messages sent only to that Member without affecting other Members of the container. Redfish Scalable Platforms Management API Specification

resource factory:

A Web service that is capable of creating new resources using the Create operation defined in this specification. Web Services for Management (WS- Management) Specification

resource identifier:

In CIM-RS, a URI that is a reference to (or an address of) a resource. Generally, a resource may have more than one resource identifier; however in CIM-RS that is not the case. CIM-RS White Paper

resource instance:

An instantiation of a resource class.

An example is the set of management-related operations and property values for a specific laptop computer Web Services for Management (WS- Management) Specification

resource pool:

An abstract entity exposed by the virtualization platform for the purpose of allocation of allocated resources to consumers. Allocation Capabilities Profile

resource representation:

A representation of a resource or some aspect thereof, in some format. A particular resource may have any number of representations. The format of a resource representation is identified by a media type. In CIM-RS protocol, the more general term "payload representation" is used, because not all protocol payload elements are resource representations. CIM-RS Protocol Specification

resource state:

The state of a resource managed by a RESTful service, in contrast to application state. CIM-RS White Paper

Resource Tree:

A Resource Tree is a tree structure of JSON encoded resources accessible via a well-known starting URI. A client may discover the resources available on a Redfish Service by following the resource links from the base of the tree.

NOTE for Redfish client implementation: Although the resources are a tree, the references between resources may result in graph instead of a tree. Clients traversing the resource tree must contain logic to avoid infinite loops. Redfish Scalable Platforms Management API Specification

resource type:

Generic type categorizing classes of resources (for example, processor, memory, network adapter). Resource Allocation Profile

response:

Control packet sent by the Network Controller to the Management Controller as a positive acknowledgement of a command received from the Management Controller, and to provide the execution outcome of the command, as well as to return any required data. Network Controller Sideband Interface (NC-SI) Specification

A message from a Server to a Client in response to a request message. It consists of a status line, response headers, an empty line and an optional message body. Redfish Scalable Platforms Management API Specification

REST architectural style:

The architectural style described in Architectural Styles and the Design of Network-based Software Architectures, chapter 5, and in REST APIs must be hypertext driven. CIM-RS Protocol Specification

Resultant Address:

The Target Address after applying the target address precedence rules. Server Management Command Line Protocol Specification (SM CLP)

Resultant Target:

The effective target for a command after applying the target address precedence rules. Server Management Command Line Protocol Specification (SM CLP)

RMII:

A reduced signal count MAC to PHY interface, based on the IEEE Media Independent Interface (MII), which was specified by the RMII Consortium (3Com Corporation; AMD Inc.; Bay Networks, Inc.; Broadcom Corp.; National Semiconductor Corp.; and Texas Instruments Inc.). MCTP Packets and NC-SI over MCTP Overview

RMII Based Transport (RBT):

Electrical and timing specification for a 3.3V physical medium that is derived from RMII. Network Controller Sideband Interface (NC-SI) Specification

Root Instance:

An instance of CIM_ManagedElement that is associated with the instance of CIM_Role through the CIM_RoleLimitedToTarget association and conceptually symbolizes the root of the scope hierarchy for the CIM_Role instance. Role Based Authorization Profile

runtime:

Describes the situation where XML instances are produced that are conformant to this standard. WS-CIM Mapping Specification

Back to Top

S

safe HTTP method:

An HTTP method that has no side-effects. RFC2616 requires the HTTP methods GET and HEAD to be safe. By definition, an HTTP method that is safe is also idempotent. CIM-RS White Paper

sampling interval:

A value that determines how often new metric values are retrieved, if metrics are retrieved periodically. Base Metrics Profile

schema:

A named set of classes with a single defining authority or owning organization. The classes in a schema have the same schema prefix in their class name. For a complete definition, see Common Information Model (CIM) Infrastructure. NOTE DMTF defines two schemas: The Common Information Model (schema prefix CIM) and the Problem Resolution Schema (schema prefix PRS). Management Profile Usage Guide

schema element:

Generally, refers to schema elements as defined in DSP0004. In DSP1001_1.2.0, the term is used for the subset of schema elements that may be constrained by profiles: classes (including association classes and indication classes), properties (including references), methods, and parameters. Management Profile Usage Guide

scope:

Part of a qualifier type, indicating the meta-elements on which the qualifier can be specified

For example, the Abstract qualifier has scope class, association and indication, meaning that it can be specified only on ordinary classes, association classes, and indication classes. CIM Infrastructure Specification

scoped profile:

A profile that receives a scope provided by a scoping profile. Synonymous with component profile. Management Profile Usage Guide

scoping class:

A class defined in a referencing profile and identified as the top-level class in an implementation hierarchy that is associated with the representation of the referencing profile and is the algorithmic focal point for identifying profile conformance when using the Scoping Class Methodology. Profile Registration

scoping class adaptation:

A specifically designated class adaptation in a profile that is the algorithmic focal point for identifying profile conformance when using the scoping class methodology. Management Profile Usage Guide

scoping class methodology:

An algorithm for advertising profile conformance that uses the scoping instances of the registered profile as an algorithmic focal point. Profile Registration Profile
See also central class methodology.

scoping element:

The managed object type modeled by a scoping class adaptation. Profile Registration
See also central element.

scoping instance:

An instance of the Scoping Class adaptation. Profile Registration Profile
See also central instance.

scoping object, scoping instance, scoping class:

A scoping object provides context for a set of other objects. A specific example is an object (class or instance) that propagates some or all of its key properties to a weak object, along a weak association. CIM Metamodel

scoping path:

An association traversal path between the central class adaptation and the scoping class adaptation. Management Profile Usage Guide

scoping profile:

A referencing profile that provides a scope to a referenced profile by defining a central class adaptation that is based on the scoping class adaptation defined by the referenced profile. Management Profile Usage Guide

Security Event:

Identified occurrence of a system, service or network state indicating a possible breach of information security, policy or failure of controls, or a previously unknown situation that may be security relevant. [ISO 27000:2009] An occurrence in a system that is relevant to the security of the system. See "Security Incident". [RFC 549 2828]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

Security Incident:

Single or a series of unwanted or unexpected information security events that have a significant probability of compromising business operations and threatening information security. [ISO 27000:2009]. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

segment:

A component of a Network that supports communication between Endpoints using a single protocol. Also referred to as a Protocol Segment to emphasize that Segments are always bound to a single communication protocol. Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol

Selection Criteria:

A set of terms that define rules for matching against a set of input records. Records that match the selection criteria are included in the output set; records that do not match are filtered out of the output set. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

selector:

A resource-relative name and value pair that acts as an instance-level discriminant when used with the WS Management default addressing model

A selector is essentially a filter or "key" that identifies the desired instance of the resource. A selector may not be present when service-specific addressing models are used.

The relationship of services to resource classes and instances is as follows:

- A service consists of one or more resource classes.

- A resource class may contain zero or more instances.

If more than one instance for a resource class exists, they are isolated or identified through parts of the SOAP address for the resource, such as the ResourceURI and SelectorSet fields in the default addressing model. Web Services for Management (WS- Management) Specification

self-contained activation:

Capability of a firmware device whereby the newly transferred component images can immediately become the actively running firmware component code image after receiving an activate command from the update agent. In some cases a firmware component is not actively running (i.e., a uEFI driver which only executes on system startup) and therefore the self-contained activation will still apply. Platform Level Data Model (PDLM) for Firmware Update Specification

sensors collection:

CIM_ConcreteCollection instance for instances of the CIM_Sensor and CIM_NumericSensor classes. SMASH Collections Profile

sequence identifier:

Data element with a reliable indication that ensures unique identification of the reliable indication. A sequence identifier is composed of a sequence context and a sequence number. Indications Profile

sequence identifier lifetime:

A maximum time interval maintained by an implementation implementing reliable indications within which the implementation retries failed indication delivery attempts. Indications Profile

server (software):

The part of a client-server application that the client software interacts with. For example: an email server. Software Identification and Entitlement Usage Metrics

Server Management Managed Element (SM ME)

service:

A Text Console Redirection Service.

A KVM Console Redirection Service.

A KVM Redirection Service.

An application that provides management services to clients by exposing the Web services defined in this document.

Typically, a service is equivalent to the network "listener," is associated with a physical transport address, and is essentially a type of manageability access point. Web Services for Management

service catalog:

Self-service portals and/or eProcurement systems that contain a list of available services and products that can be requested/ordered in an automated manner. Software Identification and Entitlement Usage Metrics

Service Delivery Model:

The approach used to deliver a given service to its intended consumers.

As it applies to software, Service Delivery Models vary to address different ways in which software can be sold, managed and accessed, such as Software as a Service vs. software that must be installed by the customer on their own server, etc. Software Identification and Entitlement Usage Metrics

service processor:

A specialized device dedicated to management. Service Processor Profile

Service Root:

The term Service Root is used to refer to a particular resource that is directly accessed via the service entry point. This resource serves as the starting point for locating and accessing the other resources and associated metadata that together make up an instance of a Redfish Service. Redfish Scalable Platforms Management API Specification

session:

A Text Console Redirection Session

A KVM Console Redirection Session.

A KVM Redirection Session. Text Console Redirection Profile

settings collection:

CIM_ConcreteCollection instance for instances of the CIM_SettingData class. SMASH Collections Profile

Sexagesimal:

A numeral system with sixty as its base (i.e. base 60). In the context of this specification, geographic coordinates are often expressed as degrees, minutes and seconds which is a base 60 system. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

shall:

Indicates requirements to be followed strictly to conform to the document and from which no deviation is permitted. Web Services for Management (WS-Management) Specification

shall not:

Indicates requirements to be followed strictly to conform to the document and from which no deviation is permitted. Web Services for Management (WS-Management) Specification

shared virtual resource:

Virtual resource that has been given the use of host resources that may also be shared with other consumers. CIM System Virtualization Model White Paper

sharing logical device:

An instance of CIM_LogicalDevice that represents a Sharing System’s view of the underlying shared resource. Shared Device Management Profile

sharing system:

An instance of CIM_ComputerSystem that represents a system that uses a shared device. Shared Device Management Profile

should:

Indicates that among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required. Web Services for Management (WS- Management) Specification

should not:

Indicates that a certain possibility or course of action is deprecated but not prohibited. Web Services for Management (WS- Management) Specification

signature:

A method name together with the type of its return value and the set of names and types of its parameters. Common Information Model (CIM) Infrastructure

simple endpoint:

An MCTP endpoint that is not associated with either the functions of an MCTP bus owner or an MCTP bridge. MCTP Base Specification

simple ethernet connection:

An Ethernet connection in which a default Ethernet switch port and a default Ethernet adapter are instantiated as part of an Ethernet connection allocation. Ethernet Port Resource Virtualization Profile

simple resource allocation:

Resource allocation with no logical device representing the allocated resources. CIM System Virtualization Model White Paper

singular KVM redirection:

A KVM Redirection in which the MaxCurrentEnabledSAPs property of the CIM_RedirectionService instance has a value of 1. KVM Redirection Profile

singular text console redirection:

A Text Console Redirection in which the MaxCurrentEnabledSAPs property of the CIM_TextRedirectionService instance has a value of 1. Text Console Redirection Profile

site:

A placement policy as defined in Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 2: Network sites; Sub-part 1: Operator sites, Technical Report, ETSI TR 105 174-2-1 V1.1.1 (2009-10). Open Virtualization Format Specification

snapshot monitoring:

The process in which metric values are gathered synchronously with a request from the instrumentation or reporting layer. Base Metrics Profile

Software as a Service (SaaS):

A service delivery model where the capability provided to the consumer is to use the provider’s application(s) running on a cloud infrastructure accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email)

The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings. Software Identification and Entitlement Usage Metrics

software bundle:

A grouping of software products which is the result of a marketing/licensing strategy to sell entitlements to multiple products as one purchased item.

As these are multiple licensed products there may be no way to determine that an individual installed product was purchased as a bundle. Software Identification and Entitlement Usage Metrics

One of the component classification values that represents a single component image containing multiple code objects each of which would be known only by the firmware device. The layout of the code objects within the software bundle is not defined in this spec. Platform Level Data Model (PDLM) for Firmware Update Specification

software catalog:

A subset of the service catalog that contains the list of software titles available for request/order through self-service portals and/or eProcurement systems. Software Identification and Entitlement Usage Metrics

software element:

A general term that is used to mean one discrete software part of a more complex software product or application. Software Identification and Entitlement Usage Metrics

software family:

A group of software in which each member software could be installed in the place of the other on a Managed Element and offer similar functionality to a Managed Element. Software Inventory Profile

software identity:

an instance of CIM_SoftwareIdentity that represents and contains the identifying property values of a software image. Software Inventory Profile

software installation service:

A component that can be used to perform an installation or update of software on a managed element. Software Update Profile

software package:

A set of related software components that are combined into a single payload or a distributable installable item.

For example, a software package is a set of files that can be used to install software on a computing device and can be distributed via CD or electronic means. An Open Virtualization Format (OVF) package is an example of a package for cloud deployment. Software Identification and Entitlement Usage Metrics

software product:

One or more applications governed by one license, which may include procedures, documentation and data, commercially available as a single item for a fee to a licensee. Software Identification and Entitlement Usage Metrics

software suite:

A set of individually licensable software products or software features, that is combined and licensed as a separate single product. Software Identification and Entitlement Usage Metrics

solution:

A combination of one or more applications, which may also include one or more computing systems, made available as a single IT Service. Software Identification and Entitlement Usage Metrics

Solution Multiplexing:

Correlation of use of multiple individually licensed software components that compose a licensed application.

For example, a web tier application with a single sign on to a data tier application may need to track those requests on a user’s behalf that result in requests to the data tier. Software Identification and Entitlement Usage Metrics

source virtualization platform:

The source of the virtual system being acted upon. Virtual System Migration Profile

span of a class adaptation:

The directed acyclic graph that contains the class adaptation, all (direct or indirect) base adaptations of the class adaptation, the adapted class, and all its superclasses. Management Profile Usage Guide

spare fan:

An instance of CIM_Fan that represents a spare fan in any condition. Fan Profile

spare power supply:

Indicates an instance of CIM_PowerSupply that represents a spare power supply in any condition.

Spare power supply is part of redundancy set but is not actively driving the load. Power Supply Profile

specification:

A collection of Common Information Model (CIM) elements and behavior rules that represents a specific area of management. Common Diagnostics Model (CDM) Conformance Program Policies

Specification Authority (SA):

The DMTF or party that is responsible for developing, maintaining, and interpreting the Specifications. Common Diagnostics Model (CDM) Conformance Program Policies; DASH 2.0 Conformance Program Policies and Procedures

Sponsored Member:

An individual who is not an employee of a Member Company but who is sponsored to participate by a Member Company and participates at the membership level of that Member Company. DMTF Process for Working Bodies

standard message format:

Refers to a log entry where the LogEntry data is contained in Message and/or MessageArguments properties. Record Log Profile

standby service processor:

An instance of CIM_ComputerSystem that represents a standby service processor of a redundancy set. Service Processor Profile

state description:

A named profile element that describes of the state of an instance of (a subset of) the model defined by a profile at a particular point in time. Management Profile Usage Guide

static ethernet connection allocation:

An Ethernet connection allocation where a specific pre-existing Ethernet switch port is requested as part of the allocation request. Ethernet Port Resource Virtualization Profile

static filter:

An instance of CIM_IndicationFilter that is created by a profile implementation at load time. These instances usually do not change. Indications Profile

static filter collection:

A filter collection whose lifecycle is controlled by the implementation, that is uniquely identifiable and for which a defined coverage is established. Indications Profile

static indication filter:

An indication filter whose life cycle is controlled by the implementation. Indications Profile

station:

A component that can connect into a wireless medium in a network. Wi-Fi Port Profile

storage blade:

A specific type of blade designed to provide storage media or access. Modular Systems Profile

Storage Management Host Bus Adapter (SM-HBA)

storage resource:

A logical disk, a storage volume or a storage extent. Storage Resource Virtualization Profile

storage resource allocation:

The allocation of a storage resource from a storage resource pool to a virtual system. Storage Resource Virtualization Profile

storage resource allocation request:

A request for a storage resource allocation. Storage Resource Virtualization Profile

storage resource pool:

A resource pool that represents storage resources available for storage resource allocation. Storage Resource Virtualization Profile

storage resource pool configuration service:

A configuration service that supports the addition or removal of host storage resources to or from a storage resource pool, and the creation or deletion of concrete subpools of a storage resource pool. Storage Resource Virtualization Profile

storage volume:

The instantiation of allocated host resources that is exposed to a virtual system through a storage device that is published for use outside of the scoping system

Like a logical disk, a storage volume is the result of a storage resource allocation based on a storage resource allocation request. Storage Resource Virtualization Profile

subclass:

A specialized class. CIM Metamodel

subject profile:

The implemented profile for which the instances of the classes defined in the Profile Registration Profile are being used to advertise profile implementation.

A profile created or verified in conformance to this guide. Management Profile Specification Usage Guide

subject virtual system:

The virtual system that is being acted upon. Virtual System Migration Profile

submission

A Participant request for Certification of Conformance Test Results for a Tested Product and any other Products the Participant claims are conformant per the same Results . DASH 2.0 Conformance Program Policies and Procedures

subscribe

The mechanism whereby a client registers for delivery of indications. Indications Profile

subscriber:

A Web service that sends requests to create, renew, and/or delete subscriptions. Web Services for Management (WS- Management) Specification

subscription:

A contract that is established between a consumer and a provider that asks the provider to deliver future generated records that match some selection criteria to the consumer. The records can be delivered in real time or on a scheduled basis; individually or in aggregated forms; or according to any other terms in the contract. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification ,

The mechanism whereby a client registers a listener for the delivery of indications from an implementation. Indications Profile

The act of registering a destination for the reception of events. Redfish Scalable Platforms Management API Specification

subscription manager:

A Web service that accepts requests to manage, get the status of, renew, and/or delete subscriptions on behalf of an event source. Web Services for Management (WS-Management) Specification

subtype:

A specialized type. CIM Infrastructure Specification

summarization:

Refers to the consolidation of multiple related events in to a single event, typically for storage, bandwidth, or other optimization purposes. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

summation metrics:

A type of counter metric that reflects the accumulation of a value. Base Metrics Profile

superclass:

A generalization of a class (i.e., a more general class). CIM Infrastructure Specification

supertype

A generalization of a type (i.e., a more general type). CIM Infrastructure Specification

suppression:

Refers to the dropping/elimination of events from an event stream or event store.

From an auditing perspective, the entity that drops the events will typically create a “meta” event indicating the count and type of event being dropped.

From a semantic perspective, suppression refers to events that have been removed from an event store, and not from a query result set. This differs from the concept of filtering, which refers to removing events from a result set returned from a query. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

System Chassis:

An instance of the CIM_PhysicalElement or CIM_Chassis that is associated to an instance of CIM_System or CIM_ComputerSystem through the CIM_SystemPackaging or CIM_ComputerSystemPackage association, representing the physical package of the managed system. Physical Asset Profile

System Management BIOS (SMBIOS):

Defines memory mapped tables, typically implemented by system firmware/BIOS and mapped into system firmware/BIOS memory space, that provide inventory and management information for the computer system. Redfish Host Interface Specification

System Management Bus (SMBus)

System Power States (S0 and Sx):

S0 represents an active system

Sx represents system power states S1 – S5 which reflects various levels of inactivity of a system.

The definition of the power states is as defined in ACPI. NC-SI over MCTP Binding Specification

system reboot:

A process whereby the firmware device, which may typically be contained within a platform that has a host operating system, is restarted. The firmware device will activate any pending firmware component images that indicated a system reboot as its activation method. Platform Level Data Model (PDLM) for Firmware Update Specification

Systems Management Architecture for Server Hardware (SMASH)

Back to Top

T

target:

The Managed Element or Association upon which a command acts. Server Management Command Line Protocol Specification (SM CLP)

target address:

A string value used as the target term in a Command Line to identify the target for a command. Server Management Command Line Protocol Specification (SM CLP)

target class addressing:

A method of selecting Managed Elements within a container based on the UFcT of the element. Server Management Command Line Protocol Specification (SM CLP)

target port:

A port that acts as a target of a data exchange operation. Storage Resource Virtualization Profile

target virtualization platform:

The destination of the virtual system being acted upon. Virtual System Migration Profile

task:

Any operation for which an RDE device cannot complete execution in the time allotted to respond to the PLDM triggering command message sent from the MC and for which the MC creates standard Redfish task and TaskMonitor objects. Platform Level Data Model (PLDM) for Redfish Device Enablement

template:

The entity that represents the set of metadata and instructions used to instantiate resources (e.g., a Machine Template is used to create Machines)

Templates may aggregate other metadata entities such as other Templates, Configurations and Images. For example, a Machine Template refers to a Machine Configuration and a Machine Image.

How a specific protocol mapping or implementation chooses to supply Templates as inputs to the instantiation process may vary. However, some common patterns should be considered:

1. By reference - allow Consumers to reference a Template (that exists as an entity in the Provider) as part of the instantiation operation.

2. By value - allow Consumers to dynamically provide the Template information as part of the instantiation operation.

3. Reference with overrides - allow Consumers to reference a Template (that exists as an entity in the Provider) and provide additional values that override the attributes of that Template as part of the instantiation operation.

The resource that represents the set of metadata and instructions used to instantiate resources (e.g., a MachineTemplate is used to create Machines). Templates may aggregate other metadata resources such as other Templates, Configurations, and Images. For example, a MachineTemplate refers to a MachineConfiguration and a MachineImage. Cloud Infrastructure Management Interface (CIMI) Model and REST Interface over HTTP

template boot configuration:

An existing instance of CIM_BootConfigSetting that is to be used as the template for creating a new boot configuration. Boot Control Profile

template privilege:

An instance of CIM_Privilege only to be used by a client as a template for creating new authorized roles or modifying the existing roles. Role Based Authorization Profile

Test Suite Authority (TSA):

The entity responsible for developing and maintaining the Conformance Test Suite and for confirming defects in the Conformance Test Suite reported as issues by Program Participants. The Test Suite Authority for this Program is the CDM Forum of the DMTF. For the DASH Conformance Program 2.0, the TSA is comprises Leadership level members of the System Management Forum.Common Diagnostics Model (CDM) Conformance Program Policies; DASH 2.0 Conformance Program Policies and Procedures

text console flow:

The bidirectional text console stream that originally flows to the Original Destination, and may be redirected to a new Text Console Flow destination, which is modeled as an instance of CIM_ProtocolEndpoint. Text Console Redirection Profile

text console redirection:

Refers to a text console redirection service session; this is composed of an instance of CIM_TextRedirectionService, an instance of CIM_TextRedirectionSAP, and the instance of the CIM_ServiceAccessBySAP between the two. Text Console Redirection Profile

text console redirection service:

The instance of CIM_TextRedirectionService that is part of a Text Console Redirection Session. Text Console Redirection Profile

text console redirection session:

The instance of CIM_TextRedirectionSAP that is part of a Text Console Redirection Session. Text Console Redirection Profile

Text Session or Text-Based Session:

An active connection to a service whereby the user can enter text-based messages and receive text-based data.

Examples of commonly used text sessions are Telnet and Secure Shell. Server Management Command Line Protocol Specification (SM CLP)

third-party authentication:

Authentication that is performed using services that execute remote to the relying, Simple Identity Management Profile

thread:

In programming, a part of a program that can execute independently of other parts Operating systems that support multithreading capabilities of processors enable programmers to design programs whose threaded parts can execute concurrently. Software Identification and Entitlement Usage Metrics

threading processor core:

Indicates the instance of CIM_ProcessorCore that represents the processor core that enables the hardware threading. CPU Profile

Transmission Unit:

Refers to the size of the portion of the MCTP packet payload, which is the portion of the message body carried in an MCTP packet. MCTP Base Specification

transport:

The layers of the communication stack responsible for reliable transportation of commands and messages between the Client and the MAP. Server Management Command Line Protocol Specification (SM CLP)

transport binding

See physical transport binding

trigger

A condition that when True, expresses the occurrence of an event. CIM Infrastructure Specification

triggering command:

The PLDM command that supplies the last bit of data needed for an RDE device to begin execution of an RDE operation. Platform Level Data Model (PLDM) for Redfish Device Enablement

trivial class adaptation:

A class adaptation that does not add requirements beyond those defined by the adapted class and, if defined, by its base adaptations. Management Profile Specification Usage Guide

truncated:

When applied to a dictionary, one that is limited to containing conversion information for properties supported by an RDE device. Platform Level Data Model (PLDM) for Redfish Device Enablement

Trusted Credential Store:

A credential store supported by a service that stores credentials used by the service to verify credentials presented to it by clients.

Such a credential store is represented by CIM_CredentialStore with the Usage property set to 3 (Trusted). Credential Management Profile

tunnel:

A path across non-routable network segments. These can be segments on different IP networks or networks using different protocols. Network Management - Tunnel Management Profile

Back to Top

U

UCS character:

A character from the Universal Character Set defined in ISO/IEC 10646:2003. See DSP0004 for the usage of UCS characters in CIM strings. An alternative term is "Unicode character. CIM-RS Payload Representation in JSON ,

A character from the Universal Multiple-Octet Coded Character Set (UCS) defined in ISO/IEC 10646. Also known as Unicode character. For an overview on UCS characters in CIM, see Common Information Model (CIM) Infrastructure. Representation of CIM in XML

UCS code position:

A numeric identification for a UCS character in the range of 0x0 to 0x10FFFF, as defined in ISO/IEC 10646:2003. CIM-RS Payload Representation in JSON

Unified Extensible Firmware Interface (UEFI):

A modern firmware standard that defines the interfaces between hardware and operating systems in a computer system. UEFI is supported on multiple processor architectures, including x86, x64, ia64, and AARCH64. Redfish Host Interface Specification

Universally Unique Identifier (UUID):

Refers to an identifier originally standardized by the Open Software Foundation (OSF) as part of the Distributed Computing Environment (DCE). UUIDs are created using a set of algorithms that enables them to be independently generated by different parties without requiring that the parties coordinate to ensure that generated IDs do not overlap. In this specification, RFC4122 is used as the base specification describing the format and generation of UUIDs. Also sometimes referred to as a globally unique identifier (GUID). MCTP Base Specification

unspecified:

Indicates that this profile does not define any constraints for the referenced CIM element or operation. Representation of CIM in XML

update agent (UA):

A PLDM endpoint (terminus) that orchestrates passing component images from a firmware update package to a firmware device. Typically this agent is contained within a management controller. Platform Level Data Model (PDLM) for Firmware Update Specification

USB redirection:

An arrangement that encompasses an instance of CIM_USBRedirectionService and an instance of CIM_USBRedirectionSAP that are joined by a CIM_ServiceAccessBySAP association. USB Redirection Profile

USB redirection SAP:

The Service Access Point for a USB Redirection Sesson as modeled by an instance of CIM_USBRedirectionSAP that is part of a USB Redirection. USB Redirection Profile

USB redirection service:

The instance of CIM_USBRedirectionService that is part of a USB Redirection. USB Redirection Profile

USB redirection session:

The context and elements of a particular USB Redirection SAP as modeled by an instance of CIM_USBRedirectionSAP. USB Redirection Profile

use case:

A named profile element that defines an interaction of an external client and an implementation in the execution of steps required to be performed in the realization of functionality defined in a profile. Management Profile Specification Usage Guide

used profile:

A referenced profile that is used by the referencing profile. Management Profile Specification Usage Guide

user:

A person who uses an IT service.

Users are distinct from customers, as some customers do not use IT services directly. Software Identification and Entitlement Usage Metrics

User-Friendly class Tag (UFcT):

A short, user-friendly alias for a CIM class name.

It has the same properties and methods as the CIM class it represents. Server Management Command Line Protocol Specification (SM CLP)

User-Friendly instance Path (UFiP):

The unique path to an instance formed by concatenating the UFiTs of each instance from the root instance to the terminating instance. Server Management Command Line Protocol Specification (SM CLP)

User-Friendly instance Tag (UFiT):

User-friendly identifier for a specific instance of a CIM class.

A User-Friendly instance Tag is constructed by concatenating an integer suffix to the UFcT for the CIM class. Server Management Command Line Protocol Specification (SM CLP)

User-Friendly selection Tag (UFsT):

Short-hand notation for selecting all instances of a given class.

A User-Friendly selection Tag is constructed by concatenating the UFcT for a class with the character *. Server Management Command Line Protocol Specification (SM CLP)

Back to Top

V

verb:

The string name of a command, used as the first term of a Command Line. Server Management Command Line Protocol Specification (SM CLP)

virtual:

As it applies to information technology, not physically existing as such but made by software to appear to do so. Software Identification and Entitlement Usage Metrics

virtual appliance:

A service delivered as a complete software stack installed on one or more virtual machines.

A virtual appliance is typically expected to be delivered in an OVF package. Open Virtualization Format Specification

virtual computer system:

Virtual system as applied to a computer system.

Other common industry terms for such a system include virtual machine, hosted computer, child partition, logical partition, domain, guest, and container. Ethernet Port Resource Virtualization Profile

virtual Ethernet switch:

The concept of a virtual system as applied to a virtual Ethernet switch.

A virtual Ethernet switch is a specialized virtual system.

A virtual Ethernet switch provides internal and external network connectivity to the virtual computer systems attached to it. A virtual Ethernet switch implements either the VEB or VEPA function. Ethernet Port Resource Virtualization Profile

virtual hardware:

The processor, memory, and I/O resources provided by a virtualization platform that supports a virtual system. Open Virtualization Format Specification

virtual machine (VM):

The virtual representation of a computing device including the CPU, memory, controllers, network interfaces, and storage that supports the execution of guest software in a virtualized environment. Software Identification and Entitlement Usage Metrics

virtual machine collection:

A collection comprised of a set of virtual machines. This service component can be a:

– simple set of one or more virtual machines, or

– complex service component built out of a combination of virtual machines and other virtual machine collections that enables nested complex service components. Open Virtualization Format Specification

virtual memory:

The instantiation of allocated host memory that is exposed to a virtual system through a logical memory device; the result of a memory resource allocation based on a memory resource allocation request

NOTE The definition of the term “virtual memory” is specialized from the term “virtual resource” and deviates from common computer industry parlance. Memory Resource Virtualization Profile

virtual network interface controller (vNIC):

An entity that performs the Media Access Control (MAC), Link Level Control (LLC), management and control functions needed to attach a VM to a network. Virtual Networking Management White Paper

virtual processor:

The instantiation of the allocated host processor resources that is exposed to a virtual system via a logical processor device. Processor Resource Virtualization Profile

virtual resource:

An allocated resource that is represented as a logical device and assigned to a virtual system. CIM System Virtualization Model White Paper

virtual resource allocation:

Resource allocation with a logical device representing the allocated resources. Resource Allocation Profile

virtual station interface (VSI):

An entity comprised of a vNIC (modeled as an Ethernet port), its internal point-to-point Ethernet connection to a virtual Ethernet switch, and the Ethernet port of the virtual Ethernet switch that is connected to the vNIC. Each VSI carries a single MAC service instance. Virtual Networking Management White Paper

virtual switch:

A software emulated virtual Ethernet switch typically implemented within the virtualization infrastructure (e.g., a Hypervisor). Virtual Networking Management White Paper

virtual system (VS):

A virtual operating system environment that includes virtual machine(s), the operating systems, and applications. The virtual system is a computer system operated in a virtualized environment that includes its software running in that environment. Software Identification and Entitlement Usage Metrics

Virtual System Collection:

A collection of virtual systems. Open Virtualization Format Specification

virtual system migration:

Process of moving a virtual system from a source virtualization platform to a target virtualization platform. Virtual System Migration Profile

virtual system migration service:

Service that provides virtual system migration facilities as defined by this standard. Virtual System Migration Profile

virtual system migration task:

Task that performs a particular virtual system migration. Virtual System Migration Profile

virtual system state:

State of a virtual system. Virtual System Migration Profile

virtualization management:

The software that performs resource allocation and management of virtual systems. Open Virtualization Format Specification

virtualization platform:

The virtualizing infrastructure provided by a host system that enables the deployment of virtual systems. Ethernet Port Resource Virtualization Profile

volatile property:

A property in a CIM instance whose value may change as a WBEM client obtains the instance repeatedly without performing any client originated updates to the property value. Generic Operations Specification

Back to Top

W

Watchdog, watchdog timer:

A timer mechanism used to monitor the health of a software or hardware entity. Platform Watchdog Profile

watermark metrics:

A type of aggregation metric used to capture the minimum or maximum value recorded for a monitored value. Base Metrics Profile

WBEM client:

A CIM client that supports a WBEM protocol.

A WBEM client originates operations for processing by a WBEM server. This definition does not imply any particular implementation architecture or scope, such as a client library component or an entire management application.

The client role in the CIM-RS protocol and in other WBEM protocols. Generic Operations Specification

WBEM indication:

An interaction within a WBEM protocol that is originated on a WBEM server and processed by a WBEM listener. Generic Operations Specification

WBEM listener:

A CIM listener that supports a WBEM protocol.

A WBEM listener processes indications originated by a WBEM server. This definition does not imply any particular implementation architecture or scope, such as a standalone demon or an entire management application.

The event listener role in the CIM-RS protocol and in other WBEM protocols. Generic Operations Specification

WBEM operations:

An interaction within a WBEM protocol that is originated by a WBEM client and processed by a WBEM server. Generic Operations Specification

WBEM protocol:

A communications protocol that defines WBEM operations between WBEM client, WBEM server and WBEM listener.

A WBEM protocol defines how the WBEM operations work, on top of an underlying protocol layer (for example, HTTP, SOAP, or TCP). Generic Operations Specification

WBEM protocol mapping:

A mapping of generic operations to a WBEM protocol. Generic Operations Specification

WBEM server:

A CIM server that supports a WBEM protocol.

A WBEM server processes operations originated by a WBEM client, and originates indications for processing by a WBEM listener. This definition does not imply any particular implementation architecture, such as a separation into a CIMOM and provider components. Generic Operations Specification

weak association:

An association that references a scoping object and weak objects, and along which the values of key properties get propagated from a scoping object to a weak object.

In the weak object, the key properties to be propagated have qualifier Propagate with an effective value of True, and the weak association has qualifier Weak with an effective value of True on its end referencing the weak object. Common Information Model (CIM) Infrastructure

weak object, weak instance, weak class:

An object (class or instance) that gets some or all of its key properties propagated from a scoping object, along a weak association. Common Information Model (CIM) Infrastructure

Web-Based Enterprise Management (WBEM):

A set of specifications published by DMTF that define how resources modeled using the DMTF’s Common Information Model (CIM) can be discovered, accessed and manipulated. WBEM provides the ability for the industry to deliver a well-integrated set of standard-based management tools, facilitating the exchange of data across otherwise disparate technologies and platforms. Web-Based Enterprise Management

Web Services Management (WS-MAN):

Provides interoperability between management applications and managed resources, and identifies a core set of web service specifications and usage requirements that expose a common set of operations central to all systems management. Web Services Management

whitespace:

One or more consecutive occurrences of any of the characters space (U+0020), carriage return (U+000D), line feed (U+000A) or horizontal tab (U+0009), consistent with the whitespace definition in the 308 W3C XML specification. Representation of CIM in XML

Wi-Fi Protected Access (WPA):

An extensible security architecture defined to replace WEP for IEEE 802.11 wireless networks. Wi-Fi Port Profile

Wired Equivalent Privacy (WEP):

A deprecated data confidentiality algorithm defined for IEEE 802.11 wireless networks. Wi-Fi Port Profile

Work In Progress:

A DMTF Document release mechanism, DMTF document status and a document phase

As a process, it is defined as a method whereby a document can be made available to the public, industry partners, and other interested parties. The purpose of this mechanism is to garner feedback before the DMTF Standard phase.

As a document status, it indicates a document proposed to be of a normative nature that addresses a specific problem domain and that has yet to be released by the DMTF as a normative nature and instead represents a snap shot of work that has not gone through any legal review.

As a document phase, it indicates that the document has been approved by a Committee but not the DMTF Board for publication only as a document of an informative nature. DMTF Process for Working Bodies

Workload:

A defined set of operations for the deployed ovf package to perform that validates the functionality and that is visible in some fashion. Profile to Enable Automated Deployment of OVF Packages

Back to Top

X

XML element:

A component of XML that is defined using the ELEMENT construct in the DTD. Representation of CIM in XML

XML instance document:

An XML document that conforms to a specified XML Schema. WS-CIM Mapping Specification

XSDL:

Offers facilities for describing the structure and constraining the contents of XML documents, including those which exploit the XML Namespace facility.

XSDL documents have the ‘.xsd’ file extension. WS-CIM Mapping Specification

Back to Top

3. Abbreviations

A

ACK (acknowledge)

ASF (Alert Standard Format)

B

BCD (binary-coded decimal)

BCV (Boot Control Vector)

BEJ (Binary Encoded JSON)

BIOS (Basic I/O System)

BMC (Baseboard Management Controller)

BSP (Board Support Package)

C

CADF (Cloud Auditing Data Federation)

CDM (Common Diagnostic Model)

CDT (Current Default Target)

CIM (Common Information Model)

CIMOM (CIM Object Manager)

CIM-RS (CIM RESTful Services)

CLP (Command Line Protocol)

CMWG (Cloud Management Working Group)

CP (Conformance Program, Program)

CPD (Conformance Program Deficiency)

CQL (CIM Query Language)

CR (Certification Registry)

CR (Change Request)

CRUD (Create, Read | Replace, Update, and Delete

CRL (Certification Revocation List)

CSD (collaboration structure diagram)

CSRF (Cross-Site Request Forgery)

CT (Common Transport)

CTS (Conformance Test Suite)

D

DA (Directory Agent)

DASH (Desktop and Mobile Architecture for System Hardware)

DDC (Display Data Channel)

DDR (Double Data Rate SDRAM)

DHCP (Dynamic Host Configuration Protocol

DMA (Direct Memory Access)

DMI (Desktop Management Interface)

DR (Document Request)

DSP (Digital Signal Processing)

DSP (DMTF Standard Publication) identifier

E

EASD (CIM_EthernetPortAllocationSettingData)

ECC (Error Checking and Correction)

EDO (Extended Data Out)

EID (Endpoint ID)

EISA (Extended Industry-Standard Architecture)

EPASD (CIM_EthernetPortAllocationSettingData)

EPS (Entry Point Structure)

ESCD (Extended System Configuration Data)

ESD (CIM_ElementSettingData)

F

FD (firmware device)

G

GPNV (General-Purpose NVRAM)

I

I2O (Intelligent Input/Output)

IaaS (Infrastructure as a Service)

IEPS (Intermediate Entry Point Structure)

INT (interpretation)

IPMB (Intelligent Platform Management Bus)

IPMI (Intelligent Platform Management Interface)

IR (Issue Report)

IRQ (Interrupt Request)

ISA (Industry Standard Architecture)

J

JSON (JavaScript Object Notation)

K

KVM-IP (Keyboard, Video, Mouse redirection over IP)

L

LIF (Low Insertion Force)

LIFO (Last In, First Out)

M

MAP (Manageability Access Point)

MCA (Micro Channel Architecture)

MCTP (Management Component Transport Protocol)

ME (managed element)

MOF (Managed Object Format)

MTU (Maximum Transmission Unit)

N

NACK (not acknowledge)

NC (Network Controller)

NC-SI (Network Controller Sideband Interface)

NMI (Non-Maskable Interrupt)

NUMA (Non-Uniform Memory Access)

NV (Non-Volatile)

NVM (Non-Volatile Memory)

NVRAM (Non-Volatile RAM)

O

OVF (Open Virtualization Format)

P

PA (Conformance Program Administrator, Program Administrator)

PCle® (PCI Express™)

PDR (Platform Descriptor Record)

PEC (Packet error code)

PM (Persistent Memory)

PMCI (Platform Management Component Intercommunications)

PSA (Persistent slave address)

PUG (Management Profile Usage Guide)

R

RDE (Redfish Device Enablement)

RPC (Remote Procedure Call)

S

S0 and Sx (System Power States)

SA (Specification Authority)

SCL (serial clock)

SDA (serial data)

SDC (CIM_SettingsDefineCapabilities)

SDS (CIM_SettingsDefineState)

SMASH (Systems Management Architecture for Server Hardware)

SMBIOS (System Management BIOS)

SM-HBA (Storage Management Host Bus Adapter)

SM ME (Server Management Managed Element)

SPNEGO (Simple and Protected GSSAPI Negotiation Mechanism)

T

TSA (Test Suite Authority)

U

UA (update agent)

UDID (Unique device identifier)

UEFI (Unified Extensible Firmware Interface)

UFcT (User-Friendly class Tag)

UFiP (User-Friendly instance Path)

UFiT (User-Friendly instance Tag)

UFsT (User-Friendly selection Tag)

UMA (Uniform Memory Access)

UUID (Universally Unique Identifier)

V

VDM (Vendor Defined Message)

VSI (virtual station interface)

W

WBEM (Web-Based Enterprise Management)

WS-MAN (Web Services Management)