Internet-Draft                                                Ryan Moats
draft-moats-dmtf-device-ldap-00.txt                     Gerald Maziarski
Expires in six months                                               AT&T
                                                          John Strassner
                                                           cisco Systems
                                                          September 1999

               LDAP Schema for the DMTF Device CIM Model
             Filename: draft-moats-dmtf-device-ldap-00.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Abstract

   This draft presents a LDAP schema for the DMTF CIM Device model [7].

1. Introduction

   This draft presents a LDAPv3 [1,2] schema for the DMTF CIM Device
   model.  It builds on the core model presented in [3].  Associations
   are mapped using a combination of auxiliary classes and DIT structure
   rules.  Where auxiliary classes are used, name form and DIT content
   rules are specified.

   Certain objects in the CIM Device model have not been represented in
   this schema.  The classes IRQ, MemoryMappedIO, and DMA are not
   included because they do not make sense for storage in a directory.
   Therefore, the associations ComputerSystemIRQ,
   ComputerSystemMappedIO, ComputerSystemDMA, and AllocatedDMA are also

Expires 3/31/00                                                 [Page 1]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   not included.

   The objects and associations VideoBIOSFeature, VideoBIOSElement, and
   VideoBIOSFeatureVideoBIOSElement are not included.

   PrintQueue and PrintJob are not included because of thier inherent
   dynacism.  This results in the associations PrinterServicingQueue,
   QueueForPrintService, QueueForwardsToPrintSAP, PrinterServicingJob,
   PrintJobFile, and OwningPrintQueue not being included.

   All of the sensor classes (BinarySensor, MultiStateSensor,
   DiscreteSensor, NumericSensor, TempatureSensor, CurrentSensor,
   VoltageSensor, Tachometer) were deemed too dynamic for a directory.
   Therefore, the associations CollectionOfSensors,
   AssociatedSupplyVoltageSensor, and AssociatedSupplyCurrentSensor are
   also not included.

   Because FCAdapterEventCounters and FibrePortEventCounters have
   nothing but counters in them, they are not included in the schema.
   Further, because USBDevice claims to be only management, it is not
   included in this schema and so USBHub, USBPortOnHub,
   USBControllerHasHub, and USBConnection are not included.

   Processor and ComputerSystemProcessor are not included because they
   do not make sense in a directory.  The StorageExtent-related classes
   and media transfer classes were not included for similar reasons.

2. Class Definitions

   For efficiency in the LDAP representation, associations are specified
   as a combination of auxiliary classes and DIT structure rules.
   Attribute definitions for each class are presented with the object
   class.  Other definitions are also provided when necessary.

   While this approach was chosen to minimize the number of DN pointers
   stored in the schema, some pointer dereferencing is necessary.  While
   not explicitly stated, all DN pointers are assumed to support the
   extended matching rule defined in [4].  Attribute names for DN
   pointers follow the convention that a single pointer to "foo" is
   named "fooRef" while an array of pointers would be named "fooRefs."

   Note: all OIDs are placeholders, and OIDs in definitions have been
   replaced by names for clarity.

2.1 dmtfDeviceConnectionAuxClass Association

   The class shows that two or more devices are connected together and
   so both antecedentRefs and dependentRefs point to dmtfLogicalDevice

Expires 3/31/00                                                 [Page 2]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   objects.  Further, it defines the attributes negotiatedSpeed (the
   speed between the two devices), and negotiatedDataWidth (the data
   width between the two devices).

      ( <oid-at82> NAME 'negotiatedSpeed'
        DESC 'When several bus and/or connection speeds are possible, the
              NegotiatedSpeed property defines the one in use between the
              Devices. Speed is specified in bits per second. If
              connection or bus speeds are not negotiated, or if this
              information is not available/important to Device
              management, the property should be set to 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at83> NAME 'negotiatedDataWidth'
        DESC 'When several bus and/or connection data widths are
              possible, the NegotiatedDataWidth property defines the one
              in use between the Devices. Data width is specified in
              bits. If data width is not negotiated, or if this
              information is not available/important to Device
              management, the property should be set to 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc52> NAME 'dmtfDeviceConnectionAuxClass'
        DESC 'shows that two or more Device are connected together.'
        SUP  dmtfDependencyAuxClass AUXILIARY
        MUST (negotiatedSpeed $ negotiatedDataWidth)
      )

2.2 dmtfDeviceIdentityAuxClass

   This association shows that two logical devices represent different
   aspects of the same underlying entity.  This association refines the
   logical identity superclass by restricting it to the device level and
   defining its use in well understood scenarios. One of these scenarios
   is to represent that a device is both a 'bus' entity and a
   'functional' entity. For example, a device could be both a PCI device
   (or an USB device), as well as a keyboard. The other scenario is a
   device having multiple functional roles that can not be distinguished
   by their hardware realization alone. For example, a Fiber Channel
   adapter might have aspects of both a NetworkAdapter and a
   SCSIController.  In this class, the attributes systemElementRefs and
   sameElementRefs both point to dmtfLogicalDevice Objects.

      ( <oid-oc53> NAME 'dmtfDeviceIdentityAuxClass'
        DESC 'shows that two LogicalDevices represent different
              aspects of the same underlying entity.'

Expires 3/31/00                                                 [Page 3]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SUP dmtfLogicalIdentityAuxClass AUXILIARY
      )

2.3 dmtfSystemResource Class

   This class provides the parent class for any entity that is both
   available for use by software and/or logical devices.  It defines the
   attribute sharable, which is documented below.

      ( <oid-at84> NAME 'sharable'
        DESC 'Boolean showing whether the Resource can be shared.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc54> NAME 'dmtfSystemResource'
        DESC 'An entity managed by BIOS and/or an OperatingSystem that
              is available for use by software and/or
              LogicalDevices.'
        SUP  dmtfLogicalElement ABSTRACT
        MUST (sharable)
      )

2.4 dmtfComputerResouceAuxClass Association

   This is a subclass of the dmtfSystemComponentAuxClass association. In
   it, groupRefs must point to a dmtfComputerSystem object and partRefs
   must point to a dmtfSystemResource object.

      ( <oid-oc55> NAME 'dmtfComputerSystemResourceAuxClass'
        DESC 'An association between a ComputerSystem and the
              SystemResources available on it.'
        SUP  dmtfSystemComponentAuxClass AUXILIARY
      )

2.5 dmtfAllocatedResourceAuxClass

   This subclass of dmtfDependencyAuxClass represents the association
   between logical devices and system resources.  The association is
   that the resource is assigned to the device.  In this association,
   antecedentRefs points to a dmtfSystemResource object and
   dependentRefs point to a dmtfLogicalDevice object.

      ( <oid-oc56> NAME 'dmtfAllocatedResourceAuxClass'
        DESC 'An association between LogicalDevices and SystemResources,
              showing that the Resource is assigned to the Device.'
        SUP  dmtfDependencyAuxClass AUXILIARY
      )

Expires 3/31/00                                                 [Page 4]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.6 dmtfDeviceServiceImplementationAuxClass

   This class represents the association between a Service and how it is
   implemented. The cardinality of this association is many-to-many. A
   service may be provided by more than one logical device, operating in
   conjunction. Further, any device may provide more than one service.
   When multiple devices are associated with a single service, it is
   assumed that these elements operate in conjunction to provide the
   service. If different implementations of a service exist, each of
   these implementations would result in individual instantiations of
   the service object. These individual instantiations would then have
   associations to the unique implementations.  In this class,
   antecedentRefs point to dmtfLogicalDevice objects and dependentRefs
   point to dmtfService objects.

      ( <oid-oc57> NAME 'dmtfDeviceServiceImplementationAuxClass'
        DESC 'An association between a Service and how it is implemented.'
        SUP  dmtfDependencyAuxClass AUXILIARY
      )

2.7 dmtfDeviceSAPImplementationAuxClass

   An association between a service access point and how it is
   implemented. The cardinality of this association is many-to-many. A
   SAP may be provided by more than one logical device, operating in
   conjunction. Further, any device may provide more than one service
   access point. When many logical devices are associated with a single
   SAP, it is assumed that these elements operate in conjunction to
   provide the access point. If different implementations of a SAP
   exist, each of these implementations would result in individual
   instantiations of the service access point object. These individual
   instantiations would then have associations to the unique
   implementations.  In this class, antecedentRefs point to
   dmtfLogicalDevice objects and dependentRefs point to
   dmtfServiceAccessPoint objects.

      ( <oid-oc58> NAME 'dmtfDeviceSAPImplementationAuxClass'
        DESC 'An association between a ServiceAccessPoint and how it is
              implemented.'
        SUP  dmtfDependencyAuxClass AUXILIARY
      )

2.8 dmtfDeviceErrorCounts object

   This object represents a statistical class containing error-related
   counters for a logical device. The types of errors are as defined by
   CCITT (Rec X.733) [5] and ISO (IEC 10164-4) [6].  This class reuses
   the attributes deviceCreationClassName, systemCreationClassName,

Expires 3/31/00                                                 [Page 5]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   systemName, and deviceID.

      ( <oid-oc59> NAME 'dmtfDeviceErrorCounts'
        DESC 'error-related counters for a LogicalDevice.'
        SUP  dmtfStatisticalInformation
        MUST (systemCreationClassName $ systemName $
              deviceCreationClassName $ deviceID $ name)
      )

   Although systemCreationClassName, systemName,
   deviceCreationClassName, deviceID and name all may be used as RDNs,
   it is recommended that this class be stored in the DIT according to
   the following structural rule and name forms.

      ( 21 NAME 'dmtfErrorCountersForDeviceStructureRule'
        FORM dmtfStatsNameForm
        SUP 1 2
      )

      ( <oid-nf21> NAME 'dmtfStatsNameForm'
        OC dmtfStats
        MUST (name)
      )

2.9 dmtfDeviceSoftwareAuxClass

   This relationship identifies any software that is associated with a
   device - such as drivers, configuration or application software, or
   firmware.  In this class, antecedentRefs point to dmtfSoftwareElement
   objects and dependentRefs point to dmtfLogicalDevice objects.  This
   class further defines the attributes purpose, purposeDescription,
   loadedOnDevice, and upgradeableOnDevice to explain the role of the
   software regarding the device.

      ( <oid-at85> NAME 'purpose'
        DESC 'An enumerated integer to show the role this software
              plays regarding its associated Device. For example,
              this software could be instrumentation (value=5) or
              firmware (6).  Allowed values are: "Unknown", "Other",
              "Driver", "Configuration Software", "Application Software",
              "Instrumentation", "Firmware".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at86> NAME 'purposeDescription'
        DESC 'A free-form string to provide more information for the
              Purpose property, e.g. "Application Software".'
        SYNTAX string SINGLE-VALUE

Expires 3/31/00                                                 [Page 6]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at87> NAME 'loadedOnDevice'
        DESC 'Boolean indicating that the software is "burned into" or
              otherwise located on the hardware of the LogicalDevice.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at88> NAME 'upgradeableOnDevice'
        DESC 'Boolean indicating whether the software is upgradeable,
              when it is LoadedOnDevice.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc60> NAME 'dmtfDeviceSoftwareAuxClass'
        DESC 'The DeviceSoftware relationship identifies any software
              that is associated with a Device.'
        SUP  dmtfDependencyAuxClass AUXILIARY
        MUST (purpose $ purposeDescription)
      )

2.10 dmtfRedundancyGroup Class

   This class is derived from dmtfLogicalElement and represents a
   special collection of managed system elements that together provide
   redundancy.  Therefore, all elements aggregated in this class should
   be from the same object class. This class uses the attributes
   creationClassName, name and defines the attribute redundancyStatus.

      ( <oid-at89> NAME 'redundancyStatus'
        DESC 'RedundancyStatus provides information on the state of the
              RedundancyGroup. "Fully Redundant" all the configured
              redundancy is still available; "Degraded Redundancy" been
              experienced but some reduced amount of redundancy is still
              available; "Redundancy Lost" enough failures
              have been experienced such that no redundancy is available
              and the next failure experienced will cause overall
              failure. Also, the values, "Other" (0), are defined.
              Allowed values are: "Unknown", "Other", "Fully Redundant",
              "Degradededundancy", "Redundancy Lost".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc61> NAME 'dmtfRedundancyGroup'
        DESC 'A class derived from LogicalElement that is a special
              collection of ManagedSystemElements. This collection
              shows that the aggregated components together provide
              redundancy. All elements aggregated in a RedundancyGroup

Expires 3/31/00                                                 [Page 7]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              should be instantiations of the same object class.'
        SUP  dmtfLogicalElement
        MUST (creationClassName $ name $ redundancyStatus)
      )

2.11 dmtfRedundancyComponentAuxClass

   A redundancy group aggregates managed system elements and shows that
   these elements, taken together, provide redundancy. All elements
   aggregated in a redundancy group should be instantiations of the same
   object class. In this class, groupRefs points to dmtfRedundancyGroup
   objects while partRefs maintains its default definition from
   dmtfComponentAuxClass.

      ( <oid-oc62> NAME 'dmtfRedundancyComponentAuxClass'
        DESC 'A RedundancyGroup aggregates Managed System Elements and
              shows that these elements, taken together, provide
              redundancy.'
        SUP  dmtfComponentAuxClass AUXILIARY
      )

2.12 dmtfSpareGroup

   Derived from RedundancyGroup, this class shows that one or more of
   the aggregated elements act as spares for the others. An example is
   the use of redundant NICs in a computer system - where one NIC is
   primary and the other is spare.

      ( <oid-oc63> NAME 'dmtfSpareGroup'
        DESC 'A class derived from RedundancyGroup indicating that one or
        more of the aggregated elements act as spares for the others.'
        SUP  dmtfRedundancyGroup
      )

2.13 dmtfActsAsSpareAuxClass

   This auxiliary class shows those elements can spare or replace the
   other aggregated elements.  Whether a spare can operate in "hot
   standby" mode is specified on an element by element basis. In this
   class groupRefs points to the dmtfSpareGroup object, spareRefs points
   to the managed system element acting as a spare and hotStandby shows
   if the spare is operating as a hotStandby or not.

      ( <oid-at90> NAME 'spareRefs'
        DESC 'A ManagedSystemElement acting as a spare and participating
              in the SpareGroup.'
        SYNTAX DN SINGLE-VALUE
      )

Expires 3/31/00                                                 [Page 8]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at91> NAME 'hotStandby'
        DESC 'boolean indicating that the spare is operating as a hot
              standby.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc64> NAME 'dmtfActsAsSpareAuxClass'
        DESC 'The ActsAsSpare association shows those elements can
              spare or replace the other aggregated elements.'
        SUP top AUXILIARY
        MUST (groupRefs $ spareRefs $ hotStandby)
      )

2.14 dmtfStorageRedundancyGroup

   This class is derived from redundancy group and contains mass
   storage-related redundancy information. Storage redundancy groups are
   used to protect user data. They are made up of one or more physical
   extents, or one or more dmtfAggregatePExtents. While storage
   redundancy groups may overlap, the underlying extents within the
   overlap should not contain any check data.  The attributes
   typeOfAlgorithm, storageRedundancy, isStriped and isConcatenated are
   defined.

      ( <oid-at92> NAME 'typeOfAlgorithm'
        DESC 'The TypeOfAlgorithm specifies the algorithm used for data
              redundancy and reconstruction. For example, "P+Q"=5) or
              "P+S"valid in the CIM Schema since in DMI it represents
              that no redundancy exists. Here, the object should
              not be instantiated.  Allowed values are: "Undefined",
              "Other", "Unknown", "Copy", "XOR", "P+Q", "S", and "P+S".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at93> NAME 'storageRedundancy'
        DESC 'StorageRedundancy provides additional information on the
              state of the RedundancyGroup, beyond the RedundancyStatus
              property.  Allowed values are: "No Additional Status",
              "Reconfig In Progress", "Data Lost",
           "Not Currently Configured", "Protected Rebuild",
           "Redundancy Disabled", "Unprotected Rebuild",
           "Recalculating", and "Verifying".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at94> NAME 'isStriped'
        DESC 'True shows that the data is striped across the various
              StorageExtents in the Group.'

Expires 3/31/00                                                 [Page 9]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at95> NAME 'isConcatenated'
        DESC 'True shows that the data is concatenated across the
              various StorageExtents in the Group.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc65> NAME 'dmtfStorageRedundancyGroup'
        DESC 'contains mass storage-related redundancy information.'
        SUP  dmtfRedundancyGroup
        MUST (typeOfAlgorithm $ storageRedundancy $ isStriped $
              isConcatenated)
      )

