[IPP] Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has comments

[IPP] Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has comments

[IPP] Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has comments

Manchala, Daniel Daniel.Manchala at xerox.com
Tue Sep 10 03:44:19 UTC 2013


Michael,

Some more comments on IPP Transaction Based Printing Extensions:

Section 8.1 job-state-reasons, it would be good to specify that 'account-authorization-failed' also means invalid job-accounting-user-id and/or 'job-account-id' were not valid.  Right now it says:

'account-authorization-failed': The "job-authorization-uri" attribute was not supplied
the value supplied is not valid, or the value supplied has expired.

The same is true for section 8.2 Status Codes.  client-error-account-authorization-failed (0x41F) should also refer to invalid job-accounting-user-id and job-account-id were supplied.  Right now it says:

client-error-account-authorization-failed (0x41F); The print job creation request is
missing the "job-authorization-uri" operation attribute, the supplied value is not valid,
or the value supplied has expired.


Xerox is ok with adding the keyword to  "job-state-reason" = 'account-info-conflicting' in Section 8.1 and 'client-error-conflicting-attributes' to Section 8.2.

Thanks,
Daniel.

From: Michael Sweet [mailto:msweet at apple.com]
Sent: Tuesday, September 03, 2013 5:10 AM
To: Manchala, Daniel
Cc: ipp at pwg.org; Ira Mcdonald; Paul Tykodi
Subject: Re: Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has comments

Daniel,

Thank you for your comments.  My initial responses are inline below...

On Aug 30, 2013, at 1:27 AM, Manchala, Daniel <Daniel.Manchala at xerox.com<mailto:Daniel.Manchala at xerox.com>> wrote:
Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has the following comments.

Xerox would like to add a new "job-state-reason" to section 8.1 "job-state-reasons (1setOf type2 keyword)": "incompatible account-information".  This account ("job-account-id") is not associated with the user ("job-accounting-user-id").

No objection, although we need a proper keyword value.  'account-info-conflicting'?

Likewise, add a new associated status-code to section 8.2 "client-error-account-information-incompatible" (or something of that nature).

In this case I'd prefer to keep using client-error-conflicting-attributes and have the printer return the job-account-id and job-accounting-user-id attributes in the unsupported attributes group.


Add an attribute: "job-account-type (type2 keyword | name(MAX))<Job Template>" along with "job-account-type-supported(1setOf type2 keyword | 1setOf name(MAX))<Printer>" and "job-account-type-default(type2 keyword | name(MAX))<Printer>". The keywords initially can start with 'none', 'general', 'group' or 'visa-card', 'master-card', 'paypal','bit-coin', 'micro-mint', 'cash', 'credit-account', etc., . The preference is to use keywords as it aids in the internationalization.

We've very specifically avoided currency or payment identifiers since a) many members, including Xerox, have indicated that payment processing is done separately from the printer and b) we have no facility in IPP to express currency values or other complex, fractional types.

What would be the purpose of adding this when the printer-charge-info and printer-charge-info-uri values provide localized resources that can be displayed by the Client? Since the Client never has to have knowledge of how transactions are processed (just whether the printer needs transactional information), and since job-account-id will not (or at least SHOULD NOT) be a credit card number or other direct payment identifier, I don't see the point in telling the Client anything other than "I need a job-account-id from the user."


Add the conformance requirement in IPP: Transaction Based Printing, as an addendum to PWG 5100.3-2001 IPP:Production Printing Attributes - Set 1, Section 7 as follows:

If the Printer supports "job-accounting-user-id" then the Printer MUST support "job-account-id".

No objection to adding this.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20130910/00e3a33a/attachment.html>


More information about the ipp mailing list