attachment-0001
Hi,<br><br>[For process review during the PWG Steering Committee tomorrow]<br><br>[For editorial review during the WIMS WG teleconference next week]<br><br><br>During the PWG Formal Vote on the Power Model/MIB specs, four <br>
vendors made editorial comments:<br><br>--------------------------------------------<br><div id=":8a">
Vendor A:<br>[comments on Power Model spec]<br><br>"Line 640 & 641: It seems that the "Suspend power state", on line 640 <br>(being set after 7pm during week days), should be switched with the <br>"Hibernate power state", on line 641 (being set every Friday after 7pm)? <br>
<br>Suspend power state consume less power than Hibernate power state, <br>more appropriate for over the weekend right?<br><br>This seems an editorial oversight, your Power Policy example on Line <br>1529 sets power state to "Suspend" every Friday at 7pm."<br>
<br><br>[Proposed resolution, discussed offline with Vendor A]<br><br>Resolved confusion in offline notes with Vendor A about power usage<br>of Suspend versus Hibernate (i.e., Hibernate uses *less* because OS<br>is NOT still running in RAM).<br>
<br>On line 640, I should change Suspend to Hibernate (best practice).<br><br>On line 641, no change.<br clear="all"><br>On line 1529, I should change Suspend to Hibernate (best practice).<br><br>---------------------------------------------<br>
Vendor B:<br>[comments on Power Model and Power MIB]<br><br>[Power Log Group]<br><br>All Imaging Systems MUST implement this Power Log group as<br>persistent across power cycles and hardware reconfigurations.<br>(section 5.3 in wd-wimspowermib10-20110107.pdf)<br>
<br>-->Do you have any idea about Printer/MFP which doesn’t have a <br>storage like HDD or enough non-volatile memory?<br><br>If you say just as above (MUST implement the persistent across <br>power cycles), I suppose most of low end printers have no chance <br>
to support the power MIB. So it would be helpful for implementer <br>how many logs you need to keep at least (like 10 logs) as a guide line.<br><br><br>[Proposed resolution, discussed offline with Vendor B]<br><br>REGRESSION LOSS - when the 'MaxXxxRecords' elements were<br>
deleted from Power General group during PWG Last Call, we lost <br>the explicit requirement for a minimum of 10 log entries.<br><br>Per WIMS WG discussion last week, we *cannot* restore this as a<br>REQUIRED because it was missing in the Formal Vote version.<br>
Therefore, I will add new text to:<br><br>- section 5.3 Power Log Group in Power Model<br>- section 4.6 Mapping of Power Model in Power MIB<br>- powLogTable object in the ASN.1 MIB source <br><br>to clarify that it is RECOMMENDED to support at least 10 log <br>
entries, for reliable fleet management applications. <br><br>I could also note that empty (or canned) PowerStateMessage <br>strings don't
need to be saved in an NVRAM log implementation.<br><br>-----------------------------------------------<br>Vendor C:<br>[comments on Power Model]<br><br>"Should the generalGroup MIB objects powGeneralNaturalLanguage <br>
and powGeneralPolicyMaxAccess be covered in the model document?"<br><br><br>[Proposed resolution, discussed offline with Vendor C]<br><br>I propose to add text to section 5.1 Power General Group of Power<br>Model to explain:<br>
<br>(a) why NaturalLanguage is not needed (because it's already in the <br>parent System or Subunit object in the PWG SM XML Schema);<br>
<br>(b) why PolicyMaxAccess is not needed (because it's for coarse <br>access-control, specific to the SNMP binding).<br><br>---------------------------------------------------<br>Vendor D:<br>[comments on Power MIB]<br>
<br>"The Power MIB spec lacks the following two sections that are present in <br>the Imaging System State and Counter MIB:<br><br>"4.2 Indexing of Imaging System State and Counter MIB"<br>- an indexing discussion of sets of groups/tables<br>
<br>"4.3 Diagram of Imaging System State and Counter MIB"<br>- a pictorial representation of the same indexing info<br><br>To improve understanding of the Power MIB by designers, implementers, <br>and testers, we request that these two missing sections be drafted and <br>
reviewed by the WIMS WG for inclusion before the approved Power MIB <br>is published."<br><br><br>[Proposed resolution, discussed offline with Vendor D]<br><br>Three other vendors independently made a similar comment recently.<br>
<br>See my separate note with text for these two sections sent to the WIMS WG<br>mailing list on Monday 21 February.<br><br>----------------------------------------------<br><br>Comments?<br><br>Cheers,<br>- Ira<br><br></div>
<br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Hardcopy WG<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 style="color: rgb(102, 0, 204);" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</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<div style="display: inline;"></div><div style="display: inline;"></div><div style="display: inline;"></div><br>
<br><br><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}</style>
<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.