2.15 dmtfExtraCapacityGroup

   A class derived from dmtfRedundancyGroup indicating that the
   aggregated elements have more capacity or capability than is needed.
   An example of this type of redundancy is the installation of N+1
   power supplies or fans in a system.  This class defines the attribute
   minNumberNeeded, which shows the smallest number of elements that
   must be operating to maintain redundancy and the attribute
   loadBalancedGroup, which shows if load balancing is supported.

      ( <oid-at96> NAME 'minNumberNeeded'
        DESC 'MinNumberNeeded shows the smallest number of elements
              that must be operational to have redundancy. For
              example, in an N+1 redundancy relationship, the
              MinNumberNeeded property should be set equal to N.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at97> NAME 'loadBalancedGroup'
        DESC 'Boolean indicating whether load balancing is supported by
              the ExtraCapacityGroup.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc66> NAME 'dmtfExtraCapacityGroup'
        DESC 'A class derived from RedundancyGroup indicating that the
              aggregated elements have more capacity or capability than
              is needed.'
        SUP  dmtfRedundancyGroup
        MUST (minNumberNeeded $ loadBalancedGroup)
      )

Expires 3/31/00                                                [Page 10]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.16 dmtfLogicalPort

   This class represents the abstraction of a port or connection point
   of a device.  This object should be instantiated when the Port has
   independent management characteristics from the Device that includes
   it.  This class defines the attributes speed and maxSpeed, both of
   which store speed information in bits per second.

      ( <oid-at98> NAME 'speed'
        DESC 'The speed of the Port in Bits per Second.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at99> NAME 'maxSpeed'
        DESC 'The max speed of the Port in Bits per Second.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc67> NAME 'dmtfLogicalPort'
        DESC 'abstraction of a port or connection point of a Device.'
        SUP dmtfLogicalDevice
        MUST (speed $ maxSpeed)
      )

2.17 dmtfPortOnDeviceAuxClass

   This auxiliary class allows a port to be associated with its device
   and so antecedentRefs point to logicalDevice objects and
   dependentRefs point to logicalPort objects.

      ( <oid-oc68> NAME 'dmtfPortOnDeviceAuxClass'
        DESC 'associates a Port or connection point with its Device.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

2.18 dmtfPrinter

   This class holds the capabilities for a printer logical device.

      ( <oid-at100> NAME 'printerStatus'
        DESC 'Status information for a Printer, beyond that specified in
              the LogicalDevice Availability property.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at101> NAME 'detectedErrorState'
        DESC 'Printer error information.  Allowed values are: "Unknown",
              "Other", "No Error", "Low Paper", "No Paper", "Low Toner",

Expires 3/31/00                                                [Page 11]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              "No Toner", "Door Open", "Jammed", "Offline",
              "Service Requested", "Output Bin Full".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at102> NAME 'errorInformation'
        DESC 'An array providing supplemental information for the current
              error state, shown in DetectedErrorState.'
        SYNTAX string
      )

      ( <oid-at103> NAME 'paperSizesSupported'
        DESC 'An integer array indicating the types of paper supported.
              Allowed values are: "Unknown", "Other", "A", "B", "C", "D",
              "E", "Letter", "Legal", "NA-10x13-Envelope",
              "NA-9x12-Envelope", "NA-Number-10-Envelope",
              "NA-7x9-Envelope", "NA-9x11-Envelope", "NA-10x14-Envelope",
              "NA-Number-9-Envelope", "NA-6x9-Envelope",
              "NA-10x15-Envelope", "A0", "A1", "A2", "A3", "A4", "A5",
              "A6", "A7", "A8", "A9" "A10", "B0", "B1", "B2", "B3", "B4",
              "B5", "B6", "B7", "B8", "B9", "B10", "C0", "C1", "C2" "C3",
              "C4", "C5", "C6", "C7", "C8", "ISO-Designated", "JIS B0",
              "JIS B1", "JIS B2", "JIS B3", "JIS B4", "JIS B5", "JIS B6",
              "JIS B7", "JIS B8", "JIS B9", "JIS B10".'
        SYNTAX integer
      )

      ( <oid-at104> NAME 'languagesSupported'
        DESC 'An array indicating the print languages natively supported.'
        SYNTAX integer
      )

      ( <oid-at105> NAME 'paperTypesAvailable'
        DESC 'An array of free-form strings specifying the types of paper
              that are currently available on the Printer. Each string
              should be expressed in the form specified by ISO/IEC 10175
              Document Printing Application (DPA) which is also
              summarized in Appendix C of RFC 1759 (Printer
              MIB).
        SYNTAX string
      )

      ( <oid-at106> NAME 'defaultPaperType'
        DESC 'Specifies the paper type that the Printer will use if a
              PrintJob does not specify a particular type. The string
              should be expressed in the form specified by ISO/IEC 10175
              Document Printing Application (DPA) which is also
              summarized in Appendix C of RFC 1759 (Printer MIB).'

Expires 3/31/00                                                [Page 12]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at107> NAME 'currentPaperType'
        DESC 'Specifies the paper type that the Printer is currently
              using. The string should be expressed in the form specified
              by ISO/IEC 10175 Document Printing Application (DPA) which
              is also summarized in Appendix C of RFC 1759 (Printer
              MIB).'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at108> NAME 'languagesSupported'
        DESC 'An array indicating the print languages natively
              supported.'
        SYNTAX integer
      )

      ( <oid-at109> NAME 'mimeTypesSupported'
        DESC 'An array of free-form strings providing more detailed
              explanations of any mime types that are supported by the
              Printer.'
        SYNTAX string
      )

      ( <oid-at110> NAME 'currentLanguage'
        DESC 'Shows the current printer language being used. A
              language that is being used by the Printer should also be
              listed in the languagesSupported attribute.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at111> NAME 'currentMimeType'
        DESC 'Specifies the mime type currently being used by the Printer
              if the CurrentLanguage is set to show a mime type is in
              use (value = 47).'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at112> NAME 'defaultLanguage'
        DESC 'Shows the default printer language. A language that is
              used as a default by the Printer should also be listed in
              LanguagesSupported.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at113> NAME 'defaultMimeType'
        DESC 'Specifies the default mime type used by the Printer if the

Expires 3/31/00                                                [Page 13]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              DefaultLanguage is set to show a mime type is in use
              (value=47).'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at114> NAME 'timeOfLastReset'
        DESC 'Time of last reset of the Printer Device.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-at115> NAME 'capabilities'
        DESC 'An array of integers indicating Printer
              capabilities. Allowed values are: "Unknown", "Other",
              "Color Printing", "Duplex Printing", "Copies", "Collation",
              "Stapling", and "Transparency Printing".'
        SYNTAX integer
      )

      ( <oid-at116> NAME 'capabilityDescriptions'
        DESC 'An array of free-form strings providing more detailed
              explanations for any of the Printer features shown in
              the Capabilities array.'
        SYNTAX string
      )

      ( <oid-at117> NAME 'defaultCapabilities'
        DESC 'Specifies those finishings and other capabilities of the
              Printer will be used by default. An entry in
              DefaultCapabilities should also be listed in the
              Capabilities array.  Allowed values are:"Unknown", "Other",
              "Color Printing", "Duplex Printing", "Copies", "Collation",
              "Stapling", "Transparency Printing", "Punch", "Cover",
              "Bind", "Black and White Printing", "One Sided",
           "Two Sided Long Edge", "Two Sided Short Edge", "Portrait",
              "Landscape", "Reverse Portrait", "Reverse Landscape",
              "Quality High", "Quality Normal", "Quality Low".'
        SYNTAX integer
      )

      ( <oid-at118> NAME 'currentCapabilities'
        DESC 'Specifies those finishings and other capabilities of the
              Printer are currently being used. An entry in this
              property should also be listed in the Capabilities array.
              Allowed values are: "Unknown", "Other", "Color Printing",
              "Duplex Printing", "Copies", "Collation", "Stapling",
              "Transparency Printing", "Punch", "Cover", "Bind",
              "Black and White Printing", "One Sided",
              "Two Sided Long Edge", "Two Sided Short Edge", "Portrait",

Expires 3/31/00                                                [Page 14]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              "Landscape", "Reverse Portrait", "Reverse Landscape",
              "Quality High", "Quality Normal", "Quality Low".'
        SYNTAX integer
      )

      ( <oid-at119> NAME 'maxCopies'
        DESC 'The maximum number of copies that can be produced by the
              Printer from a single Job.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at120> NAME 'defaultCopies'
        DESC 'The number of copies that will be produced for a single
              Job unless otherwise specified.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at121> NAME 'maxNumberUp'
        DESC 'The maximum number of print-stream pages that the Printer
              can render onto a single media sheet.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at122> NAME 'defaultNumberUp'
        DESC 'The number of print-stream pages that the Printer will
              render onto a single media sheet unless a Job specifies
              otherwise.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at123> NAME 'horizontalResolution'
        DESC 'horizontal resolution'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at124> NAME 'verticalResolution'
        DESC 'vertical resolution'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at125> NAME 'charSetsSupported'
        DESC 'Identifies the available character sets for the output of
              text related to managing the Printer. Strings provided in
              this property should conform to the semantics and syntax
              specified by section 4.1.2 of the IANA character-set
              registry. Examples include "utf-8" and "iso-8859-1".'
        SYNTAX string
      )

Expires 3/31/00                                                [Page 15]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at126> NAME 'currentCharSet'
        DESC 'Specifies the current character set being used for the
              output of text relating to management of the Printer. The
              character set described by this property should also be
              listed in CharsetsSupported. The string specified by this
              property should conform to the semantics and syntax
              specified by section 4.1.2 of the IANA character-set
              registry. Examples include "utf-8" and "iso-8859-1".'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at127> NAME 'naturalLanguagesSupported'
        DESC 'Identifies the available languages for strings used by the
              Printer for the output of management information. The
              strings should conform to RFC 1766, for example "en".'
        SYNTAX string
      )

      ( <oid-at128> NAME 'currentNaturalLanguage'
        DESC 'Identifies the current language being used by the Printer
              for management. The language listed in the
              CurrentNaturalLanguage property should also be listed in
              NaturalLanguagesSupported.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at129> NAME 'maxSizeSupported'
        DESC 'Specifies the largest Job (as a byte stream) that the
              Printer will accept in units of Kbytes. A value of zero
              shows that no limit has been set.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at130> NAME 'availableJobSheets'
        DESC 'Describes all the job sheets that are available on the
              Printer. This can also be used to describe the banner that
              a Printer might provide at the beginning of each Job, or
              can describe other user specified options.'
        SYNTAX string
      )

      ( <oid-at131> NAME 'markingTechnology'
        DESC 'Specifies the marking technology used by the Printer.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc69> NAME 'dmtfPrinter'
        DESC 'Capabilities of the Printer LogicalDevice.'

Expires 3/31/00                                                [Page 16]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SUP  dmtfLogicalDevice
        MUST (printerStatus $ detectedErrorState $ errorInformation $
              paperSizesSupported $ paperTypesAvailable $
              defaultPaperType $ currentPaperType $ languagesSupported $
              mimeTypesSupported $ currentLanguage $ currentMimeType $
              defaultLanguage $ defaultMimeType $
              timeOfLastReset $ capabilities $
              capabilityDescriptions $ defaultCapabilities $
              currentCapabilities $ maxCopies $ defaultCopies $
              maxNumberUp $ defaultNumberUp $ horizontalResolution $
              verticalResolution $ charSetsSupported $ currentCharSet $
              naturalLanguagesSupported $ currentNaturalLanguage $
              maxSizeSupported $ availableJobSheets $ markingTechnology)
      )

2.19 dmtfPrintSAP

   This class represents the service access point for a printing
   service. It defines the attributes printProtocol and
   printProtocolInfo, which contain information about the print protocol
   this access point uses.

      ( <oid-at132> NAME 'printProtocol'
        DESC 'Specifies the print procotols that this AccessPoint uses.
              Allowed values are: "Unknown", "Other", "SMB", "BSD",
              "SYSV","HPNP","IPP", and "Local".'
        SYNTAX integer
      )

      ( <oid-at133> NAME 'printProtocolInfo'
         DESC 'Provides clarifying or additional information about the
               protocols supported by this AccessPoint.'
         SYNTAX string
      )

      ( <oid-oc70> NAME 'dmtfPrintSAP'
        DESC 'The ServiceAccessPoint for a printing Service.'
        SUP  dmtfServiceAccessPoint
        MUST (printProtocol $ printProtocolInfo)
      )

2.20 dmtfPrintService

   The service that provides support for printing. The basic assumption
   of the printing model is that a print service accepts a print job for
   processing, via its print SAP.  It reuses the attributes
   paperTypesAvailable, languagesSupported, mimeTypesSupported,

Expires 3/31/00                                                [Page 17]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   capabilities, capabilityDescriptions and defines availableFilters.
      ( <oid-at134> NAME 'availableFilters'
        DESC 'Describes the filters that are available within this
              print service. For example, a print service may be able to
              convert a job submitted in one page description language to
              another, so that it can be passed to an available Printer.'
        SYNTAX string
      )

      ( <oid-oc71> NAME 'dmtfPrintService'
        DESC 'The Service that provides support for printing.'
        SUP  dmtfService
        MUST (paperTypesAvailable $ languagesSupported $
              mimeTypesSupported $ capabilities $ capabilityDescriptions $
              availableFilters)
      )

2.21 dmtfSensor Class

   This class is the parent class for hardware devices capable of
   measuring the characteristics of some physical property.

      ( <oid-at135> NAME 'sensorType'
        DESC 'The Type of the Sensor'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at136> NAME 'otherSensorTypeDescription'
        DESC 'A string describing the Sensor type - used when the
              SensorType property is set to "Other".'
        SYNTAX string{128} SINGLE-VALUE
      )

      ( <oid-at137> NAME 'possibleStates'
        DESC 'PossibleStates enumerates the string outputs of the
              Sensor.'
        SYNTAX string{128}
      )

      ( <oid-at138> NAME 'currentState'
        DESC 'The current state shown by the Sensor. This is always
              a "PossibleStates".'
        SYNTAX string{128}
        SINGLE-VALUE
      )

      ( <oid-at139> NAME 'pollingInterval'
        DESC 'The polling interval that the Sensor hardware or the

Expires 3/31/00                                                [Page 18]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              instrumentation uses to determine the current state of the
              Sensor.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc72> NAME 'dmtfSensor'
        DESC 'A Sensor is a hardware device capable of measuring the
              characteristics of some physical property - for example,
              the temperature or voltage characteristics of a
              UnitaryComputerSystem.'
        SUP  dmtfLogicalDevice ABSTRACT
        MUST (sensorType $ otherSensorTypeDescription $ possibleStates $
              currentState $ pollingInterval)
      )

2.22 dmtfAssociatedSensorAuxClass

   This subclass of dmtfDependencyAuxClass represents a device that have
   sensors that measure critical input and output properties.  In this
   class antecedentRefs point to dmtfSensor objects and dependentRefs
   point to dmtfLogicalDevice objects.

      ( <oid-oc73> NAME 'dmtfAssociatedSensorAuxClass'
        DESC 'Many Devices include Sensors or have Sensors installed
              nearby. This association shows that relationship.'
        SUP  dmtfDependencyAuxClass AUXILIARY
      )

2.23 dmtfWatchdog

   This represents a timer implemented in system hardware. It allows the
   hardware to monitor the state of a software component installed on
   the System. If the monitored component fails to re-arm the timer
   before its expiration, the hardware assumes that the System is in a
   critical state, and could reset the ComputerSystem. This feature can
   also be used as an application watchdog timer for a mission-critical
   application. Here, the application would assume responsibility for
   re-arming the timer before expiration.

      ( <oid-at140> NAME 'monitoredEntity'
        DESC 'The entity that is currently being monitored by the
              WatchDog.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at141> NAME 'monitoredEntityDescription'
        DESC 'A string describing more textual information about the
              monitored entity.'

Expires 3/31/00                                                [Page 19]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SYNTAX string{256} SINGLE-VALUE
      )

      ( <oid-at142> NAME 'timeoutInterval'
        DESC 'The timeout interval used by the watchdog, in
              MicroSeconds.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at143> NAME 'timerResolution'
        DESC 'Resolution of the timer. For example, if this value is 100,
              then the timer can expire any time between
              (TimeoutInterval-100) microseconds or (TimeoutInterval+100)
              microseconds.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at144> NAME 'timeOfLastExpiration'
        DESC 'The time of the last timer expiry.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-at145> NAME 'monitoredEntityOnLastExpiration'
        DESC 'Monitored entity at the time of last timer expiry.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at146> NAME 'actionOnExpiration'
        DESC 'The action that should happen on the expiry of the
              watchdog.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc74> NAME 'dmtfWatchdog'
        DESC 'watchdog timer model'
        SUP  dmtfLogicalDevice
        MUST (monitoredEntity $ monitoredEntityDescription $
              timeoutInterval $ timerResolution $ timeOfLastExpiration $
              monitoredEntityOnLastExpiration $ actionOnExpiration)
      )

