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]

CIMCoreCR00995

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_PrintChannel_01.htm

Errata   [Yes|No]

No

Short Description

Add class CIM_PrintChannel 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_PrintChannel.mof

Date Originated  [mm/dd/yyyy]

08/29/2007

Date of Last Revision of the Change Request [mm/dd/yyyy]

08/29/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_PrintChannel, is one of the several classes to be added.  PrintChannel represents a communications path into a printer, such as a serial or parallel line or a TCP/IP port.  A channel speaks a particular protocol and is usually related to specific PrintInterpreters for job control and page imaging.  These relationships are expressed by the use of an AssociatedPrintInterpreter association between the classes. 

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_PrintChannel


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_PrintChannel
// ==================================================================

[Experimental, Version ( "2.17.0" ),
UMLPackagePath ( "CIM::Device::Printing" ), Description (
"This class represents the PrintChannel component of a Printer "
"(print device). It contains properties that describe the print "
"protocol type and version and the status of the PrintChannel. "
"Note: A PrintChannel shall be associated with exactly one "
"Printer via an instance of the PrinterComponent class. A "
"PrintChannel may be associated with a PrintInterpreter (for "
"Job Control Language or Page Description Language defaults) "
"via an instance of AssociatedPrintInterpreter. See: Model in "
"section 2 of Printer MIB (RFC 3805)."),
MappingStrings { "MIB.IETF|Printer-MIB.prtChannelEntry" }]
class CIM_PrintChannel : CIM_PrinterElement {

[Description (
"The type of this PrintChannel. This property provides the "
"linkage to PrintChannel type-specific classes that may "
"(conceptually) extend the PrintChannel class with "
"additional details about that PrintChannel."),
ValueMap { "1", "3", "4", "5", "6", "7", "8", "9", "10", "11",
"12", "13", "14", "15", "16", "17", "18", "19", "20", "21",
"22", "23", "24", "25", "26", "27", "28", "29", "30", "31",
"32", "33", "34", "35", "36", "37", "38", "39", "40", "41",
"42", "43", "44", "45", ".." },
Values { "Other", "ChSerialPort", "ChParallelPort",
"ChIEEE1284Port", "ChSCSIPort", "ChAppleTalkPAP",
"ChLPDServer", "ChNetwareRPrinter", "ChNetwarePServer",
"ChPort9100", "ChAppSocket", "ChFTP", "ChTFTP",
"ChDLCLLCPort", "ChIBM3270", "ChIBM5250", "ChFax",
"ChIEEE1394", "ChTransport1", "ChCPAP",
"ChDCERemoteProcCall", "ChONCRemoteProcCall", "ChOLE",
"ChNamedPipe", "ChPCPrint", "ChServerMessageBlock", "ChDPMF",
"ChDLLAPI", "ChVxDAPI", "ChSystemObjectManager", "ChDECLAT",
"ChNPAP", "ChUSB", "ChIRDA", "ChPrintXChange", "ChPortTCP",
"ChBidirPortTCP", "ChUNPP", "ChAppleTalkADSP", "ChPortSPX",
"ChPortHTTP", "ChNDPS", "ChIPP", "ChSMTP", "DMTF Reserved" },
MappingStrings { "MIB.IETF|Printer-MIB.prtChannelType",
"MIB.IETF|IANA-PRINTER-MIB.PrtChannelTypeTC" },
ModelCorrespondence { "CIM_PrintChannel.OtherTypeDescription",
"CIM_PrintChannel.ProtocolVersion" }]
uint32 Type;

[Description (
"A free-form string that describes the type of PrintChannel "
"when the value of the Type property is equal to 1 (Other)."),
MinLen ( 0 ), MaxLen ( 255 ),
ModelCorrespondence { "CIM_PrintChannel.Type",
"CIM_PrintChannel.ProtocolVersion" }]
string OtherTypeDescription;

[Description (
"The version of the protocol used on this PrintChannel. The "
"format used for version numbering depends on value of the "
"Type property, as specified in the PrtChannelTypeTC textual "
"convention in the IANA Printer MIB (originally published in "
"RFC 3805)."),
MinLen ( 0 ), MaxLen ( 63 ),
MappingStrings {
"MIB.IETF|Printer-MIB.prtChannelProtocolVersion",
"MIB.IETF|IANA-PRINTER-MIB.PrtChannelTypeTC" },
ModelCorrespondence { "CIM_PrintChannel.Type",
"CIM_PrintChannel.OtherTypeDescription" }]
string ProtocolVersion;

[Description (
"This property contains detailed availability information "
"for this PrintChannel, as follows: 1 (Other) means other "
"detailed availability information is present in the "
"OtherAvailabilityStatus property. 2 (Unknown) means "
"detailed availability information for this PrintChannel is "
"unknown. 3 (AvailableIdle) means this PrintChannel is "
"available and idle, i.e., not currently in use. 4 "
"(AvailableStandy) means this PrintChannel is available but "
"on standby, e.g., in a power saving mode. 5 "
"(AvailableActive) means this PrintChannel is available and "
"active, i.e., currently in use. 6 (AvailableBusy) means "
"this PrintChannel is available but busy, i.e., not "
"immediately available for its primary function. 7 "
"(UnavailableOnRequest) means this PrintChannel is not "
"available and is on request, i.e., needs human "
"intervention. 8 (UnavailableBroken) means this PrintChannel "
"is not available and is broken, e.g., needs "
"repair/replacement."),
ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", ".." },
Values { "Other", "Unknown", "AvailableIdle",
"AvailableStandby", "AvailableActive", "AvailableBusy",
"UnavailableOnRequest", "UnavailableBroken",
"DMTF Reserved" },
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence {
"CIM_ManagedSystemElement.OperatingStatus",
"CIM_PrintChannel.OtherAvailabilityStatus" }]
uint32 AvailabilityStatus;

[Description (
"A free-form string that describes the detailed availability "
"of this PrintChannel when the value of the "
"AvailabilityStatus property is equal to 1 (Other)."),
MinLen ( 0 ), MaxLen ( 255 ),
ModelCorrespondence { "CIM_PrintChannel.AvailabilityStatus" }]
string OtherAvailabilityStatus;

[Description (
"If true, there are currently non-critical alerts on this "
"PrintChannel."),
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence { "CIM_ManagedSystemElement.DetailedStatus"
}]
boolean NonCriticalAlertsPresent;

[Description (
"If true, there are currently critical alerts on this "
"PrintChannel."),
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence { "CIM_ManagedSystemElement.DetailedStatus"
}]
boolean CriticalAlertsPresent;
};

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

01

2007/08/29

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)

Template Version 2.0.1b
Copyright (C) 2007 Distributed Management Task Force, Inc. (DMTF). All rights reserved.