On July 23, the IETF held its first Birds-of-a-Feather session dedicated to agent communication protocols, a step that treats how AI agents talk to each other as a networking-standards question rather than a vendor feature. The session, called agentproto, ran during IETF 126 in Vienna. As one industry write-up put it, the meeting brought together people asking whether protocols like Anthropic's MCP and Google's A2A should move toward a formal RFC — the bar that, as the piece notes, none of the competing agent protocols has cleared despite more than a year of vendor shipping. The IETF 126 meeting ran July 18–24 in Vienna, and among five Birds-of-a-Feather sessions scheduled that week, three touched AI agents directly, with agentproto drawing the most attention from people building systems that span multiple organizations. This matters for orchestration specifically because a BoF is the earliest formal step in IETF process — a venue for gauging whether there's enough community interest and technical clarity to charter a working group. It is explicitly not a vote and not a product announcement. Google donated A2A to the Linux Foundation in June 2025, with AWS, Cisco, Microsoft, Salesforce, SAP, and ServiceNow as founding members, and Anthropic separately donated MCP to a foundation structure — moves that already signaled vendors wanted shared governance rather than one company controlling the spec. What the IETF session adds is a path toward the kind of interoperability guarantee that only comes from a body without a commercial stake in any single protocol: two agents built by different vendors, on different platforms, being able to hand off a task to each other with a standardized handshake, the same way SMTP lets any mail server talk to any other. The realistic timeline is long. A BoF that goes well typically leads to a chartered working group months later, and a published RFC is commonly years out even after that. But the shift in framing is real: multi-agent coordination across organizational boundaries is now sitting on the same standards track as HTTP, DNS, and email, rather than being settled ad hoc between whichever vendors happen to dominate a given deployment. For anyone building systems where agents from different companies need to coordinate tasks, that's the detail worth watching — not which protocol wins, but whether the industry accepts a neutral body as the referee. For now, the practical implication is narrow: teams building cross-organization agent handoffs should track the agentproto mailing list rather than betting infrastructure decisions on any single vendor's protocol being the eventual standard.