Orchestration
IETF Weighs Chartering a Working Group for Agent-to-Agent Protocols
For over a year, vendors have shipped competing AI agent communication protocols — Anthropic's MCP, Google's A2A, and others — without any of them clearing the bar of an actual internet standard. That changed this week, or came close to changing. At IETF 126 in Vienna, running July 18–24, the "agentproto" Birds-of-a-Feather session met Thursday to decide whether the IETF should charter a formal Working Group to produce a binding RFC for agent-to-agent and agent-to-tool communication.
The session builds on prior groundwork. The IETF describes it as building on a well-attended IETF 124 side meeting and framework, use-cases, and requirements work led by Jonathan Rosenberg and Cullen Jennings, aiming to identify which building blocks of agent-to-agent and agent-to-tool communication genuinely need standardizing, with a view toward chartering a Working Group.
It's worth being precise about what a BoF actually is: this is not a vote and not a product launch — the IETF works by rough consensus, and any resulting standard is years away. Even in the best case, a BoF is an exploratory step, not a standard; even if a Working Group is chartered, a published RFC is typically two to four years out.
A parallel, non-working-group-forming session called DMSC (Dynamic Multi-Agent Secured Collaboration) met earlier in the week specifically to map the problem space around AI agent gateways — the layer that sits between an orchestrating agent and the downstream agents or tools it invokes, and how those gateways expose capabilities, forward requests, coordinate across organizational boundaries, and attribute security incidents.
The significance isn't that a standard exists yet — it doesn't. It's that agent-to-agent orchestration has moved from being treated as a vendor feature war (MCP vs. A2A vs. whatever comes next) to being treated as internet infrastructure, subject to the same rough-consensus process that produced TLS, DNS, and BGP. If a Working Group is chartered off this session, it sets up a multi-year track toward a vendor-neutral baseline for how agents discover, delegate to, and hand off tasks between each other across organizational boundaries — rather than each platform's proprietary dialect becoming the de facto default by inertia.
Outcomes and materials are being posted to the IETF Datatracker as sessions conclude.