Defining them in Job Extensions v1.1 seems to be what Mike is recommending in the other thread about JPS2v2.
Smith
> On Mar 7, 2019, at 10:39 AM, Ira McDonald <blueroofmusic at gmail.com> wrote:
>> Hi,
>> I hope Job Extensions, because I see them as filling holes in original IPP/1.1.
> All printers implement some Job History (perhaps pretty short-lived).
>> Cheers,
> - Ira
>> Ira McDonald (Musician / Software Architect)
> Co-Chair - TCG Trusted Mobility Solutions WG
> Co-Chair - TCG Metadata Access Protocol SG
> Chair - Linux Foundation Open Printing WG
> Secretary - IEEE-ISTO Printer Working Group
> Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
> IETF Designated Expert - IPP & Printer MIB
> Blue Roof Music / High North Inc
>http://sites.google.com/site/blueroofmusic <https://protect-us.mimecast.com/s/Dp6ZCM8gpgI8x06NUwZ_0u?domain=sites.google.com>
>http://sites.google.com/site/highnorthinc <https://protect-us.mimecast.com/s/VYZaCNkjqjfxVrM4t4tksB?domain=sites.google.com>
> mailto: blueroofmusic at gmail.com <mailto:blueroofmusic at gmail.com>
> PO Box 221 Grand Marais, MI 49839 906-494-2434
>>>> On Thu, Mar 7, 2019 at 12:37 PM Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy at hp.com <mailto:smith.kennedy at hp.com>> wrote:
> +1 for all 3 of them.
>> To what spec do we want to add these? Job Extensions v1.1? Enterprise Printing Extensions? Or System Service?
>>> On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp <ipp at pwg.org <mailto:ipp at pwg.org>> wrote:
>>>> Hi Mike,
>>>> Yes, to all three of these proposed attributes.
>>>> Cheers,
>> - Ira
>>>> Ira McDonald (Musician / Software Architect)
>> Co-Chair - TCG Trusted Mobility Solutions WG
>> Co-Chair - TCG Metadata Access Protocol SG
>> Chair - Linux Foundation Open Printing WG
>> Secretary - IEEE-ISTO Printer Working Group
>> Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
>> IETF Designated Expert - IPP & Printer MIB
>> Blue Roof Music / High North Inc
>>http://sites.google.com/site/blueroofmusic <https://protect-us.mimecast.com/s/Dp6ZCM8gpgI8x06NUwZ_0u?domain=sites.google.com>
>>http://sites.google.com/site/highnorthinc <https://protect-us.mimecast.com/s/VYZaCNkjqjfxVrM4t4tksB?domain=sites.google.com>
>> mailto: blueroofmusic at gmail.com <mailto:blueroofmusic at gmail.com>
>> PO Box 221 Grand Marais, MI 49839 906-494-2434
>>>>>>>> On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp <ipp at pwg.org <mailto:ipp at pwg.org>> wrote:
>> Oh, and as I was writing this up I thought of maybe the following as well (since IPP/1.1 is vague about what the history contains):
>>>> job-history-attributes-configured (1setOf keyword)
>>>> This Printer Description attribute lists the Job attributes that will be retained in the history phase of each Job. IPP/1.1 [STD92] specifies that at least the "job-id", "job-printer-uri", "job-state", and "job-state-reasons" attributes MUST be retained in the history phase.
>>>> This attribute MUST be supported if the "job-history-attributes-supported" (section N.M.P) attribute is supported.
>>>>>> job-history-attributes-supported (1setOf keyword)
>>>> This Printer Description attribute lists the Job attributes that can be retained in the history phase of each Job.
>>>> This attribute MUST be supported if the "job-history-attributes-configured" (section N.M.P) attribute is supported.
>>>>>>> On Mar 7, 2019, at 12:06 PM, Michael Sweet <msweet at apple.com <mailto:msweet at apple.com>> wrote:
>>>>>> All,
>>>>>> For your consideration, the following two Printer Description attributes would allow a Client to discover (and potentially the administrator to configure since the values are settable) how long a Job will stay in the history phase.
>>>>>> (I also considered "job-history-xxx" and "job-history-time-xxx" for the names; "interval" seemed the most consistent with other existing attributes, particularly with notifications)
>>>>>> --------
>>>>>> job-history-interval-configured (integer(0:MAX))
>>>>>> This Printer Description attribute specifies the minimum number of seconds that a Job will remain in the history phase of its lifecycle [STD92]. Printers SHOULD have a default configured value of at least 60 seconds to allow Clients to discover the disposition of any Jobs that have reached a terminating state.
>>>>>> This attribute MUST be supported if the "job-history-interval-supported" (section N.M.P) attribute is supported.
>>>>>>>>> job-history-interval-supported (rangeOfInteger(0:MAX))
>>>>>> This Printer Description attribute specifies the range of values that are supported for the "job-history-interval-configured" Printer Description attribute.
>>>>>> This attribute MUST be supported if the "job-history-interval-configured" (section N.M.P) attribute is supported.
>>>>>>>>> _________________________________________________________
>>> Michael Sweet, Senior Printing System Engineer
>>>>>>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer
>>>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org <mailto:ipp at pwg.org>
>>https://www.pwg.org/mailman/listinfo/ipp <https://protect-us.mimecast.com/s/DAB2COYkrkiX592WHk3W0z?domain=pwg.org>
>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org <mailto:ipp at pwg.org>
>>https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=pwg.org <https://protect-us.mimecast.com/s/DAB2COYkrkiX592WHk3W0z?domain=pwg.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190307/39140bb3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190307/39140bb3/attachment.sig>