Re: [IPP] Registration proposal for additional IPP Printer firmware related attributes[EXTERNAL]
Ira McDonald via ipp <ipp@pwg.org> Fri, 26 July 2024 13:38 UTC
Received: by ietfa.amsl.com (Postfix) id 19A06C16942C; Fri, 26 Jul 2024 06:38:30 -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 18B5FC137363 for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 26 Jul 2024 06:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level:
X-Spam-Status: No, score=-3.105 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, HTML_MESSAGE=0.001, 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="R46YkwTy"; dkim=pass (1024-bit key) header.d=pwg.org header.b="UwjLK4rP"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com header.b="M5Hv7Yey"
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 ifaeLDSleuxV for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 26 Jul 2024 06:38:26 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7DFC169406 for <ipp-archive2@ietf.org>; Fri, 26 Jul 2024 06:38:25 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 6C03AE901; Fri, 26 Jul 2024 13:38:25 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 6C03AE901
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1722001105; bh=59iYsq6bHPytXJ/8cEocKuAbqCthbWXgLdtumDbvgek=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=R46YkwTyFmReI66rayuyLIXlSmngxSk2fElSctcUehOc+/P7zPenksLcIowLm5Sqk T1SjabFhXe/XvnsY63PVQdAJCcV/e9U9kzDJxsyqu8NnhNc2HLNBQAtJ1qzzWCw50E 7d4STas3BjUcPmh+9lieDgCc9/45wPVWv0KI+8Cc=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 80E9D26F2; Fri, 26 Jul 2024 13:38:23 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 80E9D26F2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1722001103; bh=59iYsq6bHPytXJ/8cEocKuAbqCthbWXgLdtumDbvgek=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=UwjLK4rPAsNUvg2epKDmnnB2qadmNUHRmiDv60T1lDx9jQsI+M9cPnXie5qXxnNPQ 1xDm7+2vQPQg9yGokMTPtCuYdojd0I/yhzll1JtOygAhhXIy6M1m8LqSSSfqap094G Jn+7zwDWc76WB2XTR+MdL1PsFxZj63hgTU37+bME=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id D2D83C686; Fri, 26 Jul 2024 13:38:21 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org D2D83C686
Authentication-Results: mail.pwg.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="M5Hv7Yey"
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) by mail.pwg.org (Postfix) with ESMTPS id 4C2643A3D for <ipp@pwg.org>; Fri, 26 Jul 2024 13:38:20 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 4C2643A3D
Received: by mail-vk1-xa2e.google.com with SMTP id 71dfb90a1353d-4f4cdb520f3so376853e0c.0 for <ipp@pwg.org>; Fri, 26 Jul 2024 06:38:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722001099; x=1722605899; darn=pwg.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=reKldyrS6CDfpmlvg7ztV5N9/I7dNiseKFGFuTYmYMA=; b=M5Hv7Yey/VXAjxz8zyRDW4gsWLhgYH5uBGNZlexXkR1yQRHkZJckc/N8umxwga5OAn bjcYMSCu0Fntdscw2i9JARi6kYku5qIY8eg/vBlCSbHTLa/kaU7UEVpPcgtrqQB/iBZz Y5VwzNGAIJY+6PK7e0zwuuF/68RvjI4ClkiH28BdkQbzEf5hBYOxy0NKGjAoftKq0xOU X4Qo3JBm+5a41B8KprMRorfgc/2RTjJiWjyMfEZI7RWbH6xSRPtAGWLwn+sVAs8RnGtS 7rCVjWHhcmqW6M9hIYVmgLp3at6sy5RhF9p1ASIBy38UvkOAEg/vQhjPGfkFd/mVOIzu jpCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722001099; x=1722605899; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=reKldyrS6CDfpmlvg7ztV5N9/I7dNiseKFGFuTYmYMA=; b=Ku7FerTUVp9lj9wufPtaKFyEiSBBezqgcR2KWcsTc9JgUmnREI+2Fp5RWBKhon4tuv 50b9N6RwDf+HcwHmg3T+k8NDZsoQwza+7iCsxypHvw526cytniIrZ1XsY+NSzzzGNThM V1ZkZVjxBg39ftp/f+9BvznVwmZC7qjX2aFYlKSBXpwCMC4f7TW3TfAbb+df13PIEVcn zUNxZBjpmk0+IQMJ5CKocN3uNNE/uDtzJRPKWwSe1DFZT7I5E++WwZH1e9z14hONPCNF D/j3BzyH3ptQwANUagg3ZIP4ycC7nQAybWGrqZBH2EBSp+oLka9QBlEc3vvahzinV0GE JfEA==
X-Gm-Message-State: AOJu0YwGjs1ILXuCbLiLWNtGCU8cQFbNHL+qmxu62qvBO7DKWQyorlE8 zMG4rYLdw7ATGmqO0+SdrUV3jvhD08C2SU1IlR2Q6PTAwSiKIew8RpwjAV/0frS0d+OAkD3y6wI FtDT7yJ5telMf+oAcq8c1ZYAW/kM=
X-Google-Smtp-Source: AGHT+IF9N7RM/3n2QCqzlSg7PvmExUj6dRSEkRtQ9Spig5HRS8BBe7z+anZYSln4GQLqLGCOFLCa9fKdtEeGOGFK91U=
X-Received: by 2002:a05:6122:896:b0:4ef:58c8:4777 with SMTP id 71dfb90a1353d-4f6c6340aa9mr5748710e0c.4.1722001099175; Fri, 26 Jul 2024 06:38:19 -0700 (PDT)
MIME-Version: 1.0
References: <41E9C441-1A4F-49C3-9154-493BFE1FD1D8@hp.com> <CAN40gSuhykrHMu_U-P-FPgwSd5dGNeGJ4C3T8iZpP6EP5cQMdw@mail.gmail.com> <7E17A1D6-1843-4E3A-9794-B2EEA9E69C86@hp.com> <IA1PR17MB61217DADFFED1191AC3A015DA4B42@IA1PR17MB6121.namprd17.prod.outlook.com>
In-Reply-To: <IA1PR17MB61217DADFFED1191AC3A015DA4B42@IA1PR17MB6121.namprd17.prod.outlook.com>
Date: Fri, 26 Jul 2024 09:38:07 -0400
Message-ID: <CAN40gSs5xke=_jCpAcQ-J7RchBLL+nOPBdiT+NyBBEEEeGppEw@mail.gmail.com>
To: Uli Wehner <ulrich.wehner@ricoh-usa.com>, Ira McDonald <blueroofmusic@gmail.com>
Subject: Re: [IPP] Registration proposal for additional IPP Printer firmware related attributes[EXTERNAL]
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: Ira McDonald via ipp <ipp@pwg.org>
Reply-To: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Cc: Ira McDonald <blueroofmusic@gmail.com>, ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Content-Type: multipart/mixed; boundary="===============3745799569735509949=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Hi Uli, With IPP System Service in the Cloud, a Printer can be notified that firmware updates are available and safely fetch the updates. Direct fetch from the manufacturer has all the security weaknesses that caused us to deprecate Print-URI. Cheers, - Ira On Fri, Jul 26, 2024, 9:03 AM Uli Wehner <ulrich.wehner@ricoh-usa.com> wrote: > Smith, > > > > With software moving to the cloud, we will not be able to push firmwares > to printers directly anymore. > > > > I know we will need to be able to have the printer reach up to the service > using an agent on the device. We do this today, just not with IPP as the > vehicle. > > > > > > Regards > > > > *Uli Wehner* > > ウリ・ヴェーナー > > *From:* ipp <ipp-bounces@pwg.org> *On Behalf Of *Kennedy, Smith (Wireless > & IPP Standards) via ipp > *Sent:* Thursday, July 25, 2024 6:12 PM > *To:* Ira McDonald <blueroofmusic@gmail.com> > *Cc:* Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com>; > PWG IPP WG Reflector <ipp@pwg.org> > *Subject:* Re: [IPP] Registration proposal for additional IPP Printer > firmware related attributes[EXTERNAL] > > > > Hi Ira, > > > > Sorry for not replying sooner. > > > > On Jul 24, 2024, at 7:29 AM, Ira McDonald <blueroofmusic@gmail.com> wrote: > > > > *CAUTION: External Email * > > Hi Smith, > > > > All of this functionality has been defined in IPP System Service all along. > > > > Firmware or application resources can be created and then installed for > one > > Printer or the whole System. Then either the single Printer or whole > System > > can be restarted to activate the new firmware or application software. > > > > See sections 5.7, 6.1.1, 6.1.6, 6.2.4, 6.3.2, 6.3.13, and 6.3.17. > > > > Unless I'm mistaken, these sections in System Service are useful if the > client is managing the firmware update process directly by fetching the > firmware update and pushing that update to the printer as a resource. > > > > But if the Printer is capable of sending a firmware update query on its > own to check availability and/or fetch and update itself, we don't seem to > have any IPP attributes that can drive that. The > "printer-firmware-update-version" and > "printer-firmware-update-string-version" are intended to fill that gap. > Mike suggested that we might define a new operation to cause the printer to > fetch and update itself, and I think that is something we ought to > investigate or at least discuss. This would compliment the existing > facilities in System Service, and from a user experience and implementation > perspective it would be easier for a Client to support this type of > firmware update flow than the existing System Service supported process > where it would need to download the firmware image / file to itself and > then submit it to the printer. I think the existing System Service flow is > likely more desirable for larger / enterprise deployments where a fleet > might be upgraded using a common firmware image. > > > > The "printer-firmware-update-uri" would provide a link directly to a > firmware update page either in the printer or the manufacturer's website. >
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] Registration proposal for additional IPP Pr… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Registration proposal for additional IP… Michael Sweet via ipp
- Re: [IPP] Registration proposal for additional IP… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Registration proposal for additional IP… John Madden via ipp
- Re: [IPP] Registration proposal for additional IP… Uli Wehner via ipp
- Re: [IPP] Registration proposal for additional IP… Ira McDonald via ipp
- Re: [IPP] Registration proposal for additional IP… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Registration proposal for additional IP… Uli Wehner via ipp
- Re: [IPP] Registration proposal for additional IP… Ira McDonald via ipp
- Re: [IPP] Registration proposal for additional IP… Uli Wehner via ipp
- Re: [IPP] Registration proposal for additional IP… Michael Sweet via ipp
- Re: [IPP] Registration proposal for additional IP… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Registration proposal for additional IP… Michael Sweet via ipp
- Re: [IPP] Registration proposal for additional IP… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Registration proposal for additional IP… Michael Sweet via ipp
- Re: [IPP] Registration proposal for additional IP… Kennedy, Smith (Wireless & IPP Standards) via ipp