PMP Mail Archive: RE: PMP> Printer MIB draft posted

PMP Mail Archive: RE: PMP> Printer MIB draft posted

RE: PMP> Printer MIB draft posted

From: McDonald, Ira (
Date: Wed May 17 2000 - 14:37:02 EDT

  • Next message: "RE: PMP> Printer MIB draft posted"

    Hi Harry,

    I picked up this file yesterday from the PWG site and used
    SMICng 'mstrip' tool to extract the MIB source. It compiles
    after fixing three one-line typos (all commas that are missing
    or present when they shouldn't be):

    1) chNDPS(43), -- Ira - added comma
    2) chIPP(44) -- Ira - removed comma
    3) mediaPathcannotDuplexMediaSelected(1304), -- Ira - added comma
        [the word 'cannot' should also be capitalized in the above]

    Also, your entire file is still set at 65 columns of text (as
    Randy Turner had done) and not 72 columns (as required by RFC
    Editor for I-Ds and RFCs). This causes some additional havoc
    with some tables.

    I haven't reviewed the text updates and clarifications yet.
    Will do so shortly.

    - Ira McDonald, consulting architect at Xerox and Sharp
      High North Inc

    -----Original Message-----
    From: []
    Sent: Friday, May 05, 2000 8:52 PM
    To: Jay Martin
    Subject: Re: PMP> Printer MIB draft posted

    Yes, I'm all for highlighting it on the PWG web site and even putting a
    reference to it in the MIB draft (if that's "allowed"). I agree the "Top
    25" was a valuable exercise. It's just the lack of usability in the
    current text format that I don't like.

    Harry Lewis
    IBM Printing Systems

    Jay Martin <>
    05/05/00 04:25 PM

            To: Harry Lewis/Boulder/IBM@IBMUS
            Subject: Re: PMP> Printer MIB draft posted

    > There are a couple "issues" remaining.
    > 1. That Top 25 alert table (Apdx E) is horrible in terms of formatting
    > I think it's useless in it's current condition. I'd like to remove it!

    Generating that Top 25 table turned out to be the *only* way the group
    could narrow its focus to determine what was truly important with respect
    to alerts and associated usage scenarios, IMHO.

    I certainly understand how hard it is to put such a big table in such a
    small format, but this table should be retained *someplace* that everyone
    can access. How's about putting it on the PWG website in a


    This archive was generated by hypermail 2b29 : Wed May 17 2000 - 14:43:56 EDT