Re: [Suit] New Version Notification for draft-moran-suit-mti-00.txt

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 12 July 2022 22:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D534FC14F6E5 for <suit@ietfa.amsl.com>; Tue, 12 Jul 2022 15:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
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 KXgbgVc6yuU4 for <suit@ietfa.amsl.com>; Tue, 12 Jul 2022 15:21:40 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 450F8C14F6EB for <suit@ietf.org>; Tue, 12 Jul 2022 15:21:39 -0700 (PDT)
Received: from dooku.sandelman.ca (cpef81d0f835a73-cmf81d0f835a70.sdns.net.rogers.com [174.115.215.42]) by relay.sandelman.ca (Postfix) with ESMTPS id D64881F47D; Tue, 12 Jul 2022 22:21:37 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id C92A51A051E; Tue, 12 Jul 2022 18:21:35 -0400 (EDT)
Received: from dooku (localhost [127.0.0.1]) by dooku.sandelman.ca (Postfix) with ESMTP id C6C771A0373; Tue, 12 Jul 2022 18:21:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brendan Moran <Brendan.Moran@arm.com>
cc: suit <suit@ietf.org>
In-reply-to: <FBD0078C-A372-44D2-938F-ED3F0FD1E26E@arm.com>
References: <165756925632.5725.931709287060945912@ietfa.amsl.com> <FBD0078C-A372-44D2-938F-ED3F0FD1E26E@arm.com>
Comments: In-reply-to Brendan Moran <Brendan.Moran@arm.com> message dated "Mon, 11 Jul 2022 19:57:56 -0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 12 Jul 2022 18:21:35 -0400
Message-ID: <763261.1657664495@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/7HGqc5s4XadSM7RMSdCUFXFcqBA>
Subject: Re: [Suit] New Version Notification for draft-moran-suit-mti-00.txt
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.39
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, 12 Jul 2022 22:21:44 -0000

I guess that the things in parathesis are COSE algorithm identifiers.

2.3.1.  Symmetric
   *  A128 (-3)
   *  A192 (-4)
   *  A256 (-5)

Probably worth mentioning in the intro :-)

please consider modeling this like:
       https://www.rfc-editor.org/rfc/rfc8247.html

which extends BCP14.  {When reading the document, you may need to channel
Casey Casem (you and I know him as "Shaggy")  https://en.wikipedia.org/wiki/American_Top_40 }

   When used in the tables in this document, these terms indicate that
   the listed algorithm MUST, MUST NOT, SHOULD, SHOULD NOT, or MAY be
   implemented as part of an IKEv2 implementation.  Additional terms
   used in this document are:

   SHOULD+   This term means the same as SHOULD.  However, it is likely
             that an algorithm marked as SHOULD+ will be promoted at
             some future time to be a MUST.

   SHOULD-   This term means the same as SHOULD.  However, an algorithm
             marked as SHOULD- may be deprecated to a MAY in a future
             version of this document.

   MUST-     This term means the same as MUST.  However, it is expected
             at some point that this algorithm will no longer be a MUST
             in a future document.  Although its status will be
             determined at a later time, it is reasonable to expect that
             if a future revision of a document alters the status of a
             MUST- algorithm, it will remain at least a SHOULD or a
             SHOULD- level.

   IoT       This abbreviation stands for "Internet of Things".


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-