Before I submit my comments to Scott on his recent posting (below),
I am hoping others--especially printer vendors--could comment on
his suggestion regarding the identification of the target printer model.
It would be great if we could get this discussion going as quickly as
possible, since adding MIB objects at this late date is going to put a
lot of pressure on poor Randy to get the final draft to the IETF in a
timely manner.
...jay
----- Begin Included Message -----
Date: Wed, 23 Oct 1996 10:14:17 -0600
From: Scott A. Isaacson <Scott_Isaacson at novell.com>
To: pwg at pwg.org, jkm at underscore.com
Subject: How to identify the particular printer MODEL via SNMP? -Reply
In Novell's "on the server" implementation we are not supporting
hrDeviceID.
However, in NDPS we did create a new object (attribute) that contains
the plug-and-play device ID. This is different in syntax from the
hrDeviceID (that one is an OID, this one is a an OCTET STRING).
This new object helps us to know what the device is for auto driver
download. If the printer can't tell us, we have the administrator pick from
a more human easy to read set of names and then we associate the
correct p-n-p device id with that instance of the printer. I would make a
suggestion that we add this kind of object as well. I can look up the
specifics of the syntax, but it is some form of string with keywords like
"mfr=xxxx;mod=yyyyy;...."
Any thoughts on this idea?
Scott I.
************************************************************
Scott A. Isaacson
Print Services Consulting Engineer
Novell Inc., 122 E 1700 S, Provo, UT 84606
V: (801) 861-7366, (800) 453-1267 x17366
F: (801) 861-4025, E: scott_isaacson at novell.com
W: http://www.novell.com
************************************************************
----- End Included Message -----