
XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


--  Module: XCMI Extensions to IETF Host Resources TC
--  File:   10hosttc.txt, .dfm
--  Date:   19 July 2019 - Version 6.008.pub  VersionUpdate
--
--



                   Definitions of Textual Conventions
       for XCMI Extensions to IETF Host Resources MIB using SMIv2


Status of this Memo 

This document specifies the XCMI Extensions to IETF Host Resources (HRX)
Textual Conventions (TC).  All XCMI conforming management agents, which
implement the HRX MIB, SHALL implement the General and Device Info
groups in the XCMI HRX MIB.  

This document specifies an XCMI (Xerox Common Management Interface)
official standard MIB module for the entire Xerox community, and
requests discussion and suggestions for improvements.  Distribution of
this memo is unlimited (within Xerox).  

See the XCMI MIB Implementer's Guide (XMIG) for implementation guidance
for all of XCMI.  

See section 9 'Supplement' of the XCMI HRX TC for additional
implementation and conformance guidance for the IETF Host Resources MIB
(RFC 2790) and the XCMI Extensions to IETF Host Resources MIB (11hostx).


















XCMI Working Group  File 10hosttc               [Page 1]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



1.  Introduction

This document specifies the XCMI Extensions to IETF Host Resources (HRX)
Textual Conventions (TC).  All XCMI conforming management agents, which
implement the HRX MIB, SHALL implement the General and Device Info
groups in the XCMI HRX MIB.  

This HRX TC is a companion to the HRX MIB (published separately).  

This HRX TC has been written in ASN.1 (OSI Abstract Syntax Notation One
- CCITT X.208/209 | ISO 8824/8825), using the IETF SMI for SNMPv2
(Structure of Management Information - RFC 1442/1902/2578), the IETF TC
for SNMPv2 (Textual Conventions - RFC 1443/1903/2579), the IETF CONF for
SNMPv2 (Conformance Statements - RFC 1444/1904/2580), and the IETF Host
Resources MIB (RFC 2790) macros and textual conventions.  






































XCMI Working Group  File 10hosttc               [Page 2]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



2.  SNMP Network Management Framework

See section 2 'SNMP Network Management Framework' in the XCMI General TC
(06gentc).  


3.  Managed Object Usage



3.1.  Overview of Groups in the HRX MIB

Seventeen object groups are specified in the HRX MIB.  Diagrams of their
relationships appear below and on the following pages:  brief comment
(eg, 'Alerts') above each box; object group name (eg, 'Event') inside
each box; conformance level in parentheses ('(Mandatory)' or '(Cond
Mand)') inside each box.  An object group name in parentheses (eg,
'(Profile)') is a reference to a previously defined object group).  

Housekeeping                                            Housekeeping
|-----------|                                           |-----------|
|IETF HR MIB|                                           |(XCMI HRX) |
|  System   |                                       1-1 |  General  |
|(Mandatory)|...........................................|(Mandatory)|
|-----------|                                           |-----------|
      :
      :         System Storage                        System Storage Ext
      :         |-----------|                           |-----------|
      :         |IETF HR MIB|                           |(XCMI HRX) |
      :     1-n |  Storage  |                       1-1 |(Storage X)|
      :.........|(Mandatory)|...........................|(Cond Mand)|
      :         |-----------|                           |-----------|
      :
      :         System Device                         System Device Ext
      :         |-----------|                           |-----------|
      :         |IETF HR MIB|                           |(XCMI HRX) |
      :     1-n |  Device   |                       1-1 |(Dev Info) |
      :.........|(Mandatory)|...........................|(Mandatory)|
                |-----------|                           |-----------|

       Storage and Device Groups in IETF/XCMI Host Resources MIBs












XCMI Working Group  File 10hosttc               [Page 3]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

Housekeeping                                            Housekeeping
|-----------|                                           |-----------|
|IETF HR MIB|                                           |(XCMI HRX) |
|  System   |                                       1-1 |  General  |
|(Mandatory)|...........................................|(Mandatory)|
|-----------|                                           |-----------|
      :
      :        Software Running                     Software Running Ext
      :         |-----------|                           |-----------|
      :         |IETF HR MIB|                           |(XCMI HRX) |
      :     1-n |SW Running |                       1-1 (SW Run Ext)|
      :.........|(Cond Mand)|...........................|(Cond Mand)|
      :         |-----------|                           |-----------|
      :
      :  Software Running Performance
      :         |-----------|
      :         |IETF HR MIB|
      :     1-n |SW Run Perf|
      :.........|(Cond Mand)|
      :         |-----------|
      :
      :       Software Installed                  Software Installed Ext
      :         |-----------|                           |-----------|
      :         |IETF HR MIB|                           |(XCMI HRX) |
      :     1-n |SW Install |                       1-1 (SW Ins Ext)|
      :.........|(Cond Mand)|...........................|(Cond Mand)|
                |-----------|                           |-----------|

   Software Running/Installed Groups in IETF/XCMI Host Resources MIBs


























XCMI Working Group  File 10hosttc               [Page 4]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

Housekeeping                                            System Faults
|-----------|                                           |-----------|
|  General  |                                       1-n | Sys Fault |
|(Mandatory)|...........................................|(Cond Mand)|
|-----------|                                           |-----------|
      :
      :       System Storage Ext
      :         |-----------|
      :     1-n |Storage Ext|
      :.........|(Cond Mand)|
      :         |-----------|
      :               :
      :               :             System Storage Additional Groups
      :               :         |--------------------------------------|
      :               :     1-1 |            Storage Detail            |
      :               :.........|       (Conditionally Mandatory)      |
      :                         |--------------------------------------|
      :
      :       System Device Ext
      :         |-----------|
      :     1-n | Dev Info  |
      :.........|(Mandatory)|
      :         |-----------|
      :               :
      :               :             System Device Additional Groups
      :               :         |--------------------------------------|
      :               :1-1 Calendar/Cover/Detail/Help/Mgmt/Power/Traffic
      :               :.........|       (Conditionally Mandatory)      |
      :               :         |--------------------------------------|
      :               :
      :               :         Device Alerts
      :               :         |-----------|
      :               :     1-n | Dev Alert |
      :               :.........|(Cond Mand)|
      :               :         |-----------|
      :               :
      :               :         Console Screen           Console Tab
      :               :         |-----------|           |-----------|
      :               :     1-n |Cons Screen|       1-n |Console Tab|
      :               :.........|(Cond Mand)|...........|(Cond Mand)|
      :                         |-----------|           |-----------|
      :
      :      Software Running Ext
      :         |-----------|
      :     1-n |SW Run Ext |
      :.........|(Cond Mand)|
      :         |-----------|
      :
      :     Software Installed Ext
      :         |-----------|
      :     1-n |SW Ins Ext |
      :.........|(Cond Mand)|
                |-----------|


XCMI Working Group  File 10hosttc               [Page 5]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

Seventeen object groups are specified in the HRX MIB, as follows:  

1)  General Group (Mandatory) 
    - 'xcmHrGeneralTable' contains one entry for general information on
    the host resources subsystem on this host system 
    - the entry (always) supports a host resources subsystem version ID 
    and version date 
    - the entry (always) supports a terse conformance statement of ALL
    mandatory, conditionally mandatory, and optional IETF Host Resources
    MIB (RFC 2790) and XCMI HRX MIB object groups which are supported by
    a given management agent implementation 
    - the entry (always) supports 'highest entry index' values for all
    of the primary object tables in the IETF Host Resources MIB (RFC
    2790) and XCMI HRX MIB; 
    
2)  Device Info Group (Mandatory - extends basic Device Group) 
    - 'xcmHrDevInfoTable' contains entries for some 'physical' (real),
    'logical' (virtual), or 'logicalAndPhysical' devices resident on
    this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (always) supports a human-readable device 'name' 
    - each entry (always) supports a human-readable device serial number
    - each entry (always) supports device specific extended status,
    device independent conditions, and device specific extended
    conditions of a device on this host system 
    - each entry (always) supports device install date and device reset
    date of a device on this host system 
    - maps (optionally) ONTO the next associated Device Group entry in
    the 'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - maps (optionally) ONTO the previous associated Device Group entry
    in the 'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - maps (optionally) ONTO the associated 'physical' Device Group
    entry in the 'hrDeviceTable' of the IETF Host Resources MIB (RFC
    2790) 
    - each entry (always) supports device priority of a device on this
    host system.  
    
3)  Device Help Group (Deprecated - help for end users) 
    - PLEASE use Device Detail group instead (as of XCMI v4.1), by
    specifying 'deviceHelp...' details 
    - 'xcmHrDevHelpTable' contains entries for some 'physical' (real),
    'logical' (virtual), or 'logicalAndPhysical' devices resident on
    this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (optionally) supports a human-readable device 'operator
    message' (from the system operator) 
    - each entry (optionally) supports a human-readable device 'problem 
    message' (from the system software or system operator) 
    - each entry (optionally) supports contact info (phone, fax, etc)
    for system administrator, system operator, service, and/or supplies
    persons or organizations; 


XCMI Working Group  File 10hosttc               [Page 6]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    
4)  Device Mgmt Group (Conditionally Mandatory - simple device mgmt) 
    - 'xcmHrDevMgmtTable' contains entries for some 'physical' (real),
    'logical' (virtual), or 'logicalAndPhysical' devices resident on
    this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (always) supports command request, response, and status
    objects for simple device management; 
    
5)  Device Power Group (Conditionally Mandatory - power mgmt cycles) 
    - 'xcmHrDevPowerTable' contains entries for some 'physical' (real), 
    'logical' (virtual), or 'logicalAndPhysical' devices resident on
    this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (always) supports 'warm up', 'cool down', 'energy
    save', and 'wake up' power management cycles; 
    
6)  Device Traffic Group (Conditionally Mandatory - traffic statistics) 
    - 'xcmHrDevTrafficTable' contains entries for some 'physical'
    (real), 'logical' (virtual), or 'logicalAndPhysical' devices
    resident on this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (always) supports input and output traffic counters 
    - each entry (always) supports input and output traffic timeouts; 
    
7)  System Fault Group (Conditionally Mandatory - system fault log) 
    - 'xcmHrSystemFaultTable' contains entries for a (product specific) 
    number of most 'recent' system faults on this host system (which are
    'aged' out of 'xcmHrSystemFaultTable' by an algorithm outside the
    scope of XCMI specifications) 
    - each entry (always) supports a system fault type code (numeric)
    and a system fault type string (alpha) 
    - each entry (optionally) supports a system fault object reference 
    - each entry (optionally) supports a system fault device index; 
    
8)  Device Calendar Group (Conditionally Mandatory) 
    - 'xcmHrDevCalendarTable' contains entries for a calendar of device
    management commands to be automatically initiated for devices
    configured on this host system 
    - each entry (always) supports the 'day of week' and 'time of day'
    for automatic initiation of the specified device management command 
    - each entry (optionally) supports the 'explicit date' for
    'one-shot' automatic initiation of the specified device management
    command 
    - each entry (always) supports the 'command request' and 'command
    data' for automatic initiation of the specified device management
    command; 
    
9)  Software Running Ext Group (Conditionally Mandatory) 
    - 'xcmHrSWRunTable' contains entries for software management
    extensions for software running on this host system 

XCMI Working Group  File 10hosttc               [Page 7]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    - each entry (always) supports the 'administrative name' of this
    software running component on this host system 
    - each entry (optionally) supports the 'extended status' of this
    software running component on this host system 
    - each entry (always) supports the 'row create date' of the entry
    for this software running component on this host system 
    - maps (optionally) ONTO the first 'physical device' associated with
    this software running component (eg, ISO DPA 'server') on this host
    system 
    - maps (optionally) ONTO the first 'logical device' associated with 
    this software running component (eg, ISO DPA 'server') on this host
    system 
    - maps (optionally) ONTO the next Software Running Group entry in
    the 'hrSWRunTable' of the Host Resources MIB (RFC 2790) in a set on
    this host system 
    - maps (optionally) ONTO the previous Software Running Group entry
    in the 'hrSWRunTable' of the Host Resources MIB (RFC 2790) in a set 
    on this host system; 
    
10) Software Installed Ext Group (Conditionally Mandatory) 
    - 'xcmHrSWInstalledTable' contains entries for software management
    extensions for software installed on this host system.  
    - each entry (optionally) supports the 'extended status' of this
    software installed component on this host system 
    - each entry (always) supports the 'row create date' of the entry
    for this software installed component on this host system 
    - maps (optionally) ONTO the first 'physical device' associated with
    this software installed component (eg, ISO DPA 'server') on this
    host system 
    - maps (optionally) ONTO the first 'logical device' associated with 
    this software installed component (eg, ISO DPA 'server') on this
    host system 
    - maps (optionally) ONTO the next Software Installed Group entry in 
    the 'hrSWInstalledTable' of the Host Resources MIB (RFC 2790) in a
    set on this host system 
    - maps (optionally) ONTO the previous Software Installed Group entry
    in the 'hrSWInstalledTable' of the Host Resources MIB (RFC 2790) in
    a set on this host system; 
    
11) Device Detail Group (Conditionally Mandatory) 
    - 'xcmHrDevDetailTable' contains entries for device details for
    devices installed on this host system 
    - each entry (always) supports the type, index, and row status of
    this device detail on this host system 
    - each entry (always) supports the unit class and unit of this
    device detail on this host system 
    - each entry (always) supports the value integer, OID, and/or string
    of this device detail on this host system; 
    
12) Storage Ext Group (Conditionally Mandatory) 
    - 'xcmHrStorageTable' contains entries for device details for
    devices installed on this host system 
    - each entry (always) supports the row status, realization, and
    status of this storage on this host system 

XCMI Working Group  File 10hosttc               [Page 8]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    - each entry (optionally) supports the product, platform, paging
    (swap), and matching (equivalent) device indices of this storage on
    this host system 
    - each entry (optionally) supports the associated software running
    and software installed indices of this storage on this host system 
    - each entry (optionally) supports the next, previous, and
    (underlying) physical storage entry indices of this storage on this
    host system; 
    
13) Storage Detail Group (Conditionally Mandatory) 
    - 'xcmHrStorageDetailTable' contains entries for storage details for
    storage installed on this host system 
    - each entry (always) supports the type, index, and row status of
    this storage detail on this host system 
    - each entry (always) supports the unit, value syntax, value
    integer, value OID, and value string of this storage detail on this
    host system; 
    
14) Device Cover Group (Conditionally Mandatory - covers/interlocks) 
    - 'xcmHrDevCoverTable' contains entries for some 'physical' (real), 
    devices resident on this host system 
    - maps (sparsely) one-to-one ONTO Device Table entries in the
    'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790) 
    - each entry (always) supports type (cover or interlock),
    description, and status (open/closed) for a specific cover or
    interlock; 
    
15) Device Alert Group (Conditionally Mandatory) 
    - 'xcmHrDevAlertTable' contains entries for device alerts for
    devices installed on this host system 
    - each entry (always) supports the index and row status of this
    device alert on this host system 
    - each entry (always) supports the severity level and training level
    of this device alert on this host system 
    - each entry (always) supports the value integer and/or value string
    of this device alert on this host system 
    - each entry (always) supports the description, reference OID, and
    timestamp of this device alert on this host system; 
    
16) Console Screen Group (Conditionally Mandatory) 
    - 'xcmHrConsoleScreenTable' contains entries for console screens for
    local console devices installed on this host system 
    - each entry (always) supports the index, name, and description of
    this console screen on this host system 
    - each entry (always) supports the index of the parent screen of
    this console screen on this host system 
    - each entry (always) supports the display priority and tab count of
    this console screen on this host system; 
    
17) Console Tab Group (Conditionally Mandatory) 
    - 'xcmHrConsoleTabTable' contains entries for console tabs for local
    console devices installed on this host system 
    - each entry (always) supports the index, name, and description of
    this console tab on this host system 

XCMI Working Group  File 10hosttc               [Page 9]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    - each entry (always) supports the index of new screen selected by
    this console tab on this host system 
    - each entry (always) supports the display priority of this console
    tab on this host system.  



















































XCMI Working Group  File 10hosttc               [Page 10]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.2.  Relationship to other MIBs



3.2.1.  IETF Host Resources MIB (RFC 2790)

The Device Info, Device Mgmt, Device Power, and Device Traffic Groups of
the HRX MIB map 'sparsely' ONTO associated conceptual rows in the
'hrDeviceTable' (Device Group) of the IETF Host Resources MIB (RFC
2790), for added device management functionality.  

The Software Running Ext Group of the HRX MIB maps 'sparsely' ONTO
associated conceptual rows in the 'hrSWRunTable' (Software Running
Group) of the IETF Host Resources MIB (RFC 2790), for added software
management functionality.  

The Software Installed Ext Group of the HRX MIB maps 'sparsely' ONTO
associated conceptual rows in the 'hrSWInstalledTable' (Software
Installed Group) of the IETF Host Resources MIB (RFC 2790), for added
software management functionality.  


3.2.2.  IETF Interfaces Group MIB (RFC 2863)

The entire HRX MIB was inspired by the IETF Interfaces Group MIB (RFC
2863).  


3.2.3.  Printer MIB (RFC 1759 or successor)

The Device Info Group of the HRX MIB supports 'physical' (real),
'logical' (virtual), and 'logicalAndPhysical' device 'realizations' via 
the 'xcmHrDevInfoRealization' object - an extension of the 'printer
realization' concept in ISO DPA (Document Printing Application), ISO/IEC
10175).  Support for 'logical' printer realizations may be useful in
combination with the Printer MIB (RFC 1759 or successor).  


3.2.4.  XCMI Standard MIBs

The XCMI General, Resources (fonts, forms, and logos), Job Monitoring,
Comms Config, Comms Engine, and Scanner MIBs ALL benefit from the
enhanced device management features offered by the HRX MIB.  


3.2.5.  XCMI Job Monitoring MIB

The XCMI Job Monitoring MIB defines a Job General Basic group for
monitoring the (zero or more) user jobs associated with a given
'service' via a 'logical' or 'physical' device entry in the HRX MIB (and
its underlying entry in the IETF HR MIB, RFC 2790).  


XCMI Working Group  File 10hosttc               [Page 11]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.2.6.  XCMI Simple Job Management MIB

The XCMI Simple Job Management MIB defines a Job Management group for
managing the (zero or more) user jobs associated with a given 'service'
via a 'logical' or 'physical' device entry in the HRX MIB (and its
underlying entry in the IETF HR MIB, RFC 2790).  


3.2.7.  XCMI Service Monitoring MIB

The XCMI Service Monitoring MIB defines an Associated Queue group for
configuring/monitoring the (zero or more) named job queues associated
with a given 'logical' or 'physical' device entry in the HRX MIB (and
its underlying entry in the IETF HR MIB, RFC 2790).  


3.2.8.  XCMI System Admin MIB

The XCMI System Admin MIB defines the detailed semantics of a set of
'Device' level operations for 'secure system administration'.  These
operations are specified in terms of the objects which are defined in
the HRX MIB.  































XCMI Working Group  File 10hosttc               [Page 12]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.3.  Definition of Device FSM

The following two sections specify the Device Finite State Machine (FSM)
via a state diagram and a state table.  


3.3.1.  Device FSM State Diagram

The diagram on the following page shows all valid FSM states and state
transitions for a 'physical', 'logical', or 'logicalAndPhysical' device 
as defined by 'xcmHrDevInfoRealization' in the Device Info Group of the 
HRX MIB (which augments 'hrDeviceType' in the basic Device Group of the 
IETF Host Resources MIB, RFC 2790).  

The device states are all defined by the 'XcmHrDevInfoStatus' textual
convention in the Device Info Group, directly from the basic Device
Group - no new device states are introduced here.  The device managment 
commands and basic conditions (one per command) are all defined by the
'XcmHrDevMgmtCommandRequest' and 'XcmHrDevInfoConditions' textual
conventions in the Device Mgmt and Device Info Groups.  

Device management commands are shown lowercase with single quotes (eg,
'startup').  Device internal events are shown capitalized without quotes
(eg, WarningEvent).  Device states are shown lowercase without quotes,
but with their state ordinal (eg, running(2)).  

See comments on hrDeviceStatus in the XCMI MIB Implementer's Guide.  


























XCMI Working Group  File 10hosttc               [Page 13]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


The 'xcmHrDevMgmtCommandRequest' management commands (from the Host
Resources Extensions MIB) in this FSM diagram have the following
meanings:  

Command             Description
------------------  ----------------------------------------------------
none(1)             no operation
startup(2)          startup to 'running' (normally via 'testing')
resetWarning(3)     reset from 'warning' to 'running' (clear alert)
test(4)             goto 'testing' immediately or continue 'testing'
shutdown(5)         shutdown to 'down' (immediately)
quiesce(6)          quiesce to 'down' (with 'graceful shutdown')
resetCounters(7)    reset all device counters (remain in current state)
resetWarm(8)        warm restart with current defaults to 'running'
resetCold(9)        cold restart with current defaults to 'running'
resetFactory(10)    cold restart with factory defaults to 'running'
flushInput(11)      flush all input buffers and traffic in progress
flushOutput(12)     flush all output buffers and traffic in progress
flushInOut(13)      flush all input and output buffers and traffic
manage(14)          manage command, any state (product specific)
refresh(15)         refresh device configuration w/out reset
warmUp(16)          power to 'ready' mode from 'standby' mode
coolDown(17)        power to 'standby' mode from 'ready' mode
energySave(18)      power to 'sleep' mode from 'standby' mode
wakeUp(19)          power to 'standby' mode from 'sleep' mode
powerToReady(20)    power to 'ready' mode from 'standby|sleep' mode
powerToStandby(21)  power to 'standby' mode from 'ready|sleep' mode
powerToSleep(22)    power to 'sleep' mode from 'ready|standby' mode


























XCMI Working Group  File 10hosttc               [Page 14]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


Note_1:  The 'xcmHrDevInfoConditions' basic conditions (from the Device 
Info Group of the HRX MIB) are all of the form '...InProgress'.  The
presence of 'testInProgress' indicates that a test is currently active; 
while the absence of 'testInProgess', while 'hrDeviceStatus' is still
'testing(4)', indicates that the device is 'idle' and ready to process
another 'test' command or TestEvent.  

Note_2:  The device management command 'startup' should normally result 
in the following sequence of device states:  
'down(5)' --> 'testing(4)' --> 'running(2)' 
Implementors should set 'xcmHrDevInfoConditions' to 'startupInProgress',
until finally transitioning to 'running(2)'.  

Note_3:  The device management command 'shutdown' should normally result
in an immediate transition to 'down(4)', from any previous device state:
'any(N)' --> 'down(4)' 
The device management command 'quiesce' MAY be supported, with 'graceful
shutdown' of current work-in-progress for the device, before finally
transitioning to 'down(4)':  
'running(2)' ...graceful shutdown...  --> 'down(4)' 
The device states defined by the IETF Host Resources MIB (RFC 2790) do
NOT permit this distinction of behavior to be made visible, but the
footprint of the last device command (ie, 'shutdown' or 'quiesce') in
'xcmHrDevMgmtCommandRequest' provides some clarification.  Implementors 
who support 'quiesce' should remain in the device state 'running(2)' and
set 'xcmHrDevInfoConditions' equal to 'quiesceInProgress', until finally
transitioning to the device state 'down(4)'.  

Note_4:  The device management commands 'resetWarm', 'resetCold', and
'resetFactory' should normally result in the following sequence of
device states:  
'down(5)' --> 'testing(4)' --> 'running(2)' 
The device management command 'resetCold' shall yield the same result as
a 'power cycle reset', using the operational variables values in the
device's 'current defaults', while 'resetFactory' shall yield a 'factory
defaults reset' for all operational variables of the device (overwriting
the previous 'current defaults') and shall then be treated the same as a
'resetCold'.  The device management command 'resetWarm' shall yield a
'current defaults reset' (a software-only warm reset is permitted).  An
implementor MAY choose to treat a 'resetWarm', received while in the
'running(2)' state, as requesting a 'warm restart in place' and simply
remain in 'running(2)', with all operational variables reset to 'current
defaults' (which may differ from 'factory defaults') and all device
traffic counters reset to zero.  Implementors should ALWAYS set
'xcmHrDevInfoConditions' equal to 'reset...InProgress', until finally
transitioning to 'running(2)'.  

Note_5:  For reasons of brevity, 'quiesce' (as distinct from
'shutdown'), 'resetCounters' (zero all counters), 'resetWarm' (warm
start with current defaults), 'resetCold' (cold start with current
defaults), 'resetFactory' (cold start with factory defaults),
'flushInput', 'flushOutput', 'flushInOut', and 'manage' are not shown in
this FSM diagram.  

XCMI Working Group  File 10hosttc               [Page 15]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


          'startup'  *----------*  'shutdown'
     *<------------< |unknown(1)| >------------>*
     |               *----------*               |
     |                                          |
     |                                          |
     |                                          |
     |    'startup'  *----------*  'shutdown'   |
     *<------------< | down(5)  | <------------<*     'quiesce'
     |               *----------* <------------ | -------------<*
     |                    |                     |               |
     |          TestEvent | 'test'              |               |
     |                   \|/                    |               |
     |    'startup'  *----------*  'shutdown'   |               |
     *<------------< |testing(4)| >------------>*               |
     |               *----------*               |               |
     |                   /|\                    |               |
     |          TestEvent | 'test'              |               |
     |                    |                     |               |
     |    'startup'  *----------*  'shutdown'   |               |
     *>------------> |running(2)| >------------>*     'quiesce' |
     |               *----------* >------------ | ------------->*
     |                  |   /|\                 |               |
     |     WarningEvent |    | 'resetWarning'   |               |
     |                 \|/   |                  |               |
     |    'startup'  *----------*  'shutdown'   |               |
     *<------------< |warning(3)| >------------>*     'quiesce' |
                     *----------* >---------------------------->*

                        Device FSM State Diagram

























XCMI Working Group  File 10hosttc               [Page 16]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.3.2.  Device FSM State Table

TO BE SUPPLIED 


3.3.3.  Device Power Mode Diagram

The diagram on the following page shows all valid device power mode
transitions for a device which supports power management operations.  

The device power modes are all defined in the 'XcmHrDevInfoConditions'
textual convention and reported via the 'xcmHrDevInfoConditions' object 
in the Device Info group (essentially as 'sub-states' of the base device
state defined in the 'XcmHrDevInfoStatus' textual convention and
reported via the 'hrDeviceStatus' object in the Device group of the IETF
Host Resources MIB, RFC 2790).  

The (optional) device power management commands are all defined in the
'XcmHrDevMgmtCommandRequest' textual convention and invoked via the
'xcmHrDevMgmtCommandRequest' object in the Device Mgmt group.  

Device power management commands are shown lowercase with single quotes 
(eg, 'warmUp').  Device power modes are shown lowercase without quotes
(eg, readyMode).  

Note_1:  For reasons of brevity, 'powerToReady' (from 'sleep' or
'standby' to 'ready'), 'powerToStandby' (from 'ready' or 'sleep' to
'standby'), 'powerToSleep' (from 'ready' or 'standby' to 'sleep'), and
'resetWarm' (from 'ready' to 'ready', with software reset only) are not
shown in this power mode diagram.  

Note_2:  The 'powerTo[Ready|Standby|Sleep' power management commands are
defined for use in 'xcmHrDevCalendarCommandRequest' in the Device
Calendar group (a chronological list of automatic device management
commands), in order to avoid ambiguity of the CURRENT power mode of a
device known to be 'on' (ie, NOT 'down' in 'hrDeviceStatus'), but which 
MAY be currently in 'readyMode', 'standbyMode', or 'sleepMode' (since
the automatic device management commands are single-shot and NOT able to
inquire the current power mode in 'xcmHrDevInfoConditions').  














XCMI Working Group  File 10hosttc               [Page 17]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


    'startup'                 'shutdown'
    'resetCold'               'quiesce'
    'resetFactory'
*<------------< *-----------* <------------<*   'hrDeviceStatus'
|               |  offMode  |               |   = down(5)'
|               *-----------*               |
|                                           |
|                                           |
------------------------------------------------------------------------
|                                           |
|                                           |
| *<----------< *-----------* <----------<* |   'hrDeviceStatus'
| | 'wakeUp'    | sleepMode | 'energySave'| |   = running(2)
| |             *-----------*             | |   | warning(3)
| |                                       | |   | testing(4)
| |                                       | |
| |                                       | |
| |                                       | |
| | 'wakeUp'                  'energySave'| |
| *>----------> *-----------* >---------->* |   'hrDeviceStatus'
|               |standbyMode|               |   = running(2)
| *<----------< *-----------* <----------<* |   | warning(3)
| | 'warmUp'                  'coolDown'  | |   | testing(4)
| |                                       | |
| |                                       | |
| |                                       | |
| |                                       | |
| | 'warmUp'                  'coolDown'  | |
| *>----------> *-----------* >---------->* |   'hrDeviceStatus'
|               | readyMode |               |   = running(2)
*>------------> *-----------* >---------->* |   | warning(3)
    'startup'                 'shutdown'        | testing(4)
    'resetCold'               'quiesce'
    'resetFactory'

                       Device Power Mode Diagram


















XCMI Working Group  File 10hosttc               [Page 18]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.4.  XCMI Standard Tagged Management Data

XCMI device management commands are passed as enumerated types in
'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB.  Other XCMI management
commands are passed as enumerated types in 'xcmCommsMgmtCommandRequest',
'xcmSimpleJobMgmtOperation', etc, in the XCMI Comms Engine, Simple Job
Mgmt, and other MIBs.  

XCMI management commands MAY also require one or more arguments (in
addition to any specific variable bindings of MIB objects).  Required
arguments are passed as 'tagged string arguments' in
'xcmHrDevMgmtCommandData', 'xcmSimpleJobMgmtData', etc.  

The 'XcmHrDevMgmtCommandDataTag' textual convention in the XCMI HRX TC
defines XCMI standard 'tags' for all 'tagged string arguments'.  

Note_1:  The inclusion of a date and time stamp (using a 'DT' tag), for 
protection against 'replay' and as an extra term in the 'over-the-wire' 
protection function applied to user/account password, is STRONGLY
recommended.  

Note_2:  The inclusion of noise info (using an 'NI' tag), as an extra
term in the 'over-the-wire' protection function applied to user/account 
password, is STRONGLY recommended.  

IETF MIB-II (RFC 1213) and IETF HR MIB (RFC 2790) define a number of
'read-only' host system objects.  An XCMI standard mechanism to support 
creation and modification of these 'read-only' objects, is defined in
detail in section 3.5 'Simple Device Management Requests' of XCMI HRX TC
(please compare with the full-function POSIX Device Management described
in section 3.3 'System Admin Requests' of the XCMI System Admin TC).  

A preconfigured conceptual row ('hrDeviceType' of 'hrDeviceProcessor')
in the 'hrDeviceTable' of the IETF HR MIB and the 'xcmHrDevMgmtTable' of
the XCMI HRX MIB for the 'responsible platform CPU' (ie, location of
execution of management software for the managed host system resources) 
is used to solve the 'bootstrap problem' (ie, how to create a new device
on a managed host system).  

XCMI conforming management agents supporting 'Simple Device Management' 
shall ALWAYS preconfigure their 'main CPU' in the 'hrDeviceTable' and
the 'xcmHrDevMgmtTable'.  

To create conceptual rows in tables of the IETF MIB-II or IETF HR MIB,
XCMI conforming management stations may send device management requests 
'entityCreate' or 'entityInstall' in 'xcmHrDevMgmtCommandRequest' of the
conceptual row for the relevant 'responsible platform CPU'.  

To create conceptual rows ONLY in 'hrDeviceTable' of the IETF HR MIB,
XCMI conforming management stations may send device management requests 
'deviceCreate' or 'deviceInstall' in 'xcmHrDevMgmtCommandRequest' of the
conceptual row for the relevant 'responsible platform CPU'.  

XCMI Working Group  File 10hosttc               [Page 19]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


To modify conceptual rows in tables of the IETF MIB-II or IETF HR MIB,
XCMI conforming management stations may send device management request
'entitySet' in 'xcmHrDevMgmtCommandRequest' of the conceptual row for
the relevant 'responsible platform CPU'.  

To modify conceptual rows ONLY in 'hrDeviceTable' of the IETF HR MIB,
XCMI conforming management stations may send device management request
'deviceSet' in 'xcmHrDevMgmtCommandRequest' of the conceptual row for
the relevant 'responsible platform CPU'.  


3.4.1.  List Directory (LIST) Requests

An ambiguity has been recognized for the List Directory Tree (LIST) and
List Specific Directory (LDIR) requests, with the advent of flash
memories with visible file systems.  

Best Current Practice:  The XCMI Editors now recommend that the storage 
medium itself in the 'hrDeviceTable' be the target of 'LIST' requests.  
However, for compatibility with existing implementations, conforming
management stations (clients) should be ready to use 'hrDevicePrinter'
to read the directory of the primary hard disk 'hrDeviceDiskStorage'.  
































XCMI Working Group  File 10hosttc               [Page 20]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.5.  Simple Device Management Requests

IETF MIB-II (RFC 1213) and IETF HR MIB (RFC 2790) define a number of
'read-only' host system objects.  An XCMI standard mechanism to support 
creation and modification of these 'read-only' objects, is defined in
this section and the immediate following sections (please compare with
the full-function POSIX Device Management described in section 3.3
'System Admin Requests' of the XCMI System Admin TC).  

See section 3.3 'System Admin Requests', section 3.3.5.1 'Example of
Device Queue List Request', and section 3.3.5.2 'Example of Device Clean
Request' of the XCMI System Admin TC (60systc) for details of 'complex
device management requests'.  

See section 3.4 'Secure Modes of Operation', and section 3.5.3 'Secure
Simple Device Mgmt Requests' of the XCMI Security TC (62sectc) for
details of 'secure device management requests'.  




































XCMI Working Group  File 10hosttc               [Page 21]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.5.1.  Format and Protocol of Device Management Requests

A 'simple device management request' is conceptually 'executed' against 
a host system device (specified via 'hrDeviceIndex' in the IETF HR MIB).


* 'simple device management request' - an XCMI conforming management
station may use the XCMI HRX MIB to send a single SNMP Set-Request PDU
containing:  

1)  Request (Mandatory) 
    A device management request (eg, 'deviceSet') in
    'xcmHrDevMgmtCommandRequest', which augments 'hrDeviceTable' in the
    IETF HR MIB (RFC 2790); 
    
2)  Arguments (Optional) 
    Any (optional) 'tagged string arguments' in
    'xcmHrDevMgmtCommandData'; 
    
3a) Security (Optional) 
    If the security mode of the managed system is 'direct
    authentication', explicit authentication info in
    'xcmHrDevMgmtCommandData' (XCMI conforming management agents WITHOUT
    the XCMI Security MIB) or explicit authentication info in
    'xcmSec[Config|Account|User]MgmtData' (XCMI conforming management
    agents WITH the XCMI Security MIB); or 
    
3b) Security (Optional) 
    If the security mode of the managed system is 'source
    authentication', implicit authentication info in the SNMP
    Set-Request PDU source transport address; or 
    
3c) Security (Optional) 
    If the security mode of the managed system is 'session
    authentication', implicit authentication info in
    'xcmSecToken[Index|RowStatus]' in the XCMI Security MIB; and 
    
4)  Bindings (Optional) 
    Any additional SNMP variable bindings required for the request.  














XCMI Working Group  File 10hosttc               [Page 22]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


* 'simple device management response' - an XCMI conforming management
agent which receives a 'simple device management request' shall ALWAYS
perform the following actions:  

1)  Parsing (Mandatory) 
    Save the request parsing result (SNMP Set-Response 'error-status')
    in 'xcmHrDevMgmtCommandStatus'; 
    
2)  Response (Mandatory) 
    Send a single SNMP Set-Response PDU containing an 'error-status'
    indicating acceptance or rejection of the 'device management
    request' (if rejection, then skip following steps); 
    
3)  Processing (Mandatory) 
    Set 'xcmHrDevMgmtCommandInProgress' to 'true' and then process; 
    
    <...processing...> 
    
4)  Processing Result (Mandatory) 
    Save the request processing result in 'xcmHrDevMgmtCommandStatus'; 
    
5)  Processing Complete (Mandatory) 
    Set 'xcmHrDevMgmtCommandInProgress' to 'false'; and 
    
6)  Notification (Optional) 
    Generate an 'xcmHrDevMmgtV2Event' trap which includes the
    'xcmHrDevMgmtCommandStatus' final result of the operation.  


Conformance:  

1)  A 'simple device management request' shall ALWAYS be written to
    'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB of the 'responsible
    platform CPU' (of type 'hrDeviceProcessor') or to the immediate
    target device (Device group operations ONLY); 
    
2)  A 'simple device management request' shall ALWAYS pass 'tagged
    string arguments' in 'xcmHrDevMgmtCommandData' in a fixed locale
    specified by 'xcmGenFixedLocalizationIndex' in the XCMI General MIB
    (indexed by 'hrDeviceIndex' for the referenced device).  














XCMI Working Group  File 10hosttc               [Page 23]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.5.2.  Example of Interface Create Request

Interface entries are created, in the 'ifTable' of the IETF MIB-II,
using 'entityCreate' in 'xcmHrDevMgmtCommandRequest' in the Device Mgmt
group of the XCMI HRX MIB.  These requests are sent to the 'responsible
platform CPU' device (of type 'hrDeviceProcessor').  


Given a fixed locale specification:  

--  IETF HR MIB (RFC 2790) objects
hrDeviceType.2                          = 'hrDeviceProcessor'
    --  indexed by 'hrDeviceIndex'
    --  host system 'main CPU' (ie, 'responsible platform CPU')

--  XCMI General MIB (07gen) objects
xcmGenFixedLocalizationIndex.2          = '1'
    --  indexed by 'hrDeviceIndex'
    --  fixed (install-time) locale for 'responsible platform CPU'
xcmGenLocalizationLanguage.2.1          = 'en'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  English (from ISO 639:1988 'Codes for Names of Languages')
xcmGenLocalizationCountry.2.1           = 'us'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  USA (from ISO 3166:1993 'Codes for Names of Countries')
xcmGenLocalizationCharacterSet.2.1      = '3' -- US-ASCII
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  ANSI_X3.4-1968 or ISO_646.irv:1991 (Int'l Reference Version)
    --  (using 'MIBenum' from IANA Character Sets registry, found at
    --  'ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets')


A 'simple device management request' to create a new conceptual row in
the 'ifTable' of IETF MIB-II may be specified as follows:  

--  XCMI HRX MIB (11hostx) objects
xcmHrDevMgmtCommandRequest.2            = 'entityCreate(1901)'
    --  device management request to create a new host system interface
xcmHrDevMgmtCommandData.2   = 'IX=9:'
                            + 'ID=IBM Token Ring Adapter Z1600 v1.2'
                            + ' - Network - 16Mbps - AN299Z102:'
                            + 'IY=iso88025TokenRing:'
                            + 'IM=4096:'
                            + 'IS=16777216:'
    --  device management request 'tagged string arguments'
    --  [IX] Set 'ifIndex' to '9' (new interface conceptual row)
    --  [ID] Set 'ifDescr' to 'IBM Token Ring...'
    --  [IY] Set 'ifType' to 'iso88025TokenRing(9)' (IEEE 802.5)
    --  [IM] Set 'ifMtu' to '4096' (too large for Ethernet packets)
    --  [IS] Set 'ifSpeed' to '16777216' (16M bits/second)
    --  [IP] Omitted - get physical address from network adapter
    --  [IZ] Omitted - no TokenRing MIB (RFC 1748) on this host system

XCMI Working Group  File 10hosttc               [Page 24]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



Conformance:  

1)  An 'entityCreate' request (for an Interface) shall ALWAYS be written
    to 'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB of the
    'responsible platform CPU' (of type 'hrDeviceProcessor'); 
    
2)  An 'entityCreate' request (for an Interface) shall ALWAYS include
    the desired value of 'ifIndex' for the NEW conceptual row to be
    created in the 'ifTable' of the IETF MIB-II, specified as a 'tagged
    string argument' using the standard 'IX' tag or the generic 'OI/OV'
    tags (see 'XcmHrDevMgmtCommandDataTag' textual convention).  










































XCMI Working Group  File 10hosttc               [Page 25]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.5.3.  Example of Device Create Request

Device entries are created, in the 'hrDeviceTable' of the IETF HR MIB,
using 'deviceCreate' or 'deviceInstall' in 'xcmHrDevMgmtCommandRequest'
in the Device Mgmt group of the XCMI HRX MIB.  These requests are sent
to the 'responsible platform CPU' device (of type 'hrDeviceProcessor').


Given a fixed locale specification:  

--  IETF HR MIB (RFC 2790) objects
hrDeviceType.2                          = 'hrDeviceProcessor'
    --  indexed by 'hrDeviceIndex'
    --  host system 'main CPU' (ie, 'responsible platform CPU')

--  XCMI General MIB (07gen) objects
xcmGenFixedLocalizationIndex.2          = '1'
    --  indexed by 'hrDeviceIndex'
    --  fixed (install-time) locale for 'responsible platform CPU'
xcmGenLocalizationLanguage.2.1          = 'en'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  English (from ISO 639:1988 'Codes for Names of Languages')
xcmGenLocalizationCountry.2.1           = 'us'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  USA (from ISO 3166:1993 'Codes for Names of Countries')
xcmGenLocalizationCharacterSet.2.1      = '3' -- US-ASCII
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  ANSI_X3.4-1968 or ISO_646.irv:1991 (Int'l Reference Version)
    --  (using 'MIBenum' from IANA Character Sets registry, found at
    --  'ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets')


A 'simple device management request' to create a new conceptual row in
the 'hrDeviceTable' of IETF HR MIB may be specified as follows:  

--  XCMI HRX MIB (11hostx) objects
xcmHrDevMgmtCommandRequest.2            = 'deviceCreate(1301)'
    --  device management request to create a new host system device
xcmHrDevMgmtCommandData.2   = 'DX=13:'
                            + 'DY=hrDevicePrinter:'
                            + 'DD=Xerox DocuCentre 230 ST v1.0 Printer:'
                            + 'DI=xcmPidDC230STV1:'
    --  device management request 'tagged string arguments'
    --  [DX] Set 'hrDeviceIndex' to '13' (new device conceptual row)
    --  [DY] Set 'hrDeviceType' to 'hrDevicePrinter'
    --  [DD] Set 'hrDeviceDescr' to
    --  'Xerox DocuCentre 230 ST v1.0 Printer'
    --  [DI] Set 'hrDeviceID' to 'xcmPidDC230STV1' (product ID)


Note:  Using generic object identifier and object value 'tags' (see
'XcmHrDevMgmtCommandDataTag' textual convention), the 'simple device

XCMI Working Group  File 10hosttc               [Page 26]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

management request' above may be rewritten as follows (functionally
equivalent but longer):  

--  XCMI HRX MIB (11hostx) objects
xcmHrDevMgmtCommandRequest.2            = 'deviceCreate(1301)'
    --  device management request to create a new host system device
xcmHrDevMgmtCommandData.2   = 'OI=hrDeviceIndex:'
                            + 'OV=13:'
                            + 'OI=hrDeviceType:'
                            + 'OV=hrDevicePrinter:'
                            + 'OI=hrDeviceDescr:'
                            + 'OV=Xerox DocuCentre 230 ST v1.0 Printer:'
                            + 'OI=hrDeviceID:'
                            + 'OV=xcmPidDC230STV1:'
    --  device management request 'tagged string arguments'


Conformance:  

1)  A 'deviceCreate' or 'deviceInstall' request shall ALWAYS be written
    to 'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB of the
    'responsible platform CPU' (of type 'hrDeviceProcessor'); 
    
2)  A 'deviceCreate' or 'deviceInstall' request shall ALWAYS include the
    desired value of 'hrDeviceIndex' for the NEW conceptual row to be
    created in the 'hrDeviceTable' of the IETF HR MIB, specified as a
    'tagged string argument' using the standard 'DX' tag or the generic
    'OI/OV' tags (see 'XcmHrDevMgmtCommandDataTag' textual convention).
    
3)  A 'deviceCreate' or 'deviceInstall' request shall NOT include
    'createAndWait' or 'createAndGo' writes to the row status variables
    of one or more auxiliary device groups defined in the XCMI HRX MIB
    (eg, Device Info, Device Mgmt, Device Power, etc) - these conceptual
    rows may be SUBSEQUENTLY created by separate 'deviceManage'
    operations (also specifying 'hrDeviceIndex' via 'DX').  




















XCMI Working Group  File 10hosttc               [Page 27]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.5.4.  Example of System Job Create Request

New 'system job' entries are created, in the 'xcmJobGenBasicTable' of
the XCMI Job Monitoring MIB, using 'deviceJobCreate' in
'xcmHrDevMgmtCommandRequest' in the Device Mgmt group of the XCMI HRX
MIB.  These requests are sent to the 'responsible platform CPU' device
(of type 'hrDeviceProcessor').  


Given a fixed locale specification:  

--  IETF HR MIB (RFC 2790) objects
hrDeviceType.2                          = 'hrDeviceProcessor'
    --  indexed by 'hrDeviceIndex'
    --  host system 'main CPU' (ie, 'responsible platform CPU')

--  XCMI General MIB (07gen) objects
xcmGenFixedLocalizationIndex.2          = '1'
    --  indexed by 'hrDeviceIndex'
    --  fixed (install-time) locale for 'responsible platform CPU'
xcmGenLocalizationLanguage.2.1          = 'en'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  English (from ISO 639:1988 'Codes for Names of Languages')
xcmGenLocalizationCountry.2.1           = 'us'
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  USA (from ISO 3166:1993 'Codes for Names of Countries')
xcmGenLocalizationCharacterSet.2.1      = '3' -- US-ASCII
    --  indexed by 'hrDeviceIndex' and 'xcmGenLocalizationIndex'
    --  ANSI_X3.4-1968 or ISO_646.irv:1991 (Int'l Reference Version)
    --  (using 'MIBenum' from IANA Character Sets registry, found at
    --  'ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets')


A 'simple device management request' to create a new 'system job' row in
the 'xcmJobGenBasicTable' may be specified as follows:  

--  XCMI HRX MIB (11hostx) objects
xcmHrDevMgmtCommandRequest.2            = 'deviceJobCreate(1312)'
    --  device management request to create a new 'system job'
xcmHrDevMgmtCommandData.2   = 'JC=0.2.13.4361.2.11.3045:'
                            + 'JP=50:'
                            + 'JO=john:'
                            + 'JW=DEMO:'
                            + 'JX=1:'
    --  device management request 'tagged string arguments'
    --  [JC] Set 'xcmJobClientId' (null node / user ID / sequence ID)
    --  [JP] Set 'xcmJobPriority' to '50'
    --  [JO] Set 'xcmJobOwner' to 'john'
    --  [JW] Set system job type to 'DEMO' (basic product demo)
    --  [JX] Set product-specific extended system job type '1'
    --  [JW/JX] Set 'xcmJobName' to 'DEMO1'


XCMI Working Group  File 10hosttc               [Page 28]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



Note:  A subsequent lookup via the 'xcmClientIdMapTable' in the XCMI Job
Monitoring MIB is necessary to map from the submitted 'xcmJobClientId'
to the managed host system's 'xcmJobIdentifierOnSystem' (for monitoring 
the progress of the 'system job').  


Conformance:  

1)  A 'deviceJobCreate' request shall ALWAYS be written to
    'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB of the 'responsible
    platform CPU' (of type 'hrDeviceProcessor'); 
    
2)  A 'deviceJobCreate' request shall ALWAYS include the desired value
    of 'xcmJobClientId' for the NEW conceptual row to be created in the
    'xcmJobGenBasicTable' of the XCMI Job Mon MIB, specified as a
    'tagged string argument' using the standard 'JC' tag or the generic
    'OI/OV' tags (see 'XcmHrDevMgmtCommandDataTag' textual convention); 
    
3)  A 'deviceJobCreate' request shall ALWAYS include the desired type of
    'system job' for the NEW conceptual row to be created in the
    'xcmJobGenBasicTable' of the XCMI Job Mon MIB, specified as a
    'tagged string argument' using the standard 'JW' tag or the generic
    'OI/OV' tags (see 'XcmHrDevMgmtCommandDataTag' textual convention).






























XCMI Working Group  File 10hosttc               [Page 29]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



3.6.  Job Service Devices

Some device types (used in 'hrDeviceType' in IETF HR MIB) shall ALWAYS
support job services, when present on a managed host system, as follows:

1)  'xcmHrDeviceHostSystem' (defined in XCMI HRX TC) 
    - displays ALL jobs in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    - 'xcmJobServiceType' in Job General Basic group (XCMI Job Mon MIB) 
    and/or 'jobServiceTypes' in Job Attribute group (PWG Job Mon MIB); 
    
2)  'xcmHrDeviceScanner' (defined in XCMI HRX MIB) 
    - displays scan jobs in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    
3)  'xcmHrDeviceCopier' (defined in XCMI HRX MIB) 
    - displays copy jobs in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    
4)  'xcmHrDeviceFax' (defined in XCMI HRX MIB) 
    - displays fax jobs in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    
5)  'hrDevicePrinter' (defined in IETF HR MIB) 
    - displays print jobs in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 

A job service device MAY point to an associated job history device via
an entry in the 'xcmHrDevDetailTable' (in XCMI HRX MIB) with a type of
'deviceJobHistoryDeviceIndex'.  


3.7.  Job History Devices

Some device types (used in 'hrDeviceType' in IETF HR MIB) shall ALWAYS
support job history, when present on a managed host system, as follows:

1)  'xcmHrDeviceHostSystemHistory' (defined in XCMI HRX TC) 
    - displays ALL history in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    - 'xcmJobServiceType' in Job General Basic group (XCMI Job Mon MIB) 
    and/or 'jobServiceTypes' in Job Attribute group (PWG Job Mon MIB); 
    
2)  'xcmHrDeviceScannerHistory' (defined in XCMI HRX MIB) 
    - displays scan history in 'xcmJobGenBasicTable' (XCMI Job Mon MIB) 
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    
3)  'xcmHrDeviceCopierHistory' (defined in XCMI HRX MIB) 
    - displays copy history in 'xcmJobGenBasicTable' (XCMI Job Mon MIB) 
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    


XCMI Working Group  File 10hosttc               [Page 30]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

4)  'xcmHrDeviceFaxHistory' (defined in XCMI HRX MIB) 
    - displays fax history in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 
    
5)  'xcmHrDevicePrinterHistory' (defined in XCMI HRX MIB) 
    - displays print history in 'xcmJobGenBasicTable' (XCMI Job Mon MIB)
    and/or 'jmJobTable' (PWG Job Mon MIB); 

A job history device SHOULD point to an associated job service device
via an entry in the 'xcmHrDevDetailTable' (in XCMI HRX MIB) with a type 
of 'deviceJobServiceDeviceIndex'.  












































XCMI Working Group  File 10hosttc               [Page 31]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



4.  Managed Object Definitions



4.1.  Definition of HRX Textual Conventions


XEROX-HOST-RESOURCES-EXT-TC DEFINITIONS ::= BEGIN
--  Module: XCMI Extensions to IETF Host Resources TC
--  File:   10hosttc.mib
--  Date:   19 July 2019 - Version 6.008.pub   VersionUpdate

--  Textual Conventions companion to the Host Resources Extensions MIB
--  Contains the REGISTRY of XCMI Standard Device Types,
--  the REGISTRY of XCMI Standard CRU Types,
--  the REGISTRY of XCMI HRX Admin Service Types, and
--  the REGISTRY of XCMI HRX Admin Device Operation Types.

IMPORTS
    MODULE-IDENTITY, OBJECT-IDENTITY,
        OBJECT-TYPE
            FROM SNMPv2-SMI             -- IETF RFC 1442/1902/2578
    TEXTUAL-CONVENTION
            FROM SNMPv2-TC              -- IETF RFC 1443/1903/2579
    xeroxCommonMIB
            FROM XEROX-COMMON-MIB;

xcmHrTC MODULE-IDENTITY
    LAST-UPDATED "1907190000Z" -- 19 July 2019
    ORGANIZATION "Xerox Corporation - XCMI Working Group"
    CONTACT-INFO
        "           XCMI Editors
        Email:      xcmi.editors@xerox.com
        "
    DESCRIPTION
        "Version:    6.008.pub

        The TC module for textual conventions, enumerated types, OIDs,
        and other volatile elements of the companion Host Resources
        Extensions MIB ('xcmHrMIB'), which supports extended
        configuration and management of various host resources for
        network accessible host systems.  These modules augment and
        extend the original IETF Host Resources MIB (RFC 2790).

        Usage:  This MIB module introduces support for the 'realization'
        of both 'physical' and 'logical' devices, consistent with ISO
        DPA (Document Printing Application), ISO/IEC 10175, as reflected
        in the object 'xcmHrDevInfoRealization'.

        Note:   Conforming implementations SHALL NOT 'bubble up' status
        from 'physical' devices to associated 'logical' devices.  All

XCMI Working Group  File 10hosttc               [Page 32]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        devices SHALL report their own status ONLY.

        See:    Section 9 'Supplement' in XCMI Extensions to IETF Host
        Resources TC, for implementation guidance for this TC module.

        Copyright (C) 1995-2017 Xerox Corporation. All Rights Reserved."
    ::= { xeroxCommonMIB 52 }

--
--          XCMI Extensions to IETF Host Resources (HRX) TC
--

--          REGISTRY of XCMI Standard Device Types
--          (used with 'hrDeviceType' in Device Group
--          of the IETF Host Resources MIB, RFC 2790).
--
--  Usage:  Developers SHOULD request registration of appropriate
--  XCMI standard device types when they design or integrate a device
--  (with some physical, and NOT merely logical, realization)
--  which is network manageable on a host system.
--
--  Usage:  Logical devices (ie, services of some sort) SHOULD
--  be represented by: a) their own fully free-standing MIBs; and/or
--  b) elaboration of an existing IETF or XCMI standard device type into
--  a 'logical' sibling.
--
--  The final arc of IETF standard device types is within the
--  range '1..49'.
--  The final arc of XCMI standard device types is within the
--  range '101..149'.
--
--  In the future, XCMI MAY add types for 'marker', 'input tray', etc,
--  to enable support of managed host systems which do NOT have printer
--  capabilities (and therefore do NOT implement the Printer MIB),
--  and to support installation and configuration information for
--  their component physical subunits.

xcmHrDeviceTypes OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The root of all additional device types defined in HRX TC."
    ::= { xcmHrTC 2 }

xcmHrDeviceHostSystem OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Host system device type - manufacturer independent.
        For host systems which instrument multiple devices and
        support MIBs with tables INDEXed by 'hrDeviceIndex', the single
        'xcmHrDeviceHostSystem' device represents the 'root' device
        which MAY be used to manage overall host system defaults,
        configuration, status, etc."
    REFERENCE
        "See:   'xcmHrDeviceHostSystemHistory' in this XCMI HRX TC."

XCMI Working Group  File 10hosttc               [Page 33]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    ::= { xcmHrDeviceTypes 101 }

xcmHrDeviceScanner OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Scanner device type - manufacturer independent.
        An 'xcmHrDeviceScanner' device with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' input device (eg, a 'scan channel' on a
        multifunction printer).
        An 'xcmHrDeviceScanner' device with 'xcmHrDevInfoRealization' of
        'logical' is a 'virtual' input device (eg, a 'personality' of a
        'scan channel' on a multifunction printer)."
    REFERENCE
        "See:   'xcmHrDeviceScannerHistory' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 102 }

xcmHrDeviceCopier OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Copier device type - manufacturer independent.
        An 'xcmHrDeviceCopier' device with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' I/O device (eg, a 'copier' on a
        multifunction printer).
        An 'xcmHrDeviceCopier' device with 'xcmHrDevInfoRealization' of
        'logical' is a 'virtual' I/O device (eg, a 'personality' of a
        'copier' on a multifunction printer)."
    REFERENCE
        "See:   'xcmHrDeviceCopierHistory' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 103 }


xcmHrDeviceFax OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Fax device type - manufacturer independent.
         xcmHrDeviceFax is maintained for legacy products.  It is 
         recommended that the hrDeviceType is explicitly defined using
         xcmHrDeviceEmbeddedFax, xcmHrDeviceServerFax or
         xcmHrDeviceInternetFax.
        An 'xcmHrDeviceFax' device with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' I/O device (eg, a 'fax channel' on a
        multifunction printer).
        An 'xcmHrDeviceFax' device with 'xcmHrDevInfoRealization' of
        'logical' is a 'virtual' I/O device (eg, a 'personality' of a
        'fax channel' on a multifunction printer)."
    REFERENCE
        "See:   'xcmHrDeviceFaxHistory' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 104 }

xcmHrDeviceMailbox OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Mailbox device type - manufacturer independent.
        An 'xcmHrDeviceMailbox' device is a 'multi-bin' output device,

XCMI Working Group  File 10hosttc               [Page 34]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        with each 'bin' assigned to a user, group, account, etc, and
        (optionally) physical security associated with each 'bin'.
        An 'xcmHrDeviceMailbox' device with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' output device (eg, a 'tower mailbox' on
        a high-end printer).
        An 'xcmHrDeviceMailbox' device with 'xcmHrDevInfoRealization' of
        'logical' is a 'virtual' output device (eg, a 'personality' of a
        'tower mailbox' on a high-end printer).

        An 'xcmHrDeviceMailbox' device with 'xcmHrDevInfoRealization' of
        'logical' MAY also indicate the current configuration of a
        'physical' device of type 'xcmHrDeviceMailboxSorter'."
    REFERENCE
        "See:   'xcmHrDeviceMailboxSorter' and 'xcmHrDeviceSorter'."
    ::= { xcmHrDeviceTypes 105 }

xcmHrDeviceFinisher OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Finisher device type - manufacturer independent.
        An 'xcmHrDeviceFinisher' device is an output finishing device.
        An 'xcmHrDeviceFinisher' device with 'xcmHrDevInfoRealization'
        of 'physical' is a 'real' output device (eg, a 'stapler'
        on a high-end printer).
        An 'xcmHrDeviceFinisher' device with 'xcmHrDevInfoRealization'
        of 'logical' is a 'virtual' output device (eg, a 'personality'
        of a 'stapler' on a high-end printer)."
    ::= { xcmHrDeviceTypes 106 }

xcmHrDeviceFeeder OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Feeder device type - manufacturer independent.
        An 'xcmHrDeviceFeeder' device is an input device.
        An 'xcmHrDeviceFeeder' device with 'xcmHrDevInfoRealization'
        of 'physical' is a 'real' output device (eg, a 'high-capacity
        feeder' on a high-end printer).
        An 'xcmHrDeviceFeeder' device with 'xcmHrDevInfoRealization'
        of 'logical' is a 'virtual' output device (eg, a 'personality'
        of a 'high-capacity feeder' on a high-end printer)."
    ::= { xcmHrDeviceTypes 107 }

xcmHrDeviceSorter OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Sorter device type - manufacturer independent.
        An 'xcmHrDeviceSorter' device is a 'multi-bin' output device,
        with each 'bin' assigned to a copy of the current job, and
        NO physical security associated with each 'bin'.
        An 'xcmHrDeviceSorter' device with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' output device (eg, a '10-bin sorter' on
        a mid-range printer).
        An 'xcmHrDeviceSorter' device with 'xcmHrDevInfoRealization' of
        'logical' is a 'virtual' output device (eg, a 'personality' of a

XCMI Working Group  File 10hosttc               [Page 35]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        '10-bin sorter' on a mid-range printer).

        An 'xcmHrDeviceSorter' device with 'xcmHrDevInfoRealization' of
        'logical' MAY also indicate the current configuration of a
        'physical' device of type 'xcmHrDeviceMailboxSorter'."
    REFERENCE
        "See:   'xcmHrDeviceMailboxSorter' and 'xcmHrDeviceMailbox'."
    ::= { xcmHrDeviceTypes 108 }

xcmHrDeviceMailboxSorter OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "MailboxSorter device type - manufacturer independent.
        An 'xcmHrDeviceMailboxSorter' is a 'multi-bin' output device,
        which MAY be configured as either a 'mailbox' or a 'sorter',
        by a system adminstrator or by default product configuration.
        An 'xcmHrDeviceMailboxSorter' with 'xcmHrDevInfoRealization' of
        'physical' is a 'real' output device and associated with
        associated with exactly two 'logical' output devices of types
        'xcmHrDeviceMailbox' and 'xcmHrDeviceSorter' - one of these
        'logical' devices MAY be 'running' (currently configured) - at
        least one SHALL be 'down' (NOT currently configured)."
    ::= { xcmHrDeviceTypes 109 }

xcmHrDevicePrintAppliance OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Print appliance device type - manufacturer independent.
        An 'xcmHrDevicePrintAppliance' is a network printing appliance
        with 'xcmHrDevInfoRealization' of 'physical'.
        An 'xcmHrDevicePrintAppliance' SHALL statically and/or actively
        discover available network printers and SHOULD advertise them
        as supported output devices, using rows in 'hrDeviceTable' of
        IETF HR MIB (RFC 2790) and 'prtGeneralTable' of the Printer MIB
        (RFC 1759 or successor), with 'hrDeviceType' set to
        'hrDevicePrinter'.
        An 'xcmHrDevicePrintAppliance' SHALL NOT use 'hrDeviceIndex' of
        '1' (first row) for an 'hrDevicePrinter' row, because a network
        printing appliance is an enhanced spooler and NOT a printer."
    REFERENCE
        "See:   'hrDevicePrinter' in IETF Host Resources MIB (RFC 2790).
        See:    'xcmHrDevicePrinterHistory' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 110 }

xcmHrDeviceMarker OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Marker Engine device type - manufacturer independent.
        An 'xcmHrDeviceMarker' device with 'xcmHrDevInfoRealization' 
        of 'physical' is a 'real' output device (eg, the 
        'marking engine' on a multifunction printer or copier).  The 
        marking engine is the module that accepts a print ready image 
        and physical media as input and outputs physical media with a 
        physical representation of the print ready input image.  The 

XCMI Working Group  File 10hosttc               [Page 36]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        'xcmHrDeviceMarker' is a 
        single module within a group of modules that cumulatively are 
        represented by 'hrDevicePrinter'. The marker shall represent the
        whole marker as a single physical unit and should maintain a 
        single entry in the 'hrDeviceTable' for all products that 
        support a single marking engine regardless of internal engine
        mark points. 
        (e.g. B&W, Highlight Color and Full Color Presses shall have a 
        single entry in 'hrDeviceTable'). Multiple entries of 
        'xcmHrDeviceMarker' may exist in the 'hrDeviceTable' if the 
        system supports multiple print engines whether chained, in     
        parallel or in any other configuration.   
        An 'xcmHrDeviceMarker' SHALL NOT use 'hrDeviceIndex' of
        '1' (first row).  The index 1 is reserved for an 
        'hrDevicePrinter' row." 
    ::= { xcmHrDeviceTypes 111 }

xcmHrDeviceFinisherBFM OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Basic Finisher Module device type - manufacturer independent.
        An 'xcmHrDeviceFinisherBFM' device is a basic output finishing
        device. An 'xcmHrDeviceFinisherBFM' device with 
        'xcmHrDevInfoRealization' of 'physical' is a 'real' output 
        device (eg, a 'stapler' on a high-end printer).
        An 'xcmHrDeviceFinisherBFM' device with 
        'xcmHrDevInfoRealization' of 'logical' is a 'virtual' output 
        device (eg, a 'personality' of a 'stapler' on a high-end 
        printer)."
    ::= { xcmHrDeviceTypes 112 }

xcmHrDeviceFinisherMFF OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Multi-Function Finisher device type - manufacturer 
         independent.
        An 'xcmHrDeviceFinisherMFF' device is a multi-function output 
         finishing device. An 'xcmHrDeviceFinisherMFF' device with 
         'xcmHrDevInfoRealization' of 'physical' is a 'real' output 
         device (eg, a 'saddle stitcher', 'C-Folder', 'Z-Folder', 
         'Hole Puncher' on a high-end printer).
        An 'xcmHrDeviceFinisherMFF' device with 
         'xcmHrDevInfoRealization' of 'logical' is a 'virtual' output 
         device (eg, a 'personality' of a 'saddle stitcher', 
         'C-Folder', 'Z-Folder', 'Hole Puncher' on a 
        high-end printer)."
    ::= { xcmHrDeviceTypes 113 }

xcmHrDeviceFinisherXIM OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
         "eXternal Interface Module Finisher device type.
        An 'xcmHrDeviceFinisherXIM' device is a hardware interface 
        used to pass media from a Xerox printing device to a 3rd party

XCMI Working Group  File 10hosttc               [Page 37]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        finishing devices. The 'xcmHrDeviceFinihserXIM' may or may not 
        contain its own output trays or finishing capabilities.
        An 'xcmHrDeviceFinisherXIM' device with 
        'xcmHrDevInfoRealization' of 'physical' is a 'real' output 
        device (e.g., an 'output bridge' on a high-end printer)."
    ::= { xcmHrDeviceTypes 114 }

xcmHrDeviceFinisher3rdParty OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
         "3rd Party Finisher device type - manufacturer independent.
        An 'xcmHrDeviceFinisher3rdParty' device is an output finishing 
        device. An 'xcmHrDeviceFinisher3rdParty' device with 
        'xcmHrDevInfoRealization'
        of 'physical' is a 'real' output device (eg, a 'stapler' on 
        a high-end printer). An 'xcmHrDeviceFinisher3rdParty' device 
        with 'xcmHrDevInfoRealization' of 'logical' is a 'virtual' 
        output device (eg, a 'personality' of a 'stapler' on a high-end
        printer)."
    ::= { xcmHrDeviceTypes 115 }

xcmHrDevicePaymentInterface OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Payment Interface device type - manufacturer independent.
        An 'xcmHrDevicePaymentInterface' device is an payment 
        authorization device.
        An 'xcmHrDevicePaymentInterface' device with 
        'xcmHrDevInfoRealization' of 'physical' is a 'real' point of 
        purchase validation device (eg, a 'coin operated', 'smart card' 
        or other form of point of purchase payment for services 
        rendered on a multi-function printer or copier).
        An 'xcmHrDevicePaymentInterface' device with 
        'xcmHrDevInfoRealization' of 'logical' is a 'virtual' point 
        of purchase validation device (eg, a software service that 
        accepts payment through the Web or some other form of remote 
        point of purchase payment for services rendered on a 
        multi-function printer or copier)."
    ::= { xcmHrDeviceTypes 116 }

xcmHrDeviceInterposer OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Interposer device type - manufacturer independent.
        An 'xcmHrDeviceInterposer' device is an input device which 
        physically resides downstream of the print engine amongst 
        finishing modules.
        An 'xcmHrDeviceInterposer' device with 
        'xcmHrDevInfoRealization' of 'physical' is a 'real' input 
        device (eg, a 'high-capacity Interposing feeder' that 
        physically resides amongst finishing modules
        on a high-end printer).
        An 'xcmHrDeviceInterposer' device with 
        'xcmHrDevInfoRealization' of 'logical' is a 'virtual' 

XCMI Working Group  File 10hosttc               [Page 38]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        input device (eg, a 'personality' of a 
        'high-capacity Interposing feeder' that physically resides 
        amongst finishing modules on a high-end printer). 
        Interposers are essentially feeders that are placed 
        downstream of the print engine paper path and upstream of 
        finishing devices.  Interposer fed media is not marked by the
        print engine; instead media fed from an interposer is inserted 
        before, between or after marked pages.  The media constitutes 
        covers, separators etc."  
    ::= { xcmHrDeviceTypes 117 }

xcmHrDeviceInternetFax OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Internet Fax device type - manufacturer independent.
 A local Fax service which sends and/or receives faxes
 over the internet"
    REFERENCE
        "See:   'xcmHrDeviceFax' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 118 }

xcmHrDeviceServerFax OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Server Fax device type - manufacturer independent.
 A Fax service which works with a server on the network
 to send and/or receive faxes over a remote modem and
 phone lines"
    REFERENCE
        "See:   'xcmHrDeviceFax' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 119 }

xcmHrDeviceEmbeddedFax OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Embedded Fax device type - manufacturer independent. 
         A local fax service which sends and/or receives fax 
         directly over a modem and phone lines."
    REFERENCE
        "See:   'xcmHrDeviceFax' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 120 }

xcmHrDeviceForeignInterface OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Foreign Interface device type - manufacturer independent. 
         A physical connection provided by a device for the purpose 
         of connecting an external accessory. This accessory may 
         be capable of tracking data (e.g. Auditron) or may enable/ 
         disable device operation (e.g. card reader, coin operator, 
         etc.). This device type shall only be used when the device 
         cannot detect the type of external accessory that is 
         physically connected. If the device can detect the type of 
         external accessory which can be physically connected, 

XCMI Working Group  File 10hosttc               [Page 39]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

         then the appropriate device type for that interface should 
         be used instead. (e.g. xcmHrDevicePaymentInterface, 
         xcmHrDeviceSecurityInterface, or 
         xcmHrDeviceAccountingInterface" 
    ::= { xcmHrDeviceTypes 121 } 

xcmHrDeviceSecurityInterface OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Security device type - manufacturer independent. 
         A physical connection provided by a device for the purpose 
         of connecting an external security-related accessory. This 
         accessory may consist of a card reader or biometric device 
         which would restrict access to a machine to only authorized 
         users." 
    ::= { xcmHrDeviceTypes 122 } 

xcmHrDeviceAccountingInterface OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Accounting device type - manufacturer independent. 
         A physical connection provided by a device for the purpose 
         of connecting an external accounting-related accessory. This 
         accessory would provide the capability to track machine 
         usage but would not restrict access to the machine as would 
         an accessory defined by type xcmHrDevicePaymentInterface." 
    ::= { xcmHrDeviceTypes 123 } 

xcmHrDeviceFeederSFM OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Feeder device type - Xerox Substraite Feeding Module 
        An 'xcmHrDeviceFeederSFM' device is an input device. 
        An 'xcmHrDeviceFeederSFM' device with 
        'xcmHrDevInfoRealization' of 'physical' is a 'real' output 
        device (eg, a 'high-capacity feeder' on a high-end printer). 
        An 'xcmHrDeviceFeeder' device with 'xcmHrDevInfoRealization' 
        of 'logical' is a 'virtual' output device (eg, a 'personality' 
        of a 'high-capacity feeder' on a high-end printer)." 
    ::= { xcmHrDeviceTypes 124 } 

xcmHrDeviceFeederLFF OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Feeder device type - Xerox Large Format Feeder. 
        An 'xcmHrDeviceFeederLFF' device is an input device. 
        An 'xcmHrDeviceFeeder' device with 'xcmHrDevInfoRealization' 
        of 'physical' is a 'real' output device (eg, a 'high-capacity 
        large format feeder' on a high-end printer). 
        An 'xcmHrDeviceFeeder' device with 'xcmHrDevInfoRealization' 
        of 'logical' is a 'virtual' output device (eg, a 'personality' 
        of a 'high-capacity large format feeder' 
        on a high-end printer)." 
    ::= { xcmHrDeviceTypes 125 } 

XCMI Working Group  File 10hosttc               [Page 40]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


xcmHrDeviceScannerADF OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Scanner device type - manufacturer independent automatic 
         document feeding scanner.  An 'xcmHrDeviceScannerADF' device 
         with 'xcmHrDevInfoRealization' of 'physical' is a 'real' input 
         device (eg, a 'scan channel' on a multifunction printer). 
         An 'xcmHrDeviceScannerADF' device with 
         'xcmHrDevInfoRealization' of 'logical' is a 'virtual' input 
         device (eg, a 'personality' of a 'scan channel' on a 
         multifunction printer)." 
    REFERENCE 
        "See:   'xcmHrDeviceScannerHistory' in this XCMI HRX TC." 
    ::= { xcmHrDeviceTypes 126 } 

xcmHrDeviceScannerPlaten OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "Scanner device type -  manufacturer independent platen glass 
         scanner. An 'xcmHrDeviceScannerPlaten' device with 
         'xcmHrDevInfoRealization' of 'physical' is a 'real' input 
         device (eg, a 'scan channel' on a multifunction printer). 
        An 'xcmHrDeviceScannerPlaten' device with 
        'xcmHrDevInfoRealization' of 'logical' is a 'virtual' input 
        device (eg, a 'personality' of a 'scan channel' on a 
        multifunction printer)." 
    REFERENCE 
        "See:   'xcmHrDeviceScannerHistory' in this XCMI HRX TC." 
    ::= { xcmHrDeviceTypes 127 } 

xcmHrDeviceColorScanningCard OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "An xcmHrDeviceColorScanningCard is a physical card that allows 
         for scanning of color, or monochrome, images from the printer
         to a remote device."
    ::= { xcmHrDeviceTypes 128 } 

xcmHrDeviceSIPFax OBJECT-IDENTITY 
    STATUS      current 
    DESCRIPTION 
        "SIPFax device type - manufacturer independent. (Voice 
         Over Internet Protocol) 
 A local fax service which sends and/or receives fax 
         directly over a network line untilizing a VOIP system"

    REFERENCE 
        "See:   'xcmHrDeviceSIPFax' in this XCMI HRX TC." 
    ::= { xcmHrDeviceTypes 129 } 





XCMI Working Group  File 10hosttc               [Page 41]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--          REGISTRY of XCMI Standard History Device Types
--          (used with 'hrDeviceType' in Device Group
--          of the IETF Host Resources MIB, RFC 2790).
--
--  Usage:  May be used to segregate historical information for any
--  standard device type in any MIB table indexed by 'hrDeviceIndex'.
--
--  Eg, the 'xcmJobGenBasicTable' in the XCMI Job Monitoring MIB and/or
--  the 'jm[Job|Attribute]Table' in the PWG Job Monitoring MIB could
--  have a segment for an 'hrDevicePrinter' device type (current and
--  very recent jobs) and a segment for an 'xcmHrDevicePrinterHistory'
--  device type (longer-term job history of completed jobs).
--  Entries in the 'xcmHrDevDetailTable' SHOULD cross-link these related
--  devices (using 'deviceJob[Service|History]DeviceIndex').
--
--  Algorithm:  The final arc of each standard job history device type
--  is derived by adding decimal '50' to the final arc of the companion
--  standard job service device type.

xcmHrDeviceHostSystemHistory OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Host system history device type - manufacturer independent."
    REFERENCE
        "See:   'xcmHrDeviceHostSystem' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 151 }

xcmHrDeviceScannerHistory OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Scanner history device type - manufacturer independent."
    REFERENCE
        "See:   'xcmHrDeviceScanner' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 152 }

xcmHrDeviceCopierHistory OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Copier history device type - manufacturer independent."
    REFERENCE
        "See:   'xcmHrDeviceCopier' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 153 }

xcmHrDeviceFaxHistory OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Fax history device type - manufacturer independent."
    REFERENCE
        "See:   'xcmHrDeviceFax' in this XCMI HRX TC."
    ::= { xcmHrDeviceTypes 154 }

xcmHrDeviceNFC OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION

XCMI Working Group  File 10hosttc               [Page 42]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        "Near Field Communication (NFC)  - manufacturer independent."
    REFERENCE
        "See:   'hrDeviceType' in IETF HR MIB (RFC 2790)."
    ::= { xcmHrDeviceTypes 155 }


xcmHrDeviceWireless OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Wi-Fi or Wi-Fi Direct Interface - manufacturer independent."
    REFERENCE
        "See:   'hrDeviceType' in IETF HR MIB (RFC 2790)."
    ::= { xcmHrDeviceTypes 156 }


xcmHrDevicePrinterHistory OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "Printer history device type - manufacturer independent."
    REFERENCE
        "See:   'hrDevicePrinter' in the IETF HR MIB."
    ::= { xcmHrDeviceTypes 55 }         -- 'hrDevicePrinter' + 50

--          REGISTRY of XCMI Standard CRU Types
--          (used with 'hrDeviceType' in Device Group
--          of the IETF Host Resources MIB, RFC 2790).

xcmHrCruXerographicModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU xerographic module - manufacturer independent.
        An 'xcmHrCruXerographicModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 201 }

xcmHrCruFuserModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU fuser module - manufacturer independent.
        An 'xcmHrCruFuserModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 202 }

xcmHrCruTonerBottleModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU toner bottle module - manufacturer independent.
        An 'xcmHrCruTonerBottleModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 203 }

xcmHrCruCollectorBottleModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION

XCMI Working Group  File 10hosttc               [Page 43]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        "CRU (developer) collector bottle - manufacturer independent.
        An 'xcmHrCruCollectorBottleModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 204 }

xcmHrCruTrayFeedHeadModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU tray feed head module - manufacturer independent.
        An 'xcmHrCruTrayFeedHeadModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 205 }

xcmHrCruAdfFeedHeadModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU ADF feed head module - manufacturer independent.
        An 'xcmHrCruAdfFeedHeadModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'.
        Note:   ADF is an acronym for 'automatic document feeder'."
    ::= { xcmHrDeviceTypes 206 }

xcmHrCruFuserWebModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU fuser web module - manufacturer independent.
        An 'xcmHrCruFuserWebModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'.
        Note:   A 'fuser web' is an oil-soaked fiber roll in a fuser,
        which prevents toner from getting on the fuser roll.  The 'fuser
        web' device would normally be replaced several times before the
        actual fuser device ('xcmHrCRUFuserModule') is replaced."
    ::= { xcmHrDeviceTypes 207 }

xcmHrCruFilterModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU filter module - manufacturer independent.
        An 'xcmHrCruFilterModule' device is a customer replaceable 
        filter or filter unit, with 'xcmHrDevInfoRealization' of
        'physical'."
    ::= { xcmHrDeviceTypes 208 }

xcmHrCruCleanerUnitModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU cleaner unit module - manufacturer independent.
        An 'xcmHrCruCleanerUnitModule' device is a customer
        replaceable cleaner unit, with 'xcmHrDevInfoRealization' of
        'physical' (eg, a belt cleaner or a photoreceptor cleaner)."
    REFERENCE
        "See:   'cleanerUnit' in 'PrtMarkerSuppliesTypeTC' in
                the Printer MIB v2."
    ::= { xcmHrDeviceTypes 209 }

XCMI Working Group  File 10hosttc               [Page 44]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


xcmHrCruTransferUnitModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU transfer unit module - manufacturer independent.
        An 'xcmHrCruTransferUnitModule' device is a customer
        replaceable transfer unit, with 'xcmHrDevInfoRealization' of
        'physical'."
    REFERENCE
        "See:   'transferUnit' in 'PrtMarkerSuppliesTypeTC' in
                the Printer MIB v2."
    ::= { xcmHrDeviceTypes 210 }

xcmHrCruTransferRollerModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU transfer roller module - manufacturer independent.
        An 'xcmHrCruTransferRollerModule' device is a customer
        replaceable transfer roller, with 'xcmHrDevInfoRealization' of
        'physical' (eg, a biased transfer roller)."
    REFERENCE
        "See:   'transferUnit' in 'PrtMarkerSuppliesTypeTC' in
                the Printer MIB v2."
    ::= { xcmHrDeviceTypes 211 }

xcmHrCruPFPFeedRollModule OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "CRU Paper Feed Platform module - manufacturer independent.
        An 'xcmHrCruPaperFeedModule' device is a customer
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 212 }