2.24 dmtfCoolingDevice class

   This class shows the capabilities of a cooling device.  It defines
   the attribute activeCooling, which shows if the device provides
   active or passive cooling.

      ( <oid-at147> NAME 'activeCooling'

Expires 3/31/00                                                [Page 20]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        DESC 'ActiveCooling is a boolean indicating that the
              CoolingDevice provides active (as opposed to passive)
              cooling.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc75> NAME 'dmtfCoolingDevice'
        DESC 'Capabilities of CoolingDevices.'
        SUP  dmtfLogicalDevice
        MUST (activeCooling)
      )

2.25 dmtfRefrigeration Class

   This class is the parent class for refrigeration cooling devices

      ( <oid-oc76> NAME 'dmtfRefrigeration'
        DESC 'Capabilities of a Refrigeration
              CoolingDevice.'
        SUP  dmtfCoolingDevice
      )

2.26 dmtfHeatPipe Class

   This class is the parent class for heat pipe cooling devices.

      ( <oid-oc77> NAME 'dmtfHeatPipe'
        DESC 'Capabilities of a HeatPipe CoolingDevice.'
        SUP  dmtfCoolingDevice
      )

2.27 dmtfFan Class

   This class is the parent class for Fan cooling devices. It defines
   the attributes variableSpeed (indicating if variable speeds are
   supported) and desiredSpeed (the desired fan speed).

      ( <oid-at148> NAME 'variableSpeed'
        DESC 'Indication of whether the fan supports variable speeds.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at149> NAME 'desiredSpeed'
        DESC 'DesiredSpeed is the currently requested fan speed, defined
              in Revolutions per Minute, when a variable speed fan is
              supported (VariableSpeed boolean = TRUE)'
        SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 21]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-oc78> NAME 'dmtfFan'
        DESC 'Capabilities of a Fan CoolingDevice.'
        SUP  dmtfCoolingDevice
        MUST (variableSpeed $ desiredSpeed)
      )

2.28 dmtfAssociatedCoolingAuxClass

   This auxiliary class shows where fans or other cooling devices are
   specific to a particular device rather than providing cooling for an
   entire enclosure or cabinet. In it, antecedentRefs points to
   dmtfCoolingDevice objects and dependentRefs points to
   dmtfLogicalDevice objects.

      ( <oid-oc79> NAME 'dmtfAssociatedCoolingAuxClass'
        DESC 'This association shows where fans or other
              CoolingDevices are specific to a Device, versus providing
              enclosure or cabinet cooling.'
        SUP  dmtfDependencyAuxClass AUXILIARY
      )

2.29 dmtfUserDevice Class

   This class represents logical devices that allow a computer system's
   users to input, view or hear data and is the parent class from which
   other classes, such as keyboard or desktop monitor, descend.  It
   defines the attribute isLocked, which shows whether the device is
   locked (i.e. preventing user input or output).

      ( <oid-at150> NAME 'isLocked'
        DESC 'An indication of whether the Device is locked'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc80> NAME 'dmtfUserDevice'
        DESC 'UserDevices are LogicalDevices that allow a
              ComputerSystem's users to input, view or hear data. It is a
              superclass from which other classes, such as Keyboard or
              DesktopMonitor, descend.'
        SUP  dmtfLogicalDevice ABSTRACT
        MUST (isLocked)
      )

2.30 dmtfPointingDevice

   This class represents those devices used to "point" to regions of a
   display and defines the attributes pointingType, numberOfButtons,
   handedness, and resolution, which are all self-explanatory.

Expires 3/31/00                                                [Page 22]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at151> NAME 'pointingType'
        DESC 'The type of the pointing device.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at152> NAME 'numberOfButtons'
        DESC 'Number of buttons. If the PointingDevice has no buttons,
              enter 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at153> NAME 'handedness'
        DESC 'Integer indicating whether the PointingDevice is configured
              for right (value=2) or left handed operation
              (value=3). Also, the values, "Unknown" (1), can be
              defined.  Allowed values are: "Unknown", "Not Applicable",
              "Right Handed Operation", "Left Handed Operation".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at154> NAME 'resolution'
        DESC 'Tracking resolution of the PointingDevice in Counts per
              Inch.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc81> NAME 'dmtfPointingDevice'
        DESC 'represents those Devices used to "point" to regions of a
              Display.'
        SUP  dmtfUserDevice
        MUST (pointingType $ numberOfButtons $ handedness $ resolution)
      )

2.31 dmtfKeyboard

   This class represents the capabilities of a keyboard logical device.

      ( <oid-at155> NAME 'numberOfFunctionKeys'
        DESC 'Number of function keys on the Keyboard.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at156> NAME 'layout'
        DESC 'A free-form string indicating the format and layout of the
              Keyboard.'
        SYNTAX string SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 23]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at157> NAME 'password'
        DESC 'An integer indicating whether a hardware-level password is
              enabled at the keyboard, preventing local input'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc82> NAME 'dmtfKeyboard'
        DESC 'Capabilities of the Keyboard LogicalDevice.'
        SUP  dmtfUserDevice
        MUST (numberOfFunctionKeys $ layout $ password)
      )

2.32 dmtfDisplay

   This is the super class for the miscellaneous display devices that
   exist.

      ( <oid-oc83> NAME 'dmtfDisplay'
        DESC 'Display is a superclass for grouping the miscellaneous
              display devices that exist.'
        SUP dmtfUserDevice ABSTRACT
      )

2.33 dmtfDesktopMonitor

This class covers the capabilities of desktop monitor (i.e. CRT) logical
devices. It defines the attributes displayType and bandwidth.

   ( <oid-at158> NAME 'displayType'
     DESC 'The type of DesktopMonitor or CRT. For example, multiscan
           color or monochrome monitors (values 2 or 3, respectively)
           can be shown in this property.  Allowed values are:
           "Unknown", "Other","Multiscan Color",
           "Multiscan Monochrome", "Fixed Frequency Color",
           "Fixed Frequency Monochrome".'
     SYNTAX integer SINGLE-VALUE
   )

   ( <oid-at159> NAME 'bandwidth'
     DESC 'Monitor's bandwidth in MHertz. If unknown, enter 0.'
     SYNTAX integer SINGLE-VALUE
   )

   ( <oid-at160> NAME 'screenHeight'
     DESC 'The logical height of the Display in screen coordinates.'
     SYNTAX integer SINGLE-VALUE
   )

Expires 3/31/00                                                [Page 24]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   ( <oid-at161> NAME 'screenWidth'
     DESC 'The logical width of the Display in screen coordinates.'
     SYNTAX integer SINGLE-VALUE
   )

   ( <oid-oc84> NAME 'dmtfDesktopMonitor'
     DESC 'Capabilities of the DesktopMonitor (CRT)
           LogicalDevice.'
     SUP dmtfDisplay
     MUST (displayType $ bandwidth $ screenHeight $ screenWidth)
   )

2.34 dmtfMonitorResolution

   This class describes the possible horizontal resolutions, vertical
   resolutions, refresh rate and scan mode for a desktop monitor.  These
   are not the settings that are in use.

      ( <oid-at162> NAME 'refreshRate'
        DESC 'Monitor's refresh rate in Hertz. If a range of rates is
              supported, use the MinRefreshRate and MaxRefreshRate
              properties, and set this attribute to 0'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at163> NAME 'minRefreshRate'
        DESC 'Monitor's minimum refresh rate in Hertz, when a range of
              rates is supported at the specified resolutions.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at164> NAME 'maxRefreshRate'
        DESC 'Monitor's maximum refresh rate in Hertz, when a range of
              rates is supported at the specified resolutions.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at165> NAME 'scanMode'
        DESC 'Integer indicating whether the monitor operates in
              interlaced (value=5) or non-interlaced (4) mode.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc85> NAME 'dmtfMonitorResolution'
        DESC 'MonitorResolution describes the relationship between
              horizontal and vertical resolutions, refresh rate and scan
              mode for a DesktopMonitor.'
        SUP  dmtfSetting

Expires 3/31/00                                                [Page 25]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        MUST (settingID $ horizontalResolution $ verticalResolution $
              refreshRate $ minRefreshRate $ maxRefreshRate $ scanMode)
      )

2.35 dmtfMonitorSettingAuxClass

   This auxiliary class associates a dmtfMonitorResolution object to the
   dmtfDesktopMonitor object to which it applies.  In this class,
   elementRefs point to dmtfDesktopMonitor objects and settingRefs point
   to dmtfMonitorResolution objects.

      ( <oid-oc86> NAME 'dmtfMonitorSettingAuxClass'
        DESC 'MonitorSetting associates the MonitorResolution Setting
              object with the DesktopMonitor to which it applies.'
        SUP dmtfElementSettingAuxClass AUXILIARY
      )

2.36 dmtfFlatPanel Class

   As this class contains the capabilities of flat panel displays, it
   reuses previously defined attributes horizontalResolution,
   verticalResolution, scanMode, displayType and defines lightSource and
   supportsColor.

      ( <oid-at166> NAME 'lightSource'
        DESC 'A description of the display illumination type. For
              example, backlit (value=2) or reflective (4) can be
              specified. Allowed values are: "Unknown", "Other",
              "Backlit", "Edgelit", "Reflective".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at167> NAME 'supportsColor'
        DESC 'Boolean indicating whether the FlatPanel supports color
              display.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc87> NAME 'dmtfFlatPanel'
        DESC 'Capabilities of the FlatPanel
              LogicalDevice.'
        SUP dmtfDisplay
        MUST (horizontalResolution $ verticalResolution $ scanMode $
              displayType $ lightSource $ supportsColor)
      )

Expires 3/31/00                                                [Page 26]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.37 dmtfScanner

   This class defines capabilities for scanners.

      ( <oid-oc88> NAME 'dmtfScanner'
        DESC 'Capabilities of the Scanner LogicalDevice.'
        SUP  dmtfLogicalDevice
      )

2.38 dmtfOOBAlertService

   This service provides information about the destination and the alert
   message format for out of band management notification of alert
   messages.

      ( <oid-at168> NAME 'destinationType'
        DESC 'The type of the alert destination.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at169> NAME 'otherDestinationTypeDescription'
        DESC 'The description of the alert DestinationType, used when
              destinationType is other.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at170> NAME 'destinationAddress'
        DESC 'The address where this Service sends the alerts. The format
              of this address depends on the DestinationType.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at171> NAME 'messageFormat'
        DESC 'The format of the Alert Message sent by the Service.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at172> NAME 'otherMessageFormatDescription'
        DESC 'The description of the format of the alert message used by
              the Service when the AlertMessageFormat property is set to
              "Other".'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at173> NAME 'onlySendsFixedMessage'
        DESC 'If the AlertService only uses a fixed message to send an
              alert, then this flag should be set to TRUE.'
        SYNTAX boolean SINGLE-VALUE

Expires 3/31/00                                                [Page 27]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at174> NAME 'fixedPartOfMessage'
        DESC 'The AlertService may require some fixed data to send as
              part of the message. This may include things like the
              address or name of the System. This string contains the
              complete message when the property, OnlySendsFixedMessage,
              is set to TRUE.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at175> NAME 'destinationIsAckCapable'
        DESC 'If the destination is capable of sending an acknowledgement
              to the alert, then this flag is set to TRUE.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at176> NAME 'retryCount'
        DESC 'The AlertService may retry and send an alert more than
              once. The RetryCount identifies how often the operation
              will be repeated.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at177> NAME 'retryInterval'
        DESC 'The interval between each successive retry, in seconds.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc89> NAME 'dmtfOOBAlertService'
        DESC 'This Service is implemented by a LogicalDevice (e.g. a
              NetworkAdapter or Modem) that is capable of sending alert
              messages to a remote destination.'
        SUP dmtfService
        MUST (destinationType $ otherDestinationTypeDescription $
              destinationAddress $ messageFormat $
              otherMessageFormatDescription $ onlySendsFixedMessage $
              fixedPartOfMessage $ destinationIsAckCapable $ retryCount $
              retryInterval)
      )

2.39 dmtfWakeUpService

   This service allows a dmtfUnitaryComputerSystem to wake up from a low
   power sleep state and is implemented by a LogicalDevice (e.g.
   NetworkAdapter or Modem) that is capable of receiving wakeup
   messages, and notifying the System.

Expires 3/31/00                                                [Page 28]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at178> NAME 'wakeUpType'
        DESC 'The Type of the WakeUp Service.  Allowed values are:
              "Unknown", "Other", "Wake On LAN - Magic Packet",
              "Wake on LAN - Packet Filtering", "Wake On Ring".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at179> NAME 'otherWakeUpTypeDescription'
        DESC 'A description of the type of WakeUpService used when
              WakeUpType is set to "Other".'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at180> NAME 'filterType'
        DESC 'The filter type on the packets/messages that trigger the
              WakeUpService. This field is only used when the WakeUpType
              is set to "Wake On LAN - Packet Filtering".  Allowed
              values are: "Unknown", "Other", "ARP Broadcast",
              "Neighbor Discovery Multicast",
              "IP Packet with Directed MAC Address",
              "IPX Diagnostic Responder", "NBT Name Query",
           "Binary Match".
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at181> NAME 'filterData'
        DESC 'The binary data that is used to compare the contents of the
              received packet. This is used when the FilterType is set to
              "Binary Match" when the FilterType is set to "Other".'
        SYNTAX integer
      )

      ( <oid-at182> NAME 'otherFilterTypeDescription'
        DESC 'The description of the format of the FilterType used by the
              Service when the FilterType is set to "Other".'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc90> NAME 'dmtfWakeUpService'
        DESC 'allows a UnitaryComputerSystem to wake up from a low
              power sleep state.'
        SUP dmtfService
        MUST (wakeUpType $ otherWakeUpTypeDescription $ filterType $
              filterData $ otherFilterTypeDescription)
      )

Expires 3/31/00                                                [Page 29]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.40 dmtfModem

   The superclass for numerous types of modems.

      ( <oid-oc91> NAME 'dmtfModem'
        DESC 'the superclass for grouping the numerous types of Modems.'
        SUP dmtfLogicalDevice ABSTRACT
      )

2.41 dmtfOOBAlertServiceOnModemAuxClass

   This auxiliary class defines where the out of band alerting service
   is implemented. In this class, antecedentRefs point to a single
   dmtfModem object and dependentRefs point to dmtfOOBAlertService
   objects.

      ( <oid-oc92> NAME 'dmtfOOBAlertServiceOnModemAuxClass'
        DESC 'defines where the out of band alerting Service is
              implemented. The Service can either use a Modem or
              NetworkAdapter to send alerts.'
        SUP dmtfDeviceServiceImplementationAuxClass AUXILIARY
      )

2.42 dmtfWakeUpServiceOnModemAuxClass

   This auxiliary class defines where the wake up service is
   implemented.  In it antecedentRefs point to a single dmtfModem object
   while dependentRefs point to dmtfWakeUpService objects.

      ( <oid-oc93> NAME 'dmtfWakeUpServiceOnModemAuxClass'
        DESC 'defines where the WakeUpService is implemented. The Service
              can either use a Modem or NetworkAdapter to receive a
              wake up signal.'
        SUP dmtfDeviceServiceImplementation AUXILIARY
      )

2.43 dmtfConnectionBasedModem

   This is the superclass for grouping numerous types of connection
   based modems.

      ( <oid-at183> NAME 'vendorID'
        DESC 'VendorID information is reported via Modem-specific requests.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc94> NAME 'dmtfConnectionBasedModem'
        DESC 'the superclass for grouping the numerous types of

Expires 3/31/00                                                [Page 30]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              connection-based Modems. A CableModem is a type of
              connection-based Modem.'
        SUP dmtfModem ABSTRACT
        MUST (vendorID)
      )

2.44 dmtfDSLModem

   Parent class for DSL devices.

      ( <oid-oc95> NAME 'dmtfDSLModem'
        DESC 'The DSLModem class represents the superclass for Digital
              Subscriber Line (DSL) Devices. Properties will be defined
              in a future release of the model.'
        SUP dmtfConnectionBasedModem
      )

2.45 dmtfVDSLModem

   This will be defined later.

      ( <oid-oc96> NAME 'dmtfVDSLModem'
        DESC 'The VDSLmodem class represents Modems of the DSL type =
              VDSL, Very high data rate Digital Subscriber
              Line. Properties will be defined in a future release of the
              model.'
        SUP dmtfDSLModem
      )

