Hi Mike and all,
I'm starting to dig into creating the next draft of IPP Firmware Update Extensions v1.0 so that I can have a draft completed for review at the F2F and also hopefully have my prototype updated as well. I was reviewing what we have in the wiki:
https://github.com/istopwg/ippsample/wiki/Firmware-Updates#second-revision
The one thing that bothers me a little is the keyword structures. What has currently been proposed:
'firmware-update-acquiring'
'firmware-update-acquisition-failed'
'firmware-update-validating'
'firmware-update-validation-failed'
'firmware-update-installing'
'firmware-update-installation-failed'
'firmware-update-activating'
'firmware-update-activation-failed'
We changed from 'firmware-update-<PHASE>-in-progress' to 'firmware-update-<PHASE>ing'. This model seems a bit awkward because the "<PHASE>" substring of "<PHASE>ing" differs from the "<PHASE>" substring in "<PHASE>-failed". At the end of the day I don't actually care that much which one we choose but I want to try to avoid another round of string modifications. So should we have the above? Or should we have this?
'firmware-update-acquisition-failed'
'firmware-update-acquisition-in-progress'
'firmware-update-validation-failed'
'firmware-update-validation-in-progress'
'firmware-update-installation-failed'
'firmware-update-installation-in-progress'
'firmware-update-activation-failed'
'firmware-update-activation-in-progress'
WDYT?
Smith
> On Oct 8, 2026, at 2:29 PM, Michael Sweet via ipp <ipp at pwg.org> wrote:
>> All,
>> I have posted the minutes from today's IPP workgroup conference call to:
>>https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20261008.pdf>> Our next conference call is on October 24, 2026 at 3pm ET.
>> ________________________
> Michael Sweet
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20261020/d0a43bb3/attachment.html>