attachment-0001
Hi,<br><br>I strongly urge that we keep the first class object Cloud<br>Print Manager in the functional model. How the CPM<br>communicates with actual Print Devices (Printers) is<br>now and SHOULD remain completely out-of-scope.<br>
<br>Cheers,<br>- Ira<br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div>
</div><div></div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Fri, Apr 6, 2012 at 4:19 PM, larryupthegrove <span dir="ltr"><<a href="mailto:larryupthegrove@comcast.net">larryupthegrove@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="blue" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Glen,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’m struggling with a number of statements, I agree the connection between the user and the cloud is one part of the model, and the other part is the connection of the cloud to a logical print something or other (within my system). Since the model started as an imaging model, I believe the cloud to print connection should also be usable for a scan to cloud, with different elements.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">As a user and implementer I’m focusing on where the connection to the cloud originates, and where the connection from the cloud is terminates.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So where you have in the last drawing – Vendor M and Vendor N, are those print services from different print vendors or?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Larry<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></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" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>] <b>On Behalf Of </b>Petrie, Glen<br>
<b>Sent:</b> Friday, April 06, 2012 10:35 AM<br><b>To:</b> Michael Sweet<br><b>Cc:</b> <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>; <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br><b>Subject:</b> [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model<u></u><u></u></span></p>
</div></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">Mike,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">Thanks for the update. I was reviewing the diagram again and I had noted there was no actual print entity “in the cloud”; that is, as an SAAS in cloud terminology; so adding the Cloud Print Service at least provides a cloud print SAAS.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">Some more discussion ----------<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">I am still having a problem with the use of a Cloud Print Manager (in the printer) concept (an the name) in the general context of being a cloud citizen and with associating a User with an individual Print Service (Printers). That is, it is not modeled from User’s, use-case or Cloud Provider developers’ point of view. As currently defined, the current Cloud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal"> Cloud Print Provider<u></u><u></u></p><p class="MsoNormal"> Client <---> Cloud Print Service <---> Printer<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">With “”””””maybe””””” the Printer = [ Cloud Print Manager <---> Printer(s) ] as seen from Cloud Print Provider<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Actually, I see no reason to add the Print qualifier to the Provider; that is,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"> Cloud Provider<u></u><u></u></p><p class="MsoNormal"> Client <---> Cloud Print Service <---> Printer<u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">This model states that a Client, as a proxy for the User, can access a Print Service, of the User’s Cloud Provider, to print to a User’s register print device. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">This model can be used to represent several different solutions or implementations:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><ol style="margin-top:0in" start="1" type="1"><li class="MsoNormal" style="color:blue"><span style="font-family:"Cambria","serif"">The “Cloud Provider” is Print Cloud (like HP’s or Epson’s or)<u></u><u></u></span></li>
</ol><p class="MsoNormal"> Print Cloud Provider<u></u><u></u></p><p class="MsoNormal"> Client <---> Cloud Print Service <---> Printer<span style="font-family:"Cambria","serif";color:blue"><u></u><u></u></span></p>
<ol style="margin-top:0in" start="1" type="1"><ol style="margin-top:0in" start="1" type="a"><li class="MsoNormal" style="color:blue"><span style="font-family:"Cambria","serif"">A good and bad model – requires other Cloud Solution to federate with Print Cloud Provider. This would be a big development effort for print vendors. <u></u><u></u></span></li>
</ol></ol><p class="MsoNormal" style="margin-left:.75in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal" style="margin-left:.75in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><ol style="margin-top:0in" start="2" type="1"><li class="MsoNormal" style="color:blue">
<span style="font-family:"Cambria","serif"">Cloud Print Services are integrated into a Cloud Provider like Google Cloud<u></u><u></u></span></li></ol><p class="MsoNormal"> Cloud Provider<u></u><u></u></p>
<p class="MsoNormal"> Client <---> Cloud Print Service <---> Printer<u></u><u></u></p><ol style="margin-top:0in" start="2" type="1"><ol style="margin-top:0in" start="1" type="a"><li class="MsoNormal" style="color:blue">
<span style="font-family:"Cambria","serif"">Again, good and bad. Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason.<u></u><u></u></span></li></ol></ol><p class="MsoNormal" style="margin-left:.75in">
<span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal" style="margin-left:.75in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><ol style="margin-top:0in" start="3" type="1"><li class="MsoNormal" style="color:blue">
<span style="font-family:"Cambria","serif"">The Cloud Print Service is a “mini-cloud” or a “plug-in cloud” (but still in the Cloud) that is callable by a Cloud Provider. <u></u><u></u></span></li></ol>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"> Cloud Provider<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.25in"> Client <---> \ \ <u></u><u></u></p><p class="MsoNormal" style="margin-left:.25in"> \ \<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in"> \ Cloud Print Service <---> Printer<u></u><u></u></p><p class="MsoNormal" style="margin-left:1.5in">Where there is cloud around both Cloud Print and Cloud Print Service<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in"><u></u> <u></u></p><ol style="margin-top:0in" start="3" type="1"><ol style="margin-top:0in" start="1" type="a"><li class="MsoNormal" style="color:blue"><span style="font-family:"Cambria","serif"">Yes, this looks like model in the current specification but with some slight differences.<u></u><u></u></span></li>
</ol></ol><p class="MsoNormal" style="margin-left:1.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span><span style="font:7.0pt "Times New Roman""> </span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">The Cloud Print Services are in the cloud; thus, they are cloud SAAS <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">Yes, the Print Service could be in the physical printer but virtually linked (“registered”) in the Cloud<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span><span style="font:7.0pt "Times New Roman""> </span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">A printer is associated with a single Cloud Print Service<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">>From the User’s and the Cloud Provider’s point-of-view, one Print Service is associated with one Printer. The User and Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>a.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">Internally, an individual “Print Service” can support 2, 700,039 Printers; that is something the print vendor does as part of their implementation detail. It will not affect the API’s the Cloud Provider developers uses to print to the printer. And has nothing to do with the PWG Cloud Print specification.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">>From the User’s and the Cloud Provider’s point-of-view, one Print Service (associated with one Printer) has its own queue. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>a.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">If a print vendor wants to have individual queues (the “bucket” of Print Jobs) for each printer or have one giant queue (a big “bucket”) that individual printers pull jobs from, this again, is a print vendor implementation detail. And has nothing to do with the PWG Cloud Print specification.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span><span style="font:7.0pt "Times New Roman""> </span>iii.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">From the Cloud Provider’s point-of-view, the above definitions makes all Cloud Print Service interfaces look the same; that it,<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">An individual Printer is registered and has an associated a single Print Service<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">The Cloud Provider only talks to the Printer’s Print Service for all APIs and actions. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span><span style="font:7.0pt "Times New Roman""> </span>iv.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">Thus, the goal of the PWG Cloud activity is to define the API’s and data for the Cloud Provider to/from a Cloud Print Service<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">I know – use IPP<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:2.5in"><u></u><span style="font-family:"Cambria","serif";color:blue"><span>a.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-family:"Cambria","serif";color:blue">I don’t think IPP will be used by everyone. (Who is using it now for Cloud?) What “will be used” is the PWG:PJT, which does not require IPP to be useful. PWG:PJT make federation of the Print Jobs very simple. In general PWG:PJT is a perfect candidate for cloud print. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">So the final model is something like<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"> Cloud Provider |------- a Directory/Registry of Vendor Print Clouds<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.25in"> Client <---> \ \ < -------------------- register Printers (and its Print Service) to a User <u></u><u></u></p><p class="MsoNormal" style="margin-left:.25in">
\ \<u></u><u></u></p><p class="MsoNormal"> \ Vendor M Print Cloud \ Vendor N Print Cloud<u></u><u></u></p><p class="MsoNormal">
Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p><p class="MsoNormal"> Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p>
<p class="MsoNormal"> Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p><p class="MsoNormal"> Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p>
<p class="MsoNormal"> Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p><p class="MsoNormal"> Print Service <---> Printer Print Service <---> Printer<u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue">glen<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Cambria","serif";color:blue"><u></u> <u></u></span></p><div><div class="MsoNormal" style="text-align:center" align="center"><hr align="center" size="2" width="100%">
</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""> Michael Sweet <a href="mailto:[mailto:msweet@apple.com]" target="_blank">[mailto:msweet@apple.com]</a> <br>
<b>Sent:</b> Friday, April 06, 2012 9:00 AM<br><b>To:</b> Petrie, Glen<br><b>Cc:</b> Peter Zehler; Ira Mcdonald; <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>; <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
<b>Subject:</b> Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model</span><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">[Adding <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a> since this is a cloud discussion]<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">Glen,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">In the original BOF-generated functional model, the Cloud Print Manager is either located in the Printer or attached to the Printer (e.g. in the local print server). The Cloud Print Manager manages communications between the lower-level printer interface and the Cloud Print Provider.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII art diagram in my mind looks like this:<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"> Cloud Print Provider<u></u><u></u></p></div><div><p class="MsoNormal">
Client <---> Cloud Print Service <---> Cloud Print Manager <---> Printer(s)<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud Print Provider/Service.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">There can potentially be multiple logical or physical printers behind the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IPP/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a single "queue" with one or more output devices associated with it.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><div><div><p class="MsoNormal">On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" <<a href="mailto:glen.petrie@eitc.epson.com" target="_blank">glen.petrie@eitc.epson.com</a>> wrote:<u></u><u></u></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif"">Ira, Pete,<u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Cambria","serif""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif"">I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram “is not in the cloud”. Is this true? If so, where is it “located”? <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif"">Glen<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif""> <u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Andale Mono","serif""><br>
--<span> </span><br>This message has been scanned for viruses and<span> </span><br>dangerous content by<span> </span><a href="http://www.mailscanner.info/" target="_blank"><b><span style="color:purple">MailScanner</span></b></a>, and is<span> </span><br>
believed to be clean. _______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org" target="_blank"><span style="color:purple">ipp@pwg.org</span></a><br><a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank"><span style="color:purple">https://www.pwg.org/mailman/listinfo/ipp</span></a><u></u><u></u></span></p>
</div></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">__________________________________________________<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Michael Sweet, Senior Printing System Engineer, PWG Chair<u></u><u></u></span></p></div></div><p class="MsoNormal">
<u></u> <u></u></p></div><p class="MsoNormal"><br>-- <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. <u></u><u></u></p>
</div></div></div><div><div class="h5"><br>--
<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.
</div></div></div>
<br>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br>
<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.