<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Protocols on Boteng Yao</title>
    <link>https://botengyao.github.io/tags/protocols/</link>
    <description>Recent content in Protocols on Boteng Yao</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 12:00:00 +0800</lastBuildDate>
    <atom:link href="https://botengyao.github.io/tags/protocols/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Envoy AI Protocol Manager by Example</title>
      <link>https://botengyao.github.io/posts/envoy-ai-protocol-manager-examples/</link>
      <pubDate>Mon, 26 Oct 2026 12:00:00 +0800</pubDate>
      <guid>https://botengyao.github.io/posts/envoy-ai-protocol-manager-examples/</guid>
      <description>How Envoy&amp;rsquo;s AI Protocol Manager handles LLM traffic today, and a set of tested configs: observing native APIs, translating between OpenAI, Claude and Gemini (Vertex AI included), retries and failover across APIs, a forward-proxy egress, and model routing with ext_proc.</description>
    </item>
    <item>
      <title>Stateless MCP in Envoy 1.40</title>
      <link>https://botengyao.github.io/posts/stateless-mcp-envoy/</link>
      <pubDate>Tue, 20 Oct 2026 12:00:00 +0800</pubDate>
      <guid>https://botengyao.github.io/posts/stateless-mcp-envoy/</guid>
      <description>MCP&amp;rsquo;s 2026-07-28 revision makes the protocol stateless, so MCP traffic now looks a lot like ordinary HTTP. Envoy 1.40 builds on that: route MCP requests by tool name, stop malformed or spoofed requests at the proxy, control who can call which tool, and turn any REST API into an MCP server using only config.</description>
    </item>
  </channel>
</rss>
