DMTF Change Request

DMTF Confidential

All changes to be submitted by the Working Group Chair (or designee) after approval by the working group.

The Change Request sample (http://www.dmtf.org/members/zdata/CRTemplateSample.html) contains more detailed
information on how to complete the template.

DMTF Change Request Number [CIMCoreCR006655]	CIMCoreCR01001
CR Owner Name, Email [My Name, my.name@company.com]	Richard Landau, Richard_Landau@dell.com
Alliance Partner submitting CR request (if applicable)	Printer Working Group, www.pwg.org
Alliance Partner vote history (e.g. SNIA XYZ Approved on 8/12/06)	n/a
Alliance Partner identifier/tracking number (if available)	CIMCoreCR_PrintAlertLog_00.htm
Errata [Yes\|No]	No
Short Description	Add class CIM_PrintAlertLog to enhanced printer device model.
Spec, Document or Model(s) Being Changed [Application\|Core\|Database\|Device\|Event\|Interop\| Network\|Physical\|Policy\|Support\|System\|User ]	Device
Spec, Document or Model Version Incorporating the Change [2.16.0 Experimental \| Final]	2.17 Experimental
Filename(s) Incorporating the Change [Core/CIM_Container.mof, DSP0204.pdf]	CIM_PrintAlertLog.mof
Date Originated [mm/dd/yyyy]	09/12/2007
Date of Last Revision of the Change Request [mm/dd/yyyy]	09/12/2007
Dependencies [CIMCoreCR00555,CIMCoreCR00600,...]

Terminology

The terminology used in this CR should conform to the "Rules for the structure and drafting of International Standards", 5th Edition, 2005 available at:

http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2122/3146825/4229629/4230450/4230456/ISO_IEC_Directives__Part_2__Rules_for_the_structure_and_drafting_of_International_Standards__2004__5th_edition___pdf_format_.pdf?nodeid=4230517&vernum=0

Particular attention shall be paid to Annex H which lays out guidelines for the expression of provisions.

Background/Rationale (Explanation of the background and reason(s) for the requested change, and supporting documentation):

As part of the PWG/DMTF Work Register, PWG is updating the printing-related classes in the CIM data model. The PWG models for printing related devices and services include many properties that need to be managed but are not currently represented in CIM at all. The CIM model is being extended to include these important management objects. This requires extensions to the CIM_Printer class and the addition of other CIM classes to represent the capabilities, settings, and counters required.

Many early implementers of this class are expected to be proxy providers for SNMP-capable printers. A few properties in this class are included to permit software and users to correlate status and event information between CIM and legacy SNMP access paths. It is expected that such properties will be deprecated when they are no longer needed for this purpose.

The current new class, CIM_PrintAlertLog, is one of the several classes to be added.

The classes CIM_PrintAlertLog and CIM_PrintAlertRecord are designed to meet the requirements of the DMTF Record Log Profile (DSP1010) and the requirements of the printer model of a persistent alert log, as embodied in the prtAlert section of the IETF Printer MIB (RFCs 1759 and 3805). The CIM_PrintAlertRecord class includes a number of properties that are present in the existing native printer alerts and are used by client applications to locate alert conditions within the mechanism of the printer.

Alliance Partner Status (tracking number, other key identifiers, supporting documentation, etc.):

(insert text here)

Requested Change (Change information such as details before/after the change and/or references documents (other then MOF) if the changes are too lengthy to include inline):

// Add the new class CIM_PrintAlertLog

MOF Changes (The complete CIM Class (ASCII) using blue text for new, red text for removed and black text for no change, only one CIM Class can be changed per CR):


// Copyright (c) 2007 DMTF.  All rights reserved.
// ==================================================================
//  CIM_PrintAlertLog
// ==================================================================
   [Experimental, Version ( "2.17.0" ),
       UMLPackagePath ( "CIM::Device::Printing" ), Description (
       "PrintAlertLog serves as an aggregation point for "
       "PrintAlertRecord objects. This class exists in order to "
       "encourage the use of a consolidated record management "
       "methodology for Printer alerts. A common set of providers for "
       "this log and its associated records SHOULD be used to control "
       "functions such as record persistence, query support and "
       "overall data integrity in a consistent manner. A PrintAlertLog "
       "shall be associated with exactly one Printer via an instance "
       "of the UseOfLog class. See: Model in section 2 of Printer MIB "
       "(RFC 3805) and section 3 of Finisher MIB (RFC 3806)."), 
    MappingStrings { "MIB.IETF|Printer-MIB.prtAlertTable" }]
class CIM_PrintAlertLog : CIM_RecordLog {
};

Discussion Points (Summary of decisions and discussions of the WG in creating this CR) :

(insert text here)

Change History (Mandatory after submission to the TC, May be used by the WGs):

Version	Date	Short description of changes
00	09/12/2007	Original version.

Note that this document is labeled as "DMTF Confidential". It is intended only for DMTF member companies and alliance partners.
This Change Request may be withdrawn or modified by subsequent Change Requests.

All submissions MUST comply with the DMTF Patent and Technology policy (http://www.dmtf.org/about/policies/patent-10-18-01.pdf)