We all have software to manage firmwares on our devices in our customer's fleets. Managing firmware for other vendor's devices is not that simple. I believe the software only vendors will certainly benefit from a uniform method to trigger firmware updates.
I think this is a good step.
Regards
Uli Wehner
ウリ・ヴェーナー
-----Original Message-----
From: ipp <ipp-bounces at pwg.org> On Behalf Of John Madden via ipp
Sent: Tuesday, July 23, 2024 9:09 PM
To: ipp at pwg.org
Cc: John Madden <jpmsparks at yahoo.com>
Subject: Re: [IPP] Registration proposal for additional IPP Printer firmware related attributes[EXTERNAL]
IMO an outstanding feature suggestion, would definitely make life easier for the print hardware community.
On 7/23/2024 9:14 AM, Kennedy, Smith (Wireless & IPP Standards) via ipp
wrote:
> Hi Mike,
>>> On Jul 23, 2024, at 5:43 AM, Michael Sweet <msweet at msweet.org> wrote:
>>>> CAUTION: External Email
>>>> Smith,
>>>> I have no hard objections - we should probably discuss this in the August F2F to hammer out the details with everyone involved. We might also want to put this in an IPP registration document (or the System Service update?) due to the remote query functionality.
> I was thinking that as well.
>>> WRT remote installation of firmware updates, the IPP System service exposes a way to install firmware resources but perhaps we can expose an operation that updates manufacturer resources?
> I was also thinking a discrete operation might be the way to go so that we could define the authentication challenge semantics etc. more specifically, and the security considerations would probably want to discuss related topics, for instance that a Printer supporting the operation MUST use a mechanism such as TLS to validate the source? It's an interesting space from the perspective of requirements. But it seems worthy of standardizing to further encourage user awareness of firmware status and availability of updates.
>>>>>> On Jul 23, 2024, at 1:23 AM, Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org> wrote:
>>>>>> Greetings,
>>>>>> HP would like to register several new IPP attributes that relate to printer firmware update:
>>>>>> printer-firmware-update-uri (uri)
>>> --------------------------------------------------------------------
>>> --- This Printer Description attribute provides a URI to a page
>>> hosted in the printer or on the manufacturer's website for facilitating updating the printer's firmware. Valid schemes are "https" and "http".
>>>>>>>>> printer-firmware-update-version 1setOf (octetString(MAX) | no-value)
>>> --------------------------------------------------------------------
>>> --- This Printer Description attribute reports the latest firmware
>>> version available for the Printer by the Printer's manufacturer, in a format matching the Printer's "printer-firmware-version" Printer Description attribute [PWG 5100.13]. As this value depends on information from outside the Printer, if a Client specifically requests this attribute in a Get-Printer-Attributes request, then the Printer MUST query its manufacturer's source for printer firmware update information and provide a response within a reasonable amount of time (5 seconds? 10 seconds? 30 seconds?). If this attribute is not specifically listed in a Get-Printer-Attributes request's "requested-attributes" operation attribute, then the Printer can choose to not return this attribute, or can return this attribute with 'no-value' or a cached value from the last time the printer checked.
>>>>>>>>> printer-firmware-update-string-version (1setOf text(MAX))
>>> --------------------------------------------------------------------
>>> --- This attribute provides a string version of the value provided
>>> by the "printer-firmware-update-version" Printer Description attribute.
>>>>>>>>> We have also considered whether to propose a new IPP operation or similar mechanism to cause the Printer to proceed with fetching and installing an available firmware update, if the Printer is capable of such action (which "printer-firmware-update-version" seems to imply). But we held off of suggestions for that at this time.
>>>>>> We would like to discuss this subject perhaps at the F2F or on a teleconference in the near future.
>>>>>> Cheers,
>>>>>> Smith
>>>>>> /**
>>> Smith Kennedy
>>> Wireless & IPP Standards - IPG-PSPS
>>> IEEE ISTO Printer Working Group | Wi-Fi Alliance | Bluetooth SIG | Connectivity Standards Alliance
>>> Vice Chair, IEEE ISTO Printer Working Group
>>> HP Inc.
>>> */
>>>>>>>>> _______________________________________________
>>> ipp mailing list
>>>ipp at pwg.org>>>https://urldefense.com/v3/__https://www.pwg.org/mailman/listinfo/ipp>>> __;!!Iq1d47XejX0!iU8QTdGew71bqXBiiiUIXLAMTgssZKZoR6-X-E-LvyMD1Zm1gpu
>>> bZyShvH049iNtDOdTdixvKn_1_yw$
>>>>> ________________________
>> Michael Sweet
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://urldefense.com/v3/__https://www.pwg.org/mailman/listinfo/ipp__
> ;!!Iq1d47XejX0!iU8QTdGew71bqXBiiiUIXLAMTgssZKZoR6-X-E-LvyMD1Zm1gpubZyS
> hvH049iNtDOdTdixvKn_1_yw$
_______________________________________________
ipp mailing list
ipp at pwg.orghttps://urldefense.com/v3/__https://www.pwg.org/mailman/listinfo/ipp__;!!Iq1d47XejX0!iU8QTdGew71bqXBiiiUIXLAMTgssZKZoR6-X-E-LvyMD1Zm1gpubZyShvH049iNtDOdTdixvKn_1_yw$