xcmHrCruPFPRetardRollModule OBJECT-IDENTITY
    STATUS    current
    DESCRIPTION
        "CRU PFP Retard Roll module - manufacturer independent.
        An 'xcmHrCruPFPRetardRollModule' device is a customer 
        replaceable unit, with 'xcmHrDevInfoRealization' of 'physical'."
    ::= { xcmHrDeviceTypes 213 }

xcmHrDeviceUSBPort  OBJECT-IDENTITY 
 STATUS current 
 DESCRIPTION 
  "The device type identifier used for a
  Universal Serial Bus port." 
 ::= { xcmHrDeviceTypes 250 } 

xcmHrDeviceFlashDIMMFileStore  OBJECT-IDENTITY 
 STATUS current 
 DESCRIPTION 
         "The device type identifier used for a Flash DIMM that contains
          a file system that is used to store files such as font files. 
          As opposed to a Flash DIMM that contains a boot loader."

XCMI Working Group  File 10hosttc               [Page 45]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

 ::= { xcmHrDeviceTypes 260 } 

xcmHrDeviceFlashDIMMBootLoader  OBJECT-IDENTITY 
 STATUS current 
 DESCRIPTION 
         "The device type identifier used for a Flash DIMM that contains
          the boot loader for a device. Files may or may not be stored 
          on this device. As opposed to a Flash DIMM that contains a 
          file store system." 
 ::= { xcmHrDeviceTypes 261 } 

xcmHrDeviceFlashDrive  OBJECT-IDENTITY 
        STATUS current 
        DESCRIPTION 
        "The device type identifier used for a Flash Drive for a device.
          Files may or may not be stored on this device. As opposed to a
          Flash DIMM that contains a file store system or a bootloader."
        ::= { xcmHrDeviceTypes 262 } 

--          REGISTRY of XCMI HRX Admin Service Types (Classes)
--          (MAY be used in the 'xcmSec[Service|PolicyService]TypeOID'
--          objects in the closely related XCMI Security MIB, in
--          conforming management agents which do NOT implement the
--          related XCMI System Admin MIB).

xcmHrAdminServiceTypes OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The root of all host system management service types (classes)
        defined in the Host Resources Extensions TC."
    REFERENCE
        "See:   'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrTC 3 }

xcmHrAdminObjectService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system object management service."
    REFERENCE
        "See:   'xcmSysAdminObject...' in XCMI System Admin MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 1 }

xcmHrAdminServerService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system server management service."
    REFERENCE
        "See:   'xcmSysAdminServer...' in XCMI System Admin MIB,
                'hrSW[Running|Installed]Table' in IETF HR MIB, and
                'xcmHrSW[Running|Installed]ExtTable' in XCMI HRX MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'

XCMI Working Group  File 10hosttc               [Page 46]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 2 }

xcmHrAdminDeviceService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system device management service."
    REFERENCE
        "See:   'xcmSysAdminDevice...' in XCMI System Admin MIB,
                'hrDeviceTable' in IETF HR MIB, and
                'xcmHrDev[Info|Help|Mgmt|Power|Traffic|Calendar]Table'
                in XCMI HRX MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 3 }

xcmHrAdminJobService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system job management service."
    REFERENCE
        "See:   'xcmSysAdminJob...' in XCMI System Admin MIB, and
                'xcmJob[...]Table' in XCMI Job Monitoring MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 4 }

xcmHrAdminDocService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system document management service."
    REFERENCE
        "See:   'xcmSysAdminDoc...' in XCMI System Admin MIB, and
                'xcmDoc[...]Table' in XCMI Job Monitoring MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 5 }

xcmHrAdminSecurityService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system security management service."
    REFERENCE
        "See:   'xcmSysAdminSecurity...' in XCMI System Admin MIB.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 6 }

xcmHrAdminCommsService OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The host system communications management service."
    REFERENCE
        "See:   'xcmSysAdminComms...' in XCMI System Admin MIB and

XCMI Working Group  File 10hosttc               [Page 47]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

                XCMI Comms Config and Comms Engine MIBs.
        See:    'XcmSecPosixVerbs' and 'xcmSecServiceTypeOID'
                in XCMI Security TC/MIB."
    ::= { xcmHrAdminServiceTypes 7 }

--          REGISTRY of XCMI HRX Admin Device Operation Types
--          (MAY be used in the 'xcmSecPolicyVerbTypeOID'
--          object in the closely related XCMI Security MIB, for
--          fine-grained access control to device management verbs, in
--          conforming management agents which do NOT implement the
--          related XCMI System Admin MIB).

xcmHrAdminDeviceOperationTypes OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The root of all host resources admin device operation types
        defined in the Host Resources Extensions TC.

        Usage:  The following OIDs support access control for the simple
        device admin operations defined in 'XcmHrDevMgmtCommandRequest'
        and used in 'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB,
        via 'xcmSec[Master|Policy]VerbTypeOID' in the XCMI Security MIB,
        WITHOUT requiring implementation of the XCMI System Admin MIB."
    REFERENCE
        "See:   'xcmSec[Master|Policy]VerbTypeOID' in
                XCMI Security MIB."
    ::= { xcmHrTC 4 }

xcmHrAdminDeviceNone            OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 1 }
xcmHrAdminDeviceStartup         OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 2 }
xcmHrAdminDeviceResetWarning    OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 3 }
xcmHrAdminDeviceTest            OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 4 }
xcmHrAdminDeviceShutdown        OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 5 }
xcmHrAdminDeviceQuiesce         OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 6 }
xcmHrAdminDeviceResetCounters   OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 7 }
xcmHrAdminDeviceResetWarm       OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 8 }
xcmHrAdminDeviceResetCold       OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 9 }
xcmHrAdminDeviceResetFactory    OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 10 }
xcmHrAdminDeviceFlushInput      OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 11 }
xcmHrAdminDeviceFlushOutput     OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 12 }
xcmHrAdminDeviceFlushInOut      OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 13 }

XCMI Working Group  File 10hosttc               [Page 48]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

xcmHrAdminDeviceManage          OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 14 }
xcmHrAdminDeviceRefresh         OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 15 }
xcmHrAdminDeviceWarmUp          OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 16 }
xcmHrAdminDeviceCoolDown        OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 17 }
xcmHrAdminDeviceEnergySave      OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 18 }
xcmHrAdminDeviceWakeUp          OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 19 }
xcmHrAdminDevicePowerToReady    OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 20 }
xcmHrAdminDevicePowerToStandby  OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 21 }
xcmHrAdminDevicePowerToSleep    OBJECT IDENTIFIER
    ::= { xcmHrAdminDeviceOperationTypes 22 }

--
--          The Host Resources Extensions (HRX) TC
--
--          Textual Conventions

XcmHrDevCalendarDayOfWeek ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The day of week when the command specified in a conceptual
        row in the 'xcmHrDevCalendarTable' SHALL be invoked."
    SYNTAX      INTEGER {
        monday(1),
        tuesday(2),
        wednesday(3),
        thursday(4),
        friday(5),
        saturday(6),
        sunday(7),
        everyDay(8),                    -- monday through sunday
        businessOpenDay(9),             -- site specific
        businessClosedDay(10),          -- site specific
        businessHoliday(11)             -- site specific
    }

XcmHrDevCalendarTimeOfDay ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The time of day when the command specified in a conceptual
        row in the 'xcmHrDevCalendarTable' SHALL be invoked, specified
        as hours (0..23) multiplied by 100, added to minutes (0..59),
        added to a constant bias of 10000 (avoids an index value of zero
        in 'xcmHrDevCalendarTimeOfDay')."
    SYNTAX      INTEGER (10000..12359)



XCMI Working Group  File 10hosttc               [Page 49]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

XcmHrDevDetailType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The type of the device detail information specified
        in this conceptual row in the 'xcmHrDevDetailTable'.

        Usage:  Conforming management stations and management agents
        SHALL implement specified semantics for device detail types."

--      -   Device other/unknown details
--    * 'other'
--    * 'unknown'
--    
--      -   Device general info
--    * 'deviceName'
--      - device administrative name in directory (primary name)
--      - (same usage as 'xcmCOSpecialName' in XCMI Comms Config TC)
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCOInternetDNS')
--      - data - '...ValueString'
--      - (eg, 'showstopper.sample.com')
--      - see - 'xcmCOSpecialName' in XCMI Comms Config TC
--      - see - 'deviceAlias' in XCMI HRX TC
--      - see - 'xcmHrDevInfoName' in XCMI HRX MIB
--      - see - DPA-1 9.4.1 'Printer-name'
--      - see - DPA-1 9.5.1 'Server-name'
--    * 'deviceAlias'
--      - device administrative alias in directory (alternate name)
--      - (same usage as 'xcmCOSpecialName' in XCMI Comms Config TC)
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCOInternetDNS')
--      - data - '...ValueString'
--      - (eg, 'LaserRat')
--      - see - 'xcmCOSpecialName' in XCMI Comms Config TC
--      - see - 'deviceName' in XCMI HRX TC
--      - see - DPA-1 9.4.2 'Printer-name-aliases'
--      - see - DPA-1 9.5.2 'Server-name-aliases'
--    * 'deviceType'
--      - device type
--      - type - (OBJECT IDENTIFIER)
--      - data - '...ValueOID'
--      - (eg, 'hrDevicePrinter')
--      - see - 'hrDeviceType' in IETF HR MIB
--      - see - 'Usage of hrDeviceType and hrDeviceDescr' section of
--      - 'XCMI Supplement to IETF Host Resources MIB' in XCMI HRX TC
--    * 'deviceDescription'
--      - device description
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'Xerox DocuCentre 230 ST v1.0 - Printer')
--      - see - 'hrDeviceDescr' in IETF HR MIB
--      - see - 'Usage of hrDeviceType and hrDeviceDescr' section of

XCMI Working Group  File 10hosttc               [Page 50]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - 'XCMI Supplement to IETF Host Resources MIB' in XCMI HRX TC
--    * 'deviceID'
--      - device (product) ID
--      - type - (ProductID)
--      - data - '...ValueOID'
--      - (eg, 'xcmPidDC230STV1')
--      - see - 'ProductID' and 'hrDeviceID' in IETF HR MIB
--      - see - 'IETF HR DeviceTable' section of
--      - 'XCMI Supplement to IETF Host Resources MIB' in XCMI HRX TC
--    * 'deviceTree'
--      - device tree prefix to name/alias in directory
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCONetwareNDS')
--      - data - '...ValueString'
--      - (MAY also appear in 'deviceName')
--    * 'deviceContext'
--      - device context prefix to name/alias in directory
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCONetwareNDS')
--      - data - '...ValueString'
--      - (MAY also appear in 'deviceName')
--    * 'deviceManufacturer'
--      - device manufacturer (or OEM) name
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - compare - 'hrDeviceDescr' in IETF HR MIB
--    * 'deviceModel'
--      - device model (alphanumeric)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.4 'Printer-model'
--      - compare - 'hrDeviceDescr' in IETF HR MIB
--    * 'deviceSerialNumber'
--      - device serial number
--      - see - 'xcmHrDevInfoSerialNumber' in XCMI HRX MIB
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--    * 'deviceVendor'
--      - device vendor (to customer)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - compare - 'hrDeviceDescr' in IETF HR MIB
--    * 'deviceVersion'
--      - device version (alphanumeric)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - compare - 'hrDeviceDescr' in IETF HR MIB
--
--      -   Device service info
--    * 'deviceServiceByCustomer'
--      - device serviced by customer (rather than vendor)
--      - type - (TruthValue)

XCMI Working Group  File 10hosttc               [Page 51]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - data - '...ValueInteger'
--      - 'true' = serviced by customer
--      - 'false' = serviced by vendor
--    * 'deviceReplaceByCustomer'
--      - device replaced by customer (rather than vendor)
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - 'true' = replaced by customer
--      - 'false' = replaced by vendor
--    * 'deviceServicePlanName'
--      - device service plan name
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'Goldspot77')
--    * deviceServicePlanPassword'
--      - device service plan password (protected/encrypted)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'EA123456')
--    * 'deviceReplaceByWarranty'
--      - device replaced by warranty (rather than at end-of-life)
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - 'true' = replaced by warranty (by some date or usage limit)
--      - 'false' = replaced at end-of-life
--
--      -   Device lifetime usage and limits
--      -   (several usage counters MAY be defined for a single device)
--      -   (several usage limits MAY be defined for a single counter)
--      -   (usage counter and usage limit groups are defined as sharing
--      -   the same value of 'xcmHrDevDetailIndex')
--    * 'deviceLifetimeUsage'
--      - device lifetime usage counter (MAY be multi-valued)
--      - (SHALL NOT be remotely reset, unlike 'deviceAccountingUsage')
--      - type - (Counter32)
--      - subtype - '...ValueString' (XcmGenMessageMapStringLabel)
--      - and (optional) trailing description after whitespace
--      - data - '...ValueInteger'
--      - (eg, monochrome and color page counters)
--      - note - SHOULD be subtyped by well-formed Xerox message
--      - string label of the 'XcmGenMessageMapStringLabel' syntax
--      - defined in the XCMI General TC (06gentc)
--      - for example:
--      - 'xs-iso-101715-mediaSize-na-letter'
--      -   - counts any DPA media size (w/out type/color)
--      - 'xs-ietf-rfc2911-media-iso-a4-...'
--      -   - counts any IETF IPP 'media' (w/ size, type, or color)
--      - 'xs-xcmi-40jobtc-XcmJMImpsCountType-blackAndWhiteCount'
--      -   - counts monochrome impressions
--      - 'xs-xcmi-40jobtc-XcmJMImpsCountType-highlightColorCount'
--      -   - counts highlight color impressions
--    * 'deviceReorderLifetimeLimit'
--      - device reorder at limit (MAY be multi-valued)
--      - type - (Cardinal32)

XCMI Working Group  File 10hosttc               [Page 52]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - subtype - see parallel 'deviceLifetimeUsage'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'xcmHrDevDetailUnit' units
--      - zero = no limit specified
--    * 'deviceWarningLifetimeLimit'
--      - warn device user at usage limit (MAY be multi-valued)
--      - type - (Cardinal32)
--      - subtype - see parallel 'deviceLifetimeUsage'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'xcmHrDevDetailUnit' units
--      - zero = no limit specified
--    * 'deviceReplaceLifetimeLimit'
--      - replace device at usage limit (MAY be multi-valued)
--      - type - (Cardinal32)
--      - subtype - see parallel 'deviceLifetimeUsage'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'xcmHrDevDetailUnit' units
--      - zero = no limit specified
--    * 'deviceMaximumLifetimeLimit'
--      - stop device at usage limit (MAY be multi-valued)
--      - type - (Cardinal32)
--      - subtype - see parallel 'deviceLifetimeUsage'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'xcmHrDevDetailUnit' units
--      - zero = no limit specified
--
--      -   Device message to user time remaining
--      -   (estimated dates when messages will be sent to the user)
--      -   (estimated by the device, based on current rate of usage)
--    * 'deviceDaysUntilReorderMsg'
--      - days left until reorder msg (estimated from rate of usage)
--      - type - (Cardinal32) days
--      - data - '...ValueInteger'
--    * 'deviceDaysUntilWarningMsg'
--      - days left until warning msg (estimated from rate of usage)
--      - type - (Cardinal32) days
--      - data - '...ValueInteger'
--    * 'deviceDaysUntilReplaceMsg'
--      - days left until replace msg (estimated from rate of usage)
--      - type - (Cardinal32) days
--      - data - '...ValueInteger'
--    * 'deviceDaysUntilMaximumMsg'
--      - days left until stop msg (estimated from rate of usage)
--      - type - (Cardinal32) days
--      - data - '...ValueInteger'
--    * 'deviceLifetimeMsgDisplay'
--      - where to send lifetime msgs to user
--      - type - (Cardinal32) local enum below
--      - data - '...ValueInteger'
--      - '0' = none (no msg sent)
--      - '1' = local device UI only
--      - '2' = remote clients only
--      - '3' = both (local and remote)
--

XCMI Working Group  File 10hosttc               [Page 53]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      -   Device accounting usage
--    * 'deviceAccountingUsage'
--      - device accounting usage counter (MAY be multi-valued)
--      - (MAY be remotely reset, unlike 'deviceLifetimeUsage')
--      - type - (Counter32)
--      - subtype - '...ValueString' (XcmGenMessageMapStringLabel)
--      - and (optional) trailing description after whitespace
--      - data - '...ValueInteger'
--      - (eg, monochrome and color page counters)
--      - see - 'deviceLifetimeUsage' (which is NOT reset remotely)
--      - note - SHOULD be subtyped by a well-formed Xerox message
--      - string label of the 'XcmGenMessageMapStringLabel' syntax
--      - defined in the XCMI General TC (06gentc)
--      - for example:
--      - 'xs-iso-101715-mediaSize-na-letter'
--      -   - counts any DPA media size (w/out type/color)
--      - 'xs-ietf-rfc2911-media-iso-a4-...'
--      -   - counts any IETF IPP 'media' (w/ size, type, or color)
--      - 'xs-xcmi-40jobtc-XcmJMImpsCountType-blackAndWhiteCount'
--      -   - counts monochrome impressions
--      - 'xs-xcmi-40jobtc-XcmJMImpsCountType-highlightColorCount'
--      -   - counts highlight color impressions
--
--      -   Device message to user and reorder dates
--      -   (fixed dates when messages will be sent to the user)
--      -   (fixed by system administrator)
--    * 'deviceReorderOnDate'
--      - reorder device on fixed date (and send message to user)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceWarningOnDate'
--      - warn device user on fixed date
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceReplaceOnDate'
--      - replace device on fixed date (and send message to user)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceMaximumOnDate'
--      - stop device on fixed date (and send message to user)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--
--      -   Device lifetime errors and warnings
--      -   (several error counters MAY be defined for a single device)
--      -   (one error limit MAY be defined for a single error counter)
--      -   (error counter and error limit pairs are defined as sharing
--      -   the same value of 'xcmHrDevDetailIndex')
--    * 'deviceLifetimeErrorCount'
--      - device lifetime error counter (MAY be multi-valued)
--      - type - (Counter32)
--      - subtype - '...ValueString' (XcmGenMessageMapStringLabel)
--      - and (optional) trailing description after whitespace
--      - data - '...ValueInteger'

XCMI Working Group  File 10hosttc               [Page 54]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - note - SHOULD be subtyped by a well-formed Xerox message
--      - string label of the 'XcmGenMessageMapStringLabel' syntax
--      - defined in the XCMI General TC (06gentc)
--      - for example:
--      - 'xs-ietf-rfc1759-prtAlertCode-jam'
--      -   - paper jam - see 'prtAlertCode' in Printer MIB
--    * 'deviceLifetimeErrorLimit'
--      - device lifetime error limit (MAY be multi-valued)
--      - type - (Cardinal32)
--      - subtype - see parallel 'deviceLifetimeErrorCount'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'deviceLifetimeErrorCount' units
--      - zero = no limit specified
--      - note - product-unique error handling at this limit
--    * 'deviceLifetimeWarningCount'
--      - device lifetime warning counter (MAY be multi-valued)
--      - type - (Counter32)
--      - subtype - '...ValueString' (XcmGenMessageMapStringLabel)
--      - and (optional) trailing description after whitespace
--      - data - '...ValueInteger'
--      - note - SHOULD be subtyped by a well-formed Xerox message
--      - string label of the 'XcmGenMessageMapStringLabel' syntax
--      - defined in the XCMI General TC (06gentc)
--      - for example:
--      - 'xs-ietf-rfc1759-prtAlertCode-inputMediaSupplyLow'
--      -   - paper low - see 'prtAlertCode' in Printer MIB
--    * 'deviceLifetimeWarningLimit'
--      - device lifetime warning limit (MAY be multi-valued)
--      - type - (Cardinal32)
--      - subtype - see parallel 'deviceLifetimeWarningCount'
--      - data - '...ValueInteger'
--      - positive integer = limit in 'deviceLifetimeWarningCount' units
--      - zero = no limit specified
--      - note - product-unique warning handling at this limit
--
--      -   Device message to user triggers
--      -   (actual days before an estimated limit date, when messages
--      -   SHALL be sent to users)
--      -   (while the 'triggers' are in terms of actual days, the
--      -   determination of the [future] limit reached date is based
--      -   on estimation by the device from current rate of usage)
--    * 'deviceTriggerDaysForReorder'
--      - days to reorder msg trigger (send before reorder limit)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceTriggerDaysForWarning'
--      - days to warning msg trigger (send before warning limit)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceTriggerDaysForReplace'
--      - days to replace msg trigger (send before replace limit)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceTriggerDaysForMaximum'

XCMI Working Group  File 10hosttc               [Page 55]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - days to stop msg trigger (send before stop limit)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--
--      -   Device message to user dates actually sent
--      -   (log of dates when messages were actually sent to user,
--      -   based on estimates, actual limits, actual dates, etc)
--    * 'deviceReorderMsgSentDate'
--      - date of reorder msg to user (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * deviceWarningMsgSentDate'
--      - date of warning msg to user (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceReplaceMsgSentDate'
--      - date of replace msg to user (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceMaximumMsgSentDate'
--      - date of maximum msg to user (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--
--      -   Device reorder and replace actual dates
--      -   (log of dates when reorder and replacement were actually
--      -   done for this device)
--    * 'deviceReorderToVendorDate'
--      - date reorder to vendor sent (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceReorderConfirmDate'
--      - date reorder confirm received (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceReplaceDate'
--      - date of replacement (MAY be multi-valued)
--      - type - (DateAndTime)
--      - data - '...ValueString'
--    * 'deviceReplaceSystemUsage'
--      - system usage at date of replacement (MAY be multi-valued)
--      - type - (Counter32) some usage counter
--      - (eg, 'total marked images')
--      - date - '...ValueInteger'
--    * 'deviceReplaceWithGeneric'
--      - device MAY be replaced with generic (third-party) part
--      - (MAY indicate that a package is installed to support generics)
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - 'true' = device MAY be replaced with a generic part
--      - 'false' = device MAY NOT be replaced with a generic part
--
--      -   Device help info (contact info)
--      - NOTE - Device Help group is DEPRECATED (as of XCMI v4.1)

XCMI Working Group  File 10hosttc               [Page 56]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - The following device details SHOULD be used instead
--    * 'deviceHelpName'
--      - device help person name and role
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCONetwareBindery')
--      - data - '...ValueString'
--      - (eg, 'Joe Hampton')
--      - role - '...ValueInteger' (XcmSecUserRole in XCMI Security TC)
--      - (eg, 'systemOperator')
--    * 'deviceHelpAddress'
--      - device help person address and role
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (protocol in XCMI Comms Config TC)
--      - (eg, 'xcmCOOsiwanFax')
--      - data - '...ValueString'
--      - (eg, '1-800-232-7979')
--      - role - '...ValueInteger' (XcmSecUserRole in XCMI Security TC)
--      - (eg, 'systemOperator')
--    * 'deviceHelpDescription'
--      - device help person description
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'has keys to supplies')
--    * 'deviceHelpLocation'
--      - device help person physical location
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, '3rd floor lobby')
--      - see - DPA-1 9.4.3 'Printer-locations'
--    * 'deviceHelpURI'
--      - device help person URI (Uniform Resource Identifier)
--      - (same usage as 'xcmCOInternetHTTPAddressURI' in XCMI CC TC)
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (protocol in XCMI Comms Config TC)
--      - (eg, 'xcmCOInternetHTTP' (HTTP))
--      - data - '...ValueString'
--      - (eg, 'http://www.foo.com' (HTTP))
--      - see - 'xcmCOInternetHTTPAddressURI' in XCMI Comms Config TC
--      - see - Generic URI Syntax (RFC 2396)
--      - compare - 'system[Protocol|ProtocolDetail' in XCMI Svc Mon TC
--      - compare - 'systemURI' in XCMI Svc Mon TC
--
--      -   Device supported and ready info
--      -   (from ISO 10175 DPA-1 Section 9.4 'Printer Object')
--      -   (see 9.4.74 'Common Printer and Server object attributes')
--    * 'deviceTranslatorSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.74.5 'Translators-supported'
--    * 'deviceTranslatorReady'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.74.6 'Translators-ready'

XCMI Working Group  File 10hosttc               [Page 57]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'deviceInitialValueJobSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.74.13 'Initial-value-jobs-supported'
--    * 'deviceInitialValueDocSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.74.14 'Initial-value-documents-supported'
--    * 'deviceMultipleDocSupport'
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.74.3 'Multiple-documents-supported'
--    * 'deviceCancelDocSupport'
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.74.4 'Cancel-individual-documents-supported'
--    * 'deviceForeignJobsVisible'
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.74.15 'Are-foreign-jobs-visible'
--    * 'deviceInitialValueJobDefault'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.12 'Printer-initial-value-job'
--    * 'deviceInitialValueDocDefault'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.13 'Printer-initial-value-document'
--    * 'deviceInputMaxSpeedTrafficUnit'
--      - traffic unit of numerator of device input max speed
--      - type - (XcmHrDevTrafficUnit)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceInputMaxSpeedTimeUnit'
--      - time unit of divisor of device input max speed
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceInputMaxSpeed'
--      - device input max speed
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceOutputMaxSpeedTrafficUnit'
--      - traffic unit of numerator of device output max speed
--      - type - (XcmHrDevTrafficUnit)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceOutputMaxSpeedTimeUnit'
--      - time unit of divisor of device output max speed
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceOutputMaxSpeed'

XCMI Working Group  File 10hosttc               [Page 58]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - device output max speed
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.7 'Maximum-printer-speed'
--    * 'deviceFeedResolutionSupport'
--      - type - (Cardinal32) DPI (dots per inch)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.8 'Printer-resolutions-supported'
--    * 'deviceXFeedResolutionSupport'
--      - type - (Cardinal32) DPI (dots per inch)
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.8 'Printer-resolutions-supported'
--    * 'deviceSchedulerSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.63 'Schedulers-supported'
--    * 'deviceSchedulerReady'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.64 'Scheduler-ready'
--
--      -   Device supported and ready device name info (list)
--    * 'devicePhysicalNameSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.10 'Printer-associated-printers'
--      - see - DPA-1 9.5.6 'Physical-printers-supported' (servers)
--    * 'devicePhysicalNameReady'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.11 'Printers-ready'
--      - see - DPA-1 9.5.7 'Physical-printers-ready' (servers)
--    * 'deviceLogicalNameSupport'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.10 'Printer-associated-printers'
--      - see - DPA-1 9.5.8 'Logical-printers-supported' (servers)
--    * 'deviceLogicalNameReady'
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - DPA-1 9.4.11 'Printers-ready'
--      - see - DPA-1 9.5.9 'Logical-printers-ready' (servers)
--
--      -   Device supported and ready device index info (list)
--    * 'devicePhysicalIndexSupport'
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.10 'Printer-associated-printers'
--      - see - DPA-1 9.5.6 'Physical-printers-supported' (servers)
--    * 'devicePhysicalIndexReady'
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.11 'Printers-ready'
--      - see - DPA-1 9.5.7 'Physical-printers-ready' (servers)

XCMI Working Group  File 10hosttc               [Page 59]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'deviceLogicalIndexSupport'
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.10 'Printer-associated-printers'
--      - see - DPA-1 9.5.8 'Logical-printers-supported' (servers)
--    * 'deviceLogicalIndexReady'
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.11 'Printers-ready'
--      - see - DPA-1 9.5.9 'Logical-printers-ready' (servers)
--
--      -   Device job service and job history device index info
--    * 'deviceJobServiceDeviceIndex'
--      - device service device index (reference from history device)
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - 'xcmHrDevice...' types in XCMI HRX TC
--    * 'deviceJobHistoryDeviceIndex'
--      - device history device index (reference from service device)
--      - type - (Cardinal32) 'hrDeviceIndex'
--      - data - '...ValueInteger'
--      - see - 'xcmHrDevice...History' types in XCMI HRX TC
--
--      -   Device supported and ready font/resource index info (list)
--    * 'deviceFontIndexSupport'
--      - type - (Cardinal32) 'xcmFontIndex' in XCMI Resources MIB
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.19 'Fonts-supported'
--    * 'deviceFontIndexReady'
--      - type - (Cardinal32) 'xcmFontIndex' in XCMI Resources MIB
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.20 'Fonts-ready'
--    * 'deviceResourceIndexSupport'
--      - type - (Cardinal32) 'xcmRsrcIndex' in XCMI Resources MIB
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.21 'Resources-supported'
--    * 'deviceResourceIndexReady'
--      - type - (Cardinal32) 'xcmRsrcIndex' in XCMI Resources MIB
--      - data - '...ValueInteger'
--      - see - DPA-1 9.4.22 'Resources-ready'
--
--      -   Device power management
--    * 'devicePowerModeName'
--      - device power mode administrative name (locale dependent)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--    * 'devicePowerModeType'
--      - device power mode type (locale independent)
--      - type - (XcmHrDevPowerModeType)
--      - data - '...ValueInteger'
--    * 'devicePowerModeDescription'
--      - device power mode description (locale dependent)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'

XCMI Working Group  File 10hosttc               [Page 60]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'devicePowerModeSupport'
--      - device power mode support (MAY be used to disable a mode)
--      - type - (PresentOnOff)
--      - data - '...ValueInteger'
--    * 'devicePowerTimeUnit'
--      - device power mode transition time unit (defaults to seconds)
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueString'
--    * 'devicePowerWarmerSupport'
--      - device power mode to warmer mode transition support
--      - type - (PresentOnOff)
--      - data - '...ValueInteger'
--    * 'devicePowerCoolerSupport'
--      - device power mode to cooler mode transition support
--      - type - (PresentOnOff)
--      - data - '...ValueInteger'
--    * 'devicePowerWarmerDelay'
--      - device power mode to warmer mode transition delay
--      - (delay after trigger event until transition begins)
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--    * 'devicePowerWarmerDuration'
--      - device power mode to warmer mode transition duration
--      - (duration after transition begins until transition completes)
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--    * 'devicePowerCoolerDelay'
--      - device power mode to cooler mode transition delay
--      - (delay after trigger event until transition begins)
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--    * 'devicePowerCoolerDuration'
--      - device power mode to cooler mode transition duration
--      - (duration after transition begins until transition completes)
--      - type - (XcmHrDevPowerTimeUnit)
--      - data - '...ValueInteger'
--    * 'devicePowerWarmerTrigger'
--      - device warmer mode trigger description
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--    * 'devicePowerCoolerTrigger'
--      - device cooler mode trigger description
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--    * 'deviceNextWarmerModeIndex'
--      - device next warmer mode pointer (in device details)
--      - type - (Cardinal32) 'xcmHrDevDetailIndex'
--      - data - '...ValueInteger'
--    * 'deviceNextCoolerModeIndex'
--      - device next cooler mode pointer (in device details)
--      - type - (Cardinal32) 'xcmHrDevDetailIndex'
--      - data - '...ValueInteger'
--    * 'deviceEnergyStarSuspendMode'
--      - device (in device details)

XCMI Working Group  File 10hosttc               [Page 61]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - type - (Cardinal32) 'xcmHrDevDetailIndex'
--      - data - '...ValueInteger'
--
--      -   Device 'hrDeviceProcessor' details
--    * 'deviceProcessorFrwID'
--      - device firmware ID
--      - type - (ProductID) 'hrProcessorFrwID'
--      - data - '...ValueOID'
--
--      -   Device 'hrDeviceNetwork' details
--    * 'deviceNetworkIfIndex'
--      - device interface index
--      - type - (Cardinal32) 'hrNetworkIfIndex'
--      - data - '...ValueInteger'
--
--      -   Device 'hrDeviceDiskStorage' details
--    * 'deviceDiskStorageAccess'
--      - device disk access
--      - type - (Cardinal32) 'hrDiskStorageAccess'
--      - data - '...ValueInteger'
--    * 'deviceDiskStorageMedia'
--      - device disk media
--      - type - (Cardinal32) 'hrDiskStorageMedia'
--      - data - '...ValueInteger'
--    * 'deviceDiskStorageRemovable'
--      - device removable
--      - type - (Cardinal32) 'hrDiskStorageRemoveble' ('removable')
--      - data - '...ValueInteger'
--    * 'deviceDiskStorageCapacity'
--      - device capacity
--      - type - (Cardinal32) 'hrDiskStorageCapacity'
--      - data - '...ValueInteger'
--
--    * 'deviceMemorySize'
--      - type - (Integer32)
--      - subtype - '. . .ValueString' 
--      - (used to describe the memory and units, eg. 
--         "Embedded Fax Card Memory (Mb)")
--      - data - '. . .ValueInteger'
--
--    * 'deviceConfigurationSetting' 
--      - (used for configuration settings and device defaults) 
--      - UnitClass = classGenOptionValueSyntax(3) 
--      - DetailUnit = integerNumber(3), integerEnum(5), 
--                     integerTruthValue(8), oidObject (9), 
--                     stringDisplay(12) or stringLocalization(13)
--      - data - '. . .ValueInteger' or 
--               '. . .ValueOID' or 
--               '. . .ValueString' 
--               depending on the DetailUnit 
--      - usage: xcmHrDevDetailType or xcmHrDetailType 
--      - when used with xcmHrDevDetailType subtype - '. . .ValueString'
--        can be used as a description when the value is 
--                '. . .ValueInteger' or 

XCMI Working Group  File 10hosttc               [Page 62]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--                '. . .ValueOID' 
--       - when used with xcmHrDetailType, xcmHrDetailDescription 
--         is used for the description 
-- 
--    * 'deviceTimezone'
--      - device timezone
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - where ValueString is one of the following:
--      - ValueString            Typical Display String
--      - - - - - - -            - - - - - - - - - - - - 
--      - Pacific/Pago_Pago     (GMT -11:00) Midway Island, Niue, Samoa
--      - America/Adak          (GMT -10:00) Adak
--      - Pacific/Honolulu      (GMT -10:00) Cook Islands, Hawaii, Tahit
--      - Pacific/Marquesas     (GMT -09:30) Marquesas Islands
--      - America/Anchorage     (GMT -09:00) Alaska
--      - Pacific/Gambier       (GMT -09:00) Gambier Islands
--      - America/Dawson        (GMT -08:00) Pacific Time (US & Canada)
--      - Pacific/Pitcairn      (GMT -08:00) Pitcairn Islands
--      - America/Tijuana       (GMT -08:00) Tijuana
--      - America/Hermosillo    (GMT -07:00) Arizona, Dawson Creek, 
--      -                                     Sonora
--      - America/Chihuahua     (GMT -07:00) Chihuahhua, Mazatlan
--      - America/Cambridge_Bay (GMT -07:00) Mountain Time (US & Canada)
--      - America/Cancun        (GMT -06:00) Cancun, Mexico City, 
--      -                                     Monterrey
--      - America/Belize        (GMT -06:00) Central America
--      - America/Rainy_River   (GMT -06:00) Central Time (US & Canada)
--      - Pacific/Easter        (GMT -06:00) Easter Island
--      - Pacific/Galapagos     (GMT -06:00) Galapagos Islands
--      - America/Regina        (GMT -06:00) Saskatchewan
--      - America/Atikokan      (GMT -05:00) Atikokan, Resolute
--      - America/Bogota        (GMT -05:00) Bogota, Lima, Panama, Quito
--      - America/Cayman        (GMT -05:00) Cayman Islands, Jamaica, 
--      -                                     Port-au-Prince
--      - America/Detroit       (GMT -05:00) Eastern Time (US & Canada)
--      - America/Grand_Turk    (GMT -05:00) Grand Turk
--      - America/Havana        (GMT -05:00) Havana
--      - America/Caracas       (GMT -04:30) Caracas
--      - America/Asuncion      (GMT -04:00) Asuncion
--      - America/Glace_Bay     (GMT -04:00) Atlantic Time (Canada)
--      - Atlantic/Bermuda      (GMT -04:00) Bermuda
--      - America/Blanc-Sablon  (GMT -04:00) Blanc-Sablon
--      - America/Anguilla      (GMT -04:00) Caribbean Islands
--      - America/Campo_Grande  (GMT -04:00) Cuiaba
--      - America/Boa_Vista     (GMT -04:00) Georgetown, La Paz, Manaus
--      - Antarctica/Palmer     (GMT -04:00) Palmer Archipelago, Santiag
--      - Atlantic/Stanley      (GMT -04:00) Stanley
--      - America/Thule         (GMT -04:00) Thule
--      - America/St_Johns      (GMT -03:30) St. John's
--      - America/Araguaina     (GMT -03:00) Brasilia, Cayenne, 
--      -                                     Paramaribo
--      - America/Argentina/Catamarca   (GMT -03:00) Buenos Aires
--      - America/Godthab       (GMT -03:00) Greenland

XCMI Working Group  File 10hosttc               [Page 63]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - America/Miquelon      (GMT -03:00) Miquelon
--      - America/Montevideo    (GMT -03:00) Montevideo
--      - Antarctica/Rothera    (GMT -03:00) Rothera
--      - America/Noronha       (GMT -02:00) Noronha
--      - Atlantic/South_Georgia(GMT -02:00) South Georgia Island
--      - Atlantic/Azores       (GMT -01:00) Azores, Scoresbysund
--      - Atlantic/Cape_Verde   (GMT -01:00) Cape Verde
--      - GMT+0                 Greenwich Mean Time:  DST disabled
--      - America/Danmarkshavn. (GMT+0)
--      - Africa/Abidjan        (GMT 0:00) Accra, Bamako, Dakar, 
--      -                                     Nouakchott
--      - Africa/Casablanca     (GMT) Casablanca
--      - Europe/Dublin         (GMT) Dublin, Edinburgh, Lisbon, London
--      - Atlantic/Reykjavik    (GMT) Reykjavik
--      - Africa/Algiers        (GMT +01:00) Algiers, Douala, 
--      -                                     Libreville, Luanda
--      - Europe/Amsterdam      (GMT +01:00) Amsterdam, Berlin, Rome, 
--      -                                     Stockholm, Vienna
--      - Europe/Belgrade       (GMT +01:00) Belgrade, Bratislava, 
--      -                                     Budapest, Prague
--      - Europe/Brussels       (GMT +01:00) Brussels, Copenhagen, 
--      -                                     Madrid, Paris
--      - Europe/Warsaw         (GMT +01:00) Sarajevo, Skopje, Warsaw, 
--      -                                     Zagreb
--      - Africa/Tunis          (GMT +01:00) Tunis
--      - Africa/Windhoek       (GMT +01:00) Windhoek
--      - Asia/Amman            (GMT +02:00) Amman
--      - Europe/Athens         (GMT +02:00) Athens, Bucharest, Istanbul
--      - Asia/Beirut           (GMT +02:00) Beirut
--      - Africa/Cairo          (GMT +02:00) Cairo
--      - Asia/Damascus         (GMT +02:00) Damascus
--      - Africa/Harare         (GMT +02:00) Harare, Johannesburg, 
--      -                                     Kinshasa, Tripoli
--      - Europe/Helsinki       (GMT +02:00) Helsinki, Kiev, Riga, Sofia
--      - Asia/Jerusalem        (GMT +02:00) Jerusalem
--      - Europe/Kaliningrad    (GMT +02:00) Kaliningrad, Minsk
--      - Asia/Nicosia          (GMT +02:00) Nicosia
--      - Asia/Gaza             (GMT +02:00) Palestine
--      - Africa/Addis_Ababa    (GMT +03:00) Addis Ababa, Khartoum, 
--      -                                     Mogadishu, Nairobi
--      - Asia/Baghdad          (GMT +03:00) Aden, Baghdad, Qatar, Riyad
--      - Indian/Antananarivo   (GMT +03:00) Antanarivo, Comoro Islands,
--      -                                     Mayotte
--      - Europe/Moscow         (GMT +03:00) Moscow
--      - Antarctica/Syowa      (GMT +03:00) Syowa
--      - Asia/Tehran           (GMT +03:30) Tehran
--      - Asia/Baku             (GMT +04:00) Baku
--      - Asia/Dubai            (GMT +04:00) Dubai, Muscat, Tbilsi
--      - Indian/Mahe           (GMT +04:00) Mahe, Reunion
--      - Indian/Mauritius      (GMT +04:00) Mauritius
--      - Europe/Samara         (GMT +04:00) Samara
--      - Asia/Yerevan          (GMT +04:00) Yerevan
--      - Asia/Kabul            (GMT +04:30) Kabul
--      - Asia/Aqtau            (GMT +05:00) Aqtau, Aqtobe, Ashgabat, 

XCMI Working Group  File 10hosttc               [Page 64]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      -                                     Samarkand
--      - Asia/Yekaterinburg    (GMT +05:00) Ekaterinburg
--      - Asia/Karachi          (GMT +05:00) Karachi
--      - Indian/Kerguelen      (GMT +05:00) Kerguelen, Maldives
--      - Asia/Colombo          (GMT +05:30) Colombo, Kolkata
--      - Asia/Katmandu         (GMT +05:45) Kathmandu
--      - Asia/Almaty           (GMT +06:00) Almaty, Bishkek, Dhaka, 
--      -                                     Thimphu
--      - Indian/Chagos         (GMT +06:00) Chagos
--      - Antarctica/Mawson     (GMT +06:00) Mawson, Vostok
--      - Asia/Novosibirsk      (GMT +06:00) Novosibirsk, Omsk
--      - Indian/Cocos          (GMT +06:30) Cocos Islands
--      - Asia/Rangoon          (GMT +06:30) Yangon (Rangoon)
--      - Asia/Bangkok          (GMT +07:00) Bankok, Ho Chi Minh, Hovd, 
--      -                                     Jakarta
--      - Indian/Christmas      (GMT +07:00) Christmas Island
--      - Antarctica/Davis      (GMT +07:00) Davis
--      - Asia/Krasnoyarsk      (GMT +07:00)  Krasnoyarsk
--      - Antarctica/Casey      (GMT +08:00) Casey
--      - Asia/Chongqing        (GMT +08:00) Chongqing, Hong Kong, 
--      -                                     Shanghai
--      - Asia/Irkutsk          (GMT +08:00) Irkutsk
--      - Asia/Kuala_Lumpur     (GMT +08:00) Kuala, Lampur, Makassar, 
--      -                                     Manilla, Singapore
--      - Australia/Perth       (GMT +08:00) Perth
--      - Asia/Taipei           (GMT +08:00) Taipei
--      - Asia/Ulaanbaatar      (GMT +08:00) Ulaan Baatar
--      - Australia/Eucla       (GMT +08:45) Eucla
--      - Asia/Dili             (GMT +09:00) Dili, Jayapura
--      - Pacific/Palau         (GMT +09:00) Palau
--      - Asia/Pyongyang        (GMT +09:00) Pyongyang
--      - Asia/Seoul            (GMT +09:00) Seoul
--      - Asia/Tokyo            (GMT +09:00) Tokyo
--      - Asia/Yakutsk          (GMT +09:00) Yakutsk
--      - Australia/Adelaide    (GMT +09:30) Adelaide
--      - Australia/Darwin      (GMT +09:30) Darwin
--      - Australia/Lindeman    (GMT +10:00) Brisbane, Lindeman
--      - Antarctica/DumontDUrville   (GMT +10:00) Dumont d'Urville
--      - Pacific/Guam          (GMT +10:00) Guam, Port Moresby, Saipan
--      - Australia/Currie      (GMT +10:00) Hobart, Melbourne, Sydney
--      - Asia/Vladivostok      (GMT +10:00) Sakhalin, Vladivostok
--      - Australia/Lord_Howe   (GMT +10:30) Lord Howe Island
--      - Pacific/Efate         (GMT +11:00) Efate, Guadalcanal, Kosrae
--      - Asia/Magadan          (GMT +11:00) Magadan
--      - Pacific/Norfolk       (GMT +11:30) Norfolk Island
--      - Asia/Anadyr           (GMT +12:00) Anadyr, Kamchatka
--      - Pacific/Auckland      (GMT +12:00) Auckland
--      - Pacific/Fiji          (GMT +12:00) Fiji, Marshall Islands
--      - Antarctica/McMurdo    (GMT +12:00) McMurdo
--      - Pacific/Chatham       (GMT +12:45) Chatham
--      - Pacific/Tongatapu     (GMT +13:00) Tongatapu
--      - Pacific/Kiritimati    (GMT +14:00) Kiritimati
--      - Additional strings should be submitted to the XMCI editors as 
--      - needed so they can be added to this list of common strings

XCMI Working Group  File 10hosttc               [Page 65]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - reference: http://en.wikipedia.org/wiki/Zoneinfo
--
--
--    * 'deviceSoundControl'
--      - used to control the device sound feature
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - 'true' = enable device sounds
--      - 'false' = disable device sounds
--
--    * 'deviceLEDControl'
--      - used to control the Emotive LED feature
--      - type - (TruthValue)
--      - data - '...ValueInteger'
--      - 'true' = enable Emotive LED
--      - 'false' = disable Emotive LED
--
--      -   Device job service timeouts
--
--    * 'deviceJobIncompleteTimeout'
--      - device job incomplete timeout
--      - (delay until job with incomplete input is deleted)
--      - type - (Cardinal32) seconds
--      - data - '...ValueInteger'
--      - (zero=none or 1..n seconds)
--      - see - 'xcmCOInternetLPRJobTimeout' in XCMI CC TC
--      - compare - 'systemJobIncompleteTimeout' in XCMI Svc Mon TC
--    * 'deviceJobProgrammingTimeout'
--      - device job programming timeout
--      - (delay until job programming settings are deleted)
--      - type - (Cardinal32) seconds
--      - data - '...ValueInteger'
--      - (zero=none or 1..n seconds)
--      - see - 'deviceJobIncompleteTimeout' above
--      - compare - 'systemJobProgrammingTimeout' in XCMI Svc Mon TC
--    * 'deviceJobHoldDeleteTimeout'
--      - device job hold until delete timeout
--      - (delay until held job is automatically deleted)
--      - type - (Cardinal32) seconds
--      - data - '...ValueInteger'
--      - (zero=none or 1..n seconds)
--      - see - 'deviceJobIncompleteTimeout' above
--      - see - 'jobPause' in 'XcmSimpleJobMgmtOperation' in XCMI SJM TC
--      - compare - 'systemJobHoldDeleteTimeout' in XCMI Svc Mon TC
--    * 'deviceJobPauseResumeTimeout'
--      - device job pause until resume timeout
--      - (delay until paused job is automatically resumed)
--      - type - (Cardinal32) seconds
--      - data - '...ValueInteger'
--      - (zero=none or 1..n seconds)
--      - see - 'deviceJobIncompleteTimeout' above
--      - see - 'jobPause' in 'XcmSimpleJobMgmtOperation' in XCMI SJM TC
--      - compare - 'systemJobPauseResumeTimeout' in XCMI Svc Mon TC
--

XCMI Working Group  File 10hosttc               [Page 66]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      -   Device guest/alien job and log full policies
--    * 'deviceGuestJobPolicy'
--      - device policy for jobs with 'guest' (empty) user/account
--      - type - (XcmSecGuestJobPolicy)
--      - data - '...ValueInteger'
--      - see - 'xcmSecServiceGuestJobPolicy' in XCMI Security MIB
--    * 'deviceAlienJobPolicy'
--      - device policy for jobs with 'alien' (invalid) user/account
--      - type - (XcmSecGuestJobPolicy)
--      - data - '...ValueInteger'
--      - see - 'xcmSecServiceAlienJobPolicy' in XCMI Security MIB
--    * 'deviceEventLogFullPolicy'
--      - device policy for handling event log full conditions
--      - type - (XcmGenLogFullPolicy)
--      - data - '...ValueInteger'
--      - see - 'xcmSecServiceEventLogFullPolicy' in XCMI Security MIB
--      - see - DPA-1 9.1.6.8 'Notification-profile' (events)
--      - see - DPA-1 9.4 'Printer Object attributes' (generic)
--    * 'deviceJobLogFullPolicy'
--      - device policy for handling job log full conditions
--      - type - (XcmGenLogFullPolicy)
--      - data - '...ValueInteger'
--      - see - 'xcmSecServiceJobLogFullPolicy' in XCMI Security MIB
--      - see - DPA-1 9.1.6.9 'Logging-profile' (jobs)
--      - see - DPA-1 9.4 'Printer Object attributes' (generic)
--    * 'deviceRequestLogFullPolicy'
--      - device policy for handling request log full conditions
--      - type - (XcmGenLogFullPolicy)
--      - data - '...ValueInteger'
--      - see - 'xcmSecServiceRequestLogFullPolicy' in XCMI Security MIB
--
--      -   Device model info
--    * 'deviceUniversalProductCode'
--      - device UPC (alphanumeric)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - 'deviceSerialNumber'
--      - see - 'hrDeviceDescr' in IETF HR MIB (RFC 2790)
--    * 'deviceModelName'
--      - device model name (alphanumeric)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - 'deviceModel' and 'deviceDescription'
--      - see - 'hrDeviceDescr' in IETF HR MIB (RFC 2790)
--      - see - section 9.1.3.1.1 of XCMI HRX TC for mapping and terms
--    * 'deviceModelDescription'
--      - device model description (alphanumeric)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - 'deviceModel' and 'deviceDescription'
--      - see - 'hrDeviceDescr' in IETF HR MIB (RFC 2790)
--      - see - section 9.1.3.1.1 of XCMI HRX TC for mapping and terms
--    * 'deviceModelNumber'
--      - device model number (alphanumeric)

XCMI Working Group  File 10hosttc               [Page 67]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - see - 'deviceModel' and 'deviceDescription'
--      - see - 'hrDeviceDescr' in IETF HR MIB (RFC 2790)
--      - see - section 9.1.3.1.1 of XCMI HRX TC for mapping and terms
--    * 'deviceManufacturerURI'
--      - device manufacturer URI (per RFC 2396)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'http://www.xerox.com')
--      - see - 'deviceManufacturer'
--      - see - 'sysContact' in IETF MIB-II (RFC 1213)
--    * 'deviceModelURI'
--      - device model-specific URI (per RFC 2396)
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'http://www.xerox.com/docucentre/470')
--      - see - 'deviceModel'
--      - see - 'sysContact' in IETF MIB-II (RFC 1213)
--
--      - Service Usage Counters
--      -   Counters which can be used by a billing system to adjust
--      -   deviceLifetimeUsage counters.  These counters are set by
--      -   service to reflect the usage of the machine during the 
--      -   service call which should not be billed separately to the
--      -   customer.
--      -   (several usage counters MAY be defined for a single device)
--      -   (usage counter and service usage groups are defined as
--      -   sharing the same value of 'xcmHrDevDetailIndex')
--    * 'deviceServiceUsage'(230)
--      - device lifetime service usage counter (MAY be multi-valued)
--      - type - (Counter32)
--      - subtype - '...ValueString' counter description 
--      - data - '...ValueInteger'
--      - 
--    * 'deviceDeltaServiceUsage'(231)
--      - Delta for the sevice usage counter (MAY be multi-valued)
--      - A SET to xcmHrDevDetailValueInteger.1.231.X will increase
--      - the counter xcmHrDevDetailValueInteger.1.230.X by the amount
--      - of the SET integer.  A GET on the same value will return the
--      - last value set or 0 if there has been no set since reboot.
--      - type - (Counter32)
--      - data - '...ValueInteger'
--      - (eg, monochrome and color page counters)
--      -
--    * 'deviceRolloverValue' (232)
--      - The maximum value of a usage counter before it rolls over.
--      - For example if the counters are 6 digits, then this value 
--      -    should be 999999
--      - If it is a 32 bit integer then this value should be 
--      -     2,147,483,647   (2^31 - 1)
--      - When the counter reaches 999999 (first example) and 1 
--      -     more print is made, then the counter becomes 1 
--      -     (rolls over to 1)

XCMI Working Group  File 10hosttc               [Page 68]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      -
--    * 'deviceCPMenuControl'
--      - type - (TruthValue)
--      - subtype - '... ValueString' (DisplayString) 
--      - Control Panel Menu Element Name (NVT ASCII string)
--      - data - '...ValueInteger'
--      - 'true' = Menu element is enabled, i.e. element available 
--      -          to the user
--      - 'false' = Menu element is disabled, i.e. element not 
--      -           available to the user
--    * 'deviceUsageWarningThreshold'
--      - (warning when it is estimated that the device cannot hold 
--         more than x units)
--      - (example: scan disk cannot hold more than 10 images)
--      - type (XcmHrDevTrafficUnit)
--      - subtype - '. . .DetailUnitClass' (classHrDevTrafficUnit(9))
--      - subtype - '. . .DetailUnit' 
--         (value from XcmHrDevTrafficUnit enumeration)
--      - subtype - '. . .ValueString' (XcmGenMessageMapStringLabel)
--      - (used to describe the use of this element)
--      - data - ' . . . ValueInteger'
--
--      - Supplies Details
--
--    * 'deviceLifetimeAvgCoverage'
--      - device lifetime average toner/ink coverage (MAY be
--        multi-valued)
--      - Use the values of xcmHrDevDetailIndex is table 22 to report
--        average coverage for different types of jobs.
--      - deviceLifetimeAvgCoverage is grouped with deviceLifetimeUsage 
--        and deviceMaximumLifetimeLimit based on xcmHrDevDetailIndex.
--      - (SHALL NOT be remotely reset)
--      - type - (Counter32)
--      - subtype - '...ValueString' A US English description of the 
--        value.
--      - Localization of the string may be done using 
--        xcmGenMessageTextTable.
--      - data - '...ValueInteger' in 1/1000's of a percent, 
--        i.e. 1% = 1000
--
--    * 'deviceLifeRemainingPercent'
--      - device life remaining in percent of supply (MAY be 
--        multi-valued)
--      - (SHALL NOT be remotely reset, unlike 'deviceAccountingUsage')
--      - type - (Counter32)
--      - subtype - '...ValueString' (XcmGenMessageMapStringLabel)
--      - and (optional) trailing description after whitespace
--      - data - '...ValueInteger'
--      - note - SHOULD be subtyped by well-formed Xerox message
--      - string label of the 'XcmGenMessageMapStringLabel' syntax
--
--    * 'deviceRemainingImpressions'
--      - estimated number of impressions remaining until the supply 
--      - is empty

XCMI Working Group  File 10hosttc               [Page 69]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - (SHALL NOT be remotely reset)
--      - type - (Integer32)
--      - subtype - '...UnitClass' classHrDevTrafficUnit(9)
--      - subtype - '...DetailUnit' mediaImpression(27)
--      - subtype - '...ValueString' A US English description of the 
--        value.
--      - data - '...ValueInteger' 
--
--    * 'deviceSuppliesClass'
--      - used for detail attributes of supplies from xcmHrSuppliesTable
--      - similar to prtMarkerSuppliesClass
--      - syntax PrtMarkerSuppliesClassTC
--      - type - integer
--    * 'deviceSupplyUnit'
--      - used for detail attributes of supplies from xcmHrSuppliesTable
--      - similar to prtMarkerSuppliesSupplyUnit
--      - syntax PrtMarkerSuppliesSupplyUnitTC
--      - type - integer
--    * 'deviceSuppliesMaxCapacity'
--      - used for detail attributes of supplies from xcmHrSuppliesTable
--      - similar to prtMarkerSuppliesMaxCapacity
--      - type - integer
--    * 'deviceSuppliesCurrentLevel'
--      - used for detail attributes of supplies from xcmHrSuppliesTable
--      - similar to prtMarkerSuppliesCurrentLevel
--      - type - integer
--
--    * 'deviceInstallDate'
--      - date the device was installed on
--      - type - (DateAndTime)
-- 
--    * 'deviceStatus'
--      - (current status of the device)
--      - (example: black toner needs to be reordered)
--      - type (XcmHrDeviceStatusType) 
--      - data - ' . . . ValueInteger'
--      - subtype -'. . .DetailUnitClass' (classGenOptionValueSyntax(3))
--      - subtype - '. . .DetailUnit' (integerEnum(5))
--      -  (value from XcmHrDeviceStatusType enumeration)
--      - subtype - '. . .ValueString' (XcmGenMessageMapStringLabel)
--      - (used to describe the use of this element)
--
--    * 'deviceSupportContactInfo'
--     - used to capture Xerox support contact information for the
--     -    device
--     - type - (XcmFixedLocaleDisplayString)
--     - data - '...ValueString'
--     - -(0-127 characters, free formed string)
--    * 'deviceServiceContactInfo'
--     - used to capture Xerox service contact information for the
--     -   device
--     - type - (XcmFixedLocaleDisplayString)
--     - data - '...ValueString'
--     - -(0-127 characters, free formed string)

XCMI Working Group  File 10hosttc               [Page 70]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'deviceSuppliesContactInfo'
--     - used to capture Xerox supplies contact information for the
--     -    device
--     - type - (XcmFixedLocaleDisplayString)
--     - data - '...ValueString'
--     - -(0-127 characters, free formed string)

--    * 'deviceFaxCountry'
--      - Fax modem country setting (for example, US, FR, DE)
--      - ISO/IEC 3166:1993 - Codes for the Representation of
--      - Names of Countries
--      - type - (CodedCountry)
--      - data - '...ValueString'
--
--    * 'deviceFaxDialType'
--      - Fax modem dial type
--      - type - (Cardinal32) local enum below
--      - data - '...ValueInteger'
--      - '0' = Tone Dialing
--      - '1' = Pulse Dialing
--
-- Per Tom Friedl 6/17/2014
--
--    * ' deviceGPSLatitude'
--      device location - GPS Latitude Coordinate
--      - type - (XcmHrDevTrafficUnit)
--      - units - 'gpsOneHundredThousandthsOfDegrees(70)'
--      - data - '...ValueInteger'
--      - DISPLAY-HINT of "d-5"
--
-- Per Tom Friedl 6/17/2014
--
--    * ' deviceGPSLongitude'
--      device location - GPS Longitude Coordinate
--      - type - (XcmHrDevTrafficUnit)
--      - units - 'gpsOneHundredThousandthsOfDegrees(70)'
--      - data - '...ValueInteger'
--      - DISPLAY-HINT of "d-5"
--
-- Per Tom Friedl 6/17/2014
--
--    * ' deviceGPSAltitude'
--      device location - GPS Altitude Coordinate
--      - type - (XcmHrDevTrafficUnit)
--      - units - 'LengthFoot(30)' or 'lengthMeter(36)'
--      - data - '...ValueInteger'

--    * ' deviceMeasurementSetting'
--      - device measurement
--      - type - (classGenOptionValueSyntax)
--      - units - 'Inches(1)' or 'Metric(2)'
--      - data - '...ValueInteger'

--    * 'deviceInstallationKeyCSVPrintSubmission'

XCMI Working Group  File 10hosttc               [Page 71]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - CSV Print Submission for Feature Key enablement 
--      - enable/disable a device's ability to accept a CSV Print 
--          submission for Installation Key.
--      - type - (enable/disable)
--      - read/write
--      - data - '...IntegerTruthValue'

--    * 'deviceFeatureInstallationKeyAvailablity'
--      - Feature Key Installation
--      - Used to determine if a feature Installation Key has been 
--          installed on device
--      - type - (available/unavailable)
--      - read-only
--      - data - '...IntegerTruthValue'

--    * 'deviceFeatureInstallationKeyDisablement'
--      - Feature Key Disablement
--      - Used to determine if a Feature may or may not be disabled 
--          once installed
--      - type - (may be disabled/may NOT be disabled)
--      - read-only
--      - data - '...IntegerTruthValue'

--    * 'deviceFeatureInstallationKeyDate'
--      - Feature Key installation date
--      - Used to view when a Feature using an Installation Key was 
--          installed on a device.
--      - type - (FORMAT (in network byte order, 0-11) = <year, 0-65536>
--               <month, 1-12> <day, 1-31> <hour, 0-23> <minutes, 0-59> 
--               <seconds, 0-60> <deci-seconds, 0-9> <direction from UTC
--               "+" or "-"> <hours from UTC,  
--               0-13> <minutes from UTC, 0-59>)
--      - read-only
--      - data - '...StringLocalization'


    REFERENCE
        "See:   'xcmHrDevDetailUnitClass' and
                'xcmHrDevDetailUnit' for syntax of device detail."
    SYNTAX      INTEGER {
        --  Device other/unknown details
        other(1),
        unknown(2),
        --  Device general info
        deviceName(3),
        deviceAlias(4),
        deviceType(5),
        deviceDescription(6),
        deviceID(7),
        deviceTree(8),
        deviceContext(9),
        deviceManufacturer(10),
        deviceModel(11),
        deviceSerialNumber(12),

XCMI Working Group  File 10hosttc               [Page 72]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        deviceVendor(13),
        deviceVersion(14),
        --  Device service info
        deviceServiceByCustomer(15),
        deviceReplaceByCustomer(16),
        deviceServicePlanName(17),
        deviceServicePlanPassword(18),
        deviceReplaceByWarranty(19),
        --  Device lifetime usage and limits
        deviceLifetimeUsage(20),
        deviceReorderLifetimeLimit(21),
        deviceWarningLifetimeLimit(22),
        deviceReplaceLifetimeLimit(23),
        deviceMaximumLifetimeLimit(24),
        --  Device message to user time remaining
        deviceDaysUntilReorderMsg(25),
        deviceDaysUntilWarningMsg(26),
        deviceDaysUntilReplaceMsg(27),
        deviceDaysUntilMaximumMsg(28),
        deviceLifetimeMsgDisplay(29),
        --  Device accounting usage
        deviceAccountingUsage(30),
        --  Device message to user and reorder dates
        deviceReorderOnDate(31),
        deviceWarningOnDate(32),
        deviceReplaceOnDate(33),
        deviceMaximumOnDate(34),
        --  Device lifetime errors and warnings
        deviceLifetimeErrorCount(35),
        deviceLifetimeErrorLimit(36),
        deviceLifetimeWarningCount(37),
        deviceLifetimeWarningLimit(38),
        --  Device message to user triggers
        deviceTriggerDaysForReorder(41),
        deviceTriggerDaysForWarning(42),
        deviceTriggerDaysForReplace(43),
        deviceTriggerDaysForMaximum(44),
        --  Device message to user dates actually sent
        deviceReorderMsgSentDate(51),
        deviceWarningMsgSentDate(52),
        deviceReplaceMsgSentDate(53),
        deviceMaximumMsgSentDate(54),
        --  Device reorder and replace actual dates
        deviceReorderToVendorDate(55),
        deviceReorderConfirmDate(56),
        deviceReplaceDate(57),
        deviceReplaceSystemUsage(58),
        deviceReplaceWithGeneric(59),
        --  Device help info (contact info)
        deviceHelpName(60),
        deviceHelpAddress(61),
        deviceHelpDescription(62),
        deviceHelpLocation(63),
        deviceHelpURI(64),

XCMI Working Group  File 10hosttc               [Page 73]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  Device supported and ready info
        deviceTranslatorSupport(71),
        deviceTranslatorReady(72),
        deviceInitialValueJobSupport(73),
        deviceInitialValueDocSupport(74),
        deviceMultipleDocSupport(75),
        deviceCancelDocSupport(76),
        deviceForeignJobsVisible(77),
        deviceInitialValueJobDefault(78),
        deviceInitialValueDocDefault(79),
        deviceInputMaxSpeedTrafficUnit(80),
        deviceInputMaxSpeedTimeUnit(81),
        deviceInputMaxSpeed(82),
        deviceOutputMaxSpeedTrafficUnit(83),
        deviceOutputMaxSpeedTimeUnit(84),
        deviceOutputMaxSpeed(85),
        deviceFeedResolutionSupport(86),
        deviceXFeedResolutionSupport(87),
        deviceSchedulerSupport(88),
        deviceSchedulerReady(89),
        --  Device supported and ready device name info (list)
        devicePhysicalNameSupport(90),
        devicePhysicalNameReady(91),
        deviceLogicalNameSupport(92),
        deviceLogicalNameReady(93),
        --  Device supported and ready device index info (list)
        devicePhysicalIndexSupport(94),
        devicePhysicalIndexReady(95),
        deviceLogicalIndexSupport(96),
        deviceLogicalIndexReady(97),
        --  Device job service and job history device index info
        deviceJobServiceDeviceIndex(98),
        deviceJobHistoryDeviceIndex(99),
        --  Device supported and ready font/resource index info (list)
        deviceFontIndexSupport(100),
        deviceFontIndexReady(101),
        deviceResourceIndexSupport(102),
        deviceResourceIndexReady(103),
        --  Device power management
        devicePowerModeName(110),
        devicePowerModeType(111),
        devicePowerModeDescription(112),
        devicePowerModeSupport(113),
        devicePowerTimeUnit(114),
        devicePowerWarmerSupport(115),
        devicePowerCoolerSupport(116),
        devicePowerWarmerDelay(117),
        devicePowerWarmerDuration(118),
        devicePowerCoolerDelay(119),
        devicePowerCoolerDuration(120),
        devicePowerWarmerTrigger(121),
        devicePowerCoolerTrigger(122),
        deviceNextWarmerModeIndex(123),
        deviceNextCoolerModeIndex(124),

XCMI Working Group  File 10hosttc               [Page 74]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        -- per Hao Zou Request 8/12/03
        deviceEnergyStarSuspendMode(125),
        --  Device 'hrDeviceProcessor' details
        deviceProcessorFrwID(130),
        --  Device 'hrDeviceNetwork' details
        deviceNetworkIfIndex(140),
        --  Device 'hrDeviceDiskStorage' details
        deviceDiskStorageAccess(160),
        deviceDiskStorageMedia(161),
        deviceDiskStorageRemovable(162),
        deviceDiskStorageCapacity(163),
        -- Device Embedded Fax Card Mb 
        deviceMemorySize(170),
        --  Device configuration settings and defaults 
        deviceConfigurationSetting(180), 
        deviceTimezone(181),
        deviceSoundControl(182),
        deviceLEDControl(183),
        --  Device job service timeouts
        deviceJobIncompleteTimeout(191),
        deviceJobProgrammingTimeout(192),
        deviceJobHoldDeleteTimeout(193),
        deviceJobPauseResumeTimeout(194),
        --  Device guest/alien job and log full policies
        deviceGuestJobPolicy(200),
        deviceAlienJobPolicy(201),
        deviceEventLogFullPolicy(202),
        deviceJobLogFullPolicy(203),
        deviceRequestLogFullPolicy(204),
        --  Device model info
        deviceUniversalProductCode(210),
        deviceModelName(211),
        deviceModelDescription(212),
        deviceModelNumber(213),
        deviceManufacturerURI(220),
        deviceModelURI(221),
        --  Service Usage counters for billing.
        deviceServiceUsage(230),
        deviceDeltaServiceUsage(231),
        deviceRolloverValue(232),
        --  Control Panel Menu Control
        deviceCPMenuControl(235),
        -- Service Usage Warning
        deviceUsageWarningThreshold(240),
        --  Supplies Details
        deviceLifetimeAvgCoverage(250),
        deviceLifeRemainingPercent(251),
        deviceRemainingImpressions(252),
        deviceSuppliesClass(253),
        deviceSupplyUnit(254),
        deviceSuppliesMaxCapacity(255),
        deviceSuppliesCurrentLevel(256),
        deviceInstallDate(260),
        deviceStatus(270),

XCMI Working Group  File 10hosttc               [Page 75]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        deviceSupportContactInfo(271),
        deviceServiceContactInfo(272),
        deviceSuppliesContactInfo(273),

        --  Fax Modem Details
        deviceFaxCountry(280),
        deviceFaxDialType(281),

        deviceGPSLatitude(293),
        deviceGPSLongitude(294),
        deviceGPSAltitude(295),

        deviceMeasurementSetting(296),

        --  Feature Installation Key Details
        deviceInstallationKeyCSVPrintSubmission(500),
        deviceFeatureInstallationKeyAvailability(501),
        deviceFeatureInstallationKeyDisablement(502),
        deviceFeatureInstallationKeyDate(503)

    }

XcmHrDevDetailUnitClass ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The value unit class of the device detail information specified
        in this conceptual row in the 'xcmHrDevDetailTable'.

        Usage:  Used to select a textual convention for specifying the
        units of this device detail value.

        Usage:  Some of the value unit class enumerations specify that
        the actual unit is REQUIRED to be selected in '...DetailUnit'
        and REQUIRE '...DetailValueString' contains a value in units
        (and are commented as such below).

        Usage:  Some of the value unit class enumerations specify the
        actual unit DIRECTLY and REQUIRE that '...DetailUnit' be zero
        and REQUIRE '...DetailValueString' contains a value in the
        named textual convention (or a bit-mask derived from it)
        (and are commented as such below).

        Usage:  Some of the value unit class enumerations specify that
        '...DetailValueString' SHALL contain a bit-mask which is
        formed via the bit-wise OR of '2**(n)', where (n) is each
        selected enumerated value in the named textual convention.
        (see 'xcmGenBaseSNMPDomainSupport' object in XCMI General MIB)."
    SYNTAX      INTEGER {
        other(1),
        unknown(2),
        --  The following values specify that the actual unit
        --  is REQUIRED to be selected in the '...DetailUnit' object
        --  and REQUIRE '...DetailValueString' contains a value in units
        classGenOptionValueSyntax(3),   -- XcmGenOptionValueSyntax

XCMI Working Group  File 10hosttc               [Page 76]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  The following values specify the actual unit
        --  DIRECTLY and REQUIRE that '...DetailUnit' be zero
        --  and REQUIRE '...DetailValueString' contains a value in the
        --  named textual convention (or a bit-mask derived from it)
        classDateAndTime(4),            -- DateAndTime (from SNMPv2-TC)
        classHrDevCalendarDayOfWeek(5), -- XcmHrDevCalendarDayOfWeek
        classHrDevCalendarTimeOfDay(6), -- XcmHrDevCalendarTimeOfDay
        classHrDevMgmtCommandRequest(7),-- XcmHrDevMgmtCommandRequest
        --  The following values specify that the actual unit
        --  is REQUIRED to be selected in the '...DetailUnit' object
        --  and REQUIRE '...DetailValueString' contains a value in units
        classHrDevPowerTimeUnit(8),     -- XcmHrDevPowerTimeUnit
        classHrDevTrafficUnit(9),       -- XcmHrDevTrafficUnit
        --  The following values specify the actual unit
        --  DIRECTLY and REQUIRE that '...DetailUnit' be zero
        --  and REQUIRE '...DetailValueString' contains a value in the
        --  named textual convention (or a bit-mask derived from it)
        classRowPersistence(10),        -- XcmGenRowPersistence
        classRowPersistenceMask(11),    -- XcmGenRowPersistence -> mask
        classLogFullPolicy(12),         -- XcmGenLogFullPolicy
        classLogFullPolicyMask(13),     -- XcmGenLogFullPolicy -> mask
        classHrDevInfoStatus(14),       -- XcmHrDevInfoStatus
        classHrDevInfoStatusMask(15),   -- XcmHrDevInfoStatus -> mask
        classHrDevInfoXStatus(16),      -- XcmHrDevInfoXStatus
        classHrDpaState(17),            -- XcmHrDpaState
        classHrDpaConditions(18),       -- XcmHrDpaConditions
        classHrDpaAvailability(19),     -- XcmHrDpaAvailability
        classHrDpaObjectClassSupport(20), -- XcmHrDpaObjectClassSupport
                                          -- (is already bit-mask)
        classHrDpaJobValidateSupport(21), -- XcmHrDpaJobValidateSupport
                                          -- (is already bit-mask)
        classJMJobState(22),            -- XcmJMJobState
        classJMJobStateMask(23),        -- XcmJMJobState -> mask
        classSecGuestJobPolicy(24),     -- XcmSecGuestJobPolicy
        classSecGuestJobPolicyMask(25), -- XcmSecGuestJobPolicy -> mask
        classSecPosixRights(26),        -- XcmSecPosixRights
                                        -- (is already bit-mask)
        classSecPosixVerbs(27),         -- XcmSecPosixVerbs
                                        -- (is already bit-mask)
        classSvcMonJobConfirmSupport(28), -- XcmSvcMonJobConfirmSupport
                                          -- (is already bit-mask)

        --  The following values specify the actual unit
        --  DIRECTLY and REQUIRE that '...DetailUnit' be zero
        --  and REQUIRE '...DetailValueString' and 
        --  '...DetailValueInteger' contain a bit-mask in the named
        --  textual convention 
        classSvcMonAttachmentPDLSupport(29) 
                                        -- XcmSvcMonAttachmentPDLSupport
                                        -- (is already a bit-mask)
    }




XCMI Working Group  File 10hosttc               [Page 77]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

XcmHrDevInfoRealization ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "An extended device type (or device 'realization'),
        used by system administrators and end users of this device.

        Usage:  The use of either 'other' or 'unknown' is uninformative
        and SHOULD be avoided by conforming implementations.

      * 'physical' - 'real' device installed on this managed system;
      * 'logical' - 'virtual' device configured on this managed system;
      * 'logicalAndPhysical' - 'combined' device (from ISO DPA ??)."
    REFERENCE
        "See:   'hrDeviceType' in the basic Device Group of the
        IETF Host Resources MIB (RFC 2790).
        See:    Section 9.4 'Printer Object attributes' of ISO DPA
        (Document Printing Application) ISO/IEC 10175 (Final Text, March
        1996) for a discussion of 'printer realizations' of 'physical',
        'logical', and 'logical-and-physical' types (the latter unique
        to DPA)."
    SYNTAX      INTEGER {
        other(1),                       -- other device       
        unknown(2),                     -- unknown device     
        physical(11),                   -- 'real' device
        logical(12),                    -- 'virtual' device
        logicalAndPhysical(13)          -- 'combined' device
    }

XcmHrDevInfoStatus ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The current operational state of the device
        described by this row of the table.  A value
        'unknown(1)' indicates that the current state of the
        device is unknown.  'running(2)' indicates that the
        device is up and running and that no unusual error
        conditions are known.  The 'warning(3)' state
        indicates that agent has been informed of an
        unusual error condition by the operational software
        (eg, a disk device driver) but that the device is
        still 'operational'.  An example would be a high
        number of soft errors on a disk.  A value of
        'testing(4)', indicates that the device is not
        available for use because it is in the testing
        state.  The state of 'down(5)' is used only when the
        agent has been informed that the device is not
        available for any use.

        Usage:  Conforming implementations SHALL NOT 'bubble up' status
        from 'physical' devices to associated 'logical' devices.  All
        devices SHALL report their own status ONLY.

        Usage:  Devices in the 'down' state SHOULD NOT be accepting new
        work (or still processing old work).  Devices in the 'running'

XCMI Working Group  File 10hosttc               [Page 78]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        state SHOULD be prepared to accept new work.

        Usage:  The use of the state 'unknown' is uninformative
        and SHOULD be avoided by conforming implementations.

        Usage:  This is a textual convention representation of the
        'hrDeviceStatus' enumeration in the IETF Host Resources MIB
        (RFC 2790), rewritten from SMIv1 style (RFCs 1155 and 1212) into
        SMIv2 style (RFCs 1902/2578, 1903/2579, and 1904/2580)."
    REFERENCE
        "See:   'hrDeviceStatus' in the basic Device Group of the
        IETF Host Resources MIB (RFC 2790).
        See:    'xcmHrDevInfoXStatus', 'xcmHrDevInfoConditions', and
        'xcmHrDevInfoXConditions' in the Host Resources Extensions MIB."
    SYNTAX      INTEGER {
        unknown(1),                     -- indeterminate      
        running(2),                     -- normally operational, started
        warning(3),                     -- operational, but alert posted
        testing(4),                     -- NOT operational, testing
        down(5)                         -- NOT operational, shutdown
    }

XcmHrDevInfoXStatus ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "An extended device status, used by system administrators
        and end users of this device (here, read 'state' for 'status').

        Usage:  Conforming implementations SHALL NOT 'bubble up' status
        from 'physical' devices to associated 'logical' devices.  All
        devices SHALL report their own status ONLY.

        Usage:  Exactly one enumeration of extended device status
        SHALL be defined, with ranges for each basic device type (eg,
        'hrDevicePrinter').  The legal range for extended device status
        for a given device type (either defined by RFC 2790 or by this
        MIB) is found by multiplying the final arc of the the device
        type OID by 100 - the result is the device specific range base -
        the end of the device specific range is 99 larger.  These device
        specific extended device status values SHALL be reissued
        periodically in the 'XcmHrDevInfoXStatus' textual convention."
    REFERENCE
        "See:   Section 9.4.9 'Printer-state' of ISO DPA
        (Document Printing Application) ISO/IEC 10175 (Final Text,
        18 May 1995) for a discussion of the printer states used here.
        Note that the DPA state 'connecting-to-printer' has no meaning
        in the context of a 'physical' printer device, but only in the
        context of an intermediate DP-Server presenting a 'logical'
        printer device.
        See:    'hrPrinterStatus' and 'hrPrinterDetectedErrorState' in
        the IETF Host Resources MIB (RFC 2790) for related discussion.

        See:    'hrDeviceStatus' in the basic Device Group of the
        IETF Host Resources MIB (RFC 2790).

XCMI Working Group  File 10hosttc               [Page 79]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        See:    'xcmHrDevInfoConditions' and 'xcmHrDevInfoXConditions'
        in the Host Resources Extensions MIB."
    SYNTAX      INTEGER {
        --  Common extended device status
        commonNone(0),
        commonOther(1),
        commonUnknown(2),
        commonLast(99),

        --  'hrDeviceOther'
        otherNone(100),

        --  'hrDeviceUnknown'
        unknownNone(200),

        --  'hrDeviceProcessor'
        processorNone(300),

        --  'hrDeviceNetwork'
        networkNone(400),

        --  'hrDevicePrinter'
        --  See:    Section 9.4.9 'Printer-state' of ISO/IEC 10175
        --          (was on page 185 in earlier text, May 1995)
        --  See:    'id-val-printer-state-...' in Annex A of ISO/IEC
        --          10175 (was on page 307 in earlier text, May 1995)
        --  If 'dpaPrinterStateFinalArc' is truncated from an OID
        --  'id-val-printer-state-...' in Annex A of ISO/IEC 10175
        --  and 'xcmiPrinterStatus' is the corresponding enum value of
        --  'printer...' in 'XcmHrDevInfoXStatus' (below),
        --  then:
        --      xcmiPrinterStatus = (dpaPrinterStateFinalArc + 502)
        printerNone(500),               -- XCMI extension to ISO DPA
        printerOther(501),              -- XCMI extension to ISO DPA
        printerUnknown(502),            -- unknown or indeterminate
        printerIdle(503),               -- ready to accept jobs
        printerPrinting(504),           -- currently printing a job
        printerNeedsAttention(505),     -- needs general human attention
        printerPaused(506),             -- paused by user or operator
        printerShutdown(507),           -- taken out of service
        printerJobStartWait(508),       -- see ISO DPA 'job-start-wait'
        printerJobEndWait(509),         -- see ISO DPA 'job-end-wait'
        printerNeedsKeyOperator(510),   -- needs toner, developer, etc
        printerJobPasswordWait(511),    -- see ISO DPA 'job-password'
        printerTimedOut(512),           -- ISO DPA Servers only
        printerConnectingToPrinter(513),-- ISO DPA Servers only

        --  'hrDeviceDiskStorage'
        diskStorageNone(600),

        --  'hrDeviceVideo'
        videoNone(1000),

        --  'hrDeviceAudio'

XCMI Working Group  File 10hosttc               [Page 80]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        audioNone(1100),

        --  'hrDeviceCoprocessor'
        coprocessorNone(1200),

        --  'hrDeviceKeyboard'
        keyboardNone(1300),

        --  'hrDeviceModem'
        modemNone(1400),

        --  'hrDeviceParallelPort'
        parallelPortNone(1500),

        --  'hrDevicePointing'
        pointingNone(1600),

        --  'hrDeviceSerialPort'
        serialPortNone(1700),

        --  'hrDeviceTape'
        tapeNone(1800),

        --  'hrDeviceClock'
        clockNone(1900),

        --  'hrDeviceVolatileMemory'
        volatileMemoryNone(2000),

        --  'hrDeviceNonVolatileMemory'
        nonVolatileMemoryNone(2100),

        --  'xcmHrDeviceHostSystem'
        hostSystemNone(10100),

        --  'xcmHrDeviceScanner'
        scannerNone(10200),

        --  'xcmHrDeviceCopier'
        copierNone(10300),

        --  'xcmHrDeviceFax'
        faxNone(10400),

        --  'xcmHrDeviceMailbox'
        mailboxNone(10500),

        --  'xcmHrDeviceMarker'
        markerNone(11100),

        --  'xcmHrDeviceFinisherBFM'
        finisherBFMNone(11200),

        --  'xcmHrDeviceFinisherMFF'

XCMI Working Group  File 10hosttc               [Page 81]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        finisherMFFNone(11300),

        --  'xcmHrDeviceFinisherXIM'
        finisherXIMNone(11400),

        --  'xcmHrDeviceFinisher3rdParty'
        finisher3rdPartyNone(11500),

        --  'xcmHrDevicePaymentInterface'
        paymentInterfaceNone(11600),

        --  'xcmHrDeviceInterposer'
        interposerNone(11700),

        --  'xcmHrDeviceInternetFax'
        internetFaxNone(11800),

        --  'xcmHrDeviceServerFax'
        serverFaxNone(11900),

        --  'xcmHrDeviceEmbeddedFax'
        embeddedFaxNone(12000),

 -- 'xcmHrDeviceForeignInterface' 
 foreignInterfaceNone(12100),

        -- 'xcmHrDeviceSecurityInterface' 
        securityInterfaceNone(12200),

        -- 'xcmHrDeviceAccountingInterface' 
        accountingInterfaceNone(12300), 

        --  'xcmHrCru...' - Customer Replaceable Units
        cruNone(20000),                 -- CRU no status
        cruOther(20001),                -- CRU other status
        cruUnknown(20002),              -- CRU unknown status
        cruReady(20003),                -- CRU OK (normal wear)
        cruReorder(20004),              -- CRU should be reordered
        cruReplace(20005),              -- CRU should be replaced
        cruFault(20006),                -- CRU has one or more faults

        reserved(40000)                 -- placeholder
    }

XcmHrDevInfoConditions ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A relatively generic description of the current 'conditions'
        of this device, specified in a bit-mask.

              1 : startupInProgress             -- 2**0
              2 : resetWarningInProgresss       -- 2**1       (optional)
              4 : testInProgress                -- 2**2
              8 : shutdownInProgress            -- 2**3       (optional)

XCMI Working Group  File 10hosttc               [Page 82]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

             16 : quiesceInProgress             -- 2**4       (optional)
             32 : resetCountersInProgress       -- 2**5       (optional)
             64 : resetWarmInProgress           -- 2**6
            128 : resetColdInProgress           -- 2**7
            256 : resetFactoryInProgress        -- 2**8
            512 : flushInputInProgress          -- 2**9
           1024 : flushOutputInProgress         -- 2**10
           2048 : flushInOutInProgress          -- 2**11
           4096 : manageInProgress              -- 2**12      (optional)

        The above basic 'conditions' record the original intent of the
        current command, when it results in delayed state transitions
        before arriving at the 'target' state.  They augment the state
        information available from 'hrDeviceStatus'.

           8192 : warmUpDelayInProgress         -- 2**13      (optional)
          16384 : warmUpCycleInProgress         -- 2**14      (optional)
          32768 : readyMode                     -- 2**15      (optional)
          65536 : coolDownDelayInProgress       -- 2**16      (optional)
         131072 : coolDownCycleInProgress       -- 2**17      (optional)
         262144 : standbyMode                   -- 2**18      (optional)
         524288 : energySaveDelayInProgress     -- 2**19      (optional)
        1048576 : energySaveCycleInProgress     -- 2**20      (optional)
        2097152 : sleepMode                     -- 2**21      (optional)
        4194304 : wakeUpDelayInProgress         -- 2**22      (optional)
        8388608 : wakeUpCycleInProgress         -- 2**23      (optional)
       16777216 : powerToReadyInProgress        -- 2**24      (optional)
       33554432 : powerToStandbyInProgress      -- 2**25      (optional)
       67108864 : powerToSleepInProgress        -- 2**26      (optional)

        The above optional 'conditions' record the progress of device
        'warm up', 'cool down', 'energy save', and 'wake up' power mgmt
        cycles and also define the device 'readyMode', 'standbyMode',
        and 'sleepMode' qualifiers to the generic 'hrDeviceStatus' of
        'running(2)', 'warning(3)', or 'testing(4)' (but NOT 'down(5)').
        See the power management cycle feature support and feature time
        objects in the Device Power Group of the Host Resources Ext MIB.

        Usage:  It is desirable that the implementor report 'conditions'
        of all devices corresponding to conceptual rows in the
        'hrDeviceTable' as accurately as feasible.  'Conditions' occur
        within or across 'states' in a finite state machine (FSM)
        implementation of a device.  They represent both short term and
        long term conditions.

        Usage:  A device with 'hrDeviceStatus' of 'running(2)' might
        have 'xcmHrDevInfoConditions' of 'quiesceInProgress', indicating
        that the device will soon transition to 'hrDeviceStatus' of
        'down(5)'.

        Usage:  A multi-bit example of 'xcmHrDevInfoConditions' is
        'quiesceInProgress' concurrently with 'standbyMode', ie, the
        device has previously 'cooled down' and will soon transition
        from 'hrDeviceStatus' of 'running(2)' to 'down(5)'."

XCMI Working Group  File 10hosttc               [Page 83]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    REFERENCE
        "See:   'hrDeviceStatus' in the basic Device Group of the
        IETF Host Resources MIB (RFC 2790).
        See:    'xcmHrDevInfoXStatus' and 'xcmHrDevInfoXConditions'
        in the Host Resources Extensions MIB."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XcmHrDevInfoXConditions ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A device specific description of the extended 'conditions'
        of this device, specified in a bit-mask.

        Usage:  For FUTURE expansion.

        Usage:  Exactly one bit mask of extended device conditions SHALL
        be defined for each basic device type (eg, 'hrDevicePrinter').
        These device specific extended device conditions values SHALL be
        reissued periodically in the 'XcmHrDevInfoXConditions' textual
        convention.  These device specific extended device conditions
        are mutually exclusive and 'overloaded' in the single reporting
        object 'xcmHrDevInfoXConditions'."
    REFERENCE
        "See:   'hrDeviceStatus' in the basic Device Group of the
        IETF Host Resources MIB (RFC 2790).
        See:    'xcmHrDevInfoXStatus' and 'xcmHrDevInfoConditions'
        in the Host Resources Extensions MIB."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XcmHrDeviceStatusType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Used to describe the device status.

        Usage: used in xcmHrDetailTable for supplies.
        Required because supplies are not in the
        hrDeviceTable and therefore hrDeviceStatus
        cannot be used.

        Modeled after hrDeviceStatus where 2=running, 
        3=warning and 5=down."
    SYNTAX      INTEGER {
        unknown(1),
        ok(2),
        supplyReorder(3), 
        supplyReplace(5),
 supplyMissing(6)
    }  







XCMI Working Group  File 10hosttc               [Page 84]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

XcmHrDevMgmtCommandRequest ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A write of this type by an (authorized) management station
        invokes a command for this device.
        A read of this type always returns the command currently in
        progress or last completed.
        It is mandatory that a conforming management agent ensure that
        the contents of this object remain 'in bounds' - an undefined
        value SHALL be replaced by 'none' - ie, although rejected with
        error in the SetResponse PDU, this object SHALL NOT contain any
        such undefined value.  At system initialization, this object
        SHALL contain 'none'.

      * 'none' - NO action(s) SHALL be taken, except to clear
        '...CommandData' and set '...CommandStatus' to 'noError'.
      * 'test' or 'manage' - the associated '...CommandData' object
        SHOULD/SHALL be specified in the same SetRequest PDU.
      * all other commands - the associated '...CommandData' object
        MAY be specified in the same SetRequest PDU.
      * 'startup', 'resetWarm', 'resetCold', or 'resetFactory' - the
        final state SHALL be 'running' (after cycle completes) - the
        sequence of states SHOULD be 'down' -> 'testing' -> 'running' -
        the final power mode SHALL be 'ready'.
      * 'startup' - this device SHALL transition from the 'down' state
        to the 'running' state and 'ready' power mode.
      * 'resetWarning' - this device SHALL transition from the 'warning'
        state to the 'running' state (because a management station has
        acknowledged the management agent's previous warning).
      * 'test' - this device SHALL transition immediately (ie, without
        attempting graceful quiesce) to the 'testing' state; it is a
        local matter (ie, device specific) how this command is
        processed; however, '...CommandData' SHOULD be specified.
      * 'shutdown' - this device SHALL transition immediately (ie,
        without attempting graceful quiesce) to the 'down' state and
        'off' power mode.
      * 'quiesce' - this device MAY transition gracefully to the 'down'
        state, or it MAY choose to treat a 'quiesce' as 'shutdown'.
      * 'resetCounters' - all device counters SHALL be reset to zero and
        the device SHALL remain in the same state and power mode.
      * 'resetWarm' - a device 'warm restart' SHALL be performed (ie,
        without a power cycle reset).
      * 'resetCold' - a device 'cold restart' SHALL be performed (ie,
        with a power cycle reset).
      * 'resetFactory' - all factory defaults SHALL be restored, and a
        device 'cold restart' SHALL be performed (ie, with a power cycle
        reset).
      * 'flushInput' - all device input (in progress or internally
        queued) SHALL be gracefully flushed.
      * 'flushOutput' - all device output (in progress or internally
        queued) SHALL be gracefully flushed.
      * 'flushInOut' - all device input and output output (in progress
        or internally queued) SHALL be gracefully flushed.
      * 'manage' - it is a local matter (ie, device specific) how this

XCMI Working Group  File 10hosttc               [Page 85]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        command is processed; however, '...CommandData' SHALL be
        specified.
      * 'refresh' - the device SHALL promptly read all of its manageable
        configuration parameters, but SHALL NOT perform a reset.
      * 'warmUp' - the device SHALL transition from the 'standby' mode
        to the 'ready' mode - invalid from any other power mode
        (optional command for remote device power management).
      * 'coolDown' - the device SHALL transition from the 'ready' mode
        to the 'standby' mode - invalid from any other power mode
        (optional command for remote device power management).
      * 'energySave' - the device SHALL transition from the 'standby'
        mode to the 'sleep' mode - invalid from any other power mode
        (optional command for remote device power management).
      * 'wakeUp' - the device SHALL transition from the 'sleep'
        mode to the 'standby' mode - invalid from any other power mode
        (optional command for remote device power management).
      * 'powerToReady' - the device SHALL transition from the 'standby'
        mode or the 'sleep' mode to the 'ready' mode
        (optional command for remote device power management).
      * 'powerToStandby' - the device SHALL transition from the 'ready'
        mode or the 'sleep' mode to the 'standby' mode
        (optional command for remote device power management).
      * 'powerToSleep' - the device SHALL transition from the 'ready'
        mode or the 'standby' mode to the 'sleep' mode
        (optional command for remote device power management).

        Note:   All of the POSIX and XCMI device level operations are
        taken from the POSIX System Admin std (IEEE 1387.4) and aligned
        with the high-end XCMI System Admin MIB."
    REFERENCE
        "See:   'dot5Commands' in IEEE 802.5 Token Ring MIB (RFC 1748)
        and 'hrDeviceStatus' in IETF Host Resources MIB (RFC 2790).
        Compare:    'ifOperStatus' (current) and 'ifAdminStatus'
        (desired) in the Interfaces Group of IETF MIB-II (RFC 1213);
        'RowStatus' textual convention in IETF SMIv2 (RFC 1902/2578).

        See:    Section 4 'Print Utilities' (pages 71 to 212) of
                POSIX Sys Admin (IEEE 1387.4 / Draft 8, October 1994).
        See:    OBJECT clause in MODULE-COMPLIANCE macro of
                XCMI Ext to Host Resources MIB, for compliance info.
        See:    Section 3.4 'XCMI Standard Tagged Management Data' and
                Section 3.5 'Simple Device Management Requests' in
                XCMI Ext to Host Resources TC.
        See:    Section 3.5.3 'Secure Simple Device Mgmt Requests' in
                XCMI Security TC."
    SYNTAX      INTEGER {
        none(1),                        -- no operation
        startup(2),                     -- to 'running'
        resetWarning(3),                -- from 'warning' to 'running'
        test(4),                        -- to 'testing' immediately
        shutdown(5),                    -- to 'down' immediately
        quiesce(6),                     -- to 'down' gracefully
        resetCounters(7),               -- reset all device counters
        resetWarm(8),                   -- warm restart to 'running'

XCMI Working Group  File 10hosttc               [Page 86]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        resetCold(9),                   -- cold restart to 'running'
        resetFactory(10),               -- factory defaults cold restart
        flushInput(11),                 -- flush all input
        flushOutput(12),                -- flush all output
        flushInOut(13),                 -- flush all input and output
        manage(14),                     -- manage command, any state
        refresh(15),                    -- refresh device w/out reset
        warmUp(16),                     -- 'standby' to 'ready' ONLY
        coolDown(17),                   -- 'ready' to 'standby' ONLY
        energySave(18),                 -- 'standby' to 'sleep' ONLY
        wakeUp(19),                     -- 'sleep' to 'standby' ONLY
        powerToReady(20),               -- 'standby|sleep' to 'ready'
        powerToStandby(21),             -- 'ready|sleep' to 'standby'
        powerToSleep(22),               -- 'ready|standby' to 'sleep'
        --  POSIX - Device level operations (on host system)
        deviceCreate(1301),             -- 'pdcreate' (create device)
        deviceDelete(1302),             -- 'pddelete' (delete device)
        deviceList(1303),               -- 'pdls' (list attributes)
        deviceSet(1304),                -- 'pdset' (set attributes)
        deviceClean(1305),              -- 'pdclean' (remove all jobs)
        deviceDisable(1306),            -- 'pddisable' (stop new jobs)
        deviceEnable(1307),             -- 'pdenable' (allow new jobs)
        devicePause(1308),              -- 'pdpause' (pause device)
        deviceResume(1309),             -- 'pdresume' (resume device)
        deviceShutdown(1310),           -- 'pdshutdown' (end device)
        deviceQueueList(1311),          -- 'pdq' (list device job queue)
        deviceJobCreate(1312),          -- 'pdpr' (submit job to device)
        --  XCMI - Device level extensions (on host system)
        deviceManage(2301),             -- manage device object(s)
        deviceRestart(2302),            -- restart device
        deviceInstall(2321),            -- install device object(s)
        deviceUpgrade(2322),            -- upgrade device object(s)
        deviceBackup(2323),             -- backup device object(s)
        deviceRestore(2324),            -- restore device object(s)
        deviceConfigure(2325),          -- configure device object(s)
        deviceDiagnose(2326),           -- diagnose device object(s)
        deviceResetCounters(2331),      -- reset device counters
        deviceResetWarm(2332),          -- warm reset (no power cycle)
        deviceResetCold(2333),          -- cold reset (w/ power cycle)
        deviceResetFactory(2334),       -- factory defaults reset
        deviceFormat(2335),             -- format device (storage)
        deviceRefresh(2336),            -- refresh device (comms)
        deviceLogin(2341),              -- login w/ authentication
        deviceLogout(2342),             -- logout w/ authentication
        deviceDiskOverwrite(2343),      -- disk overwrite for security 
        --  POSIX - Entity level operations (on host system)
        entityCreate(1901),             -- 'pdcreate' (create entity)
        entityDelete(1902),             -- 'pddelete' (delete entity)
        entityList(1903),               -- 'pdls' (list attributes)
        entitySet(1904),                -- 'pdset' (set attributes)
        entityClean(1905),              -- 'pdclean' (remove all jobs)
        entityDisable(1906),            -- 'pddisable' (stop new jobs)
        entityEnable(1907),             -- 'pdenable' (allow new jobs)
        entityPause(1908),              -- 'pdpause' (pause entity)

XCMI Working Group  File 10hosttc               [Page 87]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        entityResume(1909),             -- 'pdresume' (resume entity)
        entityShutdown(1910),           -- 'pdshutdown' (end entity)
        entityQueueList(1911),          -- 'pdq' (list entity job queue)
        entityJobCreate(1912),          -- 'pdpr' (submit job to entity)
        --  XCMI - Entity level extensions (on host system)
        entityManage(2901),             -- manage entity object(s)
        entityRestart(2902),            -- restart entity
        entityInstall(2921),            -- install entity object(s)
        entityUpgrade(2922),            -- upgrade entity object(s)
        entityBackup(2923),             -- backup entity object(s)
        entityRestore(2924),            -- restore entity object(s)
        entityConfigure(2925),          -- configure entity object(s)
        entityDiagnose(2926),           -- diagnose entity object(s)
        entityResetCounters(2931),      -- reset entity counters
        entityResetWarm(2932),          -- warm reset (no power cycle)
        entityResetCold(2933),          -- cold reset (w/ power cycle)
        entityResetFactory(2934),       -- factory defaults reset
        entityFormat(2935),             -- format entity (storage)
        entityRefresh(2936),            -- refresh entity (comms)
        entityLogin(2941),              -- login w/ authentication
        entityLogout(2942)              -- logout w/ authentication
    }

XcmHrDevMgmtCommandData ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A write of this type specifies:  a) a 'test' command subtype
        and any accompanying 'test' device specific data; or b) a
        'manage' command subtype and any accompanying 'manage' device
        specific data; or c) device specific data accompanying any
        other command.
        A read of this type always returns the data (if any) which
        accompanied the current or last completed command."
    REFERENCE
        "See:   Section 4 'Print Utilities' (pages 71 to 212) of
                POSIX Sys Admin (IEEE 1387.4 / Draft 8, October 1994).
        See:    'hrDeviceStatus' in the Device group of the
                IETF Host Resources MIB (RFC 2790).
        See:    Section 3.4 'XCMI Standard Tagged Management Data' and
                Section 3.5 'Simple Device Management Requests' in
                XCMI Ext to Host Resources TC.
        See:    Section 3.5.3 'Secure Simple Device Mgmt Requests' in
                XCMI Security TC."
    SYNTAX      OCTET STRING (SIZE (0..255))

XcmHrDevMgmtCommandDataTag ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "XCMI device management commands are passed as enumerated types
        in 'xcmHrDevMgmtCommandRequest' in the XCMI HRX MIB.
        Other XCMI management commands are passed as enumerated types in
        'xcmCommsMgmtCommandRequest', 'xcmSimpleJobMgmtOperation', etc,
        in the XCMI Comms Engine, Simple Job Mgmt, and other MIBs.


XCMI Working Group  File 10hosttc               [Page 88]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


        XCMI management commands MAY also require one or more arguments
        (in addition to any specific variable bindings of MIB objects).
        Required arguments are passed as 'tagged string arguments' in
        'xcmHrDevMgmtCommandData', 'xcmSimpleJobMgmtData', etc.
        Each 'tagged string argument' substring is of the form:

            'TT=value:'

        where:
            'TT'        two-character 'tag', naming argument type
            '='         literal equal sign, beginning argument value
            'value'     human-readable string, encoding argument value
            ':'         literal colon, terminating argument value

        XCMI conforming management stations SHALL terminate ALL
        'tagged string argument' substrings properly with colon (':').

        XCMI standard 'tagged string arguments' MAY pass colon (':')
        in their 'value' by escaping it with backslash ('\').  XCMI
        conforming management agents SHALL interpret backslash
        followed by ANY other character as the literal value of the
        second character (ie, backslash is permitted, and is NOT
        restricted to certain following characters).

        XCMI standard 'tags' for data in 'tagged string arguments',
        (in 'xcmHrDevMgmtCommandData', 'xcmSimpleJobMgmtData', etc)
        are as follows:

        --  Generic Data (no object mapping to MIBs)
        --  For domain-specific future extensions to operations
      * SC  [Sub-Command - domain-specific, must be FIRST tag present]
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  domain-specific sub-command for management request
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')
        --  passed as character string, NOT as binary value

        --  For generic access to any IETF or XCMI defined objects
      * OI  [Object Identifier - no object mapping]
        --  syntax 'OBJECT IDENTIFIER'
        --  object identifier of object (WITHOUT instance qualifiers)
        --  passed as dotted decimal OID or as object label
        --  (eg, 'hrDeviceID'), NOT as binary object identifier

      * OV  [Object Value - no object mapping]
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  object value of object
        --  passed as character string, NOT as binary value
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

        --  For protection against 'replay' attacks
      * DT  [Date and Time - no object mapping]
        --  (see 'hrSystemDate' in System group of IETF HR MIB)
        --  syntax 'DateAndTime'

XCMI Working Group  File 10hosttc               [Page 89]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  date and time stamp for management request
        --  passed as dotted decimal string (ie, 'yyyy.mm.dd.hh.mm.ss'),
        --  NOT as binary value

      * NI  [Noise Information - no object mapping]
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  arbitrary noise info for management request
        --  passed as hexadecimal string, NOT as binary value

      * SI  [Sequence Identifier - no object mapping]
        --  syntax 'Ordinal32'
        --  sequence ID for management request (for 'secure streams')
        --  passed as decimal string, NOT as binary value

        --  Security Data from XCMI Security MIB (63sec)
        --  For account-based authentication
      * AI  'xcmSecAccountIndex'
        --  syntax 'Ordinal32'
        --  index of account (ie, account ID)
        --  passed as decimal string, NOT as binary value

      * AN  'xcmSecAccountName'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  human-readable name of account (ie, account label)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * AC  'xcmSecAccountPasscode'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  protected numeric password of account
        --  passed as hexadecimal string, NOT as binary value
        --  (protected text form, NOT cleartext password)

      * AW  'xcmSecAccountPassword'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  protected alphanumeric password of account
        --  passed as hexadecimal string, NOT as binary value
        --  (protected text form, NOT cleartext password)

        --  For user-based authentication
      * UI  'xcmSecUserIndex'
        --  syntax 'Ordinal32'
        --  index of user (ie, user ID)
        --  passed as decimal string, NOT as binary value

      * UN  'xcmSecUserName'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  human-readable name of user (ie, user label)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * UC  'xcmSecUserPasscode'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  protected numeric password of user
        --  passed as hexadecimal string, NOT as binary value
        --  (protected text form, NOT cleartext password)

XCMI Working Group  File 10hosttc               [Page 90]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


      * UW  'xcmSecUserPassword'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  protected alphanumeric password of user
        --  passed as hexadecimal string, NOT as binary value
        --  (protected text form, NOT cleartext password)

        --  System group of IETF MIB-II (RFC 1213)
      * ZD  'sysDescr'
        --  syntax 'DisplayString (SIZE (0..255))'
        --  (NVT ASCII string)
        --  textual description of host system, 
        --  passed as ASCII string, NOT as localized string
        --  (see XCMI MIB Implementer's Guide for the format
        --   of sysDescr).
        --  (see 'hrDeviceDescr' of type 'DisplayString' in IETF HR MIB)

      * ZI  'sysObjectID'
        --  syntax 'OBJECT IDENTIFIER'
        --  product ID of host system
        --  passed as dotted decimal OID or as system product ID label
        --  (eg, 'xcmPidStarship20'), NOT as binary object identifier
        --  (see 'hrDeviceID' of type 'ProductID' in IETF HR MIB)

      * ZS  'sysServices'
        --  syntax 'INTEGER (0..127)'
        --  bit-mask of services host system offers
        --  passed as decimal string, NOT as binary value

        --  Interface group of IETF MIB-II (RFC 1213)
      * IX  'ifIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of host system interface conceptual row
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index

      * ID  'ifDescr'
        --  syntax 'DisplayString (SIZE (0..255))'
        --  (NVT ASCII string)
        --  textual description of host system interface,
        --  including manufacturer, product name, version of hardware

      * IY  'ifType'
        --  syntax 'INTEGER (1..2147483647)' (enumeration)
        --  (see 'IANAifType' textual convention in 'IANAifType-MIB')
        --  type of host system interface
        --  passed as decimal string or as interface type enum label
        --  (eg, 'iso88025-tokenRing'), NOT as binary value

      * IM  'ifMtu'
        --  syntax 'INTEGER (0..2147483647)'
        --  max transmission unit (datagram) on host system interface
        --  passed as decimal string, NOT as binary value


XCMI Working Group  File 10hosttc               [Page 91]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


      * IS  'ifSpeed'
        --  syntax 'INTEGER (0..2147483647)'
        --  speed (bits/second) of host system interface
        --  passed as decimal string, NOT as binary value

      * IP  'ifPhysAddress'
        --  syntax 'PhysAddress'
        --  physical address of host system interface
        --  passed as hexadecimal string, NOT as binary value

      * IZ  'ifSpecific'
        --  syntax 'OBJECT IDENTIFIER'
        --  reference to media-specific MIB for host system interface
        --  passed as dotted decimal OID or as media-specific MIB label
        --  (eg, 'EtherLike-MIB'), NOT as binary value

        --  System group of IETF HR MIB (RFC 2790)
      * ZA  'hrSystemDate'
        --  syntax 'DateAndTime'
        --  local date and time on host system
        --  passed as dotted decimal string (ie, 'yyyy.mm.dd.hh.mm.ss'),
        --  NOT as binary value

      * ZL  'hrSystemInitialLoadDevice'
        --  syntax 'INTEGER (1..2147483647)'
        --  (see 'hrDeviceIndex' in IETF HR MIB)
        --  index of 'hrDeviceEntry' for host system boot device
        --  (usually a disk drive or ROM)
        --  passed as decimal string, NOT as binary value

      * ZP  'hrSystemInitialLoadParameters'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  host system boot parameters (eg, pathname and options)
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')

      * ZM  'hrSystemMaxProcesses'
        --  syntax 'INTEGER (0..2147483647)'
        --  max number of process contexts supported on host system
        --  or zero (if no fixed limit)
        --  passed as decimal string, NOT as binary value

        --  Storage group of IETF HR MIB (RFC 2790)
      * SX  'hrStorageIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of host system storage conceptual row
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index

      * SY  'hrStorageType'
        --  syntax 'OBJECT IDENTIFIER'
        --  (see 'hrStorageTypes' in IETF HR MIB)
        --  type of host system storage

XCMI Working Group  File 10hosttc               [Page 92]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  passed as dotted decimal OID or as storage type label

      * SD  'hrStorageDescr'
        --  syntax 'DisplayString (SIZE (0..64))'
        --  (NVT ASCII string)
        --  textual description of host system storage,
        --  including the type and instance of the storage
        --  passed as ASCII string, NOT as localized string

      * SU  'hrStorageAllocationUnits'
        --  syntax 'INTEGER (1..2147483647)'
        --  (size in bytes)
        --  size of allocation units on host system storage
        --  passed as decimal string, NOT as binary value

      * SS  'hrStorageSize'
        --  syntax 'INTEGER (1..2147483647)'
        --  (size in allocation units)
        --  size in 'hrStorageAllocationUnits' of host system storage
        --  passed as decimal string, NOT as binary value

        --  Device table in Device group of IETF HR MIB (RFC 2790)
      * DX  'hrDeviceIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of host system device conceptual row
        --  (REQUIRED for 'deviceCreate')
        --  passed as decimal string, NOT as binary index

      * DY  'hrDeviceType'
        --  syntax 'OBJECT IDENTIFIER'
        --  (see 'hrDeviceTypes' in IETF HR MIB)
        --  type of host system device
        --  (certain device types make related table entries MANDATORY)
        --  passed as dotted decimal OID or as device type label
        --  (eg, 'hrDevicePrinter'), NOT as binary 'OBJECT IDENTIFIER'

      * DD  'hrDeviceDescr'
        --  syntax 'DisplayString' (SIZE (0..64))
        --  (NVT ASCII string)
        --  textual description of host system device,
        --  including manufacturer and revision, and
        --  (optionally) serial number
        --  passed as ASCII string, NOT as localized string

      * DI  'hrDeviceID'
        --  syntax 'ProductID'
        --  (manufacturer defined object identifier)
        --  product ID of host system device
        --  passed as dotted decimal OID or as device product ID label
        --  (eg, 'xcmPidStarship20'), NOT as binary object identifier

        --  Processor table in Device group of IETF HR MIB (RFC 2790)
      * PI  'hrProcessorFrwID'
        --  syntax 'ProductID'

XCMI Working Group  File 10hosttc               [Page 93]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  (manufacturer defined object identifier)
        --  product ID of firmware associated with processor device
        --  passed as dotted decimal OID or as firmware product ID label
        --  (for device types 'hrDeviceProcessor' in HR Device table)

        --  Network table in Device group of IETF HR MIB (RFC 2790)
      * NI  'hrNetworkIfIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  (see 'ifIndex' in IETF MIB-II)
        --  index of 'ifEntry' associated with network device
        --  passed as decimal string, NOT as binary index
        --  (for device types 'hrDeviceNetwork' in HR Device table)

        --  Disk Storage table in Device group of IETF HR MIB (RFC 2790)
      * KA  'hrDiskStorageAccess'
        --  syntax 'INTEGER (1..2)' (enumeration)
        --  access (including write-protect) of disk storage device
        --  passed as decimal string or as access enum label
        --  (eg, 'readOnly'), NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * KM  'hrDiskStorageMedia'
        --  syntax 'INTEGER (1..8)' (enumeration)
        --  type of media used in disk storage device
        --  passed as decimal string or as media enum label
        --  (eg, 'hardDisk'), NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * KR  'hrDiskStorageRemoveble'
        --  syntax 'Boolean' (true/false, defined in IETF HR MIB)
        --  indicates if media MAY be removed for disk storage device
        --  (note the spelling error in 'hrDiskStorageRemoveble' !!)
        --  passed as decimal string or as boolean enum label
        --  (eg, 'true'), NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * KC  'hrDiskStorageCapacity'
        --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
        --  total size of disk storage device
        --  passed as decimal string, NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

        --  Partition table in Device group of IETF HR MIB (RFC 2790)
      * XX  'hrPartitionIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of disk storage partition
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * XL  'hrPartitionLabel'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  textual description of disk storage partition
        --  passed in dynamic locale

XCMI Working Group  File 10hosttc               [Page 94]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  (see 'xcmGenCurrentLocalizationIndex')
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * XI  'hrPartitionID'
        --  syntax 'OCTET STRING (SIZE (0..128))'
        --  descriptor (possibly binary) of disk storage partition
        --  passed as hexadecimal string, NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * XS  'hrPartitionSize'
        --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
        --  total size of disk storage partition
        --  passed as decimal string, NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * XF  'hrPartitionFSIndex'
        --  syntax 'INTEGER (0..2147483647)'
        --  (see 'hrFSIndex' in IETF HR MIB)
        --  index of 'hrFSEntry' mounted on disk storage partition
        --  or zero, if none
        --  passed as decimal string, NOT as binary value
        --  (exactly ONE file system MAY be mounted on a partition)
        --  (note that multiple partitions MAY support ONE file system,
        --  but multiple file systems MAY NOT reside on ONE partition)
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

        --  File System table in Device group of IETF HR MIB (RFC 2790)
      * FX  'hrFSIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of file system
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FM  'hrFSMountPoint'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  path name of the root of file system
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FR  'hrFSRemoteMountPoint'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  name or address of server file system is mounted from
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FY  'hrFSType'
        --  syntax 'OBJECT IDENTIFIER'
        --  (see 'hrFSTypes' in IETF HR MIB)
        --  type of file system
        --  passed as dotted decimal OID or as file system type label
        --  (eg, 'hrFSiso9660'), NOT as binary 'OBJECT IDENTIFIER'

XCMI Working Group  File 10hosttc               [Page 95]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FA  'hrFSAccess'
        --  syntax 'INTEGER (1..2)' (enumeration)
        --  access of WHOLE file system (NOT individual files)
        --  passed as decimal string or as access enum label
        --  (eg, 'readOnly'), NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FB  'hrFSBootable'
        --  syntax 'Boolean' (true/false, defined in IETF HR MIB)
        --  indicates if file system is bootable
        --  passed as decimal string or as boolean enum label
        --  (eg, 'true'), NOT as binary value
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

      * FS  'hrFSStorageIndex'
        --  syntax 'INTEGER (0..2147483647)'
        --  (see 'hrStorageIndex' in IETF HR MIB)
        --  index of 'hrStorageEntry' for file system
        --  or zero, if none
        --  passed as decimal string, NOT as binary value
        --  (exactly ONE file system MAY be mounted on a partition)
        --  (note that multiple partitions MAY support ONE file system,
        --  but multiple file systems MAY NOT reside on ONE partition)
        --  (for device types 'hrDeviceDiskStorage' in HR Device table)

        --  Software Running group of IETF HR MIB (RFC 2790)
      * RO  'hrSWOSIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of operating system running software conceptual row
        --  passed as decimal string, NOT as binary index

      * RX  'hrSWRunIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of host system running software conceptual row
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index

      * RN  'hrSWRunName'
        --  syntax 'InternationalDisplayString (SIZE (0..64))'
        --  textual description of running software,
        --  including manufacturer, revision, local name, and
        --  (optionally) serial number
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')

      * RI  'hrSWRunID'
        --  syntax 'ProductID'
        --  (manufacturer defined object identifier)
        --  product ID of running software
        --  passed as dotted decimal OID or as software product ID label
        --  (eg, 'xcmPidStarship20'), NOT as binary object identifier


XCMI Working Group  File 10hosttc               [Page 96]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


      * RF  'hrSWRunPath'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  initial load path (file) of running software
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')

      * RP  'hrSWRunParameters'
        --  syntax 'InternationalDisplayString (SIZE (0..128))'
        --  initial load parameters (arguments) of running software
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')

      * RY  'hrSWRunType'
        --  syntax 'INTEGER (1..4)' (enumeration)
        --  type of running software
        --  passed as decimal string or as software type enum label
        --  (eg, 'application'), NOT as binary value

        --  Software Installed group of IETF HR MIB (RFC 2790)
      * WX  'hrSWInstalledIndex'
        --  syntax 'INTEGER (1..2147483647)'
        --  index of host system installed software conceptual row
        --  (REQUIRED for 'entityCreate')
        --  passed as decimal string, NOT as binary index

      * WN  'hrSWInstalledName'
        --  syntax 'InternationalDisplayString (SIZE (0..64))'
        --  textual description of installed software,
        --  including manufacturer, revision, local name, and
        --  (optionally) serial number
        --  passed in dynamic locale
        --  (see 'xcmGenCurrentLocalizationIndex')

      * WI  'hrSWInstalledID'
        --  syntax 'ProductID'
        --  (manufacturer defined object identifier)
        --  product ID of installed software
        --  passed as dotted decimal OID or as software product ID label
        --  (eg, 'xcmPidStarship20'), NOT as binary object identifier

      * WY  'hrSWInstalledType'
        --  syntax 'INTEGER (1..4)' (enumeration)
        --  type of installed software
        --  passed as decimal string or as software type enum label
        --  (eg, 'application'), NOT as binary value

        --  Color Calibration Information
      * CN  [Color Name - no object mapping]
        --  syntax 'DisplayString (SIZE (2))'
        --  name of a color (color plus level)
        --  color:  C=cyan, M=magenta, Y=yellow, K=Black
        --  color:  R=red, G=green, B=blue
        --  level:  S=shadow, M=midbalance, H=highlight, W=whitepoint

XCMI Working Group  File 10hosttc               [Page 97]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  (eg, 'CN=CS:' specifies a color name of 'cyan-shadow')
        --  (see 'TCxx' system color calibration tests below)
      * CV  [Color Value - no object mapping]
        --  syntax 'INTEGER (0..100)'
        --  value of a color (specified by previous 'CN=xx' element)
        --  (eg, 'CV=20:' specifies a color value of '20')
        --  (see 'TCxx' system color calibration tests below)

        --  SNMP Community Names (for SNMPv1c and SNMPv2c)
      * CO  [Community Name Ordinal - no direct object mapping]
        --  syntax 'Ordinal32'
        --  ordinal for storing the 'CR|CW|CT' value below to an array
        --  (eg, 'CO=1' refers to object 'xcmGenBaseSNMPxxxCommunity')
        --  (see 'CR', 'CW', and 'CT' below)
      * CR  'xcmGenBaseSNMPReadCommunity'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  read community name for SNMP 'Get|GetNext|GetBulk' PDUs
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')
        --  (eg, 'CR=:' clears all read community names)
        --  (eg, 'CR=public:' sets a read community name of 'public')
      * CW  'xcmGenBaseSNMPWriteCommunity'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  write community name for SNMP 'Set|Get|GetNext|GetBulk' PDUs
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')
      * CT  'xcmGenBaseSNMPTrapCommunity'
        --  syntax 'XcmFixedLocaleDisplayString (SIZE (0..255))'
        --  trap community name for SNMP 'Inform|Trap' PDUs
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

        --  Job Data from XCMI Job Monitoring MIB (41jobmon)
      * JA  'xcmJobSubmittingApplication'
        --  syntax 'CodeIndexedStringIndex'
        --  job programmatic originator (as opposed to job human owner)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JC  'xcmJobClientId'
        --  syntax 'XcmGlobalUniqueID'
        --  job client-assigned identifier
        --  passed as dotted decimal string, NOT as a binary OID

      * JD  'xcmDocName'
        --  syntax 'CodeIndexedStringIndex'
        --  document name
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JF  'xcmDocFileName'
        --  syntax 'CodeIndexedStringIndex'
        --  document filename (MAY be used for print-by-reference)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JH  'jobHoldSet' in 'xcmJobStateReasons'
        --  syntax 'TruthValue'
        --  job hold (for creating job with held-by-user condition)
        --  passed as '1' (true) or '2' (false), NOT as binary value

XCMI Working Group  File 10hosttc               [Page 98]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


      * JM  'xcmJobMessageFromAdministrator'
        --  syntax 'CodeIndexedStringIndex'
        --  job message from system administrator
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JN  'xcmJobName'
        --  syntax 'CodeIndexedStringIndex'
        --  job name
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JO  'xcmJobOwner'
        --  syntax 'CodeIndexedStringIndex'
        --  job human owner (as opposed to job programmatic originator)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JP  'xcmJobPriority'
        --  syntax 'INTEGER (0..100)'
        --  job priority (0=unspecified, 1=lowest, 100=highest)
        --  passed as decimal string, NOT as binary index

      * JR  'xcmJobRetentionPeriod'
        --  syntax 'Cardinal32'
        --  job retention period (in seconds after completion)
        --  passed as decimal string, NOT as binary value

      * JS  'xcmJobServiceType'
        --  syntax 'XcmJMJobServiceTypeOID' (OBJECT IDENTIFIER)
        --  job service type
        --  passed as dotted decimal OID or as job service type label
        --  (eg, 'xcmJobServicePrintOID'),
        --  NOT as binary 'OBJECT IDENTIFIER'

      * JT  'xcmJobProcessAfter'
        --  syntax 'DateAndTime'
        --  job process after calendar date and time
        --  passed as dotted decimal string (ie, 'yyyy.mm.dd.hh.mm.ss'),
        --  NOT as binary value

      * JU  'xcmJobComment'
        --  syntax 'CodeIndexedStringIndex'
        --  job comment from user (eg, for banner sheet)
        --  passed in fixed locale (see 'xcmGenFixedLocalizationIndex')

      * JW  ['system job' standard type - no object mapping]
        --  syntax 'DisplayString'
        --  'system job' standard type (standardized below)
        --  (REQUIRED for 'deviceJobCreate')
        --  passed as ASCII string, NOT as localized string
        --  (copied to 'xcmJobName', unless 'JN' tag is specified)

      * JX  ['system job' extended type - no object mapping]
        --  syntax 'DisplayString'
        --  'system job' extended type (freeform, no standards)

XCMI Working Group  File 10hosttc               [Page 99]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        --  (OPTIONAL for 'deviceJobCreate')
        --  passed as ASCII string, NOT as localized string
        --  (appended to 'xcmJobName', unless 'JN' tag is specified)

        XCMI standard 'system job' types for use in 'JW' arguments
        (in 'xcmHrDevMgmtCommandData' and 'xcmSimpleJobMgmtData') and
        for the value of 'xcmJobName' (unless 'JN' tag is specified)
        are as follows:

        --  Accounting Reports
      * ACCT    (basic) accounting report
      * AEXT    (extended) accounting report

        --  Configuration Reports
      * CONF    (basic) system configuration report
      * CEXT    (extended) system configuration report
      * CMEM    (installed) memory configuration report
      * CMSR    media (supported and ready) configuration report
      * CNET    network interfaces configuration report
      * COPT    (installed) optional devices configuration report
      * CPDL    (JCL and/or PDL) interpreters configuration report
      * CPRO    network protocols configuration report
      * CSWI    (installed) software configuration report

        --  Demos
      * DEMO    (basic) demo job
      * DEXT    (extended) demo job

        --  Font Reports
      * FONT    (basic) fonts report
      * FEXT    (extended) fonts report
      * FPCL    (installed) HP PCL fonts report
      * FPSX    (installed) Adobe PostScript fonts report

        --  List Directories and/or Files
        --  See section 3.4.1 'List Directory (LIST) Requests'
        --  in XCMI Ext to Host Resources TC.
      * LIST    list tree of disk directories (but NOT contents)
      * LALL    list tree of disk directories (including all files)
      * LDIR    list (specific) disk directory
      * LERR    list system error file
      * LLOG    list system log file
      * LFIL    list (specific) file

        --  Local UI Menu Reports
      * MENU    (basic) local UI menu tree report
      * MEXT    (extended) local UI menu tree report

        --  Document Resources Reports
      * RSRC    (basic) document resources report
      * REXT    (extended) document resources report

        --  System Tests
      * TEST    (basic) system test

XCMI Working Group  File 10hosttc              [Page 100]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

      * TEXT    (extended) system test
      * TMEM    (installed) memory verfication test report
      * TNET    network interfaces verification test report
      * TOPT    (installed) optional devices test report
      * TPAT    print test pattern (especially for printers and copiers)
      * TPDL    (JCL and/or PDL) interpreters system test report
      * TPRO    network protocols verification test report
      * TSWI    (installed) software verfication test report

        --  System Color Calibration Tests
      * TCAC    print automatic color chart (auto calibration)
      * TCBC    print balance chart (manual calibration)
      * TCCC    print corrected color chart (color calibration)
      * TCSC    scan automatic color chart (auto calibration)
      * TCTC    print tone chart (manual calibration)
      * TCUC    print uncorrected color chart (color calibration)
      * TCBV    set balance values (manual calibration)
      * TCTV    set tone values (manual calibration)

        --  User Reports
      * USER    (basic) configured users report
      * UEXT    (extended) configured users report

        The above XCMI standard 'tags' MAY be extended in the future."
    REFERENCE
        "See:   Section 4 'Print Utilities' (pages 71 to 212) of
                POSIX Sys Admin (IEEE 1387.4 / Draft 8, October 1994).
        See:    'hrDeviceStatus' in the Device group of the
                IETF Host Resources MIB (RFC 2790).
        See:    Section 3.4 'XCMI Standard Tagged Management Data' and
                Section 3.5 'Simple Device Management Requests' in
                XCMI Ext to Host Resources TC.
        See:    Section 3.5.3 'Secure Simple Device Mgmt Requests' in
                XCMI Security TC."
    SYNTAX      OCTET STRING (SIZE (2))

XcmHrDevPowerModeType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A device power mode type, used by system administrators
        of this device for power management details.

        Usage:  Used in 'devicePowerModeType' Device Detail, to clearly
        identify the referenced power mode (without resort to strings)."
    SYNTAX      INTEGER {
        other(1),                       -- other power mode type
        unknown(2),                     -- unknown power mode type
        --  XCMI simple device power modes, supported in
        --  Device Calendar, Device Mgmt, and Device Power groups via
        --  'XcmHrDevMgmtCommandRequest' and 'XcmHrDevInfoConditions'
        readyMode(3),                   -- 'warmUp|powerToReady' in
                                        -- 'XcmHrDevMgmtCommandRequest'
        standbyMode(4),                 -- 'coolDown|powerToStandby' in
                                        -- 'XcmHrDevMgmtCommandRequest'

XCMI Working Group  File 10hosttc              [Page 101]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        sleepMode(5),                   -- 'energySave|powerToSleep' in
                                        -- 'XcmHrDevMgmtCommandRequest'
        offMode(6)                      -- 'shutdown|quiesce' in
                                        -- 'XcmHrDevMgmtCommandRequest'
        --  XCMI advanced device power modes, supported in
        --  Device Detail group via
        --  'XcmHrDevDetailType' of 'devicePowerModeType'
        --  ...to be supplied
    }

XcmHrDevPowerTimeUnit ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "A device power cycle time unit, used by system administrators
        of this device for power management cycle times.

        Usage:  Used to scale the values in the Device Power group, for
        convenience and (optional) high resolution."
    SYNTAX      INTEGER {
        other(1),                       -- other time unit
        unknown(2),                     -- unknown time unit
        microsecond(3),                 -- 1 microsecond
        millisecond(4),                 -- 1 millisecond
        second(5),                      -- 1 second
        kilosecond(6),                  -- 1 kilosecond
        megasecond(7),                  -- 1 megasecond
        minute(8),                      -- 1 minute
        hour(9),                        -- 1 hour
        day(10),                        -- 1 day
        week(11),                       -- 1 week
        month(12),                      -- 1 month
        year(13)                        -- 1 year
    }

XcmHrDevTrafficUnit ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The type of traffic unit used to measure input and/or output
        traffic for this device.

        Usage:  The use of either 'other' or 'unknown' is uninformative
        and SHOULD be avoided by conforming implementations.

        Usage:  'mediaImage' - SHOULD be used ONLY for softcopy
                INPUT page images (scan, copy, fax, etc.).
                'mediaImpression' - SHOULD be used ONLY for hardcopy
                OUTPUT page impressions (print, copy, fax, etc.)
                'mediaSheet' - SHOULD be used ONLY for hardcopy
                OUTPUT and does NOT always equal output pages
                (e.g., duplex or N-up printing)."
    SYNTAX      INTEGER {
        other(1),                       -- other traffic unit         
        unknown(2),                     -- unknown traffic unit       
        binaryBit(11),                  -- 1 bit

XCMI Working Group  File 10hosttc              [Page 102]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        binaryNibble(12),               -- 4 bits
        binaryOctet(13),                -- 8 bits
        binaryLine(14),                 -- 1 to N bits (eg, video line)
        textCharacter(15),              -- 5 to 8 bits
        textWord(16),                   -- 1 to N characters
        textLine(17),                   -- 1 to N characters
        textSentence(18),               -- 1 to N words
        textParagraph(19),              -- 1 to N sentences
        mediaBlock(20),                 -- 1 media-specific block
        mediaSector(21),                -- 1 media-specific sector
        mediaRow(22),                   -- 1 media-specific row
        mediaColumn(23),                -- 1 media-specific column
        mediaPacket(24),                -- 1 media-specific packet
        mediaCell(25),                  -- 1 media-specific cell
        mediaImage(26),                 -- 1 media-specific image
        mediaImpression(27),            -- 1 media-specific impression
        mediaSheet(28),                 -- 1 media-specific sheet
        lengthInch(29),                 -- 1 English inch
        lengthFoot(30),                 -- 1 English foot
        lengthYard(31),                 -- 1 English yard
        lengthMile(32),                 -- 1 English mile
        lengthMicrometer(33),           -- 1 micrometer
        lengthMillimeter(34),           -- 1 millimeter
        lengthCentimeter(35),           -- 1 centimeter
        lengthMeter(36),                -- 1 meter
        lengthKilometer(37),            -- 1 kilometer
        volumeMicroliter(38),           -- 1 microliter
        volumeMilliliter(39),           -- 1 milliliter
        volumeLiter(40),                -- 1 liter
        volumeKiloliter(41),            -- 1 kiloliter
        weightMicrogram(42),            -- 1 microgram
        weightMilligram(43),            -- 1 milligram
        weightGram(44),                 -- 1 gram
        weightKilogram(45),             -- 1 kilogram
        areaSqInch(50),                 -- 1 square inch
        areaSqFoot(51),                 -- 1 square Foot
        areaSqYard(52),                 -- 1 square Yard
        areaSqMile(53),                 -- 1 square Mile
        areaSqMicrometer(54),           -- 1 square Micrometer
        areaSqMillimeter(55),           -- 1 square Millimeter
        areaSqCentimeter(56),           -- 1 square Centimeter
        areaSqMeter(57),                -- 1 square Meter
        areaSqKilometer(58),            -- 1 square Kilometer
        areaSheet(59),                  -- Area in "sheets" 
        media100Image(60),              -- 100 media-specific image
        media100Impression(61),         -- 100 media-specific impression
        media100Sheet(62),              -- 100 media-specific sheet
        length100Foot(63),              -- 100 English feet
        length100Meter(64),             -- 100 meter (a hectometer)
        area100SqFoot(65),              -- 100 square Feet

        area10SqMeter(66),              -- 10 square Meters 

--      Note that 10 sqMeters = 107.584 sqFeet.

XCMI Working Group  File 10hosttc              [Page 103]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      The area of a "sheet" is defined as the area in square meters 
--      divided by 16 rounded to the nearest integer but at least 1.

        area100Sheet(67),               -- 100 times area of a sheet
        document(68),                   -- 1 document

        -- Per Tom Friedl 6/17/2014
        gpsOneHundredThousandthsOfDegrees(70),

        inkStick(100),                   -- 1 = one ink stick
        totalItemsConsumed(101) ,

        -- Per Tom Friedl 8/5/2014 102 through 105

         percent(102),
         capacityInKBytes(103),
         capacityInMegabytes(104),
         capacityInGigabytes(105)


    }

XcmHrGroupSupport ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The terse conformance statement of ALL mandatory, conditionally
        mandatory, and optional IETF Host Resources MIB (RFC 2790)
        and XCMI Ext to Host Resources MIB objects which are
        supported by this management agent implementation (ie, version)
        on this host system, specified in a bit-mask.

        The current set of values (which MAY be extended in the future)
        is given below:

        --  IETF Host Resources MIB object groups
              1 : hrSystemGroup                 -- 2**0
              2 : hrStorageGroup                -- 2**1
              4 : hrDeviceGroup                 -- 2**2
              8 : hrSWRunGroup                  -- 2**3
             16 : hrSWRunPerfGroup              -- 2**4
             32 : hrSWInstalledGroup            -- 2**5
        --  XCMI Ext to Host Resources MIB object groups
             64 : xcmHrDevInfoGroup             -- 2**6
            128 : xcmHrDevHelpGroup             -- 2**7
            256 : xcmHrDevMgmtGroup             -- 2**8
            512 : xcmHrDevPowerGroup            -- 2**9
           1024 : xcmHrDevTrafficGroup          -- 2**10
           2048 : xcmHrSystemFaultGroup         -- 2**11
           4096 : xcmHrGeneralGroup             -- 2**12
           8192 : xcmHrDevCalendarGroup         -- 2**13
          16384 : xcmHrSWRunGroup               -- 2**14
          32768 : xcmHrSWInstalledGroup         -- 2**15
          65536 : xcmHrDevDetailGroup           -- 2**16
         131072 : xcmHrStorageExtGroup          -- 2**17

XCMI Working Group  File 10hosttc              [Page 104]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

         262144 : xcmHrStorageDetailGroup       -- 2**18
         524288 : xcmHrDevCoverGroup            -- 2**19
        1048576 : xcmHrDevAlertGroup            -- 2**20
        2097152 : xcmHrConsoleScreenGroup       -- 2**21
        4194304 : xcmHrConsoleTabGroup          -- 2**22
        --  IETF Host Resources MIB tables for specific device types
       33554432 : hrProcessorTable              -- 2**25
       67108864 : hrNetworkTable                -- 2**26
      134217728 : hrPrinterTable                -- 2**27
      268435456 : hrDiskStorageTable            -- 2**28
      536870912 : hrPartitionTable              -- 2**29
     1073741824 : hrFSTable                     -- 2**30

        -- 2**31 NOT used, due to 'Integer32|Cardinal32' semantics

        Usage:  Conforming management agents SHALL accurately
        report their support for IETF Host Resources MIB (RFC 2790)
        and XCMI Ext to Host Resources MIB object groups."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XcmHrSWRunXStatus ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "An extended software status, used by system administrators and
        end users of this software (here, read 'state' for 'status').

        Note:   This extended software status is present for future
        extensions."
    REFERENCE
        "See:   'hrSWRunStatus' in the basic Software Running Group
        of the IETF Host Resources MIB (RFC 2790)."
    SYNTAX      INTEGER {
        none(0),
        other(1),
        unknown(2)
    }

XcmHrStorageDetailType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The type of the storage detail information specified
        in this conceptual row in the 'xcmHrStorageDetailTable'.

        Usage:  Used to describe system-, program-, or thread-level
        memory allocations/reservations.

        Usage:  'hrStorageEntry' and (optionally) 'xcmHrStorageEntry'
        MAY be referenced via 'xcmSecServiceHrStorageIndex' in the
        Service group of the XCMI Security MIB.

        Usage:  Conforming management stations and management agents
        SHALL implement specified semantics for storage detail types."

--    * 'other'

XCMI Working Group  File 10hosttc              [Page 105]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'unknown'
--
--      -   Storage general info
--    * 'storageName'
--      - storage administrative name in directory (primary name)
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCOInternetDNS')
--      - data - '...ValueString'
--      - (eg, 'showstopper.sample.com')
--    * 'storageAlias'
--      - storage administrative alias in directory (alternate name)
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCOInternetDNS')
--      - data - '...ValueString'
--      - (eg, 'LaserRat')
--    * 'storageType'
--      - storage type
--      - see - 'hrStorageType' in IETF HR MIB
--      - type - (OBJECT IDENTIFIER)
--      - data - '...ValueOID'
--      - (eg, 'hrStorageRam')
--    * 'storageDescription'
--      - storage description
--      - see - 'hrStorageDescr' in IETF HR MIB
--      - type - (XcmFixedLocaleDisplayString)
--      - data - '...ValueString'
--      - (eg, 'RAM Memory')
--    * 'storageAllocationUnits'
--      - storage allocation block size (in octets)
--      - type - (Cardinal32) 'hrStorageAllocationUnits'
--      - data - '...ValueInteger'
--      - (eg, '4096')
--    * 'storageTree'
--      - storage tree prefix to name/alias in directory
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCONetwareNDS')
--      - data - '...ValueString'
--      - (MAY also appear in 'storageName')
--    * 'storageContext'
--      - storage context prefix to name/alias in directory
--      - type - (XcmFixedLocaleDisplayString)
--      - subtype - '...ValueOID' (directory in XCMI Comms Config TC)
--      - (eg, 'xcmCONetwareNDS')
--      - data - '...ValueString'
--      - (MAY also appear in 'storageName')
--
--      -   System/Program/Thread storage details
--    * 'storageInputBuffer'
--      - network or standard input buffer size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'

XCMI Working Group  File 10hosttc              [Page 106]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageOutputBuffer'
--      - network or standard output buffer size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageImageBuffer'
--      - frame buffer size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageMarkerBuffer'
--      - marker buffer size (for hardcopy)
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storagePageBuffer'
--      - interpreter buffer size (for softcopy)
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageTranslationBuffer'
--      - translation/localization buffer size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageWorkingBuffer'
--      - working buffer size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--
--      -   Interpreter storage details
--    * 'storageFontCache'
--      - interpreter font cache size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageFormCache'
--      - interpreter form cache size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageLogoCache'
--      - interpreter logo cache size

XCMI Working Group  File 10hosttc              [Page 107]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageMacroCache'
--      - interpreter macro cache size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageStyleCache'
--      - interpreter style cache size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--
--      -   Program/Thread storage details
--    * 'storageHeapMemory'
--      - program/thread heap memory size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storagePrefixMemory'
--      - program/thread prefix memory size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageStackMemory'
--      - program/thread stack memory size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--    * 'storageWorkingMemory'
--      - program/thread working memory size
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - positive integer = size in 'hrStorageAllocationUnits'
--      - zero = no size specified
--
--      -   Storage addressing details
--    * 'storageBaseAddress'
--      - storage base address (physical or logical)
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - (eg, '0xF800')
--    * 'storageWordSize'
--      - storage addressability (word size in octets)
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - (eg, '4')

XCMI Working Group  File 10hosttc              [Page 108]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

--    * 'storagePageSize'
--      - storage page size (in octets)
--      - type - (Cardinal32)
--      - data - '...ValueInteger'
--      - (eg, '8192')
    REFERENCE
        "See:   'xcmHrStorageDetailUnit' for units of storage detail."
    SYNTAX      INTEGER {
        other(1),
        unknown(2),
        --  Storage general info
        storageName(3),                 -- storage name (primary name)
        storageAlias(4),                -- storage alias (other name)
        storageType(5),                 -- storage type (R/W)
        storageDescription(6),          -- storage description (R/W)
        storageAllocationUnits(7),      -- storage allocation block size
        storageTree(8),                 -- storage directory tree
        storageContext(9),              -- storage context
        --  System/Program/Thread storage details
        storageInputBuffer(10),         -- network or standard input
        storageOutputBuffer(11),        -- network or standard output
        storageImageBuffer(12),         -- frame buffer
        storageMarkerBuffer(13),        -- marker buffer (hardcopy)
        storagePageBuffer(14),          -- interpreter buffer (softcopy)
        storageTranslationBuffer(15),   -- translate/localize buffer
        storageWorkingBuffer(16),       -- working buffer
        --  Interpreter storage details
        storageFontCache(20),           -- interpreter font cache
        storageFormCache(21),           -- interpreter form cache
        storageLogoCache(22),           -- interpreter logo cache
        storageMacroCache(23),          -- interpreter macro cache
        storageStyleCache(24),          -- interpreter style cache
        --  Program/Thread storage details
        storageHeapMemory(30),          -- program/thread heap memory
        storagePrefixMemory(31),        -- program/thread prefix memory
        storageStackMemory(32),         -- program/thread stack memory
        storageWorkingMemory(33),       -- program/thread working memory
        --  Storage addressing details
        storageBaseAddress(40),         -- storage base address
        storageWordSize(41),            -- storage addressability
        storagePageSize(42)             -- storage page size
    }

XcmHrStorageRealization ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "An extended storage type (or storage 'realization'),
        used by system administrators and end users of this storage.

        Usage:  The use of either 'other' or 'unknown' is uninformative
        and SHOULD be avoided by conforming implementations.

      * 'physicalSystem' - 'real' memory installed on a 'system'
        whose product is found via 'xcmHrStorageProductDeviceIndex' and

XCMI Working Group  File 10hosttc              [Page 109]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        whose CPU is found via 'xcmHrStoragePlatformDeviceIndex' and
        whose self is found via 'xcmHrStorageMatchingDeviceIndex';
      * 'physicalProgram' - 'real' memory assigned to a 'program'
        (memory which is 'pinned' and is NOT paged to disk storage)
        whose program is found via 'xcmHrStorageSWRunIndex';
      * 'physicalThread' - 'real' memory assigned to a 'thread'
        (memory which is 'pinned' and is NOT paged to disk storage)
        whose program/thread is found via 'xcmHrStorageSWRunIndex';
      * 'logicalSystem' - 'virtual' memory assigned to a 'system'
        (memory which is NOT 'pinned' and MAY be paged to disk storage)
        whose product is found via 'xcmHrStorageProductDeviceIndex' and
        whose CPU is found via 'xcmHrStoragePlatformDeviceIndex' and
        whose self is found via 'xcmHrStorageMatchingDeviceIndex';
      * 'logicalProgram' - 'virtual' memory assigned to a 'program'
        (memory which is NOT 'pinned' and MAY be paged to disk storage)
        whose program is found via 'xcmHrStorageSWRunIndex';
      * 'logicalThread' - 'virtual' memory assigned to a 'thread'
        (memory which is NOT 'pinned' and MAY be paged to disk storage)
        whose program/thread is found via 'xcmHrStorageSWRunIndex'."
    REFERENCE
        "See:   'XcmHrDevInfoRealization' textual convention in
                the XCMI Ext to Host Resources TC.
        See:    'xcmHrDevInfoRealization' in the Device Info group of
                the XCMI Ext to Host Resources MIB."
    SYNTAX      INTEGER {
        other(1),                       -- other storage       
        unknown(2),                     -- unknown storage     
        physicalSystem(10),             -- 'real' system storage
        physicalProgram(11),            -- 'real' program storage
        physicalThread(12),             -- 'real' thread storage
        logicalSystem(20),              -- 'virtual' system storage
        logicalProgram(21),             -- 'virtual' program storage
        logicalThread(22)               -- 'virtual' thread storage
    }

XcmHrDpaAvailability ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The generic availability of this system, device, service, etc."
    REFERENCE
        "See:   Section 9.1.6.6 '[Generic attribute] Availability' and
                Annex A 'id-val-availability-...'
                in DPA (ISO/IEC 10175-1 Final Text, March 1996)."
    --  The following enum values are identical to the final arcs of
    --  the ISO DPA 'id-val-availability-...' OIDs
    SYNTAX      INTEGER {
        high(1),
        normal(2),
        low(3),
        none(5),
        unknown(6)
    }



XCMI Working Group  File 10hosttc              [Page 110]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

XcmHrDpaConditions ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The generic conditions (ie, state reasons) of this system,
        device, service, etc, specified in a bit-mask.

        --  DPA - Service level operations
        --  See section D.2.3 of DPA Mgmt Service (ISO 10175-3)
        --  and section 4 of POSIX DPA Client (IEEE 1387.4)
              1 : cleanedByOperator             -- 2**0
              2 : cleanedBySystem               -- 2**1
                --  all jobs deleted by operator/system
                --  'serviceClean' in 'XcmSvcMonServiceMgmtOperation'
                --  'pdclean' in POSIX DPA Client
              4 : disabledByOperator            -- 2**2
              8 : disabledBySystem              -- 2**3
                --  all new jobs rejected by system
                --  'serviceDisable' in 'XcmSvcMonServiceMgmtOperation'
                --  'pddisable' in POSIX DPA Client
             16 : pausedByOperator              -- 2**4
             32 : pausedBySystem                -- 2**5
                --  all existing job output suspended on system
                --  'servicePause' in 'XcmSvcMonServiceMgmtOperation'
                --  'pdpause' in POSIX DPA Client
             64 : shutdownByOperator            -- 2**6 - 'pdshutdown'
            128 : shutdownBySystem              -- 2**7 - 'pdshutdown'
                --  service state is 'terminating', then 'unavailable'
                --  'serviceShutdown' in 'XcmSvcMonServiceMgmtOperation'
                --  'pdshutdown' in POSIX DPA Client

        --  XCMI - Service level extended operations
            256 : diagnosedByOperator           -- 2**8
            512 : diagnosedBySystem             -- 2**9
                --  'serviceDiagnose' in 'XcmSvcMonServiceMgmtOperation'
           1024 : resetByOperator               -- 2**10
           2048 : resetBySystem                 -- 2**11
                --  'serviceReset[Cold|Warm|Factory]'
                --  in 'XcmSvcMonServiceMgmtOperation'
           4096 : startedByOperator             -- 2**12
           8192 : startedBySystem               -- 2**13
                --  'service[Create|Install|Upgrade|Restart]'
                --  in 'XcmSvcMonServiceMgmtOperation'

        --  XCMI - Document service activities (during 'ready' state)
          65536 : activeCopy                    -- 2**16
         131072 : activePrint                   -- 2**17
         262144 : activeScan                    -- 2**18
         524288 : activeFaxReceive              -- 2**19
        1048576 : activeFaxSend                 -- 2**20
        2097152 : activeFileReceive             -- 2**21
        4194304 : activeFileSend                -- 2**22
        8388608 : activeMailReceive             -- 2**23
       16777216 : activeMailSend                -- 2**24
       33554432 : activeImageProcess            -- 2**25

XCMI Working Group  File 10hosttc              [Page 111]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

       67108864 : activeOCR                     -- 2**26
      134217728 : activeDistribute              -- 2**27

        Usage:  The above 'conditions' augment the service state in
        'xcmSvcMonService[Current|Previous]State' and the service mgmt
        information in 'xcmSvcMonServiceMgmt[Operation|InProgress]'.

        Usage:  Conforming management agents SHALL report all
        'conditions' of entities accurately.  'Conditions' occur within
        or across 'states' in a finite state machine implementation of a
        system, device, service, etc.

        Usage:  A service with 'xcmSvcMonServiceCurrentState' of
        'ready(1)' might have 'xcmSvcMonServiceConditions' of
        'disabledByOperator', indicating that the service will not
        accept new jobs.

        Usage:  Multi-bit examples of 'xcmSvcMonServiceConditions' are
        'disabledByOperator' concurrently with 'pausedByOperator' and
        'activePrint' concurrently with 'activeMailSend'."
    REFERENCE
        "See:   Section 9.5.4 'Server-state',
                section 9.1.6.4 '[Generic attribute] State', and
                Annex A 'id-val-state-...'
                in DPA (ISO/IEC 10175-1 Final Text, March 1996).
        See:    Section D.2.3 'Server State Transitions'
                in DPA Mgmt Service (ISO 10175-3 Draft, October 1996).
        See:    Section 4 'Printing Utilities - Command Line Interface'
                in POSIX DPA Client (IEEE 1387.4, October 1994)."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XcmHrDpaJobValidateSupport ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The job validation support of this system, service, etc,
        specified in a bit-mask.

        The current set of values (which MAY be extended in the future)
        is given below:

            --  ISO DPA standard values
              1 : validateAndProcess    -- generalized from DPA 'print'
              2 : validateSubmitOnly    -- error check, do NOT process
            --  XCMI standard values
              4 : validateSyntaxOnly    -- check syntax only
              8 : validateSemanticsOnly -- check syntax/ranges/states
             16 : validateLocalOnly     -- check semantic/local services
             32 : validateDistributed   -- check distributed services
             64 : validateCreateLocal   -- create local child jobs
            128 : validateCreateRemote  -- create remote child jobs

        Usage:  Conforming management agents SHALL accurately
        report their support for job validation modes."
    REFERENCE

XCMI Working Group  File 10hosttc              [Page 112]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

        "See:   Section 9.5.10 'Job-validates-supported' (server),
                section 9.2.4.12 'Job-validate' (job), and
                Annex A 'id-val-job-validate-...'
                in DPA (ISO/IEC 10175-1 Final Text, March 1996)."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XcmHrDpaObjectClassSupport ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The object class support of this system, service, etc,
        specified in a bit-mask.

        The current set of values (which MAY be extended in the future)
        is given below:

            --  ISO DPA standard values
              1 : generic                       -- 2**0
              2 : job                           -- 2**1
              4 : printer                       -- 2**2
              8 : server                        -- 2**3
             16 : medium                        -- 2**4
             32 : font                          -- 2**5
            256 : transferMethod                -- 2**8
            512 : deliveryMethod                -- 2**9
           1024 : auxiliarySheet                -- 2**10
           2048 : finishing                     -- 2**11
           4096 : output                        -- 2**12
           8192 : imposition                    -- 2**13
          16384 : scheduler                     -- 2**14
          32768 : document                      -- 2**15
          65536 : resource                      -- 2**16
         131072 : initialValueJob               -- 2**17
         262144 : initialValueDocument          -- 2**18
         524288 : resourceContext               -- 2**19
        1048576 : auxiliarySheetPackage         -- 2**20
            --  XCMI standard values
       16777216 : deviceHostSystem              -- 2**24
       33554432 : deviceScanner                 -- 2**25
       67108864 : deviceCopier                  -- 2**26
      134217728 : deviceFax                     -- 2**27
      268435456 : deviceMailbox                 -- 2**28
      536870912 : deviceFinisher                -- 2**29
     1073741824 : deviceCRU                     -- 2**30

        -- 2**31 NOT used, due to 'Integer32|Cardinal32' semantics

        Usage:  Conforming management agents SHALL accurately
        report their support for object classes (ISO DPA and XCMI)."
    REFERENCE
        "See:   Section 9.5.5 'Object-classes-supported' (server),
                section 9.1.6.1 'Object-class' (system),
                Annex A 'id-oc-...'
                in DPA (ISO/IEC 10175-1 Final Text, March 1996)."
    SYNTAX      INTEGER (0..2147483647)  -- biggest int = 2**31-1

XCMI Working Group  File 10hosttc              [Page 113]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


XcmHrDpaState ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The generic state of this object (system, device, service,
        etc.).  The following standard values are defined (in section
        9.1.6.4 'State' of ISO 10175-1):

      * 'ready' - This object is ready to be used without human
        intervention.
      * 'onRequest' - This object requires human intervention in order
        to be used.
      * 'unavailable' - This object is NOT available for use even with
        human intervention.
      * 'unknown' - This state of this object is NOT known.
      * 'busy' - This object is temporarily inaccessible due to dynamic
        constraints, but will become 'ready' without human intervention.
      * 'initializing' - This object is being initialized (and is
        therefore temporarily inaccessible).
      * 'terminating' - This object is being terminated (and is
        therefore permanently inaccessible)."
    REFERENCE
        "See:   Section 9.1.6.4 '[Generic attribute] State' and
                Annex A 'id-val-state-...'
                in DPA (ISO/IEC 10175-1 Final Text, March 1996)."
    --  The following enum values are identical to the final arcs of
    --  the ISO DPA 'id-val-state-...' OIDs
    SYNTAX      INTEGER {
        ready(1),
        onRequest(2),
        unavailable(3),
        unknown(4),
        busy(5),
        initializing(6),
        terminating(7)
    }


XcmHrSuppliesClassTC ::= TEXTUAL-CONVENTION
    STATUS    current
    DESCRIPTION
       "The type of a supply."
    SYNTAX    INTEGER {
       other(1),
       unknown(2),
       replenishable(3),     -- Parts a customer will have
                             -- on hand such as staples
       customerReplacable(4),-- CRUs
       serviceReplacable(5), -- HFSIs
       rarelyReplaced(6),    -- Service can order these parts.
       notReplacable(7)      -- Parts that don't wear out
    }



XCMI Working Group  File 10hosttc              [Page 114]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

XcmHrDetailTableEnumTC ::= TEXTUAL-CONVENTION
    STATUS    current
    DESCRIPTION
       "The table referenced by a row in the xcmHrDetail
       table.  Add additional tables as details are
       required."
    SYNTAX    INTEGER {
       suppliesTable(1),        -- A detail for xcmHrSuppliesTable
       markerSuppliesTable(2),  -- A detail for prtMarkerSuppliesTable
       finisherSuppliesTable(3) -- A detail for finSuppliesTable
    }

XcmHrConsoleDefaultService ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The default service shown on the console user interface."
    SYNTAX      INTEGER {
        copyService(1),
        scanService(2),
        faxService(3),
        printService(4)
    }


--
--          The HRX TC Dummy Group (DO NOT USE)
--
--          DO NOT USE - Present to suppress compiler warnings ONLY!
--
--          Note:  The following objects have 'odd' use of case in their
--          names (ie, 'xCm...'), in order to make obvious their related
--          textual conventions

xCmHrDummy          OBJECT IDENTIFIER ::= { xcmHrTC 999 }

xCmHrDevCalendarDayOfWeek OBJECT-TYPE
    SYNTAX      XcmHrDevCalendarDayOfWeek
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 1 }

xCmHrDevCalendarTimeOfDay OBJECT-TYPE
    SYNTAX      XcmHrDevCalendarTimeOfDay
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 2 }

xCmHrDevDetailType OBJECT-TYPE
    SYNTAX      XcmHrDevDetailType
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"

XCMI Working Group  File 10hosttc              [Page 115]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    ::= { xCmHrDummy 3 }

xCmHrDevDetailUnitClass OBJECT-TYPE
    SYNTAX      XcmHrDevDetailUnitClass
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 4 }

xCmHrDevInfoRealization OBJECT-TYPE
    SYNTAX      XcmHrDevInfoRealization
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 5 }

xCmHrDevInfoStatus OBJECT-TYPE
    SYNTAX      XcmHrDevInfoStatus
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 6 }

xCmHrDevInfoXStatus OBJECT-TYPE
    SYNTAX      XcmHrDevInfoXStatus
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 7 }

xCmHrDevInfoConditions OBJECT-TYPE
    SYNTAX      XcmHrDevInfoConditions
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 8 }

xCmHrDevInfoXConditions OBJECT-TYPE
    SYNTAX      XcmHrDevInfoXConditions
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 9 }

xCmHrDevMgmtCommandRequest OBJECT-TYPE
    SYNTAX      XcmHrDevMgmtCommandRequest
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 10 }

