Rick,
> On Feb 14, 2020, at 8:09 PM, Rick Yardumian via ipp <ipp at pwg.org> wrote:
>> Hi,
>> In Smith’s Job Accounting Fields important to HP email( threadhttp://www.pwg.org/archives/ipp/2019/020282.html), he lists “Source document name(s)”. Is “Source document name(s)” mapped into RFC 8011 ‘document-name’ or other IPP attributes? If “Source-document-name(s)” is mapped into ‘document-name’, how is the plural of names handled?
Each Document object has its own "document-name" attribute, so a multi-document Job will have N Document objects and N "document-name" attributes.
> Canon requests that the end user have a choice to opt out of sending “Source-document-name(s)”.
Absolutely, that's the point of "printer-requested-job-attributes" - to list the attributes/values that the accounting system wants but doesn't absolutely need. The End User can then provide explicit consent via the proposed Client UI. Right now I just show a simple "yes to all", "yes to required", and "no" choice for the user, but nothing says we can't have a UI that provides check boxes in the list to allow the user to have more control over things...
> Canon thinks the mapping for currently defined IPP Job Description or Job Status attributes for Client host network identifier(s) (hostname, various addresses) is not clear. So the end user does not have clear way to opt out of sending Client host network identifier(s) (hostname, various addresses) which is not good. If Canon’s understanding is correct, Canon does not agree to the idea that Client host network identifier(s) are important.
Well, when the Client connects to the Printer it will know the Client's source address - no way around that one with a network protocol and TCP/IP sockets... The question is really whether the Printer will log or use any of that information, which normally is part of a service's privacy policy and is covered by the "printer-privacy-policy-uri" attribute. But I should probably add a section that provides additional recommendations about what the privacy policy should address (the privacy attributes registration is a little too general in this context...)
________________________
Michael Sweet