2.46 dmtfHDSLModem

   This will be defined later.

      ( <oid-oc97> NAME 'dmtfHDSLModem'
        DESC 'The HDSLModem class represents Modems of the DSL type =
              HDSL, High data rate Digital Subscribe Line, capable of
              delivering T1 or E1 speeds. Properties will be defined in a
              future release of the model.'
        SUP dmtfDSLModem
      )

2.47 dmtfSDSLModem

   This will be defined later.

      ( <oid-oc98> NAME 'dmtfSDSLModem'
        DESC 'The SDSLModem class represents Modems of the DSL type =
              SDSL, Symmetric Digital Subscriber Line. Properties will be

Expires 3/31/00                                                [Page 31]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              defined in a future release of the model.'
        SUP dmtfDSLModem
      )

2.48 dmtfADSLModem

   Models modems of the asymmetric digital subscriber line type.

      ( <oid-at184> NAME 'noiseMargin'
        DESC 'Noise Margin of this Modem with respect to its received
              signal, in tenths of dB.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at185> NAME 'lineAttenuation'
        DESC 'Measured difference in the total power transmitted by the
              peer Modem and the total power received by this Modem. This
              is measured in tenths of dB.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at186> NAME 'lineState'
        DESC 'Status shows the current state of the connection (line).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at187> NAME 'totalOutputPower'
        DESC 'Measured total output power (in tenths of dB) transmitted
              by this Modem.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at188> NAME 'maxDataRate'
        DESC 'Shows the maximum currently attainable data rate for
              the Modem. This value will be equal or greater than the
              current line rate.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc99> NAME 'dmtfADSLModem'
        DESC 'The ADSLModem class represents Modems of the DSL type =
              ADSL, Asymmetric Digital Subscriber Line.'
        SUP dmtfDSLModem
        MUST (noiseMargin $ lineAttenuation $ line $ frame $ signal $
              power $ lineState $ totalOutputPower $ maxDataRate)
      )

Expires 3/31/00                                                [Page 32]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.49 dmtfCableModem

   Represents device for transmission access a cable infrastructure.

      ( <oid-oc100> NAME 'dmtfCableModem'
        DESC 'The CableModem class represents a device for transmission
              across a cable infrastructure.'
        SUP dmtfConnectionBasedModem
      )

2.50 dmtfCallBasedModem

   The superclass for grouping call-based modems, which includes POTS
   modems.

      ( <oid-at189> NAME 'fallbackEnabled'
        DESC 'Shows whether online fallback is enabled, to be
              negotiated by the Modem.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at190> NAME 'compressionSupported'
        DESC 'An array enumerating all the compression protocols
              supported by the Modem.  Allowed values are: "Unknown",
              "Other", "No Compression", "MNP 5", "V.42bis", "MNP 3",
              "MNP 4", "V.58", "PEP", "HST".'
        SYNTAX integer
      )

      ( <oid-at191> NAME 'otherCompressionDescription'
        DESC 'Description of the compression type when "Other" is defined
              in the CompressionSupported array.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at192> NAME 'compressionInfo'
        DESC 'Describes the current data compression characteristics of
              the Modem.  Allowed values are: "Unknown", "Other",
              "No Compression", "MNP 5", "V.42bis", "MNP 3", "MNP 4",
              "V.58", "PEP", "HST".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at193> NAME 'otherCompressionInfoDescription'
        DESC 'Description of the current compression type when
             "Other" is specified in the CompressionInfo property.'
        SYNTAX string SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 33]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at194> NAME 'modulationSupported'
        DESC 'An array enumerating all the modulation protocols supported
              by the Modem. The beginning entries in the Values qualifier
              array are mapped from the modulationScheme property.
        SYNTAX integer
      )

      ( <oid-at195> NAME 'otherModulationDescription'
        DESC 'Description of the current modulation type when
              "Other" is specified in the ModulationSupported property.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at196> NAME 'modulationScheme'
        DESC 'Describes the current modulation scheme of the Modem.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at197> NAME 'otherSchemeDescription'
        DESC 'Description of the current modulation type when
              "Other"(value=1) is specified in the ModulationScheme
              property.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at198> NAME 'errorControlSupported'
        DESC 'An array enumerating the error control protocols supported
              by the Modem. The beginning entries in the Values qualifier
              array are mapped from the errorControlInfo property.
              Allowed values are: "Unknown", "Other",
              "No Error Correction", "MNP 4","LAPM", "V.58",
              "ECP Enhanced Cellular Protocol",
              "ETC Enhanced Throughput Cellular", "MNP 1", "MNP 2",
              "MNP 3", "MNP10", "PEP", "HST".'
        SYNTAX integer
      )

      ( <oid-at199> NAME 'otherErrorControlDescription'
        DESC 'Description of the error control type when "Other" is
              specified in the ErrorControlSupported property.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at200> NAME 'errorControlInfo'
        DESC 'Describes the current error correction characteristics of
              the Modem.  Allowed values are: "Unknown", "Other",
             "No Error Correction", "MNP 4", "LAPM", "V.58",
             "ECP Enhanced Cellular Protocol",

Expires 3/31/00                                                [Page 34]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

             "ETC Enhanced Throughput Cellular", "MNP 1", "MNP 2",
             "MNP 3", "MNP10", "PEP", "HST".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at201> NAME 'otherErrorControlInfoDescription'
        DESC 'Description of the error control when "Other"is defined as
              the value of the ErrorControlInfo property.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at202> NAME 'callSpeed'
        DESC 'The rate at which the receiver and transmitter are or were
              last cooperating, on a call, before disconnection.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at203> NAME 'callStatus'
        DESC 'Status of the Modem. For example, information regarding
              modem negotiation or whether the modem is connected (values
              8 and 9, respectively) can be conveyed in this property.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at204> NAME 'callLength'
        DESC 'Length of the last or current call. That a call is
              in-progress is shown by the CallStatus property. The
              "interval" format of the datetime data type should be used
              for the property value.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-at205> NAME 'numberDialed'
        DESC 'Last or current number dialed to which the statistics
              apply, or NULL if the call was incoming.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc101> NAME 'dmtfCallBasedModem'
        DESC 'the superclass for grouping the numerous types of
              call-based modems. The POTSModem is a type of call-based
Modem.'
        SUP dmtfModem ABSTRACT
        MUST (fallbackEnabled $ compressionSupported $
              otherCompressionDescription $ compressionInfo $
           otherCompressionInfoDescription $ modulationSupported $
           otherModulationDescription $ modulationScheme $
           otherSchemeDescription $ errorControlSupported $
           otherErrorControlDescription $ errorControlInfo $

Expires 3/31/00                                                [Page 35]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           otherErrorControlInfoDescription $ timeOfLastReset $
           callSpeed $ callStatus $ callLength $ numberDialed)
      )

2.51 dmtfISDNModem

   To be defined later

      ( <oid-oc102> NAME 'dmtfISDNModem'
        DESC 'The ISDNModem class, a type of call-based Modem. Properties
              will be defined in a future release of the model.'
        SUP dmtfCallBasedModem
      )

2.52 dmtfPOTSModem

   This class represents a device that translates binary data into wave
   modulations for sound based transmission and connects to the POTS
   (Plain Old Telephone System) network.

      ( <oid-at206> NAME 'enabledCapabilities'
        DESC 'Specifies those capabilities are enabled from the list of
              ones supported, defined in the Capabilities array.'
        SYNTAX integer
      )

      ( <oid-at207> NAME 'maxBaudRateToSerialPort'
        DESC 'Defines the maximum settable communication speed to the COM
              Port for an external modem. Enter 0 if not applicable.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at208> NAME 'maxBaudRateToPhone'
        DESC 'Defines the maximum settable communication speed for
              accessing the phone system.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at209> NAME 'supportsSynchronousConnect'
        DESC 'Boolean indicating that synchronous, as well as
              asynchronous, communication is supported.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at210> NAME 'dialType'
        DESC 'DialType is an integer indicating whether tone (value=1) or
              pulse dialing (value=2) is used.'
        SYNTAX integer SINGLE-VALUE

Expires 3/31/00                                                [Page 36]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at211> NAME 'inactivityTimeout'
        DESC 'InactivityTimeout defines the time limit (in seconds) for
              automatic disconnection of the phone line, if no data is
              exchanged. A value of 0 shows that this feature is
              present but not enabled.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at212> NAME 'speakerVolumeInfo'
        DESC 'Describes the volume level of the audible tones from the
              Modem. For example, high, medium or low volume can be
              reported (values 3, 4 or 5, respectively).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at213> NAME 'countriesSupported'
        DESC 'CountriesSupported is an array of strings defining the
              countries in which the POTSModem operates.'
        SYNTAX string{64}
      )

      ( <oid-at214> NAME 'countrySelected'
        DESC 'CountrySelected is a string value defining the country for
              which the Modem is currently programmed. When multiple
              countries are supported, this property defines the one that
           is currently selected for use.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at215> NAME 'ringsBeforeAnswer'
        DESC 'Number of rings before the Modem answers an incoming call.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at216> NAME 'maxNumberOfPasswords'
        DESC 'MaxNumberOfPasswords specifies the number of passwords
              definable in the Modem itself. If this feature is not
              supported, enter 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at217> NAME 'currentPasswords'
        DESC 'CurrentPasswords is an array containing the currently
              defined passwords for the Modem. This array should be left
              blank for security reasons.'
        SYNTAX string{24}

Expires 3/31/00                                                [Page 37]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at218> NAME 'supportsCallback'
        DESC 'Indication of whether the Modem supports call-back.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at219> NAME 'answerMode'
        DESC 'AnswerMode defines the current auto-answer/call-back
              setting for the Modem.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at220> NAME 'equalization'
        DESC 'The current equalization setting for the Modem.  Allowed
              values are: "Unknown", "Other", "Long", "Short".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at221> NAME 'blackListedNumbers'
        DESC 'List of black-listed numbers for the Modem.'
        SYNTAX string
      )

      ( <oid-oc103> NAME 'dmtfPOTSModem'
        DESC 'The POTSModem class represents a Device that translates
              binary data into wave modulations for sound based
              transmission.'
        SUP dmtfCallBasedModem
        MUST (capabilities $ capabilityDescriptions $
              enabledCapabilities $ maxBaudRateToSerialPort $
              maxBaudRateToPhone $ supportsSynchronousConnect $
              dialType $ inactivityTimeout $ speakerVolumeInfo $
              countriesSupported $ countrySelected $ ringsBeforeAnswer $
              maxNumberOfPasswords $ currentPasswords $
              supportsCallback $ answerMode $ equalization $
              blackListedNumbers)
      )

2.53 dmtfUnimodem

   This class represents a POTSModem that supports the Unimodem 1.0
   specification.

      ( <oid-at222> NAME 'callSetupResultCode'
        DESC 'Current call setup result code.  Allowed values are:
              "No Previous Call", "No Dial Tone Detected",
              "Reorder Signal Detected, Network Busy",

Expires 3/31/00                                                [Page 38]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              "Busy Signal Detected", "No Recognized Signal Detected",
              "Voice Detected", "Text Telephone Detected",
              "Data Answering Signal Detected",
           "Data Calling Signal Detected",
           "Fax Answering Signal Detected",
           "Fax Calling Signal Detected", "V.8bis Signal Detected".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at223> NAME 'multiMediaMode'
        DESC 'Current multi-media mode of the Unimodem.  Allowed values
           are: "Data Only", "Fax Only", "Voice Only", "Voice View",
           "ASVD V.61", "ASVD V.34Q", "DSVD Multi-Tech", "DSVD 1.2",
           "DSVD V.70", "Video Telephony H.324", "Other V.80 Call".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at224> NAME 'dTEDCEInterfaceMode'
        DESC 'Current DTE-DCE interface mode of the Unimodem, such as
           asynchronous, v.80 transparent or framed synchronous modes.
           Allowed values are: "Async Data",
           "V.80 Transparent Synchronous Mode",
           "V.80 Framed Synchronous Mode".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at225> NAME 'transmitCarrierNegotiation'
        DESC 'The active transmit modulation scheme.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at226> NAME 'receiveCarrierNegotiation'
        DESC 'The active receive modulation scheme.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at227> NAME 'initialTransmitCarrierDataRate'
        DESC 'Initial transmit carrier data rate for the current or last
           call, in bits per second.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at228> NAME 'initialReceiveCarrierDataRate'
        DESC 'Initial receive carrier data rate for the current or last
           call, in bits per second.'
        SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 39]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at229> NAME 'finalTransmitCarrierDataRate'
        DESC 'Final transmit carrier data rate of the current or last
           call, in bits per second.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at230> NAME 'finalReceiveCarrierDataRate'
        DESC 'Final receive carrier data rate of the current or last
              call, in bits per second.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at231> NAME 'terminationCause'
        DESC 'Cause of last call termination.  Allowed values are:
           "Cause Unidentified", "No Previous Call",
           "Call Is Still in Progress",
           "Call Waiting Signal Detected", "Delayed",
           "NMS Initiated Dial Call",
           "NMS Initiated Leased Line Restoral",
           "NMS Initiated Redial",
           "NMS Initiated Dial Disconnect", "Power Loss",
           "Equipment Failure", "Front Panel Disconnect Requested",
           "Front Panel Leased Line Restoral",
           "Automatic Leased Line Restoral",
           "Inactivity Timer Expired",
           "cct116 Restoral Request",
           "cct108 Is Off Inhibits Dial", "cct108 Turned Off",
           "No Number Provided", "Blacklisted Number",
           "Call Attempts Limit Exceeded", "Extension Phone Off Hook",
           "Call Setup Fail Timer Expired", "Incoming Call Detected",
           "Loop Current Interrupted", "No Dial Tone",
           "Voice Detected", "Reorder Tone", "Sit Tone",
           "Engaged Tone", "Long Space Disconnect", "Carrier Lost",
           "Training Failed", "No Modulation in Common",
           "Retrain Failed", "Retrain Attempt Count Exceeded",
           "GSTN Cleardown Received", "Fax Detected", "In Test Mode",
           "Intrusive Self Test Initiated", "Any Key Abort",
           "DTE Hangup Command", "DTE Reset Command", "Frame Reject",
           "No Error Control Established", "Protocol Violation",
           "n400 Exceeded", "Negotiation Failed",
           "Disconnect Frame Received", "Sabme Frame Received",
           "Loss Of Synchronization".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at232> NAME 'unimodemRevision'
        DESC 'Diagnostic Command Specification, Unimodem revision
           number.'

Expires 3/31/00                                                [Page 40]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at233> NAME 'estimatedNoiseLevel'
        DESC 'Estimated noise level for the last or current call in
           -dBm. Values are between 0-100.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at234> NAME 'normalizedMeanSquaredError'
        DESC 'Normalized mean squared error for the last or current
           call.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at235> NAME 'errorControlFrameSize'
        DESC 'Error Control frame size in bytes for the last or current
           call.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at236> NAME 'transmitFlowControl'
        DESC 'The flow control mechanism used in transmitting data.
           Allowed values are: "Unknown", "Off", "DC1/DC3",
           "V.24 ckt 106/133".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at237> NAME 'receiveFlowControl'
        DESC 'The flow control mechanism used in receiving data.
           Allowed values are: "Unknown", "Off", "DC1/DC3",
           "V.24 ckt 106/133".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc104> NAME 'dmtfUnimodem'
        DESC 'Unimodem is a POTSModem that supports the Unimodem 1.0
           Specification.'
        SUP dmtfPOTSModem
        MUST (callSetupResultCode $ multiMediaMode $
           dTEDCEInterfaceMode $ transmitCarrierNegotiation $
           receiveCarrierNegotiation $
           initialTransmitCarrierDataRate $
           initialReceiveCarrierDataRate $
           finalTransmitCarrierDataRate $
           finalReceiveCarrierDataRate $ terminationCause $
           unimodemRevision $ estimatedNoiseLevel $
           normalizedMeanSquaredError $

Expires 3/31/00                                                [Page 41]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           carrierRenegotiationEventCount $ errorControlFrameSize $
           transmitFlowControl $ receiveFlowControl)
      )

