IPP> NOT - Requirements - still needs an accounting applicati on scenario

IPP> NOT - Requirements - still needs an accounting applicati on scenario

IPP> NOT - Requirements - still needs an accounting applicati on scenario

Hastings, Tom N hastings at cp10.es.xerox.com
Tue Jul 13 19:06:37 EDT 1999


Bill,

This discussion is why we do Requirements.  

Why don't you think that the notification that we have in the current specs
don't have enough reliability for accounting?  It would seem to me that the
TCP/IP notification delivery method which opens a channel and keeps it open
is pretty darn reliable.  Of course, the number of such channels would be an
implementation and/or a site policy decision, as would establishing the
authorization of which applications could use this method.

Also what additional job attributes would be needed for "charge-back" type
accounting?  Why couldn't we add them to IPP?

Thanks,
Tom

-----Original Message-----
From: Wagner,William [mailto:bwagner at digprod.com]
Sent: Tuesday, July 13, 1999 14:55
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