Updated draft (Stable candidate?) of IPP Firmware Update Extensions v1.0 posted
Smith via ipp <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Greetings, In advance of next week's F2F, I've posted another update to IPP Firmware Update Extensions v1.0: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260814.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260814.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260814-rev.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260814-rev.docx Changes in this revision: Updated following prototyping the specification in C (libcups fork) and Dart / Flutter (cleanroom): Resolved issues identified in the 2026-07-30 IPP WG teleconference review of the start of the previous draft; Added the ‘firmware-update-failure’, ‘firmware-update-in-progress’ and ‘firmware-update-success’ keywords for “printer-state-reasons” to allow the Client to clearly know that a firmware update was in progress or failed or succeeded, rather than having to look for other more detailed state reasons; and Updated the definition of the ‘firmware-repository-access-error’ and ‘firmware-repository-unreachable’ keywords to more clearly define which keywords the Printer must remove when each of these keywords is added to “printer-state-reasons”. Cheers, Smith /** Smith Kennedy [email protected] */ _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp