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

Michael Sweet via ipp <ipp@pwg.org> Fri, 30 August 2024 16:41 UTC

Received: by ietfa.amsl.com (Postfix) id 71A01C1CAE66; Fri, 30 Aug 2024 09:41:49 -0700 (PDT)
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70F2FC14CE2C for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 30 Aug 2024 09:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.107
X-Spam-Level:
X-Spam-Status: No, score=-3.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MAILING_LIST_MULTI=-1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pwg.org header.b="aQBJmOCc"; dkim=pass (1024-bit key) header.d=pwg.org header.b="pM/gTri+"; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=msweet.org header.b="JJ3CRb3B"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeJGNi5tYCO1 for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 30 Aug 2024 09:41:45 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 08E3CC18DBB3 for <ipp-archive2@ietf.org>; Fri, 30 Aug 2024 09:41:44 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 1FA85E904; Fri, 30 Aug 2024 16:41:44 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 1FA85E904
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1725036104; bh=oD+cCabr9rYyZCNrZap/bcXvo2DEU7vGvgsvg/BDvbs=; h=In-Reply-To:Date:References:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=aQBJmOCcsPhDZ4PdlYrTyDJes7IZJOD7xag5PYmL7e5CNX0drhO3/6Ndea/jxdwyn TDGwyKqFWi9Rf3FKzv3u4yYnwNHjINTWd9zc1phXbBfELSSo+6qOG1lE4RoR5irqLU 824MbywTuBkxuhFbn8tT3JJcqjs+XbYjgiRbGFro=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 3F8BF3A43; Fri, 30 Aug 2024 16:41:42 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 3F8BF3A43
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1725036102; bh=oD+cCabr9rYyZCNrZap/bcXvo2DEU7vGvgsvg/BDvbs=; h=In-Reply-To:Date:References:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=pM/gTri+QVB09jFAEjCI6lj0CyCSt+UmRGbTyKjFXH/9a+r9FUM1ucizg3/YS3ohS YhNi+cKuNkTM6kwEsxtNNxriNhl22LucmiTaa6/GLByYxOWGSKMVWX06qENHl582dA jYhSBG+BdXhGM4jgp7OmZFEpqpeosMhzNBpYWx1E=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id E0DA463E6; Fri, 30 Aug 2024 16:41:40 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org E0DA463E6
Authentication-Results: mail.pwg.org; dkim=pass (1024-bit key) header.d=msweet.org header.i=@msweet.org header.b="JJ3CRb3B"
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTPS id E046C2D7 for <ipp@pwg.org>; Fri, 30 Aug 2024 16:41:39 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org E046C2D7
Received: from smtpclient.apple (unknown [129.222.139.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.msweet.org (Postfix) with ESMTPSA id 10B3D803DD; Fri, 30 Aug 2024 16:41:37 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 10B3D803DD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1725036098; bh=bnxxtCWsoSjXyJDT8jGgWidUOrZ7zfeK8xpWHCBiPas=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=JJ3CRb3BYjRa6H4HAvwe85yLtqj8hqZ8C2ksLbNa0oeBfDUa0UgyuNDdOWVkBWy3p cNqdY6Ud7c74KZw1ZnP7W0qwmeHUyCNJQ5kglJm2AezUp/pLMUB6Qm4/TK+bcRWJNr 1Y3fB+gn6VURwM8owKxRK+mA9eXX6HpoqTvrGOZ8=
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
In-Reply-To: <BA9CD2A2-EC7E-497F-9568-601B2903D0C4@hp.com>
Date: Fri, 30 Aug 2024 12:41:26 -0400
Message-Id: <787A196D-7690-47C7-BD1D-CD0805428CA0@msweet.org>
References: <BA9CD2A2-EC7E-497F-9568-601B2903D0C4@hp.com>
To: PWG IPP Workgroup <ipp@pwg.org>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Subject: Re: [IPP] IPP Firmware Update Extensions v1.0 Initial draft posted for review
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Michael Sweet via ipp <ipp@pwg.org>
Reply-To: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Cc: Michael Sweet <msweet@msweet.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

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 <ipp@pwg.org> 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
> ipp@pwg.org
> https://www.pwg.org/mailman/listinfo/ipp

________________________
Michael Sweet

_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp