1. We have taken the position that the Cloud Print Manager does not
necessarily 'manage' all jobs for a printer, that is to say, that all jobs
to the printer must go though the Cloud Print Manager; that would be a very
restrictive constraint.
2. As Ira indicated, IPP has allowed either approach (i.e., reporting
all jobs or just IPP Jobs), a less than ideal circumstance that may cause
some confusion but probably reflects some realistic compromise.
3. The corollary here might be:
a. Reporting all jobs in the printer from any source; but might there
not be security considerations?
b. Reporting all jobs going through the Cloud Print Manager; but there
may be jobs from multiple Cloud Print Services, so you have both
potentially incomplete information for how busy a printer is and potential
security concerns.
c. Reporting all jobs that were supplied by that Cloud Print Server.
4. I suggest that even knowing "all" print jobs associated with the
printer is a very poor measure of "how busy a printer is" because:
a. Any given job may be completed quickly or take significant time,
depending on various factors.
b. Jobs may have different priorities
c. Some other Print Server(s) supplying jobs to the printer may have
multiple jobs queued up
Thanks,
'Bill Wagner
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of Ira
McDonald
Sent: Wednesday, April 17, 2013 10:57 AM
To: Petrie, Glen; Ira McDonald
Cc: cloud at pwg.org
Subject: Re: [Cloud] Question on "all" print jobs
Hi Glen,
I prefer the second all alternative (report all print jobs).
IPP allows both approaches. The PWG Job Monitoring MIB (RFC 2707)
of course reports all jobs (from all job submission protocols). Some IPP
implementations that I've seen also report all print jobs.
Mike - opinion here?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<http://sites.google.com/site/blueroofmusic>
http://sites.google.com/site/blueroofmusic
<http://sites.google.com/site/highnorthinc>
http://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Wed, Apr 17, 2013 at 10:53 AM, Petrie, Glen <glen.petrie at eitc.epson.com>
wrote:
Hi,
On Monday's meeting, Paul brought up a question of the other job-submission
connections (i.e. direct network connection) to a Printer (to the Print
Manager) other than the Cloud connectivity we are discussing in this group.
This brings up the question of whether other job-submission should be
reported or not. That is, is it important or is it needed to be known "how
busy a printer is". Without knowing "all" the print jobs associated with
the printer true loading cannot be determined. This assumes the Print
Manager manages all job for a printer no matter the submission source.
* If no requirement - "A Print Manager "MUST NOT" (or at least "SHOULD
NOT") report to the Cloud Print Service jobs originating from other
job-submission services (i.e. a network print service)."
Or
* If there is a requirement - "A Print Manager "MUST" (or at least
"SHOULD") report to the Cloud Print Service the total number (and size?) of
"all" print jobs no matter the originating job-submission services."
Glen
--
This message has been scanned for viruses and
dangerous content by <http://www.mailscanner.info/> MailScanner, and is
believed to be clean.
_______________________________________________
cloud mailing list
cloud at pwg.orghttps://www.pwg.org/mailman/listinfo/cloud
--
This message has been scanned for viruses and
dangerous content by <http://www.mailscanner.info/> MailScanner, and is
believed to be clean.
--
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/20130417/b5a0505c/attachment-0002.html>