PMP Mail Archive: Re: FIN> FW: PMP> Add 'percent(19)' to

PMP Mail Archive: Re: FIN> FW: PMP> Add 'percent(19)' to

Re: FIN> FW: PMP> Add 'percent(19)' to 'PrtCapacityUnitTC' and 'PrtMarkerS uppliesUn itTC'

From: Harry Lewis (
Date: Fri Dec 15 2000 - 16:20:01 EST

  • Next message: "PMP> Access to MIB data"

    Yea... I know... super way behind on mail. Think I've already seen and
    supported addition of % as a new unit. That's not really a problem in my
    mind. But just catching up to the initial premise that there is a "serious
    problem" which requires this addition. This can easily be expressed
    without %. If you have a max capacity of 500 and you are at 50%, then your
    value is 250. Again, I'm not objecting to adding %, just the premise.
    Harry Lewis
    IBM Printing Systems

    "Bergman, Ron" <>
    Sent by:
    11/21/2000 09:40 AM

            To: "''" <>, "''" <>
            Subject: FIN> FW: PMP> Add 'percent(19)' to 'PrtCapacityUnitTC' and 'PrtMarkerS
    uppliesUn itTC'


    Ira McDonald has proposed the addition of 'percent(19)'
    to the textual conventions 'PrtCapacityUnitTC' and

    I believe that this can be accomplished during the
    RFC Editors cycle.

    If anyone has any objections to this new enumeration
    please state your reasons before December 18, 2000.

            Ron Bergman
            Hitachi Koki Imaging Solutions

    -----Original Message-----
    From: McDonald, Ira []
    Sent: Friday, November 17, 2000 11:26 AM
    To: ''; ''
    Subject: PMP> Add 'percent(19)' to 'PrtCapacityUnitTC' and
    'PrtMarkerSuppliesUn itTC'


    Implementors here at Sharp have found a serious problem with
    'prtInputCurrentLevel', 'prtOutputRemainingCapacity' and

    Their related units objects need 'percent(19)' added to
    allow reporting of RELATIVE levels (often the only
    information known from sensors).

    - 'PrtCapacityUnitTC' should have 'items(18)' (per Ron B
      and Harry L) and 'percent(19)' added
    - 'PrtMarkerSuppliesSupplyUnitTC' should have 'percent(19)'

    BOTH of these textual conventions should also have 'other(1)'
    and 'unknown(2)' added - this would provide short-term
    relief to the NEXT product team that finds a missing unit
    AFTER the Printer MIB v2 is published as an RFC.

    - Ira McDonald, consulting architect at Sharp
      High North Inc

    This archive was generated by hypermail 2b29 : Fri Dec 15 2000 - 16:21:48 EST