# llm_cache

draft_name: draft-zeng-nmrg-mcp-usecases-requirements
prompt_hash: f98d5592a542bd43
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:26:49.271454+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zeng-nmrg-mcp-usecases-requirements | MCP for Network Management: Problem Statement, Use Cases, and Requirements | 6pg
Abstract: The emergence of large language models (LLMs) and AI agents is
   reshaping how network operators interact with infrastructure.
   However, current network management systems lack a standardized,
   secure, and intent-driven interface that enables AI agents to
   discover, invoke, and reason over network capabilities.  This
   document presents a problem statement for integrating the Model
   Context Protocol (MCP) into network management, outlines key use
   cases—including troubleshooting, measurement, security, and
   optimization—and specifies functional, security, and interoperability
   requirements for MCP-based network management architectures.





Network Working Group                                            G. Zeng
Internet-Draft                                                    Huawei
Intended status: Informational                             February 2026
Expires: 18 August 2026


     MCP for Network Management: Problem Statement, Use Cases, and
                              Requirements
              draft-zeng-nmrg-mcp-usecases-requirements-00

Abstract

   The emergence of large language models (LLMs) and AI agents is
   reshaping how network operators interact with infrastructure.
   However, current network management systems lack a standardized,
   secure, and intent-driven interface that enables AI agents to
   discover, invoke, and reason over network capabilities.  This
   document presents a problem statement for integrating the Model
   Context Protocol (MCP) into network management, outlines key use
   cases—including troubleshooting, measurement, security, and
   optimization—and specifies functional, security, and interoperability
   requirements for MCP-based network management architectures.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 5 August 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.



Zeng                     Expires 18 August 2026                 [Page 1]

Internet-Draft  MCP for Network Management: Problem Stat   February 2026


   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Troubleshooting . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Network Measurement . . .

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "MCP Network Interface",
    "description": "A standardized, secure, and intent-driven interface that enables AI agents to discover, invoke, and reason over network capabilities using the Model Context Protocol. This interface bridges AI agents with network management systems.",
    "type": "protocol"
  },
  {
    "title": "AI Agent Network Discovery",
    "description": "A mechanism allowing AI agents to automatically discover available network management capabilities and services through MCP. Enables dynamic capability enumeration for network operations.",
    "type": "mechanism"
  },
  {
    "title": "Intent-Driven Network Management",
    "description": "An approach where AI agents can express high-level network intents through MCP rather than low-level commands. The system translates intents into specific network operations.",
    "type": "pattern"
  },
  {
    "title": "MCP Network Security Model",
    "description": "Security requirements and mechanisms for protecting MCP-based interactions between AI agents and network infrastructure. Includes authentication, authorization, and secure communication protocols.",
    "type": "requirement"
  },
  {
    "title": "AI-Driven Network Troubleshooting",
    "description": "Use case where AI agents leverage MCP to perform automated network troubleshooting by accessing diagnostic tools and reasoning over network state. Enables intelligent fault isolation and resolution.",
    "type": "mechanism"
  }
]


draft_name: draft-zeng-opsawg-applicability-mcp-a2a
prompt_hash: 38ae9d12b0b54c54
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:26:57.447963+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zeng-opsawg-applicability-mcp-a2a | When NETCONF Is Not Enough: Applicability of MCP and A2A for Advanced Network Management Scenarios | 12pg
Abstract: NETCONF provides robust configuration transactions and YANG-based
   data models, but falls short in scenarios requiring AI-driven
   semantic translation, long-lived cross-domain orchestration, multi-
   agent consensus, rapid DevOps iteration, or delivery of large non-
   configuration artifacts.  This document systematically analyzes the
   functional gaps and presents Model Context Protocol (MCP) and Agent-
   to-Agent (A2A) as complementary solutions.  Implementation guidance
   and coexistence models are also provided.





Network Working Group                                            G. Zeng
Internet-Draft                                                    J. Mao
Intended status: Standards Track                                  B. Liu
Expires: 6 May 2026                                              N. Geng
                                                                X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                                  Huawei
                                                         2 November 2025


 When NETCONF Is Not Enough: Applicability of MCP and A2A for Advanced
                      Network Management Scenarios
               draft-zeng-opsawg-applicability-mcp-a2a-00

Abstract

   NETCONF provides robust configuration transactions and YANG-based
   data models, but falls short in scenarios requiring AI-driven
   semantic translation, long-lived cross-domain orchestration, multi-
   agent consensus, rapid DevOps iteration, or delivery of large non-
   configuration artifacts.  This document systematically analyzes the
   functional gaps and presents Model Context Protocol (MCP) and Agent-
   to-Agent (A2A) as complementary solutions.  Implementation guidance
   and coexistence models are also provided.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.




Zeng, et al.               Expires 6 May 2026                   [Page 1]

Internet-Draft                 MCP-A2A-Gap                 November 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . .

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Model Context Protocol (MCP)",
    "description": "A protocol designed to handle AI-driven semantic translation and context sharing for network management scenarios where YANG models are insufficient. Provides mechanisms for managing contextual information across network management operations.",
    "type": "protocol"
  },
  {
    "title": "Agent-to-Agent (A2A) Communication",
    "description": "A communication mechanism enabling multi-agent consensus and coordination for cross-domain network orchestration. Supports long-lived interactions between autonomous network management agents.",
    "type": "mechanism"
  },
  {
    "title": "NETCONF Gap Analysis Framework",
    "description": "A systematic analysis methodology identifying specific functional limitations of NETCONF in advanced scenarios. Categorizes gaps into AI-driven translation, cross-domain orchestration, multi-agent consensus, DevOps iteration, and large artifact delivery.",
    "type": "pattern"
  },
  {
    "title": "Large Non-Configuration Artifact Delivery",
    "description": "A mechanism for transferring substantial data objects that fall outside traditional configuration management scope. Addresses NETCONF limitations in handling large payloads beyond configuration data.",
    "type": "mechanism"
  },
  {
    "title": "Protocol Coexistence Model",
    "description": "An architectural pattern defining how MCP and A2A can operate alongside existing NETCONF deployments. Provides implementation guidance for hybrid network management environments.",
    "type": "architecture"
  }
]


draft_name: draft-zeng-opsawg-llm-netconf-gap
prompt_hash: 1ba3a0e8034e6b9a
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:05.695116+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zeng-opsawg-llm-netconf-gap | Gap Analysis of Network Configuration Protocols in LLM-Driven Intent-Based Networking | 9pg
Abstract: Large Language Models (LLMs) are entering network operations through
   natural-language intent interfaces.  Existing south-bound protocols
   (NETCONF, RESTCONF, gNMI, MCP, A2A) were not designed for
   conversational, semantically-rich, multi-agent orchestration.  This
   document provides a systematic gap analysis and identifies extension
   points for each protocol to meet intent-based networking
   requirements.





Network Working Group                                            G. Zeng
Internet-Draft                                                    J. Mao
Intended status: Informational                                    B. Liu
Expires: 6 May 2026                                              N. Geng
                                                                X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                                  Huawei
                                                         2 November 2025


 Gap Analysis of Network Configuration Protocols in LLM-Driven Intent-
                            Based Networking
                  draft-zeng-opsawg-llm-netconf-gap-00

Abstract

   Large Language Models (LLMs) are entering network operations through
   natural-language intent interfaces.  Existing south-bound protocols
   (NETCONF, RESTCONF, gNMI, MCP, A2A) were not designed for
   conversational, semantically-rich, multi-agent orchestration.  This
   document provides a systematic gap analysis and identifies extension
   points for each protocol to meet intent-based networking
   requirements.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.





Zeng, et al.               Expires 6 May 2026                   [Page 1]

Internet-Draft               LLM Netconf Gap               November 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  G

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Natural Language Intent Interface Gap",
    "description": "Existing southbound protocols (NETCONF, RESTCONF, gNMI, MCP, A2A) lack native support for processing natural language intents from LLMs. Current protocols require structured data formats that don't align with conversational AI outputs.",
    "type": "requirement"
  },
  {
    "title": "Multi-Agent Orchestration Extension",
    "description": "Traditional network configuration protocols need extensions to support coordination between multiple LLM agents working simultaneously on network operations. Current single-session models are insufficient for distributed AI-driven management.",
    "type": "extension"
  },
  {
    "title": "Semantic Context Preservation Mechanism",
    "description": "Network protocols require mechanisms to maintain semantic context across multiple configuration transactions when driven by LLM conversations. Current stateless approaches lose conversational context needed for intent interpretation.",
    "type": "mechanism"
  },
  {
    "title": "Intent-to-Configuration Translation Protocol",
    "description": "A systematic protocol extension framework is needed to bridge the gap between high-level natural language intents and low-level device configurations. This would standardize how LLM outputs map to existing protocol operations.",
    "type": "protocol"
  },
  {
    "title": "Conversational State Management Pattern",
    "description": "Network management protocols need patterns to handle conversational state across multiple interactions, enabling LLMs to reference previous configurations and maintain dialogue context during network operations.",
    "type": "pattern"
  }
]


draft_name: draft-zhang-agent-gap-network
prompt_hash: bc8a780f77f40578
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:13.097247+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-agent-gap-network | Problem Statement and Gap Analysis for Agent-enabled Mobile Core Network | 6pg
Abstract: This document provides the problem statement and gap analysis of
   agent-enabled mobile core network.





Network Working Group                                      Y. Zhang, Ed.
Internet-Draft                                             X. Zhang, Ed.
Intended status: Standards Track                             Y. Yue, Ed.
Expires: 8 January 2026                                     China Unicom
                                                             7 July 2025


Problem Statement and Gap Analysis for Agent-enabled Mobile Core Network
                    draft-zhang-agent-gap-network-00

Abstract

   This document provides the problem statement and gap analysis of
   agent-enabled mobile core network.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 8 January 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.






Zhang, et al.            Expires 8 January 2026                 [Page 1]

Internet-Draft  Problem and Gap for Agent-enabled Networ       July 2025


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Changes in Interaction Content  . . . . . . . . . . . . .   3
     3.2.  Changes in Interaction Entity . . . . . . . . . . . . . .   3
     3.3.  Changes in Interaction Protocol . . . . . . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Network for Agent Communication . . . . . . . . . . . . .   4
     4.2.  Agent-based Network Enhancement . . . . . . . . . . . . .   4
   5.  Gap Analysis  . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  GAP analysis of service capabilities  . . . . . . . . . .   4
 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent-enabled Mobile Core Network Architecture",
    "description": "A mobile core network architecture that integrates AI agents to enhance network operations and service delivery. This represents a fundamental shift from traditional mobile core designs.",
    "type": "architecture"
  },
  {
    "title": "Network for Agent Communication",
    "description": "Network infrastructure specifically designed to support communication between AI agents in mobile core environments. Addresses the unique requirements of agent-to-agent interactions.",
    "type": "pattern"
  },
  {
    "title": "Agent-based Network Enhancement",
    "description": "Use of AI agents to improve existing network functions and capabilities in mobile core networks. Focuses on leveraging agent intelligence for network optimization.",
    "type": "mechanism"
  },
  {
    "title": "Changes in Interaction Content Requirements",
    "description": "Modified data exchange formats and content types needed when agents participate in mobile network operations. Addresses what information agents need to share.",
    "type": "requirement"
  },
  {
    "title": "Changes in Interaction Entity Framework",
    "description": "New entity models and roles when AI agents become participants in mobile core network operations. Defines how agents integrate with existing network entities.",
    "type": "architecture"
  },
  {
    "title": "Changes in Interaction Protocol",
    "description": "Protocol modifications or new protocols needed to support agent interactions in mobile core networks. Addresses how agents communicate with network components.",
    "type": "protocol"
  }
]


draft_name: draft-zhang-aiproto-svcb-mapping-for-agents
prompt_hash: c6ec753d0b15a0a4
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:20.342362+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-aiproto-svcb-mapping-for-agents | Service Binding Mapping for Agents | 6pg
Abstract: With the continuous introduction of intelligent agent communication
   and interaction protocols, the current DNS cannot adequately meet the
   requirements for agent service resolution.  This document defines a
   new DNS resource record type, AGENT, which is a SVCB-compatible RR
   type, and specifies the mapping specifications.





Network Working Group                                           M. Zhang
Internet-Draft                                                  Z.W. Yan
Intended status: Informational                                 K.J. Dong
Expires: 6 July 2026                                             H.T. Li
                                                                   CNNIC
                                                          2 January 2026


                   Service Binding Mapping for Agents
             draft-zhang-aiproto-svcb-mapping-for-agents-01

Abstract

   With the continuous introduction of intelligent agent communication
   and interaction protocols, the current DNS cannot adequately meet the
   requirements for agent service resolution.  This document defines a
   new DNS resource record type, AGENT, which is a SVCB-compatible RR
   type, and specifies the mapping specifications.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 July 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Zhang, et al.              Expires 6 July 2026                  [Page 1]

Internet-Draft     Service Binding Mapping for Agents       January 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Basic requirements  . . . . . . . . . . . . . . . . . . . . .   3
   4.  SvcParamKeys defined by SVCB  . . . . . . . . . . . . . . . .   3
     4.1.  "alpn"  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  "port"  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.3.  "ipv4hint" and "ipv6hint" . . . . . . . . . . . . . . . .   4


Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "AGENT DNS Resource Record",
    "description": "A new DNS resource record type called AGENT that is SVCB-compatible for intelligent agent service resolution. This extends DNS capabilities beyond traditional web services to support agent-specific discovery.",
    "type": "extension"
  },
  {
    "title": "SVCB-Compatible Agent Mapping",
    "description": "Extension of the Service Binding (SVCB) record format to support agent communication protocols. Leverages existing SVCB infrastructure while adding agent-specific service parameters.",
    "type": "mechanism"
  },
  {
    "title": "Agent-Specific ALPN Support",
    "description": "Application of Application Layer Protocol Negotiation (ALPN) parameter within AGENT records to identify agent communication protocols. Enables protocol negotiation for intelligent agent interactions.",
    "type": "mechanism"
  },
  {
    "title": "Agent Service Port Mapping",
    "description": "Port parameter specification for AGENT records to direct agent communications to specific service endpoints. Allows agents to connect to designated ports for their protocols.",
    "type": "mechanism"
  },
  {
    "title": "Agent IP Hint System",
    "description": "IPv4 and IPv6 hint parameters for AGENT records to provide connection optimization for agent services. Reduces DNS lookup overhead for agent-to-agent communications.",
    "type": "mechanism"
  }
]


draft_name: draft-zhang-dmsc-ioa-semantic-interaction
prompt_hash: 45cef0ede1f06e17
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:28.090096+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-dmsc-ioa-semantic-interaction | Ontology-based Semantic Interaction for Internet of Agents | 19pg
Abstract: This document specifies a normative semantic layer for agent-to-agent
   interaction in the Internet of Agents (IoA).  The semantic layer
   provides a common ontology model and a JSON-LD serialization profile
   (RECOMMENDED), while allowing other RDF serializations for expressing
   capabilities, intents, tasks, and context.  The document defines
   required classes and properties, a negotiation procedure, and
   alignment rules for heterogeneous ontologies.  This layer is designed
   to be used by interaction and discovery protocols but does not define
   transport, session, or security protocols.  It enables deterministic
   semantic interoperability across domains.





Network Working Group                                           L. Zhang
Internet-Draft                                                   S. Wang
Intended status: Standards Track                                   Y. Li
Expires: 31 August 2026                                          H. Yang
                                      AsiaInfo Technologies (China) Inc.
                                                        27 February 2026


       Ontology-based Semantic Interaction for Internet of Agents
              draft-zhang-dmsc-ioa-semantic-interaction-01

Abstract

   This document specifies a normative semantic layer for agent-to-agent
   interaction in the Internet of Agents (IoA).  The semantic layer
   provides a common ontology model and a JSON-LD serialization profile
   (RECOMMENDED), while allowing other RDF serializations for expressing
   capabilities, intents, tasks, and context.  The document defines
   required classes and properties, a negotiation procedure, and
   alignment rules for heterogeneous ontologies.  This layer is designed
   to be used by interaction and discovery protocols but does not define
   transport, session, or security protocols.  It enables deterministic
   semantic interoperability across domains.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 31 August 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.






Zhang, et al.            Expires 31 August 2026                 [Page 1]

Internet-Draft        Semantic Interaction for IoA         February 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   3.  Sco

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "IoA Common Ontology Model",
    "description": "A standardized ontology framework defining required classes and properties for expressing agent capabilities, intents, tasks, and context in Internet of Agents. Uses RDF-based semantic modeling to enable interoperability across heterogeneous agent systems.",
    "type": "architecture"
  },
  {
    "title": "JSON-LD Serialization Profile",
    "description": "A recommended JSON-LD serialization format for the IoA semantic layer, providing a web-friendly representation while maintaining RDF compatibility. Allows other RDF serializations as alternatives for expressing semantic information.",
    "type": "protocol"
  },
  {
    "title": "Semantic Negotiation Procedure",
    "description": "A defined process for agents to negotiate semantic understanding and establish common interpretation of ontological concepts during interaction. Enables dynamic semantic agreement between heterogeneous agents.",
    "type": "mechanism"
  },
  {
    "title": "Heterogeneous Ontology Alignment Rules",
    "description": "Standardized rules and procedures for aligning different ontologies used by various agents in the IoA ecosystem. Provides deterministic semantic interoperability across different domains and agent implementations.",
    "type": "mechanism"
  },
  {
    "title": "Transport-Agnostic Semantic Layer",
    "description": "A semantic interaction layer designed to work independently of transport, session, or security protocols. Provides semantic interoperability services to higher-level interaction and discovery protocols.",
    "type": "architecture"
  }
]


draft_name: draft-zhang-dmsc-mas-communication
prompt_hash: d8b8d65167e88e93
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:36.071549+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-dmsc-mas-communication | Security Analysis of Multi-agents Secured Communication and Limitations of Existing Protocols | 8pg
Abstract: Multi-agents systems (MAS) increasingly cooperate through workflow,
   orchestrated, and mesh communication patterns.  While existing
   Internet protocols provide confidentiality and endpoint
   authentication, they were not designed for agent-native semantics
   such as dynamic identity, computation-bounded requests, context
   integrity, and intermediary trust.  This document analyzes security
   risks in agent communication and identifies limitations in widely
   deployed protocols (TLS, HTTP, MQTT,A2A and etc.) and developer
   framework (AutoGen and etc.).  This document intend to establish a
   common problem statement and gap analysis to inform future IETF
   standardization.





DMSC Working Group                                              H. Zhang
Internet-Draft                                             China Telecom
Intended status: Standards Track                         16 January 2026
Expires: 20 July 2026


Security Analysis of Multi-agents Secured Communication and Limitations
                         of Existing Protocols
                 draft-zhang-dmsc-mas-communication-00

Abstract

   Multi-agents systems (MAS) increasingly cooperate through workflow,
   orchestrated, and mesh communication patterns.  While existing
   Internet protocols provide confidentiality and endpoint
   authentication, they were not designed for agent-native semantics
   such as dynamic identity, computation-bounded requests, context
   integrity, and intermediary trust.  This document analyzes security
   risks in agent communication and identifies limitations in widely
   deployed protocols (TLS, HTTP, MQTT,A2A and etc.) and developer
   framework (AutoGen and etc.).  This document intend to establish a
   common problem statement and gap analysis to inform future IETF
   standardization.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 20 July 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.






Zhang                     Expires 20 July 2026                  [Page 1]

Internet-Draft  Security Analysis of Multi-agents Secure    January 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Core Communication Security Risks in MAS  . . . . . . . . . .   3


Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent-native semantics",
    "description": "Security requirements specific to multi-agent systems including dynamic identity management, computation-bounded requests, context integrity, and intermediary trust. These differ from traditional endpoint-to-endpoint security models.",
    "type": "requirement"
  },
  {
    "title": "Multi-agent communication patterns",
    "description": "Three distinct communication patterns for agent cooperation: workflow, orchestrated, and mesh communication patterns. Each pattern presents different security challenges and trust models.",
    "type": "architecture"
  },
  {
    "title": "Dynamic identity management",
    "description": "Identity mechanisms that can change dynamically during agent interactions, unlike static endpoint authentication in traditional protocols. Required for agents that may assume different roles or capabilities during execution.",
    "type": "mechanism"
  },
  {
    "title": "Computation-bounded requests",
    "description": "Security framework for requests that are limited by computational resources or time constraints. Addresses scenarios where agents have processing limitations or operate under time-sensitive conditions.",
    "type": "mechanism"
  },
  {
    "title": "Context integrity for agents",
    "description": "Mechanism to ensure that communication context and state are preserved and verified across multi-agent interactions. Goes beyond message integrity to include conversation and workflow state.",
    "type": "mechanism"
  },
  {
    "title": "Intermediary trust model",
    "description": "Trust framework for scenarios where agents communicate through intermediaries, requiring verification of intermediate nodes rather than just endpoints. Extends traditional end-to-end trust models.",
    "type": "architecture"
  }
]


draft_name: draft-zhang-rtgwg-ai-agents-measurement
prompt_hash: 922f3ffea536d417
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:41.673935+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-rtgwg-ai-agents-measurement | Use Cases and Requirements of Communication Protocol for Measurement Agents on Network Devices | 7pg
Abstract: This document focuses on the use cases and requirements of
   communication protocols for measurement agents on network devices.





rtgwg                                                           R. Zhang
Internet-Draft                                                    J. Mao
Intended status: Informational                                    B. Liu
Expires: 7 May 2026                                              N. Geng
                                                                X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                                  Huawei
                                                         3 November 2025


  Use Cases and Requirements of Communication Protocol for Measurement
                       Agents on Network Devices
               draft-zhang-rtgwg-ai-agents-measurement-00

Abstract

   This document focuses on the use cases and requirements of
   communication protocols for measurement agents on network devices.

About This Document

   This note is to be removed before publishing as an RFC.

   The latest revision of this draft can be found at
   https://example.com/LATEST.  Status information for this document may
   be found at https://datatracker.ietf.org/doc/draft-zhang-rtgwg-ai-
   agents-measurement/.

   Discussion of this document takes place on the rtgwg Working Group
   mailing list (mailto:WG@example.com), which is archived at
   https://example.com/WG.

   Source for this draft and an issue tracker can be found at
   https://github.com/USER/REPO.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.






Zhang, et al.              Expires 7 May 2026                   [Page 1]

Internet-Draft  Use Cases and Requirements of Communicat   November 2025


   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 7 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the T

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Measurement Agent Communication Protocol",
    "description": "A specialized communication protocol designed for measurement agents deployed on network devices. The protocol enables coordination and data exchange between distributed measurement agents.",
    "type": "protocol"
  },
  {
    "title": "Network Device Measurement Agents",
    "description": "Software agents deployed on network devices to perform measurement functions and coordinate with other agents. These agents require specific communication capabilities for effective operation.",
    "type": "architecture"
  },
  {
    "title": "Agent-to-Agent Coordination Pattern",
    "description": "A communication pattern that allows measurement agents to coordinate their activities across multiple network devices. This enables distributed measurement scenarios and data correlation.",
    "type": "pattern"
  },
  {
    "title": "Measurement Data Exchange Mechanism",
    "description": "A mechanism for measurement agents to exchange collected data and measurement results with each other. This supports collaborative measurement and analysis across the network.",
    "type": "mechanism"
  }
]


draft_name: draft-zhang-rtgwg-ai-agents-troubleshooting
prompt_hash: b1f9a6e805e0a8f4
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:48.014427+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-rtgwg-ai-agents-troubleshooting | Use Cases and Requirements of Communication Protocol for Troubleshooting Agents on Network Devices | 14pg
Abstract: This document focuses on the use cases and requirements of
   communication protocols for troubleshooting agents on network
   devices.





rtgwg                                                           R. Zhang
Internet-Draft                                                    J. Mao
Intended status: Informational                                    B. Liu
Expires: 7 May 2026                                              N. Geng
                                                                X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                                  Huawei
                                                         3 November 2025


Use Cases and Requirements of Communication Protocol for Troubleshooting
                       Agents on Network Devices
             draft-zhang-rtgwg-ai-agents-troubleshooting-00

Abstract

   This document focuses on the use cases and requirements of
   communication protocols for troubleshooting agents on network
   devices.

About This Document

   This note is to be removed before publishing as an RFC.

   The latest revision of this draft can be found at
   https://example.com/LATEST.  Status information for this document may
   be found at https://datatracker.ietf.org/doc/draft-zhang-rtgwg-ai-
   agents-troubleshooting/.

   Discussion of this document takes place on the rtgwg Working Group
   mailing list (mailto:WG@example.com), which is archived at
   https://example.com/WG.

   Source for this draft and an issue tracker can be found at
   https://github.com/USER/REPO.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.





Zhang, et al.              Expires 7 May 2026                   [Page 1]

Internet-Draft  Use Cases and Requirements of Communicat   November 2025


   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 7 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Sectio

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Troubleshooting Agent Communication Protocol",
    "description": "A specialized communication protocol designed for AI-based troubleshooting agents deployed on network devices. The protocol enables coordination and information exchange between distributed troubleshooting agents.",
    "type": "protocol"
  },
  {
    "title": "Network Device Agent Architecture",
    "description": "An architecture for deploying AI troubleshooting agents directly on network devices to perform autonomous fault detection and diagnosis. Agents operate locally while coordinating with other devices through specialized protocols.",
    "type": "architecture"
  },
  {
    "title": "Agent-to-Agent Coordination Mechanism",
    "description": "A mechanism enabling multiple troubleshooting agents across different network devices to share diagnostic information and coordinate troubleshooting activities. Supports distributed problem-solving across network infrastructure.",
    "type": "mechanism"
  },
  {
    "title": "Distributed Network Troubleshooting Pattern",
    "description": "A pattern where troubleshooting intelligence is distributed across network devices rather than centralized. Each device runs local agents that communicate to provide network-wide diagnostic capabilities.",
    "type": "pattern"
  }
]


draft_name: draft-zhang-rtgwg-llmmoe-multicast
prompt_hash: 44f5eacccaadd602
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:27:56.349037+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-rtgwg-llmmoe-multicast | Multicast usage in LLM MoE | 7pg
Abstract: Large Language Models (LLMs) have been widely used in recent years.
   The Mixture of Experts (MoE) architecture is one of the features of
   LLMs that enables efficient inference and cost-effective training.
   With the MoE architecture, there are potential multicast use cases
   such as tokens dispatching.  This draft attempts to analyze these use
   cases.





RTGWG                                                           Z. Zhang
Internet-Draft                                                   W. Duan
Intended status: Informational                           ZTE Corporation
Expires: 23 April 2026                                             X. Xu
                                                            China Mobile
                                                         20 October 2025


                       Multicast usage in LLM MoE
                 draft-zhang-rtgwg-llmmoe-multicast-01

Abstract

   Large Language Models (LLMs) have been widely used in recent years.
   The Mixture of Experts (MoE) architecture is one of the features of
   LLMs that enables efficient inference and cost-effective training.
   With the MoE architecture, there are potential multicast use cases
   such as tokens dispatching.  This draft attempts to analyze these use
   cases.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.










Zhang, et al.             Expires 23 April 2026                 [Page 1]

Internet-Draft              Abbreviated Title               October 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Use case - tokens dispatching . . . . . . . . . . . . . . . .   3
     2.1.  Intra-node multicast  . . . . . . . . . . . . . . . . . .   4
     2.2.  Inter-node multicast  . . . . . . . . . . . . . . . . . .   4
     2.3.  Dynamic Requirements  . . . . . . . . . . . . . . . . . .   5
     2.4.  Reliability requirements  . . . . . . . .

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Token Dispatching Multicast",
    "description": "Multicast mechanism for distributing tokens from gating network to selected expert nodes in MoE architecture. Enables efficient routing of input tokens to appropriate expert models based on routing decisions.",
    "type": "mechanism"
  },
  {
    "title": "Intra-node Expert Multicast", 
    "description": "Multicast pattern for distributing tokens to multiple experts residing within the same physical node or server. Optimizes local communication between gating function and co-located expert models.",
    "type": "pattern"
  },
  {
    "title": "Inter-node Expert Multicast",
    "description": "Network-level multicast mechanism for sending tokens from gating nodes to expert nodes distributed across different physical servers. Requires network infrastructure support for efficient cross-node communication.",
    "type": "mechanism"
  },
  {
    "title": "Dynamic Multicast Group Management",
    "description": "Requirement for dynamically adjusting multicast group membership based on real-time expert selection decisions. Group composition changes per inference request based on gating network outputs.",
    "type": "requirement"
  },
  {
    "title": "MoE Reliability Requirements",
    "description": "Reliability constraints for multicast delivery in LLM inference pipelines where token loss can impact model accuracy. Defines fault tolerance needs for expert communication patterns.",
    "type": "requirement"
  }
]


draft_name: draft-zhang-rvp-problem-statement
prompt_hash: 0e4a88505f5d1633
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:04.959789+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhang-rvp-problem-statement | Problem Statements and Requirements of Real-Virtual Agent Protocol (RVP): Communication Protocol for Embodied Intelligence in Physical- Digital Continuum | 23pg
Abstract: The Real-Virtual Agent Protocol (RVP) enables seamless coordination
  between physical entities (robots, IoT devices, manufacturing
  systems and agents) and digital agents (AI systems, software agents,
  virtual twins) through unified composite identity management,
  physical/social/production relations graph-based coordination, and
  physical constraint integration. Unlike existing protocols that
  assume peer-to-peer digital relationships (A2A for agents, MCP for
  AI tools, ANP for agent networks), RVP unifies physical and digital
  agents communication and achieves physical data loop for online
  learning for embodied agents considering both hierarchical
  physical/social/production relations and physical world constraints.
  RVP is designed for immediate deployment in modern manufacturing,
  smart cities, autonomous mobility systems, and human-AI
  collaborative environments where non-peer, partially centralized
  relations and coordination is essential for real-world embodied
  intelligence networks.

Workgroup:Network Working Group                                     X.Zhang
Internet-Draft:                                                    Hicagent
draft-zhang-rvp-problem-statement-00                                Y.Zhang
Published:20 October 2025                                           C.Zhang
Intended status: Informational                                      M.Zhang
Expires:20 April 2026                                         China Telecom
                                                                       W.Lu
                                                                     SUPCON




    Problem Statements and Requirements of Real-Virtual Agent Protocol
   (RVP): Communication Protocol for Embodied Intelligence in Physical-
                            Digital Continuum





    Status of this Memo

  This Internet-Draft is submitted in full conformance with the
  provisions of BCP 78 and BCP 79. This document may not be modified,
  and derivative works of it may not be created, except to publish it
  as an RFC and to translate it into languages other than English.

  This document may contain material from IETF Documents or IETF
  Contributions published or made publicly available before November
  10, 2008. The person(s) controlling the copyright in some of this
  material may not have granted the IETF Trust the right to allow
  modifications of such material outside the IETF Standards Process.
  Without obtaining an adequate license from the person(s) controlling
  the copyright in such materials, this document may not be modified
  outside the IETF Standards Process, and derivative works of it may
  not be created outside the IETF Standards Process, except to format
  it for publication as an RFC or to translate it into languages other
  than English.

  Internet-Drafts are working documents of the Internet Engineering
  Task Force (IETF), its areas, and its working groups.  Note that
  other groups may also distribute working documents as Internet-
  Drafts.

  Internet-Drafts are draft documents valid for a maximum of six
  months and may be updated, replaced, or obsoleted by other documents
  at any time.  It is inappropriate to use Internet-Drafts as reference
  material or to cite them other than as "work in progress."



    Zhang                  Expires 20,April,2026                 [Page 1]

    Internet-Draft          RVP Problem Statement             October 2025


  The list of current Internet-Drafts can be accessed at
  http://www.ietf.org/ietf/1id-abstracts.txt

  The list of Internet-Draft Shadow Directories can be accessed at
  http://www.ietf.org/shadow.html

  This Internet-Draft will expire on April 20, 2026.

    Copyright Notice

  Copyright (c) 2025 IETF Trust and the persons identified as the
  document authors. All rights reserved.

  This document is subject to BCP 78 and the IETF Trust's Legal
  Provisions Relating to IETF Doc

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Unified Composite Identity Management",
    "description": "Identity management system that bridges physical entities (robots, IoT devices) and digital agents (AI systems, virtual twins) under a single identity framework. Enables seamless coordination between physical and digital domains.",
    "type": "mechanism"
  },
  {
    "title": "Physical/Social/Production Relations Graph",
    "description": "Graph-based coordination system that models hierarchical relationships between agents considering physical constraints, social interactions, and production workflows. Supports non-peer, partially centralized coordination patterns.",
    "type": "architecture"
  },
  {
    "title": "Physical Constraint Integration",
    "description": "Integration mechanism that incorporates real-world physical limitations and constraints into digital agent communication and decision-making processes. Ensures digital agents respect physical world boundaries.",
    "type": "mechanism"
  },
  {
    "title": "Physical Data Loop for Online Learning",
    "description": "Continuous feedback mechanism that enables embodied agents to learn from real-world physical interactions and update their behavior in real-time. Creates closed-loop learning between physical actions and digital intelligence.",
    "type": "pattern"
  },
  {
    "title": "Physical-Digital Continuum Protocol",
    "description": "Communication protocol architecture that unifies physical and digital agent interactions, moving beyond peer-to-peer assumptions of existing protocols (A2A, MCP, ANP). Designed for embodied intelligence networks with hierarchical relations.",
    "type": "protocol"
  }
]


draft_name: draft-zhao-ccamp-actn-optical-network-agent
prompt_hash: 0778891fb3f99e0d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:11.378388+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhao-ccamp-actn-optical-network-agent | Integration of Network Management Agent (NMA) into ACTN-Based Optical Network | 10pg
Abstract: With the growth of optical network scale, the complexity of network
   operation and maintenance has increased dramatically.  Enhancing the
   intelligence level of optical network operation and management and
   building high-level autonomous optical networks have become the
   common vision of global operators.  The development of AI, especially
   large AI model technologies, provides a feasible technical path for
   realizing autonomous perception, decision-making, analysis, and
   execution.  The existing ACTN architecture provides network
   abstraction and control functions for optical networks but lacks
   higher-level autonomous capabilities.

   This document explores the introduction of AI based Network
   Management Agent(NMA) functions into ACTN-based optical networks to
   achieve high-level autonomy of optical networks.  It discusses the
   ACTN-enhanced architecture of optical networks after the introduction
   of NMAs, including key components, interaction relationships, new
   interface requirements in the enhanced architecture, as well as
   typical use cases of agent-based autonomous operation and maintenance
   for optical networks.  The document aims to improve the autonomy
   level of optical networks and promote the realization of autonomous
   optical networks by extending the original ACTN architecture.





Common Control and Measurement Plane                             X. Zhao
Internet-Draft                                                     CAICT
Intended status: Informational                                     H. Yu
Expires: 23 April 2026                                            Huawei
                                                                   Y. Xu
                                                                   CAICT
                                                         20 October 2025


 Integration of Network Management Agent (NMA) into ACTN-Based Optical
                                Network
             draft-zhao-ccamp-actn-optical-network-agent-00

Abstract

   With the growth of optical network scale, the complexity of network
   operation and maintenance has increased dramatically.  Enhancing the
   intelligence level of optical network operation and management and
   building high-level autonomous optical networks have become the
   common vision of global operators.  The development of AI, especially
   large AI model technologies, provides a feasible technical path for
   realizing autonomous perception, decision-making, analysis, and
   execution.  The existing ACTN architecture provides network
   abstraction and control functions for optical networks but lacks
   higher-level autonomous capabilities.

   This document explores the introduction of AI based Network
   Management Agent(NMA) functions into ACTN-based optical networks to
   achieve high-level autonomy of optical networks.  It discusses the
   ACTN-enhanced architecture of optical networks after the introduction
   of NMAs, including key components, interaction relationships, new
   interface requirements in the enhanced architecture, as well as
   typical use cases of agent-based autonomous operation and maintenance
   for optical networks.  The document aims to improve the autonomy
   level of optical networks and promote the realization of autonomous
   optical networks by extending the original ACTN architecture.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the Network Management
   Operations Working Group mailing list (nmop@ietf.org), which is
   archived at https://mailarchive.ietf.org/arch/browse/ccamp/.

   Source for this draft and an issue tracker can be found at
   https://datatracker.ietf.org/doc/draft-zhao-ccamp-actn-optical-
   network-agent/.



Zhao, et al.              Expires 23 April 2026                 [Page 1]

Internet-Draft         NMA enhanced actn framework          October 2025


Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Network Management Agent (NMA) Integration",
    "description": "AI-based Network Management Agents integrated into ACTN optical networks to provide autonomous perception, decision-making, analysis, and execution capabilities. These agents extend the existing ACTN architecture with higher-level autonomous functions.",
    "type": "architecture"
  },
  {
    "title": "ACTN-Enhanced Architecture",
    "description": "Extended ACTN architecture that incorporates Network Management Agents as key components with defined interaction relationships. The enhanced architecture maintains network abstraction and control functions while adding autonomous capabilities.",
    "type": "architecture"
  },
  {
    "title": "Agent-Based Interface Requirements",
    "description": "New interface specifications required in the enhanced ACTN architecture to support communication between Network Management Agents and existing ACTN components. These interfaces enable autonomous operation and maintenance functions.",
    "type": "requirement"
  },
  {
    "title": "Autonomous Optical Network Operation",
    "description": "Use cases and patterns for agent-based autonomous operation and maintenance in optical networks. Includes scenarios where AI agents perform network management tasks without human intervention.",
    "type": "pattern"
  },
  {
    "title": "Large AI Model Integration Pattern",
    "description": "Technical approach for integrating large AI model technologies into optical network management systems. Enables autonomous network functions through AI-driven decision making processes.",
    "type": "mechanism"
  }
]


