Chris,
As many of the members on this list do not have access to the MOPRIA Alliance Print Specification, it is a bit difficult to discuss any requirements that it has, the use cases that are being addressed, etc. Moreover, this mailing list is not an appropriate forum for filing bug reports against or making claims about any other member's IPP implementation or plans. The PWG defines voluntary, interoperable standards for printing, and we have no process for enforcing compliance with any of those standards. I would prefer that we keep any discussion focused on defining an interoperable standard for accounting with well-defined use cases and requirements that all vendors can agree to follow and support.
WRT the attributes in question, both job-account-id and job-accounting-user-id are now RECOMMENDED to support by IPP Clients in the recently published PWG 5100.7-2019: IPP Job Extensions v2.0. Additional accounting- and transaction-related attributes are defined in PWG 5100.16-2013: IPP Transaction-Based Printing Extensions (currently being reviewed for an errata update), and of course we have OAuth Authorization (PWG 5100.18-2015: IPP Shared Infrastructure Extensions and PWG 5199.10-2019: IPP Authentication Methods) that will likely be part of future corporate/managed printing solutions. Finally, we have been actively revising 5100.11-2011 (Enterprise Printing Extensions, formerly JPS2) to include discussion of Release Printing and my own "Job Accounting with IPP" best practice document which is attempting to document and make recommendations for the wide variety of accounting solutions. As these most recent documents have shown, accounting support is not just a matter of adding text fields for two RECOMMENDED Job Template attributes.
I see four specific items below that are appropriate topics of discussion in the IPP workgroup as we continue to develop the Job Accounting best practice document:
1. What are the use cases that need job-accounting-user-id but not job-account-id?
2. Do we need a way for a Printer to report that it would like the Client to show UI for and send certain Job Template attributes, above and beyond the current "printer-requested-job-attributes"?
3. What additional Client UI recommendations do we want to add to the Job Accounting best practice document? For example, what is the recommended UI for "job-account-id"?
4. How can a Printer best support a (legacy/not updated) Client whose Job Creation request is missing required or requested information?
Thanks!
> On Jan 22, 2020, at 5:36 PM, Rizzo, Christopher via ipp <ipp at pwg.org> wrote:
>> All,
>> If "job-accounting-user-id" and "job-account-id" are added to IPP "printer-mandatory-job-attributes" in an IPP Get-Printer-Attributes response, as specified by MOPRIA Alliance Print Specification 2.1 section 4.18.2.d., the Apple Mac AirPrint driver ceases to print. In other words, because Apple does not properly support this functionality, and it in fact breaks Mac printing (the print job in Mac OS Mojave is never sent - I have not tested with Catalina though), this MOPRIA IPP requirement is incompatible with AirPrint, and as a result any printer vendor implementing support for this in MOPRIA will not be able to concurrently support AirPrint. Also, it is my understanding Apple's AirPrint currently does not support job-accounting-user-id and I know of no plan for it to be supported in the future.
>> I believe there needs to be some agreement across both MOPRIA Alliance and Apple/AirPrint which includes PWG working group to try and address this issue. The current MOPRIA requirement is a "MAY", which allows vendors to just skip this MOPRIA requirement if they wish to work with both types of clients. But if in the future there is a desire to make this requirement a "MUST" (for printer vendors whose systems actually require these attributes to be sent in an IPP Print-Job or Create-Job request when accounting is enabled), then this needs to be addressed.
>> Also not addressed is the fact that some accounting implementations only require job-accounting-user-id as mandatory, as all accounting users in these implementations can have a default job-account-id assigned to all their jobs, which means job-accounting-user-id would be present in printer-mandatory-job-attributes but job-account-id would not. In this instance, job-account-id could possibly be included in printer-suggested-job-attributes, in the event the user wants to specify an alternate job-account-id other than their default.
>> Thanks,
> Chris
>> Christopher Rizzo
> Xerox Corporation
> GDG/Discovery/Advance Technology
> 26600 SW Parkway Ave.
> Wilsonville, OR 97070-9251
> Phone: (585) 314-6936
> Email: Christopher.Rizzo at xerox.com>> "The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."
> -Maurice Wilkes, Memoirs of a Computer Pioneer
> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet