IETF Logo Mail Archive

Re: [Suit] SUIT rechartering: proposed text

Russ Housley <housley@vigilsec.com> Mon, 08 November 2021 18:02 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 3372B3A0BFE for <suit@ietfa.amsl.com>; Mon, 8 Nov 2021 10:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 kIOiq7zdZcVx for <suit@ietfa.amsl.com>; Mon, 8 Nov 2021 10:02:41 -0800 (PST)
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 771F63A0C0A for <suit@ietf.org>; Mon, 8 Nov 2021 10:02:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id EE16E300BF2 for <suit@ietf.org>; Mon, 8 Nov 2021 13:02:42 -0500 (EST)
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 QwQT0-JqOU6Y for <suit@ietf.org>; Mon, 8 Nov 2021 13:02:41 -0500 (EST)
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 92FE73005D7; Mon, 8 Nov 2021 13:02:41 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <BN1P110MB0939804ABED72445CBC21F67DC919@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
Date: Mon, 08 Nov 2021 13:02:38 -0500
Cc: suit <suit@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFCDE4B1-345A-4489-BCAF-B0A31AD82BD4@vigilsec.com>
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> <2002841D-85D6-41AB-B214-963174485119@vigilsec.com> <8A3FC35F-E993-4899-9213-A2DCA8D1F857@vigilsec.com> <BN1P110MB093911A420389098A6444B29DC8E9@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM> <B170B41E-CE69-4049-A091-C44DC4C934D6@vigilsec.com> <BN1P110MB0939804ABED72445CBC21F67DC919@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
To: "Roman D. Danyliw" <rdd@cert.org>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/leFraCxnLC6tHg1r8I6W8TtF7LI>
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: Mon, 08 Nov 2021 18:02:44 -0000

> 
>>> (c) Should be provide a milestone for deciding on where the joint RATS-SUIT
>> work will happen?
>> 
>> I think we can add a milestone if the work lands in SUIT.  I'm guessing it will
>> land in RATS with review in SUIT.
> 
> I was envisioning a milestone for the decision to do the work in RATS vs. SUIT, not a milestone for the work itself.  For example:
> 
> "XXX-2022  Decide with RATS WG on where the 'set of claims for attesting to firmware update status' document should be produced"

Based on the discussion on the call today, Mar 2022 seems like a good date for that milestone.

Russ

v2.23.0 | Report a Bug | By Email