Re: [IPP] IPP Firmware Update Extensions v1.0 Initial draft posted for review
Michael Sweet via ipp <ipp@pwg.org> Mon, 09 September 2024 16:28 UTC
Received: by ietfa.amsl.com (Postfix) id E73F9C15108F; Mon, 9 Sep 2024 09:28:23 -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 E68ECC14CE5E for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 9 Sep 2024 09:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.106
X-Spam-Level:
X-Spam-Status: No, score=-3.106 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_BLOCKED=0.001, 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="IOUQSlK6"; dkim=pass (1024-bit key) header.d=pwg.org header.b="GAnWNWKh"; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=msweet.org header.b="c8AzpGyZ"
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 k66PvepCYPwP for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 9 Sep 2024 09:28:19 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 9A50EC14E513 for <ipp-archive2@ietf.org>; Mon, 9 Sep 2024 09:28:19 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id D797DE902; Mon, 9 Sep 2024 16:28:18 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org D797DE902
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1725899298; bh=AwYbfBWBOC7vdmF1ie+PELHmhUb33+cEtbR2aK54cs4=; 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=IOUQSlK6v+CGHuEtH1Mbz56/Z0EgJFBNhyErxnefulyUVLI0PtmeaJXUFw0Ozbcnq wkr3Ek+ZCPrWpxNyiwRh0zaW0mPNj2ycLRK5Rr0kwH3VZ83xaV6XjBkD13tlxN0KZC V4XaQhbcS3Vpwkdf/uhdRHZJlwDkD5Wprm28sAcs=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 6F08835C1; Mon, 9 Sep 2024 16:28:16 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 6F08835C1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1725899296; bh=AwYbfBWBOC7vdmF1ie+PELHmhUb33+cEtbR2aK54cs4=; 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=GAnWNWKhVTX074y/oDggqIc5s2EcM2B4ooGjwvcnASxIIjWgNqFL67v3c0nUxhuwf BHpBOXFfXxzLrRL1QU+cza4VbEmy5zznXBdhND+IgEpiJQW9PmVDdOVQQ/hRSew9yR bnSaJxj1aDRK1nIdQ5cVYahj7QBNF3sw7s7W2DqU=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 54FAF6097; Mon, 9 Sep 2024 16:28:15 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 54FAF6097
Authentication-Results: mail.pwg.org; dkim=pass (1024-bit key) header.d=msweet.org header.i=@msweet.org header.b="c8AzpGyZ"
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTPS id 517E0A8D for <ipp@pwg.org>; Mon, 9 Sep 2024 16:28:14 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 517E0A8D
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) (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 E49C380F09; Mon, 9 Sep 2024 16:28:12 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org E49C380F09
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1725899293; bh=qxW2zmtid64GWGhczFDI8B/C3s3S/NkufKzUxejthVQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=c8AzpGyZ9LpHVj/RhdAutkRlpqmDDSXbEZI6dqeRG18h89vgRkViweembxm0HBDLL ZK9jJCLZwa/A+nd4ArPMMF0j/0ecglI8kIkLqtud3CLbzWuSERzJhRwjJMF/fJevWQ LgTadi4RGvFTf4tMPCkQDCcEkpTKqu+d+11tE+mg=
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
In-Reply-To: <FFD7870E-D50D-4117-ACA0-1D52DD874AC9@hp.com>
Date: Mon, 09 Sep 2024 12:28:01 -0400
Message-Id: <1F2B322B-318B-4890-8265-FF61DA9F67A6@msweet.org>
References: <BA9CD2A2-EC7E-497F-9568-601B2903D0C4@hp.com> <787A196D-7690-47C7-BD1D-CD0805428CA0@msweet.org> <FFD7870E-D50D-4117-ACA0-1D52DD874AC9@hp.com>
To: "Kennedy, Smith (Wireless & IPP Standards)" <smith.kennedy@hp.com>
X-Mailer: Apple Mail (2.3776.700.51)
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>, PWG IPP Workgroup <ipp@pwg.org>
Content-Type: multipart/mixed; boundary="===============4515915022425868533=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Smith, > On Sep 9, 2024, at 11:35 AM, Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com> 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). ________________________ Michael Sweet
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] IPP Firmware Update Extensions v1.0 Initial… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] IPP Firmware Update Extensions v1.0 Ini… Michael Sweet via ipp
- Re: [IPP] IPP Firmware Update Extensions v1.0 Ini… Michael Sweet via ipp
- Re: [IPP] IPP Firmware Update Extensions v1.0 Ini… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] IPP Firmware Update Extensions v1.0 Ini… Michael Sweet via ipp
- Re: [IPP] IPP Firmware Update Extensions v1.0 Ini… Kennedy, Smith (Wireless & IPP Standards) via ipp