attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">All,<div class=""><br class=""></div><div class="">During our last call review of the IPP System Service v1.0, several questions came up concerning how firmware updates will be applied once the resource is created, uploaded (sent), and installed. The consensus was to add a subsection 17.x (Appendix A - Rationale for Design Choices) documenting how we see this working without defining/requiring a particular file format. The following is my proposed text for this subsection:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">17.4 Executable Resources</div><div class=""><br class=""></div><div class="">This specification defines two types of executable resources: firmware ('executable-firmware') and application software ('executable-software'). While no specific file format has been mandated, an executable resource file:</div><div class=""><br class=""></div><div class="">- Provides a manifest providing descriptive text, version number(s), subunit or other associations, and a cryptographic hash of the executable content,</div><div class="">- Provides a cryptographic signature of the metadata, and</div><div class="">- Contains the executable content.</div><div class=""><br class=""></div><div class="">When subunit firmware is installed (or queued for installation on the next restart of the System), it applies to all compatible subunits. For example, if a System contains multiple fold finishers and an Administrator installs new fold finisher firmware, all of the fold finishers are updated - there is no way to selectively upgrade a single subunit.</div><div class=""><br class=""></div><div class="">When application software is installed, it typically applies to the System and all of its Printers. However, this specification does not prohibit applications that need to be subsequently allocated to a Printer, for example a cloud-based PDF interpreter application could be installed and later allocated to a specific Printer.</div></blockquote><div class=""><br class=""></div><div class="">Please provide your feedback before the next IPP workgroup conference call on October 24, 2019 so that we can start a PWG Formal Vote to span the November face-to-face meeting.</div><div class=""><br class=""></div><div class="">________________________</div><div class=""><div class="">Michael Sweet<br class=""><br class=""><br class=""></div><br class=""></div></body></html>