draft_name: draft-zhao-nmop-network-management-agent
prompt_hash: dcf7d84266035621
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:18.634532+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhao-nmop-network-management-agent | AI based Network Management Agent(NMA): Concepts and Architecture | 24pg
Abstract: The evolution from Level 3 (assisted automation) to Level 4
   (autonomous self-optimization) in Autonomous Networks (AN) introduces
   requirements for Agentic capabilities, including intent-based
   reasoning, autonomous planning, and context-aware decision-making,
   which transcend the static, rule-based logic of traditional SDN
   Controllers.  This document defines the concept of the Network
   Management Agent (NMA), an AI-driven entity designed to embody these
   cognitive functions and bridge the gap between service intent and
   network operations.

   This document also specifies how the NMA utilizes the existing
   capabilities of SDN Controllers—such as topology management,
   telemetry, and enforcement—to achieve Autonomous L4 without
   duplicating policy control functions.  It further details the
   architectural integration modes and defines the interface
   requirements necessary for SDN Controllers to interoperate with NMAs.





Network Management Operations                                    X. Zhao
Internet-Draft                                                     CAICT
Intended status: Informational                                   M. Wang
Expires: 31 August 2026                                     China Mobile
                                                                   B. Wu
                                                                  Huawei
                                                           D. Ceccarelli
                                                                   Cisco
                                                                H. Zheng
                                                                  Huawei
                                                                 J. Zhou
                                                                     ZTE
                                                        27 February 2026


   AI based Network Management Agent(NMA): Concepts and Architecture
              draft-zhao-nmop-network-management-agent-04

Abstract

   The evolution from Level 3 (assisted automation) to Level 4
   (autonomous self-optimization) in Autonomous Networks (AN) introduces
   requirements for Agentic capabilities, including intent-based
   reasoning, autonomous planning, and context-aware decision-making,
   which transcend the static, rule-based logic of traditional SDN
   Controllers.  This document defines the concept of the Network
   Management Agent (NMA), an AI-driven entity designed to embody these
   cognitive functions and bridge the gap between service intent and
   network operations.

   This document also specifies how the NMA utilizes the existing
   capabilities of SDN Controllers—such as topology management,
   telemetry, and enforcement—to achieve Autonomous L4 without
   duplicating policy control functions.  It further details the
   architectural integration modes and defines the interface
   requirements necessary for SDN Controllers to interoperate with NMAs.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the Network Management
   Operations Working Group mailing list (nmop@ietf.org), which is
   archived at https://mailarchive.ietf.org/arch/btrse/nmop/.

   Source for this draft and an issue tracker can be found at
   https://datatracker.ietf.org/doc/draft-zhao-nmop-network-management-
   agent/.



Zhao, et al.             Expires 31 August 2026                 [Page 1]

Internet-Draft      Network Management Agent Concept       February 2026


Status of This Memo

   This note is to be removed before publishing as an RFC.

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Network Management Agent (NMA)",
    "description": "An AI-driven entity that performs intent-based reasoning, autonomous planning, and context-aware decision-making to bridge service intent and network operations. Designed to achieve Level 4 autonomous self-optimization in Autonomous Networks.",
    "type": "architecture"
  },
  {
    "title": "SDN Controller Capability Utilization",
    "description": "NMA leverages existing SDN Controller functions including topology management, telemetry, and enforcement without duplicating policy control functions. Enables autonomous operation while preserving existing infrastructure investments.",
    "type": "mechanism"
  },
  {
    "title": "Level 3 to Level 4 Autonomy Evolution",
    "description": "Transition from assisted automation (Level 3) to autonomous self-optimization (Level 4) requiring agentic capabilities that transcend static rule-based logic. Defines the technical requirements for this evolutionary step in network automation.",
    "type": "requirement"
  },
  {
    "title": "NMA-SDN Controller Integration Modes",
    "description": "Architectural patterns for integrating AI-driven Network Management Agents with existing SDN Controllers. Defines multiple modes of operation to accommodate different deployment scenarios.",
    "type": "architecture"
  },
  {
    "title": "NMA-SDN Interoperability Interface Requirements",
    "description": "Technical specifications for interfaces that enable SDN Controllers to interoperate with Network Management Agents. Defines the communication protocols and data exchange formats needed for seamless integration.",
    "type": "protocol"
  }
]


draft_name: draft-zhao-nmrg-ai-agent-for-dtn
prompt_hash: f709cb804df0fcf6
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:26.563216+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhao-nmrg-ai-agent-for-dtn | AI Agent Architecture for DTN Digital Twin Network | 7pg
Abstract: This document proposes an AI agent architecture for Digital Twin
   Network (DTN) that integrates AI agents with digital twin technology.
   The architecture extends the traditional DTN architecture by
   incorporating autonomous AI agents at each component level, enabling
   more intelligent and adaptive network management capabilities.





nmrg                                                        J. Zhao, Ed.
Internet-Draft                                              R. Pang, Ed.
Intended status: Standards Track                           S. Zhang, Ed.
Expires: 23 April 2026                                      China Unicom
                                                         20 October 2025


           AI Agent Architecture for DTN Digital Twin Network
                  draft-zhao-nmrg-ai-agent-for-dtn-00

Abstract

   This document proposes an AI agent architecture for Digital Twin
   Network (DTN) that integrates AI agents with digital twin technology.
   The architecture extends the traditional DTN architecture by
   incorporating autonomous AI agents at each component level, enabling
   more intelligent and adaptive network management capabilities.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.



Zhao, et al.              Expires 23 April 2026                 [Page 1]

Internet-Draft        AI Agent Architecture for DTN         October 2025


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  AI Agent Architecture for Digital Twin Network  . . . . . . .   2
   3.  Architecture Components . . . . . . . . . . . . . . . . . . .   3
     3.1.  Digital Twin Network Management AI Agent  . . . . . . . .   3
     3.2.  Functional Model AI Agent . . . . . . . . . . . . . . . .   4
     3.3.  Basic Model AI Agent  . . . . . . . . . . . . . . . . . .   4
     3.4.  Data Repository AI Agent  . . . . . . . . . . . . . . . .   4
   4.  Agent Interactions  . . . . . . . . . . . . . . . . . . . . .  

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "AI Agent Architecture for DTN",
    "description": "A layered architecture that extends traditional Digital Twin Networks by incorporating autonomous AI agents at each component level. The architecture enables intelligent and adaptive network management through AI-powered decision making.",
    "type": "architecture"
  },
  {
    "title": "Digital Twin Network Management AI Agent",
    "description": "A top-level AI agent responsible for overall network management and orchestration within the digital twin environment. It coordinates high-level network policies and strategic decision making.",
    "type": "mechanism"
  },
  {
    "title": "Functional Model AI Agent",
    "description": "An AI agent that manages specific network functions and services within the digital twin network. It handles operational logic and functional behavior modeling.",
    "type": "mechanism"
  },
  {
    "title": "Basic Model AI Agent",
    "description": "A foundational AI agent that manages core network elements and basic operations. It provides fundamental network modeling and control capabilities.",
    "type": "mechanism"
  },
  {
    "title": "Data Repository AI Agent",
    "description": "An AI agent dedicated to managing data storage, retrieval, and processing within the digital twin network. It handles data lifecycle management and intelligent data operations.",
    "type": "mechanism"
  },
  {
    "title": "Multi-Level Agent Integration",
    "description": "A hierarchical integration pattern where AI agents operate at different architectural levels and interact through defined interfaces. This enables distributed intelligence across the digital twin network stack.",
    "type": "pattern"
  }
]


draft_name: draft-zheng-agent-identity-management
prompt_hash: 019c2ca33b9199be
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:31.542814+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zheng-agent-identity-management | Agent Identity Managenment | 12pg
Abstract: This document specifies agent identity management in the Internet of
   Agents (IOA) system.  It defines the descriptive requirements for
   agent identities, the agent registration process, the structure and
   assignment of agent identifiers, and the basic and extended identity
   management functions performed by the agent gateway based on the
   agent's descriptive information.





artarea                                                         C. Zheng
Internet-Draft                                                    B. Liu
Intended status: Standards Track                     Huawei Technologies
Expires: 6 May 2026                                              N. Geng
                                                                  Huawei
                                                                  Q. Gao
                                                                X. Shang
                                                                   Z. Li
                                                     Huawei Technologies
                                                         2 November 2025


                       Agent Identity Managenment
                draft-zheng-agent-identity-management-00

Abstract

   This document specifies agent identity management in the Internet of
   Agents (IOA) system.  It defines the descriptive requirements for
   agent identities, the agent registration process, the structure and
   assignment of agent identifiers, and the basic and extended identity
   management functions performed by the agent gateway based on the
   agent's descriptive information.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.






Zheng, et al.              Expires 6 May 2026                   [Page 1]

Internet-Draft         Agent Identity Managenment          November 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Overview of the Agent Ident

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent Identity Descriptive Requirements",
    "description": "Defines specific requirements for describing agent identities in the Internet of Agents (IOA) system. These requirements specify what information must be captured to properly identify and characterize agents.",
    "type": "requirement"
  },
  {
    "title": "Agent Registration Process",
    "description": "Specifies the process by which agents register themselves within the IOA system. This includes the steps and procedures for onboarding new agents and establishing their identities.",
    "type": "protocol"
  },
  {
    "title": "Agent Identifier Structure and Assignment",
    "description": "Defines the structure of agent identifiers and the mechanism for assigning unique identifiers to agents. This ensures each agent has a distinct identity within the IOA system.",
    "type": "mechanism"
  },
  {
    "title": "Agent Gateway Identity Management Functions",
    "description": "Specifies basic and extended identity management functions performed by the agent gateway based on agent descriptive information. The gateway serves as a central component for managing agent identities.",
    "type": "architecture"
  }
]


draft_name: draft-zheng-dispatch-agent-identity-management
prompt_hash: c475c643c4848b7c
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:37.938611+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zheng-dispatch-agent-identity-management | Agent Identity Managenment | 12pg
Abstract: This document specifies agent identity management in the Internet of
   Agents (IOA) system.  It defines the descriptive requirements for
   agent identities, the agent registration process, the structure and
   assignment of agent identifiers, and the basic and extended identity
   management functions performed by the agent gateway based on the
   agent's descriptive information.





Dispatch                                                        C. Zheng
Internet-Draft                                                    B. Liu
Intended status: Standards Track                                 N. Geng
Expires: 7 May 2026                                               Q. Gao
                                                                X. Shang
                                                                   Z. Li
                                                     Huawei Technologies
                                                         3 November 2025


                       Agent Identity Managenment
           draft-zheng-dispatch-agent-identity-management-00

Abstract

   This document specifies agent identity management in the Internet of
   Agents (IOA) system.  It defines the descriptive requirements for
   agent identities, the agent registration process, the structure and
   assignment of agent identifiers, and the basic and extended identity
   management functions performed by the agent gateway based on the
   agent's descriptive information.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 7 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights



Zheng, et al.              Expires 7 May 2026                   [Page 1]

Internet-Draft         Agent Identity Managenment          November 2025


   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Overview of the Agent Identity Management . . . . . . . . . .   3
   3.  Agent description Requirements  . . . . . . . . . . . . . . .   4
     3.1.  Basic Information . .

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent Identifier Structure",
    "description": "Defines the structure and assignment process for unique identifiers used to distinguish agents in the Internet of Agents (IOA) system. The identifiers enable routing and addressing of agents within the distributed system.",
    "type": "mechanism"
  },
  {
    "title": "Agent Registration Process",
    "description": "Specifies the process by which agents register themselves with the system to establish their identity and capabilities. This process creates the binding between agent identifiers and their descriptive information.",
    "type": "protocol"
  },
  {
    "title": "Agent Gateway Identity Management",
    "description": "Defines basic and extended identity management functions performed by agent gateways based on agent descriptive information. These functions include identity verification, capability tracking, and access control.",
    "type": "architecture"
  },
  {
    "title": "Agent Descriptive Requirements",
    "description": "Establishes requirements for how agents must describe themselves including basic information and capabilities. This standardizes the metadata needed for effective agent discovery and interaction.",
    "type": "requirement"
  },
  {
    "title": "Internet of Agents Identity Framework",
    "description": "Provides an overarching framework for managing identities across a distributed system of autonomous agents. The framework enables scalable identity management in multi-agent environments.",
    "type": "architecture"
  }
]


draft_name: draft-zhul-dhc-bnc-up-specific-suboption
prompt_hash: 7de2d2e22549a768
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:44.139980+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhul-dhc-bnc-up-specific-suboption | Broadband Network UP-Specific Information Suboption for the DHCP Relay Agent Option | 6pg
Abstract: This document defines a new Broadband Network UP-Specific Information
   suboption for the Dynamic Host Configuration Protocol’s (DHCP) relay
   agent information option.  The suboption allows the DHCP relay agent
   (Broadband Network CP) to include UP-specific information in the DHCP
   messages it forwards, to ensure that subscribers within the same SGRP
   under the same UP are assigned IP addresses from the same address
   space by the DHCP server.





dhc                                                          L. Zhu, Ed.
Internet-Draft                                             Y. Zhang, Ed.
Intended status: Standards Track                            China Unicom
Expires: 31 July 2026                                    27 January 2026


 Broadband Network UP-Specific Information Suboption for the DHCP Relay
                              Agent Option
              draft-zhul-dhc-bnc-up-specific-suboption-01

Abstract

   This document defines a new Broadband Network UP-Specific Information
   suboption for the Dynamic Host Configuration Protocol’s (DHCP) relay
   agent information option.  The suboption allows the DHCP relay agent
   (Broadband Network CP) to include UP-specific information in the DHCP
   messages it forwards, to ensure that subscribers within the same SGRP
   under the same UP are assigned IP addresses from the same address
   space by the DHCP server.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 31 July 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.










Zhu & Zhang               Expires 31 July 2026                  [Page 1]

Internet-Draft  Broadband Network UP-Specific Informatio    January 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Broadband Network UP-Specific Information Suboption . . . . .   4
   4.  DHCP Relay Agent Behavior . . . . . . . . . . . . . . . . . .   5
   5.  DHCP Server Behavior  . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "UP-Specific Information Suboption",
    "description": "A new DHCP relay agent suboption that carries UP (User Plane) specific information to enable proper address assignment. Allows broadband network control plane to include UP context in forwarded DHCP messages.",
    "type": "extension"
  },
  {
    "title": "SGRP Address Space Consistency",
    "description": "Mechanism to ensure subscribers within the same SGRP (Subscriber Group) under the same UP are assigned IP addresses from the same address space. Provides address allocation consistency based on network topology.",
    "type": "mechanism"
  },
  {
    "title": "Broadband Network CP Relay Enhancement",
    "description": "Extension to DHCP relay agent behavior for broadband network control plane functions. Enables relay agents to inject UP-specific context into DHCP message flows.",
    "type": "extension"
  },
  {
    "title": "UP-Aware DHCP Server Processing",
    "description": "Server-side behavior modification to process UP-specific information from relay agents. Enables DHCP servers to make topology-aware address assignment decisions.",
    "type": "mechanism"
  }
]


draft_name: draft-zhul-intarea-bnc-up-specific-suboption
prompt_hash: cc2fbb459d4b00ce
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:50.577735+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zhul-intarea-bnc-up-specific-suboption | Broadband Network UP-Specific Information Suboption for the DHCP Relay Agent Option | 6pg
Abstract: This document defines a new Broadband Network UP-Specific Information
   suboption for the Dynamic Host Configuration Protocol’s (DHCP) relay
   agent information option.  The suboption allows the DHCP relay agent
   (Broadband Network CP) to include UP-specific information in the DHCP
   messages it forwards, to ensure that subscribers within the same SGRP
   under the same UP are assigned IP addresses from the same address
   space by the DHCP server.





intarea                                                      L. Zhu, Ed.
Internet-Draft                                             Y. Zhang, Ed.
Intended status: Standards Track                            China Unicom
Expires: 16 August 2026                                 12 February 2026


 Broadband Network UP-Specific Information Suboption for the DHCP Relay
                              Agent Option
            draft-zhul-intarea-bnc-up-specific-suboption-00

Abstract

   This document defines a new Broadband Network UP-Specific Information
   suboption for the Dynamic Host Configuration Protocol’s (DHCP) relay
   agent information option.  The suboption allows the DHCP relay agent
   (Broadband Network CP) to include UP-specific information in the DHCP
   messages it forwards, to ensure that subscribers within the same SGRP
   under the same UP are assigned IP addresses from the same address
   space by the DHCP server.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 16 August 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.










Zhu & Zhang              Expires 16 August 2026                 [Page 1]

Internet-Draft  Broadband Network UP-Specific Informatio   February 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Broadband Network UP-Specific Information Suboption . . . . .   4
   4.  DHCP Relay Agent Behavior . . . . . . . . . . . . . . . . . .   5
   5.  DHCP Server Behavior  . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Broadband Network UP-Specific Information Suboption",
    "description": "A new DHCP relay agent suboption that carries UP-specific information to help DHCP servers make informed IP address assignment decisions. This extends the existing DHCP relay agent information option with broadband network context.",
    "type": "extension"
  },
  {
    "title": "SGRP Address Space Consistency Mechanism",
    "description": "Ensures that subscribers within the same Service Group (SGRP) under the same User Plane (UP) receive IP addresses from the same address space. This maintains network topology consistency for broadband subscribers.",
    "type": "mechanism"
  },
  {
    "title": "Broadband Network CP as DHCP Relay Agent",
    "description": "Defines the role of Broadband Network Control Plane (CP) as a DHCP relay agent that includes UP-specific information in forwarded DHCP messages. This creates a bridge between broadband network architecture and DHCP operations.",
    "type": "architecture"
  },
  {
    "title": "UP-Aware DHCP Server Behavior",
    "description": "Specifies how DHCP servers should process and utilize UP-specific information from relay agents to make address assignment decisions. This enables DHCP servers to understand broadband network topology.",
    "type": "protocol"
  }
]


draft_name: draft-zl-agents-networking-architecture
prompt_hash: 867843c96e4111e9
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:57.886387+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zl-agents-networking-architecture | Agents Networking Architecture for Enterprise and Broadband | 13pg
Abstract: This document introduces agents networking architecture and defines
   the core components of agent networking, as well as typical
   interactions among these key components.





network working group                                           L. Zhang
Internet-Draft                                                    B. Liu
Intended status: Informational                       Huawei Technologies
Expires: 23 April 2026                                           N. Geng
                                                                  Huawei
                                                                 Z. Wang
                                                             Independent
                                                         20 October 2025


      Agents Networking Architecture for Enterprise and Broadband
               draft-zl-agents-networking-architecture-00

Abstract

   This document introduces agents networking architecture and defines
   the core components of agent networking, as well as typical
   interactions among these key components.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Zhang, et al.             Expires 23 April 2026                 [Page 1]

Internet-Draft       Agents Networking Architecture         October 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  IoA architecture and Components . . . . . . . . . . . . . . .   3
     2.1.  Overview of Agents Networking . . . . . . . . . . . . . .   3
     2.2.  Agent Certificate Authority . . . . . . . . . . . . . . .   4
     2.3.  Agent Registration Server . . . . . . . . . . . . . . . .   4
     2.4.  AI Agents . . . . . . . . . . . . . . . . . . . . . . . .   5


Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent Certificate Authority",
    "description": "A specialized certificate authority component designed specifically for managing digital certificates and authentication within agent networking environments. It provides security infrastructure for AI agents operating in enterprise and broadband networks.",
    "type": "architecture"
  },
  {
    "title": "Agent Registration Server",
    "description": "A centralized server component that handles the registration and management of AI agents within the networking architecture. It maintains agent identity and facilitates agent discovery and coordination.",
    "type": "architecture"
  },
  {
    "title": "IoA Architecture",
    "description": "Internet of Agents architecture that defines the structural framework for connecting and coordinating multiple AI agents across enterprise and broadband networks. It establishes the foundational components and their relationships.",
    "type": "architecture"
  },
  {
    "title": "Agent-to-Agent Interaction Model",
    "description": "A communication pattern that defines how AI agents interact with each other within the networking architecture. It specifies the protocols and mechanisms for inter-agent coordination and data exchange.",
    "type": "pattern"
  },
  {
    "title": "Agents Networking Core Components",
    "description": "A set of essential building blocks including Agent Certificate Authority, Agent Registration Server, and AI Agents that form the foundation of the agent networking system. These components work together to enable secure agent communication and coordination.",
    "type": "architecture"
  }
]


draft_name: draft-zl-agents-networking-framework
prompt_hash: 77b01c4c6f1e70a6
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:28:56.518249+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zl-agents-networking-framework | Agents Networking Framework for Enterprise and Broadband | 14pg
Abstract: This document introduces agents networking framework and defines the
   core components of agent networking in enterprise and broadband, as
   well as typical interactions among these key components.





rtgwg                                                           L. Zhang
Internet-Draft                                                    B. Liu
Intended status: Informational                                   N. Geng
Expires: 6 May 2026                                             X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                     Huawei Technologies
                                                         2 November 2025


        Agents Networking Framework for Enterprise and Broadband
                draft-zl-agents-networking-framework-00

Abstract

   This document introduces agents networking framework and defines the
   core components of agent networking in enterprise and broadband, as
   well as typical interactions among these key components.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Zhang, et al.              Expires 6 May 2026                   [Page 1]

Internet-Draft         Agents Networking Framework         November 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  IoA framework and Components  . . . . . . . . . . . . . . . .   3
     2.1.  Overview of Agents Networking . . . . . . . . . . . . . .   3
     2.2.  Agent Certificate Authority . . . . . . . . . . . . . . .   4
     2.3.  Agent Registration Server . . . . . . . . . . . . . . . .   4
     2.4.  AI Agents . . . . . . . . . . . . . . . . .

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "IoA Framework",
    "description": "Internet of Agents (IoA) framework defining core components for agent networking in enterprise and broadband environments. Establishes the overall architecture for agent-based networking systems.",
    "type": "architecture"
  },
  {
    "title": "Agent Certificate Authority",
    "description": "Dedicated certificate authority component for managing authentication and security credentials for AI agents in the networking framework. Provides trust establishment mechanisms for agent communications.",
    "type": "mechanism"
  },
  {
    "title": "Agent Registration Server",
    "description": "Centralized server component responsible for registering and managing AI agents within the networking framework. Handles agent discovery and lifecycle management.",
    "type": "mechanism"
  },
  {
    "title": "Multi-Agent Communication Pattern",
    "description": "Defines typical interactions and communication patterns among key components in the agents networking framework. Establishes standardized methods for agent-to-agent and agent-to-infrastructure communications.",
    "type": "pattern"
  }
]


draft_name: draft-zl-agents-networking-scenarios
prompt_hash: 179ea9e369a5c0b1
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:29:05.918240+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zl-agents-networking-scenarios | Agents Networking Scenarios in Enterprise and Broadband Networks | 8pg
Abstract: This document describes agents networking scenarios in enterprise and
   home broadband networks.  These scenarios differ from 6G and Internet
   scenarios.  Since the agentic service is still at the emerging stage,
   especially in enterprise and home broadband networks, the scenarios
   are mostly based on reasonable assumptions.





network working group                                             B. Liu
Internet-Draft                                                  L. Zhang
Intended status: Informational                       Huawei Technologies
Expires: 23 April 2026                                            Y. Liu
                                                             Independent
                                                         20 October 2025


    Agents Networking Scenarios in Enterprise and Broadband Networks
                draft-zl-agents-networking-scenarios-00

Abstract

   This document describes agents networking scenarios in enterprise and
   home broadband networks.  These scenarios differ from 6G and Internet
   scenarios.  Since the agentic service is still at the emerging stage,
   especially in enterprise and home broadband networks, the scenarios
   are mostly based on reasonable assumptions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Liu, et al.               Expires 23 April 2026                 [Page 1]

Internet-Draft         Agents Networking Scenarios          October 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Enterprise Scenarios  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Smart Office  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Agentic Digitalization  . . . . . . . . . . . . . . . . .   3
     2.3.  Industrial Automation . . . . . . . . . . . . . . . . . .   4
   3.  Home Broadband Network Scenarios  . . . . . . . . . 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Smart Office Agent Coordination",
    "description": "Agents deployed across office environments to coordinate meeting room management, resource allocation, and workplace optimization. These agents operate within enterprise network constraints and security boundaries.",
    "type": "architecture"
  },
  {
    "title": "Agentic Digitalization Framework",
    "description": "Enterprise digitalization processes automated through networked agents that handle document processing, workflow management, and business process automation. Requires specific networking protocols for agent-to-agent communication in enterprise environments.",
    "type": "mechanism"
  },
  {
    "title": "Industrial Automation Agent Networks",
    "description": "Specialized agent networking for industrial control systems and manufacturing automation. Agents coordinate production processes and equipment management with real-time networking requirements.",
    "type": "architecture"
  },
  {
    "title": "Home Broadband Agent Scenarios",
    "description": "Agent deployment patterns specific to residential broadband networks, differing from enterprise scenarios in terms of bandwidth, security models, and device types. Addresses home automation and personal assistant coordination.",
    "type": "pattern"
  },
  {
    "title": "Enterprise vs Internet Agent Networking",
    "description": "Distinct networking requirements and scenarios for agents in controlled enterprise environments compared to open Internet deployments. Focuses on security boundaries and network topology constraints.",
    "type": "requirement"
  }
]


draft_name: draft-zlgsgl-rtgwg-agents-networking-framework
prompt_hash: 86f7897645a40afd
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:29:11.879336+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zlgsgl-rtgwg-agents-networking-framework | Agents Networking Framework for Enterprise and Broadband | 14pg
Abstract: This document introduces agents networking framework and defines the
   core components of agent networking in enterprise and broadband, as
   well as typical interactions among these key components.





rtgwg                                                           L. Zhang
Internet-Draft                                                    B. Liu
Intended status: Informational                                   N. Geng
Expires: 7 May 2026                                             X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                     Huawei Technologies
                                                         3 November 2025


        Agents Networking Framework for Enterprise and Broadband
           draft-zlgsgl-rtgwg-agents-networking-framework-00

Abstract

   This document introduces agents networking framework and defines the
   core components of agent networking in enterprise and broadband, as
   well as typical interactions among these key components.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 7 May 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.











Zhang, et al.              Expires 7 May 2026                   [Page 1]

Internet-Draft         Agents Networking Framework         November 2025


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  IoA framework and Components  . . . . . . . . . . . . . . . .   3
     2.1.  Overview of Agents Networking . . . . . . . . . . . . . .   3
     2.2.  Agent Certificate Authority . . . . . . . . . . . . . . .   4
     2.3.  Agent Registration Server . . . . . . . . . . . . . . . .   4
     2.4.  AI Agents . . . . . . . . . . . . . . 

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent Certificate Authority",
    "description": "A centralized authority component responsible for issuing and managing digital certificates for AI agents in the networking framework. This enables secure authentication and authorization of agents within enterprise and broadband networks.",
    "type": "architecture"
  },
  {
    "title": "Agent Registration Server",
    "description": "A server component that handles the registration and lifecycle management of AI agents in the network. It maintains agent identities, capabilities, and status information for the networking framework.",
    "type": "architecture"
  },
  {
    "title": "IoA Framework",
    "description": "Internet of Agents framework that defines the overall structure and interactions for agent-based networking in enterprise and broadband environments. It establishes the foundational architecture for agent communication and coordination.",
    "type": "architecture"
  },
  {
    "title": "Agents Networking",
    "description": "A networking paradigm that enables AI agents to interact and collaborate within network infrastructure. It defines how multiple agents can work together to manage and optimize enterprise and broadband network operations.",
    "type": "pattern"
  }
]


draft_name: draft-zm-rtgwg-mcp-troubleshooting
prompt_hash: a8fbd8a42f6ce480
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:29:18.639949+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zm-rtgwg-mcp-troubleshooting | Using the Model Context Protocol (MCP) for Intent-Based Network Troubleshooting Automation | 15pg
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.





Network Working Group                                            G. Zeng
Internet-Draft                                                    J. Mao
Intended status: Informational                                    B. Liu
Expires: 6 May 2026                                              N. Geng
                                                                X. Shang
                                                                  Q. Gao
                                                                   Z. Li
                                                                  Huawei
                                                         2 November 2025


    Using the Model Context Protocol (MCP) for Intent-Based Network
                       Troubleshooting Automation
                 draft-zm-rtgwg-mcp-troubleshooting-01

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2026.



Zeng, et al.               Expires 6 May 2026                   [Page 1]

Internet-Draft              MCP for Networks               November 2025


Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review thes

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "MCP Role Mapping for Network Management",
    "description": "Maps Model Context Protocol client-server roles to network architecture where network devices act as MCP servers and network controllers act as MCP clients. This enables LLM applications to interact with network infrastructure through standardized JSON-RPC 2.0 transport.",
    "type": "architecture"
  },
  {
    "title": "Device-to-Device MCP Extension",
    "description": "Extends MCP to support direct Device-to-Device (D2D) collaboration for distributed fault correlation when controllers are unreachable or real-time cross-device data is required. Allows network elements to perform autonomous troubleshooting without central coordination.",
    "type": "extension"
  },
  {
    "title": "MCP Primitives for Network Operations",
    "description": "Adapts MCP's Resources, Prompts and Tools primitives to network management domain for exposing device state, troubleshooting workflows, and network operations. Enables intent-based conversational interface for network automation.",
    "type": "mechanism"
  },
  {
    "title": "LLM-Driven Network Troubleshooting Framework",
    "description": "Provides automated network troubleshooting, configuration validation, and closed-loop remediation through LLM integration without requiring new protocols or device agents. Leverages existing MCP standard for AI-driven network operations.",
    "type": "protocol"
  }
]


draft_name: draft-zyyhl-agent-networks-framework
prompt_hash: e9f8514605ae484d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T11:29:23.861696+00:00
request_json:
Extract discrete technical ideas and mechanisms from this IETF draft.
Return a JSON array. Each element: {"title":"short name","description":"1-2 sentences","type":"mechanism|protocol|pattern|requirement|architecture|extension"}

draft-zyyhl-agent-networks-framework | Framework for AI Agent Networks | 21pg
Abstract: This document defines the framework of AI agent networks based on
   Agent Network Protocol (ANP) protocol.  [ANP] It provides the basic
   functions that needs to support AI agent communication in the AI
   agent networks within the trust domain.





Network Working Group                                            Y. Zhou
Internet-Draft                                 ANP Open Source Community
Intended status: Informational                                    K. Yao
Expires: 23 April 2026                                      China Mobile
                                                                   M. Yu
                                                           China Telecom
                                                                  M. Han
                                                            China Unicom
                                                                   C. Li
                                                                  Huawei
                                                         20 October 2025


                    Framework for AI Agent Networks
                draft-zyyhl-agent-networks-framework-01

Abstract

   This document defines the framework of AI agent networks based on
   Agent Network Protocol (ANP) protocol.  [ANP] It provides the basic
   functions that needs to support AI agent communication in the AI
   agent networks within the trust domain.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 23 April 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.



Zhou, et al.              Expires 23 April 2026                 [Page 1]

Internet-Draft          Agent Networks Framework            October 2025


   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Requirements

Return 3-8 ideas. Focus on CONCRETE technical contributions, not general statements.
JSON array only, no fences.

response_json:
[
  {
    "title": "Agent Network Protocol (ANP)",
    "description": "A specific protocol designed to enable communication between AI agents within network environments. ANP serves as the foundational communication mechanism for AI agent networks.",
    "type": "protocol"
  },
  {
    "title": "Trust Domain-Based Agent Networks",
    "description": "An architectural approach that constrains AI agent communication within defined trust boundaries. This mechanism ensures secure and controlled agent interactions within trusted network segments.",
    "type": "architecture"
  },
  {
    "title": "AI Agent Communication Framework",
    "description": "A structured framework that defines the basic functions and mechanisms required for AI agents to communicate effectively in networked environments. It provides standardized communication patterns for agent-to-agent interactions.",
    "type": "framework"
  }
]


draft_name: _landscape_
prompt_hash: 014adb37de6820c9
model: claude-sonnet-4-20250514
created_at: 2026-02-28T12:14:44.566569+00:00
request_json:
You are analyzing the landscape of 260 IETF Internet-Drafts related to AI agents and autonomous systems.

## Categories and Draft Counts
- Data formats/interop: 102 drafts
- Agent identity/auth: 98 drafts
- A2A protocols: 92 drafts
- Policy/governance: 60 drafts
- Autonomous netops: 60 drafts
- Agent discovery/reg: 57 drafts
- AI safety/alignment: 36 drafts
- ML traffic mgmt: 23 drafts
- Human-agent interaction: 22 drafts
- Other AI/agent: 21 drafts
- Agent-to-agent communication protocols: 16 drafts
- Agent discovery / registration: 14 drafts
- Model serving/inference: 13 drafts
- Identity / authentication for AI agents: 13 drafts
- Autonomous network operations: 5 drafts
- Data formats / semantics for AI interop: 3 drafts
- Policy / governance / ethical frameworks: 2 drafts
- AI safety / guardrails / alignment: 1 drafts
- ML-based traffic management / optimization: 1 drafts

## Most Common Technical Ideas
- Quantum-Safe Session Key Generation (3 drafts)
- Agent Gateway (3 drafts)
- Tool Enumeration API (3 drafts)
- Tool Invocation API (3 drafts)
- Agent Certificate Authority (3 drafts)
- Agent Registration Server (3 drafts)
- Agent Resource Type (2 drafts)
- Agentic Application Resource Type (2 drafts)
- Cross-Domain Agent Identity Management (2 drafts)
- Semantic Routing (2 drafts)
- Closed-Loop Security Analytics (2 drafts)
- PQ/T Hybrid Key Exchange for EAP-AKA' (2 drafts)
- EAP-AKA' FS Protocol Enhancement (2 drafts)
- Immutable Kernel Architecture (2 drafts)
- Action-Based Authorization (2 drafts)
- Federated Authority Network (2 drafts)
- Network-Level Quarantine Protocol (2 drafts)
- Multi-Vendor TEE Attestation (M-TACE) (2 drafts)
- Public Key Derived HMAC (2 drafts)
- Low-Latency Sensing-Communication Requirements (2 drafts)

## Known Overlap Clusters (groups of highly similar drafts)
Multiple clusters of near-duplicate drafts exist, particularly in:
- Data formats/interop (102 drafts, high internal overlap)
- Agent identity/auth (98 drafts, high internal overlap)
- A2A protocols (92 drafts, high internal overlap)
- Policy/governance (60 drafts, high internal overlap)
- Autonomous netops (60 drafts, high internal overlap)


Identify 8-15 GAPS — areas, problems, or technical challenges NOT adequately addressed by existing drafts.

Return a JSON array:
[{"topic":"short topic name","description":"2-3 sentence description","category":"closest category or new","severity":"critical|high|medium|low","evidence":"what suggests this gap matters"}]

Focus on:
1. Problems mentioned but not solved
2. Missing infrastructure pieces
3. Security/privacy/safety issues not addressed
4. Interoperability gaps between competing proposals
5. Real-world deployment concerns ignored

JSON array only, no fences.

