attachment-0002
<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.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;}
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";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Ira,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I am very glad that you and Mike intend to proceed with the IPP Cloud Binding, as I am to see that Pete indicates that a basis for the SOAP-based binding exists. The IPP slides were rather vague on the Cloud effort, but of course the Cloud group still has a significant amount of work to do on the model.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My comment reflected on the fact that the IPP WG (and especially you, Mike and Pete) have done a lot on the IPP Everywhere related efforts, which are coming to a conclusion. I fully understand that we all must direct our efforts in line with the need for gainful employment, and we must over-rely on those whose dedication to a project goes beyond that. I hope that more will recognize the value in this work and will contribute to it.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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"'> Ira McDonald [mailto:blueroofmusic@gmail.com] <br><b>Sent:</b> Friday, August 17, 2012 9:35 AM<br><b>To:</b> William A Wagner; Ira McDonald<br><b>Cc:</b> Randy Turner; cloud@pwg.org<br><b>Subject:</b> Re: [Cloud] new use case for cloud printing<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Bill,<br><br>I don't see why you suggested that the IPP WG is "running<br>out of steam?"<br><br>IPP Everywhere is proceeding on track. Our last PWG<br>spec (Everywhere itself) is now in PWG Last Call. Our <br>two related IETF specs (IPPS URI and LDAP Printer) are<br>moving along as expected.<br><br>Mike and I have every intention of proceeding w/ IPP<br>Multifunction work and new specs. <br><br>Cheers,<br>- Ira<br><br><br clear=all>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style='color:#3333FF'>http://sites.google.com/site/blueroofmusic</span></a><br><a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br>Temporary Cabin *** 2012 only *** 906-494-2523<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><o:p></o:p></p><div><p class=MsoNormal>On Fri, Aug 17, 2012 at 12:11 AM, William A Wagner <<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p><p class=MsoNormal>By the latest (but yet to be approved by the SC) Charter<br>(<a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20120428.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20120428.pdf</a>) the Cloud<br>WG is to specify the Model, first of Cloud Printing and then of Cloud<br>Imaging. The IPP group is to generate an IPP Binding to the Model<br>specification. In theory, the Semantic Model group was to generate "SOAP<br>binding documents for Cloud Print and Cloud Multifunction services with<br>associated XML schemas/WSDL definitions and equivalent informative REST<br>bindings". Practically, with Mike and Ira distracted, the IPP WG may be<br>running out of steam. With Pete leaving the Semantic Model WG, it seems<br>unlikely that a Cloud Imaging binding is on the to-do list. So we may want<br>to consider alternatives.<br><br>Bill W.<o:p></o:p></p><div><p class=MsoNormal><br>-----Original Message-----<br>From: <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a>] On Behalf Of<br>Randy Turner<o:p></o:p></p></div><div><div><p class=MsoNormal>Sent: Thursday, August 16, 2012 10:55 PM<br>To: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>Subject: Re: [Cloud] new use case for cloud printing<br><br><br><br>Is the output of the cloud WG going to be implementable, or are we keeping<br>things abstract, wherein some actual cloud print provider will essentially<br>"instance" our model and do a concrete implementation ?<br><br>R.<br><br>On Aug 16, 2012, at 3:05 PM, "larryupthegrove" <<a href="mailto:larryupthegrove@comcast.net">larryupthegrove@comcast.net</a>><br>wrote:<br><br>> I think this is a design decision based use case - that the cloud<br>> service would attempt to retrieve the files by a specific method. The<br>> use case of the user wanting to print a file from a service or<br>> location could also be met by requiring the user to upload the file,<br>> or click print on the file in Flickr (or other application) and select<br>> the cloud provider from the list of printers, or add the cloud print<br>> provider as a "trusted friend" in Flickr, or .....<br>><br>> Larry<br>><br>> -----Original Message-----<br>> From: <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a>] On Behalf<br>> Of William A Wagner<br>> Sent: Thursday, August 16, 2012 1:55 PM<br>> To: 'Randy Turner'; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>> Subject: RE: [Cloud] new use case for cloud printing<br>><br>> The scenario is interesting, but I think the conditions you suggest<br>> (Cloud or printer needs to authenticate on behalf of Alice to get<br>> access to the photos, but cannot use Alice's credentials) make this a<br>> problem in authentication/authorization akin to other cloud service<br>> issues rather than represent a printing specific issue. I think we<br>> discussed a similar case at the meeting and decided we would defer to<br>> cloud service provider solutions such as used in allowing friends to<br>> view cloud based photo albums or have files shared via Dropbox (send<br>> the link/password encrypted??); or revert to having Alice pull the photos<br>though her device.<br>><br>> But even if we do not attempt to define a solution, I agree that this<br>> is a potentially valid use case that we might list but decline to address.<br>><br>> Opinions from others in the working group??<br>><br>> Bill Wagner<br>><br>> -----Original Message-----<br>> From: <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a>] On Behalf<br>> Of Randy Turner<br>> Sent: Thursday, August 16, 2012 4:01 PM<br>> To: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>> Subject: [Cloud] new use case for cloud printing<br>><br>><br>> During the recent F-to-F meeting and re-reading the current cloud<br>> use-cases, I didn't see a use-case for accessing 3rd-party web site<br>> content to print "from" - an example being.<br>><br>> Alice has a photo album stored on Flickr.com. She wants to print one<br>> or more of her pictures from her Flickr album on a particular cloud<br>printer.<br>> This is similar to the print-by-reference case, in that Alice will<br>> probably specify a URL (URI) to print "from". However, the cloud<br>> service will have to authenticate on behalf of Alice to access her<br>> photo album (by reference), and Alice must not reveal her Flickr<br>> authentication credentials to the cloud service.<br>><br>> R.<br>><br>><br>> --<br>> This message has been scanned for viruses and dangerous content by<br>> MailScanner, and is believed to be clean.<br>><br>> _______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>><br>><br>><br>> --<br>> This message has been scanned for viruses and dangerous content by<br>> MailScanner, and is believed to be clean.<br>><br>> _______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>><br>><br><br><br>--<br>This message has been scanned for viruses and dangerous content by<br>MailScanner, and is believed to be clean.<br><br>_______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br><br><br><br>--<br>This message has been scanned for viruses and<br>dangerous content by MailScanner, and is<br>believed to be clean.<br><br>_______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></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>