2.54 dmtfBattery Class

   This class contains capabilities of battery logical devices, which
   apply to both batteries in Laptop Systems and other internal/external
   batteries, such as used in, or as UPS.  Because management functions
   are not included, several properties of the CIM object have not been
   captured as LDAP attributes.

      ( <oid-at238> NAME 'batteryStatus'
        DESC 'Description of the Battery's charge status. Values such as
              "Fully Charged" (11) can be specified. The value, 10, is
              not valid in the CIM Schema since in DMI it represents that
              no battery is installed. Here, this object should
           not be instantiated.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at239> NAME 'chemistry'
        DESC 'An enumeration that describes the Battery's chemistry.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at240> NAME 'designCapacity'
        DESC 'The design capacity of the battery in mWatt-hours. If this
              property is not supported, enter 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at241> NAME 'designVoltage'
        DESC 'The design voltage of the battery in mVolts. If this
           attribute is not supported, enter 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at242> NAME 'smartBatteryVersion'
        DESC 'The Smart Battery Data Specification version number
           supported by this Battery. If the Battery does not support
           this function, the value should be left blank.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at243> NAME 'expectedLife'
        DESC 'Shows the Battery's expected lifetime in minutes,
           if the Battery is fully charged. This property

Expires 3/31/00                                                [Page 42]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           represents the total expected life of the Battery, not its
           current remaining life, which is shown by the
           EstimatedRunTime property.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at244> NAME 'maxRechargeTime'
        DESC 'MaxRechargeTime shows the maximum time, in minutes, to
           fully charge the Battery. This property represents the time
           to recharge a fully depleted Battery, not the current
           remaining charging time, which is shown in the
           TimeToFullCharge property.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc105> NAME 'dmtfBattery'
        DESC 'Capabilities of the Battery
           LogicalDevice. This class applies to both batteries in
           Laptop Systems and other internal/external batteries, such
           as used in, or as UPSs.'
        SUP dmtfLogicalDevice
        MUST (batteryStatus $ chemistry $ designCapacity $
           designVoltage $ smartBatteryVersion $ expectedLife $
           maxRechargeTime)
      )

2.55 dmtfPowerSupply

   The class models capabilities of a logical power supply device.
   Because management functions are not included, several properties of
   the CIM object have not been captured as LDAP attributes.

      ( <oid-at245> NAME 'isSwitchingSupply'
        DESC 'Boolean indicating that the PowerSupply is a switching (vs
           linear) supply.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at246> NAME 'typeOfRangeSwitching'
        DESC 'TypeOfRangeSwitching describes the type of input voltage
           range switching implemented in this PowerSupply.
           Acceptable Values are "Other", "Unknown", "Manual",
           "Autoswitch", "Wide Range", "Not Applicable".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at247> NAME 'totalOutputPower'
        DESC 'Represents the total output power of the PowerSupply in

Expires 3/31/00                                                [Page 43]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           milliWatts. 0 denotes "unknown".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc106> NAME 'dmtfPowerSupply'
        DESC 'Capabilities of the PowerSupply LogicalDevice.'
        SUP  dmtfLogicalDevice
        MUST (isSwitchingSupply $ typeOfRangeSwitching $
           totalOutputPower)
      )

2.56 dmtfSuppliesPowerAuxClass

   This auxiliary class captures the relationship between a device and
   the power supply or UPS that, if lost, will affect that device.  In
   this class, antecedentRefs point to dmtfPowerSupply objects and
   dependentRefs point to dmtfLogicalDevice objects.

      ( <oid-oc107> NAME 'dmtfSuppliesPowerAuxClass'
        DESC 'shows that a Device is in the power domain of the
              referenced PowerSupply or UPS.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

2.57 dmtfUninterruptiblePowerSupply

   This class specifies the capabilities of an uninterruptible power
   supplies.  Because management functions are not included, several
   properties of the CIM object have not been captured as LDAP
   attributes.

      ( <oid-at248> NAME 'range1InputVoltageLow'
        DESC 'If the voltage (in millivolts) drops below the value
           specified by Range1InputVoltageLow, the UPS will compensate
           by boosting the voltage using its power source(s). A value
           of 0 shows that the voltage at which boosting occurs is
           "unknown".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at249> NAME 'range1InputVoltageHigh'
        DESC 'If the voltage (in millivolts) rises above the value
           specified by Range1InputVoltageHigh, the UPS will
           compensate by trimming the voltage. A value of 0 shows
           that the voltage at which trimming occurs is "unknown".'
        SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 44]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at250> NAME 'range2InputVoltageLow'
        DESC 'If the voltage (in millivolts) drops below the value
           specified by Range2InputVoltageLow, the UPS will compensate
           by boosting the voltage using its power source(s). A value
           of 0 shows that the voltage at which boosting occurs is
           "unknown".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at251> NAME 'range2InputVoltageHigh'
        DESC 'If the voltage (in millivolts) rises above the value
           specified by Range2InputVoltageHigh, the UPS will
           compensate by trimming the voltage. A value of 0 shows
           that the voltage at which trimming occurs is "unknown".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc108> NAME 'dmtfUninterruptiblePowerSupply'
        DESC 'Capabilities of an UninterruptiblePowerSupply.'
        SUP dmtfPowerSupply
        MUST (range1InputVoltageLow $ range1InputVoltageHigh $
           range2InputVoltageLow $ range2InputVoltageHigh)
      )

2.58 dmtfAssociatedBatteryAuxClass

   This auxiliary class shows the use of one or more dmtfBattery objects
   by a dmtfLogicalDevice object. In this class, antecedentRefs point to
   dmtfBattery objects and dependentRefs point to dmtfLogicalDevice
   objects.

      ( <oid-oc109> NAME 'dmtfAssociatedBatteryAuxClass'
        DESC 'A LogicalDevice may use or require one or more
           Batteries. This relationship is described by this
           class. It is also possible to model the individual
           Batteries that includes a UPS, using this class.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

2.59 dmtfNetworkAdapter

   This abstract class defines general networking hardware concepts (for
   example, permanent address or speed of operation). Objects of this
   class are devices with the ability to support multiple, higher level
   protocols and provide the implementation behind the network model's
   dmtfProtocolEndpoint class [8].

   The 'potential for connectivity' is different from the master-

Expires 3/31/00                                                [Page 45]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

   slave/controller-controlled by relationships of dmtfController.
   Sometimes, however, a single device is both a network adapter and a
   controller - for example, when a fibre channel adapter is operating
   as a computer system's SCSI controller.  Here, there are aspects of
   the device that are network oriented and others that are controller
   oriented.  Therefore, both the controller and adapter classes should
   be instantiated. The dmtfDeviceIdentityAuxClass would also be used to
   tie together these differing aspects/abstractions of the device.

      ( <oid-at252> NAME 'permanentAddress'
        DESC 'the network address hardcoded into an adapter.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at253> NAME 'networkAddresses'
        DESC 'An array of strings indicating the network addresses for an
           adapter.'
        SYNTAX string{64}
      )

      ( <oid-at254> NAME 'autoSense'
        DESC 'A boolean indicating whether the NetworkAdapter is capable
           of automatically determining the speed of the attached
           network media.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at255> NAME 'fullDuplex'
        DESC 'Boolean indicating that the Adapter is operating in full
           duplex mode.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc110> NAME 'dmtfNetworkAdapter'
        DESC 'NetworkAdapter is a superclass for grouping the numerous
           types of network adapters in use.'
        SUP dmtfLogicalDevice ABSTRACT
        MUST (permanentAddress $ networkAddresses $ speed $ maxSpeed $
              autoSense $ fullDuplex)
      )

2.60 dmtfOOBAlertServiceOnNetworkAdapterAuxClass

   This auxiliary class defines where the out of band alerting service is
   implemented.  Currently, either a modem or a network adapter may be
   used by the service to send alerts.  In this class, antecedentRefs
   must point to a single dmtfNetworkAdapter object and dependentRefs
   point to dmtfOOBAlertService objects.

Expires 3/31/00                                                [Page 46]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-oc111> NAME 'dmtfOOBAlertServiceOnNetworkAdapterAuxClass'
        DESC 'defines where the out of band alerting Service is
           implemented.'
        SUP dmtfDeviceServiceImplementationAuxClass AUXILIARY
      )

2.61 dmtfWakeUpServiceOnNetworkAdapterAuxClass

   Like the out of band alerting service, a wake up service may use
   either a modem or a network adapter, specified by this auxliary
   class.  In this class, antecedentRefs must point to a single
   dmtfNetworkAdapter object and dependentRefs point to
   dmtfWakeUpService objects.

      ( <oid-oc112> NAME 'dmtfWakeUpServiceOnNetworkAdapterAuxClass'
        DESC 'defines where the WakeUpService is implemented.'
        SUP dmtfDeviceServiceImplementationAuxClass AUXILIARY
      )

2.62 dmtfEthernetAdapter

   This class captures the capabilities of an ethernet adapter.

      ( <oid-at256> NAME 'maxDataSize'
        DESC 'The maximum size of the INFO (non-MAC) field that will be
              received or transmitted.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc113> NAME 'dmtfEthernetAdapter'
        DESC 'Capabilities of an EthernetAdapter.'
        SUP dmtfNetworkAdapter
        MUST (networkAddresses $ maxDataSize $ capabilities $
              capabilityDescriptions $ enabledCapabilities)
      )

2.63 dmtfTokenRingAdapter

   This class captures the capabilities of a token ring adapter.

      ( <oid-at257> NAME 'ringStatus'
        DESC 'The current status that can be used to diagnose
              fluctuating problems that can occur on token rings, after a
              station has successfully been added to the ring. Before an
              open is completed, this object contains the value
              indicating "no status" (The RingState and RingOpenStatus
              properties are also provided for debugging problems when
              the station can not even enter the ring.) The property's

Expires 3/31/00                                                [Page 47]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              value is  a sum of values, one for each currently
              applicable condition. The following values are defined for
              various conditions:
           0 = No Problems Detected,
              32 = Ring Recovery,
           64 = Single Station,
           256 = Remove Received,
           512 = Reserved,
           1024 = Auto-Removal Error,
           2048 = Lobe Wire Fault,
           4096 = Transmit Beacon,
           8192 = Soft Error,
           16384 = Hard Error,
           32768 = Signal Loss,
           131072 = No Status, Open Not Completed.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at258> NAME 'ringState'
        DESC 'The current Device state with respect to entering or
              leaving the ring.  Allowed values are: "Opened", "Closed",
           "Opening", "Closing", "Open Failure", "Ring Failure".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at259> NAME 'ringOpenStatus'
        DESC 'This property shows the success, or the reason for
              failure, of the station's most recent attempt to enter the
              ring. Allowed values are: "No Open Attempted",
           "Bad Parameter", "Lobe Failed", "Signal Loss",
           "Insertion Timeout", "Ring Failed", "Beaconing",
           "Duplicate MAC", "Request Failed", "Remove Received",
           "Last Open Successful".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at260> NAME 'ringSpeed'
        DESC 'The ring's bandwidth.  Allowed values are: "Unknown",
              "Other", "One Megabit", "Four Megabit", "Sixteen Megabit".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc114> NAME 'dmtfTokenRingAdapter'
        DESC 'Capabilities of a TokenRingAdapter.'
        SUP dmtfNetworkAdapter
        MUST ( networkAddresses $ maxDataSize $ capabilities $
               capabilityDescriptions $ enabledCapabilities $
               ringStatus $ ringState $ ringOpenStatus $ ringSpeed)

Expires 3/31/00                                                [Page 48]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

2.64 dmtfFibreChannelAdapter

   Capabilities of a fibre channel adapter

      ( <oid-at261> NAME 'maxFrameSize'
        DESC 'The maximum frame size, in bytes, supported by the Adapter.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at262> NAME 'supportedCOS'
        DESC 'The Fibre Channel Classes of Service that are supported by
              the Adapter, on its Ports. The currently negotiated COS for
              a connection is a property (NegotiatedCOS) on the
              FibrePortActiveLogin association.  Allowed values are:
              "Unknown", "1", "2", "3", "4", "6", "F".'
        SYNTAX integer
      )

      ( <oid-at263> NAME 'fC4TypesSupported'
        DESC 'An array of integers indicating the Fibre Channel FC-4
           protocols supported by the Adapter. The protocols that are
           active and running are shown in the CurrentFC4Types
           property. The values used in this array are taken from the
           FC-GS2 (bitmapped) field defined in Table 11 of the
           standard. Also, FC-SB-2 codes are included from the T11
           document, 236V0. If the FC4 Type is "Vendor Unique"then the
           specific vendor values (in the range, 0xE0 to 0xFF) should
           be listed in the FC4VendorUniqueTypes property.'
        SYNTAX integer
      )

      ( <oid-at264> NAME 'fC4VendorUniqueTypes'
        DESC 'When the FC4TypesSupported array contains the value 255
           "Vendor Unique", then this attribute lists of all the
           vendor specific protocols supported by the Adapter. These
           values are in the range, 0xE0 to 0xFF.'
        SYNTAX integer
      )

      ( <oid-at265> NAME 'currentFC4Types'
        DESC 'An array of integers indicating the Fibre Channel FC-4
           protocols currently running on the Adapter. A list of all
           protocols supported by the Adapter is shown in the
           FC4TypesSupported property.'
        SYNTAX integer
      )

Expires 3/31/00                                                [Page 49]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at266> NAME 'currentFC4VendorTypes'
        DESC 'When the CurrentFC4Types array contains the value 255
           "Vendor Unique", then this attribute lists all the vendor
           specific protocols running on the Adapter.'
        SYNTAX integer
      )

      ( <oid-at267> NAME 'resourceAllocationTimeout'
        DESC 'timeout value (in milliseconds) for determining
           when to reinstate a Recovery_Qualifier. The default value
           is 120 seconds (120000 milliseconds). It is typically set
           to the ErrorDetectTimeout value + 2*(fabric delay time).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at268> NAME 'errorDetectTimeout'
        DESC 'timeout value (in milliseconds) for determining that an
           error has occurred. The default value is 10 seconds (10000
           milliseconds).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc115> NAME 'dmtfFibreChannelAdapter'
        DESC 'Capabilities of a Fibre Channel Adapter.'
        SUP dmtfNetworkAdapter
        MUST (maxFrameSize $ supportedCOS $ fC4TypesSupported $
           fC4VendorUniqueTypes $ currentFC4Types $
           currentFC4VendorTypes $ capabilities $
           capabilityDescriptions $ resourceAllocationTimeout $
           errorDetectTimeout)
      )

2.65 dmtfFibrePort

   This class models capabilities of a fibre channel port device.

      ( <oid-at269> NAME 'addressIdentifier'
        DESC 'An address value used to identify the source (S_ID) or
              destination (D_ID) of a frame. The FC-SW standard includes
           a table of special address identifier values and their
           meanings. Consult the FC-SW documentation for additional
           information.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at270> NAME 'supportedPortTypes'
        DESC 'An array indicating the modes in which the Port can
           operate. A particular mode may be listed multiple times in

Expires 3/31/00                                                [Page 50]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           the SupportedPortTypes array to define that
           multiple, unique version levels are supported. Version
           information is defined in the PortTypeVersions property.
           Allowed values are: "Unknown", "N", "NL-Private",
           "NL-Public", "E", "F", "FL".'
        SYNTAX integer
      )

      ( <oid-at271> NAME 'portTypeVersions'
        DESC 'Version information for each of the SupportedPortTypes. A
           particular PortType (mode) may be listed multiple times in
           the SupportedPortTypes array to define multiple,
           unique version levels.'
        SYNTAX string
      )

      ( <oid-at272> NAME 'enabledPortTypes'
        DESC 'The specific modes currently enabled for the Port. The
              values are equal to, or a subset of the values in the
           SupportedPortTypes array.'
        SYNTAX integer
      )

      ( <oid-at273> NAME 'enabledVersions'
        DESC 'Version information for each of the EnabledPortTypes. A
           particular PortType (mode) may be listed multiple times in
           the EnabledPortTypes array to define multiple,
           unique version levels.'
        SYNTAX string
      )

      ( <oid-at274> NAME 'currentPortType'
        DESC 'The specific mode in which the Port is currently
           running. The value is one entry from the
           EnabledPortTypes array.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at275> NAME 'currentVersion'
        DESC 'Version information for the CurrentPortType that is
           active.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at276> NAME 'aliasAddresses'
        DESC 'One or more address identifiers that may be recognized by
           the Port, in addition to its port-specific
           identifier. Multicast or hunt group addresses that are

Expires 3/31/00                                                [Page 51]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           recognized by the Port would be identified in this array.'
        SYNTAX integer
      )

      ( <oid-at277> NAME 'receiverTransmitterTimeout'
        DESC 'Timeout value in milliseconds used to determine when loss
              of synchronization has occurred. The typical default is 100
           msec.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at278> NAME 'bypassedState'
        DESC 'Indication of whether the Port is currently bypassed
           (value=2) or not (value=1). A value of 3 ("Forced Insert")
           describes that the Port is forced active, when it would
              otherwise be "Bypassed". Allowed values are: "Unknown",
           "Not Bypassed", "Bypassed", "Forced Insert".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc116> NAME 'dmtfFibrePort'
        DESC 'Capabilities of a Fibre Channel Port Device.'
        SUP dmtfLogicalPort
        MUST (addressIdentifier $ supportedPortTypes $ portTypeVersions $
           enabledPortTypes $ enabledVersions $ currentPortType $
           currentVersion $ aliasAddresses $
           receiverTransmitterTimeout $ bypassedState)
      )

