We have a serious problem - we need a new RFC to add a supply unit!
Brief, sad story...
The Printer MIB v2 drafts foolishly kept 33 (out of 60) textual conventions
IN THE MIB - only a Printer MIB v3 RFC could ever add a marker supply
unit value! This is NOT fixable with just IANA help.
The rationale was that these were "Type 1 enums" (as in IPP/1.1) and
should be hard to expand (read impossible). I protested at the time, to no
avail, against this locking down of so many enums.
While a few (like orientation) are inherently closed (and mirror IPP stuff),
most *really* should be extensible.
Mike - I suggest a Steering Committee topic:
Write a new Printer MIB v3 Internet-Draft to replace RFC 3805 and move
all of the other textual conventions into the IANA Printer MIB module (also
update PWG MSN references, add IPP/2.0 to ChannelInfo, etc.).
On Mon, Oct 24, 2011 at 12:22 PM, Michael Sweet <msweet at apple.com> wrote:
>> My apologies for not getting back sooner...
>> Some feedback:
>> 1. hundredthsOfInkSticks(20)
>> 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...
I agree with Mike - I favor hundredthsOfItems.
**** Ira - I had trouble looking this one up since the IANA registry doesn't
> include PrtMarkerSuppliesSupplyUnitTC...
2. standardToner(35) and matteToner(36)
>> 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).
>> **** Ira - we should probably also register matteInk(36) since matte ink
> has been used on higher-end inkjet printers for a long time.
I agree with Mike that any supply unit is inherently "standard".
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...