PMP Mail Archive: RE: PMP> [Typo confusion] Updates for IANA

PMP Mail Archive: RE: PMP> [Typo confusion] Updates for IANA

RE: PMP> [Typo confusion] Updates for IANA Printer MIB

From: Harry Lewis (harryl@us.ibm.com)
Date: Thu Jul 28 2005 - 00:36:16 EDT

  • Next message: garygold@hotmail.com: "About sign_ups"

    I agree it makes more sense now.
    ----------------------------------------------
    Harry Lewis
    IBM STSM
    Chairman - IEEE-ISTO Printer Working Group
    http://www.pwg.org
    IBM Printing Systems
    http://www.ibm.com/printers
    303-924-5337
    ----------------------------------------------

    "McDonald, Ira" <imcdonald@sharplabs.com>
    Sent by: pmp-owner@pwg.org
    07/26/2005 11:08 AM

    To
    "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>, "McDonald, Ira"
    <imcdonald@sharplabs.com>, "'pmp@pwg.org'" <pmp@pwg.org>
    cc

    Subject
    RE: PMP> [Typo confusion] Updates for IANA Printer MIB

    Hi Bert,

    Darn it - my typo. What it's supposed to say is:

    (3) PrtAlertGroupTC - delete the erroneous comment
            -- (2) is reserved for conformance information

    (4) PrtAlertGroupTC - add
            unknown(2), -- Not in RFC 1759

    That is, we're only deleting an ASN.1 comment! Which
    was added in RFC 3805 and was _wrong_ anyway - we don't
    need to indicate that prtMIBConformance was the source
    of an alert!

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@sharplabs.com

    > -----Original Message-----
    > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
    > Sent: Tuesday, July 26, 2005 11:03 AM
    > To: McDonald, Ira; 'pmp@pwg.org'
    > Subject: RE: PMP> Updates for IANA Printer MIB
    >
    >
    > Inline
    >
    > Ira suggests these changes:
    > > ----------
    > >
    > > (1) PrtCoverStatusTC - add
    > > unknown(2), -- Not in RFC 1759
    > >
    > > (2) PrtChannelTypeTC - add
    > > unknown(2), -- Not in RFC 1759
    > >
    > > (3) PrtAlertGroupTC - delete
    > >
    >
    > If we want to get rid of it, then we do NOT delete it.
    > That may break existing use (possibly existing use by
    > people we do not know).
    >
    > So the best way to get rid of it is to obsolete it.
    >
    > > (4) PrtAlertGroupTC - add
    > > unknown(2), -- Not in RFC 1759
    > > -- (2) is reserved for conformance information
    > >
    >
    > Hope this helps and can be agreed to.
    >
    > Bert
    >



    This archive was generated by hypermail 2b29 : Thu Jul 28 2005 - 00:35:50 EDT