On Thursday, July 23, the agentproto Birds-of-a-Feather session at IETF 126 in Vienna took up a question that has so far been settled by vendors, not standards bodies: how should AI agents talk to each other across the open internet. The session ran during IETF 126, held 18–24 July 2026, where organizers scheduled five BoF sessions and three touched AI agents directly, with agentproto (Agent Communication Protocols) drawing the most attention from people building multi-agent systems. A BoF isn't a vote and it doesn't produce a standard on the spot. As one write-up on the session put it, the IETF works by rough consensus rather than ballots, and any resulting standard is years away. What the session represents is a shift in framing: agent-to-agent communication is starting to be treated as internet infrastructure, not a proprietary vendor feature bolted onto existing protocols. That framing matters because the last 18 months have produced a scramble of overlapping specs rather than one converged standard. Google's Agent2Agent protocol, transferred to the Linux Foundation in June 2025, has grown past 150 partner organizations and reached version 1.2 with signed agent cards for domain verification, according to reporting on Google Cloud Next 2026. Separately, Anthropic's Model Context Protocol moved to the Agentic AI Foundation under the Linux Foundation and grew to roughly 170 member organizations within four months — more than double CNCF's membership at the same stage of its own life, per a review of MCP's governance history. Each of these efforts solves a piece of the interoperability problem, but none of them carries the weight of an IETF-track specification that browser vendors, ISPs, and regulators would treat as a baseline. That's the gap agentproto is probing. If IETF eventually charters a working group, the deliverable years out would be an RFC-level spec for how agents discover, authenticate to, and hand off tasks between each other independent of which vendor's SDK either side is running. That's a materially higher bar than a corporate-led protocol with partner sign-offs, because IETF specs are meant to work regardless of which company built which agent. For now, nothing has been decided. The session was a temperature check, not a charter. But it's the first time agent-to-agent orchestration has been put in front of the body that standardized TCP/IP, HTTP, and TLS — the layer where interoperability arguments actually get resolved rather than just marketed.