Using the Model Context Protocol (MCP) for Intent-Based Network Troubleshooting Automation
draft-zm-rtgwg-mcp-troubleshooting-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Guanming Zeng , Jianwei Mao , Bing Liu , Nan Geng , Xiaotong Shang , Qiangzhou Gao , Zhenbin Li | ||
| Last updated | 2026-05-06 (Latest revision 2025-11-02) | ||
| Replaces | draft-zeng-mcp-troubleshooting | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Model Context Protocol (MCP) is an open standard that enables Large Language Model (LLM) applications to seamlessly integrate with external data sources and tools by exposing Resources, Prompts and Tools in a JSON-RPC 2.0 transport. This document describes a mapping of MCP roles, primitives and security model to the network management domain so that network devices act as MCP servers and network controllers act as MCP clients. This document also extends the model to Device-to-Device (D2D) collaboration, allowing network elements to perform distributed fault correlation when the controller is unreachable or when real-time cross-device data is required. The goal is to provide an intent-based, conversational and secure approach for automated network troubleshooting, configuration validation, and closed-loop remediation without inventing new protocols or device agents.
Authors
Guanming Zeng
Jianwei Mao
Bing Liu
Nan Geng
Xiaotong Shang
Qiangzhou Gao
Zhenbin Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)