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

Michael Sweet via ipp <[email protected]>
Newsgroups gmane.ietf.ipp
Message-ID <[email protected]>
Smith,

Some quick feedback on the parts of the registration we didn't get to yesterday:

- 5.1.1 printer-firmware-update-support-uri (uri)

This should probably be a 1setOf to provide a URI for each update.

- 5.1.2 printer-firmware-update-urgency (type2 keyword)

If we wanted to normalize this, we could base this on the CVSS v4.0 User Guide base score which is the update severity number from 0 (lowest) to 10 (highest).  Or we could include the whole CVSS string, for example:

    8.8 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N)

Also, we probably want to make this a 1setOf , e.g., "printer-firmware-update-cvss (1setOf octetString(MAX))", to capture the CVSS string for each update.

- Maybe add a new 5.1.x attribute "printer-firmware-update-time (dateTime | no-value)" that specifies when the printer will apply/install the firmware updates. The 'no-value' out-of-band value would indicate that updates will not be installed automatically.

- 6.1 Firmware-Self-Update

I suggest we call this operation "Update-Printer-Firmware" since we usually use verbs in operation names.

- 6.1.1 ... Request

I suggest we add "delay-update-until (type2 keyword)" and "delay-update-time-time (dateTime)" operation attributes to specify when to do the firmware update. Keywords could mirror the "job-hold-until" attribute: 'indefinite' to pause updates, 'now' to install immediately, 'night' to install during the night, and 'weekend' to install over the weekend.

- 7.1 printer-state-reasons

I recommend slightly different naming: 'firmware-update-available', 'firmware-update-failed', and 'firmware-updated-successfully' for consistency with other job/printer-state-reasons. Also, maybe add 'firmware-update-queued' for an update that is scheduled for installation?

Thanks for doing the work on this!


> On Aug 26, 2024, at 6:50 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected]> wrote:
> 
> Greetings, 
> 
> Following our last F2F meeting, where I had the action item to transform the firmware update registration request into an IPP Registration document, I have posted the Initial draft of IPP Firmware Update Extensions v1.0, which is here:
> 
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate-20240826.pdf  https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate-20240826.docx  
> Looking forward to feedback!
> 
> Cheers,
> 
> Smith
> 
> /**
>     Smith Kennedy
>     HP Inc.
> */ 
> 
> _______________________________________________
> ipp mailing list
> [email protected]
> https://www.pwg.org/mailman/listinfo/ipp

________________________
Michael Sweet

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.