[Rats] Re: EAT profile mechanics: ueid vs sueids for a resettable value, and current practice for profile identifiers
Laurence Lundblade <lgl@island-resort.com> Sun, 30 August 2026 17:51 UTC
Return-Path: <lgl@island-resort.com>
X-Original-To: rats@mail2.ietf.org
Delivered-To: rats@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D5F30131DD35E for <rats@mail2.ietf.org>; Sun, 30 Aug 2026 10:51:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788112314; bh=cmr+/y3/x2nxHJchSA2ZnoTEPaAwZsjuLxC8r/mRmpc=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=NfMj+Ue6i63wozxmpZ1yuygA431Zu9tbwVlURbtfTLsew2aRHvzYkTpfLCbRScRnf 17n8y/Rmtq4I9HRIEf2zR/Ys0/NuR50BOpbFGaZRcvjTpLJ78a+IrhPO9djChk8N+O lyx7TcpelU3CLuWMdaDmf0SOZccTFgVMauN1hwmo=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.695
X-Spam-Level:
X-Spam-Status: No, score=-1.695 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=island-resort.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9KLDiSFsRvb for <rats@mail2.ietf.org>; Sun, 30 Aug 2026 10:51:54 -0700 (PDT)
Received: from sender4-op-o12.zoho.com (sender4-op-o12.zoho.com [136.143.188.12]) (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 mail2.ietf.org (Postfix) with ESMTPS id 50C3A131DD359 for <rats@ietf.org>; Sun, 30 Aug 2026 10:51:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1788112305; cv=none; d=zohomail.com; s=zohoarc; b=IPfrNQljPwIEGWoOEjkhcQD5uFyNDzWhrjRXUiN5adtCX5N49CPwmsPjCWgQQUFLyaALfNKqPBnF0mVXDXZePed21jJPal8BR8LxSh4coMxmKt3zxXLQt9NhiM/Md8I4y1tOhyDyQv/5+yEjABuKPpd9VjJgCvyZ9X5s6ZZgDLc=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1788112305; h=Content-Type:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:Subject:Subject:To:To:Message-Id:Reply-To; bh=clnxtpkRBCARjwK1Pz2PsBpSkOyCOeRvDBZxNRm/EWk=; b=QoSCpAr3GoxIbuONyjAN5yevtexGtmuWDzl5D1ynLMiVd3tStl3d9LgXKiVOqyMas6eP0xoO602chBDfMR46Ef0Kt5AH0mBNh57ifovFFLDTs5wIllqIHGDuu4Xv/ftMnYwp8DtBB0WeKwliiFnlKyeMAyB5QApOrOf/xgn8s7w=
ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=island-resort.com; spf=pass smtp.mailfrom=lgl@island-resort.com; dmarc=pass header.from=<lgl@island-resort.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1788112305; s=island; d=island-resort.com; i=lgl@island-resort.com; h=From:From:Message-Id:Message-Id:Content-Type:Mime-Version:Subject:Subject:Date:Date:In-Reply-To:Cc:Cc:To:To:Reply-To; bh=clnxtpkRBCARjwK1Pz2PsBpSkOyCOeRvDBZxNRm/EWk=; b=kGrOialGX+bhgi/g+VZdcPChkkcB/RtJzLY+3wP9soC8Kpdw/5MCJR5lYvSPSOMq FqXDc4tgTFlnHBl1LlJ1GoUcsKnBC0r/khgQ+pt9fXtKo/jjEG8yaho+KIJwqk3sdet tb4Eg6hASy1ODThdT8ZNBn5OhOEq3NqVjfbgibVw=
Received: by mx.zohomail.com with SMTPS id 1788112301624299.79185542948676; Sun, 30 Aug 2026 10:51:41 -0700 (PDT)
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <757AD704-0BD3-4733-8808-65D670E896A7@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BFFBA445-B4B4-4BEF-8E25-FEB56329E64F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Date: Sun, 30 Aug 2026 10:51:30 -0700
In-Reply-To: <EA88AFD3-05C1-46AE-965C-D519BE97C470@yuthent.com>
To: Mohamad Khalil Yossif <mohamad=40yuthent.com@dmarc.ietf.org>
References: <EA88AFD3-05C1-46AE-965C-D519BE97C470@yuthent.com>
X-Mailer: Apple Mail (2.3826.500.181.1.5)
X-ZohoMailClient: External
Message-ID-Hash: Q6EZCGQAKC4H24GASAT3SIQKSNSAYRME
X-Message-ID-Hash: Q6EZCGQAKC4H24GASAT3SIQKSNSAYRME
X-MailFrom: lgl@island-resort.com
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
CC: rats@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rats] Re: EAT profile mechanics: ueid vs sueids for a resettable value, and current practice for profile identifiers
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/uBQKy3glbA9KxCAerbUrzAN9JRk>
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>
You should use sueid. The sueid text says "Examples of life-cycle events are change of ownership, factory reset, ..." LL > On Aug 30, 2026, at 4:10 AM, Mohamad Khalil Yossif <mohamad=40yuthent.com@dmarc.ietf.org> wrote: > >> 1. ueid or sueids for a value that changes on factory reset >> >> draft-yossif-psea profiles an EAT token and puts a per-deployment >> value in ueid. The value is re-derived when the device identifier is >> regenerated - a factory reset, or on iOS the loss of the Keychain >> entry. >> >> Section 4.2.1.1 says a UEID is permanent and MUST NOT change for a >> given entity. Section 4.2.2 describes a value that MAY change on >> entity life-cycle events, gives factory reset as an example, and lets >> a profile specify the triggering events and carry a label. >> >> Read plainly, a per-deployment value that changes on a life-cycle >> event is an SUEID and not a UEID. If that is right, I have the wrong >> claim rather than the wrong derivation, and I would rather move it >> once, deliberately, than ship a revision that leaves the claim >> selection wrong. >> >> The question is narrow: is the permanence requirement in 4.2.1.1 >> meant to bite on a value regenerated by a factory reset, or is that >> within what a UEID may do? A one-line view from anyone who was in the >> room for 4.2.1 and 4.2.2 settles it.
- [Rats] EAT profile mechanics: ueid vs sueids for … Mohamad Khalil Yossif
- [Rats] Re: EAT profile mechanics: ueid vs sueids … Thomas Fossati
- [Rats] Re: EAT profile mechanics: ueid vs sueids … Laurence Lundblade
- [Rats] Re: EAT profile mechanics: ueid vs sueids … Mandyam, Giridhar