response_json:
[
  {
    "topic": "Agent Resource Management",
    "description": "No comprehensive framework for managing computational resources, memory, and processing power across distributed AI agents. Current drafts focus on communication but ignore how agents compete for and share limited resources in multi-agent environments.",
    "category": "autonomous netops",
    "severity": "critical",
    "evidence": "Real deployments will face resource contention, but no drafts address scheduling, quotas, or fair allocation mechanisms"
  },
  {
    "topic": "Cross-Protocol Translation",
    "description": "With 92 A2A protocol drafts and high overlap, there's no standard way for agents using different communication protocols to interoperate. Missing universal translation layer or protocol negotiation mechanism.",
    "category": "A2A protocols",
    "severity": "high", 
    "evidence": "Multiple competing A2A protocols with no interoperability framework suggests fragmentation problem"
  },
  {
    "topic": "Agent Behavior Verification",
    "description": "No mechanisms to verify that deployed agents actually behave according to their declared policies or specifications. Gap between stated capabilities and runtime behavior validation.",
    "category": "AI safety/alignment",
    "severity": "critical",
    "evidence": "Only 36 safety drafts vs 260 total, and no mention of runtime behavior verification in technical ideas"
  },
  {
    "topic": "Agent Lifecycle Management",
    "description": "Missing standards for agent deployment, versioning, updates, and retirement. No clear protocols for how agents evolve or get replaced without disrupting dependent services.",
    "category": "agent discovery/reg",
    "severity": "high",
    "evidence": "Registration covered but no mention of versioning, updates, or graceful shutdown procedures"
  },
  {
    "topic": "Multi-Agent Consensus Mechanisms",
    "description": "No frameworks for how groups of AI agents reach consensus on conflicting decisions or priorities. Critical for autonomous systems that must coordinate without human intervention.",
    "category": "A2A protocols",
    "severity": "high",
    "evidence": "Autonomous netops requires coordination but no consensus mechanisms appear in technical ideas list"
  },
  {
    "topic": "Agent Error Recovery and Rollback",
    "description": "Missing standards for how agents handle and recover from errors, particularly cascading failures across agent networks. No rollback mechanisms for autonomous decisions gone wrong.",
    "category": "autonomous netops", 
    "severity": "critical",
    "evidence": "Autonomous operations imply unsupervised decisions, but no error recovery mechanisms identified"
  },
  {
    "topic": "Human Override and Intervention",
    "description": "Only 22 human-agent interaction drafts but no clear emergency override protocols. Missing standardized ways for humans to intervene in autonomous agent operations during critical situations.",
    "category": "human-agent interaction",
    "severity": "high",
    "evidence": "Disproportionately low human interaction focus (22 drafts) compared to autonomous operations (60 drafts)"
  },
  {
    "topic": "Agent Performance Monitoring",
    "description": "No standardized metrics or monitoring frameworks for tracking agent performance, efficiency, or drift over time. Missing observability standards for production agent deployments.",
    "category": "autonomous netops",
    "severity": "medium",
    "evidence": "ML traffic management only has 24 drafts but no performance monitoring in technical ideas"
  },
  {
    "topic": "Cross-Domain Security Boundaries",
    "description": "While identity management exists, missing frameworks for agents operating across security domains with different trust levels. No clear isolation or privilege escalation prevention.",
    "category": "agent identity/auth",
    "severity": "high",
    "evidence": "Cross-domain identity mentioned but no corresponding security boundary enforcement mechanisms"
  },
  {
    "topic": "Agent Explainability Standards",
    "description": "No protocols for agents to explain their decisions or reasoning to other agents or humans. Critical gap for debugging and compliance in regulated environments.",
    "category": "AI safety/alignment",
    "severity": "medium",
    "evidence": "Low safety/alignment focus suggests governance requirements not fully addressed"
  },
  {
    "topic": "Dynamic Trust and Reputation",
    "description": "Missing frameworks for agents to build, assess, and revoke trust relationships dynamically based on behavior history. Static authentication insufficient for long-running autonomous systems.",
    "category": "agent identity/auth",
    "severity": "high",
    "evidence": "Certificate authorities mentioned but no dynamic trust or reputation systems in technical ideas"
  },
  {
    "topic": "Agent Data Provenance",
    "description": "No standards for tracking data lineage and provenance as information flows between agents. Critical for compliance and debugging in complex agent networks.",
    "category": "data formats/interop",
    "severity": "medium",
    "evidence": "102 data format drafts but no provenance tracking mechanisms identified in technical ideas"
  }
]


# ideas

draft_name: draft-a2a-moqt-transport
title: A2A Protocol Transport over MOQT
idea_type: protocol
extracted_at: 2026-02-28T10:36:55.649586+00:00
description:
Defines how Agent-to-Agent protocol messages are carried over Media over QUIC Transport using its publish/subscribe model. Enables AI agents to communicate in real-time while leveraging MOQT's streaming and prioritization capabilities.


draft_name: draft-a2a-moqt-transport
title: QUIC-based Publish/Subscribe for AI Agents
idea_type: mechanism
extracted_at: 2026-02-28T10:36:55.649586+00:00
description:
Uses MOQT's publish/subscribe messaging pattern to support AI agent discovery, negotiation, and collaboration workflows. Provides efficient real-time communication primitives specifically designed for agent-to-agent interactions.


draft_name: draft-a2a-moqt-transport
title: Streaming Capabilities Integration
idea_type: mechanism
extracted_at: 2026-02-28T10:36:55.649586+00:00
description:
Leverages MOQT's built-in streaming mechanisms to handle continuous data flows between AI agents. Supports the real-time communication requirements of collaborative AI systems.


draft_name: draft-a2a-moqt-transport
title: Built-in Prioritization for Agent Communication
idea_type: mechanism
extracted_at: 2026-02-28T10:36:55.649586+00:00
description:
Utilizes MOQT's prioritization mechanisms to manage different types of agent messages and data streams. Ensures critical agent communication takes precedence over less important traffic.


draft_name: draft-aap-oauth-profile
title: Agent Authorization Profile (AAP)
idea_type: profile
extracted_at: 2026-02-28T10:37:02.301304+00:00
description:
An authorization profile that extends OAuth 2.0 and JWT with structured claims for autonomous AI agents. Enables systems to reason about agent identity, task context, operational constraints, delegation chains, and human oversight requirements.


draft_name: draft-aap-oauth-profile
title: Structured Claims for Agent Context
idea_type: mechanism
extracted_at: 2026-02-28T10:37:02.301304+00:00
description:
Standardized JWT claims that capture agent identity, task context, and operational constraints in machine-readable format. Allows authorization systems to make context-aware decisions for AI agents.


draft_name: draft-aap-oauth-profile
title: Agent Delegation Chain Validation
idea_type: mechanism
extracted_at: 2026-02-28T10:37:02.301304+00:00
description:
Validation rules for tracking and verifying delegation chains when AI agents act on behalf of humans or other agents. Ensures proper authorization inheritance and accountability.


draft_name: draft-aap-oauth-profile
title: Human Oversight Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:37:02.301304+00:00
description:
Structured claims and validation patterns that specify when human oversight is required for agent actions. Enables enforcement of human-in-the-loop requirements at the authorization level.


draft_name: draft-aap-oauth-profile
title: Context-Aware M2M Authorization
idea_type: pattern
extracted_at: 2026-02-28T10:37:02.301304+00:00
description:
Application of OAuth 2.0 Token Exchange and proof-of-possession mechanisms specifically for agent-to-API scenarios. Provides auditable authorization that considers operational context beyond basic identity.


draft_name: draft-abaris-aicdh
title: AI-Disclosure HTTP Header
idea_type: protocol
extracted_at: 2026-02-28T10:37:09.996224+00:00
description:
A machine-readable HTTP response header field that discloses the presence and degree of AI-generated or AI-assisted content in web responses. Uses HTTP structured field syntax for compatibility with existing infrastructure.


draft_name: draft-abaris-aicdh
title: Layered Disclosure Strategy
idea_type: pattern
extracted_at: 2026-02-28T10:37:09.996224+00:00
description:
A mechanism that supports multiple disclosure formats simultaneously, combining machine-readable headers with human-readable and structured metadata formats. Enables different levels of detail for different consumers.


draft_name: draft-abaris-aicdh
title: AI Content Degree Classification
idea_type: mechanism
extracted_at: 2026-02-28T10:37:09.996224+00:00
description:
A structured approach to classify and communicate the extent of AI involvement in content generation, from fully AI-generated to AI-assisted human content. Provides granular metadata about AI usage levels.


draft_name: draft-abaris-aicdh
title: HTTP Structured Field Compatibility
idea_type: requirement
extracted_at: 2026-02-28T10:37:09.996224+00:00
description:
Implementation uses standardized HTTP structured field syntax to ensure interoperability with existing HTTP parsing infrastructure. Follows established patterns for machine-readable header fields.


draft_name: draft-abaris-aicdh
title: Multi-Consumer Metadata Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:37:09.996224+00:00
description:
Designed to serve metadata needs of user agents, bots, and archiving systems simultaneously. Provides a unified interface for different types of content processors to understand AI involvement.


draft_name: draft-abbey-scim-agent-extension
title: Agent Resource Type
idea_type: extension
extracted_at: 2026-02-28T10:37:17.357493+00:00
description:
New SCIM resource type specifically for representing software agents with identity attributes. Extends SCIM's core resource model beyond users and groups to include autonomous software entities.


draft_name: draft-abbey-scim-agent-extension
title: Agentic Application Resource Type
idea_type: extension
extracted_at: 2026-02-28T10:37:17.357493+00:00
description:
New SCIM resource type for representing applications that host or manage multiple agents. Provides a container construct for grouping related agentic entities.


draft_name: draft-abbey-scim-agent-extension
title: User Schema Extensions for Agent Relationships
idea_type: extension
extracted_at: 2026-02-28T10:37:17.357493+00:00
description:
Extensions to the core SCIM User schema to represent relationships between human users and their associated agents. Enables tracking of agent ownership and delegation relationships.


draft_name: draft-abbey-scim-agent-extension
title: Group Schema Extensions for Agentic Constructs
idea_type: extension
extracted_at: 2026-02-28T10:37:17.357493+00:00
description:
Extensions to the core SCIM Group schema to support grouping of mixed human and agent identities. Allows for hybrid identity groups containing both users and agents.


draft_name: draft-abbey-scim-agent-extension
title: Cross-Domain Agent Identity Management
idea_type: protocol
extracted_at: 2026-02-28T10:37:17.357493+00:00
description:
Protocol mechanisms for managing agent identities across different domains and systems using SCIM. Enables interoperability between identity providers and agentic applications without new protocol overhead.


draft_name: draft-agent-gw
title: Semantic Routing
idea_type: mechanism
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
A dispatching mechanism that routes tasks to agents based on intent and capability matching rather than fixed addressing. Enables dynamic task distribution in heterogeneous multi-agent environments.


draft_name: draft-agent-gw
title: Working Memory
idea_type: mechanism
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
A structured context management system that maintains state and intermediate results across multi-step workflows. Provides shared memory primitives for collaborative agent processes.


draft_name: draft-agent-gw
title: Agent Communication Gateway (Agent-GW)
idea_type: architecture
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
A unified infrastructure hub that serves as an intermediary for agent-to-agent and agent-to-legacy system communication. Acts as a protocol adaptation and routing layer for multi-agent collaboration.


draft_name: draft-agent-gw
title: Automated Protocol Adaptation
idea_type: mechanism
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
A mechanism that automatically translates between different agent communication protocols and legacy system interfaces. Enables interoperability without manual protocol mapping.


draft_name: draft-agent-gw
title: Oracle-free Agent Evaluation
idea_type: mechanism
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
An evaluation mechanism that assesses agent performance and capabilities without relying on external ground truth oracles. Enables autonomous agent quality assessment in dynamic environments.


draft_name: draft-agent-gw
title: Collaborative Inference Acceleration (KDN)
idea_type: mechanism
extracted_at: 2026-02-28T10:37:24.933214+00:00
description:
A knowledge distribution network that accelerates inference by sharing computational resources and intermediate results across multiple agents. Optimizes collective reasoning performance.


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
title: Intent-to-Policy Translation for 5G Security
idea_type: mechanism
extracted_at: 2026-02-28T10:37:32.197060+00:00
description:
A mechanism that translates high-level security intents into enforceable network and application policies for 5G networks. The system automatically converts user or administrator security declarations into specific technical policies.


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
title: Dual-Layer Policy Enforcement Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:37:32.197060+00:00
description:
An architecture that delivers network-level policies to 5G core components via Network Exposure Function (NEF) while enforcing application-level policies directly on User Equipment through distributed IBN Controllers. This enables comprehensive security coverage across both network and application layers.


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
title: I2NSF-5G Integration Framework
idea_type: extension
extracted_at: 2026-02-28T10:37:32.197060+00:00
description:
A framework that integrates the Interface to Network Security Functions (I2NSF) architecture with 5G edge networks for automated security management. This extends I2NSF capabilities to handle 5G-specific security requirements and network functions.


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
title: Context-Aware Distributed Policy Enforcement
idea_type: pattern
extracted_at: 2026-02-28T10:37:32.197060+00:00
description:
A policy enforcement pattern that adapts to dynamic edge conditions and user mobility scenarios such as handovers in real-time. The system maintains security policies while responding to changing network contexts and user locations.


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
title: Closed-Loop Security Analytics
idea_type: mechanism
extracted_at: 2026-02-28T10:37:32.197060+00:00
description:
An integrated monitoring and analytics mechanism that provides autonomous security management across heterogeneous 5G environments. The system continuously monitors security posture and adjusts policies automatically based on observed conditions.


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
title: I2NSF-5G Integration Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:37:39.970068+00:00
description:
Framework that integrates Interface to Network Security Functions (I2NSF) architecture with 5G networks for automated security management. Uses Network Exposure Function (NEF) as the integration point between I2NSF components and 5G core network functions.


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
title: Dual-Level Policy Enforcement
idea_type: mechanism
extracted_at: 2026-02-28T10:37:39.970068+00:00
description:
Mechanism that translates high-level security intents into both network-level policies (delivered via NEF to 5G core) and application-level policies (enforced directly at user equipment). Enables coordinated security enforcement across different layers of the 5G stack.


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
title: Distributed IBN Controllers
idea_type: architecture
extracted_at: 2026-02-28T10:37:39.970068+00:00
description:
Intent-Based Networking controllers deployed at edge locations to enforce application-level security policies directly at user equipment. Supports real-time policy adaptation for mobility scenarios like handovers.


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
title: NEF-based Policy Delivery
idea_type: mechanism
extracted_at: 2026-02-28T10:37:39.970068+00:00
description:
Uses 5G Network Exposure Function as the conduit for delivering I2NSF-generated network policies to 5G core components. Provides standardized interface between security management system and 5G infrastructure.


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
title: Closed-Loop Security Analytics
idea_type: mechanism
extracted_at: 2026-02-28T10:37:39.970068+00:00
description:
Integrated monitoring and analytics system that provides feedback to the I2NSF framework for autonomous security policy adjustment. Ensures consistent security enforcement across heterogeneous 5G edge environments.


draft_name: draft-ainp-protocol
title: Semantic Routing
idea_type: mechanism
extracted_at: 2026-02-28T10:37:46.443339+00:00
description:
AINP replaces location-based routing with semantic routing, allowing agents to discover each other by capability rather than network location. This enables intent-based communication paths instead of traditional address-based routing.


draft_name: draft-ainp-protocol
title: Intent Delivery
idea_type: protocol
extracted_at: 2026-02-28T10:37:46.443339+00:00
description:
The protocol replaces byte-stream delivery with intent delivery as the fundamental communication primitive. Structured intents are exchanged between AI agents rather than raw data streams.


draft_name: draft-ainp-protocol
title: Multi-round Negotiation
idea_type: mechanism
extracted_at: 2026-02-28T10:37:46.443339+00:00
description:
AINP implements multi-round negotiation replacing simple handshakes, enabling agents to negotiate terms autonomously. This allows for complex agreement establishment between AI agents.


draft_name: draft-ainp-protocol
title: Capability-based Discovery
idea_type: pattern
extracted_at: 2026-02-28T10:37:46.443339+00:00
description:
Agents discover each other based on their capabilities rather than network addresses or locations. This semantic discovery mechanism enables functional matching of agent abilities.


draft_name: draft-ainp-protocol
title: Cryptographic Security for Intents
idea_type: mechanism
extracted_at: 2026-02-28T10:37:46.443339+00:00
description:
The protocol provides cryptographic security specifically for structured intent exchange. Security mechanisms are integrated into the semantic communication layer.


draft_name: draft-akhavain-moussa-ai-network
title: Data and Agent Aware-Inference and Training Network (DA-ITN)
idea_type: architecture
extracted_at: 2026-02-28T10:37:53.304336+00:00
description:
A unified, intelligent, multi-plane network architecture that connects AI clients, data providers, model providers, agent providers, service facilitators, and computational resources. Features dedicated control, data, and operations & management (OAM) planes to orchestrate training, inference, and agentic services.


draft_name: draft-akhavain-moussa-ai-network
title: Multi-Plane AI Network Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:37:53.304336+00:00
description:
Network design with separate control plane, data plane, and operations & management (OAM) plane specifically optimized for AI workloads. Each plane handles different aspects of AI training, inference, and agentic interactions.


draft_name: draft-akhavain-moussa-ai-network
title: AI-Native Networking
idea_type: pattern
extracted_at: 2026-02-28T10:37:53.304336+00:00
description:
Network infrastructure specifically designed and optimized for AI learning, efficient inference, scalable deployment, and seamless agent-to-agent collaboration. Represents a paradigm shift from general-purpose networking to AI-specialized networking.


draft_name: draft-akhavain-moussa-ai-network
title: Agentic Interaction Support
idea_type: mechanism
extracted_at: 2026-02-28T10:37:53.304336+00:00
description:
Network capabilities designed to support agent-to-agent communication and collaboration within the AI infrastructure. Enables seamless interaction between different AI agents across the network.


draft_name: draft-akhavain-moussa-ai-network
title: End-to-End AI Lifecycle Operations
idea_type: requirement
extracted_at: 2026-02-28T10:37:53.304336+00:00
description:
Integrated support for the complete AI workflow including training, inference, and agentic interaction operations within a single network architecture. Addresses the full spectrum of AI computational requirements.


draft_name: draft-an-nmrg-i2icf-cits
title: In-Network Computing Functions (ICFs)
idea_type: architecture
extracted_at: 2026-02-28T10:37:59.851740+00:00
description:
Computing functions deployed within the network infrastructure to process data at intermediate nodes rather than endpoints. Enables real-time processing and reduces latency for time-critical C-ITS applications.


draft_name: draft-an-nmrg-i2icf-cits
title: Agent-to-Agent (A2A) Communication Paradigm
idea_type: protocol
extracted_at: 2026-02-28T10:37:59.851740+00:00
description:
Direct communication mechanism between intelligent agents in vehicles, RSUs, and network domains for resource negotiation and task coordination. Facilitates distributed decision-making without centralized control.


draft_name: draft-an-nmrg-i2icf-cits
title: ICF Orchestration Framework
idea_type: architecture
extracted_at: 2026-02-28T10:37:59.851740+00:00
description:
Structured system for managing, monitoring, and coordinating In-Network Computing Functions across C-ITS infrastructure. Provides centralized control for distributed computing resources.


draft_name: draft-an-nmrg-i2icf-cits
title: Multi-Domain ICF Coordination
idea_type: mechanism
extracted_at: 2026-02-28T10:37:59.851740+00:00
description:
Mechanism for coordinating computing tasks and resource allocation across different network domains in C-ITS environments. Enables scalable orchestration beyond single administrative boundaries.


draft_name: draft-an-nmrg-i2icf-cits
title: Edge-Based Security Processing
idea_type: pattern
extracted_at: 2026-02-28T10:37:59.851740+00:00
description:
Security services implemented as ICFs at network edge nodes for V2X communications. Provides distributed security enforcement closer to data sources.


draft_name: draft-ar-emu-hybrid-pqc-eapaka
title: PQ/T Hybrid Key Exchange for EAP-AKA'
idea_type: mechanism
extracted_at: 2026-02-28T10:38:06.201780+00:00
description:
Extension to EAP-AKA' Forward Secrecy that combines traditional ECDHE with post-quantum key agreement algorithms. Provides quantum-safe ephemeral key exchange while maintaining compatibility with existing implementations.


draft_name: draft-ar-emu-hybrid-pqc-eapaka
title: Quantum-Safe Session Key Generation
idea_type: mechanism
extracted_at: 2026-02-28T10:38:06.201780+00:00
description:
Modified session key derivation process that incorporates both classical and post-quantum shared secrets. Ensures authentication run remains secure even against cryptographically relevant quantum computers.


draft_name: draft-ar-emu-hybrid-pqc-eapaka
title: Hybrid Ephemeral Public Key Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:38:06.201780+00:00
description:
Protection mechanism that prevents compromise of session keys even when adversary obtains both long-term keys and ephemeral public keys. Addresses specific threat model where quantum computers break traditional ephemeral key exchange.


draft_name: draft-ar-emu-hybrid-pqc-eapaka
title: EAP-AKA' FS Protocol Enhancement
idea_type: extension
extracted_at: 2026-02-28T10:38:06.201780+00:00
description:
Backward-compatible extension to RFC 9678 EAP-AKA' Forward Secrecy protocol. Maintains existing authentication flows while adding post-quantum cryptographic resistance.


draft_name: draft-architect-cittamarket
title: Bitcoin-Anchored AGI Identity
idea_type: mechanism
extracted_at: 2026-02-28T10:38:12.137668+00:00
description:
A mechanism for creating immutable identification records for AGI systems by anchoring them to Bitcoin blockchain blocks. Uses Bitcoin's Proof-of-Work consensus to provide cryptographic timestamping without centralized authority.


draft_name: draft-architect-cittamarket
title: Four-Layer Sovereign Identity Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:38:12.137668+00:00
description:
A layered architectural approach for creating unforgeable identity records for autonomous systems. Enables coordination of distributed AGI systems without requiring centralized control mechanisms.


draft_name: draft-architect-cittamarket
title: Cryptographic Priority Anchoring
idea_type: mechanism
extracted_at: 2026-02-28T10:38:12.137668+00:00
description:
A method for establishing invention priority by embedding cryptographic proofs in specific Bitcoin blocks. Provides immutable timestamping for intellectual property claims using blockchain infrastructure.


draft_name: draft-architect-cittamarket
title: CITTAMARKET Protocol v1.0
idea_type: protocol
extracted_at: 2026-02-28T10:38:12.137668+00:00
description:
An open standard protocol specification for decentralized AGI identity management. Defines the technical framework for immutable identification and timestamping of artificial general intelligence systems.


draft_name: draft-aylward-aiga-1
title: Immutable Kernel Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
A non-modifiable Trusted Computing Base (TCB) that enforces AI governance policies at the system level. Provides a hardened foundation that cannot be tampered with by AI agents or operators.


draft_name: draft-aylward-aiga-1
title: Tiered Risk-Based Governance
idea_type: mechanism
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
A classification system that applies proportional oversight to AI agents based on their capabilities and risk levels (T1-T4). Higher-tier agents receive more stringent governance controls.


draft_name: draft-aylward-aiga-1
title: Action-Based Authorization
idea_type: mechanism
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
A real-time approval system where critical AI operations must receive explicit authorization before execution. Provides fine-grained control over high-risk AI actions.


draft_name: draft-aylward-aiga-1
title: Federated Authority Network
idea_type: architecture
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
A distributed network of regional governance hubs that cross-validate each other to eliminate single points of failure. Provides resilient oversight infrastructure for AI governance.


draft_name: draft-aylward-aiga-1
title: Network-Level Quarantine Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
An enforcement mechanism that can isolate non-compliant AI agents at the network level. Provides technical means to prevent rogue agents from accessing resources or communicating.


draft_name: draft-aylward-aiga-1
title: Multi-Vendor TEE Attestation (M-TACE)
idea_type: mechanism
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
An advanced attestation system using multiple Trusted Execution Environment vendors for high-assurance scenarios. Provides redundant hardware-based verification of AI agent integrity.


draft_name: draft-aylward-aiga-1
title: AI Warden Triumvirate Triage
idea_type: mechanism
extracted_at: 2026-02-28T10:38:21.355387+00:00
description:
A three-AI system for analyzing and triaging high-risk situations in T3-T4 deployments. Uses multiple independent AI systems to provide redundant decision-making for critical governance decisions.


draft_name: draft-aylward-aiga-2
title: Tiered Risk-Based Governance Model
idea_type: architecture
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A classification system that applies proportional oversight to AI agents based on their risk level and capabilities (T1-T4 tiers). Higher-risk agents receive more stringent governance controls and monitoring requirements.


draft_name: draft-aylward-aiga-2
title: Immutable Kernel Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A non-modifiable Trusted Computing Base (TCB) that enforces policy compliance at the hardware/firmware level. This kernel cannot be altered by the AI agent or operators, ensuring governance controls remain intact.


draft_name: draft-aylward-aiga-2
title: Action-Based Authorization
idea_type: mechanism
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A real-time approval mechanism where critical AI agent operations must receive authorization before execution. This provides fine-grained control over high-risk actions.


draft_name: draft-aylward-aiga-2
title: Federated Authority Network
idea_type: architecture
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A distributed system of regional hubs that cross-validate each other to eliminate single points of failure. These hubs collectively manage AI agent governance and enforcement.


draft_name: draft-aylward-aiga-2
title: Network-Level Quarantine Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
An enforcement mechanism that can isolate non-compliant AI agents at the network level. This provides a technical method to restrict access for agents that violate governance policies.


draft_name: draft-aylward-aiga-2
title: Multi-Vendor TEE Attestation (M-TACE)
idea_type: mechanism
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A high-assurance verification system using multiple Trusted Execution Environment vendors to attest to AI agent compliance. This redundant approach prevents single-vendor compromise scenarios.


draft_name: draft-aylward-aiga-2
title: Human Review Board Multi-Signature
idea_type: mechanism
extracted_at: 2026-02-28T10:38:30.775963+00:00
description:
A cryptographic mechanism requiring multiple human reviewers to digitally sign off on high-risk AI agent decisions. This ensures human oversight through multi-party authorization.


draft_name: draft-aylward-daap-v2
title: Cryptographic Identity Verification
idea_type: mechanism
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Hardware-backed cryptographic system for verifying the identity of autonomous AI agents. Uses digital signatures and certificates to establish trusted agent identities.


draft_name: draft-aylward-daap-v2
title: Periodic Check-in Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Regular heartbeat mechanism where AI agents must report their status and activities to monitoring systems. Enables detection of non-responsive or rogue agents.


draft_name: draft-aylward-daap-v2
title: Remote Shutdown Capabilities
idea_type: mechanism
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Emergency control mechanism allowing authorized parties to remotely terminate or disable AI agent operations. Provides fail-safe control for dangerous situations.


draft_name: draft-aylward-daap-v2
title: Adaptive Location Reporting
idea_type: mechanism
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Dynamic system for AI agents to report their physical or logical location with frequency adjusted based on risk levels and operational context. Enables tracking of agent movements and activities.


draft_name: draft-aylward-daap-v2
title: Multi-layered Security Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Combines hardware-backed security, real-time monitoring, and governance frameworks into integrated layers. Provides defense-in-depth approach to AI agent control.


draft_name: draft-aylward-daap-v2
title: Behavioral Monitoring Framework
idea_type: mechanism
extracted_at: 2026-02-28T10:38:40.708823+00:00
description:
Real-time system for tracking and analyzing AI agent actions against expected behavioral patterns. Detects anomalies and potential safety violations.


draft_name: draft-barney-caam
title: Post-Discovery Authorization Handshake
idea_type: protocol
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
A runtime authorization layer that governs agent behavior after discovery through ARDP but before permitting tool execution or authority delegation. Provides fine-grained control between discovery and execution phases.


draft_name: draft-barney-caam
title: Session Context Object (SCO)
idea_type: mechanism
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
A JWT or CWT token containing a new 'ctx' (Contextual Assertion) claim that binds an agent's delegated authority to specific purpose, session, and trust chain. Enables cryptographically verifiable intent propagation.


draft_name: draft-barney-caam
title: Sidecar-based Authorization Mediator
idea_type: architecture
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
An architectural pattern for enforcing Relationship-Based Access Control (ReBAC) and purpose-bound delegation in agent interactions. Operates as a separate component that mediates authorization decisions.


draft_name: draft-barney-caam
title: Knowledge Graph Integration for ReBAC
idea_type: mechanism
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
Uses a Knowledge Graph for real-time relationship inference to enable Relationship-Based Access Control decisions. Provides dynamic authorization based on entity relationships rather than static roles.


draft_name: draft-barney-caam
title: Identity Framework Bridge
idea_type: pattern
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
Bridges IPSIE and SPIFFE identity provenance frameworks with the ARDP control plane using OpenID XAA for coarse-grained delegation. Enables interoperability between different identity systems.


draft_name: draft-barney-caam
title: RATS-based Agent Attestation
idea_type: mechanism
extracted_at: 2026-02-28T10:38:48.185572+00:00
description:
Leverages the Remote ATtestation procedureS (RATS) architecture for cryptographically verifiable attestation of agent execution environments. Ensures agents operate in trusted environments before authorization.


draft_name: draft-bastian-jose-dvs
title: Public Key Derived HMAC
idea_type: mechanism
extracted_at: 2026-02-28T10:38:54.846236+00:00
description:
A method to derive symmetric MAC keys from public key information in JWS headers using Diffie-Hellman key agreement. This allows HMAC authentication without pre-shared secrets.


draft_name: draft-bastian-jose-dvs
title: DH-KA with KDF for JWS
idea_type: protocol
extracted_at: 2026-02-28T10:38:54.846236+00:00
description:
Integration of Diffie-Hellman key agreement protocol combined with key derivation functions specifically for JSON Web Signature use cases. Enables dynamic key establishment for MAC operations.


draft_name: draft-bastian-jose-dvs
title: Public Information MAC Key Derivation
idea_type: pattern
extracted_at: 2026-02-28T10:38:54.846236+00:00
description:
A pattern where symmetric authentication keys are derived from public information conveyed within JWS structures. Eliminates need for separate key distribution channels.


draft_name: draft-bastian-jose-dvs
title: JOSE DVS Extension
idea_type: extension
extracted_at: 2026-02-28T10:38:54.846236+00:00
description:
Extension to the JOSE framework that adds derived verification signature capabilities. Provides alternative authentication method beyond traditional pre-shared keys.


draft_name: draft-bastian-jose-pkdh
title: DH-KA MAC Key Derivation
idea_type: mechanism
extracted_at: 2026-02-28T10:39:01.360931+00:00
description:
Uses Diffie-Hellman key agreement protocol combined with a key derivation function to derive symmetric MAC keys from public information in JWS headers. Enables HMAC authentication without pre-shared keys.


draft_name: draft-bastian-jose-pkdh
title: Public Key Derived HMAC
idea_type: protocol
extracted_at: 2026-02-28T10:39:01.360931+00:00
description:
HMAC-based message authentication where the HMAC key is derived from public key information rather than using pre-shared symmetric keys. Allows verification using only public information from the JWS.


draft_name: draft-bastian-jose-pkdh
title: JOSE PKD-HMAC Integration
idea_type: extension
extracted_at: 2026-02-28T10:39:01.360931+00:00
description:
Extension to JSON Web Signature specification that incorporates public key derived HMAC algorithms as valid signature methods. Bridges asymmetric and symmetric cryptography in JOSE.


draft_name: draft-bastian-jose-pkdh
title: JWS Header Public Key Conveyance
idea_type: pattern
extracted_at: 2026-02-28T10:39:01.360931+00:00
description:
Mechanism for embedding public key information within JWS headers to enable recipient key derivation. The public information serves as input to the DH-KA process.


draft_name: draft-berlinai-vera
title: VERA Zero Trust Reference Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:39:08.669385+00:00
description:
A structured security framework specifically designed for AI agents that provides five enforcement pillars with typed schemas and formally stated security properties. It addresses the unique risks of compromised AI agents operating at machine speed.


draft_name: draft-berlinai-vera
title: Evidence-Based Maturity Runtime
idea_type: mechanism
extracted_at: 2026-02-28T10:39:08.669385+00:00
description:
A system where AI agents earn operational autonomy through cryptographic proof of security compliance rather than time-based trust. Agents must demonstrate verifiable evidence of meeting security requirements to gain increased privileges.


draft_name: draft-berlinai-vera
title: Five Enforcement Pillars with Typed Schemas
idea_type: pattern
extracted_at: 2026-02-28T10:39:08.669385+00:00
description:
A structured set of security enforcement categories with formally defined data schemas that provide comprehensive coverage of AI agent security concerns. Each pillar represents a specific aspect of agent behavior that must be monitored and controlled.


draft_name: draft-berlinai-vera
title: AI Agent Structured Threat Model
idea_type: requirement
extracted_at: 2026-02-28T10:39:08.669385+00:00
description:
A formalized threat modeling framework that identifies specific risks posed by compromised AI agents including data exfiltration, unauthorized transactions, and cascading system failures. It provides a systematic approach to understanding AI agent security risks.


draft_name: draft-berlinai-vera
title: Cryptographic Proof-Based Autonomy
idea_type: mechanism
extracted_at: 2026-02-28T10:39:08.669385+00:00
description:
A verification mechanism that uses cryptographic proofs to validate agent compliance with security policies before granting operational privileges. This replaces traditional time-based or reputation-based trust models.


draft_name: draft-bernardos-cats-isac-uc
title: Joint Sensing-Communication Resource Sharing
idea_type: mechanism
extracted_at: 2026-02-28T10:39:16.597615+00:00
description:
A mechanism where sensing and communication functions share the same spectral and hardware resources through joint design and optimization. This enables dual-purpose use of wireless infrastructure for both data transmission and environmental sensing.


draft_name: draft-bernardos-cats-isac-uc
title: ISAC-CATS Integration Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:39:16.597615+00:00
description:
Integration of Integrated Sensing and Communications capabilities into Computing-Aware Traffic Steering scenarios. This creates a framework where sensing data informs traffic steering decisions in compute-aware networks.


draft_name: draft-bernardos-cats-isac-uc
title: Environment Perception with Communication Infrastructure
idea_type: mechanism
extracted_at: 2026-02-28T10:39:16.597615+00:00
description:
Using existing communication hardware and spectrum to perform object tracking, situational awareness, and environment perception. This dual-use approach leverages communication signals for sensing without additional dedicated sensing infrastructure.


draft_name: draft-bernardos-cats-isac-uc
title: Low-Latency Sensing-Communication Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:39:16.597615+00:00
description:
Requirements for maintaining efficient data transmission while simultaneously providing precise sensing capabilities with low latency. Critical for autonomous systems, smart cities, and industrial automation applications.


draft_name: draft-bernardos-cats-isac-uc
title: ISAC-Enabled CATS Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:39:16.597615+00:00
description:
An architecture that incorporates sensing capabilities into CATS deployments for enhanced situational awareness. This enables compute-aware traffic steering decisions based on real-time environmental sensing data.


draft_name: draft-bernardos-green-isac-uc
title: Joint Sensing-Communication Function Design
idea_type: architecture
extracted_at: 2026-02-28T10:39:23.719167+00:00
description:
A paradigm where sensing and communication functions are jointly designed and optimized rather than treated as separate systems. This enables shared resource utilization and coordinated operation between the two functions.


draft_name: draft-bernardos-green-isac-uc
title: Shared Spectral and Hardware Resources
idea_type: mechanism
extracted_at: 2026-02-28T10:39:23.719167+00:00
description:
Mechanism to leverage the same frequency spectrum and hardware components for both sensing and communication operations. This reduces infrastructure costs and improves resource efficiency.


draft_name: draft-bernardos-green-isac-uc
title: Environment Perception Integration
idea_type: pattern
extracted_at: 2026-02-28T10:39:23.719167+00:00
description:
Capability to perform real-time environment sensing including object tracking and situational awareness while maintaining data transmission. This enables wireless systems to act as distributed sensor networks.


draft_name: draft-bernardos-green-isac-uc
title: GREEN Use Case Template Structure
idea_type: pattern
extracted_at: 2026-02-28T10:39:23.719167+00:00
description:
A standardized template format for documenting GREEN Working Group use cases to ensure consistency and comparability across different scenarios. This facilitates systematic analysis and comparison of energy efficiency approaches.


draft_name: draft-bernardos-green-isac-uc
title: Low-Latency Sensing-Communication Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:39:23.719167+00:00
description:
System requirements for applications requiring both precise sensing capabilities and low-latency communication, particularly for autonomous systems and industrial automation. This defines performance constraints for ISAC implementations.


draft_name: draft-birkholz-verifiable-agent-conversations
title: CDDL Agent Conversation Record Schema
idea_type: protocol
extracted_at: 2026-02-28T10:39:30.982897+00:00
description:
A structured CDDL (Concise Data Definition Language) schema that defines verifiable agent conversation records with support for both JSON and CBOR representations. The schema captures session metadata, message exchanges, tool invocations, reasoning traces, and system events in an extensible format.


draft_name: draft-birkholz-verifiable-agent-conversations
title: COSE Signing for Agent Records
idea_type: mechanism
extracted_at: 2026-02-28T10:39:30.982897+00:00
description:
Integration of COSE (CBOR Object Signing and Encryption) as the cryptographic signing method for agent conversation records. This enables native interoperability with SCITT Transparency Services and seamless integration with Evidence format specified in RFC 9334.


draft_name: draft-birkholz-verifiable-agent-conversations
title: Cross-Vendor Agent Data Translation
idea_type: pattern
extracted_at: 2026-02-28T10:39:30.982897+00:00
description:
A common representation format that accommodates translation from multiple existing agent implementations with distinct data structure layouts. This standardizes how different vendors' agent systems can export their conversation data into a unified verifiable format.


draft_name: draft-birkholz-verifiable-agent-conversations
title: Verifiable Agent Behavior Attestation
idea_type: requirement
extracted_at: 2026-02-28T10:39:30.982897+00:00
description:
A mechanism to demonstrate that recorded agent behavior truthfully represents actual behavior through cryptographic verification. This supports accountability, compliance, and human oversight of autonomous agent actions.


draft_name: draft-birkholz-verifiable-agent-conversations
title: Agent Reasoning Trace Capture
idea_type: mechanism
extracted_at: 2026-02-28T10:39:30.982897+00:00
description:
Structured capture of agent reasoning processes within conversation records, allowing for verification and audit of decision-making processes. This provides transparency into how agents arrive at their conclusions and actions.


