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:m="http://schemas.microsoft.com/office/2004/12/omml" 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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.ListBullet1, li.ListBullet1, div.ListBullet1
{mso-style-name:"List Bullet 1\,lb1\,Lb1";
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.25in;
margin-bottom:.0001pt;
text-indent:-.25in;
mso-list:l0 level1 lfo3;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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:-2;
mso-list-type:simple;
mso-list-template-ids:-1787787048;}
@list l0:level1
{mso-level-start-at:0;
mso-level-style-link:"List Bullet 1";
mso-level-text:*;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:0in;
text-indent:0in;}
@list l1
{mso-list-id:185600372;
mso-list-type:hybrid;
mso-list-template-ids:-88207072 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1618098901;
mso-list-type:hybrid;
mso-list-template-ids:895937626 599001606 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l3
{mso-list-id:1870533647;
mso-list-type:hybrid;
mso-list-template-ids:1611017550 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l3:level2
{mso-level-tab-stop:1.75in;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l3:level3
{mso-level-tab-stop:2.25in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.75in;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:4.25in;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.75in;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:5.25in;
mso-level-number-position:left;
margin-left:5.25in;
text-indent:-.25in;}
@list l0:level1 lfo3
{mso-level-number-format:bullet;
mso-level-numbering:continue;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:.25in;
mso-level-legacy-space:0in;
margin-left:0in;
text-indent:-.25in;
font-family:Symbol;}
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:10.0pt;font-family:"Arial","sans-serif"'>Ira
et al,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thank
you for your suggestions. My thoughts on the subject:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;
mso-list:l2 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>1.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Although a project
statement is necessary for with Power Management effort, I do not think that a
charter is. My plan was to pass a project statement past the working group and
the SC for comment, but not to go through a charter process.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;
mso-list:l2 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>2.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Similar to what was
done for other projects, I will create a new subdirectory under WIMS, but no
new mailing list. I intend to place the existing power management information
and the project statement in this directory, as well as non-specification draft
documents. Working Draft documents for this effort will go under the WIMS/WD
directory. But quite frankly, I foresee most of the immediate term effort being
in gathering and documenting information of requirements and constraints rather
than coming out with spec drafts.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;
mso-list:l2 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>3.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Addressing Harry’s
question, I will try to make the “out of scope” area clearer and less
restrictive. At this point, I do not want to prejudge what we want
to do without better understanding of both user/administrator and manufacturer viewpoints.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.25in;text-indent:-.25in;
mso-list:l2 level2 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>a.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In general, adding power
state definitions beyond what is in ACPI is out of scope, although I would not immediately
preclude providing for manufacturer defined sub-states. That is, the state must
be one of the standard ones; but we may want to allow for a manufacturer to provide
more details so he could effectively identify more detailed sub states to
an application which understands them.<o:p></o:p></span></p>
<p class=ListBullet1 style='margin-left:1.25in;mso-list:l2 level2 lfo2'><![if !supportLists]><span
style='font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>b.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-family:"Arial","sans-serif"'>Regardless, we certainly need to address
how the standard states apply to imaging devices in such a way that an
identified state has a consistent meaning across all products. Determining just
what this meaning is will be a major task. It is not immediately clear to me
that there is an absolute power-range level associate with each state rather
than a relative level or other aspects such as the ACPI Global state definitions
include; e.g., , the latency from external events to application response, reboot
require, safe to disassemble etc.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.25in;text-indent:-.25in;
mso-list:l2 level2 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>c.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>We touched upon whether
we will identify power states for just systems, or subunits or a services or
some combination. Ira suggested that we start with systems (which I am included
to agree with)) and absolutely avoid Services (which I am not so definite
about). If at all possible, we need to get user/administrator input, and we may
find that although users think in terms Devices (Fax, Scanner, Printer), when
dealing with an MFD, they are really concerned with Services. At this point, I
think we need to listen more than dictate.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.25in;text-indent:-.25in;
mso-list:l2 level2 lfo2'><![if !supportLists]><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>d.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Although it may be
obvious, developing a protocol is out of scope and tying the elements to a
specific protocol is to be avoided. We recognize that defining a working
binding is necessary for prototype, and the obvious choice at this point is
SNMP. Nor do I believe that just mapping to a binding is a valid prototype of
the elements spec. But the Power Management Elements Spec should be
protocol agnostic.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in'><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in'><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'>Thanks,<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in'><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:.75in'><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'>Bill Wagner<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <br>
<br>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> Ira McDonald
[mailto:blueroofmusic@gmail.com] <br>
<b>Sent:</b> Monday, May 11, 2009 5:01 PM<br>
<b>To:</b> Harry Lewis; Ira McDonald<br>
<b>Cc:</b> William Wagner; wims@pwg.org<br>
<b>Subject:</b> Re: [WIMS] Draft of Charter of WIMS Power Mgmt Project<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Hi Harry,<br>
<br>
Thanks for the comments - my replies are inline below.<br>
<br>
Cheers,<br>
- Ira<br>
<br clear=all>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Blue Roof Music/High North Inc<br>
email: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
winter:<br>
579 Park Place Saline, MI 48176<br>
734-944-0094<br>
summer:<br>
PO Box 221 Grand Marais, MI 49839<br>
906-494-2434<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Mon, May 11, 2009 at 4:44 PM, Harry Lewis <<a
href="mailto:harry.lewis@infoprint.com">harry.lewis@infoprint.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ira, great
start! Couple observations.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1. As written,
adding or changing power state definitions is out of scope. Should the
objectives include "interpretation" or mapping of defined power
states as they relate to imaging devices? </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> - For
example - are we going to standardize which "power level" relates to
fuser or scanner lamp readiness etc?</span> <o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<ira><br>
My two cents.<br>
<br>
There was strong concensus at the last two face-to-face BOFs<br>
NOT to allow any but standard (CIM/ACPI) or vendor-defined <br>
power states - no site-defined power states - however, each<br>
power state should have an attribute for power consumption <br>
(in watts) - ACPI and CIM do NOT manage the absolute<br>
power level - they manage a *small* set of standard power<br>
states.<br>
<br>
Therefore, the power *state* that relates to fuser or scanner<br>
lamp readiness is in-scope for WIMS Power, but the exact <br>
power consumption should NOT be changeable by the site.<br>
<br>
Site-defined Power Policy (when to go to sleep after idle<br>
or a time-of-day) that can be changed is in-scope.<br>
</ira><o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal><br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2. Should the
subtask have its own reflector? (we can't pass up the opportunity for <a
href="mailto:POW@PWG.ORG" target="_blank">POW@PWG.ORG</a>!)</span> <o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
<ira><br>
No - we should continue to use the single WIMS reflector<br>
(as we have done for 4 years for CIM without problems).<br>
</ira><br>
<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards,</span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Harry<br>
</span><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><br>
Harry Lewis</span></b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'><br>
Program Manager - Intellectual Property & Open Standards<br>
Phone: 720-663-3456<br>
e-mail: <a href="mailto:harry.lewis@infoprint.com" target="_blank">harry.lewis@infoprint.com</a></span><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:blue'><br>
</span><a href="http://www.infoprint.com/" target="_blank"><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>infoprint.com</span></a><br>
<br>
<img border=0 width=90 height=26 id="_x0000_i1030"
src="cid:image001.gif@01C9D25D.04F9EFD0"><span style='font-family:Webdings;
color:#3F621F'><br>
P</span> <span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#3F621F'>Think before you print</span> <br>
<br>
<o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Ira
McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>></span></b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'> </span><br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by: <a
href="mailto:wims-bounces@pwg.org" target="_blank">wims-bounces@pwg.org</a></span>
<o:p></o:p></p>
<p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>05/11/2009
12:54 PM</span> <o:p></o:p></p>
</td>
<td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><a
href="mailto:wims@pwg.org" target="_blank">wims@pwg.org</a>, William Wagner
<<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>>,
Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>></span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>[WIMS]
Draft of Charter of WIMS Power Mgmt Project</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
</table>
</td>
</tr>
</table>
<div>
<div>
<p class=MsoNormal><br>
<br>
<br>
Hi Bill,<br>
<br>
Attempting to more constructively help out...<br>
<br>
I just posted a draft of a charter for WIMS Power Mgmt Project:<br>
<br>
<a
href="ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower-charter-20090511.htm"
target="_blank">ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower-charter-20090511.htm</a><br>
<br>
I followed the format approved by the PWG in IPP PSX project<br>
and more recently the MFD WG (basically the same idea).<br>
Especially, it includes a specific Out-Of-Scope section.<br>
<br>
Please add a brief Problem Statement (replace <tbd>).<br>
<br>
The Milestones during Definition Phase (Initial draft, Prototype<br>
draft, and PWG Last Call for each of Model and Binding specs) <br>
are the ones the PWG Steering Committee agreed on for MFD <br>
- the SC specifically do not want a milestone such as 'PWG CS',<br>
because a WG can't project that.<br>
<br>
Comments?<br>
<br>
Cheers,<br>
- Ira<br>
<br>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Blue Roof Music/High North Inc<br>
email: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
winter:<br>
579 Park Place Saline, MI 48176<br>
734-944-0094<br>
summer:<br>
PO Box 221 Grand Marais, MI 49839<br>
906-494-2434<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal>-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>wims mailing list</tt><br>
<tt><a href="mailto:wims@pwg.org" target="_blank">wims@pwg.org</a></tt><br>
<tt><a href="https://www.pwg.org/mailman/listinfo/wims" target="_blank">https://www.pwg.org/mailman/listinfo/wims</a></tt><br>
</span><br>
<br>
_____________________________________________________________________________<br>
"This message and any attachments are solely for the intended recipient
and may contain confidential or privileged information. If you are not the
intended recipient, any disclosure, copying, use, or distribution of the
information included in this message and any attachments is prohibited. If you
have received this communication in error, please notify us by reply e-mail and
immediately and permanently delete this message and any attachments. Thank you."
_____________________________________________________________________________<o:p></o:p></p>
</blockquote>
</div>
<p class=MsoNormal><o:p> </o:p></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>