attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">All,<div><br></div><div>Because we seem to be tripping over differences in terminology and our collective "big picture" of how cloud-based imaging is supposed to work, I put together the attached simplified diagram for a typical MFD that is registering Print, Scan, and FaxOut with a public cloud. Each of the local services is "connected" to a corresponding service in the cloud. I have purposely not included any fan-out in the diagram in order to focus our discussions on this simplified model. We can expand our discussions once there is agreement on the simplified model/diagram.</div><div><br></div><div>(When comparing this to the model described in IPPSIX, you'd just remove all of the non-print services from the diagram...)</div><div><br></div><div>Thoughts? Does this roughly match everyone's internal picture of cloud-based imaging?</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><img apple-inline="yes" id="22D3A232-E2F4-4DEB-B045-BA564E05CB6B" height="820" width="622" apple-width="yes" apple-height="yes" src="cid:B5FF619A-D199-45B4-A649-2EFDEEE3FB42@eastlink.ca"></div><div><br><div>_______________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div><br></div></body></html>