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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.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:12.0pt;
font-family:"Times New Roman","serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:322317163;
mso-list-type:hybrid;
mso-list-template-ids:-1799831018 460482930 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Ira, Cloud Imaging WG members,<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'> PWG
has its timelines and process to announce standards that are faster than many
other standard bodies. But taking Randy’s point, may I suggest the
following approach:<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=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We look at the Cloud Imaging Workflow and current solutions
being offered today - current CISPs are tending to be proprietary silos in most
cases <o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Evaluate what components in the workflow and deployment usecases
that are most likely to benefit from a standardization effort from PWG and
re-order the sequence of standards being released for adoption (not that I am
stating that the current sequence may not be right)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This would enable CISPs (we are one of them) to consider
PWG standards adoption in our roadmap, especially in areas with maximum pain
points or to tackle interoperability aspects. <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'>Regards,<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'>Ranga Raj<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thinxtream Technologies<o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="http://www.thinxtream.com">www.thinxtream.com</a> <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'><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 style='margin-left:.5in'><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"'> cloud-bounces@pwg.org
[mailto:cloud-bounces@pwg.org] <b>On Behalf Of </b>Ira McDonald<br>
<b>Sent:</b> Friday, December 09, 2011 4:03 AM<br>
<b>To:</b> Randy Turner; Ira McDonald<br>
<b>Cc:</b> cloud@pwg.org<br>
<b>Subject:</b> Re: [Cloud] Minutes posted for today's face-to-face meeting<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>Hi Randy,<br>
<br>
I'm looking forward to hearing your thoughts on accelerating<br>
delivery of practical Cloud Imaging WG deliverables.<br>
<br>
But I do want to caution you that the PWG has a Candidate<br>
Standard development document lifecycle. We've never chosen<br>
to short-circuit it yet and (speaking now as a PWG officer) I<br>
don't think the Steering Committee would be very happy about<br>
doing so for a Cloud project.<br>
<br>
So - several working drafts, a Prototype draft, actual prototype,<br>
WG last call, PWG Last Call (that MUST span a F2F meeting),<br>
and PWG Formal Vote - that's well over 6 months with no content<br>
(That's about 2-3 years faster than IETF fast-track).<br>
<br>
Just FYI.<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<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Thu, Dec 8, 2011 at 4:24 PM,
Randy Turner <<a href="mailto:rturner@amalfisystems.com">rturner@amalfisystems.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<p class=MsoNormal style='margin-left:.5in'>That's similar to what I have been
asked lately -- basically, how is what we are doing going to add value to a
Cloud Print/Imaging deployment in a 2012/2013 timeframe. Is the PWG
adding value to existing solutions ? Are we benefitting end-users or vendors
with this value? One more than the other?<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>In the August 2011
"draft", we talk about helping interoperability, speeding adoption,
and addressing privacy security and legal issues.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Adoption doesn't seem to be a
problem...current solutions are gaining traction at a steady pace.
Current CISPs (Cloud Imaging Service Providers) are not going to wait for
us to solve their privacy, security, and legal issues -- for large enterprise,
these map to regulatory requirements which they have to solve now (or CSPs have
already addressed this).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>With regards to interoperability,
this would definitely be of value to end-users -- they could buy an MFP and
connect this MFP to any CISP that supports PWG recommendations/standards.
However, the vendor community seems to be leaning towards a cloud imaging
business model that is proprietary, locking their customers into THEIR
particular brand of cloud (i.e., the recent "dropbox" announcement by
Fuji Xerox). This is what I'm trying to avoid by expediting our
deliverables. It's ok for vendors to extend a basic model with
proprietary competitive advantages, as long as we have something in place (as
quickly as possible) on which vendors can provide the most common use-cases for
cloud imaging that we are thinking about.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>I think our currently specified
goals are too "geeky" and I think we need language that clearly
describes (in laymans' terms) what we're offering. Our current goals are
expressed as "mapping of PWG Print Job Ticket to/from MSPS,PPD, and
JDF..." which is ok, but I think we need to provide end-user (or
whoever our "real" customer is) scenarios of what we're trying
to accomplish.<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>I received some concerned feedback
when I referenced the schedule in the June 2011 charter -- not sure how it will
be received when I mention the proposed new schedule. In "tech"
years, 18 months is a long time. If we wait until 2013, we may find the
ground has shifted out from under us.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Over the next couple of weeks I
will try and look at someway to "short circuit" the creation of an
initial deliverable that we may can deliver in an earlier timeframe than the
proposed schedule modification. The goal here would be to try and leverage IPP
for cloud printing for the most COMMON use-case or scenario we envision.
The larger scope of what we're trying to do will encompass the full range
of functionality we're trying to deliver. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>With NAC, none of this is a problem
as I think the PWG has been very prescient in our need to drive NAC into
imaging devices, ahead of the marketplace's perceived need -- they will thank
us later :)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'>R.<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Dec 8, 2011, at 3:20 AM, Paul
Tykodi wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Hi Randy,</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>In reading through this whole
thread, I think one useful document the Cloud Imaging Working Group could
prepare immediately would be focused on organizations that have already built a
Cloud Print Service or are developing a Cloud Print Service. It would highlight
the work being done at this time by the Cloud Imaging Workgroup (mappings), the
benefits to knowing about and using PWG Semantics in their Cloud Print
Services, and the future plans for the Workgroup to produce other Cloud Print
relevant specifications.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I believe that we can limit
the fragmentation in this particular space, by promoting what the Cloud Imaging
Workgroup is building, to those who will ultimately need to decide whether to
make their particular offering conform to the standards produced or not.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I volunteer to help get such
a document written and then delivered to appropriate organizations should the
PWG determine it has merit. I don’t have enough bandwidth available to
perform the whole task by myself so I will need some help should we decide to
try and get this document created in the near term.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Thanks.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Best Regards,</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>/Paul</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:#1F497D'>--</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:#1F497D'>Paul Tykodi<br>
Principal Consultant<br>
TCS - Tykodi Consulting Services LLC<br>
<br>
Tel/Fax: <a href="tel:603-343-1820" target="_blank">603-343-1820</a><br>
Mobile: <a href="tel:603-866-0712" target="_blank">603-866-0712</a><br>
E-mail: <a href="mailto:ptykodi@tykodi.com" target="_blank">ptykodi@tykodi.com</a></span><span
style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>WWW: </span><span style='font-size:100.0pt;font-family:
"Courier New";color:#1F497D'><a href="http://www.tykodi.com/" target="_blank"><span
style='font-family:"Arial","sans-serif"'>http://www.tykodi.com</span></a></span><o:p></o:p></p>
</div>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;
border-width:initial;border-color:initial'>
<div>
<p class=MsoNormal style='margin-left:.5in'><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"'> <a href="mailto:cloud-bounces@pwg.org"
target="_blank">cloud-bounces@pwg.org</a> [mailto:<a
href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>] <b>On
Behalf Of </b>Randy Turner<br>
<b>Sent:</b> Wednesday, December 07, 2011 7:43 PM<br>
<b>To:</b> <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
<b>Subject:</b> Re: [Cloud] Minutes posted for today's face-to-face
meeting</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Ok, thanks guys!! See you on the
IDS call Thursday...<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>R.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Dec 7, 2011, at 4:33 PM, Ira
McDonald wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Hi Randy,<br>
<br>
Sure - although there was no dissent from the actual call-in participants<br>
(either Cloud WG or Steering Committee) to moving all of the original<br>
deliverables out a calendar year.<br>
<br>
That means, I think, that a whole lot of new participants have to volunteer<br>
to do some parallel work or the new draft charter is likely to be realistic<br>
about timeframes.<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 <a
href="tel:734-944-0094" target="_blank">734-944-0094</a><br>
Summer PO Box 221 Grand Marais, MI 49839 <a
href="tel:906-494-2434" target="_blank">906-494-2434</a><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Wed, Dec 7, 2011 at 4:19 PM,
Randy Turner <<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>So the updated schedule is still
under discussion? Being as that the charter you sent has not been
"approved" ? <o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'>R.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Dec 7, 2011, at 4:13 PM, Ira
McDonald wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Hi Randy,<br>
<br>
Not really (ready to use IPP now in Cloud). <br>
<br>
There's no Register-Client operation. There's <br>
no geo-location info (it's coming in JPS3 and<br>
IPP Everywhere next year). There's no UUIDs<br>
for Client, Printer, and Job - a necessity.<br>
<br>
There are no extension operations for Printers<br>
behind firewalls talking to Cloud Services<br>
(Register-Printer, Fetch-Job, Accept-Job,<br>
Reject-Job, Notify-Job) - I wrote them up on<br>
slides a year ago - that's it. <br>
<br>
We don't have the IPP operations to make<br>
Cloud Print work like any of the current shipping<br>
implementations.<br>
<br>
That's the problem.<br>
<br>
The minutes of Cloud WG meetings have recorded<br>
WG reviews of this current draft charter for 5 months<br>
and the discussion w/ SC about waiting for MSPS.<br>
<br>
The link on website is to the last *approved* charter.<br>
There's no disconnect here. The SC minutes are<br>
also publicly archived with their discussions.<br>
<br>
Cheers,<br>
- Ira<br>
<br>
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 <a
href="tel:734-944-0094" target="_blank">734-944-0094</a><br>
Summer PO Box 221 Grand Marais, MI 49839 <a
href="tel:906-494-2434" target="_blank">906-494-2434</a><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Wed, Dec 7, 2011 at 6:46 PM,
Randy Turner <<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>The charter published on the
website is from June 2011 (or at least that's what the link says), which says
that we're delivering a prototype IPP binding spec by Q4 2011, last call Q1
2012.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>If this is incorrect or outdated,
then that's fine. Maybe we should update the website if that's the case.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>The charter you reference in your
email shows only a prototype draft for IPP in Q4 / 2012 ? <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Which means you may not see
implementation of this until sometime mid 2013 maybe.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>If there are multiple vendors
shipping products now, by mid 2013, there will be quite a few deployments
that will have to support whatever they do now, and whatever the PWG proposes.
Or have a way to re-provision their network (on the fly) with something
new.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Seems like we could get something
out the door quicker than this...something that would nail down how to use just
IPP (for now) in a cloud application. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'>R.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Dec 7, 2011, at 3:07 PM, Ira
McDonald wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'>Hi Randy,<br>
<br>
Ahem - about threats to Q1 2012 schedule.<br>
<br>
The current draft charter for the Cloud Imaging WG (from September) <br>
moves all work items out a *year* and instead adds the Mapping spec <br>
as near-term (depending on Print Job Ticket written in SM WG).<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110926.pdf"
target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110926.pdf</a><br>
<br>
The Steering Committee deferred approval of that charter until we have<br>
resolves the license/copyright/reference text for the MSPS (aka XPS)<br>
chapter the Mapping spec.<br>
<br>
Cloud Print is shipping (from lots of people). It's using PPD, XPS, and <br>
probably other job tickets now - that's where we see the "low
hanging <br>
fruit".<br>
<br>
New protocol work in IPP or SOAP bindings (for Client and Printer <br>
registration with Cloud, for Fetch Jobs, NotifyJobs, etc.) is not
"low <br>
hanging fruit", we think.<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 <a
href="tel:734-944-0094" target="_blank">734-944-0094</a><br>
Summer PO Box 221 Grand Marais, MI 49839 <a
href="tel:906-494-2434" target="_blank">906-494-2434</a><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Wed, Dec 7, 2011 at 5:30 PM,
Randy Turner <<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><br>
Hi Bill,<br>
<br>
I am sensitive to the fact that there was little progress in the last year,
and I think this is my point.<br>
<br>
As I said in my most recent message, I'm not calling into question the
"work" that is being done, I'm curious as to whether the
"sequence" or "priority" of this work with regards to
publishing a Cloud Imaging profile could be an issue.<br>
<br>
What I would like to gauge from the working group is whether or not we could
declare the job ticket as an optional "package" carried by a cloud
printing job...essentially making it an abstraction in the cloud imaging model
for now and lock-down/get consensus/publish a model that takes care of all the
"low-hanging fruit" ASAP to prevent any potential fragmentation of
the cloud imaging space.<br>
<br>
It's possible to publish a Cloud Imaging solution without detailing out job
tickets -- I print jobs every day that don't use job tickets. However, as
I said before, I'm not calling into question the work that's going...I think
it's good work, I'm just looking at this project with my "PM Hat"
on..<br>
<br>
If the Cloud Imaging WG feels there's no threat to fragmentation or that
there's no risk to the Q1 / 2012 schedule, then that's fine too -<br>
<br>
R.<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><br>
<br>
On Dec 7, 2011, at 2:15 PM, William Wagner wrote:<br>
<br>
> Randy,<br>
><br>
> One of the intentions of the Cloud Imaging group was to advance the use of<br>
> the PWG Semantic Model elements in cloud imaging implementations. A well<br>
> defined PWG Job ticket is a necessary part of the Cloud Printing
(and later<br>
> Cloud Imaging) modeling effort and therefore is not bogging down the<br>
> progress of a Cloud Printing solution. However, the workgroup believed
that<br>
> correlating the PWG Job Ticket elements with elements of Print Job Tickets<br>
> currently being used (especially PPD and so-called XPS) both would assist
in<br>
> encouraging consistent and PWG element coherent use of these other job<br>
> tickets and would prepare the way for use of the PWG Print Job Ticket in<br>
> these extant cloud Printing implementations. Because the mapping effort is<br>
> primarily addressed at existing Cloud Printing applications, it may be<br>
> considered as preempting the work on the PWG Cloud Printing solution.<br>
> However, since we went almost a year without making much progress on the
PWG<br>
> Cloud Printing solution, I suggest that the mapping effort is more a<br>
> constructive diversion rather than a blocking (or
bogging) effort.<br>
> Bill Wagner<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a
href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>]
On Behalf Of<br>
> Zehler, Peter<br>
> Sent: Wednesday, December 07, 2011 1:40 PM<br>
> To: Randy Turner; <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> Subject: RE: [Cloud] Minutes posted for today's face-to-face meeting<br>
><br>
> Randy,<br>
><br>
> The "PWG Print Job Ticket and Associated Capabilities"
specification is<br>
> not bound to Cloud Printing. Cloud Printing is one environment that<br>
> would benefit from an open specification for Print Job Tickets and the<br>
> standardization for the representation of the capabilities and defaults.<br>
> All we are really doing is splitting out the job ticket, capabilities<br>
> and defaults from the PWG semantic model. This, of course, is based
on<br>
> IPP and enjoys wide support across the industry. We have an XML
schema<br>
> encoding that will be released along with the specification.<br>
><br>
> Pete<br>
><br>
><br>
> Peter Zehler<br>
><br>
> Xerox Research Center Webster<br>
> Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a><br>
> Voice: <a href="tel:%28585%29%20265-8755" target="_blank">(585)
265-8755</a><br>
> FAX: <a href="tel:%28585%29%20265-7441" target="_blank">(585)
265-7441</a><br>
> US Mail: Peter Zehler<br>
> Xerox Corp.<br>
> 800 Phillips Rd.<br>
> M/S 128-25E<br>
> Webster NY, 14580-9701<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a
href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>]
On Behalf Of<br>
> Randy Turner<br>
> Sent: Wednesday, December 07, 2011 1:24 PM<br>
> To: <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> Subject: Re: [Cloud] Minutes posted for today's face-to-face meeting<br>
><br>
> Hi Guys,<br>
><br>
> I'm assuming all of this job ticket discussion is reusable outside of<br>
> "Cloud" applications ? Or we only talking about "Cloud-specific"<br>
> attributes of print-job-tickets ?<br>
><br>
> If this discussion is NOT cloud-specific, then I would hope that this<br>
> discussion does not artificially bog down the progress of a Cloud<br>
> Printing solution...<br>
><br>
> R.<br>
><br>
><br>
> On Dec 7, 2011, at 9:56 AM, Michael Sweet wrote:<br>
><br>
>> All,<br>
>><br>
>> I have posted the minutes from today's face-to-face to:<br>
>><br>
>><br>
>> <a
href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20111207.pdf"
target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20111207.pdf</a><br>
>><br>
>> Action items:<br>
>><br>
>> - Justin to work with Microsoft Legal on the
appropriate<br>
> citation/reference to MSPS based on the new license for inclusion with<br>
> the MSPS content in the mapping document, and any process for the PWG to<br>
> make a formal request<br>
>> - Ron or Bill to post a call for wider
participation of driver<br>
> developers for the XPS/MSPS stuff<br>
>> - Mike to make "first-index" in JPS3
1-based instead of 0-based<br>
>><br>
>> _________________________________________________________<br>
>> Michael Sweet, Senior Printing System Engineer, PWG Chair<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" target="_blank">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" target="_blank">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>
> 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" target="_blank">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<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" target="_blank">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>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>,
and is <br>
believed to be clean.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><br>
_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@pwg.org" target="_blank">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>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>,
and is <br>
believed to be clean.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><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>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'><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. <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>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>______________________________________________________________________________
DISCLAIMER: This electronic message and any attachments to this electronic
message is intended for the exclusive use of the addressee(s) named herein
and may contain legally privileged and confidential information. It is the
property of Celstream Technologies Pvt Limited. If you are not the intended
recipient, you are hereby strictly notified not to copy, forward, distribute
or use this message or any attachments thereto. If you have received this
message in error, please delete it and all copies thereof, from your system
and notify the sender at Celstream Technologies or
administrator@celstream.com immediately.
______________________________________________________________________________</pre></font></td></tr></table>