Re: [Suit] SUIT rechartering: proposed text

Russ Housley <housley@vigilsec.com> Tue, 10 August 2021 16:38 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8313A139E for <suit@ietfa.amsl.com>; Tue, 10 Aug 2021 09:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level:
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIgAt2Kgs47m for <suit@ietfa.amsl.com>; Tue, 10 Aug 2021 09:38:16 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC5733A13A0 for <suit@ietf.org>; Tue, 10 Aug 2021 09:38:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7E3F6300C9B for <suit@ietf.org>; Tue, 10 Aug 2021 12:38:15 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4lMzDZRZ5cMs for <suit@ietf.org>; Tue, 10 Aug 2021 12:38:13 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 867D630065E for <suit@ietf.org>; Tue, 10 Aug 2021 12:38:13 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FB16B8FB-6176-4BA7-8823-E20D52F8A88E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Tue, 10 Aug 2021 12:38:12 -0400
References: <66D84CE5-22E6-44F0-8239-8A5832326219@arm.com> <3E7D5E5B-03EE-4EDD-A951-FB119F72DDE8@arm.com> <16339.1613515194@localhost> <E4B87013-1498-463F-98C0-5FF13344C3EA@arm.com> <6FC3F38A-B067-4180-ACD9-A121162EA459@vigilsec.com> <26718.1626138395@localhost> <MN2PR09MB4841BA0A0CC978E70A09A509F0119@MN2PR09MB4841.namprd09.prod.outlook.com> <67F117E7-28F2-45F3-BC4C-AC8116BCB69F@vigilsec.com> <SN6PR2101MB0943178F1E627E78A1343AE8A3E59@SN6PR2101MB0943.namprd21.prod.outlook.com> <50B65F80-808D-4591-9D4D-2346796DA204@vigilsec.com> <1944E3C3-9348-4574-AE26-4133BFD932B0@vigilsec.com> <CH2PR21MB1464AC4D50A932EC45A3B369A3EF9@CH2PR21MB1464.namprd21.prod.outlook.com> <3944F4E6-9644-4D23-9DB0-B0AC0490AB51@vigilsec.com> <A460F3FC-0EC6-4B8F-9D8C-D40AC841E602@arm.com> <20192.1628612087@localhost> <CAN40gSsvPrnMzUrQASo7nmJJKYGjNm=GNtOd9v9+a7Ni1waCCQ@mail.gmail.com> <CH2PR21MB1464E5F803ED4E22B6D90DD3A3F79@CH2PR21MB1464.namprd21.prod.outlook.com>
To: suit <suit@ietf.org>
In-Reply-To: <CH2PR21MB1464E5F803ED4E22B6D90DD3A3F79@CH2PR21MB1464.namprd21.prod.outlook.com>
Message-Id: <2002841D-85D6-41AB-B214-963174485119@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/fFcn0Vwl3UXTMeTmC_PX1on60Yw>
Subject: Re: [Suit] SUIT rechartering: proposed text
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Aug 2021 16:38:22 -0000

Okay, I dropped that paragraph.

Any other comments from anyone?

Russ

> On Aug 10, 2021, at 12:33 PM, Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org> wrote:
> 
> I agree with Brendan, etc.
> Maybe we should simply remove the paragraph and remain silent.
>  
> Dave
>  
> From: Suit <suit-bounces@ietf.org <mailto:suit-bounces@ietf.org>> On Behalf Of Ira McDonald
> Sent: Tuesday, August 10, 2021 9:30 AM
> To: Michael Richardson <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>>; Ira McDonald <blueroofmusic@gmail.com <mailto:blueroofmusic@gmail.com>>
> Cc: suit <suit@ietf.org <mailto:suit@ietf.org>>; Brendan Moran <Brendan.Moran@arm.com <mailto:Brendan.Moran@arm.com>>
> Subject: Re: [Suit] SUIT rechartering: proposed text
>  
> Hi,
>  
> I suggest that SUIT indeed has potentially much wider utility
> than just the initial firmware of an embedded device.  
>  
> Without displacing other vendor and consortia based software
> update solutions, I suggest that SUIT could be used to update
> software modules (after initial firmware) in a target device.
>  
> Having spent the last two years as a US invited expert in the
> ISO 24089 Road Vehicles: Software Update project and the
> last eight years addressing OTA firmware/software update
> for the automotive industry, I suggest that SUIT has quite a
> few advantages over many of the other solutions that were
> adapted from the mobile phone industry.
>  
> I believe that it would be unfortunate for the SUIT charter to
> imply or explicitly say that it's not suitable for the automotive
> industry.
>  
> Cheers,
> - Ira
>  
>  
> On Tue, Aug 10, 2021 at 12:16 PM Michael Richardson <mcr+ietf@sandelman.ca <mailto:mcr%2Bietf@sandelman.ca>> wrote:
> 
> Brendan Moran <Brendan.Moran@arm.com <mailto:Brendan.Moran@arm.com>> wrote:
>     > I’m slightly concerned by one paragraph:
> 
>     >>> The SUIT WG does not aim to create a standard for a generic
>     >>> application software update mechanism, but instead the SUIT WG is
>     >>> focusing on firmware development practices in the embedded
>     >>> industry. Software update solutions that target updating software
>     >>> other than the firmware binaries (e.g., applications) are also out of
>     >>> scope.
> 
>     > This is a concern because, in the manifest format, we say that the
>     > primary goal is firmware update, but it’s still usable for software
>     > update. If this paragraph of the charter remains as-is, then the
>     > manifest format appears to go counter to the charter. I would argue
>     > that this paragraph appears to prohibit the development of support for
>     > TEEP.
> 
> We weren't aiming for software update, but it turns out that we hit the mark.
> 
> The paragraph, as Russ says, is left over from before.
> The important part about it is that if SUIT Manifest format was found lacking
> in some way as a "generic application software update", that wouldn't be considered a bug.
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca <mailto:mcr%2BIETF@sandelman.ca>>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> _______________________________________________
> Suit mailing list
> Suit@ietf.org <mailto:Suit@ietf.org>
> https://www.ietf.org/mailman/listinfo/suit <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsuit&data=04%7C01%7Cdthaler%40microsoft.com%7Cf2c973072f7d459050b808d95c1c6604%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637642099315360855%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=INYmiKpX8DUroLOGBG9y9K2RMJc%2B%2Bk9hbWTQRqInFUA%3D&reserved=0>_______________________________________________
> Suit mailing list
> Suit@ietf.org <mailto:Suit@ietf.org>
> https://www.ietf.org/mailman/listinfo/suit <https://www.ietf.org/mailman/listinfo/suit>