Smith,
It would be extremely useful to know *why* you collect each of these data items - what is the use case, how is the information used, etc?
> On Oct 11, 2019, at 2:35 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp at pwg.org> wrote:
>> Hi Mike,
>> Here are the Job Accounting fields that are important to HP Inc.:
>> • Source application name
> • Source application version
> • Client operating system name
> • Client operating system version
> • Source document name(s)
> • Job UUID
> • Client host network identifier(s) (hostname, various addresses)
> • Client User identifiers (including qualifiers such as Windows Active Directory domain names)
> • Extensibility mechanism to handle ISV extensions
>> I believe all of these have pretty clear mappings to currently defined IPP Job Description or Job Status attributes, though the details may depend on the values held by these attributes having a particular content or structure.
>> Smith
>> /**
> Smith Kennedy
> HP Inc.
> */
>>> On Sep 27, 2019, at 9:07 AM, Michael Sweet via ipp <ipp at pwg.org> wrote:
>>>> All,
>>>> The IPP workgroup is working on a Best Practice document on job accounting and managed printing solutions and would like your help in identifying key functionality and data elements needed to support those solutions. The ultimate goal is to determine any gaps and have specifications and best practices in place to better support job accounting and managed printing through IPP, rather than depending on vendor MIBs and network protocols, which will allow all types of IPP clients to utilize these solutions seamlessly.
>>>> To this end, I am asking that any member that has a job accounting or managed printing solution to send me a list of data elements/attributes that your solution(s) depend on along with any special requirements or use cases that are addressed. Of particular importance is information that you currently gather outside of IPP since we want IPP to provide everything that is needed. All solution-specific information can be kept confidential if necessary - I will be using it to identify any deficiencies that need to be addressed in IPP or common use cases that should be highlighted in our Best Practice document.
>>>> Also, I would be very interested to know whether your solutions use IPP or some other protocol(s), and the reasons for doing so - again so that we can make sure that IPP can satisfy as many printing requirements and use cases as possible.
>>>> We plan to next discuss this topic at the November 2019 Face-to-Face, and your participation in this effort would be greatly appreciated! Please send all information to "msweet at msweet.org" and I will summarize what I receive at the F2F.
>>>> Thank you!
>>>> ________________________
>> Michael Sweet
>>>>>>>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org>>https://www.pwg.org/mailman/listinfo/ipp>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet