attachment-0002
<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:Cambria;
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Cambria","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l0 level1 lfo2;
font-size:14.0pt;
font-family:"Cambria","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.3in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l1 level2 lfo4;
font-size:14.0pt;
font-family:"Cambria","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Cambria","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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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:"Cambria","serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";
font-family:"Cambria","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.styleheading1notboldblack, li.styleheading1notboldblack, div.styleheading1notboldblack
{mso-style-name:styleheading1notboldblack;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo5;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix, li.styleappendix, div.styleappendix
{mso-style-name:styleappendix;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo6;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack0, li.styleheading1notboldblack0, div.styleheading1notboldblack0
{mso-style-name:styleheading1notboldblack0;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo7;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix0, li.styleappendix0, div.styleappendix0
{mso-style-name:styleappendix0;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo8;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack00, li.styleheading1notboldblack00, div.styleheading1notboldblack00
{mso-style-name:styleheading1notboldblack00;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo9;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix00, li.styleappendix00, div.styleappendix00
{mso-style-name:styleappendix00;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo10;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack000, li.styleheading1notboldblack000, div.styleheading1notboldblack000
{mso-style-name:styleheading1notboldblack000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo11;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix000, li.styleappendix000, div.styleappendix000
{mso-style-name:styleappendix000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo12;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack0000, li.styleheading1notboldblack0000, div.styleheading1notboldblack0000
{mso-style-name:styleheading1notboldblack0000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo13;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix0000, li.styleappendix0000, div.styleappendix0000
{mso-style-name:styleappendix0000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo14;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack00000, li.styleheading1notboldblack00000, div.styleheading1notboldblack00000
{mso-style-name:styleheading1notboldblack00000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo15;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix00000, li.styleappendix00000, div.styleappendix00000
{mso-style-name:styleappendix00000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo16;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack000000, li.styleheading1notboldblack000000, div.styleheading1notboldblack000000
{mso-style-name:styleheading1notboldblack000000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo17;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix000000, li.styleappendix000000, div.styleappendix000000
{mso-style-name:styleappendix000000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo18;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
p.styleheading1notboldblack0000000, li.styleheading1notboldblack0000000, div.styleheading1notboldblack0000000
{mso-style-name:styleheading1notboldblack0000000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level2 lfo2;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleappendix0000000, li.styleappendix0000000, div.styleappendix0000000
{mso-style-name:styleappendix0000000;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l1 level1 lfo4;
font-size:14.0pt;
font-family:"Cambria","serif";
font-weight:bold;}
span.heading1char0
{mso-style-name:heading1char;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.heading2char0
{mso-style-name:heading2char;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.bodytextchar0
{mso-style-name:bodytextchar;
mso-style-priority:99;
font-family:"Cambria","serif";}
span.balloontextchar0
{mso-style-name:balloontextchar;
mso-style-priority:99;
font-family:"Tahoma","sans-serif";}
span.heading1char00
{mso-style-name:heading1char0;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.heading2char00
{mso-style-name:heading2char0;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.bodytextchar00
{mso-style-name:bodytextchar0;
mso-style-priority:99;
font-family:"Cambria","serif";}
span.balloontextchar00
{mso-style-name:balloontextchar0;
mso-style-priority:99;
font-family:"Tahoma","sans-serif";}
span.heading1char000
{mso-style-name:heading1char00;
mso-style-priority:9;
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.heading2char000
{mso-style-name:heading2char00;
mso-style-priority:9;
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.bodytextchar000
{mso-style-name:bodytextchar00;
mso-style-priority:99;
font-family:"Cambria","serif";}
span.balloontextchar000
{mso-style-name:balloontextchar00;
mso-style-priority:99;
font-family:"Tahoma","sans-serif";}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Cambria","serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle53
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle54
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle55
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle56
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle57
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle58
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle59
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle60
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle61
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle62
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle63
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle64
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle65
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle66
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:675117133;
mso-list-template-ids:-319017128;}
@list l0:level1
{mso-level-style-link:"Heading 1";
mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level2
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level3
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level4
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level5
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level6
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level7
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1
{mso-list-id:1691636573;
mso-list-template-ids:1894306706;}
@list l1:level1
{mso-level-style-link:styleappendix;
mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level2
{mso-level-style-link:"Heading 2";
mso-level-suffix:space;
mso-level-text:"%1\.%2\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.3in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level3
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level4
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level5
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level6
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level7
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2
{mso-list-id:1917012928;
mso-list-type:hybrid;
mso-list-template-ids:-528556522 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I find the interest and ideas in generating a viable PWG Cloud Imaging model most gratifying. Although many approaches may have some merit, I think our model must work to properly identify what imaging service access capabilities the User should have, and what the functional elements must be on the Cloud Print Manager and Device side. Our primary interest in the Cloud-resident components might be best limited to a symbolic structure that defines the services necessary to match User requirements with available imaging services.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>With respect to defining protocols, I agree that that is not the purpose of the Requirements and Model document, but rather of the bindings that will be developed to implement the Model. However, we know the characteristics of the primary binding that we have in mind and although it might not be a pure approach, it is realistic that we try to avoid having our Model impose inappropriate requirements upon the IPP binding that we intend to use.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Having proposed these general considerations (which indeed may be subject to disagreement), I would like some time to consider the comments so far to see if we can state the points and counterpoints concisely, and then present them to the working group. But the model is an evolving beast as are our thoughts about it, so please continue your comments.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </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"'> cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] <b>On Behalf Of </b>Petrie, Glen<br><b>Sent:</b> Friday, June 08, 2012 6:08 PM<br><b>To:</b> Murdock, Joe; larryupthegrove; ptykodi@tykodi.com<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree. However, the PWG does need to provide more than just a model. We do need to provide a well-defined standard interface for the CPS, CPSS and CPM to provide interoperability between vendors, otherwise why are we bothering? I agree that that interface does not need to be IPP (I’d argue for a SOAP based model, but that’s just me), but since we do have a Semantic Model that provide all of the pieces we need, we should use what we can of that.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I agree that PWG needs to create a model. But if an Epson Cloud Print Solution wants to use Zeta-Zed-92 communication protocol between a CPS and a CPM who is to know. Both entities can be instantiated by Epson (or through an Epson service for non-Epson Cloud Print Solutions). The communication must meet certain conditions but does not have to be IPP. In my architectural concept, that communication is denoted as a connection with no constrains/conditions on the CPS/CPM and is not the thrust of the architecture. The architecture needs to focus on all the components; i.e. how does a transform service get registered, are transform service private or public, are transform service (like printers) associated with Users, what is needed to support print client in all environments, what is the API between the client and CPS's, how to support federation of jobs between two Cloud Print Solutions, on and on; done of which are IPP related but needs standardization. We can simply state that from the PWG point-of-view the CPS/CPM communication is IPP and move on to the rest of the Cloud Print Solution. If there is not interest in the rest of the solution, then we can rename the project to "IPP for CPS to CPM communication" or "IPP for Cloud".<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I have wondered about the interoperability question; what needs to be interoperable, are the front-ends. That is, how to submit job, job format and how to get State, Status and Error (SSE). <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:blue'>From a User's point-of-view what else do they need or want. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:blue'>They want to register themselves and printers they own along with association of owned and available printers. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:blue'>From Google Cloud Print point-of-view what else do they need or want. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:blue'>They want to provide the user with a mechanism to set attributes for a print job based on the capabilities of the selected printer<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:blue'>From Cloud Print Provider point-of-view what else do they need or want. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:blue'>They want to receive print jobs for a specific printer (CPS), execute the job and return SSE to the User (or caller for embedded solutions)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>A print vendor wants to support all common and agreed upon set of external (exposed) job, capabilities, SSE APIs. But is the CPS/CPM communication actually an exposed API?<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.25in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So,<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo20'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree on your example 1, but we do need to define a set of standard binding. I thing we ultimately need to provide an environment where each vendor could provide printer and a compatible Cloud Print Manager (and yes it should be a Cloud Print Manage, not because it necessarily in the Cloud, but because it’s providing Cloud Printing functionality)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'>I not sure yet, but if vendors supplies (instantiates) a CPS with defined front-end API, then the CPS/CPM communication issue is mute. For example, Google Cloud Print can request from an Epson Service a CPS for Model XYZ printer. YES, there is a security question, etc.; but they are solvable.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'>I am worried that a printer will have support multiple CPS/CPM communication protocol!!!!! A big issue, both in cost and complexity, for print vendors. Right now a network printer has to support GCP I/F, AirPrint, Microsoft, and others. Next it will be IPP-Everywhere; and, unless everyone in the world agrees to use IPP-Everywhere, the print vendor will still have to support multiple I/F's. If print vendors support the front-end APIs of a CPS, they let their CPS instantiation determine the communication with individual printers. That is, I may have a print with a single I/F but different I/F's among different printers. <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'>And like all other protocol, they change over time. <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo20'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Example 2 should be perfectly feasible with our model. Nothing we’re proposing prevents that. And if a particular CPS/CPSS/CPP vendor wants to use proprietary interface between their internal processing services, fine. But they should still provide a PWG-compatible binding to either IPP or SOAP/SM and REST/SM<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'>I am not sure that it is feasible; I need to examine how a processed job in the Cloud is sent, via IPP, to the CPM/Printer.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:0in'><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </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"'> Petrie, Glen [<a href="mailto:glen.petrie@eitc.epson.com">mailto:glen.petrie@eitc.epson.com</a>] <br><b>Sent:</b> Friday, June 08, 2012 1:34 PM<br><b>To:</b> Petrie, Glen; Murdock, Joe; larryupthegrove; <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a><br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Joe,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>As far as the overall generic model is concerned; my hope is that the PWG can create a very generic model (that is not constrained by any existing PWG Candidate Standards) and, then, show where and how the PWG Candidate Standards fulfill (or maybe don't fulfill) each major components and/or protocol of the solution. Example, the communication between a CPS and the Print Cloud Manager (really should be called a Printer Manager since it is not in the Cloud) does not have to IPP ! But, IPP, fulfill the need and it is easy to show how. Example 2; what if a CPS want all print job processing to be done in the cloud (SAAS) versus in the at or beyond the Printer Manager; that should be a possible solution also of the generic PWG Cloud model. PWG would note that the CPS can be implemented as an IPP print queue and, again, easy to show how.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Petrie, Glen<br><b>Sent:</b> Friday, June 08, 2012 1:15 PM<br><b>To:</b> Murdock, Joe; larryupthegrove; <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a><br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Joe,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'></ <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There is nothing to prevent, and actually a lot to recommend/require, a Cloud Print Provider from supporting multiple Cloud Print System Services, based on a variety of performance, contractual and legal agreements/reasons. It is not unusual that a customer’s requirement for a cloud service be that the customer’s data never reside on or be processed on a service that does not reside in a specified country. With a multinational Cloud Print Provider, this would necessitate they provide multiple Cloud Print System Services on multiple pieces of physical hardware that resides in multiple countries). <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/></span><span style='color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'>According to the definition in the model the Cloud Print System Service (CPSS) "creates Cloud Print Services (CPS) and enumerates CPS available to authenticated Cloud Print Users".<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Thus, you want the Cloud Print Provider (CPP) (the environment) to have multiple services that create CPS's and can enumerate CPS's; which, if I follow your use-case, span multiples countries. I don't really understand. A single CPSS could create the CPS in any country. Your statements states that the customer's data must be in a specific country; ok! The CPSS does not possess customer's data, a CPS does (may); where the CPS resides in the country of interest. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'></<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In this scenario, a user/company/printer/other service needs to have a well know endpoint to start with (the Cloud Print Provider), from which it can be redirect as necessary to the appropriate system service, and ultimately the proper print service, based on information associated with a user’s account. If we combine the Cloud Print Provider and the Cloud Print System Service this account-base separation and redirection is no longer possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/><o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'>According to the definition in the model the Cloud Print Provider "is the environment in which the CPSS and CPS's reside. " So from this definition, there would have to be multiple CPPs; one for each constrained environment. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I actually don't understand your use-case. Any CPP (Epson's, HP's, Google's, Ford's, etc.) is just the environment (the collection of cloud print software entities). Assuming it is public in a world wide sense (and not private where everything is "contained"); then there will always be single specific world wide entry points for registration, user accounts, and so forth. It is fairly likely that the entry points processing software does nothing more than redirect to one of many, many, many Cloud Print Registry (CPR) that can communicate with each other and share information (i.e. a user and printer registration data base). (Either for load balancing or in your case for domain constraint.) Any one of the CPR can instantiate a CPS and, if necessary, on a specific domain server or in a specific country.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I believe you are really discussing implementation and deployment details versus a model. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'></<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I also don’t like the idea of renaming the Cloud Print Provided as the Cloud Print Registry, as registering a printer is only a small portion of it job. It does not register a user, rather it authenticates a user account that was previously setup via a marketing/sale organization. </span><span style='color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'>/><o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>What does marketing/sales organization have to do with User registration? I did not go to my or Google's sales or marketing group to register in the Google Cloud Print (Provider). Or do you associate a User with company. Example, Ford Motor Company wants an HP Cloud Print; so that sales and marketing provide the "User" (Ford) with an account (actually, a complete Cloud Print Solution). I believe the term User means an individual but could be a group. An indeed a CPR could register Users; that is an implementation of the Cloud Print Solution. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'></<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It does not register a Cloud Print System Service, rather it creates one or more Cloud Print Systems as dictated by the same marketing/sales organizations (based on customer requirements), with additional input from an IT organization. It does not even really register a printer, rather it creates a Cloud-based Printer Service to receive and handle jobs for that printer<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'>/><o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Again, I believe your model is that a Cloud Print System Service is Cloud Print Bundle that is sold to companies. While, I believe the model, generically, describes any Cloud Print Solution.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>We all understand (at least I hope so) that "Printer registration" implies creation of a CPS representing the physical (maybe not even a physical) printer. If the CPSS creates CPS and it does not register the CPS; then who does. It makes perfect sense that if the CPSS instantiates a CPS it should register is some data base. And, since, the CPSS (by definition) is supposed to enumerate CPS for a User; it does have to have access to both a User data base and CPS data base and association data for both the User and the collection of CPS's.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>glen<o:p></o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> Murdock, Joe <a href="mailto:%5bmailto:jmurdock@sharplabs.com%5d">[mailto:jmurdock@sharplabs.com]</a> <br><b>Sent:</b> Friday, June 08, 2012 12:21 PM<br><b>To:</b> larryupthegrove; <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a>; Petrie, Glen<br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don’t agree with combine the Cloud Print Provider and the Cloud Print System Service functionality. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There is nothing to prevent, and actually a lot to recommend/require, a Cloud Print Provider from supporting multiple Cloud Print System Services, based on a variety of performance, contractual and legal agreements/reasons. It is not unusual that a customer’s requirement for a cloud service be that the customer’s data never reside on or be processed on a service that does not reside in a specified country. With a multinational Cloud Print Provider, this would necessitate they provide multiple Cloud Print System Services on multiple pieces of physical hardware that resides in multiple countries). In this scenario, a user/company/printer/other service needs to have a well know endpoint to start with (the Cloud Print Provider), from which it can be redirect as necessary to the appropriate system service, and ultimately the proper print service, based on information associated with a user’s account. If we combine the Cloud Print Provider and the Cloud Print System Service this account-base separation and redirection is no longer possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I also don’t like the idea of renaming the Cloud Print Provided as the Cloud Print Registry, as registering a printer is only a small portion of it job. It does not register a user, rather it authenticates a user account that was previously setup via a marketing/sale organization. It does not register a Cloud Print System Service, rather it creates one or more Cloud Print Systems as dictated by the same marketing/sales organizations (based on customer requirements), with additional input from an IT organization. It does not even really register a printer, rather it creates a Cloud-based Printer Service to receive and handle jobs for that printer<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And yes, of course the term “Printer” in all of these diagrams should really be read as “Imaging”. It may be appropriate to do that now, and just limit the scope of Imaging to be printing for now.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>larryupthegrove<br><b>Sent:</b> Thursday, June 07, 2012 2:44 PM<br><b>To:</b> <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a>; 'Petrie, Glen'<br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Glen raises some interesting points for the next discussion. The challenge is that the activities in the cloud are provider dependent, so there could be a wide variety of implementations. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would like to leave client, but possibly add a cloud print client as part of the association. Long term I could see cloud print provider becomes cloud imaging provider, and “print” gets replaced with “scan”, “fax”, etc. Then we can reuse a lot of the diagrams and work.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I updated the sequence drawings, adding a Print sequence and an Enumeration sequence.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.vsd">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.vsd</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Larry Upthegrove<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Paul Tykodi<br><b>Sent:</b> Thursday, June 07, 2012 1:05 PM<br><b>To:</b> 'Petrie, Glen'<br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Glen,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I like your choice of the name registry. I find myself continually getting confused as to the actual tasks undertaken by some of the components that live within the Cloud in our current model.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>At least for me, the use of the word registry really helped with the conceptual understanding.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/Paul<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>--</span><span style='font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Paul Tykodi<br>Principal Consultant<br>TCS - Tykodi Consulting Services LLC<br><br>Tel/Fax: 603-343-1820<br>Mobile: 603-866-0712<br>E-mail: <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a></span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>WWW: </span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><a href="http://www.tykodi.com/" target="_blank"><span style='font-family:"Arial","sans-serif"'>http://www.tykodi.com</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></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"'> cloud-bounces@pwgorg <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Petrie, Glen<br><b>Sent:</b> Thursday, June 07, 2012 12:05 PM<br><b>To:</b> Petrie, Glen; William A Wagner; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>In fact, considering the functions of the Cloud Print System Service, the Cloud Print System Service should be called the Cloud Print Registry. This is where the User, Print Services, Transforms, etc are registered. It is the place where User-to-'Print Service' association is done. It is the place where a lot of the security and access functionality is done (i.e User login, access token, etc.). Now in the model diagram, the arrow going to the "cloud-boundary" now go the Cloud Print Registry. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>[ I believe using system service in the name here will be a big problem later when we define an MFD and have the MFD system service.]<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> Petrie, Glen <br><b>Sent:</b> Thursday, June 07, 2012 7:46 AM<br><b>To:</b> Petrie, Glen; 'William A Wagner'; 'cloud@pwg.org'<br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Can the methods of the Cloud Print Provider be moved to the Cloud Print System Service; thus, leaving the Cloud Print Provider as an environment (basically, the collection of all Cloud Print entities in a specific cloud implementation).<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> Petrie, Glen <br><b>Sent:</b> Thursday, June 07, 2012 7:42 AM<br><b>To:</b> Petrie, Glen; 'William A Wagner'; 'cloud@pwg.org'<br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Comment on Cloud Print Provider. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>In the current definition, the Cloud Print Provider is defined as an environment but then it methods. If the Cloud Print Provider provides methods and can perform operations then it a software entity and not just an environment. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Petrie, Glen<br><b>Sent:</b> Thursday, June 07, 2012 7:16 AM<br><b>To:</b> William A Wagner; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:blue'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I was reviewing the definition of the Client and I believe the Client does not provide the association function. It must be a Cloud entity, such as the Cloud Provider or the Cloud Print Provider (i.e. Google Cloud Print), that creates and maintains the association between the User and one or more Printers (Cloud Print Services). The Client (acting as a proxy for the User) may or may-not actually display the list of User Associated Printer Service (i.e. the Client may be an embedded Client).<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>The Client is the software component that implements the interface between the User and the Cloud Print Provider to create an Association; and to enumerate available Cloud Print Services. The Client is also implements the interface between the User and the selected Cloud Print Service to submit a Print Job and to query Job and Printer Status. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I would like to suggest the following</span><span style='font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>The Client is the software proxy implementing an interface between the User and the Cloud Print Provider for selection of a specific Cloud Print Service from an enumeration list of User associated Cloud Print Services . The Client provides an interface for setting job elements which are communicated with the specific Cloud Print Service The Client obtains and provided the User with job queries and Printer status.<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>I would like to also suggest that we name "Client" as "Cloud Print Client" since this is a specific type of generic Client that provides the interface specifically between the User and the Cloud Print solution. <o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwgorg</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>William A Wagner<br><b>Sent:</b> Wednesday, June 06, 2012 7:34 PM<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> [Cloud] Updated Mapping and Model Drafts</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Interim level, definitely work-in-progress drafts reflecting considerations during the June face-to-face meeting are posted as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.docx">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.docx</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>and<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.docx">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.docx</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Note that un-redlined versions of MS Word documents may be obtained from redline versions.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Comments are appreciated.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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><p class=MsoNormal><span style='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>