2.66 dmtfFibrePortOnFCAdapterAuxClass

   This auxiliary class associates a fibre port with a fibre channel
   adapter. Cardinalities are defined to show the intent and usage of
   the model, that an Adapter is synonymous with its Port (connection
   point). Therefore, antecedentRefs may only point to a single
   dmtfFibreChannelAdapter objects and dependentRefs may only point to a
   single dmtfFibrePort object.

   Where more than one Port may be active at a time, individual Adapters
   with individual operating data and characteristics really exist. If
   there are multiple connection points, but they exist only to provide
   multiple physical form factors (only one connection may be active at
   a time), then one fibre channel adapter and one fibre port (the
   active one) exist. On the hardware side, the realizations of these
   entities in dmtfPhysicalElement objects may be as a dmtfCard (for
   example) with multiple dmtfPhysicalConnectors.

      ( <oid-oc117> NAME 'dmtfFibrePortOnFCAdapterAuxClass'

Expires 3/31/00                                                [Page 52]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        DESC 'associates a FibrePort with a FibreChannelAdapter.'
        SUP dmtfPortOnDeviceAuxClass AUXILIARY
      )

2.67 dmtfFibrePortActiveLoginAuxClass

   This auxiliary class shows that two fibre ports are connected via a
   login and have negotiated their class of service, frame size and
   other link characteristics, as specified by an instance of this
   class.  Thus, the RDN is composed of the login originator's and
   responder's keys plus the class of service, a unique combination that
   prevents subclassing this class from dmtfDeviceConnectionAuxClass.

      ( <oid-at279> NAME 'loginOriginatorRefs'
        DESC 'The originator of the login.  May be used as an RDN.'
        SYNTAX DN
      )

      ( <oid-at280> NAME 'loginResponderRefs'
        DESC 'The responder to the login.  May be used as an RDN.'
        SYNTAX DN
      )

      ( <oid-at281> NAME 'negotiatedCOS'
        DESC 'The Fibre Channel Class of Service that is currently
              running between the Ports. Since two Ports can be
           simultaneously connected at different Classes of Service,
           this property had to be part of the object's key and
           therefore, an instance's identity.  May therefore be used
           as an RDN. Allowed values are: "Unknown", "1", "2", "3",
           "4",  "6", "F".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at282> NAME 'negotiatedFrameSize'
        DESC 'The Fibre Channel frame size, in bytes, that is currently
           negotiated between the two Ports.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at283> NAME 'aCKModel'
        DESC 'Acknowledgement model negotiated during Port login. For
          example, ACK-1 shows that each frame should be
          acknowledged. Allowed values are: "Unknown", "ACK-0",
          "ACK-1", "ACK-N".'
        SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 53]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at284> NAME 'bufferToBufferModel'
        DESC 'The buffer-to-buffer model negotiated during Port
           login. Either the model defined by the FC-PH standard is
           used (value=1, "Regular") or an "Alternate" model is
           negotiated.  Allowed values are: "Unknown", "Regular",
           "Alternate".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at285> NAME 'originatorBufferCredit'
        DESC 'OriginatorBufferCredit reflects the buffer credit of the
           Port defined as the LoginOriginator. It is the number of
           frame buffers made available BY the originating Port, TO
           the responder Port. Buffer credits are used in point to
           point connections, when an NL-Local Port is logged into
           another NL-Local Port, and when Nx Ports are logged into Fx
           Ports. In other scenarios, this value is undefined.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at286> NAME 'responderBufferCredit'
        DESC 'ResponderBufferCredit reflects the buffer credit of the
           Port defined as the LoginResponder. It is the number of
           frame buffers made available BY the responder Port, TO the
           originating Port. Buffer credits are used in point to point
           connections, when an NL-Local Port is logged into another
           NL-Local Port, and when Nx Ports are logged into Fx
           Ports. In other scenarios, this value is undefined.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at287> NAME 'originatorEndCredit'
        DESC 'OriginatorEndCredit reflects the end credit of the Port
           defined as the LoginOriginator. It is the number of frame
           buffers made available BY the originating Port, TO the
           responder Port. End credits are used in point to point
           connections, when an NL-Local Port is logged into another
           NL-Local Port, and when Nx Ports are logged into remote Nx
           Ports. In other scenarios, this value is undefined.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at288> NAME 'responderEndCredit'
        DESC 'ResponderEndCredit reflects the end credit of the Port
           defined as the LoginResponder. It is the number of frame
           buffers made available BY the responder Port, TO the
           originating Port. End credits are used in point to point
           connections, when an NL-Local Port is logged into another

Expires 3/31/00                                                [Page 54]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           NL-Local Port, and when Nx Ports are logged into remote Nx
           Ports. In other scenarios, this value is undefined.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc118> NAME 'dmtfFibrePortActiveLoginAuxClass'
        DESC shows that two FibrePorts are connected via a login.'
        SUP top AUXILIARY
        MUST (dmtfFibrePortRefs $ dmtfFibrePortRefs $ negotiatedCOS $
           negotiatedFrameSize $ negotiatedSpeed $ aCKModel $
           bufferToBufferModel $ originatorBufferCredit $
           responderBufferCredit $ originatorEndCredit $
           responderEndCredit)
      )

2.68 dmtfFibreProtocolService

   To be defined later.

      ( <oid-oc119> NAME 'dmtfFibreProtocolService'
        DESC 'FibreProtocolService abstracts and allows the management of
              the Alias, Management, Time, Security, Directory (Naming)
           and other services and functions available in a Fibre
           Channel network. This class will be further defined in a
           later release of CIM.'
        SUP dmtfService
      )

2.69 dmtfNetworkAdapterRedundancyComponentAuxClass

   This auxiliary class shows the role that a network adapter provides
   in an extra capacity group that provides load balancing.  In this
   class, groupRefs point to dmtfExtraCapacityGroup objects and partRefs
   point to dmtfNetworkAdapter objects.

      ( <oid-at289> NAME 'scopeOfBalancing'
        DESC 'Shows the scope of load balancing for the
              NetworkAdapters involved in the RedundancyGroup. Load
           balancing may be restricted to transmitting data only
           (value=1), receiving data only (value=2), or used for both
            transmit and receive (value=3).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at290> NAME 'primaryAdapter'
        DESC 'Boolean indicating whether the Network Adapter is an
           original primary adapter (value=1), a preferred primary
           adapter (2), or both (3). Values of "Unknown" (0) and

Expires 3/31/00                                                [Page 55]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           "Not Applicable" (4) may also be specified.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc120> NAME 'dmtfNetworkAdapterRedundancyComponentAuxClass'
        DESC 'shows the role that a NetworkAdapter plays in a
           ExtraCapacityGroup, providing load balancing.'
        SUP dmtfRedundancyComponentAuxClass AUXILIARY
        MUST (dmtfExtraCapacityGroupRefs $ dmtfNetworkAdapterRefs $
           scopeOfBalancing $ primaryAdapter)
      )

2.70 dmtfNetworkVirtualAdapterAuxClass

   This association shows that a network adapter is actually the result
   of several adapters participating in a load balanced redundancy
   group.  In it, systemElementRefs point to dmtfNetworkAdapter Objects
   and sameElementRefs point to dmtfExtraCapacityGroup Objects.

      ( <oid-oc121> NAME 'dmtfNetworkVirtualAdapterAuxClass'
        DESC 'describes that an instance of NetworkAdapter is actually
           the result of several Adapters participating in a load
           balanced RedundancyGroup.'
        SUP dmtfLogicalIdentityAuxClass AUXILIARY
      )

2.71 dmtfController

   This class is a superclass for grouping the miscellaneous control-
   related devices that exist and is an abstraction for devices with a
   single protocol stack, which exist primarily for communication to,
   and control or reset of downstream devices.

      ( <oid-at291> NAME 'protocolSupported'
        DESC 'The protocol used by the Controller to access "controlled"
Devices.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at292> NAME 'maxNumberControlled'
        DESC 'Maximum number of directly addressable entities supported
           by this Controller. A value of 0 should be used if the
           number is unknown or unlimited.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc122> NAME 'dmtfController'
        DESC 'superclass for grouping the miscellaneous control-related
              Devices that exist.'

Expires 3/31/00                                                [Page 56]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        SUP dmtfLogicalDevice ABSTRACT
        MUST (timeOfLastReset $ protocolSupported $ maxNumberControlled)
      )

2.72 dmtfControlledByAuxClass

   This auxiliary class shows those devices are commanded by or accessed
   through a controller. In this class, antecedentRefs point to
   dmtfController objects and dependentRefs point to dmtfLogicalDevice
   objects.

      ( <oid-at293> NAME 'accessState'
        DESC 'shows whether the Controller is actively commanding or
           accessing the Device (value=1) or not (value=2). Also, the
           value, "Unknown" (0) is defined. This information is
           necessary when a LogicalDevice can be commanded by, or
           accessed through, multiple Controllers.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at294> NAME 'timeOfDeviceReset'
        DESC 'The time that the downstream Device was last reset by the
           Controller.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-oc123> NAME 'dmtfControlledByAuxClass'
        DESC 'shows those Devices are commanded by or accessed
              through which controllers'
        SUP dmtfDeviceConnectionAuxClass AUXILIARY
        MUST (accessState $ timeOfDeviceReset)
      )

2.73 dmtfParallelController

   This class describes the capabilities of a parallel controller.

      ( <oid-at295> NAME 'dMASupport'
        DESC 'Set to true if the ParallelController supports DMA.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at296> NAME 'security'
        DESC 'An enumeration indicating the operational security for the
              Controller. For example, information that the Device's
           external interface is locked out (value=4) or "Boot"
           (value=6) can be described using this property.'
        SYNTAX integer SINGLE-VALUE

Expires 3/31/00                                                [Page 57]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-oc124> NAME 'dmtfParallelController'
        DESC 'Capabilities of the ParallelController.'
        SUP dmtfController
        MUST (dMASupport $ capabilities $ capabilityDescriptions $
           security)
      )

2.74 dmtfSerialController

   This class describes capabilities of a serial controller.

      ( <oid-at297> NAME 'maxBaudRate'
        DESC 'Maximum baud rate in Bits per Second supported by the
              SerialController.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc125> NAME 'dmtfSerialController'
        DESC 'Capabilities of the SerialController.'
        SUP dmtfController
        MUST (capabilities $ capabilityDescriptions $ maxBaudRate $
              security)
      )

2.75 dmtfSerialInterfaceAuxClass

   This auxiliary class is a subclass of dmtfControlledByAuxClass.  It
   shows those devices are accessed through a serial controller and the
   characteristics of this access.  In this class, antecedentRefs point
   to dmtfSerialController objects.

      ( <oid-at298> NAME 'numberOfStopBits'
        DESC 'Number of stop bits to be transmitted.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at299> NAME 'parityInfo'
        DESC 'Information on the parity setting for transmitted data. No
           parity (value=1), even (2) or odd (3) can be specified.
           Allowed values are: "Unknown", "None", "Even", "Odd".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at300> NAME 'flowControlInfo'
        DESC 'An integer enumeration indicating the flow control
              (Xon-Xoff and/or RTS/CTS) for transmitted data.  Allowed

Expires 3/31/00                                                [Page 58]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              values are: "Unknown", "Not Supported", "None", "XonXoff",
           "RTS/CTS", "Both XonXoff and RTS/CTS".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc126> NAME 'dmtfSerialInterfaceAuxClass'
        DESC 'shows those Devices are accessed through the
           SerialController and the characteristics of this access.'
        SUP dmtfControlledByAuxClass AUXILIARY
        MUST (negotiatedDataWidth $ numberOfStopBits $ parityInfo $
              flowControlInfo)
      )

2.76 dmtfSCSIController

   This class provides capabilities of a SCSI controller.

      ( <oid-at301> NAME 'protectionManagement'
        DESC 'An integer enumeration indicating whether the
           SCSIController provides redundancy or protection against
           device failures.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at302> NAME 'maxDataWidth'
        DESC 'Maximum data width (in bits) supported by the
              SCSIController.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at303> NAME 'maxTransferRate'
        DESC 'Maximum transfer rate (in Bits per Second) supported by the
           SCSIController.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at304> NAME 'signalCapabilities'
        DESC 'Signal capabilities that can be supported by the
           SCSIController. For example, the Controller may support
           "Single Ended". Here, the values 3 and 4 would be
           written to the SignalCapabilities array.'
        SYNTAX integer
      )

      ( <oid-oc127> NAME 'dmtfSCSIController'
        DESC 'Capabilities of the SCSIController.'
        SUP dmtfController
        MUST (protectionManagement $ maxDataWidth $ maxTransferRate $

Expires 3/31/00                                                [Page 59]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           signalCapabilities)
      )

2.77 dmtfSCSIInterfaceAuxClass

   This auxiliary class shows those devices are accessed trhough a SCSI
   controller and the characteristics of which access.  As this class is
   a subclass of dmtfControoledByAuxClass, antecedentRefs point to
   dmtfSCSICOntroller objects.

      ( <oid-at305> NAME 'initiatorId'
        DESC 'The SCSI Initiator ID.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at306> NAME 'targetId'
        DESC 'The SCSI Target ID.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at307> NAME 'targetLUN'
        DESC 'The SCSI Target LUN.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at308> NAME 'sCSIReservation'
        DESC 'SCSIReservation shows the type of SCSI reservation that
           currently exists between the source and destination.
           Allowed values are: "Unknown", "None", "Simple",
           "Persistent".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at309> NAME 'sCSISignal'
        DESC 'The SCSI signal characteristics being used for this
           connection. The value listed here must also be listed in
           the SCSIController's SignalCapabilities field.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at310> NAME 'maxQueueDepth'
        DESC 'Maximum number of Command Descriptor Blocks (CDBs) that can
           be supported by the target. This data can not be obtained
           under all circumstances.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at311> NAME 'queueDepthLimit'

Expires 3/31/00                                                [Page 60]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        DESC 'The maximum number of concurrent Command Descriptor Blocks
           (CDBs) that the initiator will send to the target. This
           value should never be greater than MaxQueueDepth.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc128> NAME 'dmtfSCSIInterfaceAuxClass'
        DESC 'shows those Devices are accessed through a
          SCSIController and the characteristics of this access.'
        SUP dmtfControlledByAuxClass AUXILIARY
        MUST (initiatorId $ targetId $ targetLUN $ sCSIReservation $
           sCSISignal $ maxQueueDepth $ queueDepthLimit)
      )

2.78 dmtfVideoController

   This class provides capabilities for a video controller.

      ( <oid-at312> NAME 'videoProcessor'
        DESC 'free-form string describing the video processor/controller'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at313> NAME 'videoMemoryType'
        DESC 'integer enumeration indicating the type of video memory'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at314> NAME 'numberOfVideoPages'
        DESC 'number of video pages supported given the current
              resolution and available memory'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at315> NAME 'maxMemorySupported'
        DESC 'maximum amount of memory supported in bytes'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at316> NAME 'acceleratorCapabilities'
        DESC 'a bag of integers indicating the graphics and 3D
           capabilities of the video controller'
        SYNTAX integer
      )

      ( <oid-at317> NAME 'currentBitsPerPixel'
        DESC 'The number of bits used to display each pixel'
        SYNTAX integer SINGLE-VALUE

Expires 3/31/00                                                [Page 61]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at318> NAME 'currentHorizontalResolution'
        DESC 'current number of horizontal pixels'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at319> NAME 'currentVerticalResolution'
        DESC 'current number of vertical pixels'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at320> NAME 'currentRefreshRate'
        DESC 'current refresh rate in hertz'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at321> NAME 'currentScanMode'
        DESC 'current scan mode. "Interlaced" (3) or "Non Interlaced" (4)
              can be defined here'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at322> NAME 'currentNumberOfRows'
        DESC 'current number of rows when in character mode'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at323> NAME 'currentNumberOfColumns'
        DESC 'current number of columns when in character mode'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at324> NAME 'currentNumberOfColors'
        DESC 'number of colors supported at current resolution'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc129> NAME 'dmtfVideoController'
        DESC 'capabilities of the VideoController'
        SUP dmtfController
        MUST (description $ videoProcessor $ videoMemoryType $
           numberOfVideoPages $ maxMemorySupported $
           acceleratorCapabilities $ capabilityDescriptions $
           currentBitsPerPixel $ currentHorizontalResoultion $
           currentVerticalResolution $ maxRefreshRate $
              minRefreshRate $ currentRefreshRate $ currentScanMode $
           currentNumberOfRows $ currentNumberOfColumns $

Expires 3/31/00                                                [Page 62]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           currentNumberOfColors)
      )

2.79 dmtfPCVideoController

   This class specifies capabilities of a PC video controller

      ( <oid-at325> NAME 'videoArchitecture'
        DESC 'The video architecture. For example, VGA (value=5) or PC-98
           (160) may be specified.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at326> NAME 'videoMode'
        DESC 'Current video mode.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at327> NAME 'numberOfColorPlanes'
        DESC 'Current number of color planes. If this value is not
           applicable for the current video configuration, enter 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc130> NAME 'dmtfPCVideoController'
        DESC 'Capabilities of a PCVideoController'
        SUP dmtfVideoController
        MUST (videoArchitecture $ videoMode $ numberOfColorPlanes)
      )

2.80 dmtfAGPVideoController

   This class specifies capabilities of an AGP video controller.

      ( <oid-at328> NAME 'nonlocalVideoMemorySize'
        DESC 'Size of the non-local video memory in KB.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at329> NAME 'localBusWidth'
        DESC 'Width of the internal bus in the graphics Controller, in
           bits.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at330> NAME 'usageModel'
        DESC 'An integer enumeration indicating the usage model of the
           graphics Controller. Usage model shows how the

Expires 3/31/00                                                [Page 63]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           Controller does manipulations of graphics surfaces,
           textures, etc. in memory. DMA shows that the graphics
           Controller brings structures from the system memory to its
           local memory to make needed manipulations or
           renderings. Execute specifies that the graphics Controller
           can directly access a specified region in main memory
           (called the graphics aperture) using GART - Graphics
           Aperture Remapping Table. It then does manipulations in
           that range as if that whole graphics aperture were part of
           its local memory. A value of "Both" DMA and Execute models
           may also be specified.  Allowed values are: "Unknown",
           "Other", "Execute", "DMA", "Both".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at331> NAME 'dataTransferRate'
        DESC 'An integer enumeration indicating the data transfer rate of
           the graphics Controller.  Allowed values are: "Unknown",
           "Other", "1X", "2X", "4X".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at332> NAME 'addressingMode'
        DESC 'An integer enumeration indicating the addressing mode of
           the graphics Controller.  Allowed values are: "Unknown",
           "Other", "Sideband", "Pipeline".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at333> NAME 'maximumAGPCommandQueuePath'
        DESC 'The maximum number of AGP Transaction requests that the
           master (AGP Graphics Controller) is allowed to enqueue into
           the target.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at334> NAME 'maxNumberOfPipelinedAGPTransactions'
        DESC 'The number of AGP Transaction that the core logic (chipset)
           can accept into its transaction request queue from the
           Controller.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at335> NAME 'graphicsApertureSize'
        DESC 'Size of the graphics aperture in KB.'
        SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 64]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at336> NAME 'aGPSpecificationVersionConformance'
        DESC 'A string containing the AGP specification version to which
           this graphics Controller conforms.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc131> NAME 'dmtfAGPVideoController'
        DESC 'Capabilities of an AGPVideoController.'
        SUP dmtfVideoController
        MUST (capabilities $ ] $ nonlocalVideoMemorySize $
           localBusWidth $ usageModel $ dataTransferRate $
           addressingMode $ maximumAGPCommandQueuePath $
           maxNumberOfPipelinedAGPTransactions $
           graphicsApertureSize $ aGPSpecificationVersionConformance)
      )

2.81 dmtfAGPSoftwareFeature

   This class adds two attributes to dmtfSoftwareFeature to represent
   the capabilities of an AGP device driver so that an instance of this
   class could be associated with the driver's software element using
   the dmtfSoftwareFeatureSoftwareElementsAuxClass relationship. The
   driver's software element is associated with the AGP video controller
   via the dmtfDeviceSoftwareAuxClass relationship.

      ( <oid-at337> NAME 'characteristics'
        DESC 'An array of integers indicating various capabilities and
           characteristics of the AGPVideoController.  Allowed values
           are: "Unknown", "Other", "OS support",
           "Hardware Acceleration", "Hardware Blit", "OpenGL Support",
           "Cache Coherency".'
        SYNTAX integer
      )

      ( <oid-at338> NAME 'characteristicDescriptions'
        DESC 'An array of free-form strings providing more detailed
           explanations for any of the features shown in the
           characteristics array.'
        SYNTAX string
      )

      ( <oid-oc132> NAME 'dmtfAGPSoftwareFeature'
        DESC 'adds two attributes to SoftwareFeature
           to represent the capabilities of an AGP device driver.'
        SUP dmtfSoftwareFeature
        MUST (characteristics $ characteristicDescriptions)
      )

Expires 3/31/00                                                [Page 65]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.82 dmtfVideoControllerResolution

   This class describes the various video modes that a video controller
   can support. Video modes are defined by the possible horizontal and
   vertical resolutions, refresh rate, scan mode and number of colors
   settings supported by a controller. The resolutions, etc. that are in
   use, are the values specified in the video controller object.

      ( <oid-at339> NAME 'numberOfColors'
        DESC 'Number of colors supported at the current resolutions.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc133> NAME 'dmtfVideoControllerResolution'
        DESC 'VideoControllerResolution describes the various video modes
           that a VideoController can support.'
        SUP dmtfSetting
        MUST (settingID $ horizontalResolution $ verticalResolution $
           refreshRate $ minRefreshRate $ maxRefreshRate $ scanMode $
           numberOfColors)
      )

2.83 dmtfVideoSettingAuxClass

   This auxiliary class allows a dmtfVideoControllerResolution object to
   be associated with the dmtfVideoController object to which it
   applies.  In this class settingRefs point to
   dmtfVideoControllerResolution objects and elementRefs point to
   dmtfVideoController objects.

      ( <oid-oc134> NAME 'dmtfVideoSettingAuxClass'
        DESC 'associates the VideoControllerResolution Setting with the
           Controller(s) to which it applies.'
        SUP dmtfElementSettingAuxClass AUXILIARY
      )

2.84 dmtfPCIController

   This is the supper class for PCI bridges and devices, which model
   adapters and bridges on a PCI bus.  The attributes here are taken
   from the various PCI specifications published by the PCI SIG.

      ( <oid-at340> NAME 'commandRegister'
        DESC 'current content of the basic control register'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at341> NAME 'deviceSelectTiming'

Expires 3/31/00                                                [Page 66]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        DESC 'the slowest device select time for a target device'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at342> NAME 'classCode'
        DESC 'identifier of the basic function of the PCI device'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at343> NAME 'cacheLineSize'
        DESC 'system cache line size in doubleword increments'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at344> NAME 'latencyTimer'
        DESC 'defines minimum amount of time (in PCI clock cycles), that
           the bus master can retain ownership of the bus'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at345> NAME 'interruptPin'
        DESC 'defines the interrupt request pin'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at346> NAME 'expansionROMBaseAddress'
        DESC 'doubleword expansion ROM base memory address
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at347> NAME 'selfTestEnabled'
        DESC 'reports if the PCI can perform the self test function'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc135> NAME 'dmtfPCIController'
        DESC 'superclass for PCIBridge and PCIDevice classes'
        SUP dmtfController
        MUST (commandRegister $ capabilities $ capabilityDescriptions $
           deviceSelectTiming $ classCode $ cacheLineSize $
           latencyTimer $ interruptPin $ expansionROMBaseAddress $
           selfTestEnabled)
      )

2.85 dmtfPCIDevice

   This class provides capabilities of a PCI device controller on an
   adapter card.

Expires 3/31/00                                                [Page 67]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at348> NAME 'baseAddress'
        DESC 'Array of doubleword base memory addresses.'
        SYNTAX integer
      )

      ( <oid-at349> NAME 'subsystemID'
        DESC 'Subsystem identifier code.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at350> NAME 'subsystemVendorID'
        DESC 'Subsystem vendor ID. ID information is reported from a
              PCIDevice via protocol-specific requests.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at351> NAME 'min_GrantTime'
        DESC 'Register indicating how long the master would like to retain
              PCI bus ownership whenever it starts a transaction. A
              zero value shows no requirement. This time is in units
           of 250 nanoseconds.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at352> NAME 'max_Latency'
        DESC 'Register specifying how often the device needs access to
           the PCI bus in 250ns. A zero value shows no
           requirement.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc136> NAME 'dmtfPCIDevice'
        DESC 'Capabilities of a PCI device controller on an adapter
           card.'
        SUP dmtfPCIController
        MUST (baseAddress $ subsystemID $ subsystemVendorID $
           min_GrantTime $ max_Latency)
      )

2.86 dmtfPCIBridge

   This class presents the capabilities of a PCI controller providing
   bridge to bridge capability.

      ( <oid-at353> NAME 'bridgeType'
         DESC 'The type of bridge.'
         SYNTAX integer SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 68]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at354> NAME 'secondaryLatencyTimer'
        DESC 'The timeslice for the secondary interface when the bridge
              is acting as an initiator. A zero value shows no
              requirement.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at355> NAME 'subordinateBusNumber'
        DESC 'The number of the highest numbered bus that exists behind
              the bridge.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at356> NAME 'secondayBusNumber'
        DESC 'The number of the PCI bus segment to which the secondary
           interface of the bridge is connected.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at357> NAME 'primaryBusNumber'
        DESC 'The number of the PCI bus segment to which the primary
           interface of the bridge is connected.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at358> NAME 'secondaryStatusRegister'
        DESC 'The contents of the Bridge's SecondaryStatusRegister. For
           more information on the contents of this register, refer to
           the PCI-to-PCI Bridge Architecture Specification.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at359> NAME 'secondaryBusDeviceSelectTiming'
        DESC 'The slowest device select timing for a target device on the
           secondary bus.  Allowed values are: "Unknown", "Other",
           "Fast", "Medium", "Slow", "Reserved".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at360> NAME 'prefetchLimitUpper32'
        DESC 'Upper 32 bits of the supported prefetch end address when
              64-bit addressing is used. The lower 32 bits are assumed to
           be all 1's.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at361> NAME 'prefetchBaseUpper32'
        DESC 'Upper 32 bits of the supported prefetch base address when

Expires 3/31/00                                                [Page 69]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           64-bit addressing is used. The lower 32 bits are assumed to
           be 0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at362> NAME 'iOLimitUpper16'
        DESC 'Upper 16 bits of the supported I/O end address when 32-bit
           I/O addressing is used. The lower 16 bits are assumed to be
           all 1's.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at363> NAME 'iOBaseUpper16'
        DESC 'Upper 16 bits of the supported I/O base address when 32-bit
           I/O addressing is used. The lower 16 bits are assumed to be
           0.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc137> NAME 'dmtfPCIBridge'
        DESC 'Capabilities of a PCI controller providing bridge to bridge
           capability.'
        SUP dmtfPCIController
        MUST (baseAddress $ bridgeType $ secondaryLatencyTimer $
              subordinateBusNumber $ secondayBusNumber $
           primaryBusNumber $ secondaryStatusRegister $
           secondaryBusDeviceSelectTiming $ iOLimit $ iOBase $
           memoryLimit $ memoryBase $ prefetchMemoryLimit $
           prefetchMemoryBase $ prefetchLimitUpper32 $
           prefetchBaseUpper32 $ iOLimitUpper16 $ iOBaseUpper16)
      )

2.87 dmtfUSBController

   This class describes the capabilities of an USB host controller.

      ( <oid-at364> NAME 'uSBVersion'
        DESC 'Shows the latest USB Version supported by the
           Controller. The property is expressed as a Binary-Coded
           Decimal (BCD) where a decimal point is implied between the
           2nd and 3rd digits. For example, a value of 0x201 shows
           that version 2.01 is supported.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at365> NAME 'interfaceType'
        DESC 'The type of interface used between the host system software
           and the USBController.  Allowed values are: "Unknown",

Expires 3/31/00                                                [Page 70]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           "Other", "UHCI", "OHCI".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at366> NAME 'controllerVersion'
        DESC 'Shows the version of the USB Host Controller register
           set, specific to the InterfaceType. The property is
           expressed as a Binary-Coded Decimal (BCD) value where a
           decimal point is implied between the 2nd and 3rd
           digits. For example, a value of 0x103 shows that
           version 1.03 is supported.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc138> NAME 'dmtfUSBController'
        DESC 'Capabilities of an USB Host Controller.'
        SUP dmtfController
        MUST (uSBVersion $ interfaceType $ controllerVersion)
      )

2.88 dmtfUSBPort

   This class models a port on an USB hub

      ( <oid-at367> NAME 'power'
        DESC 'The USB Port's power capability. The current specification
           defines that 1 or 5 loads can be supported (values 2 or 3
           would be specified, respectively).  Allowed values are:
           "Unknown", "Other", "1 Unit Load", "5 Unit Loads".'
        SYNTAX integer
        SINGLE-VALUE
      )

      ( <oid-at368> NAME 'suspended'
        DESC 'Shows whether the Port is currently Suspended.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at369> NAME 'overcurrent'
        DESC 'Shows whether the Port is disabled because of an
           overcurrent event.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc139> NAME 'dmtfUSBPort'
        DESC 'A Port on an USBHub.'
        SUP dmtfLogicalPort
        MUST (speed $ power $ statusInfo $ availability $ suspended $

Expires 3/31/00                                                [Page 71]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           overcurrent)
      )

2.89 dmtfManagementController

   This class describes the capabilities of a management controller.  It
   will be defined later.

      ( <oid-oc140> NAME 'dmtfManagementController'
        DESC 'Capabilities of a ManagementController.'
        SUP dmtfController
      )

2.90 dmtfIDEController

   This class describes the capabilities of an IDE controller.  It will
   be defined later.

      ( <oid-oc141> NAME 'dmtfIDEController'
        DESC 'Capabilities of an IDEController.'
        SUP dmtfController
      )

2.91 dmtfPCMCIAController

   This class describes the capabilities of a PCMCIA controller.  It
   will be defined later.

      ( <oid-oc142> NAME 'dmtfPCMCIAController'
        DESC 'Capabilities of a PCMCIAController.'
        SUP dmtfController
      )

2.92 dmtfInfraredController

   This class describes the capabilities of an infrared controller.  It
   will be defined later.

      ( <oid-oc143> NAME 'dmtfInfraredController'
        DESC 'Capabilities of an InfraredController.'
        SUP dmtfController
      )

2.93 dmtfESCONController

   This class describes the capabilities of an ESCON controller.  It
   will be defined later.

Expires 3/31/00                                                [Page 72]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-oc144> NAME 'dmtfESCONController'
        DESC 'Capabilities of an ESCONController.'
        SUP dmtfController
      )

2.94 dmtfMediaAccessDevice

   This class describes the capabilities of a media access device.

      ( <oid-at370> NAME 'errorMethodology'
        DESC 'a free-form string describing the type(s) of error
           detection and correction supported by this Device.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at371> NAME 'compressionMethod'
        DESC 'A free form string indicating the algorithm or tool used by
              the device to support compression.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at372> NAME 'numberOfMediaSupported'
        DESC 'When the MediaAccessDevice supports multiple individual
           Media, this property defines the maximum number that can
           be supported or inserted.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at373> NAME 'maxMediaSize'
        DESC 'Maximum size, in KBytes, of media supported by this Device.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at374> NAME 'defaultBlockSize'
        DESC 'Default block size, in bytes, for this Device.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at375> NAME 'maxBlockSize'
        DESC 'Maximum block size, in bytes, for media accessed by this
           Device.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at376> NAME 'minBlockSize'
        DESC 'Minimum block size, in bytes, for media accessed by this
           Device.'
        SYNTAX integer SINGLE-VALUE

Expires 3/31/00                                                [Page 73]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      )

      ( <oid-at377> NAME 'needsCleaning'
        DESC 'Boolean indicating that the MediaAccessDevice needs
           cleaning. Whether manual or automatic cleaning is possible
           is shown in the Capabilities array property.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at378> NAME 'mediaIsLocked'
        DESC 'True shows that the media is locked in the Device and
           can not be ejected. For non-removeable Devices, this value
           should be true.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at379> NAME 'lastCleaned'
        DESC 'The date and time on which the Device was last cleaned.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-at380> NAME 'maxAccessTime'
        DESC 'Time in milliseconds to move from the first location on the
           Media to the location that is furthest with respect to
           time. For a DiskDrive, this represents full seek + full
           rotational delay. For TapeDrives, this represents a search
           from the beginning of the tape to the most physically
           distant point. (The end of a tape may be at its most
           physically distant point, but this is not necessarily
           true).'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at381> NAME 'uncompressedDataRate'
        DESC 'The sustained data transfer rate in KB/sec that the Device
           can read from and write to a Media. This is a sustained,
           raw data rate. Maximum rates or rates assuming compression
           should not be reported in this property.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at382> NAME 'loadTime'
        DESC 'Time in milliseconds from "load" to being able to read or
           write a Media. For example, for DiskDrives, this is the
           interval between a disk not spinning to the disk reporting
           that it is ready for read/write (ie, the disk spinning at
           nominal speeds). For TapeDrives, this is the time from a
           Media being injected to reporting that it is ready for an

Expires 3/31/00                                                [Page 74]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           application. This is usually at the tape's BOT area.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at383> NAME 'unloadTime'
        DESC 'Time in milliseconds from being able to read or write a
           Media to its "unload". For example, for DiskDrives, this is the
           interval between a disk spinning at nominal speeds and a
           disk not spinning. For TapeDrives, this is the time for a
           Media to go from its BOT to being fully ejected and
           accessible to a PickerElement or human operator.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc145> NAME 'dmtfMediaAccessDevice'
        DESC 'A MediaAccessDevice represents the ability to access one or
           more media and use this media to store and retrieve data.'
        SUP dmtfLogicalDevice
        MUST (capabilities $ capabilityDescriptions $ errorMethodology $
           compressionMethod $ numberOfMediaSupported $ maxMediaSize $
           defaultBlockSize $ maxBlockSize $ minBlockSize $
           needsCleaning $ mediaIsLocked $ security $ lastCleaned $
           maxAccessTime $ uncompressedDataRate $ loadTime $
           unloadTime)
      )

