attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Bill,<div><br></div><div>Thanks for doing this. While there are some typos in there, it generally covers the differences accurately.</div><div><br></div><div>One comment on the basic differences on page 1:</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>The Cloud Model intentionally avoids any indication that the Cloud Service can change or configure the Local service in any way; it can only submit Jobs and monitor status. It appears that IPP-SIX also provides for management of the local Service by the "infrastructure printer".</div></blockquote><div><div><div><br></div><div>IPPSIX doesn't support remote management of local services. It would be more accurate to say that it allows for remote monitoring/accounting of individual Output Devices (Imaging Systems in SM parlance), while the current Cloud Imaging Model only allows for monitoring/accounting of the combination/collection of Output Devices/Imaging Systems associated with the Cloud Imaging Service.</div><div><br></div><div>Thus, with IPPSIX you can answer the question "How many pages did I print to the laser printer at 320 Sycamore?", but the Cloud Model cannot because the existence of local Imaging Systems/Services is (currently) hidden, as are the details of how a Proxy tells the Cloud Imaging System/Services which Imaging System it is representing at any given time. I don't know whether we want to expose those details in the Cloud Imaging Model, as those details may depend on the binding/implementation - perhaps we may want to include some discussion about which binding/implementation details are not specified in the model that need to be?</div><div><br></div><div><br></div><div>On Mar 21, 2014, at 4:29 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Times New Roman","serif";
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;}
@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]--><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><h1><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal">I have posted an operations comparison at <a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud-IPPSIX_Compare_20140321.docx">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud-IPPSIX_Compare_20140321.docx</a>. This is intended for discussion at the Monday Cloud Model conference call, at 3PM ET.<o:p></o:p></span></h1><h1><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal">Thanks,<o:p></o:p></span></h1><h1><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal">Bill Wagner</span><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal"><o:p></o:p></span></h1></div></div>_______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/cloud<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px;"><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; "><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></body></html>