Re: IPP Firmware Update Extensions v1.0 Initial draft posted for review

On Sep 9, 2024, at 10:28 AM, Michael Sweet <[email protected]> wrote:

CAUTION: External Email

From: Michael Sweet <[email protected]<mailto:[email protected]>>
Subject: Re: [IPP] IPP Firmware Update Extensions v1.0 Initial draft posted for review
Date: September 9, 2024 at 10:28:01 AM MDT
To: "Kennedy, Smith (Wireless & IPP Standards)" <[email protected]<mailto:[email protected]>>
Cc: PWG IPP Workgroup <[email protected]<mailto:[email protected]>>


Smith,

On Sep 9, 2024, at 11:35 AM, Kennedy, Smith (Wireless & IPP Standards) <[email protected]<mailto:[email protected]>> wrote:

Hi Mike,

Thanks for the feedback!

Your comments on "printer-firmware-update-support-uri" and "printer-firmware-update-urgency" seems to be moving us in the direction of the printer being able to report multiple firmware updates. Am I reading this right?

If so, having a bunch of "1setOf" attributes where the "the ith element in this attribute has to align with the ith element of some other attribute" starts to become messy, and scheduling or triggering a firmware update also becomes problematic because the Client won't have the ability to say which one. For this reason, should we move to a "printer-firmware-update-col" (1setOf collection) and have each collection specify an ID as well as its own support URI, urgency, etc.?

Maybe? The current printer-firmware-xxx attributes are separate 1setOf attributes with the ith value stuff, and I was under the impression that the new printer-firmware-update-xxx attributes were extending those to report when a new version of a firmware component was available...

Using a collection is cleaner but might be overkill if we decide that reporting a single set of values for whatever updates are available makes more sense.  At least one of the vendors I work with does monolithic firmware updates of multiple components because of how the firmware images are managed (whole read-only system images with A/B partitions), so if I added support for the new attributes to that product it will always show "no updates" or "N updates" (and nothing in between).

HP Inc. printer firmware updates for all the printers I've worked with (pretty much all of our ink and laser products in home and office / enterprise over the last 25 years) have a single firmware update too. I don't know if other vendors have multiple separate firmware updates, but we don't.

Given that, does it make sense to have "1setOf" for any of these unless there are printer vendors whose devices might have multiple separate firmwares?

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp