Dear Colleagues, We would like to introduce a freshly-published cluster of five Internet-Drafts that explore the use of the Model Context Protocol (MCP) for AI-driven network equipment management, and to ask for your guidance on the most appropriate IETF homes for this work.
------------------------------------------------- 1. WHAT THE DRAFTS COVER [1] MCP-based Network Measurement Framework (draft-zm-rtgwg-mcp-network-measurement-01) • Use-cases: natural-language perf queries, intelligent fault isolation, topology discovery. [2] MCP for Intent-Based Network Troubleshooting Automation (draft-zm-rtgwg-mcp-troubleshooting-01) • Conversational diagnostics (ping/BGP failure) + Device-to-Device correlation when the controller is unreachable. [3] When NETCONF Is Not Enough (draft-zeng-opsawg-applicability-mcp-a2a-00) • Gap analysis: why NETCONF/SNMP/gNMI cannot satisfy AI-native, multi-agent, DevOps-speed ops. [4] Gap Analysis of Configuration Protocols in LLM-Driven IBN (draft-zeng-opsawg-llm-netconf-gap-00) • Detailed protocol gaps (transactions, YANG discovery, multi-device context, rollback, streaming, security mapping). [5] MCP Extensions for Network Equipment Management (draft-zw-opsawg-mcp-network-mgmt-00) • Minimal, backward-compatible extensions (capability, URI templates, tools, prompts, error codes) so routers/switches can expose CLI/YANG/Syslog over a single MCP channel. ------------------------------------------------- 2. CURRENT SUBMISSION STATUS RTGWG | [1] Measurement, [2] Troubleshooting OPSAWG | [3] NETCONF-insufficient, [4] Gap-Analysis, [5] MCP-extensions ------------------------------------------------- 3. ARE WE IN THE RIGHT PLACE? MCP live in the application/AI space, but our use cases are deeply routing & operations oriented. We therefore need cross-WG coordination that includes (and is not limited to) : • RTGWG – measurement, routing-domain diagnostics • OPSAWG – device config, security, audit, DevOps workflow • ART – semantic protocol design, AI/LLM exposure • NMRG – network-management research, intent validation Your advice on the most suitable mailing-list split (or a possible joint adoption) would be highly appreciated. ------------------------------------------------- 4. COMMENTS / USE-CASES / COLLABORATION This effort is still in its early days — we are actively seeking broad input, additional use-cases, and co-authors to help shape the direction. Any high-level comments on the drafts, or experiences with MCP/A2A in network solutions, are warmly welcome. ------------------------------------------------- 5. HOW TO FIND THE DRAFTS [1] MCP-based Network Measurement Framework: Using Model Context Protocol for Intelligent Network Measurement: https://datatracker.ietf.org/doc/draft-zm-rtgwg-mcp-network-measurement/ [2] Using the Model Context Protocol (MCP) for Intent-Based Network Troubleshooting Automation: https://datatracker.ietf.org/doc/draft-zm-rtgwg-mcp-troubleshooting/ [3] When NETCONF Is Not Enough: Applicability of MCP and A2A for Advanced Network Management Scenarios: https://datatracker.ietf.org/doc/draft-zeng-opsawg-applicability-mcp-a2a/ [4] Gap Analysis of Network Configuration Protocols in LLM-Driven Intent-Based Networking: https://datatracker.ietf.org/doc/draft-zeng-opsawg-llm-netconf-gap/ [5] Model Context Protocol (MCP) Extensions for Network Equipment Management: https://datatracker.ietf.org/doc/draft-zw-opsawg-mcp-network-mgmt/ Thank you for your time Best regards, Guanming Zeng (on behalf of all co-authors) Huawei E-mail: [email protected]<mailto:[email protected]>
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
