IPP> OPS - Notes and Agreements on IPP Admin Ops from IPP WG meeting, 7/7/99 in Copenhagen

IPP> OPS - Notes and Agreements on IPP Admin Ops from IPP WG meeting, 7/7/99 in Copenhagen

IPP> OPS - Notes and Agreements on IPP Admin Ops from IPP WG meeting, 7/7/99 in Copenhagen

Hastings, Tom N hastings at cp10.es.xerox.com
Tue Jul 13 18:40:23 EDT 1999


Ben,

You replied to Bill and me on a thread about an event notification
specification.  However, there is another thread about Additional
Administrative Operations that includes some operations that are like what
you are talking about:

One of the proposed operations is Disable-Printer which shuts off network
jobs.
Perhaps we need to add a way to shut off walk up jobs.  Since an operator
might
want to shut off either or both kinds of jobs, we could add an OPTIONAL
operation attribute
to the Disable-Printer operation:
  "which-jobs" (type2 keyword)

where the values are:
  'network-jobs'
  'walkup-jobs'
  'all-jobs'

If the client omits the attribute (or it isn't supported), network jobs are
shut off.

How does that sound?

Also, feel free to send your comments to the IPP dl itself.  I've taken the
liberty to copy your reply to the DL and have changed the thread to the
Administrative Operations thread.

Tom

-----Original Message-----
From: Strum, Benjamin A. [mailto:bens at equitrac.com]
Sent: Tuesday, July 13, 1999 15:11
To: 'Wagner,William'
Cc: 'hastings at cp10.es.xerox.com'
Subject: RE: IPP> NOT - Requirements - still needs an accounting
applicati on scenar io


My name is Ben Strum and I am a project leader for Equitrac Corp., a company
that specialized in cost recovery systems.  I have just joined in the IPP
group and have been monitoring the email so forgive me if I am not totally
up to speed on the IPP spec.

The main deficiency that we are seeing on the newer style digital
copier/network printers is the inability for external programs to
differentiate between walkup jobs (such as copy) and network jobs (such as
print).  In addition, there is no way to enable/disable jobs by type.  I.e.,
an external program, with the right security, should be able to disable all
walk up jobs or all print jobs until a proper event ocurrs (such as valid
accounting codes).

There are definitely more features required to do accurate accounting, but
these two are the first to come to me.  If you are interested, I will try to
expand on it.

Ben Strum
Project Leader
Equitrac Corp.
http://www.equitrac.com


-----Original Message-----
From: Wagner,William [mailto:bwagner at digprod.com]
Sent: Tuesday, July 13, 1999 5:55 PM
To: 'Hastings, Tom N'; ipp
Subject: RE: IPP> NOT - Requirements - still needs an accounting
applicati on scenar io


Tom,

I believe the change in terminology was made because it was felt that the
level of service needed to support a high reliability accounting application
was beyond the scope of IPP, and that although accounting may be provided by
private extensions, the basic IPP reporting was suitable for usage
statistics and general  monitoring, not charge-back type accounting. 

Adding accounting back would appear to just undo this intention.

Bill Wagner

-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Tuesday, July 13, 1999 5:32 PM
To: ipp
Subject: IPP> NOT - Requirements - still needs an accounting application
scenar io


The notes from the IPP WG meeting in Copenhagen changed the 7th Scenario
from "audit and accounting" to "usage statistics".  That is ok, provided
that we add a new Scenario that does include an accounting application using
the notification mechanism for push type of accounting, where the IPP
Printer pushes the accounting data to the accounting application.  Here a
high Quality of Service is desirable for those sites that want to do
reliable accounting.

Here is the original Scenario 7 (which was agreed to be changed to "usage
statistics application):

7. I am an accounting or audit application. I subscribe independently from a
job submission so that my subscription outlasts any particular job.  My
subscription may persists across power cycles.  I subscribe with the
following attributes:

- Notification Recipient - me
- Notification Type - immediate
- Notification Events - job completion
- Notification Attributes - impression completed, sheets completed, time
submitted, time started, time completed, job owner, job size in octets, etc.



I suggest adding a Scenario 8:

8. I am an accounting application. I subscribe independently from a job
submission so that my subscription outlasts any particular job.  My
subscription may persists across power cycles.  I subscribe with the
following attributes:

- Notification Recipient - me
- Notification Type - immediate
- Notification Events - job completion
- Notification Attributes - time submitted, time started, time completed,
job owner, job size in octets, job-k-octets-processed,
job-impressions-completed, job-media-sheets-completed, etc.

Comments?

Tom



-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Monday, July 12, 1999 17:45
To: ipp
Subject: IPP> NOT - Notes and Agreements on IPP Notifications from IPP
WG meeting, 7/7/99 in Copenhagen


snip...

12.  Section 4, item 7, delete word "audit" and change "accounting" to
  "usage statistics".



More information about the Ipp mailing list