attachment-0001
Hi Tom,<br><br>We have a serious problem - we need a new RFC to add a supply unit!<br><br>Brief, sad story...<br><br>The Printer MIB v2 drafts foolishly kept 33 (out of 60) textual conventions <br>IN THE MIB - only a Printer MIB v3 RFC could ever
add a marker supply <br>unit value! This is NOT fixable with just IANA help.<br>
<br>
The rationale was that these were "Type 1 enums" (as in IPP/1.1) and<br>
should be hard to expand (read impossible). I protested at the time, to no <br>avail,
against this locking down of so many enums.<br><br>
While a few (like orientation) are inherently closed (and mirror IPP stuff),<br>most *really* should be extensible.<br>
<br>Mike - I suggest a Steering Committee topic:<br><br>Write a new Printer MIB v3 Internet-Draft to replace RFC 3805 and move <br>all of the other textual conventions into the IANA Printer MIB module (also<br>update PWG MSN references, add IPP/2.0 to ChannelInfo, etc.).<br>
<br>Cheers,<br>- Ira<br>
<br><br><div class="gmail_quote">On Mon, Oct 24, 2011 at 12:22 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><div>Tom,</div><div><br></div><div>My apologies for not getting back sooner...</div><div><br></div><div>Some feedback:</div><div><br></div><div>1. hundredthsOfInkSticks(20)</div><div>
<br></div><div>I prefer the alternate name you proposed - hundredthsOfItems - since it is more generic. The supply type will identify whether we are reporting ink sticks or some other kind of supply...</div><div><br></div>
</div></div></blockquote><div><ira> <br>I agree with Mike - I favor hundredthsOfItems.<br></ira><br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><div></div><div>**** Ira - I had trouble looking this one up since the IANA registry doesn't include PrtMarkerSuppliesSupplyUnitTC...</div><div><br></div></div></div></blockquote>
<div><ira><br><br></ira><br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div><div>
</div><div>2. standardToner(35) and matteToner(36)</div><div><br></div><div>Like Ira I'm not keen on adding a "standard" variant of the existing toner(3) enum. IMHO an unqualified toner value should just be considered "standard". I have no problem adding matteToner(35).</div>
<div><br></div><div>**** Ira - we should probably also register matteInk(36) since matte ink has been used on higher-end inkjet printers for a long time.</div><div><div></div><div class="h5"><div><br></div><div><br></div>
</div></div></div></div></blockquote><div><ira> <br>I agree with Mike that any supply unit is inherently "standard".<br></ira><br><br></div></div><style>#avg_ls_inline_popup{position:absolute;z-index:9999;padding:0px;margin:0px;overflow:hidden;wordWrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%;}#avg_ls_inline_popup div{border-width:3px;border-style:solid;padding:3px;padding-left:8px;padding-right:8px;-moz-border-radius:5px;-webkit-border-radius:5px;}#avg_ls_inline_popup .red{border-color:#D20003;;background-color:#F5D4C1;;}#avg_ls_inline_popup .orange{border-color:#F57301;;background-color:#FFD3B0;;}#avg_ls_inline_popup .yellow{border-color:#EAA500;;background-color:#FEEFAE;;}#avg_ls_inline_popup .green{border-color:#00A120;;background-color:#C3E5CA;;}</style><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup">
</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.