attachment
<html><body>
<DIV>Power Management is a good example of what is beyond the Standard MIB to CIM aspect of WS-Man for imaging that WIMS/CIM has been doing. Power management is important and (I think) most printers do have something in their private MIB to relate to this. There is a question of whether a MIB to WS-Man Converter would be usable for obejcts in enterprise MIBS.</DIV>
<DIV> </DIV>
<DIV>However, in terms of priority, I suggest that the whole group of "computer system" elements that should be addressed when we do a printer profile are perhaps more critical and perhaps more easily supported (since many are already accessible in printers via SNMP because of the standard MIB-II and Host Resources MIB).</DIV>
<DIV> </DIV>
<DIV>I will add these subjects to the f2f agenda. And, not to pound the drum too hard, it sure would be useful to have more workers on these developments.</DIV>
<DIV> </DIV>
<DIV>Bill Wagner</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR>From: <Richard_Landau@Dell.com> <BR><BR>> Nancy, <BR>> <BR>> To agree with and expand on Ira's comments, <BR>> <BR>> - Our charter in WIMS-CIM was specifically *not* to invent new <BR>> management concepts, but to translate the Printer MIB and Semantic Model <BR>> into appropriate and usable classes in the CIM architecture and schema. <BR>> We elected not to transfer the semantics of prtGeneralReset to the CIM <BR>> model. <BR>> <BR>> - CIM has a CIM_PowerManagementService defined already. It contains a <BR>> method, RequestPowerStateChange() that can be used to change the state <BR>> of the device. In the DMTF Profile for servers, this class is <BR>> associated with the CIM_ComputerSystem as the method for changing power <BR>> state. Note that CIM classes are only the protocol representation of
<BR>> some internal structures. <BR>> <BR>> - When we write the Network Printer Profile, we should include this <BR>> class as the way to manage power, similarly associated with the instance <BR>> of CIM_ComputerSystem that represents the brains of the device. <BR>> <BR>> I think that it would be very useful to discuss at the f2f <BR>> <BR>> - What states a network printer has; <BR>> - Which of those states are externally, behaviorally visible; <BR>> - What state transitions should be initiated by remote management. <BR>> <BR>> This would be great guidance for future modeling. Can we start with the <BR>> set of power states in the CIM class and see how they might apply to <BR>> network printers? Here's the list, from the MOF, some of which clearly <BR>> to not apply to printers. <BR>> <BR>> Values { <BR>> "Power On", <BR>> "Sleep - Light", <BR>> "Sleep - Deep", <BR>> "Power Cycle (Off Soft)", <BR>> "Power Off - H
ard", <BR>> "Hibernate", <BR>> "Power Off - Soft", <BR>> "Power Cycle (Off Hard)", <BR>> "Master Bus Reset", <BR>> "Diagnostic Interrupt (NMI)", <BR>> "Power Off - Soft Graceful", <BR>> "Power Off - Hard Graceful", <BR>> "Master Bus Reset Graceful", <BR>> "Power Cycle (Off - Soft Graceful)", <BR>> "Power Cycle (Off - Hard Graceful)" <BR>> } <BR>> <BR>> rick <BR>> <BR>> <BR>> -----Original Message----- <BR>> From: Ira McDonald [mailto:blueroofmusic@gmail.com] <BR>> Sent: Tuesday, June 17, 2008 12:04 <BR>> To: nchen@okidata.com; Ira McDonald; wims@pwg.org <BR>> Cc: Landau, Richard <BR>> Subject: Re: Power Management for printer CIM object <BR>> <BR>> Hi Nancy, <BR>> <BR>> Copying WIMS list so others can comment. <BR>> <BR>> CIM_PowerManagementService is a feature of a CIM_ComputerSystem <BR>> - i.e., we inherited it from standard DMTF CIM profiles when we modelled <BR>> a network printer as a CIM_P
rinter contained in a CIM_ComputerSystem <BR>> (class corresponds to System group in MIB-II and Host Resources MIB). <BR>> <BR>> Since the Printer MIB has no power management and I can't find any IETF <BR>> standards-track MIB that has power management, a CIM Printing Provider <BR>> (SNMP to CIM proxy) can't implement power management interoperably. <BR>> <BR>> A basic principle of the WIMS-CIM project is "we invent nothing new" <BR>> - so we can look at existing standard DMTF power management classes and <BR>> see if they're appropriate, but SNMP mapping will remain proprietary in <BR>> the near term. <BR>> <BR>> For future PWG work, I think PowerManagement is important - it *is* <BR>> already in the new Projector and Display Management MIB - perhaps a <BR>> topic for discussion at the PWG F2F next Wednesday? <BR>> <BR>> Cheers, <BR>> - Ira <BR>> <BR>> Cheers, <BR>> - Ira <BR>> <BR>> On Tue, Jun 17, 2008 at 9:26 AM,
<NCHEN@OKIDATA.COM>wrote: <BR>> > <BR>> > Hi Rick, <BR>> > <BR>> > I was asked this question about missing power management objects in <BR>> > CIM-printer. This is just for clarification. <BR>> > <BR>> > We do not have power management object for CIM-printer. But in <BR>> > visio-Printer_15.pdf page 6, you did make a note t hat we may need to <BR>> > implement a bunch of "profiles" listed on the diagram that include <BR>> > PowerManagement. <BR>> > <BR>> > What is the plan on Power Management for CIM printer? <BR>> > <BR>> > -Nancy <BR>> > <BR>> <BR>> <BR>> <BR>> -- <BR>> Ira McDonald (Musician / Software Architect) Chair - Linux Foundation <BR>> Open Printing WG Blue Roof Music/High North Inc <BR>> email: blueroofmusic@gmail.com <BR>> winter: <BR>> 579 Park Place Saline, MI 48176 <BR>> 734-944-0094 <BR>> summer: <BR>> PO Box 221 Grand Marais, MI 49839 <BR>
> 906-494-2434 <BR>> </BLOCKQUOTE></body></html>