[OAUTH-WG] Fwd: [agent2agent] New draft on AI Agent Auditing and proposed BoF/WG charter

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Wed, 20 May 2026 12:12 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: oauth@mail2.ietf.org
Delivered-To: oauth@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 46193F1889EC for <oauth@mail2.ietf.org>; Wed, 20 May 2026 05:12:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779279132; bh=d/rN3DwsXRxdNpMlJn2WoB3zL7V00/Ly0VCmfuZw6Io=; h=From:Subject:Date:References:Cc:To; b=Ycod6EvJb1I/maK9dGLzM/QHOVLU2NM7Kcz8QJHGs+6QYyl3QLdEN6GFLLDeTRAYc 41lKxSofEnCFJhS00VEK25uC0ibsKBoZ5Hk3aJe/eaaqbikXRZoJtxtxBr+VueDNs2 uMQRl6QbK0sr+RjgZvur8gjqVGk5MthGBaCc4T48=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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=kuehlewind.net
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 JN2N3dpzTLXc for <oauth@mail2.ietf.org>; Wed, 20 May 2026 05:12:11 -0700 (PDT)
Received: from outbound.ci.icloud.com (ci-2002k-snip4-4.eps.apple.com [57.103.88.235]) (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 4F56DF188880 for <oauth@ietf.org>; Wed, 20 May 2026 05:10:39 -0700 (PDT)
Received: from outbound.ci.icloud.com (unknown [127.0.0.2]) by p00-icloudmta-asmtp-us-central-1k-60-percent-6 (Postfix) with ESMTPS id C629118001E3; Wed, 20 May 2026 12:10:32 +0000 (UTC)
X-ICL-Out-Info: HUtFAUMHWwJACUgATUQeDx5WFlZNRAJCTQBLHV8EXRxED1YHWRcOVk1QHUcLdwBHFVEUVhpeBVZeVx1HTVEPDxlcDFUtXB5XGFUdRARZDxweXAwTH1RWAFBRHV8CCgRHBFsXRgNTRVEZFxFQAVgeVl5aF15NRx9ATWJJAVoZWxxAF0puTVMPDxtMHVsBUhxbHl1WXQhDS18ZXUUPVAFZCzQAQABAcVl2QhRMdV0ERgpDDj0eXw5aCkN6TgNcdC8KMFINVgVbDkUZVxwdA1IfDFBNAUMICghHA00XXjJTBF8RUBY=
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuehlewind.net; s=sig1; t=1779279033; x=1781871033; bh=ojWjCq7YwIsijpYJzJ6rTQXuF2YsBCczzWl+TI/x2/Q=; h=From:Content-Type:Mime-Version:Subject:Date:To:Message-Id:x-icloud-hme; b=cu13dRFVJdlrofqmad8IKz0TstSfGVZqjQVkFUyRLFyPQkAoTFaY8mIeDCbvfUcpgY+hpO27DZfqpfERuQYytXz+ls3Uoht9s3wTbAs4UgsDJqdLZNcC5fAFRhfgr5lMZrGIjVJgKVBA7Ae3yOtF1KMzc69m1daDxTO0662gEA9fvduWA4kkPUnyD3Ec/OeaSBA7TZLs9GH6VFVZ53R8XzeWac+8p+553w8rDfRUAcsaoiNBc8sDUkidVZmc+KbxUSIZ6kWMDfER1xrJPa36za4dnG1zK4a7H4jboL+MtzgFlqPaYR4qVt1SvzNqz4GMT7pimtY42WavzVVkxD6ZIw==
mail-alias-created-date: 1725731591227
Received: from smtpclient.apple (unknown [17.57.156.36]) by p00-icloudmta-asmtp-us-central-1k-60-percent-6 (Postfix) with ESMTPSA id CF51C18001D6; Wed, 20 May 2026 12:10:31 +0000 (UTC)
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1CA21039-1797-4A59-ACE6-F2B315E07B24"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Date: Wed, 20 May 2026 14:10:19 +0200
References: <0F12E264-D8D7-4746-B9F4-1C72A9D862F5@kuehlewind.net>
To: oauth@ietf.org
Message-Id: <9629D983-F2D2-4F03-837E-29183C601CD8@kuehlewind.net>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
X-Proofpoint-GUID: VEZdLGI8-KXvjullftYl1sezRp6fCNys
X-Proofpoint-ORIG-GUID: VEZdLGI8-KXvjullftYl1sezRp6fCNys
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNTIwMDExOCBTYWx0ZWRfX/WfJrGm9uK39 umkACd2iPPEy0dwHJ5zSPnal3gceLEsKvtI0DEqREgGf1T3/Nq2R/3akUfLFsmNUVynHaQSDx5f ct41HqgL+4sTNCeHcVgFJOkgL1esH69fEMsaf6Vfh4O84Z62pcUTLExqs41TM6xbEPWaBovBUd6 rHjPryX4ES1YFAa2IjodoZ6rH4Q7xvfVGzqYJMX4yepeEcQQ3a/l3rhtXQYCbeM9k5so98IbK9I G/qcJ4Tf+/+y5iNRipmgPWg0efPNybR1rExQrJE/fIfSorCMbJNKRKwUPS19AqRP4D6H1EDz5XZ gkmPeBu2fqxJzk6zra/zFlAeDsFXzRMUbSSgLoM6pgaFLyJ/TFKofkknH+a8VU=
X-Authority-Info-Out: v=2.4 cv=bo9BxUai c=1 sm=1 tr=0 ts=6a0da4b9 cx=c_apl:c_pps:t_out a=2G65uMN5HjSv0sBfM2Yj2w==:117 a=2G65uMN5HjSv0sBfM2Yj2w==:17 a=NGcC8JguVDcA:10 a=VkNPw1HP01LnGYTKEx00:22 a=48vgC7mUAAAA:8 a=0xL1y621AAAA:20 a=vbnxaXAQ9fR-OgirQrUA:9 a=QEXdDO2ut3YA:10 a=2eeaqa_RyIrOabqSWe0A:9 a=qzUqv2JPyr6asEj_:21 a=_W_S_7VecoQA:10 a=bA3UWDv6hWIuX7UZL3qL:22
Message-ID-Hash: 7RO5SFDL47YLSEVQ4WN6PZO4UF5EQT2V
X-Message-ID-Hash: 7RO5SFDL47YLSEVQ4WN6PZO4UF5EQT2V
X-MailFrom: ietf@kuehlewind.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] Fwd: [agent2agent] New draft on AI Agent Auditing and proposed BoF/WG charter
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/XmfuLtE8Jzx7qPVkXYf1BdSk_K0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

