[Rats] Re: Capitalization of RATS terms?

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 09 June 2024 22:16 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 C6EFCC14F6FF; Sun, 9 Jun 2024 15:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 I8_6DV1cSPIS; Sun, 9 Jun 2024 15:16:19 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86163C14F70A; Sun, 9 Jun 2024 15:16:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1D8D03898B; Sun, 9 Jun 2024 18:16:18 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xMFH1yByDR2S; Sun, 9 Jun 2024 18:16:17 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CB29C38988; Sun, 9 Jun 2024 18:16:16 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1717971376; bh=boDq0VFBWMrcGQ9WT2yqfTPARykTS+me8EXPAgQx3V8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=Ea+vL0Ai7QkZKNBGisUP4Nh+2/p0q3MO8yrI3rDchdQ1yy9rBt+1SER+arzLLgw5R H6MIPPPUM/fOSesNABCbRy1CeMEH5pCuUeeJ3Av+ys4JvMXerajMZanRTQD1MCLnSw LVyAYvPy1cBdgRvXppPth/kNL5wLqJt4d+uGkDqnscpFNSN9LWSVLsG8jGl3s2u8wt HSaPx2cErIDd85gX5zl670VKCBFH6JrKK4D0D0IedOhB+JIxxoftQ/IJ0BZyk/0OyN hQ95IaeH2ypbM3WbExYvW54CB0/pP27vqgYyshi6wGqIPv6HIT0x9IuHxwNvvVdANO +eXKuKgZQlcYw==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BF42147A; Sun, 9 Jun 2024 18:16:16 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, "rats@ietf.org" <rats@ietf.org>, 'LAMPS' <spasm@ietf.org>
In-Reply-To: <CH0PR11MB5739283BD1A0A264E4D96CDA9FC42@CH0PR11MB5739.namprd11.prod.outlook.com>
References: <CH0PR11MB5739283BD1A0A264E4D96CDA9FC42@CH0PR11MB5739.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
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-sha512"; protocol="application/pgp-signature"
Date: Sun, 09 Jun 2024 18:16:16 -0400
Message-ID: <4927.1717971376@obiwan.sandelman.ca>
Message-ID-Hash: 5GX2JZCHN2UF3XF4LRGRAUYZH2MANJFQ
X-Message-ID-Hash: 5GX2JZCHN2UF3XF4LRGRAUYZH2MANJFQ
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rats.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Rats] Re: Capitalization of RATS terms?
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/AmeKc43MbazypqPreKxzRasWn44>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Owner: <mailto:rats-owner@ietf.org>
List-Post: <mailto:rats@ietf.org>
List-Subscribe: <mailto:rats-join@ietf.org>
List-Unsubscribe: <mailto:rats-leave@ietf.org>

Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org> wrote:
    > Hi RATS,



    > This is spill-over from a LAMPS thread about the CSR-Attest draft [1]



    > That draft has some multiple personality disorder going on because each
    > entity (like an HSM, or a certificate issuer) holds both a PKI role
    > ("certificate requester", "CA") as well as a RATS role ("Attester",
    > "Relying Party").

I prefer this.

    > The editorial question is: we are currently capitalizing the RATS
    > roles: Evidence, Attesting Environment, Attestation Results, Verifier,
    > etc since, to a PKI audience, we want to highlight that these are
    > defined terms, but Carl points out that this practice was removed from
    > EAT during IESG review.  Would, for example, a glossary of terms that
    > we are importing from RFC 9334 better serve this purpose?

I disagreed with the changes to EAT.
It seems to me that you have already imported the terms:

   This document re-uses the terms defined in [RFC9334] related to
   remote attestation.  Readers of this document are assumed to be
   familiar with the following terms: Evidence, Claim, Attestation
   Results (AR), Attester, Verifier, Target Environment, Attesting
   Environment, and Relying Party (RP).

...


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide