attachment-0001
Hi Andrew,<br><br>First a request - please compile this MIB with any SNMP compilers (from<br>SDKs, management tools, etc.) you have available. I hate making ASN.1<br>errors that are avoidable.<br><br><br>Following IETF MIB convention, we always make whole element groups<br>
one conformance level.<br><br>So, yes we *could* add the MaxXxxRecords to some new group (but<br>not the REQUIRED PowerGeneral group).<br><br>In review discussion at the October F2F, Pete Zehler and others seemed <br>to all agree that client-side implementers will ignore these properties.<br>
<br>My experience over 15 years writing private MIBs for 3 printer vendors has<br>been Pete's right - clients just try to create the row and handle the error for <br>table full.<br><br>My Samsung implementers don't want MaxXxxRecords, because they<br>
don't plan to use them client-side and they inflate the number of <br>REQUIRED elements (which looks bad to upper management).<br><br>Cheers,<br>- Ira<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>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 class="gmail_quote">On Wed, Nov 3, 2010 at 1:50 PM, Mitchell, Andrew (Solutions Architect) <span dir="ltr"><<a href="mailto:andrew.mitchell2@hp.com">andrew.mitchell2@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Ira,<br>
<br>
I have been reviewing the doc as well as have some others within HP looking at it. While I don't have any additional comments yet, I do have a couple questions on your comments. While I agree that most clients will never use the MacXxxRecords, is that a valid rational not to include them? Would a better option be mark the MaxXxxRecords as OPTIONAL parts of the sections.<br>
<br>
Andrew<br>
<br>
From: Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>>><br>
Date: Wed, 3 Nov 2010 17:07:46 +0000<br>
To: "<a href="mailto:wims@pwg.org">wims@pwg.org</a><mailto:<a href="mailto:wims@pwg.org">wims@pwg.org</a>>" <<a href="mailto:wims@pwg.org">wims@pwg.org</a><mailto:<a href="mailto:wims@pwg.org">wims@pwg.org</a>>>, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>>><br>
Subject: [WIMS] High North has reviewed Power Model/MIB and has comments<br>
<div class="im"><br>
(2) Technical - delete all 10 PowerGeneral.MaxXxxRecords elements<br>
- section 5.1.1 through 5.1.10, lines 825-892<br>
<br>
Rationale: Table limit elements are unlikely to be queried/used<br>
- typical Client will simply attempt to create a row<br>
<br>
<br>
</div><div class="im">Power MIB (wd-wimspowermib10-20100926.pdf/mib)<br>
<br>
</div><div><div></div><div class="h5">(2) Technical - delete all 10 powGeneral.MaxXxxRecords objects<br>
- section 5 (spec), lines 261-363 and 389-413 (MIB)<br>
<br>
Rationale: See Power Model comment (2) above<br>
<br>
</div></div></blockquote></div><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.