Hi oauth group!

We proposed a new potential BoF on auditing (for AI agents mainly) on the agent2agent mailing list (see below).

This work would likely have a dependency on authorisation and delegation work in this group. Therefore we thought this group might be interested. We would definitely be interested in feedback from this group!

Mirja & Henk

————————
Here is also the proposed charter text directly (for more details checkout the architecture draft linked below!):

# Agent Use of Delegation and Interaction Traceability (AUDIT) Working Group Charter

Autonomous and semi-autonomous software agents, including those based on artificial intelligence (AI), are increasingly deployed to act on behalf of users, organizations, and services across the Internet. These agents interact across multiple administrative or trust domains and can initiate actions without direct human oversight at each step.

This introduces challenges for auditability, accountability, and transparency, including:

* Difficulty attributing actions to a specific user, agent instance, or delegation context
* Loss of visibility across long-running or distributed workflows
* Inconsistent capture of delegation relationships, authorization context, and identity transitions
* Cross-domain interactions lack interoperable means to exchange or verify audit-relevant information about the participating agents and their interactions

AI agents participate in two distinct classes of interactions that must be audited:

* User-facing interactions, such as prompts, conversations, and approvals, capturing user intent and human-in-the-loop decisions
* System-facing interactions, such as API calls, tool usage, and delegation to other agents or services

