MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

IETF vcon (Virtualized Conversations WG)

IETFchartercore entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Seams: S4

Status

Active working group in the Applications and Real-Time Area, charter-ietf-vcon-01 approved (last updated 2026-03-18); its core draft, draft-ietf-vcon-vcon-core-04 (Standards Track), is dated 2026-09-07. The datatracker lists four charter milestones, dated 2023-12-31 (adopt two drafts) and 2024-06-30 (submit them to the Internet Engineering Steering Group (IESG)), and shows no completion state. The virtual interim of 2026-10-08 (14:00 to 16:00 UTC) was held; the editor's message after it is quoted below. Minutes of that interim: not found in the latest 40 messages of the vcon list (to 2026-10-11), read 2026-10-13; the datatracker interim materials were not read. On 2026-10-13 the datatracker still shows draft-ietf-vcon-vcon-core-04 as the current revision and charter-ietf-vcon-01 as approved. The next virtual interim is on 2026-10-22. Recharter state, 2026-10-13: the datatracker history of the charter shows no revision after charter-ietf-vcon-01 (last action 2026-03-18, a change of Area Director); the recharter text exists only in the repository file changed by PR #37 (merged 2026-10-08) and is not an approved charter. PR #41 on that file is open with no comments. Issue #40 of the core draft repository (opened 2026-10-10 by a participant, no comments) quotes section 2.4 of -04, "Objects that refer to a file which is externally stored from the vCon MUST have the parameters: url, content_hash", and says that references to a streaming-service page or to a recording behind a login cannot be hashed; it reports, as its own measurement on a public dataset, that 4,079 of 8,181 containers fail the schema on that one finding (a figure declared by the issue author, not re-run here).

Relevance

The charter defines vCon as a JSON container "to contain and/or reference conversational data, including call style metadata, recordings, data exchanged or presented in the conversations, conversation analysis, transcriptions, translations and annotations", so it is the IETF format for the record of a conversation.

On 2026-10-06 a participant proposed on the list to recharter the group to finish the core specification and to add an extension for "ai agent interaction record data"; the charter text he points to adds a baseline format and an "AI Agent Extension" for tool call requests and responses, model details, token usage, prompts and reasoning.

The AUDIT effort proposes to treat VCON as its record format for interaction records (see ietf-audit); a related individual draft, draft-rosenberg-cheq-00 (dated 2025-07-24, expiry date 2026-01-25), defines a signed object by which a human confirms an action proposed by an AI agent. On 2026-10-06 the author of this map asked on the list whether the extension's list could name "user instructions and approvals, and references to related records in other protocols"; no reply to that message is among the 6 list messages of 2026-10-06 and 2026-10-07 that were read.

On 2026-10-07 the editor of the core draft reported an updated editors copy with "elevation of the party_history events to the top level Events Object" and a Session concept, and that the examples are not yet updated. The editor of the core draft wrote on 2026-10-08, "After discussion in the vCon Interim WG Meeting today, this PR has been merged in to the Charter in the repo."; pull request #37 shows the merge at 15:53 UTC (merge commit 5bd8dbf, file vcon_charter.md in ietf-wg-vcon/draft-ietf-vcon-vcon-core).

This is a change to the working group's charter file in its repository; no IESG action on a new charter was found. Pull request #39, a typo fix to the charter, was reported merged on the list on 2026-10-08.

Committed next

Boundary

The charter lists as out of scope "Real-time streaming or updating of conversational data" and "Definition of a new object security model."

Author participation

The author of this map wrote on the vcon list on 2026-10-06, asking whether the recharter text could name user instructions and approvals and references to related records, and opened PR #41 on the charter text on 2026-10-11, announced on the list the same day; see Disclosure.

Sources

Overlaps

IETF AUDIT (BoF preparation), Agent Payments Protocol (AP2), Universal Commerce Protocol (UCP), Verifiable Intent

Neighbours in the map

Neighbours of IETF vcon (Virtualized Conversations WG) in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (4)Share a seam (11)IETF AUDIT (BoF preparation) (IETF, core)IETF AUDIT Agent Payments Protocol (AP2) (Industry, core)Agent Payments Protocol Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… Verifiable Intent (Industry, core)Verifiable Intent Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe) (IETF, context)Payment HTTP Authentica… S4 AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… S4 x402 (Linux Foundation, core)x402 S4 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S4 EMILIA Protocol (individual drafts and open-source gate) (Independent, context)EMILIA Protocol S4 Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… S4 EMV Agentic Payments Framework for Specifications (draft for public feedback) (Industry, core)EMV Agentic Payments Fr… S4 FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… S4 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S4 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S4 Shopify, MCP surfaces for buyer agents, developers and merchants (Industry, context)Shopify S4 IETF vcon

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: issue #40 and PR #41 of the core draft repository (state and text), the history page of the charter, the datatracker pages of the group, its charter, draft-ietf-vcon-vcon-core and draft-rosenberg-vcon-restructure, pull request #37, and the subjects and dates of the latest 40 messages of the vcon list (to 2026-10-11).
Not read
The messages of the vcon list before 2026-09-01, the minutes, and the completion state of the milestones.
Not found
Not found in the 35 vcon list messages (2026-09-01 to 2026-10-06) and in the texts of draft-ietf-vcon-vcon-core-04, draft-ietf-vcon-overview-02, draft-rosenberg-vcon-restructure-00, draft-howe-vcon-agent-session-00 and draft-rosenberg-cheq-00, 2026-10-06: UCP, ACP, AP2, x402, Verifiable Intent, Visa. Not found in the files, issues and pull requests of the repositories of UCP, ACP, AP2, x402, Verifiable Intent and Visa TAP, 2026-10-06: vCon or "virtualized conversation". Not found in charter-ietf-vcon-01, 2026-10-06: commerce, payment, purchase, agent.

Open proposals

ProposalAuthorDateStateLink
Recharter: finish the core specification, then an extension for AI agent interaction record data (message and pull request #37, merged on 2026-10-08 into the charter file of the repository; the interim of 2026-10-08 discussed it, a chair's reminder of 2026-10-06 listing "discuss proposed charter updates").Jonathan Rosenberg2026-10-06mergedhttps://github.com/ietf-wg-vcon/draft-ietf-vcon-vcon-core/pull/37
Restructure the format with a session concept and an events object to represent AI agent use cases (draft-rosenberg-vcon-restructure-00; on 2026-10-13 the datatracker still shows -00 as the current revision, last updated 2026-09-11; the editors copy of the core draft of 2026-10-07 reports the elevation of party_history events to a top level Events Object and a Session concept, which are parts of this proposal).Jonathan Rosenberg2026-09-11openhttps://mailarchive.ietf.org/arch/msg/vcon/pSs7uBFPNQI5ZWd0h3zM60F5E0Q/