[Rats] Re: Hint Discussion in CSR Attestation Draft

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 23 June 2024 19:34 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 1FA1DC14F619; Sun, 23 Jun 2024 12:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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
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 2ZTG7XAh8SMO; Sun, 23 Jun 2024 12:34:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 7D56DC14F5FE; Sun, 23 Jun 2024 12:34:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1DDCF3898B; Sun, 23 Jun 2024 15:34:31 -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 cHs4o75qVYSH; Sun, 23 Jun 2024 15:34:28 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3912D38988; Sun, 23 Jun 2024 15:34:28 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1719171268; bh=TvrHxXbjtJFSdRMNBHB7BNwVklaKiItYonFiGa3vLuA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=hA+5fzPpUItpbYignF/IawCnckijXSXflbOUWEM6Ai1L3kOCmkVJ1FngcSpsEGU4p t3vSfZuoAd9jIjpU7rXLQIGoV4hTQv78+tRsbnnz2oewMm35A+SoostunugVrpGB5J VyT/MNzhJi2/mbVfw3Hhkc46kihbHzdwOYu0i7hd7j8Up2KnJMkMZa6oTJSTLLCvJ6 Czr7KBu8kSXMPEIDgUTkn9G/qu0hHklM9Jxfjdq4/ZVKUYmVinTUIElB1VFcHErr9m sBtOr0JfNkm/elxiMs8zevQmKrYeZPQkkQk7jjDJaD6YgQQy86SqlRiUbKMchYb8GN 3M+p0Igpbuwqg==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 35CBF24F; Sun, 23 Jun 2024 15:34:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carl Wallace <carl@redhoundsoftware.com>, "spasm@ietf.org" <spasm@ietf.org>, rats <rats@ietf.org>
In-Reply-To: <E7968891-2903-4A53-8A8C-060BFBE349AA@redhoundsoftware.com>
References: <AS8PR10MB742727BFEC71CB78468FB0E7EECD2@AS8PR10MB7427.EURPRD10.PROD.OUTLOOK.COM> <0145e095-e684-d2ee-58d5-41aee54a4b3b@ietf.contact> <2627.1718830718@obiwan.sandelman.ca> <FB01F359-84F4-4AAD-82F7-1CF2356DCD4B@redhoundsoftware.com> <CAObGJnO6bn5xEpqPxc46HRh3v2BnmxbE0YXwfNv9BtQnNV9Mag@mail.gmail.com> <E7968891-2903-4A53-8A8C-060BFBE349AA@redhoundsoftware.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, 23 Jun 2024 15:34:28 -0400
Message-ID: <12592.1719171268@obiwan.sandelman.ca>
Message-ID-Hash: RPRLXDXTS5CYIBLMXFPIH6OP2UPNBAOS
X-Message-ID-Hash: RPRLXDXTS5CYIBLMXFPIH6OP2UPNBAOS
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: Hint Discussion in CSR Attestation Draft
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/7-UT67jJs_4t8GuQcXg4PUAO2BA>
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>

Thomas Fossati wrote:
    ts> You wouldn't. The hint is a routing label that is used by the relying
    ts> party to decide which verifier to contact for handling this specific
    ts> piece of attestation evidence. When evidence reaches the verifier the
    ts> hint is no more.

Carl Wallace <carl@redhoundsoftware.com> wrote:

    CW> OK, so relying party, not verifier. How would the relying party use a
    CW> "free form" label to route anything?

I admit that I'm not keen about the free-form-ness of the hint.

I guess I'd rather it was specified as a URI, with ni:, or something like
that being the default string-like thing that one just strcmp() against a
configuration file.   That way, once we figure out what we really want,
intepreting it as a URI will already be established.
(I see in the URI list, no uuid:, but also secondlife: ha)



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