The Imperative & The Important vCon edition
Two lenses, as always.
The Imperative: what’s happening now that demands a reaction.
The Important: what stays true after the headlines fade.
Today, both lenses point at the same object: the vCon.
First, the acronym
A vCon (Virtualized Conversation) is a standardized JSON container for everything related to a human conversation.
Think vCard, but for the conversation itself.
One signed file carries the parties, the dialog (audio, video, text), the analysis (transcripts, sentiment, AI output), the attachments, and the consent.
It is being standardized right now in the IETF (Internet Engineering Task Force) Virtualized Conversations working group.
The Imperative
The standard is landing.
The core JSON specification (draft-ietf-vcon-vcon-core) hit revision 03 in June, now 130 pages, on the Standards Track. The working group also carries an overview, a privacy primer for developers, and a contact center extension. Industry watchers expect 2026 to be the ratification year.
Business impact: if your contact center, UCaaS platform, or voice AI vendor stores conversations in a proprietary blob, you are one standard away from being asked why.
The extension ecosystem is growing fast.
Individual drafts now cover SIP signaling with STIR/SHAKEN (Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs) data, GDPR lawful basis, consent attachments, generation provenance, and lifecycle management using SCITT (Supply Chain Integrity, Transparency and Trust) — an append-only ledger recording every creation, share, analysis, and deletion.
Business impact: the vCon is quietly becoming a chain-of-custody instrument for conversations. Legal, compliance, and security teams should care as much as the CX team.
AI is consuming — and generating — your conversations.
Every copilot, voice agent, and analytics engine in your stack is ingesting conversation data and producing derivatives from it. Without a standard record that carries consent and provenance alongside the content, nobody can answer where a given insight came from, whether you had the right to use the underlying conversation, or which outputs trace back to which humans.
Business impact: the question is no longer “do we record calls?” It is “can we prove what happened to every conversation after it ended?”
The Important
We have seen this movie in another domain.
In post-quantum cryptography, the enduring discipline is discovery, agility, and governance: inventory what you have, be able to change it, and assign ownership.
Conversations are now assets that demand the same discipline.
Discovery: where do your conversation records live, and in what format?
Agility: could you re-sign, re-verify, or redact them if consent is withdrawn or an algorithm is broken?
Governance: who owns the conversation record after the call ends?
And one more bridge worth naming: vCons rely on digital signatures to prove integrity over decades-long retention windows. Signatures made today with classical algorithms will need quantum-safe successors. Harvest-now-decrypt-later applies to conversation archives too.
A standard container makes all of that possible. A proprietary blob makes none of it possible.
Three questions to close
Do you know where every recorded conversation in your business lives today — and could you produce one, with its consent and chain of custody, on demand?
If a customer withdrew consent tomorrow, could you find and redact every copy — including the AI analysis derived from it?
Who in your organization owns conversation records as an asset class — CX, legal, security, or nobody?
Sources
IETF Virtualized Conversations working group documents: https://datatracker.ietf.org/group/vcon/documents/
vCon Overview (draft-ietf-vcon-overview-01): https://datatracker.ietf.org/doc/html/draft-ietf-vcon-overview-01
vCon core JSON format (draft-ietf-vcon-vcon-core): https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/
vCon Lifecycle Management using SCITT: https://datatracker.ietf.org/doc/html/draft-howe-vcon-lifecycle-01
vCon SIP Signaling and STIR/SHAKEN extension: https://datatracker.ietf.org/doc/draft-howe-vcon-sip-signaling/
A vCon Primer (Conserver.io): https://www.conserver.io/vcons/a-vcon-primer
The State of vCons 2026 (TeleCloud): https://telecloud.net/blog/state-of-vcons-2026-ai-conversation-standard
Voice AI Conversation Records (WebRTC.ventures): https://webrtc.ventures/2026/06/voice-ai-conversation-records-vcon-production-architecture/
#vCon #ConversationalAI #IETF #Compliance #CyberSecurity #DataGovernance #TheImperativeAndTheImportant