attachment

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> All,<o:p></o:p> <o:p> </o:p> Much of the discussion hinged around getting printer vendors to improve their implementations, to perform interoperability or certification, and to provide readily accessible information on the level of their implementations, etc. so that software applications can more successfully manage devices from multiple vendors.<o:p></o:p> <o:p> </o:p> As I think Harry mentioned, the original intent of the printer MIB effort was in large part to have third party vendors and the major enterprise management apps, such as <st1:City w:st="on"><st1:place w:st="on">Tivoli</st1:place></st1:City>, Unicenter, and OpenView, develop robust printer management implementations. When this failed to materialize, virtually all printer vendors developed their own software to manage their devices and, to a lesser extent, competitors devices as well. (or maybe the printer vendors shot themselves in the foot by releasing these free printer management apps and killing the incentive for other development).<o:p></o:p> <o:p> </o:p> I think many printer vendors may be resigned to the fact that the majority of print device management will be done by their own management apps and they don’t have too much incentive to improve their partial management of competitors’ devices.<o:p></o:p> <o:p> </o:p> Thus, these vendors may have difficulty seeing the benefit of the effort involved to move forward with much of the work that was proposed during the discussion. Perhaps a listing of the benefits to the printer vendors would be necessary to spur interest. Until there is market pressure to improve poor SNMP/MIB implementations or a clearly defined tangible benefit, I think some printer vendors may not be willing to allocate resources to these efforts. <o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <o:p> </o:p> <a name="OLE_LINK1"></a><st1:PersonName w:st="on">Stuart Rowley</st1:PersonName>, Network Product Mgr.<o:p></o:p> stuart.rowley@ktd-kyocera.com      925 849-3306     925 849-3399 (fax)<o:p></o:p> <o:p> </o:p> Kyocera Technology Development Inc.<o:p></o:p> <st1:Street w:st="on"><st1:address w:st="on">1855 Gateway Blvd. Suite 400</st1:address></st1:Street><o:p></o:p> <st1:place w:st="on"><st1:City w:st="on">Concord</st1:City>, <st1:State w:st="on">CA</st1:State> <st1:PostalCode w:st="on">94520</st1:PostalCode></st1:place><o:p></o:p> ************************************ <o:p></o:p> If this email is not intended for you, or you are not responsible for the delivery of this message to the addressee, please note that this message may contain Kyocera Technology Development Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to anyone. You should destroy this message and kindly notify the sender by reply email. Information contained in this message that does not relate to the business of Kyocera Technology Development is neither endorsed by nor attributable to Kyocera Technology Development. <o:p></o:p> ************************************<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>