attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ira,<div><br><div><div>On 2013-04-17, at 10:57 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div><div>Hi Glen,<br><br></div>I prefer the second all alternative (report all print jobs).<br><br></div>IPP allows both approaches. The PWG Job Monitoring MIB (RFC 2707)<br></div>of course reports all jobs (from all job submission protocols). Some IPP<br>
</div><div>implementations that I've seen also report all print jobs.<br><br></div><div>Mike - opinion here?<br></div></div></blockquote></div><div><br></div>See my separate response to Glen; in this case he is talking about what the Manager can report up to the Cloud Print Service, and in that respect the interface only allows the Cloud Print Service to see the jobs it is managing/has submitted to the local Print Service through the Manager, and I don't think we want to start advertising information about local jobs to the Cloud Print Service - that kind of information disclosure would be a serious security issue and violates one of the design requirements we have for confidentiality.</div><div><br></div><div>Locally I would expect jobs that originate from/through the Cloud to show up in the local Print Service's list of jobs, with the usual security policies in place (only authorized users can see the details of jobs, otherwise you just see the local job id placeholder)</div><div><br></div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></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>