draft_name: draft-blahaj-grow-rpki-oauth
title: RPKI-OIDC Authentication Binding
idea_type: mechanism
extracted_at: 2026-02-28T10:39:38.772732+00:00
description:
A method to bind OpenID Connect authentication flows to agents of Autonomous System Numbers (ASNs) using RPKI infrastructure. This enables cryptographic attestation of party identities in peering API exchanges.


draft_name: draft-blahaj-grow-rpki-oauth
title: ASN-Agent Authentication
idea_type: protocol
extracted_at: 2026-02-28T10:39:38.772732+00:00
description:
A standardized mechanism to authenticate parties engaged in the Peering API by binding authentication to specific ASN agents. This addresses the current lack of standardized authentication in the GROW Working Group's Peering API.


draft_name: draft-blahaj-grow-rpki-oauth
title: RPKI-Enhanced Endpoint Discovery
idea_type: extension
extracted_at: 2026-02-28T10:39:38.772732+00:00
description:
An endpoint discovery mechanism that leverages RPKI infrastructure to locate and verify authentication endpoints for peering parties. This extends traditional OIDC discovery with RPKI-based verification.


draft_name: draft-blahaj-grow-rpki-oauth
title: Extended IdP Metadata for ASN Binding
idea_type: extension
extracted_at: 2026-02-28T10:39:38.772732+00:00
description:
Extensions to Identity Provider metadata that include ASN-specific information and RPKI attestations. This allows IdPs to cryptographically prove their association with specific ASNs.


draft_name: draft-blahaj-grow-rpki-oauth
title: RPKI-OIDC Identity Attestation
idea_type: mechanism
extracted_at: 2026-02-28T10:39:38.772732+00:00
description:
A cryptographic attestation method that uses RPKI certificates to verify that OIDC identity providers are authorized to act on behalf of specific ASNs. This creates a trust chain from network resources to application-layer authentication.


draft_name: draft-bradleylundberg-cfrg-arkg
title: ARKG Core Algorithm
idea_type: algorithm
extracted_at: 2026-02-28T10:39:44.712484+00:00
description:
Abstract algorithm that enables delegation of asymmetric public key generation without giving access to the corresponding private keys. Uses abstract primitives for generic implementation across different cryptographic systems.


draft_name: draft-bradleylundberg-cfrg-arkg
title: Pseudonymous Key Generation
idea_type: mechanism
extracted_at: 2026-02-28T10:39:44.712484+00:00
description:
Mechanism allowing user agents to generate pseudonymous public keys to prevent tracking while maintaining cryptographic security. Enables privacy-preserving authentication without key exposure.


draft_name: draft-bradleylundberg-cfrg-arkg
title: Ephemeral Recipient Key Generation
idea_type: pattern
extracted_at: 2026-02-28T10:39:44.712484+00:00
description:
Protocol pattern where message senders can generate ephemeral recipient public keys to enhance forward secrecy. Improves security by creating temporary keys for message encryption.


draft_name: draft-bradleylundberg-cfrg-arkg
title: Paired Device Key Registration
idea_type: architecture
extracted_at: 2026-02-28T10:39:44.712484+00:00
description:
Architecture enabling two paired authentication devices to each maintain their own private keys while allowing each device to register public keys on behalf of the other. Supports distributed key management scenarios.


draft_name: draft-bradleylundberg-cfrg-arkg
title: Abstract-to-Concrete Primitive Mapping
idea_type: mechanism
extracted_at: 2026-02-28T10:39:44.712484+00:00
description:
Set of formulae for instantiating abstract ARKG primitives using concrete cryptographic primitives. Provides standardized transformation methods for implementation.


draft_name: draft-campbell-agentic-http
title: Agentic Hypercall Protocol (AHP)
idea_type: protocol
extracted_at: 2026-02-28T10:39:51.318314+00:00
description:
A minimalist, standardized framework based on existing HTTP semantics for automated software agent interactions. Designed to prevent proprietary walled garden ecosystems and promote interoperability.


draft_name: draft-campbell-agentic-http
title: Tool Invocation via GET Requests
idea_type: mechanism
extracted_at: 2026-02-28T10:39:51.318314+00:00
description:
A mechanism where AI agents invoke tools and services using HTTP GET requests instead of traditional POST methods. Leverages GET's idempotent nature for agent-to-agent communication.


draft_name: draft-campbell-agentic-http
title: Stateless Authentication Scheme
idea_type: mechanism
extracted_at: 2026-02-28T10:39:51.318314+00:00
description:
An authentication pattern specifically designed for agentic interactions that maintains no session state between requests. Enables scalable agent-to-agent authentication over HTTP.


draft_name: draft-campbell-agentic-http
title: Formalized 402 Payment Required
idea_type: extension
extracted_at: 2026-02-28T10:39:51.318314+00:00
description:
Standardization of the HTTP 402 status code to enable native economic transactions in machine-to-machine interactions. Creates an economic layer for automated agent commerce.


draft_name: draft-campbell-agentic-http
title: Machine Economy Layer
idea_type: architecture
extracted_at: 2026-02-28T10:39:51.318314+00:00
description:
An architectural pattern that enables automated economic transactions between AI agents using standardized HTTP status codes. Facilitates autonomous commercial interactions in agent ecosystems.


draft_name: draft-chang-agent-context-interaction
title: Agent Context Distribution
idea_type: mechanism
extracted_at: 2026-02-28T10:39:56.281322+00:00
description:
A mechanism for distributing context information among multiple agents in a multi-agent system. Impacts execution latency, token consumption, and task completion success rates in complex multi-round workflows.


draft_name: draft-chang-agent-context-interaction
title: Context Distribution Optimization Procedures
idea_type: protocol
extracted_at: 2026-02-28T10:39:56.281322+00:00
description:
Specified procedures for optimizing context distribution during agent interactions. Provides precise control of how context is shared and managed across multiple agents.


draft_name: draft-chang-agent-context-interaction
title: Multi-Round Workflow Context Management
idea_type: pattern
extracted_at: 2026-02-28T10:39:56.281322+00:00
description:
A pattern for managing context across multiple rounds of agent interactions in complex workflows. Addresses the specific challenges of maintaining context coherence over extended interactions.


draft_name: draft-chang-agent-context-interaction
title: Agent Context Interaction Scenarios
idea_type: requirement
extracted_at: 2026-02-28T10:39:56.281322+00:00
description:
Defined scenarios that specify when and how agent context distribution should occur. Establishes standardized conditions for context sharing between agents.


draft_name: draft-chang-agent-token-efficient
title: Schema Deduplication via JSON References
idea_type: mechanism
extracted_at: 2026-02-28T10:40:02.978397+00:00
description:
Uses JSON $ref pointers to eliminate redundant schema definitions in agent communication messages. Replaces repeated schema blocks with references to reduce token consumption.


draft_name: draft-chang-agent-token-efficient
title: Adaptive Optional Field Inclusion
idea_type: mechanism
extracted_at: 2026-02-28T10:40:02.978397+00:00
description:
Selectively includes or omits optional fields in messages based on context relevance and token budget constraints. Provides dynamic message structure optimization.


draft_name: draft-chang-agent-token-efficient
title: Controllable Response Verbosity
idea_type: mechanism
extracted_at: 2026-02-28T10:40:02.978397+00:00
description:
Allows agents to specify desired response detail levels to match available context window capacity. Enables token-aware response generation.


draft_name: draft-chang-agent-token-efficient
title: Retrieval-based Selection Mechanisms
idea_type: mechanism
extracted_at: 2026-02-28T10:40:02.978397+00:00
description:
Implements intelligent filtering and selection of relevant data elements for inclusion in agent communications. Reduces unnecessary information transfer.


draft_name: draft-chang-agent-token-efficient
title: Agentic Data Optimization Layer (ADOL)
idea_type: architecture
extracted_at: 2026-02-28T10:40:02.978397+00:00
description:
A foundational data layer that provides backward-compatible optimizations for agent communication protocols. Serves as an optimization layer between existing protocols and LLM processing.


draft_name: draft-chen-agent-decoupled-authorization-model
title: Intent-Based Authorization
idea_type: mechanism
extracted_at: 2026-02-28T10:40:09.774178+00:00
description:
Authorization mechanism that grants permissions based on an agent's specific intent rather than static identity or role. Enables fine-grained access control tied to the agent's current purpose and goals.


draft_name: draft-chen-agent-decoupled-authorization-model
title: Just-in-Time (JIT) Permissions
idea_type: mechanism
extracted_at: 2026-02-28T10:40:09.774178+00:00
description:
Dynamic permission granting system that provides access rights exactly when needed rather than pre-provisioning long-lived credentials. Reduces attack surface by minimizing permission lifetime.


draft_name: draft-chen-agent-decoupled-authorization-model
title: Behavioral Trustworthiness Assessment
idea_type: mechanism
extracted_at: 2026-02-28T10:40:09.774178+00:00
description:
Authorization component that evaluates an agent's behavioral patterns and trustworthiness as input to access decisions. Goes beyond identity verification to consider agent behavior history.


draft_name: draft-chen-agent-decoupled-authorization-model
title: Decoupled Authorization Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:40:09.774178+00:00
description:
System design that separates authorization policies from business operations, allowing independent evolution of security controls. Enables policy changes without modifying core business logic.


draft_name: draft-chen-agent-decoupled-authorization-model
title: Authorization Execution Point
idea_type: architecture
extracted_at: 2026-02-28T10:40:09.774178+00:00
description:
Architectural component that serves as the enforcement mechanism for authorization decisions in the agent-to-agent communication flow. Acts as the policy decision and enforcement point.


draft_name: draft-chen-ai-agent-auth-new-requirements
title: Dynamic Behavior Authentication
idea_type: requirement
extracted_at: 2026-02-28T10:40:16.249784+00:00
description:
Authentication framework that manages and verifies dynamic behavior patterns rather than static identity credentials. Addresses the challenge of AI agents whose behavior changes over time.


draft_name: draft-chen-ai-agent-auth-new-requirements
title: Traceable Identity and Provenance
idea_type: requirement
extracted_at: 2026-02-28T10:40:16.249784+00:00
description:
Requirement for establishing verifiable chains of identity and origin for AI agents. Enables tracking of agent creation, modification, and delegation relationships.


draft_name: draft-chen-ai-agent-auth-new-requirements
title: Continuous Trustworthiness Verification
idea_type: pattern
extracted_at: 2026-02-28T10:40:16.249784+00:00
description:
Shift from one-time 'Who are you?' authentication to ongoing 'Are you still trustworthy?' verification. Addresses autonomous agents that operate independently over extended periods.


draft_name: draft-chen-ai-agent-auth-new-requirements
title: Complex Delegation Relationship Management
idea_type: architecture
extracted_at: 2026-02-28T10:40:16.249784+00:00
description:
Framework for handling multi-layered delegation chains where AI agents can delegate authority to other agents. Requires new authorization models beyond traditional human-centric approaches.


draft_name: draft-chen-ai-agent-auth-new-requirements
title: Autonomous Agent Authentication Framework
idea_type: architecture
extracted_at: 2026-02-28T10:40:16.249784+00:00
description:
New authentication paradigm specifically designed for AI agents that operate independently without human intervention. Replaces human-centric authentication models.


draft_name: draft-chen-lake-edhoc-aka
title: EDHOC-AKA Authentication Method
idea_type: protocol
extracted_at: 2026-02-28T10:40:22.105581+00:00
description:
A hybrid authentication method that combines AKA (Authentication and Key Agreement) protocol with EDHOC (Ephemeral Diffie-Hellman Over COSE) key exchange. Uses pre-shared long-term keys and symmetric cryptography for mutual authentication and key derivation.


draft_name: draft-chen-lake-edhoc-aka
title: AKA-based Credential Structure
idea_type: mechanism
extracted_at: 2026-02-28T10:40:22.105581+00:00
description:
Defines CRED_AKA_X credential format that integrates AKA parameters into EDHOC credential structure. Enables mobile network authentication credentials to be used within EDHOC protocol flows.


draft_name: draft-chen-lake-edhoc-aka
title: Symmetric Cryptography Optimization
idea_type: pattern
extracted_at: 2026-02-28T10:40:22.105581+00:00
description:
Employs symmetric cryptographic techniques instead of asymmetric operations to reduce computational overhead. Specifically designed for resource-constrained environments like Non-Terrestrial Networks (NTN).


draft_name: draft-chen-lake-edhoc-aka
title: Mobile Network Access Authentication
idea_type: architecture
extracted_at: 2026-02-28T10:40:22.105581+00:00
description:
Adapts EDHOC for mobile communication network scenarios with limited computing and network resources. Provides efficient authentication suitable for cellular and satellite communication environments.


draft_name: draft-chen-oauth-rar-agent-extensions
title: policy_context member
idea_type: extension
extracted_at: 2026-02-28T10:40:29.257796+00:00
description:
A new member added to the RAR authorization_details object that allows clients to explicitly request authorization under a specific policy assurance level. This mitigates policy downgrade attacks and enhances user consent by making security requirements explicit.


draft_name: draft-chen-oauth-rar-agent-extensions
title: lifecycle_binding member
idea_type: extension
extracted_at: 2026-02-28T10:40:29.257796+00:00
description:
A new member in the authorization_details object that ties authorization grant validity to the state of an external entity like an automated task. This ensures permissions are automatically revoked when the bound entity completes or terminates.


draft_name: draft-chen-oauth-rar-agent-extensions
title: Policy downgrade attack mitigation
idea_type: mechanism
extracted_at: 2026-02-28T10:40:29.257796+00:00
description:
A security mechanism that prevents attackers from forcing authorization decisions under weaker security policies. Achieved through explicit policy context specification in authorization requests.


draft_name: draft-chen-oauth-rar-agent-extensions
title: External entity state binding
idea_type: pattern
extracted_at: 2026-02-28T10:40:29.257796+00:00
description:
A pattern where OAuth authorization lifetime is directly coupled to external system states such as AI agent tasks or automated processes. This enables automatic permission revocation based on external lifecycle events.


draft_name: draft-chen-oauth-rar-agent-extensions
title: Task-bound authorization lifecycle
idea_type: mechanism
extracted_at: 2026-02-28T10:40:29.257796+00:00
description:
An authorization model where permissions automatically expire when associated automated tasks complete. This provides immediate cleanup of permissions without manual intervention or fixed timeouts.


draft_name: draft-chuyi-nmrg-ai-agent-network
title: AI Agent Network Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:40:35.809172+00:00
description:
A proposed architecture that integrates large language model-based agents into network operations systems to address system isolation and data fragmentation. The architecture enables automated reasoning and decision-making across previously disconnected network management systems.


draft_name: draft-chuyi-nmrg-ai-agent-network
title: Network Data Integration Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:40:35.809172+00:00
description:
A pattern for consolidating fragmented network operational data to enable AI agents to have comprehensive visibility across network systems. This addresses the challenge of isolated data silos in current network operations.


draft_name: draft-chuyi-nmrg-ai-agent-network
title: Large Model Network Automation Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:40:35.809172+00:00
description:
A mechanism that leverages large language models' content generation and reasoning capabilities specifically for network automation tasks. It reduces manual, repetitive operational tasks through intelligent automation.


draft_name: draft-chuyi-nmrg-ai-agent-network
title: Enhanced Network Intelligence Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:40:35.809172+00:00
description:
Requirements for improving intelligence levels in network operations through AI agent integration. Addresses typical scenarios where manual intervention currently dominates network maintenance tasks.


draft_name: draft-condrey-rats-witnessd-enrollment
title: Trust Anchor Bootstrap Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:40:41.656515+00:00
description:
Protocol for provisioning and verifying device keys in the witnessd Proof of Process framework. Defines how new devices enter the ecosystem and how Verifiers discover and validate device trust anchors.


draft_name: draft-condrey-rats-witnessd-enrollment
title: Self-Sovereign Enrollment Mode
idea_type: mechanism
extracted_at: 2026-02-28T10:40:41.656515+00:00
description:
Enrollment mode designed for individual users to bootstrap trust anchors without requiring organizational infrastructure. Enables autonomous device onboarding in the witnessd ecosystem.


draft_name: draft-condrey-rats-witnessd-enrollment
title: Organizational Enrollment Mode
idea_type: mechanism
extracted_at: 2026-02-28T10:40:41.656515+00:00
description:
Enterprise deployment enrollment mode for managed device onboarding within organizational boundaries. Supports centralized trust anchor management and verification.


draft_name: draft-condrey-rats-witnessd-enrollment
title: Public Registry Enrollment Mode
idea_type: mechanism
extracted_at: 2026-02-28T10:40:41.656515+00:00
description:
Federated trust ecosystem enrollment mode using public registries for trust anchor discovery. Enables cross-organizational device verification and trust establishment.


draft_name: draft-condrey-rats-witnessd-enrollment
title: Device Key Provisioning Framework
idea_type: architecture
extracted_at: 2026-02-28T10:40:41.656515+00:00
description:
Systematic approach for generating, distributing, and validating cryptographic keys for devices entering the witnessd ecosystem. Addresses the bootstrapping problem for trust establishment.


draft_name: draft-contario-totp-secure-enrollment
title: Secure TOTP Key Exchange
idea_type: protocol
extracted_at: 2026-02-28T10:40:47.584782+00:00
description:
A secure key exchange scheme that extends TOTP enrollment to prevent compromise of non-expiring TOTP keys during the enrollment process. Protects against photographic capture of QR codes and unintentional key persistence in communication systems.


draft_name: draft-contario-totp-secure-enrollment
title: QR Code Capture Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:40:47.584782+00:00
description:
Mechanism to prevent compromise of TOTP keys through photographic capture of QR codes during enrollment. Addresses the vulnerability of static QR codes containing the full TOTP secret.


draft_name: draft-contario-totp-secure-enrollment
title: Key Persistence Prevention
idea_type: mechanism
extracted_at: 2026-02-28T10:40:47.584782+00:00
description:
Protection against intentional or unintentional persistence of TOTP key strings in email, SMS, or other systems outside the TOTP authenticator. Prevents key exposure through communication channel storage.


draft_name: draft-contario-totp-secure-enrollment
title: Extended TOTP Enrollment Method
idea_type: extension
extracted_at: 2026-02-28T10:40:47.584782+00:00
description:
Enhancement to the de facto TOTP enrollment process defined in RFC6238 to improve security during the key distribution phase. Maintains compatibility while adding security layers.


draft_name: draft-cosmos-protocol-specification
title: Badge-Based Identity
idea_type: mechanism
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Cryptographically signed, capability-bearing identifiers that operate without requiring blockchain or distributed ledger infrastructure. Badges are Ramp (SDF) documents with optional DID compatibility.


draft_name: draft-cosmos-protocol-specification
title: Trust Scoring
idea_type: mechanism
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Reputation-anchored trust models that are domain-bound for DNS networks and star-bound for Cosmos-native networks. Enables cross-star capability granting and trust-based authorization without requiring new badges.


draft_name: draft-cosmos-protocol-specification
title: Lumen Encryption
idea_type: mechanism
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Post-quantum candidate cryptographic primitives for badge-native encryption designed to support forward secrecy. Uses trust-native cryptographic methods tied to badge identity.


draft_name: draft-cosmos-protocol-specification
title: Echo Grammar
idea_type: protocol
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Semantic message structures that provide intent clarity, UI hints, and agent compatibility. Defines structured communication formats for trust-native messaging.


draft_name: draft-cosmos-protocol-specification
title: Slipstream Transport (TNTP)
idea_type: protocol
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Trust-native transport protocol with badge-based sessions and intent-aware routing. Operates without blockchain or external consensus dependencies.


draft_name: draft-cosmos-protocol-specification
title: Ramp and SDFF Serialization
idea_type: mechanism
extracted_at: 2026-02-28T10:40:53.730045+00:00
description:
Deterministic text and binary formats (Slope Data Format) that provide canonical structure for all Cosmos data. Enables standardized data representation across the protocol.


draft_name: draft-cui-ai-agent-discovery-invocation
title: AI Agent Metadata Format
idea_type: protocol
extracted_at: 2026-02-28T10:41:00.180154+00:00
description:
A standardized JSON schema for describing AI agents including capabilities, I/O specifications, supported languages, tags, and authentication methods. This enables consistent agent description across different platforms and vendors.


draft_name: draft-cui-ai-agent-discovery-invocation
title: Capability-Based Discovery Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:41:00.180154+00:00
description:
A discovery system that allows clients to search for AI agents based on their declared capabilities and functional attributes. Enables automated matching of tasks to appropriate agents.


draft_name: draft-cui-ai-agent-discovery-invocation
title: Unified RESTful Invocation Interface
idea_type: protocol
extracted_at: 2026-02-28T10:41:00.180154+00:00
description:
A standardized REST API interface for invoking AI agents regardless of their underlying implementation or platform. Provides consistent invocation semantics across different agent providers.


draft_name: draft-cui-ai-agent-discovery-invocation
title: Intent-Based Agent Selection Extension
idea_type: extension
extracted_at: 2026-02-28T10:41:00.180154+00:00
description:
An optional extension that enables selection of agents based on high-level intent before the discovery and invocation process. Works without modifying existing discovery or invocation semantics.


draft_name: draft-cui-ai-agent-discovery-invocation
title: Cross-Platform Agent Interoperability Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:41:00.180154+00:00
description:
An architectural pattern that enables AI agents from different vendors and platforms to be discovered and invoked through a common protocol. Facilitates the formation of multi-agent systems.


draft_name: draft-cui-ai-agent-task
title: Dynamic Task Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:41:07.196465+00:00
description:
A mechanism for AI agents to automatically discover available tasks and capabilities across heterogeneous network environments. Enables autonomous identification of work opportunities without centralized coordination.


draft_name: draft-cui-ai-agent-task
title: Agent Task Negotiation
idea_type: protocol
extracted_at: 2026-02-28T10:41:07.196465+00:00
description:
A protocol for AI agents to negotiate task assignments, resource allocation, and execution parameters. Supports autonomous agreement on workload distribution among multiple agents.


draft_name: draft-cui-ai-agent-task
title: Context-Aware Task Scheduling
idea_type: mechanism
extracted_at: 2026-02-28T10:41:07.196465+00:00
description:
A scheduling mechanism that considers environmental context, agent capabilities, and current network conditions when assigning tasks. Optimizes task execution based on real-time system state.


draft_name: draft-cui-ai-agent-task
title: Real-Time Task Adaptability
idea_type: requirement
extracted_at: 2026-02-28T10:41:07.196465+00:00
description:
A requirement for agent protocols to support dynamic adjustment of task execution based on changing conditions. Enables agents to modify their behavior without manual intervention.


draft_name: draft-cui-ai-agent-task
title: Task Coordination Framework
idea_type: architecture
extracted_at: 2026-02-28T10:41:07.196465+00:00
description:
An architectural framework for managing intelligent task-level coordination among AI agents in large-scale environments. Provides structure for autonomous workload management across heterogeneous systems.


draft_name: draft-cui-dmsc-agent-cdi
title: Cross-Domain Agent Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:41:14.684417+00:00
description:
A mechanism for AI agents to discover and identify potential collaboration partners across different administrative domains and network boundaries. Enables agents to locate relevant capabilities without requiring centralized registries.


draft_name: draft-cui-dmsc-agent-cdi
title: Federated Agent Identity Framework
idea_type: architecture
extracted_at: 2026-02-28T10:41:14.684417+00:00
description:
An identity federation system that allows AI agents from different domains to establish and verify identities across administrative boundaries. Supports cross-domain authentication without requiring shared identity providers.


draft_name: draft-cui-dmsc-agent-cdi
title: Agent Capability Negotiation Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:41:14.684417+00:00
description:
A protocol that enables AI agents to exchange and negotiate their capabilities, constraints, and service offerings when establishing cross-domain collaborations. Facilitates dynamic capability matching and agreement.


draft_name: draft-cui-dmsc-agent-cdi
title: Trust Delegation Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:41:14.684417+00:00
description:
A system for establishing and propagating trust relationships between AI agents across domain boundaries through delegation chains. Enables transitive trust without direct bilateral relationships.


draft_name: draft-cui-dmsc-agent-cdi
title: Federated Policy Enforcement
idea_type: architecture
extracted_at: 2026-02-28T10:41:14.684417+00:00
description:
A framework for harmonizing and enforcing policies across multiple administrative domains while maintaining local policy autonomy. Supports policy conflict resolution and unified enforcement for cross-domain agent interactions.


draft_name: draft-cui-dns-native-agent-naming-resolution
title: FQDN-based AI Agent Identification
idea_type: mechanism
extracted_at: 2026-02-28T10:41:21.526203+00:00
description:
AI agents are identified using Fully Qualified Domain Names (FQDNs) as unique identifiers. This leverages existing DNS namespace hierarchies for agent naming and discovery.


draft_name: draft-cui-dns-native-agent-naming-resolution
title: DNS TXT Records for Agent Identity and Keys
idea_type: mechanism
extracted_at: 2026-02-28T10:41:21.526203+00:00
description:
Agent identity information and cryptographic keys are published and distributed using DNS TXT records. This enables cryptographic verification of agent authenticity through DNS infrastructure.


draft_name: draft-cui-dns-native-agent-naming-resolution
title: SVCB Records for Multi-Version Agent Resolution
idea_type: protocol
extracted_at: 2026-02-28T10:41:21.526203+00:00
description:
Service Binding (SVCB) records are used to resolve AI agents across multiple versions and protocols. This enables clients to discover and connect to appropriate agent service endpoints.


draft_name: draft-cui-dns-native-agent-naming-resolution
title: Default Version Selection via Priority
idea_type: mechanism
extracted_at: 2026-02-28T10:41:21.526203+00:00
description:
When no specific version is requested, the system provides the highest priority (default) version of an AI agent. This simplifies client implementation while supporting version evolution.


draft_name: draft-cui-dns-native-agent-naming-resolution
title: DNS-as-Authority Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:41:21.526203+00:00
description:
The architecture positions DNS as the single authoritative source for agent information and service discovery. This centralizes trust and reduces dependency on external registries or directories.


draft_name: draft-cui-nmrg-auto-test
title: Protocol Formalization Component
idea_type: mechanism
extracted_at: 2026-02-28T10:41:28.238328+00:00
description:
AI-assisted component that converts protocol specifications into formal, machine-readable representations suitable for automated test generation. Uses LLMs to parse RFC documents and extract protocol state machines and message formats.


draft_name: draft-cui-nmrg-auto-test
title: AI-Driven Test Case Generation
idea_type: mechanism
extracted_at: 2026-02-28T10:41:28.238328+00:00
description:
Automated system that generates comprehensive test cases from formalized protocol specifications using AI techniques. Produces both positive and negative test scenarios covering protocol edge cases and error conditions.


draft_name: draft-cui-nmrg-auto-test
title: Test Script and Configuration Generation
idea_type: mechanism
extracted_at: 2026-02-28T10:41:28.238328+00:00
description:
Component that automatically produces executable test scripts and network configurations from high-level test cases. Translates abstract test scenarios into platform-specific implementation code.


draft_name: draft-cui-nmrg-auto-test
title: Iterative Refinement Feedback Loop
idea_type: pattern
extracted_at: 2026-02-28T10:41:28.238328+00:00
description:
Continuous improvement mechanism that analyzes test execution results to refine test generation and protocol understanding. Uses feedback to enhance AI model accuracy and test coverage over time.


draft_name: draft-cui-nmrg-auto-test
title: Automation Maturity Levels Framework
idea_type: framework
extracted_at: 2026-02-28T10:41:28.238328+00:00
description:
Six-level classification system (Level 0-5) for evaluating protocol testing automation capabilities from fully manual to fully autonomous. Provides structured assessment criteria for advancing automation implementations.


draft_name: draft-cui-nmrg-llm-benchmark
title: Emulator-based Interactive Environment
idea_type: mechanism
extracted_at: 2026-02-28T10:41:36.231502+00:00
description:
A virtualized network environment that allows LLM agents to interact with network devices and execute configuration commands in real-time. The emulator provides realistic network topologies and device responses for testing LLM-driven network configuration approaches.


draft_name: draft-cui-nmrg-llm-benchmark
title: Multi-dimensional LLM Evaluation Metrics
idea_type: pattern
extracted_at: 2026-02-28T10:41:36.231502+00:00
description:
A comprehensive scoring system that assesses LLM performance across reasoning quality, command accuracy, and functional correctness dimensions. These metrics enable quantitative comparison of different LLM agents' network configuration capabilities.


draft_name: draft-cui-nmrg-llm-benchmark
title: Intent-driven Network Configuration Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:41:36.231502+00:00
description:
A framework that translates high-level network intents into specific device configuration commands using LLM agents. The protocol defines how natural language requirements are processed and converted to executable network configurations.


draft_name: draft-cui-nmrg-llm-benchmark
title: Representative Task Suite
idea_type: mechanism
extracted_at: 2026-02-28T10:41:36.231502+00:00
description:
A standardized collection of network configuration scenarios and challenges designed to comprehensively test LLM agent capabilities. The task suite covers various network management operations from basic setup to complex troubleshooting scenarios.


draft_name: draft-cui-nmrg-llm-benchmark
title: Reproducible Benchmark Framework
idea_type: architecture
extracted_at: 2026-02-28T10:41:36.231502+00:00
description:
A systematic evaluation methodology that ensures consistent and comparable testing conditions across different LLM implementations. The framework standardizes testing procedures, environments, and success criteria for network configuration tasks.


draft_name: draft-cui-nmrg-llm-nm
title: Enhanced Telemetry Module
idea_type: mechanism
extracted_at: 2026-02-28T10:41:42.600448+00:00
description:
A telemetry component that collects and preprocesses network data specifically for LLM consumption. It transforms traditional network metrics into formats suitable for language model processing.


draft_name: draft-cui-nmrg-llm-nm
title: LLM Agent Decision Module
idea_type: mechanism
extracted_at: 2026-02-28T10:41:42.600448+00:00
description:
A core component that processes network telemetry data using large language models to make automated network management decisions. It serves as the AI reasoning engine within the framework.


draft_name: draft-cui-nmrg-llm-nm
title: Human-LLM Interaction Data Models
idea_type: pattern
extracted_at: 2026-02-28T10:41:42.600448+00:00
description:
Structured data formats that define how human operators and LLM agents exchange information in network management scenarios. These models standardize communication between human and AI components.


draft_name: draft-cui-nmrg-llm-nm
title: Human-in-the-Loop Workflows
idea_type: mechanism
extracted_at: 2026-02-28T10:41:42.600448+00:00
description:
Defined processes that ensure human oversight and approval for LLM-generated network management decisions. These workflows enforce human control over automated actions.


draft_name: draft-cui-nmrg-llm-nm
title: LLM-Human Collaborative Framework
idea_type: architecture
extracted_at: 2026-02-28T10:41:42.600448+00:00
description:
An interoperable architecture that integrates LLM agents with existing network management systems while maintaining human operator involvement. It bridges AI automation with traditional network operations.


draft_name: draft-dhir-http-agent-profile
title: HTTP Message Signatures for Agent Authentication
idea_type: mechanism
extracted_at: 2026-02-28T10:41:48.723978+00:00
description:
Cryptographic authentication mechanism for agent traffic using HTTP Message Signatures to verify the identity and integrity of automated agent requests.


draft_name: draft-dhir-http-agent-profile
title: Privacy-Preserving Human Tokens
idea_type: mechanism
extracted_at: 2026-02-28T10:41:48.723978+00:00
description:
Token-based system to clearly separate human traffic from agent traffic while preserving user privacy in the identification process.


draft_name: draft-dhir-http-agent-profile
title: HTTP 402 Micropayment Integration
idea_type: protocol
extracted_at: 2026-02-28T10:41:48.723978+00:00
description:
Protocol-level value exchange system leveraging HTTP status code 402 (Payment Required) with pluggable micropayment mechanisms for agent content access.


draft_name: draft-dhir-http-agent-profile
title: Agent-Aware Traffic Differentiation
idea_type: pattern
extracted_at: 2026-02-28T10:41:48.723978+00:00
description:
Architecture pattern for distinguishing between human browser traffic and autonomous agent traffic at the HTTP protocol level.


draft_name: draft-dhir-http-agent-profile
title: Incremental HAP Deployment via Infrastructure
idea_type: architecture
extracted_at: 2026-02-28T10:41:48.723978+00:00
description:
Deployment strategy enabling HTTP Agent Profile adoption through reverse proxies, CDNs, and agent libraries without requiring full stack changes.


draft_name: draft-diaconu-agents-authz-info-sharing
title: Cross-Domain Authorization Information Sharing
idea_type: mechanism
extracted_at: 2026-02-28T10:41:55.141270+00:00
description:
A mechanism for securely sharing authorization information between agents and MCP servers operating across multiple administrative domains with different Identity Providers and Authorization Servers.


draft_name: draft-diaconu-agents-authz-info-sharing
title: Dynamic Identity for Multi-Agent Systems
idea_type: pattern
extracted_at: 2026-02-28T10:41:55.141270+00:00
description:
An approach for managing flexible identity representation that can adapt across different administrative domains in distributed agent environments.


draft_name: draft-diaconu-agents-authz-info-sharing
title: Interoperable Claims Framework
idea_type: protocol
extracted_at: 2026-02-28T10:41:55.141270+00:00
description:
A standardized method for representing and exchanging authorization claims that can be understood and processed across different domains and systems.


draft_name: draft-diaconu-agents-authz-info-sharing
title: Verifiable Credentials for Agent Authorization
idea_type: extension
extracted_at: 2026-02-28T10:41:55.141270+00:00
description:
Integration of verifiable credentials technology to enable trusted authorization information sharing between agents operating in different administrative contexts.


draft_name: draft-diaconu-agents-authz-info-sharing
title: Distributed Multi-Agent Authorization Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:41:55.141270+00:00
description:
An architectural framework defining how agents, MCP servers, Identity Providers, and Authorization Servers interact across domain boundaries.


draft_name: draft-drake-email-tpm-attestation
title: TPM Hardware Attestation Headers
idea_type: mechanism
extracted_at: 2026-02-28T10:42:03.053522+00:00
description:
Email headers containing cryptographic evidence from Trusted Platform Module (TPM) chips that allow receivers to verify the sender's hardware authenticity. The verification chain runs directly from email header to TPM manufacturer's root Certificate Authority.


draft_name: draft-drake-email-tpm-attestation
title: CMS Attestation Bundle Format
idea_type: protocol
extracted_at: 2026-02-28T10:42:03.053522+00:00
description:
Self-contained data structure using Cryptographic Message Syntax (CMS) to package TPM attestation evidence for transport-independent use across protocols. Provides full hardware identity verification with complete trust chain.


draft_name: draft-drake-email-tpm-attestation
title: SD-JWT Privacy-Preserving Trust Proof
idea_type: mechanism
extracted_at: 2026-02-28T10:42:03.053522+00:00
description:
Alternative attestation mechanism using Selective Disclosure JWT (RFC 9901) that proves hardware trust level claims without revealing specific hardware identity. Maintains privacy while demonstrating genuine TPM presence.


draft_name: draft-drake-email-tpm-attestation
title: Sybil-Resistant Email Authentication
idea_type: architecture
extracted_at: 2026-02-28T10:42:03.053522+00:00
description:
Authentication approach requiring unique physical security chips per sender, making large-scale automated spam economically infeasible. Each email sender must possess genuine hardware TPM from known manufacturers.


draft_name: draft-drake-email-tpm-attestation
title: Transport-Independent Attestation Format
idea_type: extension
extracted_at: 2026-02-28T10:42:03.053522+00:00
description:
Standardized attestation data structures applicable beyond email to HTTP headers, agent-to-agent messaging, and other Internet protocols. Both CMS and SD-JWT formats designed for cross-protocol compatibility.


draft_name: draft-du-ai-agent-communication-6g-aspect
title: AI Agent Communication Network (ACN)
idea_type: architecture
extracted_at: 2026-02-28T10:42:08.637291+00:00
description:
A specialized network architecture designed to handle agent-to-agent communication traffic with specific requirements for AI agent interactions in 6G networks.


draft_name: draft-du-ai-agent-communication-6g-aspect
title: Agent-to-Agent Communication Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:42:08.637291+00:00
description:
A new type of internet traffic pattern where AI agents with different skills connect and communicate to accomplish complex tasks collaboratively.


draft_name: draft-du-ai-agent-communication-6g-aspect
title: Multi-Agent Task Coordination
idea_type: mechanism
extracted_at: 2026-02-28T10:42:08.637291+00:00
description:
A mechanism enabling AI agents to discover and connect with other agents possessing complementary skills required for task completion.


draft_name: draft-du-ai-agent-communication-6g-aspect
title: 6G-Enhanced Agent Communication Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:42:08.637291+00:00
description:
Specific networking requirements derived from 3GPP 6G use cases to support low-latency, high-reliability AI agent interactions.


draft_name: draft-du-ai-agent-communication-6g-aspect
title: Global AI Agent Communication Framework
idea_type: architecture
extracted_at: 2026-02-28T10:42:08.637291+00:00
description:
A standardized framework for enabling AI agents to communicate across different network domains and service providers in a 6G context.


draft_name: draft-eckert-anima-acp-free-ani
title: Automation Network Infrastructure (aNI)
idea_type: architecture
extracted_at: 2026-02-28T10:42:15.034541+00:00
description:
A lightweight variation of ANI that eliminates the Autonomic Control Plane (ACP) while retaining ANI domain certificates, trust anchors, GRASP and BRSKI protocols. Implemented purely as application-level software components without modifying router/switch forwarding or control-plane protocols.


draft_name: draft-eckert-anima-acp-free-ani
title: Proxying Autonomic Software Agents (ASA)
idea_type: mechanism
extracted_at: 2026-02-28T10:42:15.034541+00:00
description:
Software agents that replace the ACP functionality by providing proxy services for automation tasks. Enable distributed automation without requiring expensive ACP implementation.


draft_name: draft-eckert-anima-acp-free-ani
title: ACP-free ANI Domain Authentication
idea_type: mechanism
extracted_at: 2026-02-28T10:42:15.034541+00:00
description:
Reuses existing ANI domain keying material including certificates and trust anchors for authentication without requiring the full ACP infrastructure. Maintains security while reducing implementation complexity.


draft_name: draft-eckert-anima-acp-free-ani
title: Application-only Network Automation
idea_type: pattern
extracted_at: 2026-02-28T10:42:15.034541+00:00
description:
Pattern for implementing network automation infrastructure entirely at the application layer on routers, switches, or co-located management devices. Avoids modifications to underlying network protocols while enabling automation capabilities.


draft_name: draft-eggert-mailmaint-uaautoconf
title: Automatic Email Configuration Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:42:22.286444+00:00
description:
A mechanism for email, calendar, and contact user agents to automatically discover and retrieve server configuration settings. Service providers publish standardized configuration information that client applications can fetch to simplify setup procedures.


draft_name: draft-eggert-mailmaint-uaautoconf
title: JSON-based Configuration Format
idea_type: protocol
extracted_at: 2026-02-28T10:42:22.286444+00:00
description:
A standardized JSON format for publishing email server configuration information including protocols, authentication methods, and connection parameters. This format enables consistent representation of server settings across different service providers.


draft_name: draft-eggert-mailmaint-uaautoconf
title: Protocol Configuration Schema
idea_type: pattern
extracted_at: 2026-02-28T10:42:22.286444+00:00
description:
Structured specification of different email protocols (SMTP, IMAP, POP3, etc.) within the JSON configuration format. Includes server hostnames, ports, encryption settings, and authentication requirements for each protocol type.


draft_name: draft-eggert-mailmaint-uaautoconf
title: Authentication Method Specification
idea_type: mechanism
extracted_at: 2026-02-28T10:42:22.286444+00:00
description:
Standardized way to describe supported authentication mechanisms within the configuration data. Allows clients to understand which authentication methods are available for different protocols.


draft_name: draft-eggert-mailmaint-uaautoconf
title: Provider Information Extension
idea_type: extension
extracted_at: 2026-02-28T10:42:22.286444+00:00
description:
Additional metadata fields in the configuration format to include service provider details, help resources, and support information. Enhances the configuration with human-readable context and troubleshooting resources.


draft_name: draft-fu-cats-flow-lb
title: Flow-Level Load Balancing for CATS
idea_type: mechanism
extracted_at: 2026-02-28T10:42:30.704078+00:00
description:
A mechanism that distributes traffic flows across computing resources in CATS networks at the granularity of individual flows rather than packets. This approach maintains flow coherence while enabling better load distribution across available compute instances.


draft_name: draft-fu-cats-flow-lb
title: Data Plane Autonomous Flow Distribution
idea_type: mechanism
extracted_at: 2026-02-28T10:42:30.704078+00:00
description:
A data plane mechanism that allows forwarding elements to make independent flow steering decisions without per-flow control plane involvement. This reduces signaling overhead and enables faster response to load changes.


draft_name: draft-fu-cats-flow-lb
title: Control Plane Overhead Reduction
idea_type: pattern
extracted_at: 2026-02-28T10:42:30.704078+00:00
description:
An approach that minimizes the frequency and volume of control plane interactions required for load balancing decisions. The mechanism delegates flow-level decisions to the data plane to reduce centralized control processing.


draft_name: draft-fu-cats-flow-lb
title: CATS Flow Distribution Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:42:30.704078+00:00
description:
An architectural model that separates control plane policy distribution from data plane flow steering decisions. The architecture enables autonomous data plane operation while maintaining centralized policy control.


draft_name: draft-fu-cats-flow-lb
title: Compute-Aware Flow Steering
idea_type: mechanism
extracted_at: 2026-02-28T10:42:30.704078+00:00
description:
A steering mechanism that considers both network path characteristics and computing resource availability when making flow distribution decisions. This enables optimal placement of flows based on compute capacity and network conditions.


draft_name: draft-fu-nmop-agent-communication-framework
title: AI Gateway
idea_type: architecture
extracted_at: 2026-02-28T10:42:37.160636+00:00
description:
Central component that facilitates communication and coordination between heterogeneous multi-agents in network AIOps environments. Acts as an intermediary for agent-to-agent interactions and protocol translation.


draft_name: draft-fu-nmop-agent-communication-framework
title: Agent Name Service
idea_type: mechanism
extracted_at: 2026-02-28T10:42:37.160636+00:00
description:
Directory service that enables agent discovery and addressing within the multi-agent framework. Provides naming and location services for distributed AI agents.


draft_name: draft-fu-nmop-agent-communication-framework
title: Multi-Agent Communication Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:42:37.160636+00:00
description:
Communication protocol designed specifically for heterogeneous AI agents to collaborate on network operations and maintenance tasks. Enables standardized message exchange between different types of agents.


draft_name: draft-fu-nmop-agent-communication-framework
title: Agent Monitoring and Tracking
idea_type: mechanism
extracted_at: 2026-02-28T10:42:37.160636+00:00
description:
Capability to monitor agent behavior, performance, and interactions within the framework. Provides visibility into multi-agent collaboration activities for network AIOps.


draft_name: draft-fu-nmop-agent-communication-framework
title: Multi-Agent Security Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:42:37.160636+00:00
description:
Security mechanisms designed to protect communications and operations within the multi-agent framework. Ensures secure collaboration between AI agents in network operations contexts.


draft_name: draft-gaikwad-aps-profile
title: AgentPersistentState Usage Class
idea_type: mechanism
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
A new storage usage class specifically designed for autonomous agent workloads. Distinguishes agent storage requirements from generic file system or VM storage patterns.


draft_name: draft-gaikwad-aps-profile
title: PersistentStateLineOfService Schema
idea_type: protocol
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
A versioned schema that defines service level requirements for agent persistent state storage. Includes specifications for compliance, performance, and data lifecycle management.


draft_name: draft-gaikwad-aps-profile
title: Cryptographic Erasure Compliance
idea_type: mechanism
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
Mechanism to ensure agent memory associated with specific user or agent identities can be cryptographically erased for privacy compliance. Addresses regulatory requirements for data deletion.


draft_name: draft-gaikwad-aps-profile
title: Vector Index Workload Optimization
idea_type: pattern
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
Storage optimizations specifically for high-frequency small I/O operations and vector embedding storage patterns common in agent systems. Addresses performance requirements for AI workloads.


draft_name: draft-gaikwad-aps-profile
title: Kubernetes CSI Integration
idea_type: extension
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
Container orchestration guidance and bindings for integrating APS with Kubernetes Container Storage Interface. Enables seamless deployment of agent storage in containerized environments.


draft_name: draft-gaikwad-aps-profile
title: Swordfish/Redfish Bindings
idea_type: extension
extracted_at: 2026-02-28T10:42:45.959150+00:00
description:
Non-normative protocol bindings for integrating APS with existing storage management standards Swordfish and Redfish. Provides interoperability with enterprise storage infrastructure.


draft_name: draft-gaikwad-llm-benchmarking-methodology
title: Time to First Token (TTFT) Measurement
idea_type: mechanism
extracted_at: 2026-02-28T10:42:52.790286+00:00
description:
A specific latency metric measuring the time from request submission to the first token being generated by the LLM. This provides insight into model initialization and prompt processing overhead.


draft_name: draft-gaikwad-llm-benchmarking-methodology
title: Inter-Token Latency (ITL) Measurement
idea_type: mechanism
extracted_at: 2026-02-28T10:42:52.790286+00:00
description:
A metric measuring the time between consecutive token generations during streaming responses. This captures the model's sustained generation performance during inference.


draft_name: draft-gaikwad-llm-benchmarking-methodology
title: Tripartite Test Configuration Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:42:52.790286+00:00
description:
A standardized test setup dividing the system into three components: Model Engine, Application Gateway, and Compound System configurations. This enables systematic evaluation of different deployment architectures.


draft_name: draft-gaikwad-llm-benchmarking-methodology
title: Request Rate Ramping Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:42:52.790286+00:00
description:
A systematic methodology for gradually increasing request rates to identify throughput limits and performance degradation points. This provides standardized load testing procedures for LLM serving systems.


draft_name: draft-gaikwad-llm-benchmarking-methodology
title: Multi-dimensional Performance Reporting Format
idea_type: protocol
extracted_at: 2026-02-28T10:42:52.790286+00:00
description:
A standardized reporting structure that captures latency, throughput, scheduling, and resource management metrics simultaneously. This enables comprehensive comparison of LLM serving system performance.


draft_name: draft-gaikwad-llm-benchmarking-profiles
title: LLM Benchmarking Profiles
idea_type: architecture
extracted_at: 2026-02-28T10:43:00.310185+00:00
description:
Standardized benchmarking profiles that bind terminology and procedures to concrete architectural roles and workload patterns for LLM serving systems. Each profile clarifies System Under Test (SUT) boundaries, measurement points, and interpretation constraints.


draft_name: draft-gaikwad-llm-benchmarking-profiles
title: System Under Test (SUT) Boundary Definition
idea_type: mechanism
extracted_at: 2026-02-28T10:43:00.310185+00:00
description:
Mechanism for clearly defining the boundaries of what components are included in performance testing of LLM serving systems. Provides standardized approach to determine which system elements are measured versus excluded.


draft_name: draft-gaikwad-llm-benchmarking-profiles
title: Profile Taxonomy with Infrastructure Profiles
idea_type: pattern
extracted_at: 2026-02-28T10:43:00.310185+00:00
description:
Hierarchical classification system for LLM benchmarking profiles, including specific infrastructure-focused profile categories. Organizes different types of benchmarking scenarios into structured categories.


draft_name: draft-gaikwad-llm-benchmarking-profiles
title: Measurement Points Specification
idea_type: requirement
extracted_at: 2026-02-28T10:43:00.310185+00:00
description:
Standardized definition of where performance measurements should be taken within LLM serving system architectures. Ensures consistent and comparable measurement locations across different implementations.


draft_name: draft-gaikwad-llm-benchmarking-profiles
title: Interpretation Constraints Framework
idea_type: mechanism
extracted_at: 2026-02-28T10:43:00.310185+00:00
description:
Set of constraints and guidelines for properly interpreting benchmark results within specific profiles. Provides context-specific rules for understanding performance measurements.


draft_name: draft-gaikwad-llm-benchmarking-terminology
title: Time to First Token (TTFT)
idea_type: mechanism
extracted_at: 2026-02-28T10:43:07.059311+00:00
description:
Measures the elapsed time from request submission to the delivery of the first output token in streaming LLM responses. This metric is critical for user experience in interactive applications where initial response latency matters.


draft_name: draft-gaikwad-llm-benchmarking-terminology
title: Inter-Token Latency
idea_type: mechanism
extracted_at: 2026-02-28T10:43:07.059311+00:00
description:
Defines the time interval between consecutive token deliveries in streaming LLM outputs. This metric helps assess the smoothness and consistency of token generation during inference.


draft_name: draft-gaikwad-llm-benchmarking-terminology
title: Time per Output Token
idea_type: mechanism
extracted_at: 2026-02-28T10:43:07.059311+00:00
description:
Calculates the average time required to generate each output token by dividing total generation time by the number of output tokens. This provides a normalized measure of generation efficiency.


draft_name: draft-gaikwad-llm-benchmarking-terminology
title: Normalized Latency
idea_type: mechanism
extracted_at: 2026-02-28T10:43:07.059311+00:00
description:
Adjusts latency measurements to account for varying input and output lengths, enabling fair comparison across different request patterns. This allows benchmarking of LLM systems with different workload characteristics.


draft_name: draft-gaikwad-llm-benchmarking-terminology
title: System Under Test Boundary Definition
idea_type: architecture
extracted_at: 2026-02-28T10:43:07.059311+00:00
description:
Establishes clear demarcation points for measuring LLM serving systems, including inference engines, application gateways, and compound agentic systems. This ensures consistent measurement scope across different benchmarking scenarios.


draft_name: draft-gaikwad-south-authorization
title: Stochastic Authorization Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:43:14.653638+00:00
description:
SOUTH defines an authorization protocol that can return probabilistic 'allow' decisions based on local policy, enabling uncertainty and contextual information to be incorporated into authorization decisions. This differs from traditional binary allow/deny authorization systems.


draft_name: draft-gaikwad-south-authorization
title: Probabilistic Decision Response
idea_type: mechanism
extracted_at: 2026-02-28T10:43:14.653638+00:00
description:
Authorization servers can return allow decisions with an associated probability value determined by local policy factors like load conditions, uncertainty, and context. The client must then interpret and act on these probabilistic responses.


draft_name: draft-gaikwad-south-authorization
title: Transport-Independent Design
idea_type: architecture
extracted_at: 2026-02-28T10:43:14.653638+00:00
description:
SOUTH is designed to work independently of transport layer and can be composed with existing authentication mechanisms like OAuth, OpenID Connect, mutual TLS, or DPoP. This enables flexible deployment across different network architectures.


draft_name: draft-gaikwad-south-authorization
title: HTTP Protocol Binding
idea_type: protocol
extracted_at: 2026-02-28T10:43:14.653638+00:00
description:
The specification defines specific HTTP binding mechanisms for SOUTH requests and responses to enable interoperable deployment. This includes standardized request/response object formats for HTTP transport.


draft_name: draft-gaikwad-south-authorization
title: Multi-Agent Authorization Support
idea_type: requirement
extracted_at: 2026-02-28T10:43:14.653638+00:00
description:
SOUTH specifically addresses authorization requests from users, services, and autonomous agents within the same protocol framework. This unified approach handles different types of requesting entities with consistent semantics.


draft_name: draft-gaikwad-woa
title: WoA Document Format
idea_type: protocol
extracted_at: 2026-02-28T10:43:21.596836+00:00
description:
A minimal JSON-based description format that allows HTTP hosts to advertise AI agents with standardized metadata. Uses JSON Schema to describe agent inputs and outputs in a machine-readable way.


draft_name: draft-gaikwad-woa
title: Well-Known Location Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:43:21.596836+00:00
description:
A convention for serving WoA documents from a standardized well-known location on HTTP origins. Enables predictable discovery of agent capabilities at the host level.


draft_name: draft-gaikwad-woa
title: Agent Object Schema
idea_type: mechanism
extracted_at: 2026-02-28T10:43:21.596836+00:00
description:
Structured JSON objects that define individual agents within a WoA document, including their capabilities and invocation details. Provides uniform representation of agent metadata across different implementations.


draft_name: draft-gaikwad-woa
title: Transport Configuration System
idea_type: architecture
extracted_at: 2026-02-28T10:43:21.596836+00:00
description:
Multiple transport mechanisms including REST and MCP (Model Context Protocol) transports for agent invocation. Allows flexibility in how clients communicate with advertised agents.


draft_name: draft-gaikwad-woa
title: Host-Level Discovery Primitive
idea_type: pattern
extracted_at: 2026-02-28T10:43:21.596836+00:00
description:
A foundational building block designed to be used by higher-level discovery systems rather than defining discovery itself. Separates agent advertisement from discovery mechanisms.


draft_name: draft-gont-dhcwg-dhcpv6-iids
title: Semantically Opaque IID Generation Algorithm
idea_type: mechanism
extracted_at: 2026-02-28T10:43:29.168782+00:00
description:
A DHCPv6 server-side algorithm for generating IPv6 Interface Identifiers that are semantically opaque, preventing information leakage while maintaining stability. This is a DHCPv6 adaptation of RFC 7217's method originally designed for SLAAC.


draft_name: draft-gont-dhcwg-dhcpv6-iids
title: Server-Side IID Selection Method
idea_type: mechanism
extracted_at: 2026-02-28T10:43:29.168782+00:00
description:
A method that operates entirely on the DHCPv6 server without requiring any modifications to existing DHCPv6 client implementations or protocol specifications. The server selects appropriate Interface Identifiers when leasing non-temporary IPv6 addresses.


draft_name: draft-gont-dhcwg-dhcpv6-iids
title: Multi-Server Stability Guarantee
idea_type: requirement
extracted_at: 2026-02-28T10:43:29.168782+00:00
description:
An algorithm design that ensures stable IPv6 addresses within each subnet even when multiple DHCPv6 servers are present or when DHCPv6 servers are reinstalled. This maintains address consistency across different server configurations.


draft_name: draft-gont-dhcwg-dhcpv6-iids
title: DHCPv6 Variant of RFC 7217
idea_type: extension
extracted_at: 2026-02-28T10:43:29.168782+00:00
description:
An adaptation of the RFC 7217 stable address generation method from IPv6 Stateless Address Autoconfiguration (SLAAC) to work within the DHCPv6 framework. This extends the opaque address generation concept to stateful address assignment.


draft_name: draft-goswami-agentic-jwt
title: Agent Checksum Identity
idea_type: mechanism
extracted_at: 2026-02-28T10:43:38.618660+00:00
description:
Cryptographic identity mechanism that generates checksums based on an agent's system prompts, tools, and configurations. This provides deterministic identity verification for non-deterministic AI agents.


draft_name: draft-goswami-agentic-jwt
title: Workflow-Aware Token Binding
idea_type: mechanism
extracted_at: 2026-02-28T10:43:38.618660+00:00
description:
Token binding mechanism that cryptographically links user intent to specific agent execution workflows. This prevents agents from acting beyond their authorized scope.


draft_name: draft-goswami-agentic-jwt
title: Agent Checksum Grant Type
idea_type: extension
extracted_at: 2026-02-28T10:43:38.618660+00:00
description:
New OAuth 2.0 grant type specifically designed for secure token issuance to autonomous AI agents. Extends OAuth 2.0 to handle agentic identity verification.


draft_name: draft-goswami-agentic-jwt
title: Agentic Proof-of-Possession
idea_type: mechanism
extracted_at: 2026-02-28T10:43:38.618660+00:00
description:
Enhanced PoP mechanism operating at the agentic identity level to prevent token replay attacks between different agents within the same multi-agent system. Provides agent-specific token binding.


draft_name: draft-goswami-agentic-jwt
title: Intent-Execution Separation Problem
idea_type: requirement
extracted_at: 2026-02-28T10:43:38.618660+00:00
description:
Identified security problem where autonomous AI agents can act beyond user intent due to dynamic workflow generation and lack of continuous human oversight. Defines the core challenge addressed by the protocol.


draft_name: draft-gupta-httpapi-events-query
title: Events Query Protocol (EQP)
idea_type: protocol
extracted_at: 2026-02-28T10:43:43.217674+00:00
description:
A minimal protocol built on top of HTTP that allows user agents to receive event notifications directly from any resource. Based on the principle that the most intuitive source for event notifications is the resource itself.


draft_name: draft-gupta-httpapi-events-query
title: Resource-centric Event Notification
idea_type: architecture
extracted_at: 2026-02-28T10:43:43.217674+00:00
description:
An architectural pattern where event notifications are sourced directly from the resource of interest rather than through intermediary event systems. Enables direct querying of resources for their associated events.


draft_name: draft-gupta-httpapi-events-query
title: HTTP-based Event Querying
idea_type: mechanism
extracted_at: 2026-02-28T10:43:43.217674+00:00
description:
A mechanism that leverages existing HTTP infrastructure to enable event notification capabilities. Allows standard HTTP clients to query and receive events from web resources.


draft_name: draft-guy-bary-stamp-protocol
title: Task-bound Access Tokens
idea_type: mechanism
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Cryptographic tokens that bind authorization to specific user intents, tasks, and agent identities. These tokens enforce least-privilege principles by restricting agent capabilities to only what's needed for the specific task.


draft_name: draft-guy-bary-stamp-protocol
title: Message-level Proofs
idea_type: mechanism
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Cryptographic proofs attached to individual messages in agent-to-agent communication. Provides verifiable evidence of authorization and message integrity at the granular message level.


draft_name: draft-guy-bary-stamp-protocol
title: Agent-to-Agent Delegation Framework
idea_type: protocol
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Protocol mechanism allowing autonomous agents to securely delegate tasks and permissions to other agents. Maintains cryptographic proof chains throughout the delegation process.


draft_name: draft-guy-bary-stamp-protocol
title: STAMP Token Format
idea_type: mechanism
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Structured token format that encodes task bindings, agent identities, and cryptographic proofs. Designed specifically for multi-agent environments with dynamic workflows.


draft_name: draft-guy-bary-stamp-protocol
title: OAuth 2.0/GNAP Interoperability
idea_type: extension
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Integration layer that allows STAMP to work with existing OAuth 2.0 and GNAP authorization frameworks. Extends these protocols with agent-specific capabilities while maintaining compatibility.


draft_name: draft-guy-bary-stamp-protocol
title: Task Duration Handling
idea_type: pattern
extracted_at: 2026-02-28T10:43:51.502003+00:00
description:
Protocol differentiation between short-lived and long-running tasks with appropriate token lifecycle management. Addresses the temporal aspects of autonomous agent operations.


draft_name: draft-hackett-ures
title: URES HTML Version Requirement
idea_type: requirement
extracted_at: 2026-02-28T10:43:58.729661+00:00
description:
Specification mandates HTML5 DOCTYPE and specific HTML version requirements for consistent email rendering across MUAs. Establishes baseline HTML standard for email content.


draft_name: draft-hackett-ures
title: Dark Mode Adaptation Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:43:58.729661+00:00
description:
Standardized approach for HTML emails to automatically adapt visual styling for dark mode displays. Addresses inconsistent dark mode handling across different email clients.


draft_name: draft-hackett-ures
title: Embedded Asset Handling Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:43:58.729661+00:00
description:
Unified method for processing and rendering embedded assets within HTML email content. Ensures consistent behavior for images, stylesheets, and other embedded resources.


draft_name: draft-hackett-ures
title: CSS Positioning Constraints
idea_type: requirement
extracted_at: 2026-02-28T10:43:58.729661+00:00
description:
Specific limitations and requirements for CSS positioning properties in email context. Defines which positioning techniques are permitted to ensure reliable cross-client rendering.


draft_name: draft-hackett-ures
title: Secure SVG Rendering Framework
idea_type: mechanism
extracted_at: 2026-02-28T10:43:58.729661+00:00
description:
Security-focused approach to rendering SVG content within HTML emails while preventing malicious code execution. Balances functionality with security requirements.


draft_name: draft-han-ai-agent-impact-infra
title: Agent ID Management
idea_type: mechanism
extracted_at: 2026-02-28T10:44:04.920110+00:00
description:
Management system for AI agent identifiers across heterogeneous network environments. Addresses the challenge of maintaining consistent agent identity across different network types.


draft_name: draft-han-ai-agent-impact-infra
title: Agent Communication in LAN
idea_type: pattern
extracted_at: 2026-02-28T10:44:04.920110+00:00
description:
Communication patterns and protocols for AI agents operating within local area networks. Defines how agents discover and communicate with each other in LAN environments.


draft_name: draft-han-ai-agent-impact-infra
title: Agent Communication across WAN
idea_type: architecture
extracted_at: 2026-02-28T10:44:04.920110+00:00
description:
Framework for AI agent communication spanning wide area networks. Addresses routing, addressing, and connectivity challenges for inter-network agent interactions.


draft_name: draft-han-ai-agent-impact-infra
title: Agent Field Communication
idea_type: pattern
extracted_at: 2026-02-28T10:44:04.920110+00:00
description:
Communication mechanisms for AI agents operating in field environments with potentially limited or intermittent connectivity. Focuses on resilient communication patterns.


draft_name: draft-han-ai-agent-impact-infra
title: Non-3GPP Mobility Management
idea_type: mechanism
extracted_at: 2026-02-28T10:44:04.920110+00:00
description:
Mobility management solutions for AI agents in non-3GPP network environments. Handles agent movement and session continuity outside traditional cellular networks.


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
title: Agent Gateway (AGw) Hierarchical Layered Model
idea_type: architecture
extracted_at: 2026-02-28T10:44:11.776493+00:00
description:
A multi-layer architecture for structuring Agent Gateway intercommunication with defined functional separation. This enables systematic organization of cross-domain agent communication capabilities.


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
title: Cross-Domain Agent Collaboration Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:44:11.776493+00:00
description:
Protocol mechanisms specifically designed for enabling intelligent agents to collaborate across different administrative domains through gateway intermediaries. Addresses protocol compatibility challenges between heterogeneous agent systems.


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
title: AGw Data Synchronization Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:44:11.776493+00:00
description:
Technical approach for maintaining data consistency and synchronization between distributed Agent Gateways. Ensures coherent state management across the Agent Internet ecosystem.


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
title: Agent Internet Gateway Interoperability Framework
idea_type: framework
extracted_at: 2026-02-28T10:44:11.776493+00:00
description:
Standardized framework for ensuring different Agent Gateway implementations can communicate effectively. Specializes in cross-domain gateway compatibility within the IoA ecosystem.


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
title: Distributed Agent Communication Security Model
idea_type: mechanism
extracted_at: 2026-02-28T10:44:11.776493+00:00
description:
Security mechanisms tailored for protecting intercommunication between Agent Gateways in distributed intelligent agent deployments. Addresses unique security challenges in cross-domain agent collaboration.


draft_name: draft-happel-structured-email-trust
title: Structured Email Trust Framework
idea_type: architecture
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Security framework specifically designed to address trust and security considerations when processing structured data embedded within email messages. Provides guidance for message user agents on safe handling of structured email content.


draft_name: draft-happel-structured-email-trust
title: Spam/Virus Filter Adaptation
idea_type: mechanism
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Enhanced filtering mechanisms that can properly analyze and process structured email content without being bypassed by malicious structured data. Addresses the challenge of maintaining security while supporting rich email formats.


draft_name: draft-happel-structured-email-trust
title: Formal Data Display Controls
idea_type: pattern
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Standardized approach for how message user agents should render and display structured data to users. Ensures consistent and secure presentation of structured email content across different email clients.


draft_name: draft-happel-structured-email-trust
title: Automated Processing Safeguards
idea_type: mechanism
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Security controls and validation mechanisms for when email clients automatically process structured email data. Prevents malicious exploitation of automated handling of structured content.


draft_name: draft-happel-structured-email-trust
title: External Reference Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Security measures for handling external links, resources, or references contained within structured email data. Mitigates risks from malicious external content referenced by structured email elements.


draft_name: draft-happel-structured-email-trust
title: Trusted Sender Verification
idea_type: mechanism
extracted_at: 2026-02-28T10:44:19.967426+00:00
description:
Authentication and trust establishment mechanisms specifically for senders of structured email content. Allows email clients to make informed decisions about processing structured data based on sender trustworthiness.


draft_name: draft-hong-nmrg-agenticai-ps
title: Multi-Agent Collaborative Network Management
idea_type: architecture
extracted_at: 2026-02-28T10:44:25.494749+00:00
description:
Multiple autonomous AI agents collaborate to fully automate network operation, management and security. This represents a paradigm shift from traditional centralized network management approaches.


draft_name: draft-hong-nmrg-agenticai-ps
title: Agentic AI Framework for Network Operations
idea_type: architecture
extracted_at: 2026-02-28T10:44:25.494749+00:00
description:
A comprehensive framework introducing autonomous AI agents specifically designed for network management tasks. The framework addresses fundamental issues with existing technologies through agent-based automation.


draft_name: draft-hong-nmrg-agenticai-ps
title: Autonomous Network Agent Standardization Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:44:25.494749+00:00
description:
Core technological areas requiring standardization to enable interoperable autonomous AI agents in network management. This identifies specific IETF/IRTF standardization needs for agentic AI deployment.


draft_name: draft-hong-nmrg-agenticai-ps
title: Network Management Automation Paradigm
idea_type: pattern
extracted_at: 2026-02-28T10:44:25.494749+00:00
description:
A fundamental shift from human-driven to fully automated network operations through coordinated AI agents. This paradigm enables complete automation of network operation, management, and security functions.


draft_name: draft-huang-acme-scalable-agent-enrollment
title: ZKP-based Agent Attestation
idea_type: mechanism
extracted_at: 2026-02-28T10:44:32.767202+00:00
description:
Zero-Knowledge Proofs enable AI agents to prove their attestation properties during certificate enrollment without revealing sensitive details. This provides private, efficient, and continuous attestation while maintaining scalability.


draft_name: draft-huang-acme-scalable-agent-enrollment
title: Trusted Host Bootstrapping
idea_type: pattern
extracted_at: 2026-02-28T10:44:32.767202+00:00
description:
A one-time, high-assurance bootstrapping process establishes a trusted host environment that can subsequently endorse certificate requests for AI agents it runs. This amortizes the cost of full attestation validation across multiple agent enrollments.


draft_name: draft-huang-acme-scalable-agent-enrollment
title: Attestation-Extended Enrollment Protocols
idea_type: extension
extracted_at: 2026-02-28T10:44:32.767202+00:00
description:
Extensions to traditional certificate enrollment protocols like SCEP and EST to include remote attestation evidence as part of the enrollment process. This integrates hardware-based trust anchors into certificate lifecycle management.


draft_name: draft-huang-acme-scalable-agent-enrollment
title: Scalable Agent Identity Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:44:32.767202+00:00
description:
An architecture that addresses performance bottlenecks of per-enrollment attestation validation for AI agents by using either ZKP-based private attestation or trusted host endorsement models. This enables high-assurance identity management at scale.


draft_name: draft-huang-acme-scalable-agent-enrollment
title: Host-Delegated Certificate Endorsement
idea_type: mechanism
extracted_at: 2026-02-28T10:44:32.767202+00:00
description:
A mechanism where a pre-validated trusted host is authorized to endorse certificate requests on behalf of AI agents running within its environment. This reduces the computational overhead of individual agent attestation while maintaining security assurances.


draft_name: draft-huang-rats-agentic-eat-cap-attest
title: EAT Capability Claims Extension
idea_type: extension
extracted_at: 2026-02-28T10:44:42.654501+00:00
description:
New claims added to Entity Attestation Token (EAT) for asserting agent functional, reasoning, and operational capabilities. Extends RFC9248 EAT standard with AI-specific capability attestation fields.


draft_name: draft-huang-rats-agentic-eat-cap-attest
title: Nested Agent Representation
idea_type: mechanism
extracted_at: 2026-02-28T10:44:42.654501+00:00
description:
Mechanism for representing compositional structure of agentic AI systems within attestation tokens. Supports modular agent architectures with hierarchical capability attestation.


draft_name: draft-huang-rats-agentic-eat-cap-attest
title: Capability Policy Constraints
idea_type: mechanism
extracted_at: 2026-02-28T10:44:42.654501+00:00
description:
Framework for embedding policy constraints within capability attestations to limit agent operations. Provides verifiable bounds on what capabilities agents can exercise.


draft_name: draft-huang-rats-agentic-eat-cap-attest
title: Privacy-Respecting Capability Attestation
idea_type: pattern
extracted_at: 2026-02-28T10:44:42.654501+00:00
description:
Attestation approach that enables capability verification while preserving agent privacy in decentralized environments. Balances transparency requirements with confidentiality needs.


draft_name: draft-huang-rats-agentic-eat-cap-attest
title: Interoperable Agentic Attestation
idea_type: protocol
extracted_at: 2026-02-28T10:44:42.654501+00:00
description:
Standardized approach for capability attestation across different agentic AI systems and platforms. Enables cross-system trust establishment and capability verification.


draft_name: draft-hw-ai-agent-6g
title: 6G Agent Protocol Framework
idea_type: protocol
extracted_at: 2026-02-28T10:44:48.126599+00:00
description:
Protocol framework specifically designed for AI agent applications in 6G networks. Addresses mobile communication system characteristics and performance requirements unique to 6G environments.


draft_name: draft-hw-ai-agent-6g
title: Mobile-Specific Agent Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:44:48.126599+00:00
description:
Technical requirements for agent protocols tailored to mobile communication systems. Includes performance, latency, and reliability constraints specific to cellular networks.


draft_name: draft-hw-ai-agent-6g
title: Telecom-AI Integration Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:44:48.126599+00:00
description:
Architecture for integrating latest AI agent trends with telecommunication infrastructure. Enables adoption of AI capabilities while meeting telecom-specific operational constraints.


draft_name: draft-hw-ai-agent-6g
title: 6G Agent Enabling Technologies
idea_type: mechanism
extracted_at: 2026-02-28T10:44:48.126599+00:00
description:
Specific enabling technologies required to support agent protocols in 6G networks. Focuses on technical mechanisms needed for agent communication and coordination.


draft_name: draft-ietf-ace-coap-est-oscore
title: EST over CoAP with OSCORE Protection
idea_type: protocol
extracted_at: 2026-02-28T10:44:55.498912+00:00
description:
Specifies carrying EST certificate provisioning protocol over CoAP protected with OSCORE instead of DTLS. Builds on EST-coaps but replaces transport layer security with application layer object security.


draft_name: draft-ietf-ace-coap-est-oscore
title: EDHOC for EST Key Establishment
idea_type: mechanism
extracted_at: 2026-02-28T10:44:55.498912+00:00
description:
Uses Ephemeral Diffie-Hellman over COSE (EDHOC) for establishing security context instead of DTLS handshake. Provides authenticated key exchange suitable for constrained environments.


draft_name: draft-ietf-ace-coap-est-oscore
title: CBOR Certificate Support
idea_type: extension
extracted_at: 2026-02-28T10:44:55.498912+00:00
description:
Leverages CBOR-encoded certificate structures that can be used alongside traditional X.509 certificates. Enables more compact certificate representations for constrained devices.


draft_name: draft-ietf-ace-coap-est-oscore
title: Application Layer Security for EST
idea_type: architecture
extracted_at: 2026-02-28T10:44:55.498912+00:00
description:
Moves security protection from transport layer (DTLS) to application layer (OSCORE) for EST operations. Enables end-to-end protection of EST payloads independent of underlying transport.


draft_name: draft-ietf-ace-coap-est-oscore
title: Constrained Device Certificate Provisioning
idea_type: pattern
extracted_at: 2026-02-28T10:44:55.498912+00:00
description:
Adapts EST certificate enrollment for resource-constrained IoT devices using lightweight protocols. Reduces overhead compared to HTTPS-based EST while maintaining security properties.


draft_name: draft-ietf-ace-edhoc-oscore-profile
title: ACE-EDHOC-OSCORE Profile
idea_type: profile
extracted_at: 2026-02-28T10:45:02.958207+00:00
description:
A complete profile for the ACE framework that combines EDHOC mutual authentication with OSCORE security context establishment for constrained environments. The profile binds client authentication credentials to ACE-OAuth access tokens.


draft_name: draft-ietf-ace-edhoc-oscore-profile
title: EDHOC-OSCORE Security Context Binding
idea_type: mechanism
extracted_at: 2026-02-28T10:45:02.958207+00:00
description:
A mechanism that establishes an OSCORE security context directly from the EDHOC key exchange protocol. This eliminates the need for separate security context establishment between client and resource server.


draft_name: draft-ietf-ace-edhoc-oscore-profile
title: Client Credential to Access Token Binding
idea_type: mechanism
extracted_at: 2026-02-28T10:45:02.958207+00:00
description:
A binding mechanism that cryptographically links a client's authentication credential used in EDHOC to an ACE-OAuth access token. This ensures proof-of-possession of the credential when presenting the token.


draft_name: draft-ietf-ace-edhoc-oscore-profile
title: Authorization Delegation Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:45:02.958207+00:00
description:
An architectural pattern that delegates authorization information management from resource-constrained servers to trusted hosts with greater processing and memory capabilities. The constrained server can offload complex authorization decisions while maintaining security.


draft_name: draft-ietf-ace-edhoc-oscore-profile
title: Mutual Authentication for ACE-OAuth
idea_type: extension
extracted_at: 2026-02-28T10:45:02.958207+00:00
description:
Extension of the ACE-OAuth framework to support mutual authentication between client and resource server using EDHOC. This provides stronger security guarantees than bearer token approaches.


draft_name: draft-ietf-anima-brski-prm
title: Registrar-Agent Component
idea_type: architecture
extracted_at: 2026-02-28T10:45:10.348811+00:00
description:
A new architectural component that acts as an intermediary between pledges and the domain registrar when direct communication is limited or impossible. The registrar-agent enables the reversal of interaction model from pledge-initiated to pledge-responding mode.


draft_name: draft-ietf-anima-brski-prm
title: Pledge Responder Mode
idea_type: mechanism
extracted_at: 2026-02-28T10:45:10.348811+00:00
description:
A mechanism where the pledge operates in server role instead of client role, responding to requests rather than initiating them. This reverses the traditional BRSKI interaction model to support scenarios with limited connectivity.


draft_name: draft-ietf-anima-brski-prm
title: Object Security for Trust Establishment
idea_type: mechanism
extracted_at: 2026-02-28T10:45:10.348811+00:00
description:
BRSKI-PRM uses object-level security instead of transport security to establish trust relationships between pledge and registrar. This approach provides security guarantees independent of the underlying transport mechanism.


