Smith.
If we are only focused on the activation phase, then it should be called "printer-new-firmware-activation-time".
> On Aug 27, 2026, at 10:29 AM, Smith <smitty.standards at gmail.com> wrote:
>> Hi Mike,
>> If you recall from our discussion at the face-to-face, we identified a need for an attribute it would indicate the amount of time that the Printer would be unreachable and unable to respond to IPP requests while it is restarting in the process of installing and activating new firmware. This was to try to improve the user experience over the current “state-of-the-art“ which seems to be to not provide such a not provide such an estimate, which causes clients to show an indeterminate progress indicator (“never-ending pinwheel“).
>> I suppose we could have an attribute that provides a number for the entire process and then the client would have to subtract whatever time has already evolved to show an estimate to the user, but this doesn’t seem like the best way to do this because download speeds and other things get factored in and those are quite variable on their own. And this is why I suggested having an attribute that just provided a focused estimate for the reboot time.
>> Smith
> Sent from my iPhone 4
>>> On Aug 27, 2026, at 8:21 AM, Michael Sweet via ipp <ipp at pwg.org> wrote:
>>>> Smith/Ira,
>>>> For jobs we have the “job-processing-time” attribute that reports the total processing time for a job. I’m not keen on “xxx-duration”, “xxx-delay”, or “xxx-interval” for this attribute since it isn’t a delay or periodic interval and we have no other attributes with duration in the name.
>>>> How about “printer-new-firmware-update-time (integer(0:MAX))”? The definition can be explicit about the value being the estimated time in seconds it will take to do a full update (including time to download/acquire the new firmware?)
>>>> ____________________
>> Michael Sweet
>>>>> On Aug 27, 2026, at 8:03 AM, Ira McDonald via ipp <ipp at pwg.org> wrote:
>>>>>> Hi,
>>>>>> Interesting idea. I dislike the ambiguity with actual reported time of "duration" and
>>> would prefer "delay".
>>>>>> Cheers,
>>> - Ira
>>>>>> Ira McDonald (Musician / Software Architect)Co-Chair - TCG Mobile Platform WGChair - Linux Foundation Open Printing WG
>>> Secretary - ISTO Printer Working Group
>>> Co-Chair - ISTO PWG Internet Printing Protocol WG
>>> IETF Designated Expert - IPP & Printer MIB
>>> Blue Roof Music / High North Inc
>>>http://sites.google.com/site/blueroofmusic>>>http://sites.google.com/site/highnorthinc>>> mailto: blueroofmusic at gmail.com>>> (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434
>>>>>>>>> On Wed, Aug 26, 2026 at 5:29 PM Smith Kennedy via ipp <ipp at pwg.org> wrote:
>>> Hi there,
>>>>>> Following up from last week's F2F, we discussed adding a new attribute to provide a hint to the client indicating an estimate for how long a printer reboot would take. Any objections with the following definition?
>>>>>> printer-new-firmware-restart-duration (integer(0:120))
>>>>>> where the value is defined to provide the duration in minutes (minimum 1 minute, maximum 2 hours).
>>>>>> Thoughts?
>>>>>> Smith
>>>>>> /**
>>> Smith Kennedy
>>>smitty.standards at gmail.com>>> */
>>>>>>>>>>>> _______________________________________________
>>> 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>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org>>https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet