attachment

<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Mike and all,<div><br></div><div>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:</div><div><br></div><div><a href="https://github.com/istopwg/ippsample/wiki/Firmware-Updates#second-revision">https://github.com/istopwg/ippsample/wiki/Firmware-Updates#second-revision</a></div><div><br></div><div>The one thing that bothers me a little is the keyword structures. What has currently been proposed:</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><br></div><div><div>'firmware-update-acquiring'</div></div><div><div>'firmware-update-acquisition-failed'</div></div><div><div>'firmware-update-validating'</div></div><div><div>'firmware-update-validation-failed'</div></div><div><div>'firmware-update-installing'</div></div><div><div>'firmware-update-installation-failed'</div></div><div><div>'firmware-update-activating'</div></div><div><div>'firmware-update-activation-failed'</div></div></blockquote><div><div><br></div></div><div>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?</div><div><br></div><div><blockquote style="margin: 0px 0px 0px 40px; border: medium; padding: 0px;"><div>'firmware-update-acquisition-failed'</div><div>'firmware-update-acquisition-in-progress'</div><div>'firmware-update-validation-failed'</div><div>'firmware-update-validation-in-progress'</div><div>'firmware-update-installation-failed'</div><div>'firmware-update-installation-in-progress'</div><div>'firmware-update-activation-failed'</div><div>'firmware-update-activation-in-progress'</div><div><br></div></blockquote></div><div>WDYT?</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Smith<br><br><br></div>
</div>

<div><br><blockquote type="cite"><div>On Oct 8, 2026, at 2:29 PM, Michael Sweet via ipp <ipp@pwg.org> wrote:</div><br class="Apple-interchange-newline"><div><div>All,<br><br>I have posted the minutes from today's IPP workgroup conference call to:<br><br>    https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20261008.pdf<br><br>Our next conference call is on October 24, 2026 at 3pm ET.<br><br>________________________<br>Michael Sweet<br><br>_______________________________________________<br>ipp mailing list<br>ipp@pwg.org<br>https://www.pwg.org/mailman/listinfo/ipp<br></div></div></blockquote></div><br></div></body></html>