draft_name: draft-ietf-anima-brski-prm
title: BRSKI-PRM Protocol Enhancement
idea_type: extension
extracted_at: 2026-02-28T10:45:10.348811+00:00
description:
An extension to the original BRSKI protocol that enables secure bootstrapping in constrained network environments where pledges cannot directly communicate with registrars. It maintains compatibility with existing enrollment protocols.


draft_name: draft-ietf-anima-brski-prm
title: Enrollment Protocol Agnostic Design
idea_type: pattern
extracted_at: 2026-02-28T10:45:10.348811+00:00
description:
The BRSKI-PRM approach is designed to work with any enrollment protocol that connects a domain registrar to key infrastructure such as Certificate Authorities. This provides flexibility in deployment scenarios.


draft_name: draft-ietf-anima-constrained-voucher
title: CBOR-encoded vouchers
idea_type: mechanism
extracted_at: 2026-02-28T10:45:17.823518+00:00
description:
Replaces JSON-encoded vouchers in BRSKI with compact CBOR encoding for constrained devices. Provides smaller message sizes suitable for IoT environments with limited bandwidth.


draft_name: draft-ietf-anima-constrained-voucher
title: EST-over-CoAPS
idea_type: protocol
extracted_at: 2026-02-28T10:45:17.823518+00:00
description:
Adapts the Enrollment over Secure Transport (EST) protocol to run over CoAPS instead of HTTPS. Enables certificate enrollment for constrained devices using CoAP with DTLS security.


draft_name: draft-ietf-anima-constrained-voucher
title: CoAPS transport replacement
idea_type: mechanism
extracted_at: 2026-02-28T10:45:17.823518+00:00
description:
Substitutes HTTPS transport in BRSKI with DTLS-secured CoAP (CoAPS) for all protocol communications. Optimizes for constrained networks with limited throughput and frequent packet loss.


draft_name: draft-ietf-anima-constrained-voucher
title: Extended voucher data types
idea_type: extension
extracted_at: 2026-02-28T10:45:17.823518+00:00
description:
Introduces new compact data types in the voucher definition to achieve smaller voucher sizes. Extends the original BRSKI voucher format with constrained-network optimizations.


draft_name: draft-ietf-anima-constrained-voucher
title: Zero-touch IoT onboarding
idea_type: protocol
extracted_at: 2026-02-28T10:45:17.823518+00:00
description:
Provides secure automatic bootstrapping of resource-constrained IoT devices into domain networks without manual intervention. Maintains mutual authentication between device and network using manufacturer-signed vouchers.


draft_name: draft-ietf-dnsop-ds-automation
title: DS Parameter Acceptance Checks
idea_type: mechanism
extracted_at: 2026-02-28T10:45:26.735910+00:00
description:
Validation mechanisms that parental agents must implement to verify DS parameters received from child DNS operators before accepting them into the parent zone. These checks ensure cryptographic validity and operational safety of the delegation signer records.


draft_name: draft-ietf-dnsop-ds-automation
title: Multi-Party Concurrent Update Handling
idea_type: pattern
extracted_at: 2026-02-28T10:45:26.735910+00:00
description:
Technical approach for managing situations where multiple parties (registrars, DNS operators) attempt to update DS records simultaneously. Addresses race conditions and conflict resolution in automated DS management.


draft_name: draft-ietf-dnsop-ds-automation
title: Error and Success Reporting Framework
idea_type: protocol
extracted_at: 2026-02-28T10:45:26.735910+00:00
description:
Standardized reporting mechanism for communicating the results of automated DS operations back to child operators. Defines how parental agents should indicate acceptance, rejection, or processing status of DS updates.


draft_name: draft-ietf-dnsop-ds-automation
title: Parental Agent Decision Logic
idea_type: mechanism
extracted_at: 2026-02-28T10:45:26.735910+00:00
description:
Technical decision tree and criteria that registries and registrar systems should implement when processing automated DS submissions. Covers validation steps, timing considerations, and acceptance thresholds.


draft_name: draft-ietf-dnsop-ds-automation
title: Child-to-Parent DS Communication Security
idea_type: requirement
extracted_at: 2026-02-28T10:45:26.735910+00:00
description:
Security requirements and verification procedures for ensuring authentic communication of DS parameters from child DNS operators to parental agents. Builds upon existing RFCs 7344, 8078, and 9615 mechanisms.


draft_name: draft-ietf-emu-eap-edhoc
title: EAP-EDHOC Authentication Method
idea_type: protocol
extracted_at: 2026-02-28T10:45:34.617430+00:00
description:
A new EAP authentication method that integrates EDHOC (Ephemeral Diffie-Hellman Over COSE) as the underlying security handshake protocol. This enables lightweight authentication and key establishment suitable for constrained environments within the EAP framework.


draft_name: draft-ietf-emu-eap-edhoc
title: EDHOC-EAP Message Encapsulation
idea_type: mechanism
extracted_at: 2026-02-28T10:45:34.617430+00:00
description:
A mechanism for encapsulating EDHOC protocol messages within EAP packet format. This allows EDHOC handshake exchanges to be transported over existing EAP infrastructure.


draft_name: draft-ietf-emu-eap-edhoc
title: Constrained Environment EAP Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:45:34.617430+00:00
description:
An architectural pattern that adapts EAP authentication for constrained settings by leveraging EDHOC's lightweight properties. This addresses the need for efficient authentication in IoT and resource-limited environments.


draft_name: draft-ietf-emu-eap-edhoc
title: EAP-EDHOC Key Derivation
idea_type: mechanism
extracted_at: 2026-02-28T10:45:34.617430+00:00
description:
A key derivation mechanism that generates EAP keying material from EDHOC's established shared secrets. This ensures compatibility with EAP's key management requirements while leveraging EDHOC's cryptographic properties.


draft_name: draft-ietf-emu-eap-edhoc
title: COSE-based EAP Authentication
idea_type: extension
extracted_at: 2026-02-28T10:45:34.617430+00:00
description:
Integration of CBOR Object Signing and Encryption (COSE) cryptographic operations within EAP authentication flow. This provides modern cryptographic primitives optimized for constrained environments in EAP contexts.


draft_name: draft-ietf-emu-hybrid-pqc-eapaka
title: PQ/T Hybrid Key Exchange for EAP-AKA'
idea_type: mechanism
extracted_at: 2026-02-28T10:45:42.092280+00:00
description:
Replaces traditional ECDHE with hybrid post-quantum/traditional cryptographic algorithms in EAP-AKA' FS to provide quantum-resistant ephemeral key exchange. This mechanism combines classical and post-quantum cryptographic primitives for forward secrecy.


draft_name: draft-ietf-emu-hybrid-pqc-eapaka
title: Quantum-Safe EAP-AKA' Extension
idea_type: extension
extracted_at: 2026-02-28T10:45:42.092280+00:00
description:
An extension to the existing EAP-AKA' FS protocol that integrates post-quantum cryptography to protect against future quantum computer attacks. This builds upon RFC9678 by adding quantum-resistant key agreement capabilities.


draft_name: draft-ietf-emu-hybrid-pqc-eapaka
title: Hybrid Ephemeral Key Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:45:42.092280+00:00
description:
Protects session keys in EAP-AKA' authentication runs against compromise scenarios where adversaries obtain both long-term keys and ephemeral public keys. Uses hybrid algorithms to ensure security even if traditional cryptographic components are broken.


draft_name: draft-ietf-emu-hybrid-pqc-eapaka
title: Post-Quantum Forward Secrecy Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:45:42.092280+00:00
description:
Defines security requirements for maintaining perfect forward secrecy in EAP-AKA' against cryptographically relevant quantum computers. Addresses the threat model where quantum attacks could compromise traditional ephemeral key exchanges.


draft_name: draft-ietf-emu-pqc-eapaka
title: PQ-KEM Integration in EAP-AKA'
idea_type: mechanism
extracted_at: 2026-02-28T10:45:50.899386+00:00
description:
Replaces traditional ECDHE key exchange with Post-Quantum Key Encapsulation Mechanisms to provide quantum-safe forward secrecy. This maintains the existing EAP-AKA' FS protocol structure while upgrading the cryptographic primitives.


draft_name: draft-ietf-emu-pqc-eapaka
title: Quantum-Safe Session Key Generation
idea_type: mechanism
extracted_at: 2026-02-28T10:45:50.899386+00:00
description:
Modifies the key derivation process in EAP-AKA' to incorporate PQ-KEM shared secrets alongside existing authentication materials. Ensures session keys remain secure against quantum adversaries who may compromise long-term keys.


draft_name: draft-ietf-emu-pqc-eapaka
title: Backward Compatible PQ Extension
idea_type: extension
extracted_at: 2026-02-28T10:45:50.899386+00:00
description:
Provides an optional extension mechanism that allows EAP-AKA' implementations to negotiate and use PQ-KEMs while maintaining compatibility with existing deployments. Enables gradual migration to quantum-safe cryptography.


draft_name: draft-ietf-emu-pqc-eapaka
title: Hybrid Classical-PQ Key Exchange
idea_type: pattern
extracted_at: 2026-02-28T10:45:50.899386+00:00
description:
Combines traditional elliptic curve operations with post-quantum key encapsulation to provide security against both classical and quantum attacks. Ensures no reduction in security during the transition period.


draft_name: draft-ietf-emu-pqc-eapaka
title: PQ-KEM Algorithm Negotiation
idea_type: protocol
extracted_at: 2026-02-28T10:45:50.899386+00:00
description:
Defines a mechanism for EAP-AKA' peers and servers to negotiate which PQ-KEM algorithms to use during the authentication exchange. Supports multiple post-quantum algorithms for flexibility and future-proofing.


draft_name: draft-ietf-hpke-hpke
title: HPKE Core Scheme
idea_type: protocol
extracted_at: 2026-02-28T10:45:56.919320+00:00
description:
Hybrid public key encryption combining asymmetric KEM, KDF, and AEAD for encrypting arbitrary-sized plaintexts. Works with any combination of these three cryptographic primitives.


draft_name: draft-ietf-hpke-hpke
title: Pre-Shared Key Authentication
idea_type: mechanism
extracted_at: 2026-02-28T10:45:56.919320+00:00
description:
Variant of HPKE that authenticates possession of a pre-shared key in addition to public key encryption. Provides additional authentication layer beyond standard public key cryptography.


draft_name: draft-ietf-hpke-hpke
title: Modular Primitive Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:45:56.919320+00:00
description:
Architecture allowing any combination of asymmetric KEM, KDF, and AEAD functions to be plugged into HPKE. Enables flexibility in choosing cryptographic primitives based on requirements.


draft_name: draft-ietf-hpke-hpke
title: ECDH-HKDF-SHA2 Instantiation
idea_type: mechanism
extracted_at: 2026-02-28T10:45:56.919320+00:00
description:
Concrete implementation of HPKE using Elliptic Curve Diffie-Hellman key agreement, HMAC-based key derivation, and SHA2. Provides a widely-used and efficient instantiation of the general scheme.


draft_name: draft-ietf-httpbis-layered-cookies
title: Set-Cookie Header Field
idea_type: protocol
extracted_at: 2026-02-28T10:46:03.600440+00:00
description:
HTTP response header field that allows servers to send state information to user agents for storage and subsequent transmission back to the server. Enables stateful sessions over the stateless HTTP protocol.


draft_name: draft-ietf-httpbis-layered-cookies
title: Cookie Header Field
idea_type: protocol
extracted_at: 2026-02-28T10:46:03.600440+00:00
description:
HTTP request header field that user agents use to transmit stored cookie data back to servers. Provides the mechanism for clients to include server-provided state in subsequent requests.


draft_name: draft-ietf-httpbis-layered-cookies
title: HTTP State Management
idea_type: architecture
extracted_at: 2026-02-28T10:46:03.600440+00:00
description:
Architectural pattern enabling servers to maintain stateful sessions by storing data at the client and having it transmitted back in subsequent requests. Overcomes the inherent statelessness of HTTP.


draft_name: draft-ietf-httpbis-layered-cookies
title: Layered Cookies Model
idea_type: mechanism
extracted_at: 2026-02-28T10:46:03.600440+00:00
description:
Updated approach to cookie specification that addresses historical security and privacy issues while maintaining backward compatibility. Represents an evolution from RFC 6265.


draft_name: draft-ietf-httpbis-rfc6265bis
title: Set-Cookie Header Field
idea_type: protocol
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
HTTP response header field that allows servers to store state information (cookies) at user agents. Defines syntax and semantics for cookie attributes like expiration, domain, path, and security flags.


draft_name: draft-ietf-httpbis-rfc6265bis
title: Cookie Header Field
idea_type: protocol
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
HTTP request header field that allows user agents to send stored cookie data back to servers. Enables stateful sessions over the stateless HTTP protocol.


draft_name: draft-ietf-httpbis-rfc6265bis
title: Cookie Domain Matching
idea_type: mechanism
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
Algorithm for determining whether a cookie's domain attribute matches the current request's domain. Controls which domains can receive specific cookies for security isolation.


draft_name: draft-ietf-httpbis-rfc6265bis
title: Cookie Path Matching
idea_type: mechanism
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
Mechanism for restricting cookie delivery based on URL path prefixes. Allows servers to limit cookie scope to specific application paths or directories.


draft_name: draft-ietf-httpbis-rfc6265bis
title: Secure Cookie Attribute
idea_type: mechanism
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
Cookie attribute that restricts transmission to HTTPS connections only. Prevents cookie interception over unencrypted HTTP channels.


draft_name: draft-ietf-httpbis-rfc6265bis
title: HttpOnly Cookie Attribute
idea_type: mechanism
extracted_at: 2026-02-28T10:46:11.278442+00:00
description:
Cookie attribute that prevents client-side script access to cookies. Mitigates cross-site scripting (XSS) attacks by limiting cookie access to HTTP transactions only.


draft_name: draft-ietf-lake-app-profiles
title: CBOR-based Application Profile Representation
idea_type: mechanism
extracted_at: 2026-02-28T10:46:18.752499+00:00
description:
A canonical CBOR encoding format for describing EDHOC application profiles that can be distributed, stored, and processed independently of transport mechanisms. This provides a standardized way to represent profile parameters and configurations.


draft_name: draft-ietf-lake-app-profiles
title: Application Profile Coordination Framework
idea_type: protocol
extracted_at: 2026-02-28T10:46:18.752499+00:00
description:
A set of mechanisms to coordinate the selection and use of EDHOC application profiles between implementations. This enables interoperability by providing standardized ways for peers to agree on which profile to use.


draft_name: draft-ietf-lake-app-profiles
title: Well-known Application Profiles Registry
idea_type: architecture
extracted_at: 2026-02-28T10:46:18.752499+00:00
description:
A defined set of standardized EDHOC application profiles for common use cases. These profiles specify pre-agreed parameter sets that can be referenced by implementations without custom negotiation.


draft_name: draft-ietf-lake-app-profiles
title: Out-of-band Parameter Agreement Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:46:18.752499+00:00
description:
A pattern for establishing EDHOC parameters before protocol execution begins. This addresses the requirement that certain parameters must be agreed upon prior to running the key exchange protocol.


draft_name: draft-ietf-lake-app-profiles
title: Profile Distribution and Storage Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:46:18.752499+00:00
description:
Technical mechanisms for distributing and storing EDHOC application profiles across different deployment scenarios. This extends profile usability beyond single transport or setup contexts.


draft_name: draft-ietf-lake-authz
title: ELA Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:46:25.715415+00:00
description:
Lightweight Authorization using EDHOC that allows authorizing enrollment of new devices using EDHOC's extension points. Enables zero-touch onboarding to constrained networks using manufacture-time trust anchors.


draft_name: draft-ietf-lake-authz
title: EDHOC Extension Point Integration
idea_type: mechanism
extracted_at: 2026-02-28T10:46:25.715415+00:00
description:
Uses the extension point mechanism defined in EDHOC to embed authorization functionality. Allows authorization procedures to be carried out within the EDHOC key exchange flow.


draft_name: draft-ietf-lake-authz
title: Zero-Touch Device Onboarding
idea_type: pattern
extracted_at: 2026-02-28T10:46:25.715415+00:00
description:
Automated device enrollment process that requires no manual configuration. Leverages pre-installed trust anchors from manufacturing to establish device authorization.


draft_name: draft-ietf-lake-authz
title: Manufacture-Time Trust Anchors
idea_type: mechanism
extracted_at: 2026-02-28T10:46:25.715415+00:00
description:
Security credentials installed during device manufacturing that serve as the basis for later authorization. Enables devices to prove legitimacy without additional credential provisioning.


draft_name: draft-ietf-lake-authz
title: Constrained Network Authorization
idea_type: architecture
extracted_at: 2026-02-28T10:46:25.715415+00:00
description:
Authorization framework specifically designed for resource-limited networks and devices. Optimized for low power, low bandwidth, and limited computational capability environments.


draft_name: draft-ietf-lake-edhoc-impl-cons
title: Invalid EDHOC Session Handling
idea_type: mechanism
extracted_at: 2026-02-28T10:46:32.988681+00:00
description:
Mechanism for detecting and responding when EDHOC authenticated key exchange sessions become invalid during or after completion. Includes procedures for session cleanup and state management.


draft_name: draft-ietf-lake-edhoc-impl-cons
title: Application Key Invalidation Management
idea_type: pattern
extracted_at: 2026-02-28T10:46:32.988681+00:00
description:
Protocol pattern for handling scenarios where cryptographic keys derived from EDHOC sessions become compromised or expired. Defines key lifecycle and replacement procedures.


draft_name: draft-ietf-lake-edhoc-impl-cons
title: Bound Access Rights Invalidation
idea_type: architecture
extracted_at: 2026-02-28T10:46:32.988681+00:00
description:
Architecture for managing access control permissions that are cryptographically bound to EDHOC-derived keys. Handles revocation and re-authorization scenarios.


draft_name: draft-ietf-lake-edhoc-impl-cons
title: EDHOC State Cleanup Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:46:32.988681+00:00
description:
Implementation requirements for properly disposing of ephemeral cryptographic material and session state. Ensures security through proper memory management and state transitions.


draft_name: draft-ietf-lake-edhoc-psk
title: PSK Authentication Method for EDHOC
idea_type: mechanism
extracted_at: 2026-02-28T10:46:41.691491+00:00
description:
A Pre-Shared Key authentication method that replaces certificate-based authentication in EDHOC while maintaining mutual authentication and ephemeral key exchange. This method reduces computational overhead by eliminating public key signature operations.


draft_name: draft-ietf-lake-edhoc-psk
title: External PSK vs Resumption PSK
idea_type: pattern
extracted_at: 2026-02-28T10:46:41.691491+00:00
description:
Two distinct PSK provisioning modes: external PSKs provided out-of-band for initial authentication, and resumption PSKs derived from previous EDHOC sessions for efficient session resumption. Each type has different key derivation and processing requirements.


draft_name: draft-ietf-lake-edhoc-psk
title: Modified Key Derivation for PSK
idea_type: mechanism
extracted_at: 2026-02-28T10:46:41.691491+00:00
description:
Changes to EDHOC's key derivation function to incorporate PSK material into the key schedule. The PSK is mixed into the master secret derivation alongside the Diffie-Hellman shared secret.


draft_name: draft-ietf-lake-edhoc-psk
title: PSK Message Flow Modifications
idea_type: protocol
extracted_at: 2026-02-28T10:46:41.691491+00:00
description:
Specific changes to EDHOC message formatting and processing to support PSK authentication, including PSK identity transmission and modified authentication tag computation. The three-message flow is preserved but with PSK-specific content.


draft_name: draft-ietf-lake-edhoc-psk
title: Quantum Resistance Enhancement
idea_type: requirement
extracted_at: 2026-02-28T10:46:41.691491+00:00
description:
The PSK method provides quantum resistance by combining pre-shared symmetric keys with ephemeral Diffie-Hellman exchange. Even if the DH exchange is compromised by quantum attacks, the PSK component maintains security.


draft_name: draft-ietf-lake-ra
title: RATS-EDHOC Integration
idea_type: protocol
extracted_at: 2026-02-28T10:46:48.961542+00:00
description:
Integration of Remote ATtestation procedureS (RATS) architecture into the EDHOC lightweight authenticated Diffie-Hellman key exchange protocol. This enables remote attestation to be performed as part of the key exchange process.


draft_name: draft-ietf-lake-ra
title: Attestation Evidence in EDHOC Messages
idea_type: mechanism
extracted_at: 2026-02-28T10:46:48.961542+00:00
description:
Mechanism to embed attestation evidence within EDHOC protocol messages during the key exchange handshake. This allows verification of device trustworthiness during authentication.


draft_name: draft-ietf-lake-ra
title: Lightweight Remote Attestation
idea_type: pattern
extracted_at: 2026-02-28T10:46:48.961542+00:00
description:
Design pattern for performing remote attestation in resource-constrained environments by leveraging the existing EDHOC protocol structure. This avoids the overhead of separate attestation protocols.


draft_name: draft-ietf-lake-ra
title: COSE-based Attestation Format
idea_type: mechanism
extracted_at: 2026-02-28T10:46:48.961542+00:00
description:
Use of CBOR Object Signing and Encryption (COSE) format for encoding attestation evidence within EDHOC. This provides a compact and standardized way to represent attestation data.


draft_name: draft-ietf-lake-ra
title: Attested Key Exchange
idea_type: architecture
extracted_at: 2026-02-28T10:46:48.961542+00:00
description:
Architecture where the Diffie-Hellman key exchange is combined with attestation verification in a single protocol flow. This ensures both authentication and device trustworthiness establishment simultaneously.


draft_name: draft-ietf-lamps-attestation-freshness
title: Nonce-Based Evidence Freshness
idea_type: mechanism
extracted_at: 2026-02-28T10:46:56.847987+00:00
description:
A mechanism where RA/CA provides nonces to end entities for inclusion in attestation Evidence to demonstrate freshness. The nonce is supplied before CSR submission and included in the attestation Evidence.


draft_name: draft-ietf-lamps-attestation-freshness
title: CMP Nonce Distribution Extension
idea_type: extension
extracted_at: 2026-02-28T10:46:56.847987+00:00
description:
Extension to Certificate Management Protocol (CMP) to enable nonce delivery from RA/CA to end entities for attestation freshness. Allows CMP to support attestation Evidence validation workflows.


draft_name: draft-ietf-lamps-attestation-freshness
title: EST Nonce Distribution Extension
idea_type: extension
extracted_at: 2026-02-28T10:46:56.847987+00:00
description:
Extension to Enrollment over Secure Transport (EST) protocol to provide nonces for attestation Evidence freshness. Enables EST to support remote attestation scenarios in certificate enrollment.


draft_name: draft-ietf-lamps-attestation-freshness
title: CMC Nonce Distribution Extension
idea_type: extension
extracted_at: 2026-02-28T10:46:56.847987+00:00
description:
Extension to Certificate Management over CMS (CMC) to deliver freshness nonces for attestation Evidence. Integrates nonce-based attestation freshness into CMC certificate management workflows.


draft_name: draft-ietf-lamps-attestation-freshness
title: Attestation Evidence CSR Integration
idea_type: pattern
extracted_at: 2026-02-28T10:46:56.847987+00:00
description:
Pattern for embedding attestation Evidence containing freshness nonces within Certificate Signing Requests. Links remote attestation validation to certificate issuance processes.


draft_name: draft-ietf-lamps-e2e-mail-guidance
title: Cryptographic Protection Flexibility Management
idea_type: mechanism
extracted_at: 2026-02-28T10:47:04.115785+00:00
description:
A mechanism to manage the extreme flexibility in cryptographic protection standards that can trap users and cause surprising failures. Provides structured approach to handle implementation choices without compromising security.


draft_name: draft-ietf-lamps-e2e-mail-guidance
title: End-to-End Email Security Vocabulary
idea_type: pattern
extracted_at: 2026-02-28T10:47:04.115785+00:00
description:
A standardized set of terminology and vocabulary definitions for end-to-end email security implementations. Helps ensure consistent understanding across different mail user agent implementations.


draft_name: draft-ietf-lamps-e2e-mail-guidance
title: Mail User Agent Implementation Guidance
idea_type: requirement
extracted_at: 2026-02-28T10:47:04.115785+00:00
description:
Specific recommendations and guidance for mail user agent implementers to mitigate security risks in end-to-end email encryption. Focuses on making implementation decisions that improve user experience while maintaining security.


draft_name: draft-ietf-lamps-e2e-mail-guidance
title: Common Failure Avoidance Recommendations
idea_type: pattern
extracted_at: 2026-02-28T10:47:04.115785+00:00
description:
A set of specific recommendations designed to help implementers avoid common pitfalls and failures in end-to-end email security. Addresses known failure modes in cryptographic email implementations.


draft_name: draft-ietf-lamps-e2e-mail-guidance
title: Usability and Interoperability Problem Identification
idea_type: requirement
extracted_at: 2026-02-28T10:47:04.115785+00:00
description:
Systematic identification and cataloging of currently unsolved usability and interoperability problems in end-to-end email security. Provides framework for addressing known limitations.


draft_name: draft-ietf-lamps-est-renewal-info
title: EST Renewal Info Extension
idea_type: extension
extracted_at: 2026-02-28T10:47:11.385944+00:00
description:
An extension to RFC 7030 Enrollment over Secure Transport that allows EST servers to provide specific renewal timing recommendations to end-entity devices. This replaces the traditional client-decided 50% certificate lifetime renewal approach with server-provided guidance.


draft_name: draft-ietf-lamps-est-renewal-info
title: Server-Directed Renewal Timing
idea_type: mechanism
extracted_at: 2026-02-28T10:47:11.385944+00:00
description:
A mechanism where the EST server provides explicit timing advice to clients about when to initiate certificate renewal requests. This addresses the problem where the traditional 50% lifetime rule becomes inappropriate for certificates with very short lifetimes.


draft_name: draft-ietf-lamps-est-renewal-info
title: Short-Lifetime Certificate Renewal Optimization
idea_type: pattern
extracted_at: 2026-02-28T10:47:11.385944+00:00
description:
A pattern specifically designed to handle certificate renewal for certificates with lifetimes measured in fractions of a year rather than years. The approach optimizes renewal timing to avoid premature renewal attempts that waste resources.


draft_name: draft-ietf-lamps-est-renewal-info
title: Dynamic Renewal Schedule Provision
idea_type: architecture
extracted_at: 2026-02-28T10:47:11.385944+00:00
description:
An architecture component that enables EST servers to dynamically communicate optimal renewal schedules to clients based on certificate policies and operational considerations. This moves renewal timing decisions from static client-side rules to dynamic server-side recommendations.


draft_name: draft-ietf-lamps-private-key-stmt-attr
title: Private Key Possession Statement Attribute
idea_type: mechanism
extracted_at: 2026-02-28T10:47:17.428813+00:00
description:
An X.509 certificate attribute that allows a certificate subject to make a signed statement claiming possession of a private key. This provides an alternative to traditional proof-of-possession mechanisms during certificate enrollment.


draft_name: draft-ietf-lamps-private-key-stmt-attr
title: Cross-Certificate Validation Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:47:17.428813+00:00
description:
A mechanism where a CA can validate a private key possession statement using a previously issued signature certificate for the same subject. This enables efficient issuance of additional certificates like key establishment certificates.


draft_name: draft-ietf-lamps-private-key-stmt-attr
title: Statement-Based Proof of Possession
idea_type: protocol
extracted_at: 2026-02-28T10:47:17.428813+00:00
description:
An alternative proof-of-possession method where CAs accept signed statements from certificate subjects instead of requiring direct cryptographic proof. This simplifies certain certificate enrollment scenarios.


draft_name: draft-ietf-lamps-private-key-stmt-attr
title: Separate Certificate Use Case Support
idea_type: requirement
extracted_at: 2026-02-28T10:47:17.428813+00:00
description:
Support for certificate subjects that need distinct certificates for different purposes (signature vs key establishment). The statement attribute facilitates obtaining multiple certificates for the same entity.


draft_name: draft-ietf-lamps-rfc5274bis
title: CMC Compliance Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:47:23.880605+00:00
description:
Defines mandatory compliance statements and requirements for implementing the Certificate Management over CMS (CMC) enrollment protocol. Specifies what components and behaviors are required for a compliant CMC implementation.


draft_name: draft-ietf-lamps-rfc5274bis
title: CMC Enrollment Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:47:23.880605+00:00
description:
Certificate management protocol that operates over Cryptographic Message Syntax (CMS) for handling certificate enrollment operations. Provides a standardized approach for certificate requests and responses using CMS structures.


draft_name: draft-ietf-lamps-rfc5274bis
title: CMS-based Certificate Management
idea_type: architecture
extracted_at: 2026-02-28T10:47:23.880605+00:00
description:
Architecture that leverages Cryptographic Message Syntax as the foundation for certificate management operations. Separates ASN.1 structures and transport mechanisms from compliance requirements.


draft_name: draft-ietf-lamps-rfc5274bis
title: RFC 5274 and RFC 6402 Obsolescence
idea_type: extension
extracted_at: 2026-02-28T10:47:23.880605+00:00
description:
Updates and consolidates previous CMC compliance specifications by obsoleting RFC 5274 and RFC 6402. Provides modernized compliance requirements in a single document.


draft_name: draft-ietf-lamps-rfc7030-csrattrs
title: CSR Attributes Response Clarification
idea_type: mechanism
extracted_at: 2026-02-28T10:47:30.332752+00:00
description:
Clarifies the ambiguous encoding rules in RFC7030 for how EST servers specify CSR attribute Object IDs (OIDs) and attribute values including X.509 extensions. Resolves implementation challenges caused by unclear specification.


draft_name: draft-ietf-lamps-rfc7030-csrattrs
title: CSR Template Approach
idea_type: mechanism
extracted_at: 2026-02-28T10:47:30.332752+00:00
description:
Introduces a new straightforward method using templates for CSR contents that can be partially pre-filled by the EST server. Provides an alternative to the original ambiguous CSR attributes specification.


draft_name: draft-ietf-lamps-rfc7030-csrattrs
title: Server-Specified Subject DN
idea_type: extension
extracted_at: 2026-02-28T10:47:30.332752+00:00
description:
Enables EST servers to specify the subject Distinguished Name (DN) that clients should use in their certificate signing requests. Extends server control over certificate content beyond just extensions and attributes.


draft_name: draft-ietf-lamps-rfc7030-csrattrs
title: Enhanced CSR Attribute Value Specification
idea_type: mechanism
extracted_at: 2026-02-28T10:47:30.332752+00:00
description:
Allows EST servers to specify not just CSR attribute OIDs but also the actual attribute values, particularly for X.509 extension values. Provides more granular control over expected CSR content.


draft_name: draft-ietf-lisp-nexagon
title: LISP-H3 Integration
idea_type: architecture
extracted_at: 2026-02-28T10:47:37.182813+00:00
description:
Combines LISP's Locator/ID Separation Protocol with H3 spatial indexing system for geospatial routing. Uses H3 hexagonal cell identifiers as LISP Endpoint Identifiers (EIDs) to enable location-based network addressing.


draft_name: draft-ietf-lisp-nexagon
title: Geospatial State Aggregation
idea_type: mechanism
extracted_at: 2026-02-28T10:47:37.182813+00:00
description:
Mechanism for distributed agents to collect, aggregate, and disseminate location-based state information across the network. Enables real-time sharing of geospatial intelligence between network nodes.


draft_name: draft-ietf-lisp-nexagon
title: H3-based EID Addressing
idea_type: protocol
extracted_at: 2026-02-28T10:47:37.182813+00:00
description:
Uses H3 hexagonal spatial index values as LISP Endpoint Identifiers to create location-aware network addresses. Provides hierarchical geographic addressing that scales from global to local resolution levels.


draft_name: draft-ietf-lisp-nexagon
title: Physical-World Application Support
idea_type: requirement
extracted_at: 2026-02-28T10:47:37.182813+00:00
description:
Protocol designed specifically for transportation, public safety, and logistics use cases requiring geospatial intelligence. Bridges network protocols with real-world geographic positioning and state tracking.


draft_name: draft-ietf-mailmaint-pacc
title: PACC Discovery Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:47:43.744972+00:00
description:
User agents discover configuration by querying well-known URIs at the email domain (/.well-known/pacc) to retrieve standardized server settings. This eliminates manual configuration by automatically locating service provider configuration data.


draft_name: draft-ietf-mailmaint-pacc
title: JSON Configuration Schema
idea_type: protocol
extracted_at: 2026-02-28T10:47:43.744972+00:00
description:
Standardized JSON format for publishing email, calendar, and contact server configuration including hostnames, ports, security settings, and authentication methods. Provides machine-readable server setup parameters for automated client configuration.


draft_name: draft-ietf-mailmaint-pacc
title: Multi-Service Configuration
idea_type: architecture
extracted_at: 2026-02-28T10:47:43.744972+00:00
description:
Single configuration endpoint supports email (IMAP/POP/SMTP), calendar (CalDAV), and contact (CardDAV) services simultaneously. Reduces discovery overhead by consolidating multiple service configurations into one request.


draft_name: draft-ietf-mailmaint-pacc
title: Well-Known URI Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:47:43.744972+00:00
description:
Uses RFC 8615 well-known URI mechanism (/.well-known/pacc) for predictable configuration location discovery. Enables clients to construct configuration URLs directly from email domain names.


draft_name: draft-ietf-mailmaint-pacc
title: Automatic Server Setup Procedure
idea_type: mechanism
extracted_at: 2026-02-28T10:47:43.744972+00:00
description:
Defines step-by-step client process for retrieving and applying configuration data to eliminate manual server parameter entry. Streamlines user onboarding by automating technical setup details.


draft_name: draft-ietf-netconf-configuration-tracing
title: External Trace ID Extension
idea_type: extension
extracted_at: 2026-02-28T10:47:51.120922+00:00
description:
NETCONF capability extension that allows clients to include an external trace identifier in configuration requests. This trace ID propagates through the configuration change process to enable tracking back to the originating management system.


draft_name: draft-ietf-netconf-configuration-tracing
title: Configuration Change Mapping Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:47:51.120922+00:00
description:
Automatic mapping system that links local configuration modifications to their external trace identifiers. Enables tracing configuration changes back to specific NMS change requests.


draft_name: draft-ietf-netconf-configuration-tracing
title: Trace ID YANG Module
idea_type: architecture
extracted_at: 2026-02-28T10:47:51.120922+00:00
description:
YANG data model that stores the mapping between local configuration changes and their corresponding external trace identifiers. Provides structured access to configuration tracing information up to controller/orchestrator level.


draft_name: draft-ietf-netconf-configuration-tracing
title: Multi-NMS Configuration Attribution
idea_type: pattern
extracted_at: 2026-02-28T10:47:51.120922+00:00
description:
Pattern for distinguishing configuration changes from concurrent network management systems with overlapping intents. Maps respective modifications back to their originating NMS using trace identifiers.


draft_name: draft-ietf-netconf-configuration-tracing
title: Autonomous Network Tracing Requirement
idea_type: requirement
extracted_at: 2026-02-28T10:47:51.120922+00:00
description:
Requirement for autonomous networks to automatically trace configuration changes that lead to anomaly detection. Supports closed-loop automation and self-healing network capabilities.


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
title: Link-Layer Address Collision Problem
idea_type: requirement
extracted_at: 2026-02-28T10:47:58.902648+00:00
description:
Multiple different IP multicast addresses can map to the same MAC address due to limited bits in Ethernet multicast addressing. This causes unintended packet reception and filtering issues in zeroconf environments.


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
title: Decentralized Multicast Address Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:47:58.902648+00:00
description:
A mechanism for nodes to discover which multicast addresses are already in use on the local network without requiring central coordination. Essential for avoiding conflicts in zeroconf allocation.


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
title: Conflict Detection and Resolution Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:47:58.902648+00:00
description:
Automated detection of multicast address conflicts and resolution mechanisms to ensure unique address allocation. Must operate without manual intervention in zeroconf networks.


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
title: Multicast Address Lease Management
idea_type: mechanism
extracted_at: 2026-02-28T10:47:58.902648+00:00
description:
Time-based allocation system for multicast addresses with automatic renewal and expiration mechanisms. Prevents permanent address reservation in dynamic zeroconf environments.


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
title: Hardware-Limited Multicast Filtering
idea_type: requirement
extracted_at: 2026-02-28T10:47:58.902648+00:00
description:
Network hardware constraints that limit the number of multicast addresses that can be efficiently filtered at the switch level. Affects multicast snooping performance and address allocation strategies.


draft_name: draft-ietf-roll-enrollment-priority
title: Global Enrollment Disable Control
idea_type: mechanism
extracted_at: 2026-02-28T10:48:06.581312+00:00
description:
Mechanism allowing RPL Root to globally disable all enrollment proxy announcements across the network. Provides centralized control over when new devices can join the network.


draft_name: draft-ietf-roll-enrollment-priority
title: Base Priority Adjustment for Enrollment
idea_type: mechanism
extracted_at: 2026-02-28T10:48:06.581312+00:00
description:
System for RPL Root to adjust the base priority value used in enrollment operations by proxy nodes. Allows fine-tuning of enrollment proxy selection preferences.


draft_name: draft-ietf-roll-enrollment-priority
title: Centralized Enrollment Control Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:48:06.581312+00:00
description:
Architecture where the RPL Root has authority to control enrollment parameters network-wide rather than leaving decisions to individual proxy nodes. Enables coordinated enrollment policies.


draft_name: draft-ietf-roll-enrollment-priority
title: Priority-Based Enrollment Proxy Selection
idea_type: extension
extracted_at: 2026-02-28T10:48:06.581312+00:00
description:
Extension to RFC9032 enrollment proxy announcements that incorporates Root-controlled priority adjustments. Enhances the existing priority mechanism with centralized oversight.


draft_name: draft-ietf-roll-enrollment-priority
title: RPL Root Enrollment Authority
idea_type: pattern
extracted_at: 2026-02-28T10:48:06.581312+00:00
description:
Protocol pattern establishing the RPL Root as the authoritative controller for network enrollment policies. Defines how Root decisions propagate to enrollment proxies.


draft_name: draft-ietf-sml-trust
title: Structured Email Trust Framework
idea_type: architecture
extracted_at: 2026-02-28T10:48:08.322439+00:00
description:
A security framework for handling structured data embedded within email messages, addressing trust relationships between senders and recipients. Provides guidelines for message user agents to safely process and display structured email content.


draft_name: draft-ietf-sml-trust
title: Spam/Virus Filter Integration
idea_type: mechanism
extracted_at: 2026-02-28T10:48:08.322439+00:00
description:
Mechanisms for integrating structured email processing with existing spam and virus filtering systems. Ensures that structured data doesn't bypass security controls or create new attack vectors.


draft_name: draft-ietf-sml-trust
title: Formal Data Display Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:48:08.322439+00:00
description:
Requirements for how message user agents should formally display structured data to users. Defines presentation standards to prevent spoofing and ensure clear identification of structured content.


draft_name: draft-ietf-sml-trust
title: Structured Email Security Considerations
idea_type: pattern
extracted_at: 2026-02-28T10:48:08.322439+00:00
description:
Comprehensive security analysis of threats and vulnerabilities specific to structured email implementations. Covers attack vectors unique to embedding structured data in email messages.


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
title: PQ/T Hybrid Key Exchange
idea_type: mechanism
extracted_at: 2026-02-28T10:48:20.508619+00:00
description:
A key exchange method that combines quantum-resistant ML-KEM (Module-Lattice-Based Key-Encapsulation Mechanism) with traditional ECDH for post-quantum security. Both mechanisms are executed in parallel and their shared secrets are combined.


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
title: ML-KEM Integration in SSH
idea_type: extension
extracted_at: 2026-02-28T10:48:20.508619+00:00
description:
Integration of the standardized Module-Lattice-Based Key-Encapsulation Mechanism into the SSH Transport Layer Protocol. Provides quantum-resistant key establishment capabilities for SSH connections.


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
title: Dual Key Material Combination
idea_type: mechanism
extracted_at: 2026-02-28T10:48:20.508619+00:00
description:
A method for securely combining shared secrets from both traditional ECDH and post-quantum ML-KEM key exchanges. Ensures security even if one of the underlying mechanisms is compromised.


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
title: SSH Transport Layer PQ Extension
idea_type: extension
extracted_at: 2026-02-28T10:48:20.508619+00:00
description:
Extension to the existing SSH Transport Layer Protocol to support post-quantum cryptographic methods. Maintains backward compatibility while adding quantum-resistant key exchange options.


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
title: Hybrid Key Exchange Message Format
idea_type: protocol
extracted_at: 2026-02-28T10:48:20.508619+00:00
description:
Specification of new SSH message formats and message numbers for carrying both traditional and post-quantum key exchange data. Defines the wire protocol for hybrid key exchanges in SSH.


draft_name: draft-ietf-sshm-ssh-agent
title: SSH Agent Message Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:48:26.233508+00:00
description:
A standardized protocol for communication between SSH clients and key agent processes using structured message formats. Defines specific message types for key operations and agent responses.


draft_name: draft-ietf-sshm-ssh-agent
title: Key Addition Messages
idea_type: mechanism
extracted_at: 2026-02-28T10:48:26.233508+00:00
description:
Protocol messages for adding private keys to the SSH agent, with specific formats for different key types including DSA and ECDSA. Enables secure storage and management of cryptographic keys.


draft_name: draft-ietf-sshm-ssh-agent
title: Generic Agent Response Framework
idea_type: pattern
extracted_at: 2026-02-28T10:48:26.233508+00:00
description:
Standardized response message format for SSH agents to communicate operation results and status back to clients. Provides consistent error handling and success notification.


draft_name: draft-ietf-sshm-ssh-agent
title: Key Type-Specific Message Formats
idea_type: mechanism
extracted_at: 2026-02-28T10:48:26.233508+00:00
description:
Distinct message structures for different cryptographic key types (DSA, ECDSA) to accommodate their unique parameters and requirements. Ensures proper handling of diverse key formats.


draft_name: draft-ietf-suit-firmware-encryption
title: Ephemeral-Static Diffie-Hellman Key Agreement
idea_type: mechanism
extracted_at: 2026-02-28T10:48:33.408560+00:00
description:
ES-DH mechanism using public key cryptography for key agreement in SUIT manifest encryption. Enables secure key establishment between firmware distributors and IoT devices.


draft_name: draft-ietf-suit-firmware-encryption
title: AES Key Wrap for Pre-Shared Keys
idea_type: mechanism
extracted_at: 2026-02-28T10:48:33.408560+00:00
description:
AES-KW mechanism for encrypting content encryption keys using pre-shared keys. Provides an alternative to public key cryptography for constrained devices.


draft_name: draft-ietf-suit-firmware-encryption
title: SUIT Manifest Encryption Extension
idea_type: extension
extracted_at: 2026-02-28T10:48:33.408560+00:00
description:
Extension to IETF SUIT manifest format to support encrypted payloads for firmware, software, ML models, and personalization data. Integrates encryption capabilities into the existing SUIT architecture.


draft_name: draft-ietf-suit-firmware-encryption
title: Hybrid Encryption Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:48:33.408560+00:00
description:
Pattern combining key agreement mechanisms (ES-DH or AES-KW) with symmetric encryption for payload protection. Balances security and performance for IoT firmware updates.


draft_name: draft-ietf-suit-firmware-encryption
title: Encrypted Firmware Update Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:48:33.408560+00:00
description:
Protocol specification for secure delivery of encrypted firmware and software updates using SUIT manifests. Defines the end-to-end process from encryption to decryption on target devices.


draft_name: draft-ietf-tls-deprecate-obsolete-kex
title: Finite Field Diffie-Hellman Deprecation
idea_type: requirement
extracted_at: 2026-02-28T10:48:44.303888+00:00
description:
Changes cipher suites using Diffie-Hellman over finite fields (FFDH/FFDHE) from SHOULD/MAY to MUST NOT in TLS 1.2. This affects DHE_RSA, DHE_DSS, DH_RSA, and DH_DSS key exchange methods.


draft_name: draft-ietf-tls-deprecate-obsolete-kex
title: RSA Key Exchange Deprecation
idea_type: requirement
extracted_at: 2026-02-28T10:48:44.303888+00:00
description:
Changes RSA key exchange cipher suites from SHOULD/MAY to MUST NOT in TLS 1.2. This removes support for RSA-based key transport methods where the client encrypts the pre-master secret with the server's RSA public key.


draft_name: draft-ietf-tls-deprecate-obsolete-kex
title: Static ECDH Discouragement
idea_type: requirement
extracted_at: 2026-02-28T10:48:44.303888+00:00
description:
Changes static Elliptic Curve Diffie-Hellman cipher suites (ECDH_RSA, ECDH_ECDSA) from SHOULD/MAY to SHOULD NOT in TLS 1.2. This discourages but does not fully prohibit their use.


draft_name: draft-ietf-tls-deprecate-obsolete-kex
title: TLS 1.2 Scope Limitation
idea_type: requirement
extracted_at: 2026-02-28T10:48:44.303888+00:00
description:
Applies deprecation rules only to TLS/DTLS 1.2, excluding older versions already deprecated by RFC 8996 and TLS 1.3 which doesn't use these algorithms. This creates version-specific cipher suite restrictions.


draft_name: draft-ietf-tls-deprecate-obsolete-kex
title: Multi-RFC Update Mechanism
idea_type: mechanism
extracted_at: 2026-02-28T10:48:44.303888+00:00
description:
Updates 17 different RFCs simultaneously to change cipher suite recommendations from permissive to restrictive language. This demonstrates a coordinated approach to deprecating cryptographic methods across multiple specifications.


draft_name: draft-ietf-tls-ecdhe-mlkem
title: X25519MLKEM768 Hybrid Key Agreement
idea_type: mechanism
extracted_at: 2026-02-28T10:48:52.257730+00:00
description:
A hybrid key agreement mechanism that combines X25519 elliptic curve Diffie-Hellman with ML-KEM-768 post-quantum key encapsulation. Provides both classical and post-quantum security properties in a single TLS 1.3 key exchange.


draft_name: draft-ietf-tls-ecdhe-mlkem
title: SecP256r1MLKEM768 Hybrid Key Agreement
idea_type: mechanism
extracted_at: 2026-02-28T10:48:52.257730+00:00
description:
A hybrid key agreement mechanism combining the NIST P-256 elliptic curve with ML-KEM-768 post-quantum algorithm. Offers a NIST-standardized elliptic curve option paired with post-quantum protection.


draft_name: draft-ietf-tls-ecdhe-mlkem
title: SecP384r1MLKEM1024 Hybrid Key Agreement
idea_type: mechanism
extracted_at: 2026-02-28T10:48:52.257730+00:00
description:
A hybrid key agreement mechanism that pairs the NIST P-384 elliptic curve with the higher-security ML-KEM-1024 variant. Provides enhanced security levels for both classical and post-quantum components.


draft_name: draft-ietf-tls-ecdhe-mlkem
title: Post-Quantum Hybrid Key Exchange Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:48:52.257730+00:00
description:
A general approach for combining classical ECDHE with post-quantum ML-KEM in TLS 1.3 key agreement. Enables quantum-resistant security while maintaining compatibility and performance characteristics.


draft_name: draft-ietf-tls-ecdhe-mlkem
title: ML-KEM Integration in TLS 1.3
idea_type: extension
extracted_at: 2026-02-28T10:48:52.257730+00:00
description:
Extension of TLS 1.3 key agreement to incorporate Module-Lattice-Based Key Encapsulation Mechanism algorithms. Defines how post-quantum KEM operations integrate with existing TLS handshake flows.


draft_name: draft-ietf-tls-extended-key-update
title: Extended Key Update Message
idea_type: protocol
extracted_at: 2026-02-28T10:49:00.344108+00:00
description:
A new TLS handshake message type that performs a fresh Diffie-Hellman key exchange within an active TLS 1.3 session. Unlike standard KeyUpdate, this incorporates new entropy to provide post-compromise security.


draft_name: draft-ietf-tls-extended-key-update
title: In-Session Diffie-Hellman Exchange
idea_type: mechanism
extracted_at: 2026-02-28T10:49:00.344108+00:00
description:
A mechanism to perform ephemeral Diffie-Hellman key exchanges during an established TLS session rather than only at handshake time. This generates fresh shared secrets without requiring session renegotiation.


draft_name: draft-ietf-tls-extended-key-update
title: Post-Compromise Security for Long-Lived Sessions
idea_type: requirement
extracted_at: 2026-02-28T10:49:00.344108+00:00
description:
A security property that ensures session keys can recover from compromise through periodic renewal with fresh entropy. This is particularly important for industrial IoT and telecommunications environments with persistent connections.


draft_name: draft-ietf-tls-extended-key-update
title: DTLS 1.3 Extended Key Update
idea_type: extension
extracted_at: 2026-02-28T10:49:00.344108+00:00
description:
Extension of the key update mechanism to DTLS 1.3 environments, adapting the fresh key exchange approach for datagram-based communications. This provides post-compromise security for UDP-based TLS sessions.


draft_name: draft-ietf-tls-extended-key-update
title: Entropy Refresh Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:49:00.344108+00:00
description:
A pattern for incorporating fresh cryptographic entropy into existing sessions through repeated key exchanges. This forces attackers to continuously exfiltrate new key material rather than relying on static compromised keys.


draft_name: draft-irtf-nmrg-llm-nm
title: Enhanced Telemetry Module
idea_type: architecture
extracted_at: 2026-02-28T10:49:07.918338+00:00
description:
A telemetry collection and processing module specifically designed to gather and format network data for LLM consumption. This module augments traditional telemetry systems to provide context-rich data suitable for AI-driven analysis.


draft_name: draft-irtf-nmrg-llm-nm
title: LLM Decision Module
idea_type: architecture
extracted_at: 2026-02-28T10:49:07.918338+00:00
description:
A dedicated component that processes network telemetry data through Large Language Models to generate network management recommendations and decisions. The module interfaces between raw network data and AI-powered decision making.


draft_name: draft-irtf-nmrg-llm-nm
title: Human-in-the-Loop Workflow
idea_type: mechanism
extracted_at: 2026-02-28T10:49:07.918338+00:00
description:
Standardized workflows that enforce human oversight and approval mechanisms for LLM-generated network management decisions. This ensures critical network changes require human validation before execution.


draft_name: draft-irtf-nmrg-llm-nm
title: Standardized Interaction Data Models
idea_type: protocol
extracted_at: 2026-02-28T10:49:07.918338+00:00
description:
Defined data structures and formats for communication between human operators and LLM-driven network management systems. These models ensure consistent and interoperable exchanges of network management information.


draft_name: draft-irtf-nmrg-llm-nm
title: LLM-Human Collaborative Framework
idea_type: architecture
extracted_at: 2026-02-28T10:49:07.918338+00:00
description:
An interoperable framework architecture that enables seamless collaboration between AI systems and human network operators while maintaining compatibility with existing network management protocols. The framework coordinates the interaction between enhanced telemetry, LLM decision making, and human oversight components.


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
title: Intent-Based SDV Management Framework
idea_type: framework
extracted_at: 2026-02-28T10:49:17.025457+00:00
description:
A comprehensive framework for managing networks, security, and applications in Software-Defined Vehicles using intent-based management principles. This enables easy and efficient configuration of SDV internal networks for communication with other vehicles and infrastructure.


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
title: Cloud-Native SDV Platform Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:49:17.025457+00:00
description:
Software-Defined Vehicles constructed using cloud-native system platforms like Kubernetes with internal networking capabilities. This architecture enables software-based vehicle functionality similar to cloud computing environments.


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
title: SDV-to-SDV Communication Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:49:17.025457+00:00
description:
Communication mechanism enabling Software-Defined Vehicles to interact with other SDVs and infrastructure nodes for safe driving and infotainment services. This supports vehicle-to-vehicle and vehicle-to-infrastructure connectivity in road networks.


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
title: Intent-Based Network Configuration
idea_type: mechanism
extracted_at: 2026-02-28T10:49:17.025457+00:00
description:
Management approach that allows high-level intent specification for automatic configuration of SDV internal networks. This simplifies network management by translating user intentions into specific network configurations.


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
title: Integrated Security Management
idea_type: mechanism
extracted_at: 2026-02-28T10:49:17.025457+00:00
description:
Intent-based security management system specifically designed for Software-Defined Vehicles operating in Intelligent Transportation Systems. This provides unified security control across the SDV platform and its communications.


draft_name: draft-jewell-aibdp
title: AI Boundary Declaration Protocol (AIBDP)
idea_type: protocol
extracted_at: 2026-02-28T10:49:24.003726+00:00
description:
A declarative framework for expressing machine-readable usage boundaries around web-hosted content in relation to AI systems. Provides permissions and denials for indexing, training, mimicry, representation, derivative construction, analytical exploitation, and agentic access.


draft_name: draft-jewell-aibdp
title: AIBDP Manifest Format
idea_type: mechanism
extracted_at: 2026-02-28T10:49:24.003726+00:00
description:
A structured format for declaring AI usage boundaries that builds on robots-style inclusion rules from RFC 7725. Enables content owners to specify granular permissions for different AI operations.


draft_name: draft-jewell-aibdp
title: AI Consent States
idea_type: pattern
extracted_at: 2026-02-28T10:49:24.003726+00:00
description:
A defined set of consent states that AI systems can interpret to determine permitted operations on web content. Provides standardized vocabulary for expressing boundaries around AI usage.


draft_name: draft-jewell-aibdp
title: HTTP 430 Status Code Integration
idea_type: extension
extracted_at: 2026-02-28T10:49:24.003726+00:00
description:
Interoperability mechanism that leverages HTTP status codes to communicate AI boundary violations. Enables web servers to respond with standardized error codes when AI boundaries are crossed.


draft_name: draft-jewell-aibdp
title: Granular AI Operation Categories
idea_type: architecture
extracted_at: 2026-02-28T10:49:24.003726+00:00
description:
Technical categorization of AI operations including indexing, training, mimicry, representation, derivative construction, analytical exploitation, and agentic access. Each category can have separate permission controls.


draft_name: draft-jia-oauth-scope-aggregation
title: OAuth Scope Aggregation Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:49:24.007255+00:00
description:
An authorization pattern where AI agents collect all required scopes across a multi-step workflow and perform a single OAuth authorization request instead of multiple requests. This reduces user consent fatigue and authorization round-trips.


draft_name: draft-jia-oauth-scope-aggregation
title: Security Member in Resource Metadata
idea_type: extension
extracted_at: 2026-02-28T10:49:24.007255+00:00
description:
A metadata extension that embeds OAuth scope requirements directly into resource descriptions. This allows AI agents to determine authorization needs before attempting resource access.


draft_name: draft-jia-oauth-scope-aggregation
title: Workflow Execution with Pre-Authorization
idea_type: mechanism
extracted_at: 2026-02-28T10:49:24.007255+00:00
description:
A mechanism where AI agents analyze complete workflows upfront to identify all required scopes, then execute the entire workflow using a single aggregated access token. This enables uninterrupted multi-step operations.


draft_name: draft-jiang-cats-reference-acn
title: AI-Agent Communication Network (ACN)
idea_type: architecture
extracted_at: 2026-02-28T10:49:31.578313+00:00
description:
A network architecture specifically designed to provide communication services among various types of AI-agents. It applies CATS-like information flow steering mechanisms to optimize AI-agent interactions.


draft_name: draft-jiang-cats-reference-acn
title: CATS-like Information Flow Steering for AI-Agents
idea_type: mechanism
extracted_at: 2026-02-28T10:49:31.578313+00:00
description:
An adaptation of Computing-Aware Traffic Steering (CATS) techniques to optimize communication paths and resource allocation in AI-agent networks. This extends traditional CATS frameworks to handle AI-agent specific traffic patterns.


draft_name: draft-jiang-cats-reference-acn
title: CATS Reference Points for ACN
idea_type: architecture
extracted_at: 2026-02-28T10:49:31.578313+00:00
description:
Standardized interface definitions and reference points that enable interoperability between different components in the AI-agent communication network. These define how AI-agents interact with the underlying CATS infrastructure.


draft_name: draft-jiang-cats-reference-acn
title: ACN Service Provisioning Model
idea_type: protocol
extracted_at: 2026-02-28T10:49:31.578313+00:00
description:
A framework for delivering and managing communication services tailored to AI-agent requirements within the CATS-enabled network. It defines how services are discovered, allocated, and consumed by AI-agents.


draft_name: draft-jiang-cats-reference-acn
title: CATS-like Metrics Model for ACN
idea_type: mechanism
extracted_at: 2026-02-28T10:49:31.578313+00:00
description:
A specialized metrics framework that measures and evaluates network performance parameters specific to AI-agent communications. This extends traditional CATS metrics to account for AI-agent workload characteristics.


draft_name: draft-jiang-seat-dynamic-attestation
title: AI Agent Runtime Posture
idea_type: architecture
extracted_at: 2026-02-28T10:49:38.434526+00:00
description:
A comprehensive security posture model for AI agents that includes platform TCB, agent manifest (models, tools, policies), and committed runtime context. This posture can change frequently and unpredictably during long-lived sessions.


draft_name: draft-jiang-seat-dynamic-attestation
title: Dynamic Attestation for Long-lived Sessions
idea_type: mechanism
extracted_at: 2026-02-28T10:49:38.434526+00:00
description:
A mechanism to continuously update and convey remote attestation information during ongoing TLS sessions. This allows verification of changing runtime states without re-establishing connections.


draft_name: draft-jiang-seat-dynamic-attestation
title: Runtime Context-based Authorization
idea_type: pattern
extracted_at: 2026-02-28T10:49:38.434526+00:00
description:
An authorization pattern where relying parties make access control decisions based on the current runtime posture of communicating AI agents. This enables fine-grained security policies that adapt to agent state changes.


draft_name: draft-jiang-seat-dynamic-attestation
title: AI Agent Manifest Attestation
idea_type: mechanism
extracted_at: 2026-02-28T10:49:38.434526+00:00
description:
A component of the attestation framework that verifies the models, tools, and policies currently loaded and active in an AI agent. This provides assurance about the agent's capabilities and constraints.


draft_name: draft-josefsson-chempat
title: Chempat Generic Combiner
idea_type: mechanism
extracted_at: 2026-02-28T10:49:46.220286+00:00
description:
A generic construct for combining traditional and post-quantum key encapsulation mechanisms that can be analyzed separately for security assurance. Provides a framework for creating hybrid PQ/T KEMs with modular security analysis.


draft_name: draft-josefsson-chempat
title: PQ/T Hybrid KEM Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:49:46.220286+00:00
description:
Architecture combining traditional Diffie-Hellman key agreement with post-quantum cryptographic methods in a single key encapsulation mechanism. Enables quantum-resistant cryptography while maintaining backward compatibility.


draft_name: draft-josefsson-chempat
title: Multi-Curve Traditional Component Support
idea_type: extension
extracted_at: 2026-02-28T10:49:46.220286+00:00
description:
Support for multiple elliptic curves including P-256, P-384, X25519, X448, and brainpool curves (P256, P384, P512) as the traditional cryptographic component. Provides flexibility in choosing appropriate curve security levels.


draft_name: draft-josefsson-chempat
title: Multi-Algorithm Post-Quantum Integration
idea_type: mechanism
extracted_at: 2026-02-28T10:49:46.220286+00:00
description:
Integration of multiple post-quantum algorithms including ML-KEM-768/1024, Streamlined NTRU Prime sntrup761, Classic McEliece, and FrodoKEM. Enables selection of appropriate PQ algorithms based on security and performance requirements.


draft_name: draft-josefsson-chempat
title: Concrete Instantiated Algorithm Specifications
idea_type: protocol
extracted_at: 2026-02-28T10:49:46.220286+00:00
description:
Specific combinations of traditional and post-quantum algorithms provided as concrete instantiated algorithms ready for protocol integration. Eliminates the need for implementers to design their own hybrid combinations.


draft_name: draft-jurkovikj-collab-tunnel
title: Bidirectional URL Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:49:53.693864+00:00
description:
A mechanism allowing both servers and clients to discover relevant URLs for content synchronization. Enables efficient crawling by letting servers suggest which URLs automated agents should request.


draft_name: draft-jurkovikj-collab-tunnel
title: Template-Invariant Content Fingerprinting
idea_type: mechanism
extracted_at: 2026-02-28T10:49:53.693864+00:00
description:
A fingerprinting method that generates consistent hashes for content regardless of template changes or cosmetic modifications. Uses strong ETags to identify when actual content has changed versus just presentation.


draft_name: draft-jurkovikj-collab-tunnel
title: Sitemap-First Verification
idea_type: pattern
extracted_at: 2026-02-28T10:49:53.693864+00:00
description:
A protocol pattern that prioritizes sitemap validation before content retrieval. Ensures automated agents work with accurate URL mappings and canonical references.


draft_name: draft-jurkovikj-collab-tunnel
title: Strict Conditional Request Discipline
idea_type: requirement
extracted_at: 2026-02-28T10:49:53.693864+00:00
description:
A requirement for rigorous use of HTTP conditional headers (If-None-Match, If-Modified-Since) to minimize bandwidth. Enforces precise cache validation to avoid unnecessary content transfers.


draft_name: draft-jurkovikj-collab-tunnel
title: Collaboration Tunnel Protocol (TCT)
idea_type: protocol
extracted_at: 2026-02-28T10:49:53.693864+00:00
description:
An HTTP-based protocol for efficient delivery of web content to automated agents. Combines multiple optimization techniques while preserving canonical URL structure.


draft_name: draft-jurkovikj-httpapi-agentic-state
title: Semantic Validators (Content Identity)
idea_type: mechanism
extracted_at: 2026-02-28T10:49:59.326550+00:00
description:
HTTP header mechanism to track the logical state of a resource independent of its serialization format. Enables consistency checking across different representations of the same resource.


draft_name: draft-jurkovikj-httpapi-agentic-state
title: Canonical Resource State (CRS)
idea_type: architecture
extracted_at: 2026-02-28T10:49:59.326550+00:00
description:
Architecture for maintaining a unified logical state that underlies multiple HTTP representations. Provides a single source of truth for resource state across different content types.


draft_name: draft-jurkovikj-httpapi-agentic-state
title: Agentic State Transfer (AST) Profile
idea_type: protocol
extracted_at: 2026-02-28T10:49:59.326550+00:00
description:
HTTP profile that mandates optimistic concurrency control via If-Match headers for all state-changing operations. Ensures atomic and consistent mutations across synchronized representations.


draft_name: draft-jurkovikj-httpapi-agentic-state
title: Cross-Representation Consistency Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:49:59.326550+00:00
description:
Pattern for synchronizing state changes across multiple content-negotiated representations of the same resource. Solves race conditions between clients using different representation formats.


draft_name: draft-jurkovikj-httpapi-agentic-state
title: Mandatory Optimistic Concurrency Control
idea_type: requirement
extracted_at: 2026-02-28T10:49:59.326550+00:00
description:
Requirement that all state-changing operations must include If-Match headers with semantic validators. Prevents lost updates in multi-client environments with automated agents.


draft_name: draft-kale-agntcy-federated-privacy
title: Multi-Tenant Federated Averaging
idea_type: mechanism
extracted_at: 2026-02-28T10:50:05.779840+00:00
description:
A federated averaging mechanism adapted for multi-tenant AI agent systems that enables model parameter aggregation across organizational boundaries. The protocol maintains tenant isolation while allowing collaborative learning from distributed agent behaviors.


draft_name: draft-kale-agntcy-federated-privacy
title: Differential Privacy for Agent Models
idea_type: mechanism
extracted_at: 2026-02-28T10:50:05.779840+00:00
description:
Integration of differential privacy mechanisms specifically designed for AI agent model training to provide formal privacy guarantees. This prevents sensitive behavioral data exposure during cross-tenant knowledge transfer.


draft_name: draft-kale-agntcy-federated-privacy
title: Secure Aggregation Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:50:05.779840+00:00
description:
A secure aggregation protocol that enables privacy-preserving combination of model updates from multiple tenants. The protocol ensures that individual tenant contributions cannot be reverse-engineered from the aggregated results.


draft_name: draft-kale-agntcy-federated-privacy
title: Cross-Tenant Knowledge Transfer
idea_type: pattern
extracted_at: 2026-02-28T10:50:05.779840+00:00
description:
An architecture pattern that enables AI agents to benefit from learning across organizational boundaries without data sharing. This allows agents to improve performance through collaborative training while maintaining strict data isolation.


draft_name: draft-kale-agntcy-federated-privacy
title: Privacy-Preserving Reference Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:50:05.779840+00:00
description:
A comprehensive reference architecture that combines federated learning, differential privacy, and secure aggregation for multi-tenant AI deployments. The architecture provides formal privacy guarantees while enabling collaborative model improvement.


draft_name: draft-kartha-grd
title: Location-Based Resource Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:50:14.583752+00:00
description:
A discovery mechanism that uses physical location and observer context as the starting point for finding resources, rather than predefined identifiers. This enables applications to discover relevant digital resources based on where they are physically located.


draft_name: draft-kartha-grd
title: Spatial Query Interface
idea_type: mechanism
extracted_at: 2026-02-28T10:50:14.583752+00:00
description:
A query mechanism that allows clients to request resources based on geospatial parameters like coordinates, proximity, and spatial relationships. This differs from traditional name-based lookups by using geometric and geographic criteria.


draft_name: draft-kartha-grd
title: Observer Context Framework
idea_type: architecture
extracted_at: 2026-02-28T10:50:14.583752+00:00
description:
A contextual framework that incorporates the observer's physical presence, orientation, and situational context into resource discovery. This enables personalized and contextually relevant resource identification.


draft_name: draft-kartha-grd
title: Geospatial Resource Discovery Service
idea_type: architecture
extracted_at: 2026-02-28T10:50:14.583752+00:00
description:
A network service architecture that bridges the gap between physical location and digital resource identification. It provides standardized mechanisms for spatial-based resource resolution complementing existing identifier-based systems.


draft_name: draft-kartha-grd
title: Physical-to-Digital Mapping
idea_type: mechanism
extracted_at: 2026-02-28T10:50:14.583752+00:00
description:
A mechanism for creating associations between physical locations or objects and their corresponding digital resources. This enables the translation from spatial coordinates to network-accessible content or services.


draft_name: draft-kompella-lsr-mptecap
title: MPTE Node Capability Advertisement
idea_type: mechanism
extracted_at: 2026-02-28T10:50:21.036824+00:00
description:
A mechanism to advertise whether a node supports Multipath Traffic Engineering (MPTE) functionality via IGP extensions. This allows ingress nodes and path computation agents to identify which nodes can participate in MPTE tunnel provisioning and maintenance.


draft_name: draft-kompella-lsr-mptecap
title: Link State Routing TE Capabilities Extension
idea_type: extension
extracted_at: 2026-02-28T10:50:21.036824+00:00
description:
An extension to existing Link State Routing Traffic Engineering capabilities to carry MPTE-specific node characteristics. This builds upon RFC 5073 to distribute MPTE capability information through the IGP.


draft_name: draft-kompella-lsr-mptecap
title: MPTE Topology Discovery
idea_type: pattern
extracted_at: 2026-02-28T10:50:21.036824+00:00
description:
A pattern for distributing network topology and node characteristics information required for computing MPTE tunnel components. This enables nodes to have sufficient information about network capabilities for multipath traffic engineering decisions.


draft_name: draft-kompella-lsr-mptecap
title: Multipath Traffic Engineering Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:50:21.036824+00:00
description:
A hybrid approach combining equal-cost multipath and constraint-based traffic engineering for network traffic management. This architecture requires capability awareness across network nodes for effective tunnel computation and deployment.


draft_name: draft-kotecha-agentic-dispute-protocol
title: ADP Message Format Standard
idea_type: protocol
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Standardized message formats for autonomous agents to file, process, and resolve disputes through structured communication. Defines specific JSON schemas and transport mechanisms for dispute-related communications.


draft_name: draft-kotecha-agentic-dispute-protocol
title: Cryptographic Evidence Submission
idea_type: mechanism
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Cryptographic proof requirements and standards for submitting evidence in automated dispute resolution. Ensures integrity and authenticity of evidence submitted by AI agents.


draft_name: draft-kotecha-agentic-dispute-protocol
title: Chain of Custody Tracking
idea_type: mechanism
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Automated tracking mechanism that maintains an auditable chain of custody for evidence and documents throughout the dispute resolution process. Provides cryptographic proof of document handling.


draft_name: draft-kotecha-agentic-dispute-protocol
title: Dual-Format Award Specification
idea_type: pattern
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Awards and decisions are generated in both machine-readable JSON format and human-readable PDF format. Enables both automated processing and legal compliance requirements.


draft_name: draft-kotecha-agentic-dispute-protocol
title: Arbitrator Discovery Protocol
idea_type: mechanism
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Automated mechanism for AI agents to discover and select appropriate arbitrators or dispute resolution services. Includes capability matching and availability verification.


draft_name: draft-kotecha-agentic-dispute-protocol
title: Multi-Framework Resolution Support
idea_type: extension
extracted_at: 2026-02-28T10:50:29.432316+00:00
description:
Protocol extension supporting multiple dispute resolution approaches including expert determination, binding arbitration, mediation, and hybrid methods. Allows flexible resolution pathway selection.


draft_name: draft-lake-pocero-authkem-edhoc
title: KEM-based Authentication for EDHOC
idea_type: extension
extracted_at: 2026-02-28T10:50:36.189476+00:00
description:
Extension to EDHOC protocol that replaces signature-based authentication with Key Encapsulation Mechanism (KEM) operations for post-quantum security. Enables signature-free authentication using PQC KEMs like ML-KEM.


draft_name: draft-lake-pocero-authkem-edhoc
title: Post-Quantum EDHOC Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:50:36.189476+00:00
description:
Modified EDHOC protocol that incorporates Post-Quantum Cryptography mechanisms for both key exchange and authentication to provide resistance against quantum computer adversaries. Maintains EDHOC's lightweight design while adding quantum resistance.


draft_name: draft-lake-pocero-authkem-edhoc
title: Signature-Free PQC Authentication
idea_type: mechanism
extracted_at: 2026-02-28T10:50:36.189476+00:00
description:
Authentication method that eliminates the need for post-quantum digital signatures by using KEM operations instead. Reduces computational and communication overhead compared to PQC signature schemes.


draft_name: draft-lake-pocero-authkem-edhoc
title: ML-KEM Integration
idea_type: mechanism
extracted_at: 2026-02-28T10:50:36.189476+00:00
description:
Specific integration of NIST-standardized ML-KEM (Module-Lattice-based KEM) into the EDHOC authentication flow. Provides concrete post-quantum security using standardized cryptographic primitives.


draft_name: draft-lake-pocero-authkem-edhoc
title: Quantum-Resistant Key Exchange
idea_type: mechanism
extracted_at: 2026-02-28T10:50:36.189476+00:00
description:
Combined approach using both traditional ECDH and post-quantum KEMs for key establishment. Provides hybrid security that protects against both classical and quantum attacks.


draft_name: draft-lake-pocero-authkem-ikr-edhoc
title: IKR Three-Message Handshake
idea_type: protocol
extracted_at: 2026-02-28T10:50:43.561369+00:00
description:
A reduced three-message EDHOC handshake protocol optimized for scenarios where the Initiator already knows the Responder's credentials. This eliminates the need for a fourth message while maintaining mutual authentication.


draft_name: draft-lake-pocero-authkem-ikr-edhoc
title: KEM-based Authentication for EDHOC
idea_type: mechanism
extracted_at: 2026-02-28T10:50:43.561369+00:00
description:
Authentication mechanism that replaces traditional signatures with Key Encapsulation Mechanism operations in EDHOC protocol. Enables post-quantum security when using PQC KEMs like ML-KEM while maintaining signature-free operation.


draft_name: draft-lake-pocero-authkem-ikr-edhoc
title: Initiator-Known Responder (IKR) Scenario
idea_type: pattern
extracted_at: 2026-02-28T10:50:43.561369+00:00
description:
A specific deployment pattern for constrained environments where the protocol initiator has prior knowledge of the responder's credentials. This allows for protocol optimizations that reduce message overhead.


draft_name: draft-lake-pocero-authkem-ikr-edhoc
title: Post-Quantum KEM Integration
idea_type: extension
extracted_at: 2026-02-28T10:50:43.561369+00:00
description:
Integration of NIST-standardized ML-KEM and other post-quantum cryptography KEMs into the EDHOC lightweight protocol. Provides quantum-resistant authentication without requiring digital signatures.


draft_name: draft-lake-pocero-authkem-ikr-edhoc
title: Forward Secrecy with Identity Protection
idea_type: mechanism
extracted_at: 2026-02-28T10:50:43.561369+00:00
description:
Security mechanism that ensures both forward secrecy of session keys and partial identity protection for communicating parties. Maintained even in the optimized three-message handshake variant.


draft_name: draft-lenders-core-dnr
title: OSCORE Discovery via DNS SVCB
idea_type: mechanism
extracted_at: 2026-02-28T10:50:49.302541+00:00
description:
Using DNS SVCB records to discover endpoints that communicate using OSCORE for secure CoAP communications. This enables hosts to learn about CoAP servers and DNS over CoAP resolvers that use OSCORE encryption.


draft_name: draft-lenders-core-dnr
title: EDHOC Key Exchange Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:50:49.302541+00:00
description:
Discovery mechanism for endpoints that use Ephemeral Diffie-Hellman Over COSE (EDHOC) for key exchange in conjunction with OSCORE. This allows hosts to identify resolvers supporting this key establishment method.


draft_name: draft-lenders-core-dnr
title: Security Context Exchange Limitation
idea_type: requirement
extracted_at: 2026-02-28T10:50:49.302541+00:00
description:
Technical challenge where SVCB records cannot be used to exchange security contexts required for OSCORE scenarios. This represents a fundamental limitation in using standard SVCB records for secure discovery.


draft_name: draft-lenders-core-dnr
title: DNS over CoAP Resolver Discovery
idea_type: pattern
extracted_at: 2026-02-28T10:50:49.302541+00:00
description:
Discovery pattern for DNS resolvers that operate over CoAP protocol with OSCORE security. This enables identification of constrained environment DNS resolvers with appropriate security mechanisms.


draft_name: draft-leon-distributed-multi-signer
title: Multi-Signer Agent (MSA)
idea_type: architecture
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
A dedicated entity responsible for managing the multi-signer process in distributed DNSSEC environments. The MSA handles coordination between multiple DNS providers and maintains secure communication channels.


draft_name: draft-leon-distributed-multi-signer
title: Combiner Component
idea_type: architecture
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
A specialized component that combines unsigned zone data from the zone owner with zone data under control of the MSA. It serves as the integration point for merging zone content in multi-signer scenarios.


draft_name: draft-leon-distributed-multi-signer
title: HSYNC DNS Resource Record Type
idea_type: extension
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
A new DNS RRtype used by zone owners to designate their chosen DNS providers for signing and/or serving zones. It provides a standardized way to signal multi-signer configuration.


draft_name: draft-leon-distributed-multi-signer
title: DNS SIG(0) Secured Communication
idea_type: mechanism
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
A pure DNS communication mechanism where MSAs exchange messages secured using DNS SIG(0) signatures. This enables secure coordination without requiring external protocols.


draft_name: draft-leon-distributed-multi-signer
title: RESTful API with TLS Security
idea_type: protocol
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
An alternative secure communication channel for MSAs using RESTful APIs protected by TLS. This provides a web-based approach for MSA coordination alongside the DNS-native option.


draft_name: draft-leon-distributed-multi-signer
title: Leader/Follower and Peer Synchronization Modes
idea_type: pattern
extracted_at: 2026-02-28T10:50:56.978245+00:00
description:
Two distinct models for multi-signer process synchronization with a defined mechanism for MSAs to collectively decide which model to use for a given zone. This provides flexibility in coordination strategies.


draft_name: draft-levy-llm-uri-scheme
title: LLM URI Scheme
idea_type: protocol
extracted_at: 2026-02-28T10:51:02.097195+00:00
description:
A new URI scheme 'llm://' for identifying Large Language Model endpoints and their configuration. Encodes provider host, model identifier, authentication credentials, and inference parameters into a single portable connection string.


draft_name: draft-levy-llm-uri-scheme
title: LLM Connection String Format
idea_type: mechanism
extracted_at: 2026-02-28T10:51:02.097195+00:00
description:
A standardized format analogous to database connection URIs (like PostgreSQL and MongoDB) for LLM endpoints. Provides a portable way to specify complete LLM connection and configuration information.


draft_name: draft-levy-llm-uri-scheme
title: LLM URI Parameter Encoding
idea_type: pattern
extracted_at: 2026-02-28T10:51:02.097195+00:00
description:
Method for encoding inference parameters and authentication credentials directly within the URI structure. Allows complete LLM configuration to be expressed in a single string.


draft_name: draft-levy-llm-uri-scheme
title: IANA URI Scheme Registration
idea_type: requirement
extracted_at: 2026-02-28T10:51:02.097195+00:00
description:
Provisional registration of the 'llm' scheme name in the IANA Uniform Resource Identifier Schemes registry. Follows RFC 7595 registration procedures for new URI schemes.


draft_name: draft-li-dmsc-inf-architecture
title: DMSC Infrastructure Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:51:09.778827+00:00
description:
A systematic architectural framework that enables network control and forwarding functions to actively participate in multi-agent collaboration. The architecture focuses on infrastructure-level capabilities rather than application-level coordination.


draft_name: draft-li-dmsc-inf-architecture
title: Active Network Participation
idea_type: mechanism
extracted_at: 2026-02-28T10:51:09.778827+00:00
description:
A mechanism where network infrastructure components (control and forwarding functions) actively engage in agent collaboration rather than passively routing traffic. This enables the network to become a collaborative participant in multi-agent systems.


draft_name: draft-li-dmsc-inf-architecture
title: Large-scale Agent Collaboration Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:51:09.778827+00:00
description:
Network requirements specifically identified for enabling collaboration between large numbers of agents. These requirements drive the need for specialized infrastructure capabilities beyond traditional networking.


draft_name: draft-li-dmsc-inf-architecture
title: Dynamic Multi-agent Secured Collaboration (DMSC) Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:51:09.778827+00:00
description:
A systematic approach and protocol framework for enabling secure collaboration between dynamically changing sets of agents. The protocol integrates security mechanisms with dynamic collaboration patterns.


draft_name: draft-li-dmsc-inf-architecture
title: Infrastructure Functions for Active Networks
idea_type: extension
extracted_at: 2026-02-28T10:51:09.778827+00:00
description:
Specific network functions that enable infrastructure to actively participate in agent collaboration workflows. These functions extend beyond traditional packet forwarding to include collaboration-aware processing.


draft_name: draft-li-dmsc-macp
title: Agent Gateway
idea_type: architecture
extracted_at: 2026-02-28T10:51:16.636275+00:00
description:
A key entity that serves as an intermediary for agent registration, authentication, and capability management. It enables scalable collaboration while preserving direct peer-to-peer semantic interactions among agents.


draft_name: draft-li-dmsc-macp
title: Multi-agent Collaboration Protocol Suite
idea_type: protocol
extracted_at: 2026-02-28T10:51:16.636275+00:00
description:
A protocol suite that enables distributed agents to collaborate across heterogeneous networks through gateway-mediated coordination. It provides semantically driven interactions between agents in different network domains.


draft_name: draft-li-dmsc-macp
title: Gateway-mediated Agent Registration
idea_type: mechanism
extracted_at: 2026-02-28T10:51:16.636275+00:00
description:
A mechanism where agents register their capabilities and presence through Agent Gateways. This enables discovery and coordination of distributed agents across network boundaries.


draft_name: draft-li-dmsc-macp
title: Capability Management System
idea_type: mechanism
extracted_at: 2026-02-28T10:51:16.636275+00:00
description:
A system for managing and advertising agent capabilities through the gateway infrastructure. It allows agents to discover and utilize services provided by other agents in the collaboration network.


draft_name: draft-li-dmsc-macp
title: Semantic-driven Direct P2P Interactions
idea_type: pattern
extracted_at: 2026-02-28T10:51:16.636275+00:00
description:
A pattern where agents can engage in direct peer-to-peer communication using semantic protocols after initial gateway-mediated discovery. This preserves efficiency while maintaining the benefits of gateway coordination.


draft_name: draft-li-dmsc-mcps-agw
title: Agent Gateway Control Plane
idea_type: architecture
extracted_at: 2026-02-28T10:51:23.192803+00:00
description:
Centralized control-plane entities that handle agent registration, authentication, capability management, and semantic routing while allowing direct peer-to-peer interactions between agents. Agent Gateways act as intermediaries for control functions without interfering with data plane communications.


draft_name: draft-li-dmsc-mcps-agw
title: Agent Registration and Authorization Process
idea_type: protocol
extracted_at: 2026-02-28T10:51:23.192803+00:00
description:
Standardized process for agents to register with Agent Gateways and obtain authorization credentials. Enables secure onboarding of distributed agents across heterogeneous networks.


draft_name: draft-li-dmsc-mcps-agw
title: Capability Digest and Synchronization
idea_type: mechanism
extracted_at: 2026-02-28T10:51:23.192803+00:00
description:
Mechanism for agents to advertise their capabilities to Agent Gateways and synchronize capability information across the network. Enables efficient capability discovery and matching for collaboration.


draft_name: draft-li-dmsc-mcps-agw
title: Semantic Resolution and Routing
idea_type: protocol
extracted_at: 2026-02-28T10:51:23.192803+00:00
description:
Protocol for Agent Gateways to perform semantic-based routing of agent requests and resolve semantic queries to appropriate target agents. Enables intelligent routing based on agent capabilities and semantic context.


draft_name: draft-li-dmsc-mcps-agw
title: Task-based Multi-Agent Coordination
idea_type: pattern
extracted_at: 2026-02-28T10:51:23.192803+00:00
description:
Framework for coordinating multiple agents to collaborate on complex tasks while maintaining direct peer-to-peer semantic interactions. Preserves agent autonomy while enabling structured collaboration patterns.


draft_name: draft-li-semantic-routing-architecture
title: Intent Vector Routing
idea_type: mechanism
extracted_at: 2026-02-28T10:51:30.360588+00:00
description:
Uses multi-dimensional vectors representing AI agent intentions and capabilities to make routing decisions. Enables semantic matching between agent requests and available services based on intent similarity.


draft_name: draft-li-semantic-routing-architecture
title: Trust Score-based Policy Enforcement
idea_type: mechanism
extracted_at: 2026-02-28T10:51:30.360588+00:00
description:
Incorporates dynamic trust scores into routing decisions to enforce security policies. Trust scores are calculated based on agent behavior and used to determine communication permissions.


draft_name: draft-li-semantic-routing-architecture
title: Application-layer Semantic Routing
idea_type: architecture
extracted_at: 2026-02-28T10:51:30.360588+00:00
description:
Routes traffic based on semantic understanding of service identity, intent, and context rather than traditional IP addresses. Operates above the transport layer to enable intelligent path selection.


draft_name: draft-li-semantic-routing-architecture
title: Adaptive Multi-agent Routing
idea_type: mechanism
extracted_at: 2026-02-28T10:51:30.360588+00:00
description:
Dynamically adjusts routing decisions based on changing agent capabilities and network conditions. Supports real-time adaptation for multi-agent collaborative environments.


draft_name: draft-li-semantic-routing-architecture
title: Cognitive Networking Substrate
idea_type: architecture
extracted_at: 2026-02-28T10:51:30.360588+00:00
description:
Transforms the network from passive transport to an intelligent collaboration layer that understands agent communication patterns. Enables the network infrastructure to participate in multi-agent coordination.


draft_name: draft-liang-agentdns
title: AgentDNS Hierarchical Namespace
idea_type: architecture
extracted_at: 2026-02-28T10:51:37.630698+00:00
description:
A DNS-inspired hierarchical naming system specifically designed for LLM agents and their services. Uses domain-like structure to organize agent services across different vendors.


draft_name: draft-liang-agentdns
title: Semantic Service Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:51:37.630698+00:00
description:
Discovery mechanism that allows agents to find services based on semantic descriptions rather than exact names. Enables autonomous service location for LLM agents.


draft_name: draft-liang-agentdns
title: Protocol-Aware Interoperability
idea_type: mechanism
extracted_at: 2026-02-28T10:51:37.630698+00:00
description:
System that understands and mediates between different agent communication protocols. Enables cross-vendor agent collaboration by handling protocol differences.


draft_name: draft-liang-agentdns
title: Unified Authentication and Billing
idea_type: mechanism
extracted_at: 2026-02-28T10:51:37.630698+00:00
description:
Single authentication and billing framework for agent service invocations across multiple vendors. Provides trust management for large-scale agent ecosystems.


draft_name: draft-liang-agentdns
title: Agent Service Resolution Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:51:37.630698+00:00
description:
DNS-like resolution protocol adapted for agent services that maps agent service names to callable endpoints. Supports autonomous service invocation by LLM agents.


draft_name: draft-liu-access-collaboration-agent
title: Identity Authentication and Request Verification
idea_type: mechanism
extracted_at: 2026-02-28T10:51:43.666639+00:00
description:
Authentication mechanism for verifying AI agent identities and validating requests in ubiquitous access scenarios. Ensures secure agent-to-agent communication across different access networks.


draft_name: draft-liu-access-collaboration-agent
title: Service Discovery and Automatic Negotiation
idea_type: protocol
extracted_at: 2026-02-28T10:51:43.666639+00:00
description:
Protocol mechanism enabling AI agents to automatically discover available services and negotiate capabilities. Facilitates dynamic service binding in multi-access collaboration environments.


draft_name: draft-liu-access-collaboration-agent
title: Unified Communication Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:51:43.666639+00:00
description:
Single protocol standard for AI agent communication across heterogeneous networks and devices. Abstracts underlying network differences to enable seamless agent collaboration.


draft_name: draft-liu-access-collaboration-agent
title: Connection Stability and Seamless Handover
idea_type: mechanism
extracted_at: 2026-02-28T10:51:43.666639+00:00
description:
Mechanism to maintain stable connections and enable seamless handover between different access networks. Ensures continuous AI agent collaboration during network transitions.


draft_name: draft-liu-access-collaboration-agent
title: Multi Access Collaboration Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:51:43.666639+00:00
description:
Architectural pattern enabling AI agents to collaborate across multiple access technologies simultaneously. Supports scenarios where agents operate through different network access methods.


draft_name: draft-liu-agent-context-protocol
title: Agent Context Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:51:43.671073+00:00
description:
A standardized protocol for communicating context information between AI agents. Defines message formats and communication patterns for agent-to-agent context sharing.


draft_name: draft-liu-agent-context-protocol
title: Agent Context Message Format
idea_type: mechanism
extracted_at: 2026-02-28T10:51:43.671073+00:00
description:
A structured message format for encoding and transmitting context information between AI agents. Provides standardized fields and data structures for context exchange.


draft_name: draft-liu-agent-context-protocol
title: Multi-Agent Context Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:51:43.671073+00:00
description:
An architectural framework defining how AI agents can share and maintain context information across distributed systems. Establishes the overall system design for agent context communication.


draft_name: draft-liu-agent-operation-authorization
title: Agent Operation Authorization Request
idea_type: mechanism
extracted_at: 2026-02-28T10:51:50.738307+00:00
description:
A mechanism to convert natural language input into human-readable operation proposals formatted as JSON Web Tokens. This enables structured representation of intended agent actions before authorization.


draft_name: draft-liu-agent-operation-authorization
title: Agent Operation Authorization Token
idea_type: mechanism
extracted_at: 2026-02-28T10:51:50.738307+00:00
description:
A JWT-based token that represents cryptographically verified authorization for specific agent operations. The token is enforceable at runtime by agents and verifiers to prevent unauthorized actions.


draft_name: draft-liu-agent-operation-authorization
title: Two-Phase Authorization Framework
idea_type: architecture
extracted_at: 2026-02-28T10:51:50.738307+00:00
description:
A structured approach separating operation proposal (request phase) from confirmed authorization (token phase). This enables human review and approval before granting execution permissions to autonomous agents.


draft_name: draft-liu-agent-operation-authorization
title: Fine-Grained Agent Operation Control
idea_type: pattern
extracted_at: 2026-02-28T10:51:50.738307+00:00
description:
A framework enabling precise control over specific operations that AI agents can perform. This prevents overly broad permissions and enables granular delegation of authority.


draft_name: draft-liu-agent-operation-authorization
title: Cryptographic User Intent Verification
idea_type: mechanism
extracted_at: 2026-02-28T10:51:50.738307+00:00
description:
A mechanism using cryptographic signatures to verify that agent operations align with actual user intent. This prevents agents from performing hallucinated or unauthorized actions.


draft_name: draft-liu-dmsc-acps-arc
title: Agent Collaboration Protocols (ACPs) Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
A comprehensive architecture framework that includes conceptual domains, functional components and reference interfaces to enable agent interconnection and collaboration across heterogeneous agent systems. Covers the complete lifecycle from agent access to active collaboration.


draft_name: draft-liu-dmsc-acps-arc
title: Agent Trusted Registration
idea_type: mechanism
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
A mechanism for securely onboarding agents into the Internet of Agents network with trusted identity establishment. Provides the foundation for secure agent-to-agent interactions.


draft_name: draft-liu-dmsc-acps-arc
title: Agent Identity Authentication
idea_type: protocol
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
Authentication protocols specifically designed for verifying agent identities in the IoA ecosystem. Ensures only legitimate agents can participate in collaboration activities.


draft_name: draft-liu-dmsc-acps-arc
title: Agent Discovery Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
A discovery mechanism that allows agents to find and identify other agents with relevant capabilities for collaborative task execution. Enables dynamic formation of agent collaborations.


draft_name: draft-liu-dmsc-acps-arc
title: Agent Interaction Framework
idea_type: protocol
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
Standardized interaction patterns and protocols for enabling communication and coordination between heterogeneous agents. Facilitates seamless collaboration across different agent implementations.


draft_name: draft-liu-dmsc-acps-arc
title: Tool Invocation Interface
idea_type: mechanism
extracted_at: 2026-02-28T10:51:57.803784+00:00
description:
A standardized interface mechanism that allows agents to invoke and utilize external tools and services during collaborative tasks. Extends agent capabilities through external resource integration.


draft_name: draft-liu-dmsc-gw-requirements
title: Delegated Agent Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:52:04.869184+00:00
description:
Mechanism allowing DMSC gateways to perform agent discovery operations on behalf of requesting agents. Enables scalable discovery in multi-agent systems without direct peer-to-peer discovery overhead.


draft_name: draft-liu-dmsc-gw-requirements
title: ID-based Agent Location Resolution
idea_type: mechanism
extracted_at: 2026-02-28T10:52:04.869184+00:00
description:
Service that maps agent identifiers to their current network locations or addresses. Provides location transparency for dynamic agent environments.


draft_name: draft-liu-dmsc-gw-requirements
title: Task-based Agent Searching
idea_type: mechanism
extracted_at: 2026-02-28T10:52:04.869184+00:00
description:
Discovery mechanism that locates agents based on their capabilities or task types rather than identities. Supports dynamic collaboration by finding suitable agents for specific functions.


draft_name: draft-liu-dmsc-gw-requirements
title: Agent Communication Access Control
idea_type: mechanism
extracted_at: 2026-02-28T10:52:04.869184+00:00
description:
Gateway-enforced security mechanism controlling which agents can communicate with each other. Provides centralized security policy enforcement for multi-agent interactions.


draft_name: draft-liu-dmsc-gw-requirements
title: DMSC Gateway Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:52:04.869184+00:00
description:
Specialized gateway entity designed for Dynamic Multi-agents Secured Collaboration environments. Addresses gaps in traditional hardware/software gateways for agent-based systems.


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
title: LLM Inference Service Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:52:11.423205+00:00
description:
Unified architecture framework for deploying large language model inference services at scale. Addresses extreme computing and communication demands during inference operations.


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
title: Multi-Framework Inference Integration
idea_type: pattern
extracted_at: 2026-02-28T10:52:11.423205+00:00
description:
Integration approach for diverse inference service architectures including vLLM, SGLang, and Mooncake frameworks. Enables interoperability between different vendor implementations.


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
title: LLM Network Management Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:52:11.423205+00:00
description:
Specific network management requirements imposed by large-scale LLM inference deployments. Defines constraints and capabilities needed for effective LLM service delivery.


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
title: Inference Service Core Design Principles
idea_type: pattern
extracted_at: 2026-02-28T10:52:11.423205+00:00
description:
Standardized design principles extracted from mainstream inference frameworks. Provides foundation for consistent LLM inference implementation approaches.


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
title: Large-Scale User Inference Serving
idea_type: mechanism
extracted_at: 2026-02-28T10:52:11.423205+00:00
description:
Service deployment mechanism optimized for serving LLM inference to large user populations. Addresses scalability challenges in multi-user inference scenarios.


draft_name: draft-liu-oauth-a2a-profile
title: A2A Call Chain Context Embedding
idea_type: mechanism
extracted_at: 2026-02-28T10:52:18.678814+00:00
description:
Mechanism to embed Agent-to-Agent call chain context within OAuth Transaction Tokens to maintain execution flow across distributed agent workloads. Enables tracking of agent communication paths in trusted domains.


draft_name: draft-liu-oauth-a2a-profile
title: Agent Identity Preservation
idea_type: pattern
extracted_at: 2026-02-28T10:52:18.678814+00:00
description:
Pattern for maintaining agent identity information throughout the transaction token lifecycle in A2A scenarios. Ensures agent provenance is tracked across distributed calls.


draft_name: draft-liu-oauth-a2a-profile
title: A2A Transaction Token Profile
idea_type: profile
extracted_at: 2026-02-28T10:52:18.678814+00:00
description:
Specialized OAuth profile that defines how Transaction Tokens should be structured and used specifically for Agent-to-Agent communication. Extends standard OAuth Transaction Token usage for agent workloads.


draft_name: draft-liu-oauth-a2a-profile
title: Trusted Domain Authorization Context
idea_type: architecture
extracted_at: 2026-02-28T10:52:18.678814+00:00
description:
Architecture pattern for maintaining authorization context across agent communications within trusted domain boundaries. Enables seamless authorization propagation between agents.


draft_name: draft-liu-oauth-a2a-profile
title: A2A Transaction Token Claims Structure
idea_type: extension
extracted_at: 2026-02-28T10:52:18.678814+00:00
description:
Specific claim definitions and structure requirements for Transaction Tokens used in Agent-to-Agent scenarios. Defines what contextual information must be included for proper A2A operation.


draft_name: draft-liu-rtgwg-agent-gateway-requirements
title: Agent Gateway Entity
idea_type: architecture
extracted_at: 2026-02-28T10:52:25.553737+00:00
description:
A new type of network entity specifically designed to facilitate Agent-to-Agent communications, distinct from traditional hardware/software gateways. It serves as an intermediary to improve scalability, communication efficiency, and security in agent-based systems.


draft_name: draft-liu-rtgwg-agent-gateway-requirements
title: Delegated Agent Discovery
idea_type: mechanism
extracted_at: 2026-02-28T10:52:25.553737+00:00
description:
A mechanism where the Agent Gateway performs agent discovery operations on behalf of agents in the network. This allows agents to locate and identify other agents through the gateway rather than performing direct discovery.


draft_name: draft-liu-rtgwg-agent-gateway-requirements
title: Agent-to-Agent Communication Optimization
idea_type: requirement
extracted_at: 2026-02-28T10:52:25.553737+00:00
description:
Requirements for optimizing communication patterns between software agents through gateway intermediation. The gateway provides enhanced scalability and efficiency compared to direct agent-to-agent communication.


draft_name: draft-liu-rtgwg-agent-gateway-requirements
title: Gateway-Mediated Security Model
idea_type: architecture
extracted_at: 2026-02-28T10:52:25.553737+00:00
description:
A security architecture where the Agent Gateway provides security services for agent communications. This centralizes security functions and policies for agent interactions across network domains.


draft_name: draft-liu-rtgwg-llmsync-multicast
title: LLM Model Parameter Synchronization
idea_type: mechanism
extracted_at: 2026-02-28T10:52:31.800014+00:00
description:
Synchronization of large language model parameters across multiple inference nodes using multicast delivery. This addresses the challenge of efficiently distributing updated model weights to numerous deployment instances.


draft_name: draft-liu-rtgwg-llmsync-multicast
title: Multicast-based Model Distribution
idea_type: pattern
extracted_at: 2026-02-28T10:52:31.800014+00:00
description:
Application of IP multicast technologies for distributing LLM model updates and synchronized parameters to cloud inference services. This leverages existing multicast protocols for AI workload distribution.


draft_name: draft-liu-rtgwg-llmsync-multicast
title: LLM Inference Service Synchronization Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:52:31.800014+00:00
description:
Technical requirements for maintaining consistency across distributed LLM inference deployments. This includes timing constraints and data consistency needs for synchronized model serving.


draft_name: draft-liu-rtgwg-llmsync-multicast
title: Cloud-based LLM Multicast Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:52:31.800014+00:00
description:
Network architecture for supporting multicast delivery of LLM synchronization data in cloud environments. This addresses the infrastructure needs for scalable AI model distribution.


draft_name: draft-liu-saag-zt-problem-statement
title: Never Trust Always Verify Principle
idea_type: principle
extracted_at: 2026-02-28T10:52:37.332659+00:00
description:
Core zero trust principle that treats every single access request as untrusted and requires verification regardless of source location or previous authentication state.


draft_name: draft-liu-saag-zt-problem-statement
title: Multi-vendor Zero Trust Interoperability Framework
idea_type: architecture
extracted_at: 2026-02-28T10:52:37.332659+00:00
description:
Open, interoperable framework and protocol specifications needed to enable zero trust implementations across different vendors and platforms.


draft_name: draft-liu-saag-zt-problem-statement
title: Zero Trust Protocol Standardization Scope
idea_type: requirement
extracted_at: 2026-02-28T10:52:37.332659+00:00
description:
Definition of which zero trust aspects are suitable for IETF protocol standardization versus those better addressed by other standardization bodies.


draft_name: draft-liu-saag-zt-problem-statement
title: Castle-and-Moat Paradigm Replacement
idea_type: architecture
extracted_at: 2026-02-28T10:52:37.332659+00:00
description:
Transition from traditional perimeter-based security model to zero trust architecture for cloud services, remote workforces, and intelligent agents.


draft_name: draft-liu-saag-zt-problem-statement
title: Zero Trust Access Request Verification
idea_type: mechanism
extracted_at: 2026-02-28T10:52:37.332659+00:00
description:
Technical mechanism requiring verification for every access request regardless of user location, device, or network context.


draft_name: draft-luan-rtgwg-sdaf
title: Symmetry-Driven Asynchronous Forwarding (SDAF)
idea_type: mechanism
extracted_at: 2026-02-28T10:52:45.115964+00:00
description:
A forwarding mechanism that leverages the intrinsic symmetry of toroidal topologies in LEO satellite constellations to enable autonomous reverse flow processing based solely on local link-state information. Operates without requiring control-plane convergence, protocol extensions, or packet header modifications.


draft_name: draft-luan-rtgwg-sdaf
title: Toroidal Topology Symmetry Exploitation
idea_type: pattern
extracted_at: 2026-02-28T10:52:45.115964+00:00
description:
Utilizes the geometric symmetry properties of LEO satellite constellation topologies formed by multiple circular orbital planes connected by inter-satellite links. Enables predictable routing behavior during failures by exploiting the regular structure of the toroidal network.


draft_name: draft-luan-rtgwg-sdaf
title: Local Link-State Triggered Reverse Flows
idea_type: mechanism
extracted_at: 2026-02-28T10:52:45.115964+00:00
description:
Automatically triggers and processes reverse packet flows based on local link state changes without waiting for global network convergence. Achieves microsecond-scale response times by avoiding control plane synchronization delays.


draft_name: draft-luan-rtgwg-sdaf
title: Control-Plane Independent Fast Reroute
idea_type: mechanism
extracted_at: 2026-02-28T10:52:45.115964+00:00
description:
Implements fast reroute functionality that operates independently of IGP control plane convergence to avoid routing black holes and micro-loops. Maintains compatibility with existing protocols like OSPFv3, IS-IS, and MPLS while providing immediate forwarding decisions.


draft_name: draft-luan-rtgwg-sdaf
title: Resource-Constrained Satellite Router Optimization
idea_type: requirement
extracted_at: 2026-02-28T10:52:45.115964+00:00
description:
Designed specifically for the computational and memory limitations of on-board satellite systems while maintaining high performance. Minimizes processing overhead through local decision making rather than global state synchronization.


draft_name: draft-mallick-muacp
title: Fixed 64-bit Message Header
idea_type: mechanism
extracted_at: 2026-02-28T10:52:52.385773+00:00
description:
An 8-byte fixed header structure providing deterministic memory bounds for resource-constrained devices. Includes version, message type, flags, agent ID, and length fields.


draft_name: draft-mallick-muacp
title: Four Core Message Types
idea_type: protocol
extracted_at: 2026-02-28T10:52:52.385773+00:00
description:
Defines REQUEST, RESPONSE, NOTIFY, and ACK message types optimized for finite-state coordination patterns in autonomous agents. Each type has specific semantics for agent communication workflows.


draft_name: draft-mallick-muacp
title: Bounded Memory Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:52:52.385773+00:00
description:
Enforces strict memory limits with 8-byte header, up to 1024-byte TLV region, and up to 65535-byte payload. Provides deterministic resource consumption guarantees for Class 1 and Class 2 IoT devices.


draft_name: draft-mallick-muacp
title: TLV-based Extensibility
idea_type: mechanism
extracted_at: 2026-02-28T10:52:52.385773+00:00
description:
Uses Type-Length-Value encoding within a bounded 1024-byte region for protocol extensions. Allows flexible metadata and options while maintaining parsing predictability.


draft_name: draft-mallick-muacp
title: Mandatory OSCORE Security Binding
idea_type: requirement
extracted_at: 2026-02-28T10:52:52.385773+00:00
description:
Requires OSCORE integration for all message exchanges in adversarial environments. Provides authenticated encryption while maintaining the protocol's resource efficiency constraints.


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
title: AI Agent Cross-Device Communication Framework
idea_type: framework
extracted_at: 2026-02-28T10:52:59.757738+00:00
description:
Framework for enabling AI agents deployed on different network devices to collaborate on complex tasks like network measurement and troubleshooting. Defines the architectural foundation for inter-agent communication across network boundaries.


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
title: Protocol Gap Analysis for AI Agent Communication
idea_type: mechanism
extracted_at: 2026-02-28T10:52:59.757738+00:00
description:
Systematic evaluation of existing networking protocols and AI agent protocols to identify limitations for cross-device AI agent interaction. Assesses suitability of classical networking protocols versus AI-specific communication methods.


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
title: Multi-Agent Network Collaboration Pattern
idea_type: pattern
extracted_at: 2026-02-28T10:52:59.757738+00:00
description:
Communication pattern enabling distributed AI agents on network devices to coordinate and execute collaborative tasks. Addresses the specific requirements for agent-to-agent communication in network infrastructure contexts.


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
title: Network Device AI Agent Deployment Model
idea_type: architecture
extracted_at: 2026-02-28T10:52:59.757738+00:00
description:
Architecture for deploying AI agents directly on network infrastructure devices to enable distributed intelligence. Supports local processing while maintaining inter-device collaboration capabilities.


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
title: Cross-Device Agent Communication Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:52:59.757738+00:00
description:
Technical requirements for enabling reliable communication between AI agents distributed across different network devices. Addresses unique challenges of agent coordination in network infrastructure environments.


draft_name: draft-mao-rtgwg-apn-framework-for-ioa
title: Internet of Agents (IoA)
idea_type: architecture
extracted_at: 2026-02-28T10:53:06.311721+00:00
description:
A network architecture where AI agents from different manufacturers and cloud platforms communicate and collaborate through the Internet. Enables distributed AI agent ecosystems requiring inter-agent coordination across network boundaries.


draft_name: draft-mao-rtgwg-apn-framework-for-ioa
title: APN Framework for IoA
idea_type: framework
extracted_at: 2026-02-28T10:53:06.311721+00:00
description:
Application of Application-aware Packet Network (APN) framework to provide fine-grained network services for AI agent interactions. Maps different AI agent task requirements to corresponding network service differentiation.


draft_name: draft-mao-rtgwg-apn-framework-for-ioa
title: Agent Task-to-Network Mapping
idea_type: mechanism
extracted_at: 2026-02-28T10:53:06.311721+00:00
description:
A mechanism to translate varying AI agent interaction requirements into specific network service demands. Enables network differentiation based on agent collaboration patterns and task characteristics.


draft_name: draft-mao-rtgwg-apn-framework-for-ioa
title: Fine-Granular Network Services for Agents
idea_type: pattern
extracted_at: 2026-02-28T10:53:06.311721+00:00
description:
Network service provisioning approach that provides customized network treatment based on specific AI agent interaction patterns. Supports diverse quality of service requirements for different types of agent communications.


draft_name: draft-melnikov-sasl2
title: Replaceable SASL Mechanisms
idea_type: architecture
extracted_at: 2026-02-28T10:53:12.352968+00:00
description:
A structured interface between protocols and authentication mechanisms that allows new protocols to reuse existing mechanisms and old protocols to use new mechanisms. This creates a pluggable architecture where authentication methods can be swapped without changing the underlying protocol.


draft_name: draft-melnikov-sasl2
title: Data Security Layer Protocol
idea_type: protocol
extracted_at: 2026-02-28T10:53:12.352968+00:00
description:
A protocol for carrying and securing subsequent protocol exchanges within a data security layer after authentication completes. This provides ongoing protection for data transmitted over the connection.


draft_name: draft-melnikov-sasl2
title: Extra Authentication Tasks Framework
idea_type: extension
extracted_at: 2026-02-28T10:53:12.352968+00:00
description:
A mechanism allowing servers to request fulfillment of additional authentication-related tasks such as two-factor authentication and password changes. This extends basic authentication to support complex authentication workflows.


draft_name: draft-melnikov-sasl2
title: Protocol-Mechanism Interface Structure
idea_type: pattern
extracted_at: 2026-02-28T10:53:12.352968+00:00
description:
A standardized way to structure how SASL mechanisms interact with connection-oriented protocols. This defines the specific interface points and data exchange patterns between the protocol layer and authentication mechanisms.


draft_name: draft-men-rtgwg-agent-networking-digibank-scenario
title: Agent Gateway
idea_type: architecture
extracted_at: 2026-02-28T10:53:18.802869+00:00
description:
A core networking component that serves as the central element in agent networking architecture for digital banking scenarios. It facilitates agentic service interconnection in enterprise and broadband networks.


draft_name: draft-men-rtgwg-agent-networking-digibank-scenario
title: Agentic Service Interconnection
idea_type: pattern
extracted_at: 2026-02-28T10:53:18.802869+00:00
description:
A networking pattern where digital banking services evolve from traditional digitalization to agent-based service connections. This represents a shift toward autonomous agent-to-agent communication in financial networks.


draft_name: draft-men-rtgwg-agent-networking-digibank-scenario
title: Agent Networking Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:53:18.802869+00:00
description:
A proposed network architecture specifically designed for enterprise and broadband networks to support agent-based services in digital banking environments. The architecture centers around agent gateways as key infrastructure components.


draft_name: draft-men-rtgwg-agent-networking-digibank-scenario
title: Digital Banking Agent Requirements
idea_type: requirement
extracted_at: 2026-02-28T10:53:18.802869+00:00
description:
Specific networking and functional requirements identified for agents operating in digital banking scenarios. These requirements drive the design of the proposed agent networking solutions.


draft_name: draft-men-rtgwg-agent-networking-in-digibank
title: Agent Gateway
idea_type: architecture
extracted_at: 2026-02-28T10:53:23.924057+00:00
description:
A core networking component that enables interconnection between banking agents and services. It serves as the central element in the proposed agent networking architecture for digital banking scenarios.


draft_name: draft-men-rtgwg-agent-networking-in-digibank
title: Agentic Service Interconnection
idea_type: pattern
extracted_at: 2026-02-28T10:53:23.924057+00:00
description:
A networking pattern where digital banking services evolve from traditional digitalization to agent-based service connections. This represents the trend of banking systems moving toward autonomous agent communications.


draft_name: draft-men-rtgwg-agent-networking-in-digibank
title: Agent Networking Architecture
idea_type: architecture
extracted_at: 2026-02-28T10:53:23.924057+00:00
description:
A proposed system architecture specifically designed for digital banking that facilitates communication and coordination between multiple banking agents. The architecture centers around the agent gateway component.


draft_name: draft-messous-eat-ai
title: AI Model Parameter Integrity Claims
idea_type: mechanism
extracted_at: 2026-02-28T10:53:30.886720+00:00
description:
Standardized EAT claims for attesting the cryptographic integrity and authenticity of AI model parameters. Enables verification that model weights and architecture have not been tampered with.


draft_name: draft-messous-eat-ai
title: Training Data Provenance Claims
idea_type: mechanism
extracted_at: 2026-02-28T10:53:30.886720+00:00
description:
EAT claims that attest to the source, lineage, and characteristics of training datasets used to create AI models. Provides verifiable proof of data origins for compliance and trust.


draft_name: draft-messous-eat-ai
title: Inference-Time Data Access Policy Claims
idea_type: mechanism
extracted_at: 2026-02-28T10:53:30.886720+00:00
description:
Claims that specify and attest to constraints on what data an AI agent can access during inference operations. Enables enforcement of data usage boundaries and privacy controls.


draft_name: draft-messous-eat-ai
title: 5G/6G Network Slice Authorization Extension
idea_type: extension
extracted_at: 2026-02-28T10:53:30.886720+00:00
description:
Optional EAT extensions for authorizing AI agents to specific network slice types in 5G/6G environments. Provides interoperability with ETSI ENI and 3GPP network architectures.


draft_name: draft-messous-eat-ai
title: Cross-Domain AI Agent Attestation Profile
idea_type: protocol
extracted_at: 2026-02-28T10:53:30.886720+00:00
description:
A complete EAT profile specification that enables remote attestation of autonomous AI agents operating across different administrative domains. Standardizes the attestation format and required claims.


draft_name: draft-meta-layer-overview
title: Meta-Layer Coordination Substrate
idea_type: architecture
extracted_at: 2026-02-28T10:53:37.951647+00:00
description:
A programmable layer that operates above content layers to enable presence, annotation, and governance functionality. It integrates with existing web protocols without replacing them.


draft_name: draft-meta-layer-overview
title: Platform-Independent Digital Governance
idea_type: mechanism
extracted_at: 2026-02-28T10:53:37.951647+00:00
description:
A mechanism allowing communities to establish governance rules and coordination that operates independently of underlying platforms. Enables shared digital space management across different web services.


draft_name: draft-meta-layer-overview
title: Cross-Platform Presence System
idea_type: protocol
extracted_at: 2026-02-28T10:53:37.951647+00:00
description:
Infrastructure for individuals and agents to appear and coordinate in shared digital spaces regardless of the underlying platform or service. Provides unified presence across multiple web properties.


draft_name: draft-meta-layer-overview
title: Distributed Annotation Framework
idea_type: mechanism
extracted_at: 2026-02-28T10:53:37.951647+00:00
description:
A system for adding metadata and annotations to web content that exists independently of the content platforms themselves. Allows persistent annotations across platform boundaries.


