IETF Logo Mail Archive

[Anima] Re: Question regarding use of assertions in vouchers in RFC8366bis

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 09 September 2024 19:10 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45FE7C1CAE97 for <anima@ietfa.amsl.com>; Mon, 9 Sep 2024 12:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.406
X-Spam-Level:
X-Spam-Status: No, score=-4.406 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_MED=-2.3, 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 JrNPTj8RvJ1K for <anima@ietfa.amsl.com>; Mon, 9 Sep 2024 12:10:53 -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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D80DC16943D for <anima@ietf.org>; Mon, 9 Sep 2024 12:10:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D67C138EA6; Mon, 9 Sep 2024 15:10:50 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id fl6cnffMe2xO; Mon, 9 Sep 2024 15:10:50 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1725909050; bh=Xt8j2cCaY75vCzCmhEmFGPFX41uwiLnQDJAyBwNo+ao=; h=From:To:Subject:In-Reply-To:References:Date:From; b=a/axlgn6BZ7N+4w3I47a9T4K6/tHGzA0SLc0jyvREpe3XqpFK/89JtUr5+AiFFF7Q VCSUfm5irrXHMPC9wpbM6urFEMbIoRxpJsj/0DkC+wZL6n/l/M+Is0IUGI+s25ZyzG nphpGRUuchFixH3A/B/H/18Vg0ATuCceUW+ojGsdtP0Didu+rt60L0kpqvtRkcAdZb KVQsYIPokcBwkHYjtGzVW1P5rh62wm0V5mTHinCMIrXuyE0bgwVa1F1hQSSlX4ukIb vdFjPbKpS/Qf/Oiq3Ltclm0YubmhcREc61ua83JJj68z8I6MaEK4x3A5mLyuOECdJ1 GKyyx7nVtioHg==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0725738EA5; Mon, 9 Sep 2024 15:10:50 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BE0AC96D; Mon, 9 Sep 2024 15:10:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Fries, Steffen" <steffen.fries@siemens.com>, "anima@ietf.org" <anima@ietf.org>
In-Reply-To: <DB9PR10MB635433EA7646492016C25783F3932@DB9PR10MB6354.EURPRD10.PROD.OUTLOOK.COM>
References: <DB9PR10MB6354B8FF05E979ED40F70165F3962@DB9PR10MB6354.EURPRD10.PROD.OUTLOOK.COM> <22780.1725237355@obiwan.sandelman.ca> <DB9PR10MB63541732C4FDDBC9329BF252F3922@DB9PR10MB6354.EURPRD10.PROD.OUTLOOK.COM> <29913.1725280803@obiwan.sandelman.ca> <DB9PR10MB6354C77326D9B96D7AFAC207F3922@DB9PR10MB6354.EURPRD10.PROD.OUTLOOK.COM> <DU0P190MB197830EBB45A86F171712F36FD932@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <DB9PR10MB635433EA7646492016C25783F3932@DB9PR10MB6354.EURPRD10.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: Mon, 09 Sep 2024 15:10:49 -0400
Message-ID: <23686.1725909049@obiwan.sandelman.ca>
Message-ID-Hash: 3NWH27DAYI74KKDHMNORIFS2DOFG7WPX
X-Message-ID-Hash: 3NWH27DAYI74KKDHMNORIFS2DOFG7WPX
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-anima.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: [Anima] Re: Question regarding use of assertions in vouchers in RFC8366bis
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/htPXOP_e7ZJekATNkDvDYg_mtdM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Owner: <mailto:anima-owner@ietf.org>
List-Post: <mailto:anima@ietf.org>
List-Subscribe: <mailto:anima-join@ietf.org>
List-Unsubscribe: <mailto:anima-leave@ietf.org>

Fries, Steffen <steffen.fries@siemens.com> wrote:
    > Hi Esko

    > What irritates me is the statement in the YANG definition of RFC 8366bis:
    > "Indicates that the voucher has been issued after

okay, so let's do better text.

    > Therefore the question for me is not quite answered, if the MASA gets a
    > PVR with a nonce and is able to verify proximity, but does not know the
    > customer domain, he could provide both values, "proximity" as he could
    > verify that the pledge was in direct contact with the registrar and
    > "logged" because he does not know the customer domain (maybe I'm
    > relating to much in the "trust-on-first-use" statement in the YANG
    > description, which I understand as trust-on-first-use for the MASA when
    > seeing a PVR from an unknown domain.

I think that I'd pick proximity.

Some manufacturers and some device classes are reasonable for TOFU, some are not.
In between full supply chain integration would be some kind of Trust-on-First-Customer.
In that case, the customer domain has to be a known *customer*, but which
device they get is TOFU.
It would be good to come up with words to explain this.

If you think it should be reflected in the new/additional voucher types, I'm
certain open to that idea.



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

v2.46.0 | Report a Bug | By Email | System Status