attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>MFP Alerts Teleconference Scheduled for June 8</TITLE> <META content="MSHTML 6.00.2800.1528" name=GENERATOR><o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:SmartTagType><o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:SmartTagType> <STYLE>@font-face { font-family: MS Mincho; } @font-face { font-family: Tahoma; } @font-face { font-family: @MS Mincho; } @page Section1 {size: 8.5in 11.0in; margin: .8in .8in .8in .8in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle18 { COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal } SPAN.EmailStyle19 { COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=blue link=blue> <DIV>Hi,</DIV> <DIV> </DIV> <DIV>My mistake about (3) below - of course prtAlertDescription can only</DIV> <DIV>discriminate between multiple subunits for _humans_.  A proper MIB</DIV> <DIV>is required (which is by the way named "Imaging System MIB", not</DIV> <DIV>"MFP MIB") - the term "MFP" is used in WIMS/1.0 and the SM/2.0</DIV> <DIV>update work only informatively - the authoritative term is "Imaging</DIV> <DIV>System" (containing Agent, Manager, Services, Subunits, etc).</DIV> <DIV> </DIV> <DIV>Cheers,</DIV> <DIV>- Ira</DIV> <DIV> </DIV> Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221  Grand Marais, MI  49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf Of Bergman, Ron Sent: Tuesday, June 06, 2006 1:52 PM To: PMP@pwg.org Subject: FW: PMP> MFP Alerts Questions </DIV> <DIV> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Stuart Rowley [mailto:Stuart.Rowley@ktd-kyocera.com] Sent: Thursday, June 01, 2006 5:56 PM To: Bergman, Ron Subject: RE: PMP> MFP Alerts Questions </DIV> <DIV class=Section1> Hi Ron,<o:p></o:p> <o:p> </o:p> Will you send your response to the PMP list, so others may see your answers?<o:p></o:p> <o:p> </o:p> I am thinking it is really weird to have the scanner covers, input, and media path defined in the print mib and other components defined in the MFP mib...<o:p></o:p> <o:p> </o:p> I suppose the description field could be used as a quick and dirty alternative to implementing the MFP mib. I would be interested in what Ira has to say.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <o:p> </o:p> <DIV> <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center> <HR tabIndex=-1 align=center width="100%" SIZE=2> </DIV> From: Bergman, Ron [mailto:Ron.Bergman@rpsa.ricoh.com] Sent: Thursday, June 01, 2006 5:49 PM To: Stuart Rowley Subject: RE: PMP> MFP Alerts Questions<o:p></o:p></DIV> <o:p> </o:p> <DIV> Hi Stuart,<o:p></o:p></DIV> <DIV>  <o:p></o:p></DIV> <DIV> 1)  I do recall discussing this in the conference, but left it out of my notes.  Media path should not be a Scan Group.  I will remove in the next revision.<o:p></o:p></DIV> <DIV>  <o:p></o:p></DIV> <DIV> 2)  That is correct.  So the covers table (or group) includes the Printer, Sacn Device, and Fax Device.  Same for the other common groups.<o:p></o:p></DIV> <DIV>  <o:p></o:p></DIV> <DIV> 3)  Ira has said that this would be covered by the description field in the alert table.  I disagree and believe a MIB is necessary to properly define.  Do you agree?<o:p></o:p></DIV> <DIV>  <o:p></o:p></DIV> <DIV> Hope this helps.<o:p></o:p></DIV> <DIV> <o:p></o:p></DIV> <DIV>     Regards,<o:p></o:p></DIV> <DIV>     Ron<o:p></o:p></DIV> <BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in"> -----Original Message----- From: Stuart Rowley [mailto:Stuart.Rowley@ktd-kyocera.com] Sent: Thursday, June 01, 2006 1:42 PM To: Bergman, Ron; pmp@pwg.org Subject: RE: PMP> MFP Alerts Questions<o:p></o:p> Hi Ron,<o:p></o:p> <o:p> </o:p> I have a few questions about the MFP Alerts draft.<o:p></o:p> <o:p> </o:p> 1. If there are no groups for scanDeviceCover or scanDeviceInput, why is there a group for scanDeviceMediaPath?<o:p></o:p> <o:p> </o:p> 2. If, for example, the scanner document feeder cover was open, then the prtAlertTable entry would include prtAlertGroup = 6 (Cover), but then the prtAlertGroupIndex should point to a cover in the prtCover table. So now I have scan device covers implemented in the printer MIB, but other scan device subunits in the MFP MIB? <o:p></o:p> <o:p> </o:p> 3. In the examples in section 10.1.3 for the scanDeviceScanner group there is Lamp Missing, subunitMissing(9) / subunitRemoved(26). What if I have multiple subunits that could be missing? There is no way to tell without using prtAlertGroupIndex to point to a table entry in the MFP MIB?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <o:p> </o:p> Stuart Rowley<o:p></o:p> Kyocera Technology Development<o:p></o:p> <o:p> </o:p> <DIV> <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center> <HR tabIndex=-1 align=center width="100%" SIZE=2> </DIV> From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org] On Behalf Of Bergman, Ron Sent: Thursday, June 01, 2006 8:49 AM To: pmp@pwg.org Subject: PMP> MFP Alerts Teleconference Scheduled for June 8<o:p></o:p></DIV> <o:p> </o:p> The next teleconference for MFP Alerts is scheduled for June 8, 2006 at 11:00 AM EDT (8:00 AM PDT). <o:p></o:p> Agenda:      1. Review previous meeting minutes      2. Continue review of the draft Alert Groups document      3. Start review of the Imaging System MIB <o:p></o:p> The latest version of the Alert Groups document is at: <o:p></o:p>         <A href="ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-mfp-alert-groups10-20060601.pdf">ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-mfp-alert-groups10-20060601.pdf</A> <o:p></o:p> Meeting access:     1-866-365-4406     Passcode: 2635888#<o:p></o:p></BLOCKQUOTE></DIV> -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.2/357 - Release Date: 6/6/2006 </BLOCKQUOTE></BODY></HTML> -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.2/357 - Release Date: 6/6/2006