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)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{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.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:51388764;
mso-list-type:hybrid;
mso-list-template-ids:-645344532 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;}
@list l1
{mso-list-id:315233062;
mso-list-template-ids:-1374665848;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:820080133;
mso-list-template-ids:-472588712;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1161235544;
mso-list-template-ids:1861245768;}
@list l3:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1935481118;
mso-list-template-ids:-1858183872;}
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'>Hi Kelly,<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'>To elaborate a bit more on the distinction between the work of the IPP WG and the Cloud Imaging Model WG:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![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'>The Cloud WG is working on a “model” of Cloud Printing based on the PWG Semantic Model. The intent is to later expand this model to address all “Imaging” services using Cloud-based intermediaries.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![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'>The concept is that once a general model is agreed to, it will be up to the IPP WG group to specify an IPP binding and the Semantic Model WG to develop a Web Services binding.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>3.<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'>The main contributions of the Cloud Group at this point have been in identifying areas that the Semantic Model WG has had to work on, specifically the PWG Job Ticket and the additional “reverse” set of operations by which an Imaging Service (such as provided by a printer) must initiate communication with a Cloud-based intermediary to allow the interchange normally initiated by the Client.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>4.<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'>The initial idea was to handle Cloud Printing within the IPP WG, but the membership decided that a model not restricted to a specific binding was preferable. <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>5.<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'>This Cloud Imaging model is intended to be consistent with the Semantic model, and I expect will eventually be absorbed into the Semantic Model effort.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>6.<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'>The earlier Print Job Ticket Mapping activities, which have now been transferred to the Semantic Model WG, correlate Semantic Model elements with the Printer Capabilities and Print Job Ticket structures based on PPDs or XPS (MSPS), approaches used by existing Cloud Print Services. One intent of this effort was to encourage some degree of compatibility between current Cloud Print Services and the PWG Semantic Model.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo5'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>7.<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'>However, creating a model to address </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>interoperability with current or potential 3rd party Cloud Print Services is not a part of</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> the current charter of the Cloud WG, although some aspects of compatibility with some extant implementations are occasionally considered. This is perhaps a deficiency, but this path was taken because no standard exists for Cloud Print Services and existing services are considered as offering inadequate flexibility to Users. However, the Cloud WG would welcome input and requests from those familiar with and/or planning Cloud Print Services.<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><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>Michael Sweet<br><b>Sent:</b> Monday, January 28, 2013 9:36 AM<br><b>To:</b> K.D. Lucas<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> Re: [Cloud] Cloud Imaging and IPP Printer and Print Job States<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kelly,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 2013-01-28, at 1:51 AM, "K.D. Lucas" <<a href="mailto:kdlucas@gmail.com">kdlucas@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>I was looking over IPP definitions for Printer and Print Job states, according to <a href="http://tools.ietf.org/html/rfc2911">RFC 2911</a>. I found these in section <a href="http://tools.ietf.org/html/rfc2911#section-4.3.7">4.3.7</a>, <a href="http://tools.ietf.org/html/rfc2911#section-4.3.8">4.3.8</a>, <a href="http://tools.ietf.org/html/rfc2911#section-4.4.11">4.4.11,</a> and <a href="http://tools.ietf.org/html/rfc2911#section-4.4.12">4.4.12</a>.<o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal>I have a few questions:<o:p></o:p></p></div><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo1'>Is this the latest definitions for Printer and Print Job Statuses?<o:p></o:p></li></ol></div></div></blockquote><p class=MsoNormal>Yes.<o:p></o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><ol start=2 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Has Cloud Print Imaging adopted/used these definitions?<o:p></o:p></li></ol></div></div></blockquote><div><p class=MsoNormal>Yes, as Cloud Imaging is an extension of the Semantic Model which started as an abstract definition of IPP.<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><ol start=3 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3'>If so, it looks like the "Reasons" why printers and print jobs get into their various states is the most significant piece of information in these definitions. Under reasons, there seems to be some ambiguous definitions. It's not clear to me that many of the reasons are needed. <o:p></o:p></li></ol></div></div></blockquote><div><p class=MsoNormal>Can you provide some specific examples?<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><p class=MsoNormal>I'm also slightly confused about the distinction between the IPP Everywhere Group and the Cloud Imaging Group. Is the Cloud Imaging group focused on the use case where there is a Cloud Print Service in between the printer device and the client? Correspondingly I'm guessing IPP Everywhere does not address interoperability of potential 3rd party Cloud Print Services. Am I interpreting that correctly?<o:p></o:p></p></div></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>IPP Everywhere addresses basic printing and interoperability through a higher minimum set of required capabilities - protocols, file formats, etc. Basically, how do we make the existing IPP support "driverless" printing from multiple platforms?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The Cloud Imaging Model addresses printing across network boundaries, specifically where the Client is unable to communicate directly with the Printer. This has traditionally been done using output device support in IPP ("print servers") and a lot of hand-waving ("implementation-defined" behavior) but we are now tackling it directly.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The corresponding IPP binding of the Cloud Imaging Model is called IPP Shared Infrastructure Extensions - the naming of the IPP spec is different because the same model applies much more broadly than just "cloud".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Andale Mono","serif";color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></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/"><b>MailScanner</b></a>, and is <br>believed to be clean. <o:p></o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>