attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1008993082;
mso-list-type:hybrid;
mso-list-template-ids:910207324 302439636 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Note that this item relating to registering the PWG Imaging System Power MIB (ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspowermib10-20110214-5106.5.mib) power state set with IANA for reference in the IETF eman Energy Monitoring MIB is on the agenda for the WIMS concall the Wednesday at 1PM EDT. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For those who have not been following the IETF eman list (and it is very active), there are three recent documents of interest. All of these are revisions of earlier documents, and all have been subject to extensive comment, so nothing in them is necessarily firm.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://tools.ietf.org/html/draft-ietf-eman-requirements-04">http://tools.ietf.org/html/draft-ietf-eman-requirements-04</a> (July 11, 2011)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://tools.ietf.org/html/draft-ietf-eman-framework-02">http://tools.ietf.org/html/draft-ietf-eman-framework-02</a> (July 8, 2011)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.ietf.org/id/draft-ietf-eman-energy-monitoring-mib-00.txt">http://www.ietf.org/id/draft-ietf-eman-energy-monitoring-mib-00.txt</a> (Aug 5, 2011)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My understanding is that, although there was a drive for a simple, consistent power state set, it was recognized that:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Several such sets were already defined (e.g., IETF 1621 and DMTF, and also ACPI which both the PWG and eman seem to prefer to avoid)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Certain types of devices have power states that are traditional and, in many cases most appropriate to the nature of those type of devices.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, the conclusion was that a device in implementing the eman mib could identify the power state set it was using as either the eman defined state or an allowed IANA registered power state set. The current eman energy monitoring MIB allows devices to identify the power states set as IETF 1621, DMTF or EMAN.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Because the PWG has sought to keep the eman group aware of the fact that hardcopy equipment has a significant energy use contribution (Randy recently observed that </span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>“</span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif"'>multi-function peripherals (high duty-cycle printer, copier, fax, scanner products) consume an order of magnitude more power than any switch or router”) and that there was an approved </span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Imaging System Power MIB with a power state set appropriate to these devices, the current draft of the eman energy monitoring MIB asks whether the PWG Power State Set (provided that it is EMAN registered) be allowed. This would allow the PWG Power State Set (which although derived from the DMTF, does provides for vendor extensions) to be used in responses to eman MIB queries. With regard to the “tail wagging the dog comment”, although it may require management applications to recognize the PWG set, it would not require not have any effect on devices that which to use a different power state set.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Considering that hardcopy devices may well be implementing both the PWG and the eman MIBs, I join with Ira in requesting that the industry give issue consideration. It is not often that the infrastructure groups of the IETF recognize that hardcopy devices are more than little peripherals attached to workstations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner –CoChair, WIMS/PMP<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> wims-bounces@pwg.org [mailto:wims-bounces@pwg.org] <b>On Behalf Of </b>Ira McDonald<br><b>Sent:</b> Thursday, August 11, 2011 11:48 AM<br><b>To:</b> wims@pwg.org; Ira McDonald<br><b>Subject:</b> [WIMS] Should IETF EMAN register PWG power states? - No<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi,<br><br>ACTION - All - Read and comment on this power states issue for EMAN.<br><br>The latest draft of the IETF EMAN Energy Monitoring MIB (monitor-only<br>subset of EMAN model) includes the following issue:<br><br> "OPEN ISSUE 12: Consideration of IEEE-ISTO PWG in the IANA list <br> of Power State Set ? PWG Imaging Systems Power Management MIB <br> reference."<br><br>And Bruce Nordman (EMAN co-chair) raised the question of registering the<br>PWG power states with IANA for EMAN last week at the PWG meeting <br>- I waffled in my reply.<br><br>On reflection, I propose that the PWG does NOT register their own power<br>states (adding significant complexity to the NMS systems that will already<br>support the other three standard power state sets).<br><br>Instead, best practice would be for PWG Power MIB enabled devices to<br>*fold* vendor extension states into their base DMTF power states (already<br>in EMAN) for more coherent power monitoring and power management<br>across the enterprise. This folding would have to occur anyway for a DMTF<br>CIM mapping of the PWG Power Model, so we'd be consistent for "outside"<br>standards.<br><br>Comments?<br><br>Cheers,<br>- Ira<br><br>PS - I'd like to reply on the IETF EMAN mailing list within the next two weeks<br>on this issue - please send your opinions.<br><br><br clear=all>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SWG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Christmas through April:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br>-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is <br>believed to be clean. <o:p></o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>