AI Agent Protocol Standard Vote Arrives Thursday at IETF 126 in Vienna

The body that produced TLS, DNS, BGP, and QUIC is now four days into its 126th meeting in Vienna — and the most consequential two hours of the week have not happened yet. Wednesday morning, an invited diagnostic session called DMSC finished mapping the problem space for AI agent gateway-mediated collaboration: how agents expose capabilities, forward requests, coordinate across organizational boundaries, and attribute security incidents. Thursday morning, the agentproto Birds-of-a-Feather session opens at 09:00 Central European Summer Time (03:00 ET) to decide whether the Internet Engineering Task Force will charter a Working Group to turn that work into a binding internet standard — one that would carry the same implementation authority as every RFC the IETF has ever produced, as described in the IETF's official BoF session listing. At stake is a question the AI industry has deferred for eighteen months: will inter-domain AI agent communication be standardized by an open, multi-stakeholder internet body, or will Anthropic's Model Context Protocol and Google's Agent2Agent Protocol harden into the de facto baseline by deployment momentum alone — and then be nearly impossible to displace, as happened when the OSI networking stack lost to TCP/IP in the 1980s? Five competing protocols — MCP,…