§MSG From: SMTP3 --IINUS1 To: pwg at pwg.org +12/04/96 16:32:48á
Received: from lists.underscore.com by vnet.IBM.COM (IBM VM SMTP V2R3) with
Wed, 04 Dec 96 18:34:08 EST
Received: from localhost (daemon at localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id SAA02152; Wed, 4 Dec 1996 18:33:02 -0500 (EST)
Received: by pwg.org (bulk_mailer v1.5); Wed, 4 Dec 1996 18:32:05 -0500
Received: (from daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) id
SAA01506 for pwg-outgoing; Wed, 4 Dec 1996 18:22:48 -0500 (EST)
Message-Id: <199612042322.SAA01499 at lists.underscore.com>
Date: Wed, 4 Dec 96 16:22:17 MST
From: "Harry Lewis <harryl at vnet.ibm.com>" <harryl at vnet.ibm.com>
To: pwg at pwg.org
Subject: PWG> Printer MIB comments
Sender: owner-pwg at pwg.org
Previously, I had sent...
>Sorry for these late comments but in reviewing the latest draft I noticed
I would like to make one correction (inserted below) and reiterate my comments.
>1. Pg. 15 - With the new definition of Active, Busy/Temporarily Unavailable
> in the "table" below should probably be changed to Busy/Active
>>2. Pg. 57 - In the new definition of phone, fax and e-mail conventions for
> Operator and Service Person... we specify phone: fax: email:. I've been
> told the "colon" is not in international character in that it is not in
> the minimum Unicode set. I'm checking on this but, meanwhile, do we care
> in this instance?
Sorry - I was misinformed regarding the :. My mistake, this is (obviously)
a valid unicode character even in the "base" definition.
>> Also, should we specify in the convention what to do if you have a phone
> and e-mail but no fax (i.e. :: ?).
>>3. Pg. 58 - The description for prtGeneralAdminName makes it sound like the
> name of the Administrator. I probably missed something, here, but I thought
> this was the name assigned by the administrator to the printer! Anyway...
> if it really is the name of the administrator, then shouldn't it be in
> the "Responsible Parties" group?
>>4. Pg. 58 - prtGeneralSerialNumber has SYNTAX of PresentOnOff. This must
> be an error
>>5. Pg. 58 - prtAlertCriticalEvents. Should we clarify whether this value
> is supposed to persist or reset across power cycles?
>> Also, the prtAlertEvent stuff we added seems like it would be much more
> useful if we also added something like...
> prtAlertMaxTableSize. Then, knowing the max number of entries a given
> printer could store and, keeping track of the new alert counters, it could
> be determined if any alerts were lost. Polling could presumable be adjusted.>
>> This may have to be in a future revision.
>>6. No one seems to have written any prtChannelInformation for chPortTCP (37/38)>
> It seems like the port number would be very useful here. May I suggest?
>> Keyword: "Port"
> Syntax HexString
> Status Mandatory
> Multiplicity Multiple
Harry Lewis - IBM Printing Systems