attachment

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">In general you can't assume that any data or document from the government is not copyrighted since contractors often hold joint copyright (and patents, etc.) with the government, and there are more contractors than civil service...<div> </div><div>In any case, based on Ira's statement I'm thinking we'll want to reference the NIST definitions and describe how Cloud Imaging fits in...</div><div> <div><div>On Apr 15, 2011, at 12:54 PM, Petrie, Glen wrote:</div> <blockquote type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 11 (filtered medium)"> <base href="x-msg://239/"> <o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"> <o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">  <style>  </style> <div lang="EN-US" link="blue" vlink="blue" style="word-wrap: break-word;-webkit-nbsp-mode: space; -webkit-line-break: after-white-space"> <div class="Section1">NIST is a <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> agency and, as so, work products are not copyrighted (I believe by law).  In fact their top page on cloud computing has the following statement.<o:p></o:p><o:p> </o:p>�This material is public domain although attribution to NIST is requested. It may be freely duplicated and translated.�<o:p></o:p> So maybe we should ask a different question.   Do we want to (very) tightly align our definition with content from NIST?  I vote yes because it shows coherence/alignment/??? with existing or other organization. <o:p></o:p><o:p> </o:p>Note that the NIST definition and the one I propose are very high level and interpretation for �Imaging� is what is are address.<o:p></o:p><o:p> </o:p>Glen<o:p></o:p><o:p> </o:p>p.s. If I can find the contact information I will send a note.<o:p></o:p><o:p> </o:p>gwp<o:p></o:p><o:p> </o:p> <div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="100%" align="center" tabindex="-1"> </div>From: Petrie, Glen Sent: Friday, April 15, 2011 12:45 PM To: Petrie, Glen; Michael Sweet Cc: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a> Subject: RE: [Cloud] Fwd: NIST cloud defs<o:p></o:p> </div><o:p> </o:p>Sorry Mike,  I skipped over the part where you like the substance.   So I will send a note NIST folks.<o:p></o:p><o:p> </o:p> <div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="100%" align="center" tabindex="-1"> </div>From: <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, April 15, 2011 12:41 PM To: Michael Sweet Cc: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a> Subject: RE: [Cloud] Fwd: NIST cloud defs<o:p></o:p> </div><o:p> </o:p>Your right about the �copying� but that can be addressed at a later date.  For the moment; is this the type of definition that was intended?  If not, can you or others suggest a couple to sentence on a definition?<o:p></o:p><o:p> </o:p>I understand your point on �Imaging� versus �Printing/Printer�; but can we put together a Print/Printing first at then see how to scope it for Imaging?<o:p></o:p><o:p> </o:p>Glen<o:p></o:p><o:p> </o:p><o:p> </o:p> <div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="100%" align="center" tabindex="-1"> </div>From: Michael Sweet [mailto:msweet@apple.com] Sent: Friday, April 15, 2011 12:15 PM To: Petrie, Glen Cc: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a> Subject: Re: [Cloud] Fwd: NIST cloud defs<o:p></o:p> </div><o:p> </o:p> <div>Glen,<o:p></o:p> </div> <div><o:p> </o:p> </div> <div>While I like the substance of the definition, I am uneasy about copying their words like this - it would be good to contact the authors to get their written permission so that we credit them appropriately in the cloud model spec.<o:p></o:p> </div> <div><o:p> </o:p> </div> <div>Also, since we *are* doing Cloud Imaging, we probably want the definition to use Cloud Imaging instead of Cloud Printing and Imaging Device instead of Printer.<o:p></o:p> </div> <div><o:p> </o:p> </div> <div>Thanks!<o:p></o:p> </div> <div><o:p> </o:p> <div> <div>On Apr 15, 2011, at 8:44 AM, Petrie, Glen wrote:<o:p></o:p> </div><o:p> </o:p> <span style="orphans: 2;text-align:-webkit-auto;widows: 2;-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;word-spacing: 0px"> <div link="blue" vlink="blue"> <div>Based on the article referenced below I modified in an attempt to create a definition for cloud printing.   I thought it could be reviewed to see if could be useful definition.   In most cases, I literal changed �computing� to �printing� (or printer).  I also added a few print related items.<u1:p></u1:p><o:p></o:p> </div> <div><u1:p> </u1:p><o:p></o:p> </div> <div><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/CloudPrintingDef_V01_-_A_Suggestion.doc">ftp://ftp.pwg.org/pub/pwg/cloud/white/CloudPrintingDef_V01_-_A_Suggestion.doc</a><u1:p></u1:p><o:p></o:p> </div> <div><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/CloudPrintingDef_V01_-_A_Suggestion.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/CloudPrintingDef_V01_-_A_Suggestion.pdf</a><u1:p></u1:p><o:p></o:p> </div> <div><u1:p> </u1:p><o:p></o:p> </div> <div>glen<u1:p></u1:p><o:p></o:p> </div> <div><u1:p> </u1:p><o:p></o:p> </div> <div><u1:p> </u1:p><o:p></o:p> </div> <div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="100%" align="center" tabindex="-1"> </div> <div>From: <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [mailto:cloud-bounces@pwg.org] On Behalf Of Ira McDonald Sent: Tuesday, April 05, 2011 9:47 AM To: <a href="mailto:cloud@pwg.org">cloud@pwg.org</a>; Ira McDonald Subject: [Cloud] Fwd: NIST cloud defs<o:p></o:p> </div> </div> <u1:p></u1:p> <div><u1:p> </u1:p><o:p></o:p> </div> <div> <o:p></o:p> </div> <div><u1:p></u1:p>---------- Forwarded message ---------- From: Brian Smithson <<a href="mailto:bsmithson@ricohsv.com">bsmithson@ricohsv.com</a>> Date: Tue, Apr 5, 2011 at 12:26 PM Subject: NIST cloud defs To: Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> To share at the meeting, if it's useful: <a href="http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc" target="_blank">http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc</a> -- Regards, Brian Smithson PMP, CSM, CISSP, CISA, ISO 27000 PA Security Research, Planning Advanced Customer Technologies Ricoh Americas Corporation <a href="mailto:bsmithson@ricohsv.com">bsmithson@ricohsv.com</a> <a href="tel:%28408%29346-4435">(408)346-4435</a><u1:p></u1:p><o:p></o:p> </div> <div><u1:p> </u1:p><o:p></o:p> </div> <div> --  This message has been scanned for viruses and  dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is  believed to be clean.<u1:p></u1:p><o:p></o:p> </div> --  This message has been scanned for viruses and  dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is  believed to be clean. _______________________________________________ cloud mailing list <a href="mailto:cloud@pwg.org">cloud@pwg.org</a> <a href="https://www.pwg.org/mailman/listinfo/cloud">https://www.pwg.org/mailman/listinfo/cloud</a><o:p></o:p> </div> </div><o:p> </o:p> <div><span style="orphans: 2;text-align:-webkit-auto;widows: 2;-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;word-spacing: 0px"> <div>__________________________________________________<o:p></o:p> </div> <div>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p> </div> </div><o:p> </o:p> </div> -- This message has been scanned for viruses and dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is believed to be clean. <o:p></o:p> </div> </div> </o:smarttagtype></o:smarttagtype></blockquote></div> <div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; 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>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair </div> </div> </div> -- This message has been scanned for viruses and dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is believed to be clean. </body></html>