attachment
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
Hi Bill,</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
Replies inline below in red.</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div id="ms-outlook-mobile-signature">
<div class="MsoNormal" style="margin: 0in; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: black;">
Smith</div>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
</div>
<div style="padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>wamwagner@comcast.net <wamwagner@comcast.net><br>
<b>Date: </b>Monday, May 25, 2026 at 2:50 PM<br>
<b>To: </b>PWG IPP WG Reflector <ipp@pwg.org><br>
<b>Cc: </b>Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com><br>
<b>Subject: </b>Re: IPP Firmware Update Extensions v1.0 - recommendations for "Security and Privacy" and "Implementation Considerations" sections<br>
<br>
</div>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="font-size: 11pt; color: red;">
<span style="line-height: 107%;"><b>CAUTION: External Email</b></span></div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Smith et al,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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:</div>
<ol start="1" data-editing-info="{"applyListStyleFromLevel":false,"orderedStyleType":1}" style="margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">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. ]</div>
</li></ol>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
<span style="color: rgb(200, 38, 19);">If the new firmware was installed successfully, then PWG 5100.13 defines the "printer-firmware-xxx" attributes that will hold the values for the currently installed firmware, which will have been recently updated. In our
IPP Firmware Update Extensions v1.0 draft there is a "printer-new-firmware-support-uri" which could point to release notes. Perhaps we should also define a "printer-firmware-support-uri" so that the currently installed firmware's release notes / support info
continues to be available?<br>
</span><span style="color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<ol start="2" data-editing-info="{"applyListStyleFromLevel":false,"orderedStyleType":1}" style="margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">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.</div>
</li></ol>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
Why is there only a limited number of times? Do you mean it might be silently retrying to download before giving up? </div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
I think the current proposal treats retries as an implementation detail which is not visible over IPP. I'm a bit reluctant to expose those details via IPP because it adds complexity. If the Printer wants to expose that as a setting, it can do that in its own
administrative interface, but I'd probably resist adding that to IPP Firmware Update Extensions v1.0.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
If the download process errors out, it will be indicated by a new "printer-state-reasons" keyword 'new-firmware-download-failure'. If download fails, then there is nothing to install, and so the current firmware will continue to be used, right?</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
Does this satisfy your concern #2?</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<ol start="3" data-editing-info="{"applyListStyleFromLevel":false,"orderedStyleType":1}" style="margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">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.</div>
</li></ol>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(200, 38, 19);">
<span style="font-size: 16px;">This seems to be similar to your download phase concerns, but with the failures occurring during the
</span>validation<span style="font-size: 16px;"> phase. </span></div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 16px; color: rgb(200, 38, 19);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 16px; color: rgb(200, 38, 19);">
If the download process errors out, it will be indicated by a new "printer-state-reasons" keyword 'new-firmware-validation-failure'. If validation fails, then the downloaded file(s) are or ought to be discarded, and so there is nothing to install, and the current
firmware will continue to be used, right?</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<ol start="4" data-editing-info="{"applyListStyleFromLevel":false,"orderedStyleType":1}" style="margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">It a problem occurs in the attempt to execute the new firmware:</div>
</li><ol start="1" data-editing-info="{"applyListStyleFromLevel":true}" style="margin-top: 0px; margin-bottom: 0px; list-style-type: lower-alpha;">
<li style="margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There must be a clear indication to the user both of the failure and the current state of the device.</div>
<div class="elementToProof" role="presentation" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" role="presentation" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(200, 38, 19);">
<span style="font-size: 16px;">There is a new "activation" phase and it has a similar "printer-state-reasons" keyword 'new-firmware-activation-failure' to indicate that. The expected behavior is that if installation or activation phases fail, the Printer will
recover by re-activating </span>the previously installed firmware.</div>
<div class="elementToProof" role="presentation" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">If possible, the device should be returned to full operation with the previous firmware.</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px;">
<div class="elementToProof" role="presentation">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.</div>
</li></ol>
</ol>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(200, 38, 19);">
I want to be careful about being overly prescriptive with IPP Firmware Update Extensions v1.0. If granular control and exposure of the process is needed, I'd suggest that the printer not implement this and/or that it implement System Service or a proprietary
method for managing firmware updates, and the vendor encourage their users to handle firmware updates that way. The original design goal was to expose printer self-update capabilities via an IPP interface so that some level of status is available to users,
and to allow stages of those processes to be triggered out of cycle.</div>
<div style="direction: ltr; margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div class="elementToProof" style="margin-top: 0px; margin-bottom: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Bill Wagner</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg">
<div style="direction: ltr; font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<b>From:</b> ipp <ipp-bounces@pwg.org> on behalf of Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp@pwg.org><br>
<b>Sent:</b> Thursday, May 21, 2026 4:32 PM<br>
<b>To:</b> PWG IPP WG Reflector <ipp@pwg.org><br>
<b>Cc:</b> Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com><br>
<b>Subject:</b> [IPP] IPP Firmware Update Extensions v1.0 - recommendations for "Security and Privacy" and "Implementation Considerations" sections</div>
<div style="direction: ltr;"> </div>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">Hi there,</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">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.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">Cheers, </div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
</div>
</body>
</html>