2.95 dmtfDiskDrive

   This class describes the capabilities of a disk drive.  It will be
   defined later.

      ( <oid-oc146> NAME 'dmtfDiskDrive'
        DESC 'Capabilities of a DiskDrive, a subtype of
           MediaAccessDevice.'
        SUP dmtfMediaAccessDevice
      )

2.96 dmtfDisketteDrive

   This class describes the capabilities of a diskette drive.  It will
   be defined later.

      ( <oid-oc147> NAME 'dmtfDisketteDrive'
        DESC 'Capabilities of a DisketteDrive, a subtype of
           MediaAccessDevice.'
        SUP dmtfMediaAccessDevice
      )

Expires 3/31/00                                                [Page 75]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

2.97 dmtfCDROMDrive

   This class describes the capabilities of a CDROM drive.  It will be
   defined later.

      ( <oid-oc148> NAME 'dmtfCDROMDrive'
        DESC 'Capabilities of a CDROMDrive, a subtype of
           MediaAccessDevice.'
    SUP  dmtfMediaAccessDevice
    MUST ()
   )

2.98 dmtfWORMDrive

   This class describes the capabilities of a WORM drive.  It will be
   defined later.

      ( <oid-oc149> NAME 'dmtfWORMDrive'
        DESC 'Capabilities of a WORMDrive, a subtype of
           MediaAccessDevice.'
        SUP dmtfMediaAccessDevice
      )

2.99 dmtfMagnetoOpticalDrive

   This class describes the capabilities of a Magneto Optical drive.  It
   will be defined later.

      ( <oid-oc150> NAME 'dmtfMagnetoOpticalDrive'
        DESC 'Capabilities of a MagnetoOpticalDrive, a
           subtype of MediaAccessDevice.'
    SUP  dmtfMediaAccessDevice
    MUST ()
   )

2.100 dmtfTapeDrive

   This class describes the capabilities of a tape drive.  It will be
   defined later.

      ( <oid-at384> NAME 'eOTWarningZoneSize'
        DESC 'EOTWarningZoneSize shows the size, in bytes, of the
           area designated as "end of tape". Access in this area
           generates an "end of tape" warning.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at385> NAME 'maxPartitionCount'

Expires 3/31/00                                                [Page 76]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        DESC 'Maximum partition count for the TapeDrive.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at386> NAME 'padding'
        DESC 'Padding shows the number of bytes inserted between
           blocks on a tape Media.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at387> NAME 'maxRewindTime'
        DESC 'Time in milliseconds to move from the most physically
           distant point on the tape to the beginning.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc151> NAME 'dmtfTapeDrive'
        DESC 'Capabilities of a TapeDrive, a subtype of
           MediaAccessDevice.'
        SUP dmtfMediaAccessDevice
        MUST (eOTWarningZoneSize $ maxPartitionCount $ padding $
           maxRewindTime)
      )

2.101 dmtfDVDDrive

   This class describes the capabilities of a DVD drive.

      ( <oid-at388> NAME 'formatsSupported'
        DESC 'The CD and DVD formats that are supported by this
           Device.
        SYNTAX integer
      )

      ( <oid-oc152> NAME 'dmtfDVDDrive'
        DESC 'Capabilities of a DVDDrive, a subtype of
           MediaAccessDevice.'
        SUP dmtfMediaAccessDevice
        MUST (formatsSupported)
      )

2.102 dmtfDiskGroup

   This class defines a named collection of disk drives and storage
   extents.

      ( <oid-oc153> NAME 'dmtfDiskGroup'
        DESC 'A DiskGroup is a named collection of DiskDrives and the

Expires 3/31/00                                                [Page 77]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

              StorageExtent(s) accessed via those Drives.'
        SUP dmtfCollectionOfMSEs
        MUST (collectionID)
      )

2.103 dmtfAlarmDevice

   This class represents devices that emits either audible or visible
   indications related to a problem.

      ( <oid-at389> NAME 'audibleAlarm'
        DESC 'Boolean indicating that the Alarm is audible.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at390> NAME 'visibleAlarm'
        DESC 'Boolean indicating that the Alarm is visible.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at391> NAME 'motionAlarm'
        DESC 'Boolean indicating that the Alarm causes motion of the
           Device.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at392> NAME 'urgency'
        DESC 'Urgency is an enumerated value that shows the relative
           frequency at which the Alarm flashes, vibrates and/or emits
           audible tones.  Allowed values are: "Unknown", "Other",
           "Not Supported", "Informational", "Non-Critical",
           "Critical", "Unrecoverable".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at393> NAME 'alarmState'
        DESC 'The current state of the alarm.  Allowed values are:
           "Unknown", "Off", "Steady", "Alternating".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at394> NAME 'audioIndicatorIsDisabled'
        DESC 'True shows that the audio of an AlarmState indicator
           has been disabled (i.e. muted). A disabled state here does
           not imply that the AlarmState is off.'
        SYNTAX boolean SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 78]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at395> NAME 'visualIndicatorIsDisabled'
        DESC 'True shows that the visual of an AlarmState indicator
           has been disabled (i.e. dimmed). A disabled state here does
           not imply that the AlarmState is off.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at396> NAME 'motionIndicatorIsDisabled'
        DESC 'True shows that the motion of an AlarmState indicator
           has been disabled (i.e. stopped). A disabled state here
           does not imply that the AlarmState is off.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc154> NAME 'dmtfAlarmDevice'
        DESC 'An AlarmDevice is a type of Device that emits audible or
           visible indications related to a problem.'
        SUP dmtfLogicalDevice
        MUST (audibleAlarm $ visibleAlarm $ motionAlarm $ urgency $
           alarmState $ audioIndicatorIsDisabled $
           visualIndicatorIsDisabled $ motionIndicatorIsDisabled)
      )

2.104 dmtfAssociatedAlarmAuxClass

   This auxiliary class relates a logical device to the alarm devices
   that show problem. In this class, antecedentRefs point to
   dmtfAlarmDevice objects and dependentRefs point to dmtfLogicalDevice
   objects.

      ( <oid-oc155> NAME 'dmtfAssociatedAlarmAuxClass'
        DESC 'LogicalDevices may have one or more AlarmDevices associated
           with them, to show problem. This
           relationship is shown by the AssociatedAlarm
           dependency.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

2.105 dmtfDoor

   This class is an abstraction of hardware that provides access to the
   internal componentry of a system.

      ( <oid-at397> NAME 'open'
        DESC 'Boolean indicating the "open" (TRUE) or "closed" (FALSE)
              status of the Door.'
        SYNTAX boolean SINGLE-VALUE
      )

Expires 3/31/00                                                [Page 79]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-at398> NAME 'locked'
        DESC 'Boolean indicating that the Door is "locked" (TRUE) or
              "unlocked" (FALSE). When the Door is locked, access to the
           componentry is prevented, without the use of a physical key
           or the issuance of a software unlock command.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at399> NAME 'timeout'
        DESC 'When a Door is "Open", all accessible, moving componentry
           and Device operation are typically stopped.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at400> NAME 'lastOpened'
        DESC 'Date and time that the Door was last opened.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-oc156> NAME 'dmtfDoor'
        DESC 'A Door is the abstraction of hardware providing access to
           the internal componentry of a System.'
        SUP dmtfLogicalDevice
        MUST (open $ locked $ timeout $ lastOpened $ capabilities)
      )

2.106 dmtfDoorAccessToPhysicalElementAuxClass

   This auxiliary class relates doors to the physical elements that are
   accessible from the door.  In it, antecedentRefs point to dmtfDoor
   objects and dependentRefs to dmtfPhysicalElement objects.

      ( <oid-oc157> NAME 'dmtfDoorAccessToPhysicalElementAuxClass'
        DESC 'Doors provide access to PhysicalElements for hot swap,
           repair and similar activities. The entities accessed
           through a Door are shown in this relationship.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

2.107 dmtfDoorAccessToDeviceAuxClass

   This auxiliary class relates doors to the logical devices that are
   accessible from the door.  In it, antecedentRefs point to dmtfDoor
   objects and dependentRefs to dmtfLogicalDevice objects.

      ( <oid-oc158> NAME 'dmtfDoorAccessToDeviceAuxClass'
        DESC 'Doors provide access to LogicalDevices for hot swap,
           repair and similar activities. The entities accessed

Expires 3/31/00                                                [Page 80]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

           through a Door are shown in this relationship.'
        SUP dmtfDependencyAuxClass AUXILIARY
      )

3. DIT Content Rules

   The following DIT Content Rules apply to objects in this schema.
   These content rules referrence not only auxiliary classes in this
   draft but auxiliary classes from other DMTF CIM models [8, 9, 10, 11,
   12]

      ( <oid-oc54> NAME 'dmtfSystemResourceContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfSystemResource class'
        AUX (dmtfComputerSystemResourceAuxClass $
          dmtfAllocatedResourceAuxClass)
      )

      ( <oid-oc61> NAME 'dmtfRedundancyGroupContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfRedundancyGroup class'
        AUX (dmtfRedundancyComponentAuxClass)
      )

      ( <oid-oc66> NAME 'dmtfExtraCapacityGroupContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfExtraCapacityGroup class'
        AUX (dmtfNetworkAdapterRedundancyComponentAuxClass $
          dmtfNetworkVirtualAdapterAuxClass)
      )

      ( <oid-oc67> NAME 'dmtfLogicalPortContentRule'
        DESC 'shows what auxiliary classes may go with the
              dmtfLogicalPort class'
        AUX (dmtfPortOnDeviceAuxClass)
      )

      ( <oid-oc72> NAME 'dmtfSensorContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfSensor
           class'
        AUX (dmtfAssociatedSensorAuxClass)
      )

      ( <oid-oc75> NAME 'dmtfCoolingDeviceContentRule'
        DESC 'shows what auxiliary classes may go with the
              dmtfCoolingDevice class'
        AUX (dmtfAssociatedCoolingAuxClass $ dmtfPackageCoolingAuxClass)
      )

Expires 3/31/00                                                [Page 81]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-oc84> NAME 'dmtfDesktopMonitorContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfDesktopMonitor class'
        AUX (dmtfMonitorSettingAuxClass)
      )

      ( <oid-oc85> NAME 'dmtfMonitorResolutionContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfMonitorResolution class'
        AUX (dmtfMonitorSettingAuxClass)
      )

      ( <oid-oc89> NAME 'dmtfOOBAlertServiceContentRule'
         DESC 'shows what auxiliary classes may go with the
            dmtfOOBAlertService class'
         AUX (dmtfOOBAlertServiceOnModemAuxClass $
           dmtfOOBAlertServiceOnNetworkAdapterAuxClass)
      )

      ( <oid-oc90> NAME 'dmtfWakeUpServiceContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfWakeUpService class'
        AUX (dmtfWakeUpServiceOnModemAuxClass $
          dmtfWakeUpServiceOnNetworkAdapterAuxClass)
      )

      ( <oid-oc91> NAME 'dmtfModemContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfModem
           class'
        AUX (dmtfOOBAlertServiceOnModemAuxClass $
          dmtfWakeUpServiceOnModemAuxClass)
      )

      ( <oid-oc105> NAME 'dmtfBatteryContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfBattery
           class'
        AUX (dmtfAssociatedBatteryAuxClass)
      )

      ( <oid-oc106> NAME 'dmtfPowerSupplyContentRule'
        DESC 'shows what auxiliary classes may go with the
              dmtfPowerSupply class'
        AUX (dmtfSuppliesPowerAuxClass)
      )

      ( <oid-oc110> NAME 'dmtfNetworkAdapterContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfNetworkAdapter class'

Expires 3/31/00                                                [Page 82]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

        AUX (dmtfOOBAlertServiceOnNetworkAdapterAuxClass $
          dmtfWakeUpServiceOnNetworkAdapterAuxClass $
             dmtfNetworkAdapterRedundancyComponentAuxClass $
          dmtfNetworkVirtualAdapterAuxClass $
          dmtfAdapterActiveConnectionAuxClass)
      )

      ( <oid-oc115> NAME 'dmtfFibreChannelAdapterContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfFibreChannelAdapter class'
        AUX (dmtfFibrePortOnFCAdapterAuxClass)
      )

      ( <oid-oc116> NAME 'dmtfFibrePortContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfFibrePort
class'
        AUX (dmtfFibrePortOnFCAdapterAuxClass $
          dmtfFibrePortActiveLoginAuxClass)
      )

      ( <oid-oc122> NAME 'dmtfControllerContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfController
           class'
        AUX (dmtfControlledByAuxClass $ )
      )

      ( <oid-oc125> NAME 'dmtfSerialControllerContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfSerialController class'
           AUX (dmtfSerialInterfaceAuxClass)
      )

      ( <oid-oc127> NAME 'dmtfSCSIControllerContentRule'
         DESC 'shows what auxiliary classes may go with the
            dmtfSCSIController class'
         AUX (dmtfSCSIInterfaceAuxClass)
      )

      ( <oid-oc129> NAME 'dmtfVideoControllerContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfVideoController class'
        AUX (dmtfVideoSettingAuxClass)
      )

      ( <oid-oc133> NAME 'dmtfVideoControllerResolutionContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfVideoControllerResolution class'
        AUX (dmtfVideoSettingAuxClass)
      )

Expires 3/31/00                                                [Page 83]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

      ( <oid-oc154> NAME 'dmtfAlarmDeviceContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfAlarmDevice class'
        AUX (dmtfAssociatedAlarmAuxClass $ dmtfPackageAlarmAuxClass)
      )

      ( <oid-oc156> NAME 'dmtfDoorContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfDoor
           class'
        AUX (dmtfDoorAccessToPhysicalElementAuxClass)
      )

4. References

   Request For Comments (RFC) and Internet Draft documents are available
   from numerous mirror sites.

[1]         M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
            Protocol (v3)," RFC 2251, Decemeber 1997.

[2]         M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
            Directory Access Protocol (v3): Attribute Synatx Defini-
            tions," RFC 2252, December 1997.

[3]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Core CIM Model," Internet Draft (work in
            progress), June 1999.

[4]         Ryan Moats, Gerald Maziarski, John Strassner, "Extensible
            Match Rule to Dereference Pointers", Internet Draft (work in
            progress), June 1999.

[5]         ITU, Rec X.733

[6]         ISO, IEC 10164-4

[7]         DMTF, "CIM Device Model v2.2"

[8]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Network CIM Model", October 1999.

[9]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Core CIM Model", September 1999.

[10]        Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Application CIM Model", October 1999.

Expires 3/31/00                                                [Page 84]

INTERNET DRAFT  LDAP Schema for the DMTF Device CIM Model September 1999

[11]        Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF System CIM Model", October 1999.

[12]        Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Physical CIM Model", October 1999.

5. Author's Addresses

   Ryan Moats               Jerry Maziarski           John Strassner
   15621 Drexel Circle      Room C3-3Z01              Cisco Systems, Bldg 1
   Omaha, NE 68135          200 S. Laurel Ave.        170 West Tasman Drive
   USA                      Middletown, NJ 07748      San Jose, CA 95134
   E-mail: jayhawk@att.com  USA                       E-mail:
johns@cisco.com
                            E-mail: gfm@qsun.att.com

Expires 3/31/00                                                [Page 85]