Smith et al,
There are some things that perhaps cannot be specified, but might be appropriate under implementation considerations. These reflect my apprehension with regard to machines doing their own thing, and might not be considered necessary by others, but suggest the following:
1.
If the new firmware update is successful, there should be some clear indication that a device has firmware and some way a user can get some information about the new firmware. [I have had successful computer updates that have, perhaps inadvertently, affected functionality. ]
2.
If a new firmware update fails because of transmission problems or errors, the device can clear itself and retry, but for only a limited number of times, after which there should be an indication to the user that new firmware update attempt failed because of download problems. The user may have the option of allowing an automatic reattempt or initiating a reattempt (perhaps after resolving communication issues.) In either case the device should resume normal operation with the previous un-updated firmware.
3.
If a new firmware update fails because of security issues, or questions about the validity of the update package, the device should resume normal operation with the previous un-updated firmware and there should be clear indication of the failure to the user. It may be desirable to give the user the ability to postpone update attempts until the issue is resolved and new firmware update re-enabled.
4.
It a problem occurs in the attempt to execute the new firmware:
*
There must be a clear indication to the user both of the failure and the current state of the device.
*
If possible, the device should be returned to full operation with the previous firmware.
*
If (b) is not possible, the device should be left in a mode which would allow analyses and perhaps operational recovery by remote maintenance efforts.
Thanks,
Bill Wagner
________________________________
From: ipp <ipp-bounces at pwg.org> on behalf of Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org>
Sent: Thursday, May 21, 2026 4:32 PM
To: PWG IPP WG Reflector <ipp at pwg.org>
Cc: Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy at hp.com>
Subject: [IPP] IPP Firmware Update Extensions v1.0 - recommendations for "Security and Privacy" and "Implementation Considerations" sections
Hi there,
For IPP Firmware Update Extensions v1.0, does anybody have any recommendations for items to list in the "Security and Privacy" and "Implementation Considerations" sections? I'd like to get that before I produce my next draft, which will be ready for our IPP WG meeting June 18.
Cheers,
Smith
/**
Smith Kennedy
HP Inc.
*/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20260525/5574bd09/attachment.html>