IETF Logo Mail Archive

Re: [Rats] use case document updates on Roots of Trust

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 16 September 2019 17:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54139120888 for <rats@ietfa.amsl.com>; Mon, 16 Sep 2019 10:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 mIA84MA1v23G for <rats@ietfa.amsl.com>; Mon, 16 Sep 2019 10:09:48 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86D5B120887 for <rats@ietf.org>; Mon, 16 Sep 2019 10:09:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9B6E93897B; Mon, 16 Sep 2019 13:08:09 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C32F571B; Mon, 16 Sep 2019 13:09:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ira McDonald <blueroofmusic@gmail.com>
cc: "Smith, Ned" <ned.smith@intel.com>, "rats@ietf.org" <rats@ietf.org>
In-Reply-To: <CAN40gStjcnOoxbKLBokfTGs3wD1rBBT+dXvvDN=aTvukePc+CA@mail.gmail.com>
References: <4155.1567948986@dooku.sandelman.ca> <91BE5953-1EB8-4FEB-9F20-3C6FCB448302@intel.com> <CAN40gStjcnOoxbKLBokfTGs3wD1rBBT+dXvvDN=aTvukePc+CA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 16 Sep 2019 13:09:47 -0400
Message-ID: <23577.1568653787@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/qVj8N72_5L4tY7-UuhCFzJ55cWU>
Subject: Re: [Rats] use case document updates on Roots of Trust
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 17:09:51 -0000

Ira McDonald <blueroofmusic@gmail.com> wrote:
    > FWIW, the various SAE vehicle security committees commonly use "Trust
    > Anchor"
    > (rather than "RoT") to encompass the entire spectrum of RoTs, *as well as*
    > the
    > X.509 CA style trust anchor.  There's an entire SAE vehicle security
    > committee
    > titled SAE Trust Anchors and Authentication.  In addition, the SAE J3101
    > spec,

okay, so if we reference any SAE documents, let's be really specific about
what we mean, and let's not use the SAE documents as reasonable sources of
clear definitions ;-)

If there were some alternate words that we could use for self-measuring code,
then I'd like to use that term ourselves.  I'd rather break down the spectrum
of the terms into it's component "colours".


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

v2.23.0 | Report a Bug | By Email