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="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="place"/> <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=blue> <div class=Section1> Ron,<o:p></o:p> <o:p> </o:p> I took a stab at new text for section 7 Recommended Indexing Method.<o:p></o:p> <o:p> </o:p> Ira suggested that it should not be normative and should therefore be in an appendix. I wasn’t sure how to handle whether the ranges are recommended or just an example. If there is no explicit agreement on the ranges, then a management app has no idea of the special meaning of the index. Therefore, “recommended” seems appropriate to me. I expanded the ranges because Ira said that some device implementations may bump into the previous range limits.<o:p></o:p> <o:p> </o:p> Appendix (x) - prtAlertGroupIndex Indexing Option<o:p></o:p> The various MFD functions share some common alert groups, such as prtMediaPath, prtInput, prtOutput, prtChannel, prtConsole, prtCover, etc., For alerts in these common alert groups, there may be no information which indicates the MFD function affected by the alert. The recommended method to allow a management application to associate an alert with a specific device function is to assign index ranges to each device function. The following prtAlertGroupIndex index ranges are recommended; index values from 1 to 255 (0x0001 to 0x00FF) may be assigned to the print function, index values from 256 to 511 (0x0100 to 0x01FF) may be assigned to the scan function, and index values from 512 to 767 (0x0200 to 0x02FF) may be assigned to the fax function. Note that this method does not indicate when a common group alert affects multiple device functions. For example, an open cover may affect the print, fax, and scan functions, but only one prtAlertGroupIndex is used. <o:p></o:p> <o:p> </o:p> For the alert groups that are specific to one MFD function, such as faxDeviceGeneral or scanDeviceScanner, prtAlertGroupIndex indices may be assigned normally, i.e starting at index 1.<o:p></o:p> <o:p> </o:p> Best regards,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <o:p> </o:p> <st1:PersonName w:st="on">Stuart Rowley</st1:PersonName><o:p></o:p> Network Product Mgr.<o:p></o:p> Kyocera Technology Development<o:p></o:p> <st1:Street w:st="on"><st1:address w:st="on">1855 Gateway Blvd. #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> <a href="mailto:stuart.rowley@ktd-kyocera.com">stuart.rowley@ktd-kyocera.com</a><o:p></o:p> V: 925.849.3306<o:p></o:p> F: 925.849.3399<o:p></o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>