xCmHrDevMgmtCommandData OBJECT-TYPE
    SYNTAX      XcmHrDevMgmtCommandData
    MAX-ACCESS  not-accessible

XCMI Working Group  File 10hosttc              [Page 116]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 11 }

xCmHrDevMgmtCommandDataTag OBJECT-TYPE
    SYNTAX      XcmHrDevMgmtCommandDataTag
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 12 }

xCmHrDevPowerModeType OBJECT-TYPE
    SYNTAX      XcmHrDevPowerModeType
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 13 }

xCmHrDevPowerTimeUnit OBJECT-TYPE
    SYNTAX      XcmHrDevPowerTimeUnit
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 14 }

xCmHrDevTrafficUnit OBJECT-TYPE
    SYNTAX      XcmHrDevTrafficUnit
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 15 }

xCmHrGroupSupport OBJECT-TYPE
    SYNTAX      XcmHrGroupSupport
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 16 }

xCmHrSWRunXStatus OBJECT-TYPE
    SYNTAX      XcmHrSWRunXStatus
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 17 }

xCmHrStorageDetailType OBJECT-TYPE
    SYNTAX      XcmHrStorageDetailType
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 18 }

xCmHrStorageRealization OBJECT-TYPE

XCMI Working Group  File 10hosttc              [Page 117]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    SYNTAX      XcmHrStorageRealization
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 19 }

xCmHrDpaAvailability OBJECT-TYPE
    SYNTAX      XcmHrDpaAvailability
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 20 }

xCmHrDpaConditions OBJECT-TYPE
    SYNTAX      XcmHrDpaConditions
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 21 }

xCmHrDpaJobValidateSupport OBJECT-TYPE
    SYNTAX      XcmHrDpaJobValidateSupport
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 22 }

xCmHrDpaObjectClassSupport OBJECT-TYPE
    SYNTAX      XcmHrDpaObjectClassSupport
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 23 }

xCmHrDpaState OBJECT-TYPE
    SYNTAX      XcmHrDpaState
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 24 }

xCmHrDetailTableEnumTC OBJECT-TYPE
    SYNTAX      XcmHrDetailTableEnumTC
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 25 }

xCmHrSuppliesClassTC OBJECT-TYPE
    SYNTAX      XcmHrSuppliesClassTC
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 26 }

XCMI Working Group  File 10hosttc              [Page 118]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


xCmHrConsoleDefaultService OBJECT-TYPE
    SYNTAX      XcmHrConsoleDefaultService
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Dummy - DO NOT USE"
    ::= { xCmHrDummy 27 }
END















































XCMI Working Group  File 10hosttc              [Page 119]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



5.  Acknowledgements

--
--


6.  References

See section 6 'References' in the XCMI General TC (06gentc).  



































XCMI Working Group  File 10hosttc              [Page 120]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



7.  Security Considerations

Security issues are addressed in the Device Mgmt group, in
'xcmHrDevMgmt[User|Operator|Admin]Password' objects.  

Security issues are addressed via the XCMI Security MIB, in
'xcmSecUser[Name|Index]', 'xcmSecUser[Password|Passcode]' and
'xcmSec[Config|Account|User]MgmtData' objects.  


8.  Authors' Addresses


        XCMI Editors
Email:  coherence@crt.xerox.com

--
--

























XCMI Working Group  File 10hosttc              [Page 121]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.  Supplement

This section provides guidance and examples for SNMP implementors
(management station or management agent) of the following MIBs:  

1)  IETF Host Resources (HR) MIB (RFC 2790); and 
    
2)  XCMI Extensions to IETF Host Resources (HRX) TC/MIB
    (10hosttc/11hostx).  

See the XCMI MIB Implementer's Guide (XMIG) for implementation guidance
for all of XCMI.  This section enhances the XMIG.  In cases of
incompatible requirements, the XMIG SHALL take precedence.  




9.1.  XCMI Supplement to IETF Host Resources MIB



9.1.1.  IETF HR System (Mandatory)

This object group contains seven (7) leaf objects (with a fixed instance
qualifier of zero, by IETF SMI rules), zero (0) table objects, zero (0)
index objects, and zero (0) columnar objects.  

This object group extends the information provided by the System group
of the IETF MIB-II (RFC 1213).  

Conformance:  Implementation of the IETF HR System group is MANDATORY
for conformance to the IETF HR MIB (RFC 2790).  

Therefore, all XCMI conforming management agents SHALL implement the
IETF HR System group.  

Note:  The Printer MIB v1 (RFC 1759) SHOULD have required conformance to
the entire IETF HR MIB (RFC 2790) as a prerequisite and THEN stated its
specific dependencies on the Device and Storage groups.  However, the
Printer MIB v1 (RFC 1759) defined a non-standard compliance profile for
the IETF HR MIB (RFC 2790).  This is a technical defect in the Printer
MIB v1 (RFC 1759) and is NOT relevant for XCMI conformance!  

Examples of System group objects:

hrSystemUptime.0                        = 12437
    --  syntax 'TimeTicks' (hundredths of seconds since an epoch)
    --  defval { 0 }                    - initial system uptime
    --  time since this host system was last initialized
    --  compare with 'sysUpTime' in IETF MIB-II (NMS subsystem uptime)
    --  (note - spelling inconsistent with 'sysUpTime' in IETF MIB-II)


XCMI Working Group  File 10hosttc              [Page 122]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


hrSystemDate.0                          = 0x07cc0307090d00002b0000
                                        --  YearMoDyHrMiSeDe__UhUm
                                        --  7 March 1996 9:13am UTC +0hr
    --  syntax 'DateAndTime' (8-octet and 11-octet forms)
    --  defval { '0000000000000000'H }  - no system date
    --  local date and time on this host system
    --  XCMI conforming management agents SHOULD use the 11-octet form
    --  (note - 'DateAndTime' is now defined in SNMPv2-TC, RFC 2579)

hrSystemInitialLoadDevice.0             = 3
    --  syntax 'INTEGER (1..2147483647)'
    --  defval omitted                  - boot device in 'hrDeviceTable'
    --  (see - 'hrDeviceIndex' in IETF HR MIB)
    --  index of 'hrDeviceEntry' for host system boot device
    --  (usually a disk drive or ROM)
    --  XCMI conforming management agents SHALL report boot devices

hrSystemInitialLoadParameters.0         = '/dev/boot_image'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval { ''H }                  - no system load paramaters
    --  host system boot parameters (eg, pathname and options)

hrSystemNumUsers.0                      = 0
    --  syntax 'Gauge'
    --  defval { 0 }                    - no authenticated users
    --  number of authenticated user sessions on this host system

hrSystemProcesses.0                     = 14
    --  syntax 'Gauge'
    --  defval { 0 }                    - no process contexts
    --  number of process contexts loaded or running on this host system

hrSystemMaxProcesses.0                  = 0
    --  syntax 'INTEGER (0..2147483647)'
    --  defval { 0 }                    - no max process contexts
    --  max number of process contexts supported on this host system
    --  or zero (if no fixed limit)

















XCMI Working Group  File 10hosttc              [Page 123]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.2.  IETF HR Storage (Mandatory)

This object group contains one (1) leaf object (with a fixed instance
qualifier of zero, by IETF SMI rules), one (1) table object (standard in
IETF MIBs), one (1) index object (which should NOT be read by
convention), and six (6) columnar objects (with positive, non-zero
instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Storage group is MANDATORY
for conformance to the IETF HR MIB (RFC 2790).  

Therefore, all XCMI conforming management agents SHALL implement the
IETF HR Storage group.  

Note:  The Printer MIB v1 (RFC 1759) SHOULD have required conformance to
the entire IETF HR MIB (RFC 2790) as a prerequisite and THEN stated its
specific dependencies on the Device and Storage groups.  However, the
Printer MIB v1 (RFC 1759) defined a non-standard compliance profile for
the IETF HR MIB (RFC 2790).  This is a technical defect in the Printer
MIB v1 (RFC 1759) and is NOT relevant for XCMI conformance!  

Examples of Storage group objects:

hrMemorySize.0                          = 4096
    --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
    --  defval { 0 }                    - no physical main memory
    --  physical main memory on this host system

hrStorageType.1                         = hrStorageRam
    --  syntax 'OBJECT IDENTIFIER'
    --  defval omitted                  - storage type
    --  (see - 'hrStorageTypes' in IETF HR MIB)
    --  (see - section 'Usage of hrStorageType and hrStorageDescr' in
    --  XCMI HRX TC for detailed usage/conformance requirements)
    --  type of this host system storage

hrStorageDescr.1                        = 'RAM Memory'
    --  syntax 'DisplayString (SIZE (0..64))' (NVT ASCII string)
    --  defval omitted                  - storage description
    --  (see - section 'Usage of hrStorageType and hrStorageDescr' in
    --  XCMI HRX TC for detailed usage/conformance requirements)
    --  textual description of this host system storage,
    --  including the type and size of the storage

hrStorageAllocationUnits.1              = 1
    --  syntax 'INTEGER (1..2147483647)' (size in bytes)
    --  defval omitted                  - storage allocation units
    --  size of allocation units on this host system storage

hrStorageSize.1                         = 67108864
    --  syntax 'INTEGER (1..2147483647)' (size in allocation units)
    --  defval omitted                  - storage size

XCMI Working Group  File 10hosttc              [Page 124]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    --  size in 'hrStorageAllocationUnits' of this host system storage

hrStorageUsed.1                         = 56246336
    --  syntax 'INTEGER (0..2147483647)' (size in allocation units)
    --  defval { ''H }                  - no storage used
    --  size in 'hrStorageAllocationUnits' of used host system storage

hrStorageAllocationFailures.1           = 0
    --  syntax 'Counter'
    --  defval { 0 }                    - no storage allocation failures
    --  number of allocation failures for this host system storage


9.1.2.1.  Usage of hrStorageType and hrStorageDescr

Conformance:  All XCMI conforming management agents:  

1)  SHALL place 'hrStorageRam' in 'hrStorageType' of the first row in
    'hrStorageTable' (at 'hrStorageIndex' of '1') and SHALL place '1' in
    'hrStorageAllocationUnits' for this RAM storage for interworking
    with third-party tools which (naively) read 'hrStorageSize' of the
    first storage on a system (but do NOT read
    'hrStorageAllocationUnits') and display it as 'memory' size; 
    
2) SHALL conform to the following requirements on the content of
    'hrStorageType'; and 
    
3)  SHALL conform to the following requirements on the content of
    'hrStorageDescr'.  


Conformance for 'hrStorageType' - XCMI conforming management agents:  

1)  SHALL implement 'hrStorageType' of 'hrStorageRam' at
    'hrStorageIndex' of '1'; 
    
2)  SHALL implement 'hrStorageType' of 'hrStorageFixedDisk' at
    'hrStorageIndex' of '2' (if they have a hard disk); and 
    
3)  SHALL implement 'hrStorageType' of other values in the relative
    order shown in the following example.  


Conformance for 'hrStorageDescr' - XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrStorageDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrStorageDescr'); 
    
2)  SHALL place a storage description (eg, 'RAM Memory'), corresponding
    to the specific storage type (eg, 'hrStorageRam'), first in each
    'hrStorageDescr' instance; 
    
    3)  SHOULD NOT place a size description (eg, '64 MB') 

XCMI Working Group  File 10hosttc              [Page 125]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

second in each 'hrStorageDescr' instance (after a hyphen), because this
    is REDUNDANT with the 'hrStorageSize' object; 
    
4)  SHALL NOT place manufacturer, product, model, or serial number in
    any 'hrStorageDescr' instance (use corresponding 'hrDeviceDescr'
    instead); and 
    
5)  SHALL NOT place disk partition information (eg, '/dev/sd0b' path) in
    any 'hrStorageDescr' instance (use corresponding 'hrPartitionLabel' 
    instead).  


Formal ABNF syntax for 'hrStorageDescr' follows:  

hrStorageDescr  = sto_type              -- storage type
                + [' - ' sto_size]      -- storage size

                --  All component values in English ONLY
sto_type        = storage type from 'hrStorageType'
sto_size        = storage size in kilobytes/megabytes/gigabytes


Examples of 'hrStorageDescr' values:

hrStorageDescr.1                = 'RAM Memory'
hrStorageDescr.2                = 'Fixed Disk'
hrStorageDescr.3                = 'Floppy Disk'
hrStorageDescr.4                = 'ROM Memory'
hrStorageDescr.5                = 'Virtual Memory'


9.1.2.2.  Usage of hrStorageTable

See:  Section 'Usage of hrStorageType and hrStorageDescr' in this XCMI
HRX TC for detailed usage/conformance requirements.  

Example of 'hrStorageTable':

--  SHALL be main RAM memory for all agents (for interworking)
hrStorageType.1                 = hrStorageRam
hrStorageDescr.1                = 'RAM Memory'
hrStorageAllocationUnits.1      = 1
hrStorageSize.1                 = 67108864
hrStorageUsed.1                 = 56246336
hrStorageAllocationFailures.1   = 0

--  SHALL be main hard disk for all agents (for interworking)
hrStorageType.2                 = hrStorageFixedDisk
hrStorageDescr.2                = 'Fixed Disk'
hrStorageAllocationUnits.2      = 8192
hrStorageSize.2                 = 262144
hrStorageUsed.2                 = 131072
hrStorageAllocationFailures.2   = 0


XCMI Working Group  File 10hosttc              [Page 126]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


--  SHOULD be main floppy disk for all agents (if present)
hrStorageType.3                 = hrStorageFloppyDisk
hrStorageDescr.3                = 'Floppy Disk'
hrStorageAllocationUnits.3      = 512
hrStorageSize.3                 = 2847
hrStorageUsed.3                 = 0
hrStorageAllocationFailures.3   = 0

--  SHOULD be main ROM memory for all agents (if present)
hrStorageType.4                 = hrStorageOther (no type for ROM)
hrStorageDescr.4                = 'ROM Memory'
hrStorageAllocationUnits.4      = 512
hrStorageSize.4                 = 128
hrStorageUsed.4                 = 94
hrStorageAllocationFailures.4   = 0

--  SHOULD be virtual memory for all agents (if present)
hrStorageType.5                 = hrStorageVirtualMemory
hrStorageDescr.5                = 'Virtual Memory'
hrStorageAllocationUnits.5      = 8192
hrStorageSize.5                 = 131072
hrStorageUsed.5                 = 6453
hrStorageAllocationFailures.5   = 0

--  SHOULD be other storage types at higher 'hrStorageIndex' values





























XCMI Working Group  File 10hosttc              [Page 127]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.3.  IETF HR Device (Mandatory)

This object group contains zero (0) leaf objects, seven (7) table
objects (nonstandard in IETF MIBs), three (3) index objects (which
should NOT be read by convention), and twenty-six (26) columnar objects 
(with positive, non-zero instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Device group is MANDATORY
for conformance to the IETF HR MIB (RFC 2790).  

Therefore, all XCMI conforming management agents SHALL implement the
IETF HR Device group.  

Note:  The Printer MIB v1 (RFC 1759) SHOULD have required conformance to
the entire IETF HR MIB (RFC 2790) as a prerequisite and THEN stated its
specific dependencies on the Device and Storage groups.  However, the
Printer MIB v1 (RFC 1759) defined a non-standard compliance profile for
the IETF HR MIB (RFC 2790).  This is a technical defect in the Printer
MIB v1 (RFC 1759) and is NOT relevant for XCMI conformance!  


9.1.3.1.  IETF HR Device Table (Mandatory)

This object table contains zero (0) leaf objects, one (1) index object
(which should NOT be read by convention), and five (5) columnar objects 
(with positive, non-zero instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Device table (Device group)
is MANDATORY for conformance to the IETF HR MIB (RFC 2790).  

Therefore, all XCMI conforming management agents SHALL implement the
IETF HR Device table.  

Example of 'hrDeviceDescr' for a 'physical printer' device with all
required, recommended, and optional components:

hrDeviceDescr.1 =
    'Xerox DocuCentre 230 ST v1.0 - 64 MB - Printer - AN2078BZ102'
    |      |          |      |      |       |         |
    vendor product    model  rev    size    type      serial number


Examples of Device table objects:

hrDeviceType.1          = hrDevicePrinter
    --  syntax 'OBJECT IDENTIFIER'
    --  defval omitted                  - device type
    --  (see - 'hrDeviceTypes' in IETF HR MIB)
    --  (see - section 'Usage of hrDeviceType and hrDeviceDescr' in
    --  XCMI HRX TC for detailed usage/conformance requirements)
    --  type of this host system device
    --  (certain device types make related table entries MANDATORY)

XCMI Working Group  File 10hosttc              [Page 128]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


hrDeviceDescr.1         = 'Xerox DocuCentre 230 ST v1.0 - Printer'
    --  syntax 'DisplayString (SIZE (0..64))' (NVT ASCII string)
    --  defval omitted                  - device description
    --  (see - The XCMI MIB Implementer's Guide and the section 
    --  'Usage of hrDeviceType and hrDeviceDescr' in
    --  XCMI HRX TC for detailed usage/conformance requirements)

hrDeviceID.1            = xcmPidDC230STV1
    --  syntax 'ProductID' (manufacturer defined object identifier)
    --  defval { zeroDotZero }    - no device product ID
    --  product ID of this host system device
    --  XCMI conforming management agents on network printers
    --  SHALL set 'hrDeviceID' for the printer device in this table
    --  to a value from the XCMI Product ID TC (93pidtc.mib) and SHALL
    --  set the SAME value in 'sysObjectID' in IETF MIB-II (RFC 1213),
    --  unless 'sysObjectID' represents an 'external print server'

hrDeviceStatus.1        = 2 (running)
    --  syntax 'INTEGER (1..5)' (enumeration)
    --  defval { unknown(1) }           - no device status
    --  (see - XCMI MIB Implementer's Guide)
    --  current operational state of this host system device

hrDeviceErrors.1        = 0
    --  syntax 'Counter'
    --  defval { 0 }                    - no device errors
    --  number of errors detected on this host system device


9.1.3.1.1.  Usage of hrDeviceType and hrDeviceDescr

Conformance:  All XCMI conforming management agents:  

1)  SHALL place 'hrDevicePrinter' in 'hrDeviceType' of the first row in 
    'hrDeviceTable' (at 'hrDeviceIndex' of '1') for interworking with
    third-party tools which (naively) read 'hrDeviceStatus' of the first
    device on a system (but do NOT read 'hrDeviceType') and display it
    as 'printer' status (unless they don't implement a network printer);
    
2) SHALL conform to the following requirements on the content of
    'hrDeviceType'; and 
    
3)  SHALL conform to the following requirements on the content of
    'hrDeviceDescr'.  


Conformance for 'hrDeviceType' - XCMI conforming management agents:  

1)  SHALL implement 'hrDeviceType' of 'hrDevicePrinter' at
    'hrDeviceIndex' of '1' (if they have a network printer); 
    
2)  SHALL implement 'hrDeviceType' of 'hrDeviceProcessor' at
    'hrDeviceIndex' of '2' (for their host system 'main CPU'); and 

XCMI Working Group  File 10hosttc              [Page 129]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    
3)  SHALL implement 'hrDeviceType' of other values in the relative order
    shown in the following example.  


Conformance for 'hrDeviceDescr' (for device type 'xcmHrDeviceScanner') -
XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHALL place a product manufacturer (eg, 'Xerox') first in each
    'hrDeviceDescr' instance; 
    
3)  SHALL place color capability (eg, 'Color' or 'B&W') second in each
    'hrDeviceDescr' instance; 
    
4)  SHALL place 'Scanner' third in each 'hrDeviceDescr' instance; 
    
5)  SHALL place the maximum rated auto document feeder ppm (eg, '32ppm')
    fourth in each 'hrDeviceDescr' instance; 
    
6)  SHALL place the auto document feeder name (eg, 'Auto Doc Handler')
    fifth in each 'hrDeviceDescr' instance; 
    
7)  SHALL place the scanner resolution in DPI units (eg, '600x600dpi')
    sixth in each 'hrDeviceDescr' instance; 
    
Examples of 'hrDeviceDescr' for device type 'xcmHrDeviceScanner':

hrDeviceDescr.1         = 'Xerox Color Scanner, 65ppm Auto Doc 
                           Feeder 600x600 dpi'
hrDeviceDescr.2         = 'Xerox B&W Scanner, 32ppm, Duplex Auto 
                           Doc Handler, 600x600 dpi'

Conformance for 'hrDeviceDescr' (for device type 'xcmHrDeviceFax') -
XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHALL place a product manufacturer (eg, 'US Robotics ') first in
    each 'hrDeviceDescr' instance; 
    
3)  SHALL place line speed in Kbps(eg, '33.6Kbps') second in each
    'hrDeviceDescr' instance; 
    
4)  SHALL place the protocol supported (eg, 'V.34') third in each
    'hrDeviceDescr' instance; 
    
5)  SHALL place the FAX resolution in units of DPI (eg, '400x400dpi')
    fourth in each 'hrDeviceDescr' instance; 

XCMI Working Group  File 10hosttc              [Page 130]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    
6)  SHALL place the area code-phone number with parentheses [eg,
    '(585-123-1234)'] fifth in each 'hrDeviceDescr' instance OR if
    multiple phone lines exist SHALL place the number of phones lines
    fifth in each 'hrdDeviceDescr' (eg, '2 analog lines'); 
    

Examples of 'hrDeviceDescr' for device types 'xcmHrDeviceFax',
'xcmHrDeviceInternetFax', 'xcmHrDeviceServerFax' and
'xcmHrDeviceEmbeddedFax' 

Please note the xcmHrDeviceFax is maintained for legacy
products only. 

hrDeviceDescr.1         = 'US Robotics FAX Modem 33.6 Kbps V.34 
                           400x400dpi (585-422-0096)' 
hrDeviceDescr.2         = 'US Robotics FAX Modem 33.6 Kbps V.34 
                           400x400dpi 2 analog lines'

Conformance for 'hrDeviceDescr' (for device type 'xcmHrDeviceFinisher')
- XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHALL place a product manufacturer (eg, 'Xerox') first in each
    'hrDeviceDescr' instance; 
    
3)  SHALL place a product model name (eg, 'High Capacity Finisher')
    second in each 'hrDeviceDescr' instance; 
    
4)  SHALL place the finishing options supported (eg, '(fold, staple,
    trim, stack)') third in each 'hrDeviceDescr' instance; 
    

Examples of 'hrDeviceDescr' for device type 'xcmHrDeviceFinisher'

hrDeviceDescr.1         = 'Xerox High Capacity Finisher
                           (staple, stacker, hole punch, fold)'
hrDeviceDescr.2         = 'Bourg Professional Booklet Maker 
                          (fold, staple, trim, stack)'

Conformance for 'hrDeviceDescr' (for device type 'hrDeviceDiskStorage') 
- XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHOULD place a product manufacturer / vendor name (eg, 'Seagate')
    first in each 'hrDeviceDescr' instance; 
    


XCMI Working Group  File 10hosttc              [Page 131]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

3)  SHOULD place a product model name (eg, 'Barracuda') second in each
    'hrDeviceDescr' instance; 
    
4)  SHOULD place a product model number (eg, '7200.7') third in each
    'hrDeviceDescr' instance; 
    
5)  SHOULD place a product firmware version (eg, 'v3.06') fourth in each
    'hrDeviceDescr' instance; 
    
6)  SHOULD place a product part number (eg, 'PN-9W2005-311') fifth in
    each 'hrDeviceDescr' instance; 
    


Examples of 'hrDeviceDescr' for device type 'hrDeviceDiskStorage':

hrDeviceDescr.1         = 'Seagate Barracuda 7200.7 Model-ST340014A 
                           v3.06 PN-9W2005-311'
hrDeviceDescr.2         = 'Western Digital Model-AC34000-00LA 
                           vA2.11 May97 PN-ACMCBYVYOMB'


Conformance for 'hrDeviceDescr' (for all other 'physical' devices not
listed above) - XCMI conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of
    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHALL place a product manufacturer name (eg, 'Xerox') first in each
    'hrDeviceDescr' instance; 
    
3)  SHALL place a product name (eg, 'DocuCentre') second in each
    'hrDeviceDescr' instance; 
    
4)  SHALL place a product model (eg, '230 ST') third in each
    'hrDeviceDescr' instance; 
    
5)  MAY place a product revision (eg, 'v1.0') fourth in each
    'hrDeviceDescr' instance; 
    
6)  MAY place a size description (eg, '64 MB') fifth in each
    'hrDeviceDescr' instance (after a hyphen); 
    
7)  SHOULD place a device description (eg, 'Printer'), corresponding to
    the specific device type (eg, 'hrDevicePrinter'), sixth in each
    'hrDeviceDescr' instance (after a hyphen); and 
    
8)  MAY place a product serial number (eg, 'AH2078BZ102') seventh in
    each 'hrDeviceDescr' instance (after a hyphen).  

Note_1:  Use of 'xcmHrDevInfoName' in 'xcmHrDevInfoTable' (or
'deviceName' in 'xcmHrDevDetailType' of 'xcmHrDevDetailTable') of the
XCMI HRX MIB is RECOMMENDED in ADDITION to 'hrDeviceDescr', since the

XCMI Working Group  File 10hosttc              [Page 132]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

name can be localized into the installed device locale.  

Note_2:  Use of 'xcmHrDevInfoSerialNumber' in 'xcmHrDevInfoTable' (or
'deviceSerialNumber' in 'xcmHrDevDetailType' of 'xcmHrDevDetailTable')
of the XCMI HRX MIB is RECOMMENDED in ADDITION to 'hrDeviceDescr', since
the serial number can be machine parsed.  


Formal ABNF syntax for 'hrDeviceDescr' (for 'physical' devices) follows:

hrDeviceDescr   = dev_man_name          -- manufacturer name
                + ' ' dev_pro_family    -- product family name
                + ' ' dev_pro_model     -- product model
                + [' ' dev_pro_rev]     -- product revision
                + [[' - ' dev_size] /   -- device (memory) size
                   [' - ' dev_speed]]   -- device (network) speed
                + [' - ' dev_type]      -- device type
                + [' - ' dev_ser_no]    -- device serial number

                --  All component values in English ONLY
dev_man_name    = device manufacturer name (eg, 'Xerox')
dev_pro_family  = device product family name (eg, 'DocuCentre')
dev_pro_model   = device product model (eg, '230 ST')
dev_pro_rev     = device product revision (eg, 'v1.0')
dev_size        = device (memory) size in kilobytes/megabytes/gigabytes
dev_speed       = device (network) speed in kilobits/megabits/gigabits
dev_type        = device type from 'hrDeviceType' (eg, 'Printer')
dev_ser_no      = device serial number (eg, 'AN2078BZ102')


Example of 'hrDeviceDescr' for a 'physical printer' device with all
required, recommended, and optional components:

hrDeviceDescr.1 =
    'Xerox DocuCentre 230 ST v1.0 - 64 MB - Printer - AN2078BZ102'
    |      |          |      |      |       |         |
    vendor product    model  rev    size    type      serial number


Examples of 'hrDeviceDescr' values:

hrDeviceDescr.1         = 'Xerox DocuCentre 230 ST v1.0 - Printer'
hrDeviceDescr.2         = 'Motorola Power PC 601 v1.3 - Processor'
hrDeviceDescr.3         = 'Kingston AZ 1035 v2.3 - RAM Memory'
hrDeviceDescr.4         = 'Sony AB17300 v1.2 - 1.44 MB - Floppy Disk'
hrDeviceDescr.5         = 'AMD ZZ015638 v7.3 - 64 KB - ROM Memory'
hrDeviceDescr.6         = 'Motorola Power PC 601 v1.3 - Coprocessor'


Conformance for 'hrDeviceDescr' (for 'logical' devices) - XCMI
conforming management agents:  

1)  SHALL use only US English text in 'hrDeviceDescr' (due to ASCII
    charset restrictions on the 'DisplayString' type and the lack of

XCMI Working Group  File 10hosttc              [Page 133]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    'language/country' information for 'hrDeviceDescr'); 
    
2)  SHALL place a logical device description (eg, 'Logical Printer'),
    corresponding to the specific device type (eg, 'hrDevicePrinter'),
    first in each 'hrDeviceDescr' instance (after a DOUBLE hyphen); and 
    
3)  SHOULD place logical device defaults (eg, 'Duplex' or 'Staple'),
    corresponding to the specific logical device configuration second in
    each 'hrDeviceDescr' instance (after a SINGLE hyphen).  


Formal ABNF syntax for 'hrDeviceDescr' (for 'logical' devices) follows:

hrDeviceDescr   = '--' log_type         -- logical device type
                + *[' - ' log_default]  -- logical device defaults

                --  All component values in English ONLY
log_type        = logical device type (eg, 'Logical Printer')
log_default     = logical device default (eg, 'Duplex')


Example of 'hrDeviceDescr' for a 'logical printer' device with all
required, recommended, and optional components:

hrDeviceDescr.23 =
    '-- Logical Printer - Duplex - Staple'
    |                   |        |
    logical device      default  default


9.1.3.1.2.  Usage of hrDeviceID

Conformance for 'hrDeviceID' - XCMI conforming management agents:  

1)  SHALL set the network product ID in 'hrDeviceID' (eg, for a network
    printer of device type 'hrDevicePrinter' with 'hrDeviceIndex' of
    '1') with a registered network product ID from the XCMI Product ID
    TC (in a PUBLIC version of the XCMI Product ID TC, 93pidtc); 
    
2)  SHALL set the SAME network product ID in 'sysObjectID' in IETF
    MIB-II (RFC 1213).  

See:  Section 'Usage of sysDescr and sysObjectID' in XCMI General TC.  


9.1.3.1.3.  Usage of hrDeviceTable

See:  Section 'Usage of hrDeviceType and hrDeviceDescr' in this XCMI HRX
TC for detailed usage/conformance requirements.  

Example of 'hrDeviceTable':

--  SHALL be a printer for all agents which implement a network printer
hrDeviceType.1          = hrDevicePrinter

XCMI Working Group  File 10hosttc              [Page 134]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

hrDeviceDescr.1         = 'Xerox DocuCentre 230 ST v1.0 - Printer'
hrDeviceID.1            = xcmPidDC230STV1
hrDeviceStatus.1        = 2 (running)
hrDeviceErrors.1        = 0

--  SHALL be a processor (main CPU) for all agents
hrDeviceType.2          = hrDeviceProcessor
hrDeviceDescr.2         = 'Motorola Power PC 601 v1.3 - Processor'
hrDeviceID.2            = zeroDotZero (unknown)
hrDeviceStatus.2        = 2 (running)
hrDeviceErrors.2        = 0

--  SHALL correspond to 'hrStorageIndex' of '1' (main RAM memory)
hrDeviceType.3          = hrDeviceVolatileMemory
hrDeviceDescr.3         = 'Kingston AZ 1035 v2.3 - RAM Memory'
hrDeviceID.3            = zeroDotZero (unknown)
hrDeviceStatus.3        = 2 (running)
hrDeviceErrors.3        = 0

--  SHALL correspond to 'hrStorageIndex' of '2' (main hard disk)
hrDeviceType.4          = hrDeviceDiskStorage
hrDeviceDescr.4         = 'Maxtor KD 017200A v1.0 - 2.0 GB - Fixed Disk'
hrDeviceID.4            = zeroDotZero (unknown)
hrDeviceStatus.4        = 2 (running)
hrDeviceErrors.4        = 0

--  SHOULD correspond to 'hrStorageIndex' of '3' (main floppy disk)
hrDeviceType.5          = hrDeviceDiskStorage
hrDeviceDescr.5         = 'Sony AB17300 v1.2 - 1.44 MB - Floppy Disk'
hrDeviceID.5            = zeroDotZero (unknown)
hrDeviceStatus.5        = 2 (running)
hrDeviceErrors.5        = 0

--  SHOULD correspond to 'hrStorageIndex' of '4' (main ROM memory)
hrDeviceType.6          = hrDeviceNonVolatileMemory
hrDeviceDescr.6         = 'AMD ZZ015638 v7.3 - 64 KB - ROM Memory'
hrDeviceID.6            = zeroDotZero (unknown)
hrDeviceStatus.6        = 2 (running)
hrDeviceErrors.6        = 0

--  SHOULD be any 'hrDeviceCoprocessor' devices (IOT/IIT/NIC processors)
hrDeviceType.7          = hrDeviceCoprocessor
hrDeviceDescr.7         = 'Motorola Power PC 601 v1.3 - Coprocessor'
hrDeviceID.7            = zeroDotZero (unknown)
hrDeviceStatus.7        = 2 (running)
hrDeviceErrors.7        = 0

--  SHOULD be any 'hrDeviceNetwork' devices (network interfaces)
hrDeviceType.8          = hrDeviceNetwork (see 'ifTable' in MIB-II)
hrDeviceDescr.8         = 'IBM TR Adapter 301 v1.0 - Network Interface'
hrDeviceID.8            = zeroDotZero (unknown)
hrDeviceStatus.8        = 2 (running)
hrDeviceErrors.8        = 0


XCMI Working Group  File 10hosttc              [Page 135]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


--  SHOULD be any 'hrDeviceParallelPort' devices (direct interfaces)

--  SHOULD be any 'hrDeviceSerialPort' devices (direct interfaces)

--  SHOULD be other physical devices at higher 'hrDeviceIndex' values

--  SHOULD be 'hrDevicePrinter|'xcmHrDevice...' devices (job service)

--  SHOULD be 'xcmHrDevice...History' devices (job history)













































XCMI Working Group  File 10hosttc              [Page 136]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.3.1.4.  Usage of Physical and Logical Devices

The IETF HR Device table does not allow the distinction from DPA (ISO
10175) between 'physical' devices (actual hardware on a managed system) 
and 'logical' devices (configured defaults for underlying 'physical'
devices on a managed system).  

However, the XCMI HRX Device Info table allows this distinction to be
made, based on the DPA (ISO 10175) concept of 'realization'.  It is ALSO
possible for a managed system to present ONLY a 'logical' device of a
particular type (where the underlying 'physical' device is off-system).


