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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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";}
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";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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='color:#1F497D'>Peter - thanks for the input.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>A revision to show that registration takes place with the Cloud Print Provider (creating a Cloud Print Service) seems to be appropriate. This appears to match with existing implementations where a print device can be configured as an output destination for a cloud provider. Having the registration done from the Cloud Print Manager would work for individual print devices with embedded Cloud Print Managers (from a front panel or remote interface), and a Cloud Print Manager for multiple devices hosted on a workstation/server. It seems there would also be a way for an enterprise to register multiple devices at the same time.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>In the discussions at the F2F, there was only one Cloud Print Service created to each instance of the Cloud Print Managers, but there could be multiple registrations initiated by a Cloud Print Manager that reflect different capabilities and/or devices (color, monochrome, duplex, special paper). This sounds confusing – maybe a Cloud Print Manager Service or other term for the portion of the Cloud Print Manager that talks to the Cloud Print Service?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Larry<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='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"'> Zehler, Peter [mailto:Peter.Zehler@xerox.com] <br><b>Sent:</b> Monday, May 14, 2012 5:20 AM<br><b>To:</b> larryupthegrove; cloud@pwg.org<br><b>Subject:</b> RE: [Cloud] Cloud white board diagram from meeting - converted tovisio/pdf<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>All,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The main problem I have with the diagram is that it shows a Cloud Print Manager registering with the Cloud Print Service instead of the Cloud Print Provider. In my (protocol centric) view a upon the receipt of a registration request from a Cloud Print Service, or its agent, the Cloud Print Provider instantiates a cloud environment specific implementation of a Cloud Print Service. The requirements for that implementation are that it implements the PWG Print Service interface, exposes the appropriate objects and attributes, and externally conforms to the state models codified in the PWG model. At a later time the Cloud Print Manager will bind to the Cloud Print Service to provide updated status and capability information and to process Print Jobs destined for the physical printer(s) associated with the Cloud Print Manager. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I expect the normal cardinality would be one physical device per Cloud Print Manager and One Cloud Print Manager per Cloud Print Service. The PWG model accommodates both Fan-Out and Fan-In of Printers. This allows a Cloud Print Manager to “front end” a number of physical printers. Those printers can be collocated (i.e., printer farm) or distributed (e.g., FedEx printer in Google Cloud Print). Alternatively a single physical device could be associated with a Cloud Print Manager that registers multiple Cloud Print Services. The purpose of such a configuration could be to present different capabilities and/or different defaults for each of the Cloud Print Services.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The [Print] Client is shown sending an Association request to the Cloud Print Provider. Once the association is established and based on the policies in place for the associated user, a set of Cloud Print Services will be visible to the [Print] Client. The [Print] Client can then interact (e.g., query status, query capabilities, submit print jobs) with the Cloud Print Service.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </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> </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:[mailto:cloud-bounces@pwg.org]">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>larryupthegrove<br><b>Sent:</b> Friday, May 11, 2012 7:05 PM<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> [Cloud] Cloud white board diagram from meeting - converted tovisio/pdf<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.vsd">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.vsd</a><o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.pdf</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please review and I’ll update drawing before inserting into the cloudmodel draft.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Larry<o:p></o:p></p><p class=MsoNormal><o:p> </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>