attachment
<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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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.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;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle20
{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;}
--></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>REMINDER to ALL: Cloud Call this afternoon at 3PM ET!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Mike,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for the comments. Sorry about the typos.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>With respect to management capability, I guess I was confused by the “MAY” operations listed in Table 4 for the Proxy (and I tend to get confused by the IPP use of “Printer” and “Output Device” terms). By my understanding, an Output Device may or may not include a Printer Object. But it is not the (possible) local Printer Object that is the object of Proxy operations such as “Activate-Printer” and “Shutdown-Printer”, which I take as management operations. Rather these are intended to allow a proxy to control the Infrastructure Printer? And, since the Proxy presumably interfaces for the “Output Device”, I wonder about operations such as “Get-Output-Device-Attributes” directed from the Proxy to the Infrastructure Printer; is this to confirm the information in “Update-Output-Device-Attributes” by which the Proxy has informed the infrastructure printer of the output device attributes?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am concerned that IPP SIX and Model differences may be more inherent than just nomenclature differences. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On the question of monitoring/accounting, the Model does include Update of Service Elements, which the set of which elements are included being determined by the proxy. Service elements could include all of the service counters. Update Job Status could similarly provide Job progress information. I do not understand your comment that, in the Model, the “existence of local Imaging Systems/Services is (currently) hidden” or that there is a question “the details of how a Proxy tells the Cloud Imaging System/Services which Imaging System it is representing at any given time”. All messages from the Proxy include the unique identification of the Local Service relative to the message. And in registering and updating Systems, it is intended that the values of all elements of the Local system that are to be made known to the Cloud System are communicated. <o:p></o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Bill W.<o:p></o:p></p><p class=MsoNormal><span style='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"'> Michael Sweet [mailto:msweet@apple.com] <br><b>Sent:</b> Monday, March 24, 2014 10:20 AM<br><b>To:</b> William A Wagner<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> Re: [Cloud] IPP SIC- Cloud Imaging Model Comparison<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bill,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for doing this. While there are some typos in there, it generally covers the differences accurately.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>One comment on the basic differences on page 1:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><p class=MsoNormal>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".<o:p></o:p></p></div></blockquote><div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>On Mar 21, 2014, at 4:29 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><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.</span><o:p></o:p></h1><h1><span style='font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>Thanks,</span><o:p></o:p></h1><h1><span style='font-size:12.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>Bill Wagner</span><o:p></o:p></h1></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>_______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/cloud">https://www.pwg.org/mailman/listinfo/cloud</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><div><div><p class=MsoNormal><span style='font-size:12.0pt;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><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p></div></div></body></html>