Example of an actual 'physical printer' device:

--  'hrDeviceTable' in IETF HR MIB (RFC 2790)
hrDeviceType.1          = hrDevicePrinter
                        --  physical printer device in first row
hrDeviceDescr.1         = 'Xerox DocuCentre 230 ST v1.0 - Printer'
                        --  XCMI conforming device description
hrDeviceID.1            = xcmPidDC230STV1
                        --  registered in XCMI ProductID TC (93pidtc)
hrDeviceStatus.1        = 2 (running)
                        --  normal device operating state
hrDeviceErrors.1        = 0
                        --  no device errors encountered

--  'xcmHrDevInfoTable' in XCMI HRX MIB (11hostx)
hrDeviceType.1          = hrDevicePrinter
xcmHrDevInfoRowStatus.1                 = active(1)
                                        --  normal row status
xcmHrDevInfoName.1                      = 'showstopper.sample.com/lpt1:'
                                        --  device administrative name
xcmHrDevInfoSerialNumber.1              = 'AN2078BZ102'
                                        --  device serial number
xcmHrDevInfoRealization.1               = physical(11)
                                        --  physical printer device
xcmHrDevInfoXStatus.1                   = printerIdle(503)
                                        --  device idle (not printing)
xcmHrDevInfoConditions.1                = standbyMode(262144)
                                        --  device standby (power save)
xcmHrDevInfoXConditions.1               = 0
                                        --  no extended conditions
xcmHrDevInfoInstallDate.1               = 0x07cc0307090d00002b0000
                                        --  7 March 1996 9:13am UTC +0hr
xcmHrDevInfoResetDate.1                 = 0x07cc0307090d00002b0000
                                        --  7 March 1996 9:13am UTC +0hr
xcmHrDevInfoNextDeviceIndex.1           = 0
                                        --  no next physical printer
xcmHrDevInfoPreviousDeviceIndex.1       = 0
                                        --  no next physical printer
xcmHrDevInfoPhysicalDeviceIndex.1       = 0

XCMI Working Group  File 10hosttc              [Page 137]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

                                        --  no related physical device
xcmHrDevInfoPriority.1                  = 0
                                        --  default device priority




















































XCMI Working Group  File 10hosttc              [Page 138]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


Example of a corresponding 'logical printer' device:

--  'hrDeviceTable' in IETF HR MIB (RFC 2790)
hrDeviceType.23         = hrDevicePrinter
                        --  logical printer device in higher row
hrDeviceDescr.23        = '-- Logical Printer - Duplex - Staple'
                        --  XCMI conforming device description
hrDeviceID.23           = 0.0
                        --  no device ID
hrDeviceStatus.23       = 2 (running)
                        --  normal device operating state
hrDeviceErrors.23       = 0
                        --  no device errors encountered

--  'xcmHrDevInfoTable' in XCMI HRX MIB (11hostx)
hrDeviceType.23         = hrDevicePrinter
xcmHrDevInfoRowStatus.23                = active(1)
                                        --  normal row status
xcmHrDevInfoName.23                     = 'showstopper.sample.com/lpds:'
                                        --  device administrative name
xcmHrDevInfoSerialNumber.23             = ''
                                        --  no device serial number
xcmHrDevInfoRealization.23              = logical(12)
                                        --  logical printer device
xcmHrDevInfoXStatus.23                  = printerIdle(503)
                                        --  device idle (not printing)
xcmHrDevInfoConditions.23               = 0
                                        --  no device conditions
xcmHrDevInfoXConditions.23              = 0
                                        --  no extended conditions
xcmHrDevInfoInstallDate.23              = 0x07cc0307090d00002b0000
                                        --  7 March 1996 9:13am UTC +0hr
xcmHrDevInfoResetDate.23                = 0x07cc0307090d00002b0000
                                        --  7 March 1996 9:13am UTC +0hr
xcmHrDevInfoNextDeviceIndex.23          = 0
                                        --  no next logical printer
xcmHrDevInfoPreviousDeviceIndex.23      = 0
                                        --  no next logical printer
xcmHrDevInfoPhysicalDeviceIndex.23      = 1
                                        --  related physical device
xcmHrDevInfoPriority.23                 = 50
                                        --  medium device priority


9.1.3.1.5.  Usage of hrDeviceErrors

Conforming management agents that implement IETF HR MIB (RFC 2790), and
ALSO implement the Printer MIB (RFC 1759 or successor), for rows in
'hrDeviceTable' of 'hDeviceType' of 'hrDevicePrinter', SHOULD increment
'hrDeviceErrors' for at least the following conditions:  

(a) those alerts that require Xerox service to resolve (i.e.,
    'prtAlertTrainingLevel' = 'fieldService'); 

XCMI Working Group  File 10hosttc              [Page 139]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

(b) whenever a machine consumable reaches an "End-of-Life"/Empty/Full
    state; 
(c) all printer paper path alerts; and 
(d) those warning alerts which degrade machine performance and require
    user intervention to resolve.  

Conforming management agents that implement IETF HR MIB (RFC 2790), for
rows in 'hrDeviceTable' of 'hDeviceType' of 'xcmHrDeviceHostSystem',
SHOULD increment 'hrDeviceErrors' for at least the following conditions:

(a) all ESS (network controller) software process failures; and 
(b) all network connectivity configuration errors.  

Conforming management agents that implement IETF HR MIB (RFC 2790), for
rows in 'hrDeviceTable' of 'hDeviceType' of 'hrDeviceNetwork', SHOULD
increment 'hrDeviceErrors' for ONLY the following conditions:  

(a) network hardware-related errors.  

Conforming management agents that implement IETF HR MIB (RFC 2790), for
ALL rows in 'hrDeviceTable' of ANY 'hDeviceType', SHOULD increment
'hrDeviceErrors' for at least the following conditions:  

(a) critical alerts (i.e.,'hrDeviceStatus' = 'down') 

Conforming management agents that implement IETF HR MIB (RFC 2790), for
ALL rows in 'hrDeviceTable' of ANY 'hDeviceType', SHOULD NOT increment
'hrDeviceErrors' for the following conditions (which indicate normal
operations or non-critical warnings):  

- machine/CRU power-up
- remote reset initiated
- machine put in offline mode by SA
- opening/closing input trays
- intrusive diagnostics or preventative maintenance modes enabled
- machine put in pause mode
- machine requires money to begin operation
- low CRU capacity warning messages
- CRU reorder warning messages
- software upgrade mode enablement
- etc.  














XCMI Working Group  File 10hosttc              [Page 140]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.3.2.  IETF HR Processor Table (Cond Mandatory)

This  object  table  contains  zero (0) leaf  objects,  zero  (0)  index
objects,  and two (2) columnar objects (with positive, non-zero instance
qualifiers, by IETF SMI rules).  

Conformance:  Implementation  of  the  IETF HR Processor  table  (Device
group)  is  CONDITIONALLY MANDATORY for conformance to the IETF HR  MIB,
for  host  systems which represent one or more devices in the HR  Device
table of type 'hrDeviceProcessor' (ie, CPU).  

However,  all XCMI conforming management agents SHALL implement the IETF
HR Processor table.  

Examples of Processor table objects:

hrProcessorFrwID.3                      = xcmPid???.x.y.z
    --  syntax 'ProductID' (manufacturer defined object identifier)
    --  defval { zeroDotZero }    - no processor f/w product ID
    --  product ID of the firmware associated with this processor
    --  (for devices of type 'hrDeviceProcessor' in HR Device table)
    --  XCMI conforming management agents SHALL represent ALL of their
    --  their processors in HR Device table entries

hrProcessorLoad.3                       = 43
    --  syntax 'INTEGER (0..100)'
    --  defval { 0 }                    - no processor load
    --  over the last minute, percentage of time processor was NOT idle


9.1.3.3.  IETF HR Network Table (Cond Mandatory)

This object table contains zero (0) leaf objects, zero (0) index
objects, and one (1) columnar object (with positive, non-zero instance
qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Network table (Device group)
is CONDITIONALLY MANDATORY for conformance to the IETF HR MIB, for host 
systems which represent one or more devices in the HR Device table of
type 'hrDeviceNetwork' (ie, network interface).  

However, all XCMI conforming management agents SHALL implement the IETF
HR Network table.  

Examples of Network table objects:

hrNetworkIfIndex.4                      = 17
    --  syntax 'INTEGER'
    --  defval omitted                  - network interface index
    --  'ifIndex' in Interface table of IETF MIB-II
    --  associated with this network interface device
    --  (for devices of type 'hrDeviceNetwork' in HR Device table)

XCMI Working Group  File 10hosttc              [Page 141]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    --  XCMI conforming management agents SHALL represent ALL of their
    --  network interfaces in the HR Device and MIB-II Interface tables


9.1.3.4.  IETF HR Printer Table (Cond Mandatory)

This object table contains zero (0) leaf objects, zero (0) index
objects, and two (2) columnar objects (with positive, non-zero instance
qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Printer table (Device group)
is CONDITIONALLY MANDATORY for conformance to the IETF HR MIB, for host 
systems which represent one or more devices in the HR Device table of
type 'hrDevicePrinter'.  

However, all XCMI conforming management agents (which instrument network
printers) SHALL implement the IETF HR Printer table.  

Examples of Printer table objects:

hrPrinterStatus.5                       = 4 (printing)
    --  syntax 'INTEGER (1..5)' (enumeration)
    --  defval omitted                  - printer status
    --  current operational state of this network printer device
    --  (for devices of type 'hrDevicePrinter' in HR Device table)
    --  XCMI conforming management agents SHALL represent ALL of their
    --  network printers in HR Device table entries

hrPrinterDetectedErrorState             = 0x0800 (doorOpen)
    --  syntax 'OCTET STRING (0..2)' (bit-array of error conditions)
    --  defval { '0000'H }              - no printer error state
    --  current error conditions of this network printer device
    --  (note - bits are numbered (0..n) from the MOST significant bit
    --  in each byte in the (currently two bytes) OCTET STRING, per the
    --  IETF HR MIB in SMIv2, RFC 2790


9.1.3.4.1.  Usage of hrPrinterDetectedErrorState

Conformance:  All XCMI conforming management agents (which instrument
network printers):  

1)  SHALL follow the recommendations for the values of 'hrDeviceStatus',
    'hrPrinterStatus', and 'hrPrinterDetectedErrorState' in the XCMI MIB
    Implementer's Guide (XMIG).  
    
1)  SHOULD follow the recommendations for the values of
    'hrDeviceStatus', 'hrPrinterStatus', and
    'hrPrinterDetectedErrorState' in Appendix E 'Overall Printer Status
    Table' of the most recent draft of the Printer MIB v2 (or any
    standards track RFC) from the Printer Working Group as interpretted
    in the XCMI MIB Implementer's Guide; and 
    


XCMI Working Group  File 10hosttc              [Page 142]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

2)  SHALL follow the recommendations for the values of 'hrDeviceStatus' 
    and 'hrPrinterDetectedErrorState' in the IETF HR MIB (RFC 2790) in
    SMIv2 (or any standards track RFC) as interpretted in the XCMI MIB
    Implementer's Guide; 



9.1.3.5.  IETF HR Disk Storage Table (Cond Mandatory)

This object table contains zero (0) leaf objects, zero (0) index
objects, and four (4) columnar objects (with positive, non-zero instance
qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Disk Storage table (Device
group) is CONDITIONALLY MANDATORY for conformance to the IETF HR MIB,
for host systems which represent one or more devices in the HR Device
table of type 'hrDeviceDiskStorage'.  

However, all XCMI conforming management agents (which instrument disk
storage) SHALL implement the IETF HR Disk Storage table.  

Examples of Disk Storage table objects:

hrDiskStorageAccess.6                   = 1 (readWrite)
    --  syntax 'INTEGER (1..2)' (enumeration)
    --  defval omitted                  - disk storage access
    --  access (including write-protect) of this disk storage device
    --  (for devices of type 'hrDeviceDiskStorage' in HR Device table)
    --  XCMI conforming management agents SHALL represent ALL of their
    --  disk storage in HR Device table entries

hrDiskStorageMedia.6                    = 3 (hardDisk)
    --  syntax 'INTEGER (1..8)' (enumeration)
    --  defval omitted                  - disk storage media
    --  type of media used in this disk storage device

hrDiskStorageRemoveble.6                = 2 (false)
    --  syntax 'Boolean' (defined in IETF HR MIB)
    --  defval omitted                  - disk storage removable
    --  indicates if media may be removed for this disk storage device
    --  (note - the spelling error in 'hrDiskStorageRemoveble' !!)

hrDiskStorageCapacity.6                 = 262144
    --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
    --  defval omitted                  - disk storage capacity
    --  total size of this disk storage device


9.1.3.6.  IETF HR Partition Table (Cond Mandatory)

This object table contains zero (0) leaf objects, one (1) index object
(which should NOT be read by convention), and four (4) columnar objects 
(with positive, non-zero instance qualifiers, by IETF SMI rules).  


XCMI Working Group  File 10hosttc              [Page 143]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


Conformance:  Implementation of the IETF HR Partition table (Device
group) is CONDITIONALLY MANDATORY for conformance to the IETF HR MIB,
for host systems which represent one or more devices in the HR Device
table of type 'hrDeviceDiskStorage'.  

However, all XCMI conforming management agents (which instrument disk
storage) SHALL implement the IETF HR Partition table.  

Examples of Partition table objects:

hrPartitionLabel.6.1                    = 'SomePartitionLabel'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval omitted                  - partition label (description)
    --  textual description of this disk storage partition
    --  (for devices of type 'hrDeviceDiskStorage' in HR Device table)
    --  XCMI conforming management agents SHALL represent ALL of their
    --  disk storage partitions in HR Partition table entries

hrPartitionID.6.1                       = SomePartitionDescriptor
    --  syntax 'OCTET STRING (SIZE (0..128))'
    --  defval { ''H }                  - partition ID (descriptor)
    --  descriptor (possibly binary) of this disk storage partition

hrPartitionSize.6.1                     = 4096
    --  defval omitted                  - partition size
    --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
    --  total size of this disk storage partition

hrPartitionFSIndex.6.1                  = 4
    --  syntax 'INTEGER (0..2147483647)'
    --  defval { 0 }                    - partition file system index
    --  (see - 'hrFSIndex' in IETF HR MIB)
    --  index of 'hrFSEntry' mounted on this disk storage partition
    --  or zero, if none
    --  (exactly ONE file system may be mounted on a partition)
    --  (note - multiple partitions may support ONE file system,
    --  but multiple file systems may NOT reside on ONE partition)


9.1.3.7.  IETF HR File System Table (Cond Mandatory)

This object table contains zero (0) leaf objects, one (1) index object
(which should NOT be read by convention), and eight (8) columnar objects
(with positive, non-zero instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR File System table (Device
group) is CONDITIONALLY MANDATORY for conformance to the IETF HR MIB,
for host systems which represent one or more devices in the HR Device
table of type 'hrDeviceStorage'.  

However, all XCMI conforming management agents (which instrument disk
storage) SHALL implement the IETF HR File System table.  


XCMI Working Group  File 10hosttc              [Page 144]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


Examples of File System table objects:

hrFSMountPoint.4                        = 'SomeMountPoint'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval omitted                  - file system mount point (path)
    --  path name mounted as the root of this file system
    --  (for devices of type 'hrDeviceDiskStorage' in HR Device table)
    --  XCMI conforming management agents SHALL represent ALL of their
    --  file systems in HR File System table entries

hrFSRemoteMountPoint.4                  = 'SomeRemoteMountDescription'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval { ''H }                  - file system remote mount point
    --  name and/or address of server this file system is mounted from

hrFSType.4                              = hrFSBFS (UNIX SVR4 Boot FS)
    --  syntax 'OBJECT IDENTIFIER'
    --  defval omitted                  - file system type
    --  (see - 'hrFSTypes' in IETF HR MIB)
    --  type of this file system

hrFSAccess.4                            = 2 (readOnly)
    --  syntax 'INTEGER (1..2)' (enumeration)
    --  defval omitted                  - file system access
    --  access of this WHOLE file system (NOT individual files)

hrFSBootable.4                          = 1 (true)
    --  syntax 'Boolean' (defined in IETF HR MIB)
    --  defval omitted                  - file system bootable
    --  indicates if this file system is bootable

hrFSStorageIndex.4                      = 1
    --  syntax 'INTEGER (0..2147483647)'
    --  defval { 0 }                    - no file system storage index
    --  (see - 'hrStorageIndex' in IETF HR MIB)
    --  index of 'hrStorageEntry' for this file system
    --  or zero, if none

hrFSLastFullBackupDate.4                = 0x07cc0307090d00002b0000
                                        --  YearMoDyHrMiSeDe__UhUm
                                        --  7 March 1996 9:13am UTC +0hr
    --  syntax 'DateAndTime' (8-octet and 11-octet forms)
    --  defval { '0000000000000000'H }  - no last full backup date
    --  date and time of last full backup of this file system
    --  XCMI conforming management agents SHOULD use the 11-octet form
    --  (note - 'DateAndTime' is now defined in SNMPv2-TC, RFC 2579)

hrFSLastPartialBackupDate.4             = 0x07cc0307090d00002b0000
                                        --  YearMoDyHrMiSeDe__UhUm
                                        --  7 March 1996 9:13am UTC +0hr
    --  syntax 'DateAndTime' (8-octet and 11-octet forms)
    --  defval { '0000000000000000'H }  - no last partial backup date
    --  date and time of last partial backup of this file system

XCMI Working Group  File 10hosttc              [Page 145]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

    --  XCMI conforming management agents SHOULD use the 11-octet form
    --  (note - 'DateAndTime' is now defined in SNMPv2-TC, RFC 2579)





















































XCMI Working Group  File 10hosttc              [Page 146]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.4.  IETF HR Software Running (Optional)

This object group contains one (1) leaf object (with a fixed instance
qualifier of zero, by IETF SMI rules), one (1) table object (standard in
IETF MIBs), one (1) index object (which should NOT be read by
convention), and six (6) columnar objects (with positive, non-zero
instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Software Running group is
OPTIONAL for conformance to the IETF HR MIB.  

However, all XCMI conforming management agents SHOULD implement the IETF
HR Software Running group (for customer support and diagnostics).  

Examples of Software Running group objects:

hrSWOSIndex.0                           = 1
    --  syntax 'INTEGER (1..2147483647)'
    --  defval omitted                  - primary OS s/w running index
    --  (see - 'hrSWRunIndex' in IETF HR MIB)
    --  index of 'hrSWRunEntry' for primary operating system

hrSWRunName.4                           = 'Xerox DocuCentre '
                                        + 'NetScan v1.0 - AN2078BZ102'
    --  syntax 'InternationalDisplayString (SIZE (0..64))'
    --  defval omitted                  - s/w running description/name
    --  textual description of this software running component,
    --  including manufacturer, software product name, revision, and
    --  (optionally) serial number
    --  XCMI conforming management agents on network products
    --  SHALL set the SAME value in 'hrSWInstalledName'
    --  (see - section 'Usage of hrSWRunID and hrSWRunName'
    --  in XCMI HRX TC for detailed usage/conformance requirements)

hrSWRunID.4                             = xcmPid???.x.y.z
    --  syntax 'ProductID' (manufacturer defined object identifier)
    --  defval { zeroDotZero }    - no s/w running product ID
    --  product ID of this software running component
    --  XCMI conforming management agents on network products
    --  SHALL set the SAME value in 'hrSWInstalledID'
    --  XCMI conforming management agents on network products
    --  SHALL set 'hrSWRunID' for each software component
    --  to a value derived from the XCMI Product ID TC (93pidtc.mib),
    --  that is, a value subordinate to a registered network product
    --  (see - section 'Usage of hrSWRunID and hrSWRunName'
    --  in XCMI HRX TC for detailed usage/conformance requirements)

hrSWRunPath.4                           = 'SomePath'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval omitted                  - s/w running load path
    --  path used to load this software running component


XCMI Working Group  File 10hosttc              [Page 147]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


hrSWRunParameters.4                     = 'SomeParameters'
    --  syntax 'InternationalDisplayString (SIZE (0..128))'
    --  defval omitted                  - s/w running load parameters
    --  defval { ''H }                  - no s/w running load paramaters
    --  parameters used to load this software running component

hrSWRunType.4                           = 4 -- application
    --  syntax 'INTEGER (1..4)' (enumeration)
    --  defval omitted                  - s/w running type
    --  type of this software running component

hrSWRunStatus.4                         = 1 (running)
    --  syntax 'INTEGER (1..4)' (enumeration)
    --  defval omitted                  - s/w running status
    --  current operational state of this software running component


9.1.4.1.  Usage of hrSWRunID and hrSWRunName

Conformance:  All XCMI conforming management agents:  

1) SHALL conform to the following requirements on the content of
    'hrSWRunID'; and 
    
2)  SHALL conform to the following requirements on the content of
    'hrSWRunName'.  


Conformance for 'hrSWRunID' - XCMI conforming management agents:  

1)  SHALL derive the software product ID in 'hrSWRunID' from a
    registered network product ID from the XCMI Product ID TC (by
    appending a suffix to such a registered network product ID); 
    
2)  SHALL set the SAME software product ID in 'hrSWInstalledID' for the
    same software component.  


Conformance for 'hrSWRunName' - XCMI conforming management agents:  

1)  SHALL set the SAME software name in 'hrSWInstalledName' for the same
    software component; 
    
2)  SHALL place a software manufacturer name (eg, 'Xerox') first in each
    'hrSWRunName' instance; 
    
3)  SHALL place a software product family name (eg, 'DocuCentre') second
    in each 'hrSWRunName' instance (SHALL be the base network product
    family name, eg, 'DocuCentre', found in the 'dev_pro_family' element
    of the ABNF for 'hrDeviceDescr' in the section 'Usage of
    hrDeviceType and hrDeviceDescr'); 
    


XCMI Working Group  File 10hosttc              [Page 148]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

4)  SHALL place a software product common name (eg, 'NetScan') third in
    each 'hrSWRunName' instance 
    
5)  SHALL place a software product revision (eg, 'v1.0') fourth in each
    'hrSWRunName' instance (SHALL match any 'banner message' this
    software component outputs); 
    
6)  MAY place a software product serial number (eg, 'AH2078BZ102') fifth
    in each 'hrSWRunName' instance (after a hyphen).  

Note_1:  Use of 'xcmHrSWRunAdminName' in 'xcmHrSWRunTable' of the XCMI
HRX MIB is RECOMMENDED in ADDITION to 'hrSWRunName', since the name can
be localized into the installed device locale.  


Formal ABNF syntax for 'hrSWRunName' follows:  

hrSWRunName     = sw_man_name           -- software manufacturer name
                + ' ' sw_pro_family     -- software product family name
                + ' ' sw_pro_common     -- software product common name
                + ' ' sw_pro_rev        -- software product revision
                + [' - ' sw_ser_no]     -- software product serial no

                --  All component values SHOULD be in English ONLY
                --  (see discussion above)
sw_man_name     = software manufacturer name (eg, 'Xerox')
sw_pro_family   = software product family name (eg, 'DocuCentre')
sw_pro_common   = software product common name (eg, 'NetScan')
sw_pro_rev      = software product revision (eg, 'v1.0')
sw_ser_no       = software serial number (eg, 'AN2078BZ102')


Example of 'hrSWRunName' for a network scan service with all
required, recommended, and optional components:

hrSWRunName.1 =
    'Xerox DocuCentre NetScan v1.0 - AN2078BZ102'
    |      |          |       |      |
    vendor product    name    rev    serial number
















XCMI Working Group  File 10hosttc              [Page 149]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.5.  IETF HR Software Running Performance (Optional)

This object group contains zero (0) leaf objects, one (1) table object
(standard in IETF MIBs), zero (0) index objects (it augments the HR
Software Running group), and two (2) columnar objects (with positive,
non-zero instance qualifiers, by IETF SMI rules).  

Conformance:  Implementation of the IETF HR Software Running Performance
group is OPTIONAL for conformance to the IETF HR MIB.  

Therefore, all XCMI conforming management agents MAY implement the IETF
HR Software Running Performance group (for customer support and
diagnostics).  

Examples of Software Running Performance group objects:

hrSWRunPerfCPU.4                        = 13
    --  syntax 'INTEGER' (hundredths of seconds)
    --  defval { 0 }                    - no s/w running CPU consumed
    --  hundredths of seconds of CPU consumed by this software running
    --  (on multiprocessor systems, may be GREATER than wall clock time)

hrSWRunPerfMem.4                        = 107
    --  syntax 'KBytes' (kilobytes, defined in IETF HR MIB)
    --  defval { 0 }                    - no s/w running memory consumed
    --  total real system memory allocated to this software running



























XCMI Working Group  File 10hosttc              [Page 150]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.1.6.  IETF HR Software Installed (Optional)

This object group contains two (2) leaf objects
(with a fixed instance qualifier of zero, by IETF SMI rules),
one (1) table object (standard in IETF MIBs),
one (1) index object (which should NOT be read by convention),
and four (4) columnar objects
(with positive, non-zero instance qualifiers, by IETF SMI rules).

Conformance:~~Implementation of the IETF HR Software Installed
group is OPTIONAL for conformance to the IETF HR MIB.

However, all XCMI conforming management agents SHOULD implement the
IETF HR Software Installed group (for customer support and diagnostics).

Examples of Software Installed group objects:

hrSWInstalledLastChange.0               = 35461
    --  syntax 'TimeTicks' (hundredths of seconds since an epoch)
    --  defval { '0000000000000000'H }  - no s/w installed last change
    --  time of last add/rename/delete of any 'hrSWInstalledEntry'
    --  (value of 'sysUpTime' in IETF MIB-II at change)

hrSWInstalledLastUpdate.0               = 0
    --  syntax 'TimeTicks' (hundredths of seconds since an epoch)
    --  defval { '0000000000000000'H }  - no s/w installed last update
    --  time of last COMPLETE update of 'hrSWInstalledTable'
    --  (value of 'sysUpTime' in IETF MIB-II at COMPLETE update)

hrSWInstalledName.4                     = 'SomeSWInstalledName'
    --  syntax 'InternationalDisplayString (SIZE (0..64))'
    --  defval omitted                  - s/w running description/name
    --  textual description of this software installed component,
    --  including manufacturer, software product name, revision, and
    --  (optionally) serial number
    --  XCMI conforming management agents on network products
    --  SHALL set the SAME value in 'hrSWRunName'
    --  (see - section 'Usage of hrSWInstalledID and hrSWInstalledName'
    --  in XCMI HRX TC for detailed usage/conformance requirements)

hrSWInstalledID.4                       = xcmPid???.x.y.z
    --  syntax 'ProductID' (manufacturer defined object identifier)
    --  defval { zeroDotZero }    - no s/w installed product ID
    --  product ID of this software installed component
    --  XCMI conforming management agents on network products
    --  SHALL set the SAME value in 'hrSWRunID'
    --  XCMI conforming management agents on network products
    --  SHALL set 'hrSWInstalledID' for each software component
    --  to a value derived from the XCMI Product ID TC (93pidtc.mib),
    --  that is, a value subordinate to a registered network product
    --  (see - section 'Usage of hrSWInstalledID and hrSWInstalledName'
    --  in XCMI HRX TC for detailed usage/conformance requirements)

XCMI Working Group  File 10hosttc              [Page 151]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       


hrSWInstalledType.4                     = 4 -- application
    --  syntax 'INTEGER (1..4)' (enumeration)
    --  type of this software installed component

hrSWInstalledDate.4                     = 0x07cc0307090d00002b0000
                                        --  YearMoDyHrMiSeDe__UhUm
                                        --  7 March 1996 9:13am UTC +0hr
    --  syntax 'DateAndTime' (8-octet and 11-octet forms)
    --  defval { '0000000000000000'H }  - no s/w installed date
    --  date and time of installation of this software installed
    --  XCMI conforming management agents SHOULD use the 11-octet form
    --  (note - 'DateAndTime' is now defined in SNMPv2-TC, RFC 2579)


9.1.6.1.  Usage of hrSWInstalledID and hrSWInstalledName

Conformance:  All XCMI conforming management agents:  

1) SHALL conform to the following requirements on the content of
    'hrSWInstalledID'; and 
    
2)  SHALL conform to the following requirements on the content of
    'hrSWInstalledName'.  


Conformance for 'hrSWInstalledID' - XCMI conforming management agents:  

1)  SHALL derive the software product ID in 'hrSWInstalledID' from a
    registered network product ID from the XCMI Product ID TC (by
    appending a suffix to such a registered network product ID); 
    
2)  SHALL set the SAME software product ID in 'hrSWRunID' for the same
    software component.  


Conformance for 'hrSWInstalledName' - XCMI conforming management agents:

1)  SHALL set the SAME software name in 'hrSWRunName' for the same
    software component; 
    
2)  SHALL place a software manufacturer name (eg, 'Xerox') first in each
    'hrSWInstalledName' instance; 
    
3)  SHALL place a software product family name (eg, 'DocuCentre') second
    in each 'hrSWInstalledName' instance (SHALL be the base network
    product family name, eg, 'DocuCentre', found in the 'dev_pro_family'
    element of the ABNF for 'hrDeviceDescr' in the section 'Usage of
    hrDeviceType and hrDeviceDescr'); 
    
4)  SHALL place a software product common name (eg, 'NetScan') third in
    each 'hrSWInstalledName' instance 
    


XCMI Working Group  File 10hosttc              [Page 152]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

5)  SHALL place a software product revision (eg, 'v1.0') fourth in each
    'hrSWInstalledName' instance (SHALL match any 'banner message' this
    software component outputs); 
    
6)  MAY place a software product serial number (eg, 'AH2078BZ102') fifth
    in each 'hrSWInstalledName' instance (after a hyphen).  

Note_1:  Use of 'xcmHrSWInstalledAdminName' in 'xcmHrSWInstalledTable'
of the XCMI HRX MIB is RECOMMENDED in ADDITION to 'hrSWInstalledName',
since the name can be localized into the installed device locale.  


Formal ABNF syntax for 'hrSWInstalledName' follows:  

hrSWInstalledName   = sw_man_name       -- software manufacturer name
                    + ' ' sw_pro_family -- software product family name
                    + ' ' sw_pro_common -- software product common name
                    + ' ' sw_pro_rev    -- software product revision
                    + [' - ' sw_ser_no] -- software product serial no

                --  All component values SHOULD be in English ONLY
                --  (see discussion above)
sw_man_name     = software manufacturer name (eg, 'Xerox')
sw_pro_family   = software product family name (eg, 'DocuCentre')
sw_pro_common   = software product common name (eg, 'NetScan')
sw_pro_rev      = software product revision (eg, 'v1.0')
sw_ser_no       = software serial number (eg, 'AN2078BZ102')


Example of 'hrSWInstalledName' for a network scan service with all
required, recommended, and optional components:

hrSWInstalledName.1 =
    'Xerox DocuCentre NetScan v1.0 - AN2078BZ102'
    |      |          |       |      |
    vendor product    name    rev    serial number



















XCMI Working Group  File 10hosttc              [Page 153]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       



9.2.  XCMI Supplement to XCMI Ext to Host Resources MIB

All XCMI conforming management agents which implement the HRX MIB, SHALL
implement the General and Device Info groups in the XCMI HRX MIB.  



9.2.1.  XCMI HRX General (Mandatory)

To be supplied...  











































XCMI Working Group  File 10hosttc              [Page 154]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       

Change Log 
--
--




XCMI Working Group  File 10hosttc              [Page 170]               

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       
                           TABLE OF CONTENTS                            

1.  Introduction ...............................................       2
2.  SNMP Network Management Framework ..........................       3
3.  Managed Object Usage .......................................       3
  3.1.  Overview of Groups in the HRX MIB ......................       3
  3.2.  Relationship to other MIBs .............................      11
    3.2.1.  IETF Host Resources MIB (RFC 2790) .................      11
    3.2.2.  IETF Interfaces Group MIB (RFC 2863) ...............      11
    3.2.3.  Printer MIB (RFC 1759 or successor) ................      11
    3.2.4.  XCMI Standard MIBs .................................      11
    3.2.5.  XCMI Job Monitoring MIB ............................      11
    3.2.6.  XCMI Simple Job Management MIB .....................      12
    3.2.7.  XCMI Service Monitoring MIB ........................      12
    3.2.8.  XCMI System Admin MIB ..............................      12
  3.3.  Definition of Device FSM ...............................      13
    3.3.1.  Device FSM State Diagram ...........................      13
    3.3.2.  Device FSM State Table .............................      17
    3.3.3.  Device Power Mode Diagram ..........................      17
  3.4.  XCMI Standard Tagged Management Data ...................      19
    3.4.1.  List Directory (LIST) Requests .....................      20
  3.5.  Simple Device Management Requests ......................      21
    3.5.1.  Format and Protocol of Device Management Requests ..      22
    3.5.2.  Example of Interface Create Request ................      24
    3.5.3.  Example of Device Create Request ...................      26
    3.5.4.  Example of System Job Create Request ...............      28
  3.6.  Job Service Devices ....................................      30
  3.7.  Job History Devices ....................................      30
4.  Managed Object Definitions .................................      32
  4.1.  Definition of HRX Textual Conventions ..................      32
    4.1.1.  REGISTRY of XCMI Standard Device Types .............      33
    4.1.2.  REGISTRY of XCMI Standard History Device Types .....      42
    4.1.3.  REGISTRY of XCMI Standard CRU Types ................      43
    4.1.4.  REGISTRY of XCMI HRX Admin Service Types ...........      46
    4.1.5.  REGISTRY of XCMI HRX Admin Device Operation Types ..      48
    4.1.6.  XcmHrDevCalendarDayOfWeek ..........................      49
    4.1.7.  XcmHrDevCalendarTimeOfDay ..........................      49
    4.1.8.  XcmHrDevDetailType .................................      50
    4.1.9.  XcmHrDevDetailUnitClass ............................      76
    4.1.10.  XcmHrDevInfoRealization ...........................      78
    4.1.11.  XcmHrDevInfoStatus ................................      78
    4.1.12.  XcmHrDevInfoXStatus ...............................      79
    4.1.13.  XcmHrDevInfoConditions ............................      82
    4.1.14.  XcmHrDevInfoXConditions ...........................      84
    4.1.15.  XcmHrDeviceStatusType .............................      84
    4.1.16.  XcmHrDevMgmtCommandRequest ........................      85
    4.1.17.  XcmHrDevMgmtCommandData ...........................      88
    4.1.18.  XcmHrDevMgmtCommandDataTag ........................      88
    4.1.19.  XcmHrDevPowerModeType .............................     101
    4.1.20.  XcmHrDevPowerTimeUnit .............................     102
    4.1.21.  XcmHrDevTrafficUnit ...............................     102
    4.1.22.  XcmHrGroupSupport .................................     104
    4.1.23.  XcmHrSWRunXStatus .................................     105
    4.1.24.  XcmHrStorageDetailType ............................     105
    4.1.25.  XcmHrStorageRealization ...........................     109

XCMI Working Group  File 10hosttc               [Page i]                

XCMI Extensions to IETF Host Resources TC V6.004       11-10-2015       
                           TABLE OF CONTENTS                            

    4.1.26.  XcmHrDpaAvailability ..............................     110
    4.1.27.  XcmHrDpaConditions ................................     111
    4.1.28.  XcmHrDpaJobValidateSupport ........................     112
    4.1.29.  XcmHrDpaObjectClassSupport ........................     113
    4.1.30.  XcmHrDpaState .....................................     114
    4.1.31.  XcmHrSuppliesClassTC ..............................     114
    4.1.32.  XcmHrDetailTableEnumTC ............................     115
    4.1.33.  XcmHrConsoleDefaultService ........................     115
    4.1.34.  Dummy Group (to suppress compiler warnings) .......     115
5.  Acknowledgements ...........................................     120
6.  References .................................................     120
7.  Security Considerations ....................................     121
8.  Authors' Addresses .........................................     121
9.  Supplement .................................................     122
  9.1.  XCMI Supplement to IETF Host Resources MIB .............     122
    9.1.1.  IETF HR System (Mandatory) .........................     122
    9.1.2.  IETF HR Storage (Mandatory) ........................     124
      9.1.2.1.  Usage of hrStorageType and hrStorageDescr ......     125
      9.1.2.2.  Usage of hrStorageTable ........................     126
    9.1.3.  IETF HR Device (Mandatory) .........................     128
      9.1.3.1.  IETF HR Device Table (Mandatory) ...............     128
        9.1.3.1.1.  Usage of hrDeviceType and hrDeviceDescr ....     129
        9.1.3.1.2.  Usage of hrDeviceID ........................     134
        9.1.3.1.3.  Usage of hrDeviceTable .....................     134
        9.1.3.1.4.  Usage of Physical and Logical Devices ......     137
        9.1.3.1.5.  Usage of hrDeviceErrors ....................     139
      9.1.3.2.  IETF HR Processor Table (Cond Mandatory) .......     141
      9.1.3.3.  IETF HR Network Table (Cond Mandatory) .........     141
      9.1.3.4.  IETF HR Printer Table (Cond Mandatory) .........     142
        9.1.3.4.1.  Usage of hrPrinterDetectedErrorState .......     142
      9.1.3.5.  IETF HR Disk Storage Table (Cond Mandatory) ....     143
      9.1.3.6.  IETF HR Partition Table (Cond Mandatory) .......     143
      9.1.3.7.  IETF HR File System Table (Cond Mandatory) .....     144
    9.1.4.  IETF HR Software Running (Optional) ................     147
      9.1.4.1.  Usage of hrSWRunID and hrSWRunName .............     148
    9.1.5.  IETF HR Software Running Performance (Optional) ....     150
    9.1.6.  IETF HR Software Installed (Optional) ..............     151
      9.1.6.1.  Usage of hrSWInstalledID and hrSWInstalledName .     152
  9.2.  XCMI Supplement to XCMI Ext to Host Resources MIB ......     154
    9.2.1.  XCMI HRX General (Mandatory) .......................     154














XCMI Working Group  File 10hosttc               [Page ii]               
