IETF Logo Mail Archive

[Rats] Re: [Use Case] RATS for Hardware-Enforced State Management in Autonomous Agents (AIGA)

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 14 January 2026 17:19 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 7F176A7A6FA6 for <rats@mail2.ietf.org>; Wed, 14 Jan 2026 09:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 07rLAl-yj7yI for <rats@mail2.ietf.org>; Wed, 14 Jan 2026 09:19:00 -0800 (PST)
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 ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 23E83A7A6F9C for <rats@ietf.org>; Wed, 14 Jan 2026 09:19:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 95D331801A; Wed, 14 Jan 2026 12:18:59 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id A1nmbgt_CEVq; Wed, 14 Jan 2026 12:18:57 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1768411137; bh=cxvr42jpx2DWNyAxdmkQNU5yBMt0hUas7qqanXE/hFA=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=t0CYP0BGs3u81rXtKwaWZf4iUw+jUwqRWMNb/RpYDUWBKSmTlRSdRWQFhjmNyZUiO WfL4sL5eTWyB/O9OIXV45Zklmr0+JsmI+PDkKi7MqzGclZQNC4zlkYxLHrt2eSlv3c OVTAqA4ratTLjBPa0hT4eN6QyE5Wx/WUVX11TjP9/60JvY6KQGu0QHYs0aP+gRibmy s3EUhuSQKr9BHoiwpQ8qmiETocnXjjbsNDH+HVcFyyJk3OT4mcretRc9SEsXZXBcto quG/KAo65uMWJwVKpBDTgZZJAXxw7S3pB7zRWqW7CmPwdauioeii4CTQeKIIxJ7BX6 dS3brbUHdIVZQ==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2C1B618019; Wed, 14 Jan 2026 12:18:57 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 22B5B1AE; Wed, 14 Jan 2026 12:18:57 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Edward Aylward <aylward.edward@gmail.com>
In-Reply-To: <CAL6-Gb-O7LEifnA1iT5hHC78_svdDSyoje7G6E6X0yb6yRhTHw@mail.gmail.com>
References: <CAL6-Gb-O7LEifnA1iT5hHC78_svdDSyoje7G6E6X0yb6yRhTHw@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.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-sha512"; protocol="application/pgp-signature"
Date: Wed, 14 Jan 2026 12:18:57 -0500
Message-ID: <8222.1768411137@obiwan.sandelman.ca>
Message-ID-Hash: EK2HABD47OI62RTSK5QDONT4YGVYVPKQ
X-Message-ID-Hash: EK2HABD47OI62RTSK5QDONT4YGVYVPKQ
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
CC: rats@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rats] Re: [Use Case] RATS for Hardware-Enforced State Management in Autonomous Agents (AIGA)
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/lq40eazuS9GZDLXWL1KLMWSe20A>
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>

Edward Aylward <aylward.edward@gmail.com> wrote:
    > My Questions for the WG:
    > 1. Does the RATS architecture support a model where the "Relying Party"
    > (the network peer) is distinct from the "Verifier" (the Governance Node) in
    > a real-time loop?

Explicitely, see figure 1 of RFC9334.

    > 2. Are there existing EAT claims (CWT/JWT) best suited for representing
    > "Operational State" (e.g., Active vs. Terminated), or would this require a
    > custom profile?

Seems like a specific claim would be worthwhile.
I would not make it an on/off.

I would make it a date:
  Agent-Last-Activated: YYYY-MM-DD
  Agent-Last-Deactivated: YYYY-MM-DD

it would work like notBefore/notAfter in certificates.

    > I would appreciate any guidance on whether this use case fits within the
    > current RATS charter or if there are existing profiles I should reference
    > to align Section 5.1 with standard practices.


--
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