attachment-0001

<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" 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 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Impact;
        panose-1:2 11 8 6 3 9 2 5 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
        {mso-style-link:"Comment Text Char";
        margin-top:6.0pt;
        margin-right:0in;
        margin-bottom:6.0pt;
        margin-left:0in;
        font-size:10.0pt;
        font-family:"Arial","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.CommentTextChar
        {mso-style-name:"Comment Text Char";
        mso-style-link:"Comment Text";
        font-family:"Arial","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
 /* List Definitions */
 @list l0
        {mso-list-id:805194950;
        mso-list-type:hybrid;
        mso-list-template-ids:-2076947280 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1
        {mso-list-id:1957785049;
        mso-list-type:hybrid;
        mso-list-template-ids:441593924 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Happy New Year!<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>I have posted
an update to the Overall MFD Model document, reflecting those issues from the
December face-to-face that I can address. <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><a
href="ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100104.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100104.pdf</a><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Note some schema
diagrams need updating and are awaiting a new schema post. Other items also remain
open.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>MS Word
continues to be difficult, especially in screwing up cross references. <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>&nbsp;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>In addition to
highlighting some new text, there are some comments that, to avoid balloons, do
not show up. They are as follows:<o:p></o:p></span></p>

<p class=MsoCommentText><o:p>&nbsp;</o:p></p>

<p class=MsoCommentText>C1<o:p></o:p></p>

<p class=MsoCommentText>Paragraph 2.3 Needs to be reworked to reflect schema
changes.<o:p></o:p></p>

<p class=MsoCommentText>C2 <o:p></o:p></p>

<p class=MsoCommentText>Table 17.Keyword for Feed direction?<o:p></o:p></p>

<p class=MsoCommentText>C3<o:p></o:p></p>

<p class=MsoCommentText>Section 7.3&nbsp; originally followed the pattern of
Scan and Resource specs, although additional operations added have had
descriptions derived from IPP corollaries. However, operation attributes, error
messages etc have not been discussed. Should they be?<o:p></o:p></p>

<p class=MsoCommentText>Note that some new operation descriptions have been
added.<o:p></o:p></p>

<p class=MsoNormal>C4, 5, 6, 8, 9, 10<o:p></o:p></p>

<p class=MsoNormal>Service Operations in 7.3.2: Since there can be multiple
instance of a given service type, need the request identify the instance? If
so, how?<o:p></o:p></p>

<p class=MsoCommentText>C7<o:p></o:p></p>

<p class=MsoCommentText>Para 7.3.2.8 New writeup<o:p></o:p></p>

<p class=MsoNormal>C 11<o:p></o:p></p>

<p class=MsoCommentText>Para 7.3.2.18 The IPP spec includes processing stopped
as a valid state from which to suspend a job. Is a job in Processing Stopped
considered a current job? If any Job is in Processing Stopped, is the operation
considered successful? Following paragraph says no.<o:p></o:p></p>

<p class=MsoNormal>C12<o:p></o:p></p>

<p class=MsoCommentText>Para 7.3.2.18&nbsp; If the JobID is included and it is
one of several jobs in processing, I assume only the ID'd job is suspended?<o:p></o:p></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Bill Wagner<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Zehler, Peter
[mailto:Peter.Zehler@xerox.com] <br>
<b>Sent:</b> Wednesday, January 06, 2010 12:49 PM<br>
<b>To:</b> William Wagner; mfd@pwg.org<br>
<b>Subject:</b> RE: [MFD] Job State Transition Diagram error<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='color:#1F497D'>Bill,<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'>My only points for the items
below was that<o:p></o:p></span></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style='color:#1F497D'>System configuration
or conditions can cause the transition as well as an operation<o:p></o:p></span></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style='color:#1F497D'>Job operations or
conditions can affect this transition change for a specific job just as well as
service wide operations or conditions can affect this job transitions. <o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'>The issue was raised by an
implementer that was unsure if a required resource would affect the state of a
pending job.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'>Pete<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><span style='color:#1F497D'><br>
<br>
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Xerox Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span
style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>

</div>

<p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> William Wagner
[mailto:wamwagner@comcast.net] <br>
<b>Sent:</b> Wednesday, January 06, 2010 12:36 PM<br>
<b>To:</b> Zehler, Peter; mfd@pwg.org<br>
<b>Subject:</b> RE: [MFD] Job State Transition Diagram error<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Yes. Right now,
the transition effectors are indicated by italicized general statements (e.g., <i>Job
Completed</i>) or citing actual operations (CreateJob). &nbsp;Although it would
be useful to indicate how each transition&nbsp; may be effected by an
operation, that would probably render the diagram unreadable. Further, we
appear to be constantly adding more operations and now operation attributes
that affect Job State. My inclination is to replace all remaining operation
transition effectors with generic statements; e.g., HoldJob Request becomes <i>Job
Held</i>. The correlation between the general statements and the transition
&nbsp;effectors (Operations, Processing Events, &nbsp;Problem Events, Operation
Attribute enabled Events) would be dealt with elsewhere (perhaps in the
descriptions of Operations).<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>That does bring
up another question.&nbsp; How many more of the IPP operations will be
re-stated as&nbsp; &lt;service&gt; Operations? I have attached (if it gets
through) &nbsp;a table of IPP operations (derived from the recent IPP work)
versus MFD Operations as they now are listed, with my understanding of
correlation. &nbsp;I think it best to resolve the discrepancies now.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Bill Wagner<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mfd-bounces@pwg.org
[mailto:mfd-bounces@pwg.org] <b>On Behalf Of </b>Zehler, Peter<br>
<b>Sent:</b> Wednesday, January 06, 2010 8:03 AM<br>
<b>To:</b> mfd@pwg.org<br>
<b>Subject:</b> [MFD] Job State Transition Diagram error<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>All,<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>The diagram for the Job State transition is incorrect.&nbsp;
<o:p></o:p></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The transition from Pending to PendingHeld only shows
the HoldJob event.&nbsp; According to the definition of the PendingHeld state
&#8220;the job is not a candidate for processing for any number of reasons and
will return to the Pending state when the reasons are no longer
present&#8221;.&nbsp; An example could be an unavailable resource.<o:p></o:p></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The transition from Processing to ProcessingStopped
says &#8220;Service Stopped&#8221;.&nbsp; I believe that it should be
&#8220;Job or Service Stopped&#8221;.&nbsp; The commands
Suspend&lt;service&gt;Job and Resume&lt;service&gt;Job cause the
transitions.&nbsp; A required resource or a critical fault will cause the
transition to ProcessingStopped.&nbsp; The resource becoming available or
clearing the critical fault can cause the reverse transition.&nbsp; The
currently described Service conditions for the transition remain valid.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Pete<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><span style='color:#1F497D'><br>
<br>
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Xerox Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span
style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <o:p></o:p></span></p>

</div>

<br />-- 
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>

</html>