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>.<div>
<div>I have a few questions:</div><div><ol><li>Is this the latest definitions for Printer and Print Job Statuses?</li><li>Has Cloud Print Imaging adopted/used these definitions?</li><li>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. </li>
</ol><div>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?</div>
<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.