attachment
<div dir="ltr"><div dir="ltr"><div>Hi</div><div><br></div><div>Over all a very good initiative, but i have some concerns - sorry if they have already been addressed (i couldn't find it).</div><div><br></div><div>With this mirroring the installed firmware in being able to communicate that there are multiple firmware types and versions, </div><div>i think it could be worth being super-duper clear on that the contents of these lists describe a set of firmware files that would get applied together when triggering an update.</div><div>(...and is not to be used to contain multiple versions of the same thing).</div><div>A naive implementer might be tempted to list all versions offered, only to find out the update operation has no way of saying to what version.</div><div></div><div><br></div><div>I also think it is a mistake to only support, possible even to require, some online repository for firmware.</div><div>I think it would be very good to be able to supply the firmware file(s) directly from the client.</div><div>Files tend to stick around much longer than the services that served them most of the time.</div><div>Currently a lot of firmware updates are simply performed by "printing" a file with some magic (often PJL) in it.</div><div>Also think of use in air-gapped environments, not just post-support-window devices.</div><div>With no standard on what a repository is, there is no guarantee i could deploy my own.</div><div><br></div><div>Br,</div><div>Anton</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Den tis 27 jan. 2026 kl 19:59 skrev Kennedy, Smith (Wireless & IPP Standards) via ipp <<a href="mailto:ipp@pwg.org">ipp@pwg.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Greetings,
<div><br>
</div>
<div>I've posted a new draft of IPP Firmware Update Extensions v1.0:</div>
<div><br>
</div>
<blockquote style="margin:0px 0px 0px 40px;border:medium;padding:0px">
<div>
<div><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.pdf" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.pdf</a> </div>
</div>
<div>
<div><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.docx" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.docx</a> </div>
</div>
<div>
<div><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.pdf" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.pdf</a> </div>
</div>
<div>
<div><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.docx" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.docx</a></div>
</div>
</blockquote>
<div>
<div><br>
</div>
<div>Changes:</div>
<div><br>
</div>
<div>
<div>
<ul>
<li>Updates to section 4 to consolidate discussion of the linkage between the new operations, the new attributes, and the new values for existing attributes</li><li>Updated the abstract</li><li>Fixed the document file name</li><li>Added section 4.5 “Enabling or Disabling the Printer Firmware Update Feature” and defined the “printer-firmware-update-enabled” attribute to allow a Client to have an easy way to detect support for the feature, and to provide the Printer and its Administrator
with a way to disable the feature.</li></ul>
<div><br>
</div>
</div>
</div>
<div>I know we won't be looking at this Thursday but its there for review before the F2F and we could peek at it if we want to.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/ </div>
<br>
</div>
</div>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div></div>