Re: [IPP] Updated IPP Firmware Update Extensions figure slides posted (plain text version)
Michael Sweet via ipp <ipp@pwg.org> Mon, 16 September 2024 15:56 UTC
Received: by ietfa.amsl.com (Postfix) id 8E567C1840DB; Mon, 16 Sep 2024 08:56:16 -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 8DA8EC151996 for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 16 Sep 2024 08:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.107
X-Spam-Level:
X-Spam-Status: No, score=-8.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_DNSWL_HI=-5, 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="eqMW7YpK"; dkim=pass (1024-bit key) header.d=pwg.org header.b="AT1nd9Gi"; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=msweet.org header.b="uFSxcFfq"
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 Kj_ksAdiUVuh for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 16 Sep 2024 08:56:12 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 254E6C1840CD for <ipp-archive2@ietf.org>; Mon, 16 Sep 2024 08:56:12 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 87C9AE901; Mon, 16 Sep 2024 15:56:11 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 87C9AE901
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1726502171; bh=R+rqAb1B4+jVxpFY835ecRdgQ9gXqZ4nuJLLd596zpo=; 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=eqMW7YpKPMB8I02tsg+rizlAIc94QaKzMRzGlgb3IGsRJ2rlzZOt/9BNuBV/MLRRW 7fgggBVdMmvVfWwbYfCzSQiv4pE4+0+ewoJeGnHdL0SDYpgA04HXa75YPCaQs3pkBI YuRsHQLdOJl1w7BaRR/yb0QcX7daQoSnpG/54KAE=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id A2DF620AB; Mon, 16 Sep 2024 15:56:07 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org A2DF620AB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1726502167; bh=R+rqAb1B4+jVxpFY835ecRdgQ9gXqZ4nuJLLd596zpo=; 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=AT1nd9GiqkJvNQHhrXWnb+ZLiv670BYRELng1LsA3qNC7YaPaxKADX/b03jW8RJN1 LoIc7bdrQJNJgg7QspKD3XaHDm7zY1gM+YALITAMtN0UZTc0Qtbo5XJE88C5ZiI3NB TKS7L3TicgV/wj4Lo1zzdSAoLVXe8cPjIvebdwi8=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id D0FC441C2; Mon, 16 Sep 2024 15:56:06 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org D0FC441C2
Authentication-Results: mail.pwg.org; dkim=pass (1024-bit key) header.d=msweet.org header.i=@msweet.org header.b="uFSxcFfq"
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTPS id 8C49F3CB for <ipp@pwg.org>; Mon, 16 Sep 2024 15:56:04 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 8C49F3CB
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 13CFA80438; Mon, 16 Sep 2024 15:56:02 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 13CFA80438
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1726502163; bh=Ef58/7/ghgCTQ0x/RIpCk1uGYm/OjPDSFATjSOHK5qQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=uFSxcFfqjP/JuKEVivReigu8soc8oOlfHZ8SlhrbMrsKJW+epU7bqE6kpfw4xPAOV FzAJOxPrznXd6EOcDqDDWMUYvaueofM9ImCzCYCpbDxHEQgUDtiJy84E7DQ304Bu7a zcvZITMckBS7z7+69htwxGCWEBPmYv/CXJ7PB/cs=
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
In-Reply-To: <C95ACE81-403B-45F1-AC76-7B7982D4422D@hp.com>
Date: Mon, 16 Sep 2024 11:55:51 -0400
Message-Id: <45C8B197-B6B7-4024-BB50-1A82F69FEC7E@msweet.org>
References: <C95ACE81-403B-45F1-AC76-7B7982D4422D@hp.com>
To: PWG IPP Workgroup <ipp@pwg.org>
X-Mailer: Apple Mail (2.3776.700.51)
Subject: Re: [IPP] Updated IPP Firmware Update Extensions figure slides posted (plain text version)
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: multipart/mixed; boundary="===============0689330172020978236=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Smith, OK, making use of the "PlantUML web server" (http://www.plantuml.com/plantuml/uml) which allows you to fiddle with these diagrams in real time, I have some updates: 1. Client Managed Firmware Update (I normalized the communication with the repository, added the client requests from IPP System Service, added a Printer self-update step, added double-ended arrows for the query/notify step, and grouped things like you did for the other scenarios) @startuml title Firmware Update Scenario 1: Client Managed Firmware Update autonumber skinparam sequenceMessageAlign direction participant Client participant Printer participant Repository group Client checks for firmware update Client -> Repository: Firmware update available? Repository -> Client: Update availability Client -> Repository: Download firmware update Repository -> Client: Firmware update file end group group Client sends firmware update to printer Client -> Printer: Create-Resource Client -> Printer: Send-Resource w/firmware update file Client -> Printer: Install-Resource Printer -> Printer: Install firmware update end group ||| group Client monitors Printer firmware status Client <-> Printer: Query/notify firmware update status end group @enduml 2. Autonomous Printer Firmware Update (I separated the "self-update" into download from repo and install to self, and added a client query/notify grouping) @startuml title Firmware Update Scenario 2: Autonomous Printer Firmware Update autonumber skinparam sequenceMessageAlign direction participant Client participant Printer participant Repository group Printer autonomously installs firmware updates Printer -> Repository: Firmware update available? Repository -> Printer: Update availability Printer -> Repository: Download firmware update Repository -> Printer: Firmware update file Printer -> Printer: Install firmware update end group ||| group Client monitors Printer firmware status Client <-> Printer: Query/notify firmware update status end group @enduml 3. Client Triggered Firmware Update (Tried to normalize things with the prior diagrams, dropped reboot because that isn't always necessary) @startuml title Firmware Update Scenario 3: Triggered Firmware Update autonumber skinparam sequenceMessageAlign direction participant Client participant Printer participant Repository group Client asks Printer to check for firmware update Client -> Printer: Check for Firmware Update Printer -> Repository: Update available? Repository -> Printer: Update availability Printer -> Client: Update availablility end group ||| group Client ask Printer to install firmware update Client -> Printer: Update Firmware Printer -> Repository: Firmware update available? Repository -> Printer: Update availability Printer -> Repository: Download firmware update Repository -> Printer: Firmware update file Printer -> Client: Firmware update status Printer -> Printer: Install firmware update end group ||| group Client monitors Printer firmware status Client <-> Printer: Query/notify firmware update status end group @enduml > On Sep 13, 2024, at 9:53 AM, Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp@pwg.org> wrote: > > Greetings, > > (Sending again in plain text) > > We agreed that I should post the slides we were using to model the scenarios and think about them and decide. Here's the slides: > > https://ftp.pwg.org/pub/pwg/ipp/slides/IPP-Firmware-Update-Extensions-Registration-Options-20240912.pptx > > > Here's PlantUML for Scenario #1: > > @startuml > > title Firmware Update Scenario 1: Client Managed Firmware Update > autonumber > skinparam sequenceMessageAlign direction > > participant Client > participant Printer > participant Repository > > Client -> Repository: Firmware update available? > Client <- Repository: Download firmware update > ||| > Client -> Printer: Send firmware update to Printer > Client -> Printer: Monitor firmware update progress > > @enduml > > > Here's PlantUML for Scenario #2: > > @startuml > > title Firmware Update Scenario 2: Autonomous Printer Firmware Self-Update > autonumber > skinparam sequenceMessageAlign direction > > participant Client > participant Printer > participant Repository > > Printer -> Repository: Firmware update available? > Printer <- Repository: Firmware Self-update > > @enduml > > > Here's a longer PlantUML for Scenario #3, incorporating both Check-For-Firmware-Update and Update-Printer-Firmware but no scheduling: > > @startuml > > title Firmware Update Scenario 3: Triggered Self-Update > autonumber > skinparam sequenceMessageAlign direction > > participant Client > participant Printer > participant Repository > > group Client triggers Printer to check for firmware update > Client -> Printer: Check for Firmware Update > Printer -> Repository: Firmware update available? > Printer <- Repository: Firmware update is available > Client <- Printer: Firmware update is available > end group > > > group Client triggers Printer to self-update > Client -> Printer: Update Firmware > Printer -> Repository: Firmware Self-update > Repository -> Printer: Firmware update > Client --> Printer: Monitor firmware update progress > Printer -> Printer: Update firmware > Client --> Printer: Monitor firmware update progress > Printer -> Printer: Reboot > Client --> Printer: Monitor firmware update progress > Printer -> Printer: Update complete > end group > @enduml > > Feel free to post updates to the slides or tweaks to the PlantUML UML sequences. > > 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
- [IPP] Updated IPP Firmware Update Extensions figu… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Updated IPP Firmware Update Extensions … Michael Sweet via ipp
- Re: [IPP] Updated IPP Firmware Update Extensions … Michael Sweet via ipp
- Re: [IPP] Updated IPP Firmware Update Extensions … Kennedy, Smith (Wireless & IPP Standards) via ipp