I don't have a clear recollection of why we were talking
about the move of this object either, but it seems to me
that I did take some editorial action awhile back and
suggested we move and group objects differently so that
implementers could see things a little clearer....
Randy
> -----Original Message-----
> From: Jay Martin [SMTP:jkm at underscore.com]
> Sent: Thursday, November 20, 1997 10:57 AM
> To: Bob Pentecost
> Cc: pmp at pwg.org> Subject: Re: PMP> Justification for prtAlertTime and
> prtAlertTimeGrou
>> Umm...I don't think so, Bob. (I can't speak for Dave Kellerman.)
>> While it's true that I always had quite a bit of heartburn
> accepting the group's original decision to NOT require some
> kind of a timing value (relative or absolute) for an alert
> event, I always just accepted the group's wishes.
>> Later, when the group finally realized that, "Hey, we also
> must support MIB-II...and that requires time-ticks!", it
> then became pretty apparent (to me, anyway) that an alert
> time component for an alert entry should be MANDATORY, since
> all printers supporting the Printer MIB had that value, anyway.
>> I don't wish to fight the mandatory-vs-optional argument all over
> again. But suffice to say, I was NOT involved in the move of the
> original alert time object from one part of the MIB to another.
>> Could such a move have been proposed by Tom Hastings, perhaps
> motivated by creating "a more perfect MIB"? (Hey, let's keep
> passing this buck! ;-)
>> Again, Dave Kellerman may have some fond memories of this situation.
>> ...jay
>> ----------------------------------------------------------------------
> -- JK Martin | Email: jkm at underscore.com --
> -- Underscore, Inc. | Voice: (603) 889-7000 --
> -- 41C Sagamore Park Road | Fax: (603) 889-2699 --
> -- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
> ----------------------------------------------------------------------
> << Message: RE: PMP> Justification for prtAlertTime and
> prtAlertTimeGrou >>