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=utf-8"><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:"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:"Arial MT";}
@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";}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial MT";
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{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:1561750489;
mso-list-type:hybrid;
mso-list-template-ids:1844217158 985287930 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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='color:#1F497D'>Last week’s conference call did not have a quorum, so we will try again this week.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span></p><p class=MsoNormal>There will be a Cloud conference call on Monday<span style='color:#1F497D'> </span><span style='color:#1F497D'>24 Feb </span>at 3PM E<span style='color:#1F497D'>S</span>T (Noon PDT).<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>AUDIO:</span> <span style='color:#1F497D'>Phone Bridge<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'> Call-in toll-free number (US/Canada): 1-866-469-3239<br> Call-in toll number (US/Canada): 1-650-429-3300 (Primary)<br> Call-in toll number (US/Canada): 1-408-856-9570 (Backup)<br><br> Attendee Access Code: *******#<br> Attendee ID Code: # (empty)<br><br>If you need the Attendee Access code, please email me a request.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>VIDEO: </span>PWG WebEx. <o:p></o:p></p><p class=MsoNormal>Topic: IPP/Cloud WG <o:p></o:p></p><p class=MsoNormal>Date: Every Monday<o:p></o:p></p><p class=MsoNormal>Time: 3:00 pm, Eastern Daylight Time (New York, GMT-04:00) <o:p></o:p></p><p class=MsoNormal>Meeting Number: 682 763 393 <o:p></o:p></p><p class=MsoNormal>Meeting Password: Printing123 <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>To join the online meeting (Now from mobile devices!) <o:p></o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>1. Go to <a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&RT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&RT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal>2. If requested, enter your name and email address. <o:p></o:p></p><p class=MsoNormal>3. If a password is required, enter the meeting password: Printing123 <o:p></o:p></p><p class=MsoNormal>4. Click "Join". <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>NOTE that conference uses phone bridge as indicated above, not audio with PWG Webex <o:p></o:p></span></p><p class=MsoNormal>To view in other time zones or languages, please click the link: <o:p></o:p></p><p class=MsoNormal><a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&ORT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&ORT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>For assistance <o:p></o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>1. Go to <a href="https://ieee-isto.webex.com/ieee-isto/mc">https://ieee-isto.webex.com/ieee-isto/mc</a> <o:p></o:p></p><p class=MsoNormal>2. On the left navigation bar, click "Support". <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To add this meeting to your calendar program (for example Microsoft Outlook), click this link: <o:p></o:p></p><p class=MsoNormal><a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAgN0HgWlP05sWLy7lRjCXMtc9FsW9s-XNPklCRd8QoYu&RT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAgN0HgWlP05sWLy7lRjCXMtc9FsW9s-XNPklCRd8QoYu&RT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;color:#993366'><br></span><span style='font-size:10.0pt'><br></span>Agenda:<br>(1) PWG IP Policy and Minute Taker <br>(2) <span style='color:#1F497D'>Approve</span> <span style='color:#1F497D'>Cloud minutes from February Face-to-face (<a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20140204.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20140204.pdf</a>) <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(3) Review updated Draft</span><span style='color:#1F497D'> </span><span style='color:#1F497D'> <a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20140216.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20140216.pdf</a> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(4) Consider whether Cloud Imaging Model workgroup should have more projects (e.g., comparison of PWG model to existing Cloud Imaging Services)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Following are review comments from F2F minutes with my actions with regard to text, questions and comments. (Comments are underlined)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Review of Cloud Imaging Model<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>a. <a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20140128.docx">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20140128.docx</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>b. Q: How does client discover cloud services? <u>Added paragraphs on this and showed lines on diagram</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Two ways:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Client-side account credentials point to cloud system control <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>service, and client uses ListAllServices operation to get a list <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>of available services (similar to CUPS-Get-Printers and <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>future IPP Get-Printers operation for IPP System Control <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Service spec)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>2. LDAP/DNS-SD/etc. discovery protocols for public services <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>(e.g. hotel managed printing services)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>c. Q: Does the IDS group deal with client/proxy association/registration issues? <u>No effect</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Yes, that will be one of the items addressed by IDS<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>d. Q: Do we assume proxy can register with multiple cloud services?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><a name=2></a><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Yes <u>Fanout instance included see (comment 'i')<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>e. Q: Any kind of financial elements with proxy interface?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: No, that is external to the model (i.e. there is a pre-existing business relationship that enables registration) no effect<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>f. Section 4.1.2.1: <u>changes made</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Line 727: "The proxy also periodically queries ..."<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Line 728: "to check for waiting jobs" (drop "notification of")<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Lines 729-734: Move "A failure to ..." after following paragraph, "failure to receive a query from the Proxy".<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>g. Section 4.1.2.2:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>owner == Local Imaging System Owner <u>changes made</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>h. Q: What about conformance requirements? <u>no effect</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Pretty loose for the model spec, binding specs will have the <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>usual SHOULD, MUST, etc.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Historically, MFD Model had conformance requirements for <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>operations and elements, but interoperability requirements tend to <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>just be in the binding specs (e.g. IPP)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>i. Section 4.1.4: <u>Changes made to text and diagram</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"MS Mincho"'>⁃</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>device -> equipment<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>May have one proxy talking to multiple Cloud Imaging Services of the same or different types.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>j. Figure 4:Show one Proxy talking to multiple Cloud Imaging Services -<u>changes made</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>k. Q: Can multiple proxies be chained? no effect<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Conceptually yes. Fanout allows both direct (traditional Semantic Model/IPP interface) and indirect (the Proxy interface in the Cloud Imaging Model) usage, and this can be daisy-chained as needed. <u>Question this. Proxy can interface with service which interfaces with downstream service, and conceivably proxy can interface with service that interfaces with proxy...but what would be the purpose?<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>l. Q: What about poll delays/responsiveness? Isn't directly talking to printer faster? <u>no effect</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Bindings will likely provide long-running "get" operations - you "poll" to wait for notifications, response comes as soon as event is available<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Talking directly *is* faster, however the purpose of this model is to enable imaging when the client is unable to create a direct connection to the service due to firewall or other network restrictions<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>m. Section 4.2.1.2:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Yes, we need to be able to target a device to conform to SM/IPP fan-out<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>May change name/terminology here to follow <u>SM ? No effect</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>n. Section 4.2.2, item 5:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Q: How to represent capabilities for multiple devices?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: No way to report separate device capabilities as a single Local service </span><span style='font-size:8.0pt;font-family:"Courier New"'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Solution: register multiple Local services, one per device<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Solution: construct constraints that prevent combinations that are not supported (e.g. color, duplex, tabloid not <a name=3></a>supported by any one device)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Talk about implementation choice WRT intersection (only the common capabilities) vs. union (all capabilities) vs. separate local services - <u>Don't understand the problem. Proxy will provide composite of capabilities and status as though there were a single service. Jobs will be directed to appropriate local service by proxy. User and Cloud service do not know nor care which specific local service is being used.<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>o. Section 4.2.2.3:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Q: What about race conditions, e.g. two proxies fetching the same job?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: While we don't talk about it here, in IPPSIX we use a "first proxy to fetch wins" approach, with the other proxy getting a "not fetchable" error <u>. Answer is reasonable, but why would Cloud System provide same job to multiple proxies? Presumably User has selected desired endpoint.<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Add paragraph, "If the Job is no longer available to be fetched, an error is returned" (the model requires bindings to handle concurrency issues). <u>Comment added. Indeed , general error comment added to assumptions<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>p. Section 4.2.2.9<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Don't want best effort for registration, if everything isn't OK then the response is an error with a list of elements that are not supported <u>- It was my intent that the Cloud Service did not have to accept all the features of the Local Service that the proxy reported as available. (Just as the Local service did not need to make all of its featuires accessable)<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>("I can't do scan") or missing ("I need your geo-location"). <u>Obviously, errors will be provided in response to incomplete or erronious requests, and .text modified to reflect this. But I suggest that first example is unreasonable. Proxy will contact</u> <u>Cloud Imaging service specified by Cloud System Control Service for each local service the Proxy has listed for a Local System. Contacting the wrong Cloud Service would seem unlikely.<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>OK to ignore proxy info that the cloud doesn't care about (e.g. geo-location), do we need to report it<u>? Yes, it is dsirable so that proxy does not need to update undesired info. I believe this is covered - is it necessary to make this process clearer?<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>IPP has successful-ok-ignored-or-substituted-attributes status code<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>What about reporting mobile printer geo-location in a moving car?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Might be useful to report attributes/elements that are not required (don't tell me about your geo-location) <u>Yes , this was intent.<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>q. Section 4.2.2.11:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Should not allow proxy to deregister permanently, that is something you do through the cloud-specific interface, just like the initial setup prior to register<u>. Assume request is to change de-register to suspend registration. This, at least, is necessary.<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Q: Do we even need/want the operation?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Yes, because one proxy can register multiple systems<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>r. Section 4.2.2.13<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Response is just success or error (document not found, etc.) <u>No change</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>s. Section 4.2.2.13/4.2.2.14:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Q: Should we combine UpdateJobStatus and UpdateActiveJobs, to make a single UpdateJobs operation to update 1 to N jobs in one step?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: No, see below<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>UpdateActiveJobs response, in all cases, returns list of job IDs and their updated states in the Cloud Imaging Service<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>New "invalid" job state for jobs that are not fetched or do not exist <u>Question if this is optimum response. Why not just error message and list of fetched but cloud terminated jobs? Analogous to UpdateServiceElements, where response is error message with rejected or unwanted elements.<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>t. Section 4.2.2.15:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Eliminate GetCloudTerminatedJobs. <u>OK, Function is now implicit in UpdateActiveJobs response.<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>u. GetServiceNotifications:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>JobTerminated: Add list of terminated jobs and their states. <u>OK.</u> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>v. Figure 5:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Add a second set of GetServiceNotifications requests after the <a name=4></a>responses <u>OK<o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>w. Figure 5:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Q: Can job states persist across re-registration?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>A: Assume they can (not necessarily, but they could) and that the Proxy still does an UpdateActiveJobs to discover the fate of the old jobs. Cloud would move existing jobs to fetchable when the proxy doesn't include them in UpdateActiveJobs, as it does with any UpdateActiveJobs operation. - <u>No Text Change</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>x. Figure 6:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Drop GetCloudTerminatedJobs <u>OK</u><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>y. Figure 9:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Drop GetCloudTerminatedJobs <u>OK</u><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Add GetJobElements <u>operation OK - understood that this is to allow optional Proxy record-keeping on Job activity and resolution.<o:p></o:p></u></span></p><p class=MsoNormal style='margin-left:.5in'><u><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>GetServiceNotification includes</span></u><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'> No longer just a JobTerminated flag - includes job Id.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill Wagner<o:p></o:p></span></p></div></body></html>