Hi Glen,
Contact info - the NIST website for Cloud Computing says:
"To learn more about NIST's cloud efforts, join the NIST cloud computing
announcement mailing list (very low volume) by sending an email to "
listproc at nist.gov" with "subscribe cloudlist" in the message body text."
(I just subscribed to this list).
The attribution needs to be to US NIST, *not* to the individual authors
of the NIST Cloud Computing definition.
For customers (especially government departments) purchasing
devices/services in the US, the NIST definition of Cloud Computing
is authoritative.
WHY are we quoting them, rather than just referencing them?
I'm strongly opposed to a PWG definition of Cloud Imaging or
Cloud Printing that diverges *at all* from the NIST definition.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Christmas through April:
579 Park Place Saline, MI 48176
734-944-0094
May to Christmas:
PO Box 221 Grand Marais, MI 49839
906-494-2434
On Fri, Apr 15, 2011 at 3:54 PM, Petrie, Glen <glen.petrie at eitc.epson.com>wrote:
> NIST is a US 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.
>>>> “This material is public domain although attribution to NIST is requested.
> It may be freely duplicated and translated.”
>> 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.
>>>> Note that the NIST definition and the one I propose are very high level and
> interpretation for “Imaging” is what is are address.
>>>> Glen
>>>> p.s. If I can find the contact information I will send a note.
>>>> gwp
>>> ------------------------------
>> *From:* Petrie, Glen
> *Sent:* Friday, April 15, 2011 12:45 PM
> *To:* Petrie, Glen; Michael Sweet
>> *Cc:* cloud at pwg.org> *Subject:* RE: [Cloud] Fwd: NIST cloud defs
>>>> Sorry Mike, I skipped over the part where you like the substance. So I
> will send a note NIST folks.
>>> ------------------------------
>> *From:* cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] *On Behalf Of
> *Petrie, Glen
> *Sent:* Friday, April 15, 2011 12:41 PM
> *To:* Michael Sweet
> *Cc:* cloud at pwg.org> *Subject:* RE: [Cloud] Fwd: NIST cloud defs
>>>> 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?
>>>> 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?
>>>> Glen
>>>>> ------------------------------
>> *From:* Michael Sweet [mailto:msweet at apple.com]
> *Sent:* Friday, April 15, 2011 12:15 PM
> *To:* Petrie, Glen
> *Cc:* cloud at pwg.org> *Subject:* Re: [Cloud] Fwd: NIST cloud defs
>>>> Glen,
>>>> 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.
>>>> 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.
>>>> Thanks!
>>>> On Apr 15, 2011, at 8:44 AM, Petrie, Glen wrote:
>>>> 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.
>>>>>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.pdf>>>> glen
>>>>> ------------------------------
>> *From:* cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] *On Behalf Of
> *Ira McDonald
> *Sent:* Tuesday, April 05, 2011 9:47 AM
> *To:* cloud at pwg.org; Ira McDonald
> *Subject:* [Cloud] Fwd: NIST cloud defs
>>>>> ---------- Forwarded message ----------
> From: *Brian Smithson* <bsmithson at ricohsv.com>
> Date: Tue, Apr 5, 2011 at 12:26 PM
> Subject: NIST cloud defs
> To: Ira McDonald <blueroofmusic at gmail.com>
>>> To share at the meeting, if it's useful:
>http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc>> --
> Regards,
> Brian Smithson
> PMP, CSM, CISSP, CISA, ISO 27000 PA
> Security Research, Planning
> Advanced Customer Technologies
> Ricoh Americas Corporation
>bsmithson at ricohsv.com> (408)346-4435
>>>>> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>>> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean. _______________________________________________
> cloud mailing list
>cloud at pwg.org>https://www.pwg.org/mailman/listinfo/cloud>>>> __________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>> _______________________________________________
> cloud mailing list
>cloud at pwg.org>https://www.pwg.org/mailman/listinfo/cloud>>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20110415/d6e5efb8/attachment-0001.html>