Effective auditing requires linking user intent to resulting system actions across protocol and administrative boundaries. While traditional workflows support evolving authorization, these transitions are usually explicit and predefined. AI agent systems introduce dynamic, fine-grained authorization changes that arise during execution, driven by agent decisions, delegation, and human interaction. Auditing must therefore capture authorization as a time-evolving state and correlate these transitions across interactions and domains.

Additionally, AI agent behavior may be non-deterministic and not fully predefined, requiring auditing mechanisms to capture execution context and structure as they emerge. Auditing must also distinguish between user, agent, and service identities, and ensure audit data remains interpretable across systems without shared assumptions.

## Scope and Goals

The AUDIT working group will define interoperable mechanisms for auditing and accountability of AI agents and delegated systems across Internet protocols.

The group will focus on architectures, protocol-layer specifications, and data representations that enable systems to record, exchange, and verify audit-relevant information across user-facing and system-facing interactions. This includes capturing delegation chains, evolving authorization state, and enabling consistent interpretation and correlation of audit data across domains.

The working group will not define auditing policies or compliance frameworks, but instead provide the technical building blocks needed to support them.

## Deliverables

The AUDIT working group is expected to produce:

1. Architecture for AI Agent Auditing
An Informational RFC describing roles, trust relationships, and data flows for interoperable auditing, including the relationship between user-facing and system-facing audit signals.

2. Audit Data Models and Semantics
One or more Standards Track RFCs defining data models for representing audit information, including interaction records, agent identity, delegation context, authorization state over time, and action provenance.

3. Protocol Extensions or Profiles
One or more Standards Track RFCs specifying extensions to existing IETF protocols (e.g., HTTP, OAuth, or token formats) to convey audit-related information.

4. Best Practices for Deployment and Operation
An Informational or BCP document providing guidance for secure, interoperable, and privacy-aware auditing, including correlation across interaction types.


> Begin forwarded message:
> 
> From: "Mirja Kuehlewind \(IETF\)" <ietf=40kuehlewind.net@dmarc.ietf.org>
> Subject: [agent2agent] New draft on AI Agent Auditing and proposed BoF/WG charter
> Date: 19. May 2026 at 10:03:46 CEST
> To: agent2agent@ietf.org
> Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
> 
> Hi all,
> 
> We been working on auditing for AI agents and submitted yesterday a new draft that proposes a high-level architecture. Auditing is becoming increasingly important for monitoring long-running workflows, trust, and also due to regulatory requirements. The proposed architecture takes a holistic approach to enable monitoring for the whole agent chain. However, please have a look directly at the draft here:
> 
> https://www.ietf.org/archive/id/draft-kuehlewind-audit-architecture-00.html
> 
> In parallel and given the BoF deadline is already this Friday, we started working on a proposed charter. We believe the proposed work would be in scope for the IETF and would likely need a new working group, therefore we thought it might be useful to provide already a strawman charter to outline the potential scope. Please see here:
> 
> https://github.com/mirjak/draft-audit-architecture/blob/main/audit-charter.md
> 
> We would be very interesting to get some quick feedback (before Friday), especially about:
> 
> 1) Is there general interest in agent auditing work in the IETF? Are there other people who maybe already work on this topic or a planning to?
> 
> 2) Any comments on the proposed scope of the work? Is the scope clear? Is the IETF the right place for this work? Does this need a new working group?
> 
> 2) Any comments on the proposed architecture or any additional work in the space!
> 
> Thanks!
> Mirja & Henk
> _______________________________________________
> agent2agent mailing list -- agent2agent@ietf.org
> To unsubscribe send an email to agent2agent-leave@ietf.org