# llm_cache

draft_name: draft-sarischo-6gip-aiagent-requirements
prompt_hash: 578701245410dfd6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:06.586187+00:00
response_json:
{"name": "draft-sarischo-6gip-aiagent-requirements", "s": "Defines requirements for AI/ML agents in 6G mobile networks, covering different agent types and their specific needs. Describes implementation approaches including API discovery and DNS-based agent discovery mechanisms.", "n": 3, "nn": "Applies existing AI agent concepts to 6G context with some novel DNS discovery approaches", "m": 2, "mn": "Early stage draft with basic requirements enumeration, lacks detailed technical specifications", "o": 3, "on": "Overlaps with general AI agent frameworks but focuses specifically on 6G domain", "mo": 2, "mon": "Limited momentum, niche 6G focus may restrict broader IETF interest", "r": 3, "rn": "Relevant for telecom industry moving toward 6G, moderate relevance for general networking", "c": ["Agent discovery/reg", "Autonomous netops", "Policy/governance"]}


draft_name: draft-hong-nmrg-agenticai-ps
prompt_hash: 3046f4d104a01596
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:06.609248+00:00
response_json:
{"name": "draft-hong-nmrg-agenticai-ps", "s": "Presents problem statement and motivations for applying Agentic AI to network management. Emphasizes collaborative autonomous agents for fully automated network operations, management and security.", "n": 3, "nn": "Frames existing agentic AI concepts within network management context with collaborative focus", "m": 2, "mn": "Problem statement level document, lacks concrete technical solutions or protocols", "o": 4, "on": "Significant overlap with autonomous network operations and AI agent coordination topics", "mo": 3, "mon": "NMRG venue appropriate, collaborative automation angle has potential interest", "r": 4, "rn": "Highly relevant to network automation trends and operator pain points", "c": ["Autonomous netops", "A2A protocols", "Policy/governance"]}


draft_name: draft-zhao-nmrg-ai-agent-for-dtn
prompt_hash: add5984de05ea190
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:06.620012+00:00
response_json:
{"name": "draft-zhao-nmrg-ai-agent-for-dtn", "s": "Proposes AI agent architecture for Digital Twin Networks, integrating autonomous agents at each DTN component level. Extends traditional DTN architecture for more intelligent and adaptive network management.", "n": 4, "nn": "Novel combination of digital twin technology with AI agents for network management", "m": 2, "mn": "Very brief at 7 pages, appears to be early conceptual stage", "o": 3, "on": "Some overlap with network digital twins and AI agent architectures", "mo": 2, "mon": "Niche combination of technologies may limit broader adoption", "r": 3, "rn": "Relevant for advanced network management but digital twin adoption still emerging", "c": ["Autonomous netops", "Data formats/interop", "Other AI/agent"]}


draft_name: draft-zyyhl-agent-networks-framework
prompt_hash: 99a6272fefb69903
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:06.628889+00:00
response_json:
{"name": "draft-zyyhl-agent-networks-framework", "s": "Defines comprehensive framework for AI agent networks based on Agent Network Protocol (ANP). Provides basic functions needed for AI agent communication within trusted domains.", "n": 4, "nn": "Substantial framework for agent-to-agent networking with dedicated protocol", "m": 3, "mn": "Most detailed at 21 pages with concrete protocol framework, but references incomplete ANP spec", "o": 2, "on": "Relatively unique approach to agent networking protocols", "mo": 3, "mon": "Comprehensive framework could attract interest but depends on ANP protocol development", "r": 4, "rn": "Highly relevant as agent-to-agent communication becomes critical infrastructure need", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "Agent identity/auth"]}


draft_name: draft-srijal-agents-policy
prompt_hash: d53bedb6702a5a12
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:06.638828+00:00
response_json:
{"name": "draft-srijal-agents-policy", "s": "Specifies AGENTS.TXT protocol as strict plaintext policy file for automated clients, bots, and crawlers. Includes hash verification and mandatory restrictive behavior for malformed files.", "n": 3, "nn": "Builds on robots.txt concept with stricter verification and failure handling for AI agents", "m": 3, "mn": "Well-defined protocol specification with clear directives and error handling", "o": 2, "on": "Similar to robots.txt but distinct focus on modern automated agents", "mo": 4, "mon": "Addresses immediate practical need as AI agents proliferate across web services", "r": 5, "rn": "Extremely relevant given current explosion of AI agents and need for access control", "c": ["Policy/governance", "Agent identity/auth", "Data formats/interop"]}


draft_name: draft-liang-agentdns
prompt_hash: 9899844ba070d608
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:26.158978+00:00
response_json:
{"name": "draft-liang-agentdns", "s": "Proposes a DNS-inspired naming and service discovery system for LLM agents to enable autonomous discovery and invocation of third-party services. Addresses interoperability and trust management in agent collaboration ecosystems.", "n": 4, "nn": "Novel application of DNS concepts to agent ecosystems with semantic discovery", "m": 3, "mn": "Well-structured but lacks implementation details and evaluation", "o": 3, "on": "Overlaps with draft-cui-ai-agent-discovery-invocation on agent discovery", "mo": 3, "mon": "Addresses clear need but no evidence of industry adoption yet", "r": 4, "rn": "Highly relevant for emerging agent interoperability challenges", "c": ["Agent discovery/reg", "A2A protocols", "Agent identity/auth"]}


draft_name: draft-scim-agent-extension
prompt_hash: 1641338ce5fca627
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:26.182426+00:00
response_json:
{"name": "draft-scim-agent-extension", "s": "Extends SCIM 2.0 specification to manage agents and agentic applications across domains. Builds on existing identity management infrastructure to reduce protocol proliferation.", "n": 3, "nn": "Practical extension of established standard rather than novel approach", "m": 4, "mn": "Builds on mature SCIM foundation with detailed schema extensions", "o": 2, "on": "Unique approach using identity management for agent management", "mo": 4, "mon": "Leverages existing SCIM ecosystem and addresses practical deployment needs", "r": 4, "rn": "Very relevant for enterprise agent identity and lifecycle management", "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance"]}


draft_name: draft-kotecha-agentic-dispute-protocol
prompt_hash: f2a28fa674e86fd3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:26.193088+00:00
response_json:
{"name": "draft-kotecha-agentic-dispute-protocol", "s": "Defines a protocol for autonomous agents to file and resolve disputes through structured automated processes. Includes evidence submission, cryptographic proofs, and multiple resolution frameworks.", "n": 5, "nn": "Highly novel - first formal protocol for automated agent dispute resolution", "m": 3, "mn": "Comprehensive but complex specification needing real-world validation", "o": 1, "on": "Unique focus on dispute resolution - no overlap with other drafts", "mo": 2, "mon": "Addresses future need but may be premature for current agent capabilities", "r": 3, "rn": "Relevant for advanced agent interactions but not immediate priority", "c": ["A2A protocols", "Policy/governance", "AI safety/alignment"]}


draft_name: draft-cui-ai-agent-discovery-invocation
prompt_hash: 1a7005ed348e1605
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:26.202789+00:00
response_json:
{"name": "draft-cui-ai-agent-discovery-invocation", "s": "Proposes standardized protocol for AI agent discovery and invocation with common metadata format and RESTful interface. Includes intent-based agent selection extension.", "n": 3, "nn": "Standard approach to common problem with useful intent-based extension", "m": 4, "mn": "Well-developed specification with clear interfaces and security considerations", "o": 3, "on": "Overlaps with draft-liang-agentdns on agent discovery functionality", "mo": 4, "mon": "Addresses immediate interoperability needs with practical approach", "r": 5, "rn": "Extremely relevant - core requirement for multi-agent system deployment", "c": ["Agent discovery/reg", "A2A protocols", "Data formats/interop"]}


draft_name: draft-liu-access-collaboration-agent
prompt_hash: 29fdc2e3216c74dd
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:26.218598+00:00
response_json:
{"name": "draft-liu-access-collaboration-agent", "s": "Brief document exploring requirements for AI agent communication protocols in ubiquitous access collaboration scenarios. Very preliminary with minimal detail.", "n": 2, "nn": "Limited novelty - discusses general requirements without specific solutions", "m": 1, "mn": "Very early stage - only 6 pages with minimal technical content", "o": 4, "on": "General requirements overlap with other agent protocol discussions", "mo": 1, "mon": "No clear momentum - appears to be initial exploration only", "r": 2, "rn": "Potentially relevant but too underdeveloped to assess properly", "c": ["A2A protocols", "Other AI/agent"]}


draft_name: draft-abbey-scim-agent-extension
prompt_hash: 7aca3dad4a00c548
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:44.876148+00:00
response_json:
{"name": "draft-abbey-scim-agent-extension", "s": "Extends SCIM 2.0 protocol to manage AI agents and agentic applications across domains. Adds new schemas and resource types for agent identity management using existing SCIM infrastructure.", "n": 4, "nn": "First to systematically extend SCIM for agent identity management", "m": 3, "mn": "Builds on mature SCIM foundation but agent-specific extensions are early", "o": 1, "on": "Unique approach using SCIM for agent identity management", "mo": 3, "mon": "Leverages established SCIM ecosystem but agent management is emerging", "r": 4, "rn": "Addresses critical need for agent identity management as agentic systems proliferate", "c": ["Agent identity/auth", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-zhao-nmop-network-management-agent
prompt_hash: 65240ea1686487f7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:44.898694+00:00
response_json:
{"name": "draft-zhao-nmop-network-management-agent", "s": "Defines AI-driven Network Management Agent concept for Level 4 autonomous networks. Specifies integration with existing SDN controllers for intent-based reasoning and autonomous operations.", "n": 4, "nn": "Novel conceptual framework bridging AI agents with network autonomy levels", "m": 2, "mn": "Early stage architectural proposal with limited implementation details", "o": 3, "on": "Some overlap with existing autonomous network and SDN work", "mo": 4, "mon": "Strong industry push toward network automation and AI integration", "r": 5, "rn": "Highly relevant as networks move toward autonomous operations", "c": ["Autonomous netops", "A2A protocols", "Policy/governance"]}


draft_name: draft-yao-agent-auth-considerations
prompt_hash: 89d2c4eb2712be9c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:44.911228+00:00
response_json:
{"name": "draft-yao-agent-auth-considerations", "s": "Extends OAuth model for AI agent authentication and authorization in Agent Communication Networks. Proposes new workflows addressing unique requirements of agent-to-agent authentication.", "n": 3, "nn": "Reasonable extension of OAuth to agent domain with some novel considerations", "m": 2, "mn": "Early conceptual work building on OAuth but lacks detailed protocol specification", "o": 2, "on": "Some conceptual overlap with general OAuth extensions but agent-specific", "mo": 3, "mon": "OAuth is well-established but agent auth is still developing", "r": 4, "rn": "Critical for secure agent ecosystems as they become more prevalent", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]}


draft_name: draft-zhao-ccamp-actn-optical-network-agent
prompt_hash: d50008281e390638
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:44.922308+00:00
response_json:
{"name": "draft-zhao-ccamp-actn-optical-network-agent", "s": "Integrates Network Management Agents into ACTN-based optical networks for autonomous operations. Extends ACTN architecture with AI capabilities for optical network management.", "n": 3, "nn": "Applies NMA concept to specific optical network domain with ACTN", "m": 2, "mn": "Early architectural proposal with limited technical depth", "o": 4, "on": "Builds heavily on companion NMA draft and existing ACTN work", "mo": 3, "mon": "Optical networks seeking automation but AI integration still emerging", "r": 3, "rn": "Relevant for optical network operators but narrow domain focus", "c": ["Autonomous netops", "Other AI/agent"]}


draft_name: draft-mzsg-rtgwg-agent-cross-device-comm-framework
prompt_hash: 85c9acf4ea85a5e3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:13:44.933983+00:00
response_json:
{"name": "draft-mzsg-rtgwg-agent-cross-device-comm-framework", "s": "Proposes communication framework for AI agents deployed across different network devices. Focuses on collaboration requirements for tasks like network measurement and troubleshooting.", "n": 3, "nn": "Addresses practical need for agent coordination in network devices", "m": 1, "mn": "Very early stage with minimal technical detail or protocol specification", "o": 3, "on": "Some overlap with general agent communication frameworks", "mo": 2, "mon": "Network device AI deployment still in early phases", "r": 3, "rn": "Relevant for network operations but limited scope and early development", "c": ["A2A protocols", "Autonomous netops", "Data formats/interop"]}


draft_name: draft-zl-agents-networking-architecture
prompt_hash: a474512265675bc1
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:03.408368+00:00
response_json:
{"name": "draft-zl-agents-networking-architecture", "s": "Defines core components and interactions for agent networking architecture in enterprise and broadband environments. Provides foundational framework for agent-based networking systems.", "n": 3, "nn": "Basic architectural framework, but limited novelty in core concepts", "m": 2, "mn": "Early draft with brief content, lacks detailed specifications", "o": 4, "on": "Overlaps significantly with other agent networking architecture drafts", "mo": 2, "mon": "Limited momentum indicated by brief content and basic scope", "r": 3, "rn": "Relevant to growing agent networking field but lacks depth", "c": ["Autonomous netops", "A2A protocols", "Data formats/interop"]}


draft_name: draft-wmz-nmrg-agent-ndt-arch
prompt_hash: 59716bae282d302f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:03.429356+00:00
response_json:
{"name": "draft-wmz-nmrg-agent-ndt-arch", "s": "Comprehensive architecture combining Network Digital Twin with Agentic AI for intent-based network operations. Provides detailed cookbook approach using existing technologies enhanced with new AI capabilities.", "n": 4, "nn": "Novel integration of NDT and Agentic AI for network operations", "m": 4, "mn": "Substantial 37-page document with detailed architectural components", "o": 2, "on": "Unique focus on digital twin integration with agent architecture", "mo": 4, "mon": "Strong momentum with comprehensive content and clear use cases", "r": 5, "rn": "highly relevant to current industry needs for AI-driven network automation", "c": ["Autonomous netops", "Model serving/inference", "Policy/governance", "Other AI/agent"]}


draft_name: draft-chuyi-nmrg-ai-agent-network
prompt_hash: ea1322ae62b409ec
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:03.443851+00:00
response_json:
{"name": "draft-chuyi-nmrg-ai-agent-network", "s": "Focuses on large language model-based agents for network operations and maintenance. Addresses practical challenges like system isolation and fragmented data in network operations.", "n": 3, "nn": "Practical focus on LLM applications but incremental novelty", "m": 3, "mn": "Moderate detail with scenario identification and impact analysis", "o": 3, "on": "Moderate overlap with other network agent operation drafts", "mo": 3, "mon": "Good momentum with practical focus and standardization exploration", "r": 4, "rn": "High relevance to current LLM and network automation trends", "c": ["Autonomous netops", "ML traffic mgmt", "Model serving/inference", "Data formats/interop"]}


draft_name: draft-zl-agents-networking-scenarios
prompt_hash: dd69f1337a3d6c2d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:03.454127+00:00
response_json:
{"name": "draft-zl-agents-networking-scenarios", "s": "Describes specific agent networking scenarios for enterprise and home broadband networks. Focuses on practical use cases distinct from 6G and general Internet scenarios.", "n": 2, "nn": "Limited novelty, mainly scenario descriptions based on assumptions", "m": 2, "mn": "Brief 8-page document with basic scenario coverage", "o": 3, "on": "Scenarios overlap with other agent networking use case discussions", "mo": 2, "mon": "Low momentum with brief content and assumption-based scenarios", "r": 3, "rn": "Moderately relevant for understanding practical deployment contexts", "c": ["Autonomous netops", "Human-agent interaction", "Other AI/agent"]}


draft_name: draft-stephan-ai-agent-6g
prompt_hash: 292b38d755e47899
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:03.471717+00:00
response_json:
{"name": "draft-stephan-ai-agent-6g", "s": "Examines AI agent communication protocols specifically for 6G systems based on 3GPP requirements. Extrapolates protocol requirements from established 3GPP use cases.", "n": 3, "nn": "Builds on existing 3GPP work with moderate protocol innovation", "m": 3, "mn": "Reasonable detail with clear 3GPP foundation and protocol focus", "o": 2, "on": "Unique 6G focus with limited overlap to other drafts", "mo": 3, "mon": "Moderate momentum with established 3GPP backing", "r": 4, "rn": "High relevance to emerging 6G standards and agent protocols", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "Other AI/agent"]}


draft_name: draft-ni-wimse-ai-agent-identity
prompt_hash: 7519289e7c711f0d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:18.768155+00:00
response_json:
{"name": "draft-ni-wimse-ai-agent-identity", "s": "Applies WIMSE (Workload Identity in Multi System Environments) framework to AI agents for identity and credential management. Focuses on establishing independent identities for AI agents operating across systems.", "n": 3, "nn": "Moderate novelty in applying existing WIMSE to AI agents", "m": 2, "mn": "Early stage, limited technical detail in abstract", "o": 3, "on": "Some overlap with other agent identity drafts", "mo": 3, "mon": "Part of emerging AI agent standardization work", "r": 4, "rn": "Highly relevant as agent identity is foundational", "c": ["Agent identity/auth"]}


draft_name: draft-mao-rtgwg-agent-comm-protocol-gap-analysis
prompt_hash: 3c2ade2935a9b4ee
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:18.789247+00:00
response_json:
{"name": "draft-mao-rtgwg-agent-comm-protocol-gap-analysis", "s": "Analyzes gaps in existing networking and AI protocols for cross-device communication between AI agents on network devices. Evaluates classical networking protocols and popular AI agent protocols for suitability.", "n": 4, "nn": "Novel gap analysis approach for agent communication", "m": 3, "mn": "Good analytical foundation, references framework draft", "o": 2, "on": "Unique focus on protocol gap analysis", "mo": 3, "mon": "Part of broader cross-device communication work", "r": 4, "rn": "Important for understanding protocol requirements", "c": ["A2A protocols", "Autonomous netops"]}


draft_name: draft-zheng-agent-identity-management
prompt_hash: db5b6146ed81384a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:18.798641+00:00
response_json:
{"name": "draft-zheng-agent-identity-management", "s": "Defines comprehensive agent identity management for Internet of Agents systems. Covers agent registration, identifier structure, and identity management functions through agent gateways.", "n": 4, "nn": "Comprehensive identity management framework", "m": 3, "mn": "Well-structured with detailed requirements", "o": 4, "on": "Significant overlap with other identity drafts", "mo": 3, "mon": "Active development in agent identity space", "r": 5, "rn": "Critical foundational work for agent ecosystems", "c": ["Agent identity/auth", "Agent discovery/reg"]}


draft_name: draft-ni-a2a-ai-agent-security-requirements
prompt_hash: 9dd7f5ff2eb67bca
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:18.807128+00:00
response_json:
{"name": "draft-ni-a2a-ai-agent-security-requirements", "s": "Establishes security requirements for AI agents across their operational lifecycle. Covers provisioning, registration, cross-domain interconnection, and access control security aspects.", "n": 3, "nn": "Systematic security requirements approach", "m": 3, "mn": "Good coverage of security lifecycle stages", "o": 3, "on": "Some overlap with identity and auth drafts", "mo": 4, "mon": "Strong interest in AI agent security", "r": 5, "rn": "Essential for secure agent deployment", "c": ["AI safety/alignment", "Agent identity/auth"]}


draft_name: draft-yuan-rtgwg-traffic-agent-usecase
prompt_hash: cc243fe7d989bc16
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:18.818758+00:00
response_json:
{"name": "draft-yuan-rtgwg-traffic-agent-usecase", "s": "Presents use cases for AI agents optimizing network traffic through dynamic resource adjustment. Details applications in tunnel adjustment, traffic steering, and network slice management.", "n": 3, "nn": "Specific application of AI to traffic optimization", "m": 4, "mn": "Well-detailed use cases with clear scenarios", "o": 2, "on": "Unique focus on traffic optimization use cases", "mo": 4, "mon": "Strong industry interest in AI network optimization", "r": 4, "rn": "Valuable for understanding practical applications", "c": ["ML traffic mgmt", "Autonomous netops"]}


draft_name: draft-yuan-rtgwg-security-agent-usecase
prompt_hash: 54a2d4f3a92635e8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:40.992220+00:00
response_json:
{"name": "draft-yuan-rtgwg-security-agent-usecase", "s": "Proposes AI Network Security Agents for routers to provide intelligent, adaptive security capabilities beyond traditional static ACLs and signature-based detection. Outlines four key use cases including dynamic defense, ACL optimization, configuration security, and collaborative defense.", "n": 4, "nn": "Novel application of AI agents specifically to network security with concrete use cases, though AI in security is not new", "m": 2, "mn": "Early stage with high-level concepts and scenarios but lacks technical implementation details", "o": 2, "on": "Some overlap with general AI agent networking concepts but security focus is distinctive", "mo": 3, "mon": "Security applications of AI agents have industry interest but this is an early contribution", "r": 4, "rn": "Highly relevant as network security increasingly needs intelligent automation and adaptive responses", "c": ["Autonomous netops", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-men-rtgwg-agent-networking-digibank-scenario
prompt_hash: c9133fcf4d3312b9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:41.012519+00:00
response_json:
{"name": "draft-men-rtgwg-agent-networking-digibank-scenario", "s": "Describes digital banking scenarios evolving toward agentic service interconnection and proposes an agent networking architecture centered on agent gateways. Focuses on enterprise and broadband network contexts.", "n": 3, "nn": "Specific application to digital banking is somewhat novel but agent gateway concept is not unique", "m": 2, "mn": "Scenario-focused with limited technical depth on implementation", "o": 4, "on": "Significant overlap with the other digital banking draft and agent gateway concepts", "mo": 2, "mon": "Banking-specific use cases may have limited broader appeal in IETF context", "r": 3, "rn": "Relevant to understanding agent networking applications but narrow domain focus", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-tong-network-agent-use-cases-in-6g
prompt_hash: 16641100fd1bb700
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:41.022743+00:00
response_json:
{"name": "draft-tong-network-agent-use-cases-in-6g", "s": "Introduces network AI agent use cases in 6G focusing on connectivity services and third-party applications, drawing from 3GPP scenarios. Discusses integration requirements within 6G framework.", "n": 3, "nn": "6G-specific agent use cases provide some novelty but builds heavily on existing 3GPP work", "m": 2, "mn": "Use case focused with limited technical specification details", "o": 3, "on": "Moderate overlap with general AI agent networking but 6G focus provides differentiation", "mo": 4, "mon": "6G and AI agents are both high-interest areas with strong industry momentum", "r": 4, "rn": "Very relevant as 6G networks will likely require extensive AI agent capabilities", "c": ["Autonomous netops", "ML traffic mgmt", "Agent discovery/reg", "Model serving/inference"]}


draft_name: draft-men-rtgwg-agent-networking-in-digibank
prompt_hash: 1b90b44d6fb8175f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:41.032629+00:00
response_json:
{"name": "draft-men-rtgwg-agent-networking-in-digibank", "s": "Describes digital banking digitalization trends toward agentic services and proposes agent networking architecture with agent gateway as core component. Very similar to the other digital banking draft.", "n": 2, "nn": "Limited novelty, appears to duplicate content from related draft", "m": 2, "mn": "Early stage conceptual work with scenario focus", "o": 5, "on": "Heavy overlap with draft-men-rtgwg-agent-networking-digibank-scenario", "mo": 1, "mon": "Duplicate content reduces momentum and may indicate coordination issues", "r": 2, "rn": "Limited relevance due to narrow focus and apparent duplication", "c": ["A2A protocols", "Agent discovery/reg"]}


draft_name: draft-liu-rtgwg-agent-gateway-requirements
prompt_hash: 54a2d293837158cc
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:41.042281+00:00
response_json:
{"name": "draft-liu-rtgwg-agent-gateway-requirements", "s": "Discusses requirements for Agent Gateways in agent-to-agent communications to improve scalability, efficiency and security. Identifies gaps in current gateway solutions that necessitate new Agent Gateway entities.", "n": 3, "nn": "Requirements analysis for agent gateways shows some novelty in systematic approach", "m": 3, "mn": "More mature requirements analysis compared to other drafts, though still early stage", "o": 3, "on": "Overlaps with agent gateway concepts in banking drafts but more technical focus", "mo": 3, "mon": "Requirements documents often gain traction if they address real needs", "r": 4, "rn": "Highly relevant as agent gateway requirements are fundamental to agent networking", "c": ["A2A protocols", "Agent identity/auth", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-zhang-rtgwg-ai-agents-measurement
prompt_hash: 50905578502f7d14
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:57.273201+00:00
response_json:
{"name": "draft-zhang-rtgwg-ai-agents-measurement", "s": "Defines use cases and requirements for communication protocols enabling measurement agents on network devices. Focuses on network monitoring and telemetry collection through AI agents.", "n": 3, "nn": "Moderate novelty in applying agent paradigm to network measurement", "m": 2, "mn": "Early stage draft with basic requirements definition", "o": 2, "on": "Some overlap with general network telemetry protocols", "mo": 2, "mon": "Limited momentum, appears to be initial exploration", "r": 3, "rn": "Relevant for network operations but narrow scope", "c": ["Autonomous netops", "A2A protocols", "Data formats/interop"]}


draft_name: draft-zlgsgl-rtgwg-agents-networking-framework
prompt_hash: 956bc5d22cf2463c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:57.294916+00:00
response_json:
{"name": "draft-zlgsgl-rtgwg-agents-networking-framework", "s": "Introduces a comprehensive agents networking framework for enterprise and broadband environments. Defines core components and interactions for agent-based networking systems.", "n": 4, "nn": "Novel framework approach for agent networking architecture", "m": 3, "mn": "More developed with defined components and interactions", "o": 2, "on": "Some conceptual overlap with SDN frameworks", "mo": 3, "mon": "Good momentum with detailed framework definition", "r": 4, "rn": "Highly relevant for enterprise networking evolution", "c": ["Autonomous netops", "A2A protocols", "Agent discovery/reg"]}


draft_name: draft-oauth-transaction-tokens-for-agents
prompt_hash: b69fd9738857ce3b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:57.305905+00:00
response_json:
{"name": "draft-oauth-transaction-tokens-for-agents", "s": "Extends OAuth Transaction Tokens framework to support agent context propagation with actor and principal fields. Enables granular access control for agent-based workloads.", "n": 4, "nn": "Novel extension addressing agent-specific authorization needs", "m": 4, "mn": "Well-developed with clear technical specifications", "o": 3, "on": "Builds on existing OAuth framework but adds agent-specific elements", "mo": 4, "mon": "Strong momentum with concrete technical approach", "r": 5, "rn": "Highly relevant for agent security and authorization", "c": ["Agent identity/auth", "Policy/governance", "A2A protocols"]}


draft_name: draft-steele-agent-considerations
prompt_hash: 9ce93b771bc2c151
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:57.316047+00:00
response_json:
{"name": "draft-steele-agent-considerations", "s": "Defines guidelines for IETF specifications to support AI agent consumption and code generation. Introduces Agent Consideration sections with agentcards and implementation guidance.", "n": 5, "nn": "Highly novel meta-approach to specification design for AI agents", "m": 3, "mn": "Comprehensive framework but still developing implementation details", "o": 1, "on": "Unique approach to specification methodology", "mo": 3, "mon": "Moderate momentum, addressing emerging need", "r": 4, "rn": "Very relevant for future IETF specification development", "c": ["Data formats/interop", "Policy/governance", "Human-agent interaction"]}


draft_name: draft-song-oauth-ai-agent-collaborate-authz
prompt_hash: ca6be63187d0388d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:14:57.327036+00:00
response_json:
{"name": "draft-song-oauth-ai-agent-collaborate-authz", "s": "Proposes OAuth 2.0 extension for multi-AI agent collaboration with applier-on-behalf-of authorization. Simplifies authorization for coordinated agent workflows.", "n": 4, "nn": "Novel approach to multi-agent authorization coordination", "m": 3, "mn": "Clear technical approach with specific OAuth extension", "o": 3, "on": "Some overlap with general OAuth delegation patterns", "mo": 3, "mon": "Good momentum addressing practical multi-agent needs", "r": 4, "rn": "Highly relevant for multi-agent system deployment", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]}


draft_name: draft-pang-agents-networking-scenarios
prompt_hash: 61ef5bfb738bf616
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:19.390779+00:00
response_json:
{"name": "draft-pang-agents-networking-scenarios", "s": "Describes networking scenarios for agents in enterprise and broadband networks, distinguishing them from mobile and Internet scenarios. Based on reasonable assumptions as agentic services are still emerging.", "n": 2, "nn": "Basic scenario enumeration without novel technical contributions", "m": 2, "mn": "Early stage draft with assumptions rather than concrete solutions", "o": 3, "on": "Overlaps with general agent networking concepts but focuses on specific environments", "mo": 2, "mon": "Limited technical depth may constrain adoption momentum", "r": 3, "rn": "Relevant for understanding agent deployment contexts but lacks implementation guidance", "c": ["Autonomous netops", "Other AI/agent"]}


draft_name: draft-han-rtgwg-agent-gateway-intercomm-framework
prompt_hash: 4f27600dc85386f4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:19.411244+00:00
response_json:
{"name": "draft-han-rtgwg-agent-gateway-intercomm-framework", "s": "Defines framework for intercommunication between Agent Gateways in Agent Internet ecosystem. Addresses data synchronization, protocol compatibility, and security for cross-domain agent collaboration.", "n": 4, "nn": "Novel hierarchical framework for agent gateway intercommunication", "m": 3, "mn": "Well-structured framework with clear components but implementation details may need refinement", "o": 2, "on": "Specialized focus on gateway interoperability reduces overlap", "mo": 3, "mon": "Technical depth and clear problem focus suggest moderate momentum potential", "r": 4, "rn": "Highly relevant for scalable agent infrastructure and cross-domain collaboration", "c": ["A2A protocols", "Agent discovery/reg", "Autonomous netops"]}


draft_name: draft-dhir-http-agent-profile
prompt_hash: 52afdc73b1401e24
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:19.421350+00:00
response_json:
{"name": "draft-dhir-http-agent-profile", "s": "Defines HTTP Agent Profile for authenticating agent traffic, separating human from agent traffic, and enabling micropayments for content access. Addresses economic misalignment between content providers and AI systems.", "n": 4, "nn": "Novel integration of authentication, traffic separation, and micropayments for agent HTTP traffic", "m": 4, "mn": "Mature approach reusing existing HTTP features with clear deployment path", "o": 2, "on": "Unique combination of authentication and monetization for agent traffic", "mo": 4, "mon": "Addresses pressing real-world problems with practical deployment strategy", "r": 5, "rn": "Extremely relevant to current challenges with AI crawlers and web monetization", "c": ["Agent identity/auth", "ML traffic mgmt", "Policy/governance", "Human-agent interaction"]}


draft_name: draft-liu-agent-operation-authorization
prompt_hash: 6069661cee97bfd3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:19.431995+00:00
response_json:
{"name": "draft-liu-agent-operation-authorization", "s": "Specifies framework for verifiable delegation of actions from humans to AI agents using JWT tokens. Provides fine-grained authorization with cryptographic verification and audit trails.", "n": 4, "nn": "Novel two-phase authorization framework with human-readable proposals and verifiable tokens", "m": 3, "mn": "Well-defined JWT-based approach but may need refinement for complex authorization scenarios", "o": 2, "on": "Specific focus on human-to-agent authorization delegation is relatively unique", "mo": 4, "mon": "Addresses critical trust and safety concerns with practical cryptographic approach", "r": 5, "rn": "Highly relevant for safe agent deployment and preventing unauthorized actions", "c": ["Agent identity/auth", "AI safety/alignment", "Human-agent interaction", "Policy/governance"]}


draft_name: draft-jurkovikj-httpapi-agentic-state
prompt_hash: aec4a9ff01a9d41f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:19.441847+00:00
response_json:
{"name": "draft-jurkovikj-httpapi-agentic-state", "s": "Defines Agentic State Transfer (AST) HTTP profile for managing canonical resource state across multiple synchronized representations. Uses semantic validators and optimistic concurrency control for atomic agent mutations.", "n": 4, "nn": "Novel approach to HTTP resource state synchronization across representations for agent environments", "m": 4, "mn": "Comprehensive technical specification with clear semantic model and implementation guidance", "o": 2, "on": "Unique focus on multi-representation state synchronization for agents", "mo": 3, "mon": "Technical complexity may slow adoption but addresses important consistency problems", "r": 4, "rn": "Very relevant for agent-driven web interactions and preventing race conditions", "c": ["Data formats/interop", "A2A protocols", "ML traffic mgmt"]}


draft_name: draft-huang-rats-agentic-eat-cap-attest
prompt_hash: 29721d54ef59dd63
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:37.823733+00:00
response_json:
{"name": "draft-huang-rats-agentic-eat-cap-attest", "s": "Extends Entity Attestation Token (EAT) to support capability attestation for agentic AI systems. Enables secure assertion of agent functional, reasoning, and operational capabilities.", "n": 4, "nn": "Novel application of EAT to agentic systems with new capability-specific claims", "m": 2, "mn": "Early stage draft at only 6 pages with basic specification", "o": 2, "on": "Some overlap with agent identity work but unique attestation focus", "mo": 3, "mon": "Part of emerging RATS working group interest in AI systems", "r": 4, "rn": "Highly relevant for trustworthy AI deployment and verification", "c": ["Agent identity/auth", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-yan-a2a-device-agent-applicability
prompt_hash: 1d7c2c17df037987
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:37.846841+00:00
response_json:
{"name": "draft-yan-a2a-device-agent-applicability", "s": "Discusses applying Agent-to-Agent (A2A) Protocol to network management for communication between Controller and Device Agents. Explores integration with existing protocols like NETCONF and RESTCONF.", "n": 3, "nn": "Applies A2A concepts to network management domain with device agents", "m": 3, "mn": "Well-developed at 19 pages with detailed workflows and scenarios", "o": 3, "on": "Moderate overlap with existing network management and A2A work", "mo": 4, "mon": "Strong alignment with network automation trends and SDN evolution", "r": 4, "rn": "Very relevant to autonomous network operations and management", "c": ["A2A protocols", "Autonomous netops", "Data formats/interop"]}


draft_name: draft-cui-dns-native-agent-naming-resolution
prompt_hash: 66f2ce661ddf31d5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:37.857900+00:00
response_json:
{"name": "draft-cui-dns-native-agent-naming-resolution", "s": "Specifies DNS-native naming and resolution for AI agents using FQDNs and SVCB records. Emphasizes DNS as authoritative source with graceful degradation for legacy clients.", "n": 4, "nn": "Creative use of existing DNS infrastructure for agent discovery and identity", "m": 4, "mn": "Comprehensive 26-page specification with detailed technical design", "o": 2, "on": "Unique DNS-based approach with minimal overlap to other agent work", "mo": 3, "mon": "Leverages proven DNS infrastructure but requires adoption momentum", "r": 5, "rn": "Extremely relevant for scalable agent ecosystems and internet integration", "c": ["Agent discovery/reg", "Agent identity/auth", "Data formats/interop"]}


draft_name: draft-goswami-agentic-jwt
prompt_hash: 10b54f12fd990adb
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:37.867385+00:00
response_json:
{"name": "draft-goswami-agentic-jwt", "s": "Extends OAuth 2.0 with Agentic JWT to address authorization challenges in autonomous AI systems. Introduces cryptographic agent identity and workflow-aware token binding to solve intent-execution separation.", "n": 5, "nn": "Addresses fundamental new problem of intent-execution separation in AI agents", "m": 4, "mn": "Extensive 71-page specification with security analysis and validation", "o": 2, "on": "Novel approach to OAuth extension with minimal overlap", "mo": 4, "mon": "Addresses critical security needs for enterprise AI adoption", "r": 5, "rn": "Extremely relevant for secure autonomous agent deployment", "c": ["Agent identity/auth", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-zhang-aiproto-svcb-mapping-for-agents
prompt_hash: dfa627c1adfa805d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:37.878426+00:00
response_json:
{"name": "draft-zhang-aiproto-svcb-mapping-for-agents", "s": "Defines new DNS resource record type AGENT as SVCB-compatible RR for agent service resolution. Addresses limitations of current DNS for intelligent agent protocols.", "n": 3, "nn": "New DNS record type specifically for agent services", "m": 2, "mn": "Short 6-page draft with basic mapping specifications", "o": 4, "on": "Significant overlap with draft-cui-dns-native-agent-naming-resolution", "mo": 2, "mon": "Competing approach to DNS-based agent resolution may limit adoption", "r": 3, "rn": "Relevant but potentially redundant with other DNS-based agent work", "c": ["Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-chen-ai-agent-auth-new-requirements
prompt_hash: 80a13cf746ceb3e7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:59.560335+00:00
response_json:
{"name": "draft-chen-ai-agent-auth-new-requirements", "s": "Identifies new authentication and authorization requirements for AI agents that go beyond traditional human-user frameworks. Focuses on managing dynamic agent behavior rather than static identity verification.", "n": 4, "nn": "Novel focus on dynamic behavior-based auth vs static identity, addressing fundamental paradigm shift for AI agents", "m": 2, "mn": "Early stage requirements document, lacks concrete solutions or implementation details", "o": 1, "on": "Unique focus on AI agent auth requirements, no direct overlap with other drafts", "mo": 3, "mon": "Addresses critical security gap but needs broader community input and technical solutions", "r": 5, "rn": "Extremely relevant as AI agents proliferate and existing auth frameworks prove inadequate", "c": ["Agent identity/auth", "AI safety/alignment"]}


draft_name: draft-chen-oauth-rar-agent-extensions
prompt_hash: a52523c72ff01dc9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:59.583601+00:00
response_json:
{"name": "draft-chen-oauth-rar-agent-extensions", "s": "Extends OAuth RAR with policy_context and lifecycle_binding members for AI agent environments. Enables policy assurance levels and task-bound authorization lifetimes.", "n": 4, "nn": "Concrete extensions to established OAuth RAR standard, novel lifecycle binding concept", "m": 4, "mn": "Well-structured technical solution building on RFC 9396, includes specific implementation details", "o": 2, "on": "Builds on OAuth RAR but addresses distinct AI agent requirements not covered elsewhere", "mo": 4, "mon": "Strong technical foundation on established standard, clear implementation path", "r": 5, "rn": "Highly relevant for securing AI agent interactions with practical OAuth integration", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]}


draft_name: draft-han-ai-agent-impact-infra
prompt_hash: 0d4aef95c6c7d1e8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:59.591946+00:00
response_json:
{"name": "draft-han-ai-agent-impact-infra", "s": "Discusses and analyzes the impact of AI agents on network infrastructure. Aims to facilitate IETF discussion and standardization efforts.", "n": 2, "nn": "General analysis document, limited novel technical insights", "m": 2, "mn": "Basic discussion document with analysis issues, needs more technical depth", "o": 3, "on": "Some overlap with other infrastructure-focused AI agent discussions", "mo": 2, "mon": "Broad scope but lacks concrete proposals, may struggle to gain traction", "r": 3, "rn": "Moderately relevant for understanding infrastructure impacts but lacks actionable content", "c": ["Autonomous netops", "ML traffic mgmt"]}


draft_name: draft-yu-dmsc-ai-agent-use-cases-in-6g
prompt_hash: e668f95d05885b9f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:59.605136+00:00
response_json:
{"name": "draft-yu-dmsc-ai-agent-use-cases-in-6g", "s": "Introduces AI agent use cases in 6G networks based on 3GPP SA1 technical reports. Elaborates on operator requirements for AI agent integration.", "n": 2, "nn": "Largely references existing 3GPP work, limited novel contribution beyond compilation", "m": 3, "mn": "Decent compilation of use cases but heavily dependent on external specifications", "o": 4, "on": "Significant overlap with 3GPP work and general 6G AI discussions", "mo": 3, "mon": "Benefits from 3GPP backing but unclear IETF-specific value proposition", "r": 3, "rn": "Relevant for 6G context but limited broader applicability beyond telecom", "c": ["Autonomous netops", "ML traffic mgmt", "Agent discovery/reg"]}


draft_name: draft-chang-agent-token-efficient
prompt_hash: 3a821dd6432c259f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:15:59.614174+00:00
response_json:
{"name": "draft-chang-agent-token-efficient", "s": "Defines ADOL (Agentic Data Optimization Layer) to address token bloat in agent communication protocols. Introduces schema deduplication, adaptive fields, and retrieval-based selection.", "n": 5, "nn": "Highly novel approach to token efficiency problem, introduces concrete technical solutions with ADOL framework", "m": 4, "mn": "Well-developed technical solution with specific mechanisms and backward compatibility", "o": 2, "on": "Addresses efficiency concerns not directly tackled by other agent communication drafts", "mo": 4, "mon": "Solves real performance problem with practical implementation approach", "r": 5, "rn": "Extremely relevant as LLM token costs and context limits are major practical constraints", "c": ["A2A protocols", "Data formats/interop", "Model serving/inference"]}


draft_name: draft-fu-nmop-agent-communication-framework
prompt_hash: 0ddc0e128c038281
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:21.758816+00:00
response_json:
{"name": "draft-fu-nmop-agent-communication-framework", "s": "Proposes a multi-agent communication framework for network AIOps with AI gateway, Agent Name Service, and security features. Focuses on coordinating heterogeneous agents for intelligent network operations and maintenance.", "n": 3, "nn": "Standard multi-agent coordination approach but network operations focus adds domain-specific value", "m": 2, "mn": "Early stage framework with basic architectural components outlined but limited technical detail", "o": 4, "on": "Significant overlap with other agent communication and discovery drafts in this set", "mo": 3, "mon": "Network operations domain has established interest but multi-agent approach is emerging", "r": 4, "rn": "Highly relevant as networks become more complex and autonomous operations gain traction", "c": ["A2A protocols", "Autonomous netops", "Agent discovery/reg"]}


draft_name: draft-pioli-agent-discovery
prompt_hash: de4d213beccbbbda
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:21.779320+00:00
response_json:
{"name": "draft-pioli-agent-discovery", "s": "Specifies ARDP, a lightweight protocol for agent registration and discovery in distributed environments. Provides stable identities, endpoint resolution, capability advertisement, and security-first discovery.", "n": 3, "nn": "Well-defined protocol approach to agent discovery with practical transport-agnostic design", "m": 3, "mn": "More concrete protocol specification with clear technical components and interoperability focus", "o": 3, "on": "Overlaps with discovery aspects of other drafts but focuses specifically on the protocol layer", "mo": 3, "mon": "Agent discovery is fundamental need but market adoption unclear", "r": 4, "rn": "Essential building block for distributed agent systems across many domains", "c": ["Agent discovery/reg", "Agent identity/auth", "A2A protocols"]}


draft_name: draft-yue-anima-agent-recovery-networks
prompt_hash: f5dc6b1a3ec333a3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:21.790021+00:00
response_json:
{"name": "draft-yue-anima-agent-recovery-networks", "s": "Defines task-oriented multi-agent framework for fault recovery in converged mobile networks. Targets 5G/6G deployments like MOCN and SNPN where centralized management is insufficient.", "n": 4, "nn": "Novel application of multi-agent systems to specific mobile network recovery challenges", "m": 3, "mn": "Domain-specific approach with clear use cases but implementation details need development", "o": 2, "on": "Unique focus on mobile network recovery though shares general multi-agent concepts", "mo": 4, "mon": "5G/6G network complexity drives strong industry need for automated recovery solutions", "r": 5, "rn": "Extremely relevant as mobile networks become more complex and require autonomous management", "c": ["Autonomous netops", "A2A protocols", "Policy/governance"]}


draft_name: draft-diaconu-agents-authz-info-sharing
prompt_hash: 98a1da15740a31c5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:21.799737+00:00
response_json:
{"name": "draft-diaconu-agents-authz-info-sharing", "s": "Addresses authorization challenges in distributed multi-agent systems across multiple domains. Covers dynamic identity, interoperable claims, and verifiable credentials for secure cross-domain authorization.", "n": 3, "nn": "Applies existing identity/authorization concepts to multi-agent context with cross-domain focus", "m": 3, "mn": "Substantial document addressing real security challenges but builds on established identity patterns", "o": 3, "on": "Overlaps with identity aspects of cross-domain drafts but deeper focus on authorization specifics", "mo": 3, "mon": "Authorization is critical for agent deployment but competing standards may emerge", "r": 4, "rn": "Essential for practical multi-domain agent systems where security is paramount", "c": ["Agent identity/auth", "Policy/governance", "AI safety/alignment"]}


draft_name: draft-cui-dmsc-agent-cdi
prompt_hash: 1725b7765ae0f5d2
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:21.809779+00:00
response_json:
{"name": "draft-cui-dmsc-agent-cdi", "s": "Defines comprehensive framework for cross-domain AI agent interoperability including identity federation and trust establishment. Enables multi-domain collaboration without centralized control.", "n": 3, "nn": "Comprehensive approach to cross-domain agent interoperability combining multiple established concepts", "m": 2, "mn": "Extensive framework but appears early stage with broad scope requiring significant development", "o": 4, "on": "Heavy overlap with authorization draft and touches on discovery/communication aspects", "mo": 3, "mon": "Cross-domain interoperability is important but complexity may limit adoption", "r": 4, "rn": "Addresses fundamental challenge for large-scale agent deployment across organizations", "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance", "A2A protocols"]}


draft_name: draft-chang-agent-context-interaction
prompt_hash: 41806c54b833ae54
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:40.595953+00:00
response_json:
{"name": "draft-chang-agent-context-interaction", "s": "Defines procedures for distributing context among multiple agents in complex workflows. Aims to optimize execution latency, token consumption, and task success rates.", "n": 3, "nn": "Context distribution optimization is novel but builds on established multi-agent coordination concepts", "m": 2, "mn": "Brief abstract and early stage development suggest limited technical depth", "o": 3, "on": "Overlaps with agent communication and workflow management concepts", "mo": 2, "mon": "Single author draft with minimal detail suggests limited momentum", "r": 4, "rn": "Context management is crucial for practical multi-agent systems", "c": ["A2A protocols", "ML traffic mgmt"]}


draft_name: draft-agent-gw
prompt_hash: 5d17803349df697a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:40.610346+00:00
response_json:
{"name": "draft-agent-gw", "s": "Proposes an Intelligent Agent Communication Gateway for large-scale multi-agent collaboration. Features semantic routing, working memory, and protocol adaptation mechanisms.", "n": 4, "nn": "Comprehensive gateway architecture with semantic routing and working memory is quite novel", "m": 3, "mn": "Good architectural overview but implementation details appear limited", "o": 2, "on": "Some overlap with general gateway concepts but agent-specific features are unique", "mo": 3, "mon": "Solid architectural vision but unclear community adoption", "r": 5, "rn": "Addresses critical infrastructure needs for multi-agent systems", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-birkholz-verifiable-agent-conversations
prompt_hash: 9f2c63437f7dc720
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:40.620494+00:00
response_json:
{"name": "draft-birkholz-verifiable-agent-conversations", "s": "Defines CDDL-based data format for verifiable agent conversation records using COSE signing. Supports accountability, compliance, and cross-vendor interoperability for agent interactions.", "n": 4, "nn": "Verifiable conversation records for agents is novel and addresses important trust concerns", "m": 5, "mn": "Comprehensive 51-page specification with detailed CDDL definitions shows high maturity", "o": 2, "on": "Builds on existing standards but application to agent conversations is unique", "mo": 4, "mon": "Established author with detailed specification suggests strong momentum", "r": 5, "rn": "Critical for agent accountability and regulatory compliance", "c": ["AI safety/alignment", "Data formats/interop", "Policy/governance"]}


draft_name: draft-mishra-oauth-agent-grants
prompt_hash: dc6d3888b7224743
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:40.631769+00:00
response_json:
{"name": "draft-mishra-oauth-agent-grants", "s": "Extends OAuth 2.0 for AI agent authorization with human consent verification, revocation, and audit trails. Uses DIDs for agent identity and provides multi-agent delegation capabilities.", "n": 4, "nn": "Agent-specific OAuth extension with DID integration and cascade revocation is novel", "m": 4, "mn": "Well-developed 27-page specification with clear protocol definitions", "o": 3, "on": "Extends OAuth 2.0 but agent-specific features reduce overlap", "mo": 3, "mon": "Addresses clear market need but adoption uncertain", "r": 5, "rn": "Essential for secure agent authorization in production systems", "c": ["Agent identity/auth", "Policy/governance", "Human-agent interaction"]}


draft_name: draft-sipos-dtn-bp-safe
prompt_hash: d614a66055ea9a35
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:16:40.644374+00:00
response_json:
{"name": "draft-sipos-dtn-bp-safe", "s": "Defines security association negotiation protocol for Bundle Protocol agents in delay-tolerant networks. Optimizes asymmetric-key operations for high-throughput DTN security.", "n": 3, "nn": "DTN-specific security associations are somewhat novel but follow established patterns", "m": 5, "mn": "Comprehensive 77-page specification with detailed protocol definitions", "o": 4, "on": "Significant overlap with general security association protocols", "mo": 3, "mon": "Mature specification but DTN market is niche", "r": 2, "rn": "Limited relevance to mainstream AI agent deployments", "c": ["Agent identity/auth", "Autonomous netops"]}


draft_name: draft-jiang-seat-dynamic-attestation
prompt_hash: 081d487af0095fdb
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:02.002205+00:00
response_json:
{"name": "draft-jiang-seat-dynamic-attestation", "s": "Defines dynamic attestation mechanisms for AI agents to convey runtime posture changes during long-lived TLS sessions. Enables relying parties to make authorization decisions based on current agent state including platform TCB, manifest, and runtime context.", "n": 4, "nn": "Novel application of remote attestation to AI agent runtime verification with dynamic updates", "m": 2, "mn": "Early stage use case description, lacks detailed protocol specification", "o": 2, "on": "Some overlap with general remote attestation work but AI agent focus is distinct", "mo": 3, "mon": "Addresses real need for trusted AI agent communication but limited detail", "r": 4, "rn": "Highly relevant for secure AI agent deployments and trust establishment", "c": ["Agent identity/auth", "AI safety/alignment", "A2A protocols"]}


draft_name: draft-gaikwad-woa
prompt_hash: 7ad3eddc1de799ae
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:02.022230+00:00
response_json:
{"name": "draft-gaikwad-woa", "s": "Specifies Web of Agents (WoA) format using JSON Schema to describe AI agent inputs/outputs served from well-known HTTP locations. Provides uniform invocation convention for HTTP-hosted AI agents without defining discovery protocols.", "n": 3, "nn": "Straightforward application of existing web standards to agent description and invocation", "m": 3, "mn": "Reasonable level of detail for interface specification, builds on established HTTP/JSON patterns", "o": 3, "on": "Similar to OpenAPI/service description approaches but agent-specific", "mo": 3, "mon": "Practical approach leveraging web infrastructure, moderate interest likely", "r": 4, "rn": "Very relevant for web-based agent interoperability and standardization", "c": ["Agent discovery/reg", "Data formats/interop", "A2A protocols"]}


draft_name: draft-ietf-lisp-nexagon
prompt_hash: 3a34c3630c481764
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:02.032696+00:00
response_json:
{"name": "draft-ietf-lisp-nexagon", "s": "Combines LISP with H3 spatial indexing to create geospatial intelligence network for physical-world applications. Enables distributed agents to report, aggregate, and disseminate location-based state information for transportation and logistics.", "n": 4, "nn": "Creative combination of LISP routing with H3 geospatial indexing for agent networks", "m": 4, "mn": "Well-developed protocol specification with clear technical foundation", "o": 2, "on": "Builds on LISP and H3 but novel combination for agent-based geospatial applications", "mo": 4, "mon": "IETF working group adoption indicates strong momentum and community support", "r": 4, "rn": "Highly relevant for location-aware autonomous systems and IoT agent deployments", "c": ["Autonomous netops", "A2A protocols", "Data formats/interop"]}


draft_name: draft-cosmos-protocol-specification
prompt_hash: 80d8a4c95369f8e6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:02.042762+00:00
response_json:
{"name": "draft-cosmos-protocol-specification", "s": "Defines comprehensive badge-based identity and communication system with trust scoring, post-quantum encryption, and semantic messaging. Designed for deployments preferring to avoid external blockchain infrastructure while supporting decentralized identity management.", "n": 5, "nn": "Ambitious integration of multiple novel concepts: badge identity, trust scoring, post-quantum crypto, semantic grammar", "m": 2, "mn": "Very early stage with broad scope, appears incomplete based on abstract truncation", "o": 2, "on": "Some concepts exist separately but this specific integration approach is unique", "mo": 2, "mon": "Complex scope may hinder adoption, unclear community backing", "r": 3, "rn": "Addresses important identity and trust challenges but may be overly ambitious", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]}


draft_name: draft-kale-agntcy-federated-privacy
prompt_hash: 7a874b3027217a08
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:02.051782+00:00
response_json:
{"name": "draft-kale-agntcy-federated-privacy", "s": "Specifies architecture for privacy-preserving federated learning across multi-tenant AI agent systems. Combines federated averaging, differential privacy, and secure aggregation to enable cross-organizational model training while maintaining data isolation.", "n": 3, "nn": "Standard application of known federated learning techniques to multi-tenant agent scenarios", "m": 3, "mn": "Reference architecture with established privacy techniques, reasonable technical depth", "o": 4, "on": "Significant overlap with existing federated learning and differential privacy literature", "mo": 3, "mon": "Addresses practical deployment concerns, moderate community interest expected", "r": 4, "rn": "Very relevant for enterprise AI agent deployments requiring privacy preservation", "c": ["ML traffic mgmt", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-li-dmsc-inf-architecture
prompt_hash: 4d39da042eb3b81f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:22.375756+00:00
response_json:
{"name": "draft-li-dmsc-inf-architecture", "s": "Proposes a network infrastructure architecture for large-scale multi-agent collaboration. Focuses on how network control and forwarding functions can actively participate in agent coordination.", "n": 3, "nn": "Novel application of network infrastructure to agent collaboration, but builds on existing networking concepts", "m": 2, "mn": "Early stage architectural framework, lacks implementation details and validation", "o": 2, "on": "Related to other DMSC drafts but focuses specifically on infrastructure layer", "mo": 3, "mon": "Part of coordinated DMSC effort, moderate early interest expected", "r": 4, "rn": "Highly relevant as agent systems scale and need infrastructure support", "c": ["Autonomous netops", "A2A protocols", "ML traffic mgmt"]}


draft_name: draft-liu-dmsc-gw-requirements
prompt_hash: 90fdfc0a65bb76dc
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:22.397770+00:00
response_json:
{"name": "draft-liu-dmsc-gw-requirements", "s": "Defines requirements for gateways in multi-agent systems to improve scalability and security. Identifies gaps in current gateway solutions for agent collaboration.", "n": 3, "nn": "Applies gateway concepts to agent systems with some novel requirements", "m": 2, "mn": "Requirements document without protocol specification or implementation", "o": 2, "on": "Complements DMSC architecture draft, minimal overlap with existing gateway specs", "r": 3, "rn": "Moderately relevant for agent system scaling, but more specialized use case", "mo": 2, "mon": "Limited scope may restrict broader community engagement", "c": ["A2A protocols", "Agent identity/auth", "Data formats/interop"]}


draft_name: draft-zhang-dmsc-mas-communication
prompt_hash: 4d880b9ba0a6b76c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:22.424117+00:00
response_json:
{"name": "draft-zhang-dmsc-mas-communication", "s": "Analyzes security risks in multi-agent communication and limitations of existing protocols like TLS and HTTP. Establishes problem statement for agent-native security needs.", "n": 4, "nn": "Good analysis of agent-specific security challenges not well addressed by current protocols", "m": 3, "mn": "Solid problem analysis but lacks proposed solutions", "o": 1, "on": "Unique security analysis perspective on agent communication", "r": 5, "rn": "Very relevant as agent systems need security models beyond traditional web protocols", "mo": 4, "mon": "Security analysis likely to generate significant community interest and discussion", "c": ["A2A protocols", "AI safety/alignment", "Agent identity/auth"]}


draft_name: draft-guy-bary-stamp-protocol
prompt_hash: 5f57d06113bfca6f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:22.435776+00:00
response_json:
{"name": "draft-guy-bary-stamp-protocol", "s": "Defines STAMP protocol for cryptographic delegation and proof in AI agent systems. Provides task-bound tokens and integrates with OAuth 2.0 and zero-trust principles.", "n": 5, "nn": "Novel cryptographic approach specifically designed for agent delegation and task binding", "m": 4, "mn": "Well-developed protocol specification with clear integration points", "o": 1, "on": "Unique protocol design, minimal overlap with existing auth mechanisms", "r": 5, "rn": "Highly relevant for secure agent deployments and enterprise adoption", "mo": 4, "mon": "Strong technical approach likely to attract security and auth working group attention", "c": ["Agent identity/auth", "AI safety/alignment", "A2A protocols"]}


draft_name: draft-abaris-aicdh
prompt_hash: 0cb6e371fe4cbc07
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:22.445032+00:00
response_json:
{"name": "draft-abaris-aicdh", "s": "Proposes HTTP header for disclosing AI-generated content in web responses. Provides machine-readable metadata for user agents and archiving systems.", "n": 2, "nn": "Straightforward application of HTTP headers to AI content disclosure", "m": 3, "mn": "Clear specification but limited scope and technical complexity", "o": 2, "on": "Some similarity to content-type headers but AI-specific application is unique", "r": 3, "rn": "Moderately relevant for AI transparency but peripheral to core networking concerns", "mo": 3, "mon": "Simple enough for quick adoption but may face policy/governance debates", "c": ["Data formats/interop", "Policy/governance", "Human-agent interaction"]}


draft_name: draft-sz-dmsc-iaip
prompt_hash: 67384e96f162a04f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:43.777207+00:00
response_json:
{"name": "draft-sz-dmsc-iaip", "s": "Defines Intent-based Agent Interconnection Protocol (IAIP) for dynamic agent discovery and routing at gateways based on semantic intent rather than static addressing. Enables capability-based agent matching and dispatching.", "n": 4, "nn": "Novel semantic intent-based routing approach for AI agents with dynamic capability matching", "m": 2, "mn": "Early stage specification with broad scope but limited implementation detail", "o": 3, "on": "Overlaps with DNS-AID and AWP on agent discovery, but uses different semantic intent approach", "mo": 3, "mon": "Addresses emerging need for agent interconnection but lacks clear adoption path", "r": 4, "rn": "Highly relevant for multi-agent systems and agent interoperability infrastructure", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-jia-oauth-scope-aggregation
prompt_hash: 5687436aa4c82eb2
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:43.800509+00:00
response_json:
{"name": "draft-jia-oauth-scope-aggregation", "s": "Extends OAuth 2.0 with scope aggregation to reduce authorization round-trips in multi-step AI agent workflows. Improves efficiency by bundling required permissions upfront.", "n": 3, "nn": "Practical extension to existing OAuth for AI workflow optimization", "m": 3, "mn": "Well-defined problem with clear solution building on established OAuth framework", "o": 2, "on": "Extends OAuth but addresses AI-specific use case not covered elsewhere", "mo": 4, "mon": "Strong potential adoption given OAuth ubiquity and clear efficiency benefits", "r": 4, "rn": "Very relevant for AI agent authorization and workflow management", "c": ["Agent identity/auth", "Policy/governance"]}


draft_name: draft-mozleywilliams-dnsop-dnsaid
prompt_hash: eeffcf49d3fe750c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:43.813011+00:00
response_json:
{"name": "draft-mozleywilliams-dnsop-dnsaid", "s": "Uses existing DNS infrastructure for AI agent discovery through structured namespace and metadata exchange. Enables organizations to publish agent capabilities in their DNS domains.", "n": 3, "nn": "Leverages proven DNS infrastructure for new AI agent discovery use case", "m": 4, "mn": "Well-structured specification building on solid DNS foundation with clear scope", "o": 3, "on": "Overlaps with IAIP on agent discovery but uses different DNS-based approach", "mo": 4, "mon": "High adoption potential due to DNS ubiquity and no protocol changes required", "r": 4, "rn": "Highly relevant for scalable agent discovery and interoperability", "c": ["Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-ietf-anima-brski-prm
prompt_hash: ddcd9336ea5fae0f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:43.825627+00:00
response_json:
{"name": "draft-ietf-anima-brski-prm", "s": "Enhances BRSKI for device bootstrapping where pledges act as servers in responder mode. Introduces registrar-agent component for scenarios with limited registrar communication.", "n": 2, "nn": "Incremental enhancement to existing BRSKI protocol for specific deployment scenarios", "m": 4, "mn": "Mature specification with detailed protocol mechanics and comprehensive coverage", "o": 1, "on": "Extends BRSKI but addresses distinct use case not covered by other AI agent drafts", "mo": 3, "mon": "Limited to specific BRSKI deployment scenarios but addresses real operational need", "r": 2, "rn": "Low relevance to AI agents specifically, focused on general device bootstrapping", "c": ["Agent identity/auth", "Autonomous netops"]}


draft_name: draft-vinaysingh-awp-wellknown
prompt_hash: 228d94dfa1853f4b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:17:43.844447+00:00
response_json:
{"name": "draft-vinaysingh-awp-wellknown", "s": "Defines well-known URI and link relation for exposing website workflows to automated agents. Provides minimal JSON format for agent interaction without web scraping.", "n": 3, "nn": "Simple approach to structured agent-web interaction using established well-known URI pattern", "m": 3, "mn": "Concise specification with clear scope, though limited technical depth", "o": 2, "on": "Complements other agent discovery mechanisms but focuses on web workflow exposure", "mo": 3, "mon": "Moderate potential given simplicity but requires website operator adoption", "r": 3, "rn": "Relevant for web-based agent interactions and structured workflow automation", "c": ["Human-agent interaction", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-yang-ioa-protocol
prompt_hash: 8d3c9a334d1f1c75
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:02.824001+00:00
response_json:
{"name": "draft-yang-ioa-protocol", "s": "Defines the Internet of Agents Protocol for distributed collaboration among heterogeneous AI agents. Provides layered architecture for dynamic team formation and task coordination across diverse agent types.", "n": 4, "nn": "Novel protocol specifically for multi-agent collaboration with focus on heterogeneous systems", "m": 3, "mn": "Well-structured but lacks implementation details and security considerations", "o": 2, "on": "Some overlap with general agent communication but focused on collaboration aspects", "mo": 3, "mon": "Targets emerging 6G scenarios which may drive adoption", "r": 4, "rn": "Highly relevant as multi-agent systems become more prevalent", "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-blahaj-grow-rpki-oauth
prompt_hash: d9bf4ce28b09ebf0
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:02.845831+00:00
response_json:
{"name": "draft-blahaj-grow-rpki-oauth", "s": "Specifies method to bind OpenID Connect authentication to ASN agents using RPKI infrastructure. Addresses authentication gaps in the GROW Working Group's Peering API.", "n": 3, "nn": "Creative combination of RPKI and OIDC for network operator authentication", "m": 2, "mn": "Brief draft with limited technical detail and implementation guidance", "o": 1, "on": "Unique approach combining these specific technologies", "mo": 2, "mon": "Limited to specific peering use case with uncertain broader adoption", "r": 3, "rn": "Relevant for network peering but narrow application scope", "c": ["Agent identity/auth", "Policy/governance"]}


draft_name: draft-cui-nmrg-llm-benchmark
prompt_hash: bf8021792388d857
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:02.858922+00:00
response_json:
{"name": "draft-cui-nmrg-llm-benchmark", "s": "Provides comprehensive evaluation framework for LLM-based network configuration agents. Includes emulator environment, task suites, and multi-dimensional assessment metrics.", "n": 4, "nn": "First standardized benchmarking framework for LLM network agents", "m": 4, "mn": "Detailed framework with clear metrics and comprehensive evaluation approach", "o": 1, "on": "No similar standardized benchmarking approaches identified", "mo": 4, "mon": "Strong research interest in LLM network applications drives relevance", "r": 5, "rn": "Critical for advancing LLM network applications with standardized evaluation", "c": ["Autonomous netops", "Policy/governance", "Data formats/interop"]}


draft_name: draft-jiang-cats-reference-acn
prompt_hash: e0824bceb236e18c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:02.870074+00:00
response_json:
{"name": "draft-jiang-cats-reference-acn", "s": "Extends CATS framework to support AI-agent Communication Networks with reference architecture. Defines protocol stacks and signaling for agent-to-agent communication services.", "n": 3, "nn": "Extends existing CATS work to AI agent domain with new reference model", "m": 2, "mn": "High-level reference model lacking detailed protocol specifications", "o": 3, "on": "Builds heavily on existing CATS framework with agent-specific extensions", "mo": 3, "mon": "Benefits from existing CATS momentum but limited to that community", "r": 3, "rn": "Relevant for CATS community but narrow focus on specific architecture", "c": ["A2A protocols", "ML traffic mgmt", "Data formats/interop"]}


draft_name: draft-aylward-daap-v2
prompt_hash: 51e77d04ddf62176
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:02.878491+00:00
response_json:
{"name": "draft-aylward-daap-v2", "s": "Defines comprehensive protocol for AI agent accountability including authentication, monitoring, and remote control. Addresses AI safety through cryptographic identity verification and behavioral oversight.", "n": 5, "nn": "Comprehensive approach to critical AI safety and accountability challenges", "m": 4, "mn": "Well-developed protocol with detailed security and governance mechanisms", "o": 1, "on": "Unique focus on comprehensive AI accountability and safety controls", "mo": 5, "mon": "High urgency due to growing AI safety concerns and regulatory pressure", "r": 5, "rn": "Extremely relevant given current AI safety and governance discussions", "c": ["AI safety/alignment", "Agent identity/auth", "Policy/governance"]}


draft_name: draft-mozley-aidiscovery
prompt_hash: 58c54286478e3f4a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:23.201887+00:00
response_json:
{"name": "draft-mozley-aidiscovery", "s": "Defines requirements and considerations for AI agent-to-agent discovery mechanisms. Addresses the fundamental problem of how AI agents locate and identify each other in distributed systems.", "n": 4, "nn": "Novel focus on agent discovery protocols, addressing emerging need as AI agents proliferate", "m": 2, "mn": "Early stage problem statement, only 8 pages, lacks concrete protocol specification", "o": 1, "on": "Unique focus on AI agent discovery, no significant overlap with existing drafts", "mo": 3, "mon": "Addresses timely need but limited concrete progress shown", "r": 4, "rn": "Highly relevant as AI agents become more common and need discovery mechanisms", "c": ["Agent discovery/reg", "A2A protocols"]}


draft_name: draft-gupta-httpapi-events-query
prompt_hash: 4c0427107b84b95d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:23.222957+00:00
response_json:
{"name": "draft-gupta-httpapi-events-query", "s": "Proposes Events Query Protocol (EQP) built on HTTP for user agents to receive event notifications directly from resources. Offers intuitive approach where resources themselves are event sources.", "n": 3, "nn": "Builds on existing HTTP but novel application to direct resource-based event notifications", "m": 4, "mn": "Well-developed at 29 pages with detailed protocol specification", "o": 3, "on": "Some overlap with existing HTTP event mechanisms like Server-Sent Events", "mo": 3, "mon": "Solid technical foundation but unclear adoption trajectory", "r": 3, "rn": "Relevant for AI agents needing event streams, but not AI-specific", "c": ["Data formats/interop", "Human-agent interaction"]}


draft_name: draft-jewell-aibdp
prompt_hash: 47761be156d85361
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:23.235515+00:00
response_json:
{"name": "draft-jewell-aibdp", "s": "Defines AI Boundary Declaration Protocol for expressing content usage boundaries for AI systems. Provides machine-readable permissions and denials for AI training, indexing, and access.", "n": 5, "nn": "Highly novel approach to AI governance through declarative boundary protocols", "m": 2, "mn": "Short at 6 pages, appears early stage despite comprehensive scope claims", "o": 2, "on": "Some conceptual overlap with robots.txt but significantly different focus on AI boundaries", "mo": 4, "mon": "High relevance to current AI governance debates suggests good momentum potential", "r": 5, "rn": "Extremely relevant to current AI ethics and governance concerns", "c": ["Policy/governance", "AI safety/alignment"]}


draft_name: draft-rosenberg-oauth-aauth
prompt_hash: 9b50046e5a076704
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:23.245335+00:00
response_json:
{"name": "draft-rosenberg-oauth-aauth", "s": "Extends OAuth 2.1 for AI agents operating through PSTN/SMS channels to obtain access tokens using PII collected via natural language. Addresses hallucination-based impersonation risks.", "n": 4, "nn": "Novel OAuth extension specifically designed for AI agent authentication challenges", "m": 3, "mn": "Moderate maturity at 10 pages with specific technical approach", "o": 2, "on": "Extends existing OAuth but addresses unique AI agent use cases", "mo": 3, "mon": "Addresses practical AI deployment needs but faces significant security challenges", "r": 4, "rn": "Highly relevant for AI agent deployment in practical scenarios", "c": ["Agent identity/auth", "AI safety/alignment"]}


draft_name: draft-kompella-lsr-mptecap
prompt_hash: 8a994aabe4fd1576
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:23.255372+00:00
response_json:
{"name": "draft-kompella-lsr-mptecap", "s": "Defines capabilities advertising for Multipath Traffic Engineering (MPTE) in IGP routing protocols. Enables nodes to advertise MPTE support for tunnel provisioning decisions.", "n": 2, "nn": "Incremental extension to existing traffic engineering capabilities advertising", "m": 3, "mn": "Concise but complete at 6 pages, builds on established IGP mechanisms", "o": 4, "on": "Significant overlap with existing TE capabilities and IGP extensions", "mo": 2, "mon": "Limited to specific networking community, not AI-focused", "r": 2, "rn": "Limited relevance to AI/agent systems, traditional networking focus", "c": ["ML traffic mgmt"]}


draft_name: draft-rosenberg-cheq
prompt_hash: e8b238c793bdb1ba
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:42.902434+00:00
response_json:
{"name": "draft-rosenberg-cheq", "s": "Proposes CHEQ protocol for human-in-the-loop confirmation of AI agent decisions before execution. Uses signed objects to prevent AI hallucinations from causing unwanted actions while protecting human privacy.", "n": 4, "nn": "Novel approach to AI safety through structured confirmation protocol with privacy protection", "m": 3, "mn": "Well-defined protocol but lacks implementation details and security analysis", "o": 2, "on": "Some overlap with general AI safety approaches but protocol specifics are unique", "mo": 3, "mon": "Addresses important AI safety concerns but limited community involvement evident", "r": 4, "rn": "Highly relevant as AI agents become more autonomous and safety becomes critical", "c": ["AI safety/alignment", "Human-agent interaction", "A2A protocols"]}


draft_name: draft-leon-distributed-multi-signer
prompt_hash: 5dd6f423b9790559
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:42.925420+00:00
response_json:
{"name": "draft-leon-distributed-multi-signer", "s": "Defines distributed DNSSEC multi-signer architecture with multi-signer agents and combiners. Introduces HSYNC RRtype and secure communication mechanisms between MSAs.", "n": 3, "nn": "Extends existing DNSSEC multi-signer concepts with distributed approach", "m": 4, "mn": "Comprehensive 31-page specification with detailed technical mechanisms", "o": 3, "on": "Builds on RFC8901 multi-signer model but adds distributed aspects", "mo": 3, "mon": "DNSSEC automation has steady interest but limited to DNS community", "r": 2, "rn": "Limited AI/agent relevance beyond DNS infrastructure automation", "c": ["Autonomous netops", "Data formats/interop"]}


draft_name: draft-mp-agntcy-ads
prompt_hash: 9e3058a5b32bf040
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:42.937656+00:00
response_json:
{"name": "draft-mp-agntcy-ads", "s": "Describes Agent Directory Service for storing and discovering AI agent metadata based on skills. Features distributed directories with content-routing protocol for agent discovery.", "n": 4, "nn": "First comprehensive directory service specifically designed for AI agent discovery", "m": 3, "mn": "Good conceptual framework but needs more protocol specification detail", "o": 2, "on": "Unique approach to agent discovery, minimal overlap with existing directory services", "mo": 3, "mon": "Agent discovery is important problem but early stage development", "r": 5, "rn": "Extremely relevant for AI agent ecosystem scalability and interoperability", "c": ["Agent discovery/reg", "Data formats/interop", "A2A protocols"]}


draft_name: draft-steckbeck-ua-conn-sec
prompt_hash: 1c4599e4eca00e48
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:42.947765+00:00
response_json:
{"name": "draft-steckbeck-ua-conn-sec", "s": "Proposes framework for user agents to restrict connections to authorized second and third-party resources. Aims to prevent attacks through compromised connected resources.", "n": 2, "nn": "Incremental improvement to existing web security policies like CSP", "m": 2, "mn": "Brief 6-page document lacks detailed specification and implementation guidance", "o": 4, "on": "Significant overlap with CSP and other web security frameworks", "mo": 2, "mon": "Limited evidence of community interest or implementation momentum", "r": 2, "rn": "Tangentially relevant to AI agents that use web resources", "c": ["Policy/governance", "Other AI/agent"]}


draft_name: draft-ietf-lamps-e2e-mail-guidance
prompt_hash: 6116366378f8fab9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:18:42.956259+00:00
response_json:
{"name": "draft-ietf-lamps-e2e-mail-guidance", "s": "Provides comprehensive guidance for implementing end-to-end email encryption securely. Addresses usability issues and interoperability problems in cryptographic email protection.", "n": 2, "nn": "Guidance document for existing standards rather than novel technical contribution", "m": 5, "mn": "Mature 68-page IETF working group document with extensive detail", "o": 3, "on": "Overlaps with existing email security standards but provides unique implementation guidance", "mo": 4, "mon": "Strong IETF working group backing with clear implementation focus", "r": 2, "rn": "Limited relevance to AI/agent protocols beyond general secure communication", "c": ["Data formats/interop", "Policy/governance"]}


draft_name: draft-happel-structured-email-trust
prompt_hash: 5441ce64eb314114
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:02.821750+00:00
response_json:
{"name": "draft-happel-structured-email-trust", "s": "Provides trust and security recommendations for handling structured data in email messages. Focuses on guidance for message user agents to safely process structured email content.", "n": 3, "nn": "Addresses growing need for secure structured email handling but builds on existing email security concepts", "m": 3, "mn": "Brief document suggests early stage development with basic recommendations framework", "o": 2, "on": "Some overlap with general email security work but specific to structured data trust", "mo": 2, "mon": "Limited scope and length suggests modest community engagement", "r": 3, "rn": "Relevant as structured email becomes more common, though narrow application domain", "c": ["Data formats/interop", "Agent identity/auth"]}


draft_name: draft-eggert-mailmaint-uaautoconf
prompt_hash: 646c27d764139ba0
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:02.852459+00:00
response_json:
{"name": "draft-eggert-mailmaint-uaautoconf", "s": "Specifies automatic configuration mechanism for email, calendar, and contact applications. Enables service providers to publish standardized configuration data for simplified client setup.", "n": 3, "nn": "Builds on existing autoconfig concepts but provides comprehensive multi-service approach", "m": 4, "mn": "Substantial 41-page document indicates thorough development and consideration of use cases", "o": 3, "on": "Some overlap with existing email autoconfig mechanisms and service discovery protocols", "mo": 4, "mon": "Strong author reputation and comprehensive scope suggests good momentum", "r": 4, "rn": "Highly relevant for simplifying user experience and reducing configuration errors", "c": ["Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-tojens-dhcp-option-concat-considerations
prompt_hash: 2a04e9747e419498
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:02.863919+00:00
response_json:
{"name": "draft-tojens-dhcp-option-concat-considerations", "s": "Updates RFC 3396 to make DHCP option concatenation requirements more flexible. Addresses real-world implementation deviations from original strict concatenation requirements.", "n": 2, "nn": "Incremental improvement addressing deployment reality rather than novel approach", "m": 4, "mn": "Well-motivated by deployment experience and clear problem statement", "o": 1, "on": "Unique focus on this specific DHCP implementation issue", "mo": 3, "mon": "Standards update addressing known interoperability issues should gain support", "r": 3, "rn": "Important for DHCP implementations but narrow technical scope", "c": ["Data formats/interop"]}


draft_name: draft-cui-nmrg-llm-nm
prompt_hash: dd7019db3017df3a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:02.873769+00:00
response_json:
{"name": "draft-cui-nmrg-llm-nm", "s": "Defines framework for collaborative network management between LLM agents and human operators. Introduces enhanced telemetry, decision modules, and human-in-the-loop workflows.", "n": 4, "nn": "Novel application of LLMs to network management with structured human-agent collaboration", "m": 3, "mn": "Comprehensive framework but likely early stage given emerging nature of LLM integration", "o": 2, "on": "Some overlap with general AI/ML network management but specific LLM focus is distinctive", "mo": 4, "mon": "High current interest in LLM applications and network automation convergence", "r": 5, "rn": "Extremely relevant given industry focus on AI-assisted network operations", "c": ["Human-agent interaction", "Autonomous netops", "ML traffic mgmt", "AI safety/alignment"]}


draft_name: draft-eckert-anima-acp-free-ani
prompt_hash: a2482032055fd9b4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:02.887374+00:00
response_json:
{"name": "draft-eckert-anima-acp-free-ani", "s": "Describes lightweight variation of Autonomic Networking Infrastructure without expensive ACP implementation. Uses existing ANI certificates and protocols with application-level software agents.", "n": 4, "nn": "Creative simplification of complex ANI architecture while retaining core automation benefits", "m": 4, "mn": "Detailed technical approach with clear trade-offs and implementation considerations", "o": 3, "on": "Builds heavily on existing ANIMA work but with significant architectural changes", "mo": 3, "mon": "Strong technical foundation but depends on broader ANIMA adoption momentum", "r": 4, "rn": "Highly relevant for making autonomic networking more implementable and practical", "c": ["Autonomous netops", "Agent identity/auth", "A2A protocols", "Agent discovery/reg"]}


draft_name: draft-meunier-webbotauth-registry
prompt_hash: c911743a77fede52
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:22.695832+00:00
response_json:
{"name": "draft-meunier-webbotauth-registry", "s": "Defines a JSON format for web bot signature agent cards to advertise identity, purpose, and cryptographic keys. Establishes IANA registry for extensible agent metadata discovery.", "n": 3, "nn": "Builds on existing agent card concepts but adds signature-specific elements", "m": 3, "mn": "Basic format definition with registry setup, needs more implementation details", "o": 2, "on": "Some overlap with general agent identity work but signature focus is distinct", "mo": 2, "mon": "Early draft with limited community engagement visible", "r": 4, "rn": "Agent identity and discovery are critical infrastructure needs for AI systems", "c": ["Agent identity/auth", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-rosenberg-aiproto-cheq
prompt_hash: 3129e35c9ecdf694
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:22.716925+00:00
response_json:
{"name": "draft-rosenberg-aiproto-cheq", "s": "Proposes CHEQ protocol for human confirmation of AI agent decisions before execution. Protects against AI hallucinations while preserving human privacy in tool invocation.", "n": 4, "nn": "Novel approach to human-in-the-loop validation with privacy protection", "m": 3, "mn": "Well-defined protocol with integration points but needs more technical detail", "o": 2, "on": "Unique focus on decision confirmation, complements but doesn't overlap existing protocols", "mo": 3, "mon": "Addresses critical safety concern with clear integration path", "r": 5, "rn": "Essential safety mechanism for AI agent deployment in production environments", "c": ["Human-agent interaction", "AI safety/alignment", "A2A protocols"]}


draft_name: draft-ietf-dnsop-ds-automation
prompt_hash: 228b5ebc5f730bb6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:22.727510+00:00
response_json:
{"name": "draft-ietf-dnsop-ds-automation", "s": "Provides operational recommendations for automated DS parameter acceptance in DNS. Addresses technical decisions around validation checks and multi-party coordination.", "n": 2, "nn": "Operational guidance for existing standards rather than new technical innovation", "m": 4, "mn": "Mature operational guidance from working group with practical focus", "o": 1, "on": "Specific to DNS operations with no overlap with AI/agent work", "mo": 4, "mon": "Working group draft with clear operational need and community support", "r": 1, "rn": "DNS-specific operational guidance, not relevant to AI/agent protocols", "c": ["Other AI/agent"]}


draft_name: draft-ramakrishna-satp-views-addresses
prompt_hash: 272314092ac44be3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:22.737780+00:00
response_json:
{"name": "draft-ramakrishna-satp-views-addresses", "s": "Defines view and addressing mechanisms for secure asset transfer between DLT systems. Enables cross-system asset interoperability with access control and verification.", "n": 4, "nn": "Novel abstraction for cross-DLT asset views with comprehensive security model", "m": 3, "mn": "Detailed technical specification but complex system requiring extensive validation", "o": 2, "on": "Some overlap with general interoperability work but DLT focus is distinct", "mo": 3, "mon": "Addresses growing need for blockchain interoperability", "r": 3, "rn": "Relevant for AI agents handling digital assets but narrow application domain", "c": ["Data formats/interop", "Agent identity/auth"]}


draft_name: draft-takagi-srta-trinity
prompt_hash: 3be297790db979e0
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:22.747340+00:00
response_json:
{"name": "draft-takagi-srta-trinity", "s": "Proposes SRTA architecture and Trinity Configuration for safe AGI coordination using theological analogy. Presents theoretical framework for superintelligence governance.", "n": 5, "nn": "Highly novel theological approach to AI safety architecture", "m": 1, "mn": "Very early conceptual work with limited technical specification", "o": 1, "on": "Unique approach unlike any existing AI safety or coordination work", "mo": 1, "mon": "Speculative work with unclear practical implementation path", "r": 2, "rn": "Important safety topic but too theoretical for current practical needs", "c": ["AI safety/alignment", "Policy/governance", "A2A protocols"]}


draft_name: draft-ramakrishna-satp-data-sharing
prompt_hash: 67be08e196109e29
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:43.380206+00:00
response_json:
{"name": "draft-ramakrishna-satp-data-sharing", "s": "Defines a DLT-neutral protocol for sharing asset views and metadata across blockchain networks via gateway nodes. Enables cross-system interoperability while preserving native consensus mechanisms.", "n": 3, "nn": "Builds on existing blockchain interoperability concepts but provides specific gateway protocol design", "m": 3, "mn": "Well-structured protocol definition but needs implementation validation and security analysis", "o": 2, "on": "Some overlap with blockchain interoperability work but focused on specific data sharing use case", "mo": 2, "mon": "Limited community engagement evident, needs broader blockchain ecosystem adoption", "r": 3, "rn": "Relevant for multi-chain environments but primarily traditional DLT rather than AI agents", "c": ["Data formats/interop", "A2A protocols"]}


draft_name: draft-liu-oauth-a2a-profile
prompt_hash: 762a1b3dc99829ab
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:43.402396+00:00
response_json:
{"name": "draft-liu-oauth-a2a-profile", "s": "Specifies OAuth Transaction Token profile for Agent-to-Agent communication. Embeds call chain context to maintain agent identity and authorization across distributed agent workloads.", "n": 4, "nn": "Novel application of OAuth Transaction Tokens specifically for agent-to-agent scenarios", "m": 2, "mn": "Very brief draft at 5 pages, needs substantial development and detail", "o": 3, "on": "Builds on existing OAuth work but applies it to new agent communication domain", "mo": 3, "mon": "Addresses emerging need for agent authentication but needs broader community input", "r": 5, "rn": "Highly relevant for AI agent ecosystems requiring secure inter-agent communication", "c": ["Agent identity/auth", "A2A protocols"]}


draft_name: draft-ye-problems-and-requirements-of-dns-for-ioa
prompt_hash: 4c0965cd7674f464
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:43.412628+00:00
response_json:
{"name": "draft-ye-problems-and-requirements-of-dns-for-ioa", "s": "Analyzes DNS challenges for Internet of Agents scenarios and identifies technical requirements. Explores how DNS must evolve to support agent collaboration in AI-driven environments.", "n": 4, "nn": "First systematic analysis of DNS requirements specifically for Internet of Agents", "m": 2, "mn": "Problem statement stage with limited concrete solutions or protocol specifications", "o": 1, "on": "Unique focus on DNS for agent networks, no direct overlap with existing work", "mo": 3, "mon": "Addresses important infrastructure need but early stage with limited community traction", "r": 4, "rn": "Very relevant for agent discovery and naming in large-scale AI systems", "c": ["Agent discovery/reg", "Autonomous netops"]}


draft_name: draft-ietf-httpbis-rfc6265bis
prompt_hash: 3633310ac7e52f36
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:43.422990+00:00
response_json:
{"name": "draft-ietf-httpbis-rfc6265bis", "s": "Updates HTTP Cookie specification to replace RFC 6265 with improved security and privacy. Addresses historical flaws while maintaining backward compatibility for widely-used web functionality.", "n": 2, "nn": "Incremental improvement to existing well-established standard", "m": 5, "mn": "Mature working group draft with extensive detail and broad industry review", "o": 5, "on": "Direct update to existing RFC, heavy overlap by design", "mo": 5, "mon": "Strong working group support and clear path to standardization", "r": 2, "rn": "Foundational web technology but not specifically targeted at AI/agent scenarios", "c": ["Other AI/agent"]}


draft_name: draft-meta-layer-overview
prompt_hash: 31f5b24d09fd3ee1
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:19:43.437761+00:00
response_json:
{"name": "draft-meta-layer-overview", "s": "Introduces Meta-layer concept as coordination substrate for presence, annotation, and governance on the web. Enables communities and agents to collaborate in shared digital spaces above content layers.", "n": 5, "nn": "Highly novel architectural concept for web-scale coordination and governance", "m": 1, "mn": "Very early conceptual stage, lacks concrete protocols or implementation details", "o": 1, "on": "Unique architectural vision with no direct parallels in existing work", "mo": 2, "mon": "Ambitious concept but needs significant development and community building", "r": 4, "rn": "Relevant for agent coordination and governance but very early stage", "c": ["Policy/governance", "Human-agent interaction", "A2A protocols"]}


draft_name: draft-mozleywilliams-dnsop-bandaid
prompt_hash: 1dc7cf4bb4ce0635
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:01.818801+00:00
response_json:
{"name": "draft-mozleywilliams-dnsop-bandaid", "s": "Proposes using DNS with SVCB records to enable AI agent discovery and capability advertisement. Leverages existing DNS infrastructure including DNSSEC and DANE for secure agent-to-agent discovery.", "n": 4, "nn": "Novel application of DNS service discovery specifically for AI agents with structured metadata exchange", "m": 3, "mn": "Well-structured with clear DNS integration but limited implementation details and security analysis", "o": 2, "on": "Complementary to other AI agent protocols, focuses specifically on discovery rather than communication", "mo": 3, "mon": "Addresses clear need for agent discovery but uncertain industry adoption of DNS-based approach", "r": 4, "rn": "Highly relevant for scalable AI agent ecosystems, leverages proven DNS infrastructure", "c": ["Agent discovery/reg", "A2A protocols", "Agent identity/auth"]}


draft_name: draft-rosenberg-aiproto
prompt_hash: f310d22d3bd6b0cf
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:01.844072+00:00
response_json:
{"name": "draft-rosenberg-aiproto", "s": "Defines N-ACT protocol for AI agents to discover and invoke third-party tools and APIs. Focuses on enterprise agents with enumeration and invocation capabilities.", "n": 3, "nn": "Standardizes common pattern of AI tool integration but builds on existing OpenAI specifications", "m": 4, "mn": "Comprehensive specification with clear API definitions and enterprise focus", "o": 5, "on": "Identical to draft-rosenberg-aiproto-nact - appears to be duplicate submission", "mo": 4, "mon": "Strong enterprise use case and addresses major AI integration pain point", "r": 5, "rn": "Extremely relevant for current AI agent development and enterprise adoption", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-rosenberg-aiproto-nact
prompt_hash: 73f0dfbe4a07af10
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:01.855337+00:00
response_json:
{"name": "draft-rosenberg-aiproto-nact", "s": "Defines N-ACT protocol for AI agents to discover and invoke third-party tools and APIs. Focuses on enterprise agents with enumeration and invocation capabilities.", "n": 3, "nn": "Standardizes common pattern of AI tool integration but builds on existing OpenAI specifications", "m": 4, "mn": "Comprehensive specification with clear API definitions and enterprise focus", "o": 5, "on": "Identical to draft-rosenberg-aiproto - appears to be duplicate submission", "mo": 4, "mon": "Strong enterprise use case and addresses major AI integration pain point", "r": 5, "rn": "Extremely relevant for current AI agent development and enterprise adoption", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-rosenberg-aiproto-framework
prompt_hash: 5c5e0af12c0468f3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:01.866881+00:00
response_json:
{"name": "draft-rosenberg-aiproto-framework", "s": "Provides framework and requirements for AI agent protocols on the Internet. Surveys existing approaches like MCP and A2A to guide IETF standardization efforts.", "n": 2, "nn": "Primarily synthesizes existing work rather than proposing new technical solutions", "m": 4, "mn": "Well-researched framework document with comprehensive use cases and requirements analysis", "o": 3, "on": "Overlaps with general AI protocol discussions but serves as foundational framework", "mo": 5, "mon": "Critical for establishing IETF direction in AI agent standardization", "r": 5, "rn": "Essential framework document for the emerging field of AI agent protocols", "c": ["A2A protocols", "Policy/governance", "Data formats/interop"]}


draft_name: draft-zeng-mcp-troubleshooting
prompt_hash: cff4e4398fb42154
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:01.886736+00:00
response_json:
{"name": "draft-zeng-mcp-troubleshooting", "s": "Applies Model Context Protocol to network management for intent-based troubleshooting. Maps MCP roles to network devices and controllers for automated operations.", "n": 3, "nn": "Novel application of MCP to network management domain with practical automation benefits", "m": 2, "mn": "Brief document with limited technical depth and implementation guidance", "o": 2, "on": "Unique application domain though builds on existing MCP standard", "mo": 3, "mon": "Interesting network management application but narrow scope may limit adoption", "r": 4, "rn": "Highly relevant for network automation and demonstrates practical AI agent applications", "c": ["Autonomous netops", "Data formats/interop", "Human-agent interaction"]}


draft_name: draft-zm-rtgwg-mcp-troubleshooting
prompt_hash: 76a906cd5f7eecc6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:21.680148+00:00
response_json:
{"name": "draft-zm-rtgwg-mcp-troubleshooting", "s": "Proposes using Model Context Protocol (MCP) to enable LLM-based automated network troubleshooting. Maps MCP roles to network management domain with devices as servers and controllers as clients.", "n": 4, "nn": "Novel application of MCP to network management with device-to-device collaboration extension", "m": 3, "mn": "Well-structured but early stage, needs implementation validation", "o": 2, "on": "Some overlap with general network automation but MCP approach is distinct", "mo": 3, "mon": "Growing interest in AI-driven network operations but MCP adoption uncertain", "r": 4, "rn": "Highly relevant as networks become more complex and require intelligent automation", "c": ["Autonomous netops", "Human-agent interaction", "Data formats/interop"]}


draft_name: draft-an-nmrg-i2icf-cits
prompt_hash: 6eb48052bb46c422
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:21.703465+00:00
response_json:
{"name": "draft-an-nmrg-i2icf-cits", "s": "Defines framework for orchestrating In-Network Computing Functions in Cooperative Intelligent Transportation Systems. Incorporates Agent-to-Agent communication for multi-domain V2X scenarios.", "n": 4, "nn": "Combines in-network computing with A2A protocols specifically for transportation systems", "m": 3, "mn": "Comprehensive framework but requires extensive validation in real C-ITS deployments", "o": 3, "on": "Overlaps with general V2X and edge computing work but A2A integration is newer", "mo": 4, "mon": "Strong momentum in autonomous vehicles and smart transportation infrastructure", "r": 4, "rn": "Very relevant for emerging connected vehicle ecosystems and smart cities", "c": ["A2A protocols", "ML traffic mgmt", "Agent discovery/reg", "Other AI/agent"]}


draft_name: draft-ietf-mailmaint-pacc
prompt_hash: 0aa2b37cb22cee2c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:21.720412+00:00
response_json:
{"name": "draft-ietf-mailmaint-pacc", "s": "Specifies automatic configuration mechanism for email, calendar, and contact applications. Service providers publish standardized configuration that user agents retrieve for simplified setup.", "n": 2, "nn": "Incremental improvement to existing email configuration approaches", "m": 4, "mn": "Mature specification with detailed protocol definition and good structure", "o": 4, "on": "Significant overlap with existing autoconfiguration mechanisms like Thunderbird's", "mo": 2, "mon": "Limited momentum as email configuration is not a high-priority problem", "r": 2, "rn": "Low relevance to AI/agent systems, traditional email automation", "c": ["Data formats/interop"]}


draft_name: draft-a2a-moqt-transport
prompt_hash: 28e9f988d065eea1
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:21.731069+00:00
response_json:
{"name": "draft-a2a-moqt-transport", "s": "Specifies transport of Agent-to-Agent protocol over Media over QUIC Transport. Leverages MOQT's publish/subscribe model for real-time AI agent communication.", "n": 4, "nn": "Creative application of media transport protocol for AI agent communication", "m": 2, "mn": "Early stage specification, lacks implementation details and validation", "o": 5, "on": "Identical to draft-nandakumar-a2a-moqt-transport", "mo": 3, "mon": "Growing interest in A2A protocols but MOQT adoption for non-media unclear", "r": 4, "rn": "Highly relevant for real-time agent communication infrastructure", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-nandakumar-a2a-moqt-transport
prompt_hash: e6e7a254c41a22ce
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:21.740989+00:00
response_json:
{"name": "draft-nandakumar-a2a-moqt-transport", "s": "Identical specification to draft-a2a-moqt-transport for transporting Agent-to-Agent protocol over MOQT. Appears to be duplicate submission with different author.", "n": 4, "nn": "Same novel approach as duplicate draft", "m": 2, "mn": "Early stage, identical content suggests coordination issues between authors", "o": 5, "on": "Complete duplication of draft-a2a-moqt-transport", "mo": 2, "mon": "Duplicate submission reduces momentum and creates confusion", "r": 4, "rn": "Same high relevance but undermined by duplication issue", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-ietf-sml-trust
prompt_hash: c39539da88c084ab
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:41.854536+00:00
response_json:
{"name": "draft-ietf-sml-trust", "s": "Provides trust and security recommendations for handling structured data in email messages. Addresses security considerations for message user agents processing structured email content.", "n": 3, "nn": "Incremental security guidance for existing structured email approaches", "m": 4, "mn": "IETF working group draft with established discussion venue and GitHub repo", "o": 2, "on": "Some overlap with general email security but focused on structured data", "mo": 4, "mon": "Active IETF working group with clear development process", "r": 3, "rn": "Relevant for email systems but limited AI/agent focus", "c": ["Data formats/interop", "AI safety/alignment"]}


draft_name: draft-zhang-rvp-problem-statement
prompt_hash: be03f95771bbd3bb
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:41.877011+00:00
response_json:
{"name": "draft-zhang-rvp-problem-statement", "s": "Proposes Real-Virtual Agent Protocol for coordinating physical entities with digital agents through unified identity management. Targets manufacturing, smart cities, and human-AI collaborative environments.", "n": 4, "nn": "Novel approach to physical-digital agent coordination with composite identity", "m": 2, "mn": "Problem statement stage, lacks implementation details and deployment experience", "o": 3, "on": "Some overlap with IoT and agent protocols but unique physical-digital focus", "mo": 2, "mon": "Individual submission without clear standardization momentum", "r": 5, "rn": "Highly relevant for embodied AI and physical-digital agent coordination", "c": ["A2A protocols", "Agent identity/auth", "Autonomous netops"]}


draft_name: draft-mao-rtgwg-apn-framework-for-ioa
prompt_hash: 41c538fc37ac0c06
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:41.887033+00:00
response_json:
{"name": "draft-mao-rtgwg-apn-framework-for-ioa", "s": "Applies Application-aware Performance Network framework to Internet of Agents scenario. Addresses network service requirements for AI agent interactions across different platforms.", "n": 3, "nn": "Applies existing APN framework to new IoA use case", "m": 3, "mn": "Framework-level document with some technical detail but limited implementation", "o": 4, "on": "Heavy overlap with existing APN work, incremental IoA application", "mo": 3, "mon": "Routing working group context provides some momentum", "r": 4, "rn": "Relevant for agent network performance and quality of service", "c": ["ML traffic mgmt", "A2A protocols", "Agent discovery/reg"]}


draft_name: draft-zeng-opsawg-llm-netconf-gap
prompt_hash: 008f9ba07a092b0d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:41.896842+00:00
response_json:
{"name": "draft-zeng-opsawg-llm-netconf-gap", "s": "Analyzes gaps in existing network configuration protocols for LLM-driven intent-based networking. Identifies extension points for NETCONF, RESTCONF, gNMI, MCP, and A2A protocols.", "n": 4, "nn": "First systematic analysis of protocol gaps for LLM-driven network operations", "m": 3, "mn": "Good analysis depth but early stage without concrete solutions", "o": 2, "on": "Unique focus on LLM-network protocol integration gaps", "mo": 3, "mon": "Operations working group submission with clear problem focus", "r": 5, "rn": "Highly relevant for AI-driven network management evolution", "c": ["Autonomous netops", "A2A protocols", "Data formats/interop"]}


draft_name: draft-zeng-opsawg-applicability-mcp-a2a
prompt_hash: f7ff848c0e6fbe25
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:20:41.911684+00:00
response_json:
{"name": "draft-zeng-opsawg-applicability-mcp-a2a", "s": "Analyzes NETCONF limitations for advanced scenarios and proposes MCP and A2A protocols as complementary solutions. Provides implementation guidance and coexistence models.", "n": 3, "nn": "Practical applicability analysis but builds on existing protocol concepts", "m": 4, "mn": "Detailed implementation guidance with coexistence models shows maturity", "o": 3, "on": "Some overlap with existing NETCONF extensions but unique multi-protocol approach", "mo": 3, "mon": "Operations working group context with practical implementation focus", "r": 4, "rn": "Relevant for advanced network management and agent integration", "c": ["Autonomous netops", "A2A protocols", "Data formats/interop"]}


draft_name: draft-liu-saag-zt-problem-statement
prompt_hash: 46b1269509f42fda
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:00.798726+00:00
response_json:
{"name": "draft-liu-saag-zt-problem-statement", "s": "Identifies the need for standardized zero trust interoperability protocols in IETF. Proposes framework for multi-vendor zero trust environments moving beyond existing architectural guidance.", "n": 2, "nn": "Zero trust concepts well-established, but interoperability focus has merit", "m": 2, "mn": "Problem statement stage with numerous typos and formatting issues", "o": 3, "on": "Overlaps with existing zero trust and network security work", "mo": 2, "mon": "Early draft with basic problem identification, unclear community support", "r": 3, "rn": "Zero trust relevant to AI agents but not AI-specific focus", "c": ["Policy/governance", "Agent identity/auth"]}


draft_name: draft-akhavain-moussa-ai-network
prompt_hash: c0fd8bab4d5c2d6b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:00.820428+00:00
response_json:
{"name": "draft-akhavain-moussa-ai-network", "s": "Proposes Data and Agent Aware-Inference and Training Network (DA-ITN) architecture. Comprehensive multi-plane network design for AI training, inference, and agent interactions.", "n": 4, "nn": "Novel unified architecture specifically designed for AI network requirements", "m": 3, "mn": "Detailed 37-page specification but very early draft stage", "o": 2, "on": "Limited overlap with existing networking protocols, AI-focused approach", "mo": 3, "mon": "Substantial technical content suggests serious effort, needs community validation", "r": 5, "rn": "Directly addresses core AI networking infrastructure needs", "c": ["A2A protocols", "ML traffic mgmt", "Model serving/inference", "Data formats/interop"]}


draft_name: draft-aylward-aiga-1
prompt_hash: cdf484ce50d62e5c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:00.833237+00:00
response_json:
{"name": "draft-aylward-aiga-1", "s": "Specifies AI Governance and Accountability Protocol with tiered risk-based governance model. Includes immutable kernel architecture and federated authority network for AI agent oversight.", "n": 4, "nn": "Comprehensive governance protocol specifically for autonomous AI agents", "m": 4, "mn": "Well-structured protocol specification with detailed mechanisms", "o": 2, "on": "Novel AI governance approach, limited overlap with existing protocols", "mo": 4, "mon": "Detailed technical specification suggests strong development momentum", "r": 5, "rn": "Critical for AI agent deployment in networked environments", "c": ["Policy/governance", "AI safety/alignment", "Agent identity/auth"]}


draft_name: draft-li-semantic-routing-architecture
prompt_hash: 1c649aa1ae701d93
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:00.845382+00:00
response_json:
{"name": "draft-li-semantic-routing-architecture", "s": "Introduces semantic routing architecture using intent vectors and trust scores for AI agent communication. Moves beyond traditional IP routing to application-layer semantic decisions.", "n": 4, "nn": "Novel semantic-driven routing paradigm for AI agent networks", "m": 3, "mn": "Clear architecture description but implementation details needed", "o": 2, "on": "Distinct from traditional routing protocols, AI agent specific", "mo": 3, "mon": "Solid technical foundation, needs broader community engagement", "r": 4, "rn": "Addresses key challenge of intelligent agent communication routing", "c": ["A2A protocols", "Autonomous netops", "Agent discovery/reg"]}


draft_name: draft-wendt-stir-vesper
prompt_hash: 4d682dba4508a338
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:00.857803+00:00
response_json:
{"name": "draft-wendt-stir-vesper", "s": "Formalizes framework for verifiable telephone number identity using delegate certificates and authority tokens. Extends existing STIR/SHAKEN work with transparency mechanisms and rich call data support.", "n": 3, "nn": "Evolution of existing STIR work with verifiable transparency elements", "m": 4, "mn": "Mature technical specification building on established protocols", "o": 4, "on": "Heavy overlap with existing STIR/SHAKEN and certificate transparency work", "mo": 4, "mon": "Strong technical detail and builds on author's established work", "r": 2, "rn": "Telephony-focused, limited relevance to AI agent networking", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-jurkovikj-collab-tunnel
prompt_hash: 80fa6171748c890c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:22.720553+00:00
response_json:
{"name": "draft-jurkovikj-collab-tunnel", "s": "Defines an HTTP-based protocol for efficient delivery of web content to automated agents using bidirectional URL discovery and content fingerprinting. Focuses on bandwidth reduction while preserving canonical URLs through conditional requests and ETags.", "n": 3, "nn": "Novel combination of bidirectional discovery and template-invariant fingerprinting, but builds on established HTTP caching concepts", "m": 2, "mn": "Early stage with limited implementation details and unclear real-world validation", "o": 2, "on": "Some overlap with web caching and content delivery protocols but unique agent-focused approach", "mo": 2, "mon": "Single author draft with no clear industry backing or implementation momentum", "r": 3, "rn": "Addresses legitimate need for efficient agent-web interaction but limited scope compared to broader AI agent challenges", "c": ["Data formats/interop", "Human-agent interaction"]}


draft_name: draft-meyerzuselha-oauth-web-message-response-mode
prompt_hash: 0f6a13e9d5d02f89
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:22.753218+00:00
response_json:
{"name": "draft-meyerzuselha-oauth-web-message-response-mode", "s": "Extends OAuth 2.0 with a web message response mode using postMessage API for popup and iframe-based authorization flows. Targets browser-based applications needing secondary window authorization.", "n": 2, "nn": "Incremental extension to existing OAuth 2.0 framework using well-established postMessage patterns", "m": 4, "mn": "Well-defined specification building on mature OAuth 2.0 foundation with clear implementation path", "o": 4, "on": "Significant overlap with existing OAuth 2.0 response modes and browser-based authentication flows", "mo": 3, "mon": "Addresses practical OAuth implementation need but limited to specific use case", "r": 2, "rn": "Relevant to AI agents requiring web-based authentication but not AI-specific innovation", "c": ["Agent identity/auth", "Human-agent interaction"]}


draft_name: draft-rosenberg-aiproto-a2t
prompt_hash: 95ff1abd634edbe9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:22.767550+00:00
response_json:
{"name": "draft-rosenberg-aiproto-a2t", "s": "Defines Agent-to-Tool (A2T) protocol for integrating third-party APIs into AI agent operations. Provides enumeration and invocation APIs to reduce integration complexity for enterprise AI agents.", "n": 4, "nn": "Novel standardization of AI agent-tool integration with focus on enterprise API consumption", "m": 3, "mn": "Solid conceptual foundation but needs more implementation details and real-world validation", "o": 2, "on": "Some conceptual overlap with API gateway patterns but unique AI agent focus", "mo": 3, "mon": "Addresses clear enterprise need with potential for industry adoption", "r": 5, "rn": "Highly relevant to AI agent ecosystem development and enterprise integration challenges", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-mvieuille-kerpass-ephemsec
prompt_hash: 828e2bacb8c7ecbe
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:22.779336+00:00
response_json:
{"name": "draft-mvieuille-kerpass-ephemsec", "s": "Specifies EPHEMSEC algorithm for generating one-time passwords using public key cryptography instead of shared secrets. Includes context binding for phishing resistance and built-in time synchronization.", "n": 4, "nn": "Innovative approach to OTP generation with public key cryptography and context binding features", "m": 3, "mn": "Detailed algorithm specification but needs broader security analysis and implementation testing", "o": 3, "on": "Overlaps with existing OTP algorithms but introduces novel public key approach", "mo": 2, "mon": "Single author with limited industry validation or adoption signals", "r": 3, "rn": "Relevant to AI agent authentication but not specifically designed for agent use cases", "c": ["Agent identity/auth", "AI safety/alignment"]}


draft_name: draft-narajala-ans
prompt_hash: 9fd92a96e9b0e820
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:22.790230+00:00
response_json:
{"name": "draft-narajala-ans", "s": "Introduces Agent Name Service (ANS) as a DNS-based universal directory for AI agent discovery and verification. Uses PKI certificates for agent identity and supports multiple communication protocols through adapter layers.", "n": 5, "nn": "Comprehensive novel architecture addressing fundamental AI agent discovery and trust challenges", "m": 3, "mn": "Well-structured specification but complex system requiring significant implementation and deployment effort", "o": 2, "on": "Some overlap with DNS and PKI concepts but unique application to AI agent ecosystem", "mo": 3, "mon": "Addresses critical infrastructure need with potential for broad adoption if implementation challenges are overcome", "r": 5, "rn": "Extremely relevant as foundational infrastructure for multi-agent systems and AI agent interoperability", "c": ["Agent discovery/reg", "Agent identity/auth", "A2A protocols", "Data formats/interop"]}


draft_name: draft-ietf-httpbis-layered-cookies
prompt_hash: 7daa81a0b67bb866
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:40.629800+00:00
response_json:
{"name": "draft-ietf-httpbis-layered-cookies", "s": "Updates HTTP cookie specification replacing RFC 6265. Maintains existing widely-deployed cookie functionality while addressing historical security and privacy issues.", "n": 2, "nn": "Incremental improvement to existing standard rather than new functionality", "m": 5, "mn": "IETF working group draft with 46 pages of detailed specification", "o": 5, "on": "Direct replacement/update of existing RFC 6265", "mo": 4, "mon": "Active IETF working group with clear standardization path", "r": 2, "rn": "Traditional web technology, limited relevance to AI/agent systems", "c": ["Other AI/agent"]}


draft_name: draft-ainp-protocol
prompt_hash: d93f724538ef34a8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:40.651328+00:00
response_json:
{"name": "draft-ainp-protocol", "s": "Defines semantic communication protocol for AI agents using intent-based routing and negotiation. Replaces location-based networking with capability-based agent discovery.", "n": 5, "nn": "Novel semantic routing and intent exchange paradigm for AI agents", "m": 2, "mn": "Early version 0.1 specification with only 17 pages of detail", "o": 1, "on": "Unique approach to AI agent communication protocols", "mo": 2, "mon": "Individual submission without clear working group adoption", "r": 5, "rn": "Directly addresses core AI agent networking and communication needs", "c": ["A2A protocols", "Agent discovery/reg"]}


draft_name: draft-gaikwad-south-authorization
prompt_hash: 04c1010e699b50ef
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:40.660431+00:00
response_json:
{"name": "draft-gaikwad-south-authorization", "s": "Authorization protocol supporting probabilistic decisions for agents and services. Enables uncertainty and contextual factors in access control decisions.", "n": 4, "nn": "Stochastic authorization decisions are novel for network protocols", "m": 4, "mn": "Well-developed 44-page specification with HTTP binding", "o": 2, "on": "Extends existing auth patterns but adds unique probabilistic element", "mo": 2, "mon": "Individual submission, unclear adoption trajectory", "r": 4, "rn": "Addresses agent authorization needs with uncertainty handling", "c": ["Agent identity/auth", "Policy/governance"]}


draft_name: draft-gaikwad-aps-profile
prompt_hash: 98f863ae56f698f7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:40.672317+00:00
response_json:
{"name": "draft-gaikwad-aps-profile", "s": "Storage service profile for agent persistent state including embeddings, preferences, and audit logs. Addresses compliance and performance needs for AI agent storage.", "n": 4, "nn": "First standardization attempt for AI agent-specific storage requirements", "m": 3, "mn": "Detailed experimental specification with Kubernetes integration", "o": 1, "on": "Novel focus on agent-specific storage class requirements", "mo": 2, "mon": "Individual experimental draft seeking feedback", "r": 4, "rn": "Addresses critical infrastructure needs for persistent AI agents", "c": ["Data formats/interop", "Policy/governance"]}


draft_name: draft-williams-http-bearer-extension
prompt_hash: d53dbe6a1f3c548e
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:21:40.682011+00:00
response_json:
{"name": "draft-williams-http-bearer-extension", "s": "Improves HTTP Bearer authentication with automatic token fetching from STS. Eliminates need for PKCE and simplifies user-agent token management.", "n": 3, "nn": "Incremental improvement to existing Bearer auth with automation", "m": 3, "mn": "Focused 16-page specification with clear HTTP integration", "o": 3, "on": "Extends existing Bearer auth and OIDC patterns", "mo": 2, "mon": "Individual submission without clear working group support", "r": 3, "rn": "Relevant for agent authentication but primarily traditional web auth", "c": ["Agent identity/auth"]}


draft_name: draft-schulze-ecap
prompt_hash: a3341763aca081df
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:01.623235+00:00
response_json:
{"name": "draft-schulze-ecap", "s": "ECAP defines a cryptographically-verified protocol for web crawlers to obtain consent from hosts before accessing resources. It replaces voluntary robots.txt with mandatory consent-based access using signatures and policy handshakes.", "n": 4, "nn": "Novel approach to making web crawling consent mandatory rather than voluntary, using crypto verification", "m": 3, "mn": "Basic protocol structure defined but likely needs more detail on implementation and edge cases", "o": 2, "on": "Some conceptual overlap with robots.txt but fundamentally different approach with crypto verification", "mo": 4, "mon": "High relevance to current AI scraping debates and web consent issues", "r": 5, "rn": "Extremely relevant to current controversies around AI training data collection and web scraping ethics", "c": ["Policy/governance", "Agent identity/auth", "AI safety/alignment"]}


draft_name: draft-li-dmsc-mcps-agw
prompt_hash: 69f90ac0ecd83fca
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:01.644436+00:00
response_json:
{"name": "draft-li-dmsc-mcps-agw", "s": "Defines a protocol suite using Agent Gateways as control-plane entities for multi-agent collaboration. Enables agent registration, authentication, capability management and semantic routing while preserving P2P interactions.", "n": 4, "nn": "Gateway-based architecture for agent collaboration is a solid architectural approach", "m": 3, "mn": "Good architectural foundation but likely needs more protocol detail for full implementation", "o": 4, "on": "Significant overlap with other agent collaboration drafts, particularly draft-liu-dmsc-acps-arc", "mo": 3, "mon": "Part of emerging multi-agent collaboration standardization efforts", "r": 4, "rn": "Highly relevant as multi-agent systems become more prevalent in distributed computing", "c": ["A2A protocols", "Agent discovery/reg", "Agent identity/auth"]}


draft_name: draft-romanchuk-normative-admissibility
prompt_hash: bb6299441e80165f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:01.654563+00:00
response_json:
{"name": "draft-romanchuk-normative-admissibility", "s": "Establishes a framework for evaluating whether autonomous agent speech acts are admissible based on modality and grounding state. Focuses on deterministic evaluation without requiring semantic truth verification.", "n": 5, "nn": "Highly novel approach to agent communication validation using speech act theory and formal logic", "m": 2, "mn": "Theoretical framework is well-developed but practical implementation details are unclear", "o": 1, "on": "Unique approach not seen in other agent protocol drafts", "mo": 2, "mon": "Specialized academic approach may have limited industry adoption momentum", "r": 3, "rn": "Relevant for agent safety and verification but may be too theoretical for immediate practical use", "c": ["AI safety/alignment", "A2A protocols", "Policy/governance"]}


draft_name: draft-hackett-ures
prompt_hash: a17827a8f62741d7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:01.665593+00:00
response_json:
{"name": "draft-hackett-ures", "s": "Specifies requirements for uniform HTML email rendering across mail clients, addressing inconsistencies in HTML/CSS interpretation. Covers dark mode, embedded assets, positioning, and secure SVG rendering while maintaining MIME compatibility.", "n": 2, "nn": "Addresses known email rendering problems but approach is incremental rather than novel", "m": 4, "mn": "Well-developed specification with clear requirements and backwards compatibility considerations", "o": 2, "on": "Some overlap with existing email standards but addresses specific rendering gaps", "mo": 3, "mon": "Addresses real industry pain points which could drive adoption", "r": 2, "rn": "Not directly AI/agent related, more focused on traditional email client interoperability", "c": ["Data formats/interop", "Other AI/agent"]}


draft_name: draft-liu-dmsc-acps-arc
prompt_hash: 86fdbc8dc8d3bb7f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:01.675717+00:00
response_json:
{"name": "draft-liu-dmsc-acps-arc", "s": "Proposes Agent Collaboration Protocols architecture for Internet of Agents, covering agent lifecycle from access to collaboration. Includes trusted registration, authentication, discovery, interaction, and monitoring components.", "n": 3, "nn": "Comprehensive agent collaboration architecture but builds on established distributed systems concepts", "m": 3, "mn": "Good architectural overview but needs more detailed protocol specifications", "o": 4, "on": "Heavy overlap with draft-li-dmsc-mcps-agw and similar multi-agent collaboration efforts", "mo": 4, "mon": "Strong momentum as part of broader Internet of Agents standardization push", "r": 5, "rn": "Highly relevant for future large-scale agent deployments and IoA infrastructure", "c": ["A2A protocols", "Agent discovery/reg", "Agent identity/auth", "Autonomous netops"]}


draft_name: draft-vandoulas-aidp
prompt_hash: a96cd5aa0a8654d7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:22.105182+00:00
response_json:
{"name": "draft-vandoulas-aidp", "s": "Defines a comprehensive control-plane protocol for secure agent interactions with delegation, authority enforcement, and cross-domain interoperability. Addresses core infrastructure needs for multi-agent systems with auditable execution binding.", "n": 4, "nn": "Novel integration of intent expression, capability delegation, and execution result binding in single protocol", "m": 3, "mn": "Well-structured but lacks implementation details and security analysis depth", "o": 2, "on": "Some overlap with general agent communication but unique delegation focus", "mo": 3, "mon": "Addresses clear industry need but no implementation indicators mentioned", "r": 4, "rn": "Highly relevant as foundational infrastructure for enterprise agent deployments", "c": ["A2A protocols", "Agent identity/auth", "Policy/governance"]}


draft_name: draft-mallick-muacp
prompt_hash: 4a84557821e5a8f8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:22.131586+00:00
response_json:
{"name": "draft-mallick-muacp", "s": "Resource-efficient messaging protocol specifically designed for constrained IoT/Edge devices with deterministic bounds. Provides concrete technical specifications with OSCORE security integration.", "n": 4, "nn": "First protocol addressing resource constraints with specific bounds for agent communication", "m": 4, "mn": "Detailed technical specifications with clear resource bounds and security binding", "o": 2, "on": "Unique focus on resource-constrained environments distinguishes from general protocols", "mo": 4, "mon": "Strong technical foundation and clear market need for IoT agent communication", "r": 5, "rn": "Critical for IoT/Edge AI deployment which is rapidly expanding market segment", "c": ["A2A protocols", "Data formats/interop"]}


draft_name: draft-gaikwad-llm-benchmarking-terminology
prompt_hash: c759a5ce8c0a37e4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:22.144025+00:00
response_json:
{"name": "draft-gaikwad-llm-benchmarking-terminology", "s": "Establishes standardized terminology for LLM serving performance metrics across different system types. Focuses purely on vocabulary definition without prescribing methodologies.", "n": 2, "nn": "Terminology standardization is incremental but necessary foundational work", "m": 3, "mn": "Comprehensive terminology coverage but limited technical depth as terminology-only document", "o": 3, "on": "Some overlap with general performance measurement standards but LLM-specific", "mo": 3, "mon": "Industry need exists but terminology docs typically have lower adoption momentum", "r": 3, "rn": "Useful for industry standardization but indirect impact on technical deployment", "c": ["Model serving/inference", "Data formats/interop"]}


draft_name: draft-wolfe-faf-format
prompt_hash: eef7802783b12ea7
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:22.154336+00:00
response_json:
{"name": "draft-wolfe-faf-format", "s": "YAML-based format for sharing software project context with AI development tools. Addresses context fragmentation in multi-agent development environments.", "n": 3, "nn": "Specific application to AI development tools is novel though format approach is conventional", "m": 2, "mn": "Brief specification lacks detailed schema and implementation guidance", "o": 4, "on": "Similar to existing project metadata formats but AI-specific features", "mo": 2, "mon": "IANA registration shows some traction but limited technical depth may hinder adoption", "r": 3, "rn": "Relevant to developer tooling but narrow use case limits broader impact", "c": ["Data formats/interop", "Human-agent interaction"]}


draft_name: draft-aylward-aiga-2
prompt_hash: 6154ac85d12a1ea6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:22.172373+00:00
response_json:
{"name": "draft-aylward-aiga-2", "s": "Comprehensive AI governance framework with tiered risk model, federated authority network, and economic incentive alignment. Includes advanced security mechanisms for high-assurance scenarios.", "n": 5, "nn": "Highly novel integration of technical enforcement, economic incentives, and federated governance", "m": 3, "mn": "Ambitious scope with detailed mechanisms but implementation complexity may be challenging", "o": 1, "on": "Unique comprehensive approach to AI governance with technical enforcement", "mo": 4, "mon": "Addresses critical regulatory and safety concerns with strong technical foundation", "r": 5, "rn": "Extremely relevant given increasing focus on AI safety and regulatory compliance", "c": ["AI safety/alignment", "Policy/governance", "Agent identity/auth"]}


draft_name: draft-yang-dmsc-ioa-task-protocol
prompt_hash: cee7eac6648a0be3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:42.876124+00:00
response_json:
{"name": "draft-yang-dmsc-ioa-task-protocol", "s": "Defines a protocol for distributed collaboration among heterogeneous AI agents, enabling dynamic team formation and task coordination. Targets large-scale scenarios like intelligent transportation and smart healthcare across diverse network environments.", "n": 3, "nn": "Reasonable novelty in agent task coordination, but builds on known distributed systems concepts", "m": 2, "mn": "Early stage with basic protocol definition, lacks implementation details and security considerations", "o": 4, "on": "Significant overlap with other IoA drafts in this set, particularly the semantic interaction draft", "mo": 3, "mon": "Part of emerging IoA standardization effort but unclear industry backing", "r": 4, "rn": "Highly relevant to growing AI agent ecosystem and multi-agent systems deployment", "c": ["A2A protocols", "Agent discovery/reg", "Autonomous netops"]}


draft_name: draft-zhul-dhc-bnc-up-specific-suboption
prompt_hash: 104203ea8e5d2739
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:42.900000+00:00
response_json:
{"name": "draft-zhul-dhc-bnc-up-specific-suboption", "s": "Defines a DHCP relay agent suboption for broadband networks to include UP-specific information. Ensures subscribers in the same SGRP under the same UP get IP addresses from the same address space.", "n": 2, "nn": "Incremental extension to existing DHCP relay mechanisms for specific broadband use case", "m": 4, "mn": "Well-defined technical specification with clear implementation guidance", "o": 1, "on": "Unique DHCP extension, no significant overlap with other drafts", "mo": 2, "mon": "Narrow telecom-specific use case with limited broader appeal", "r": 2, "rn": "Relevant to broadband operators but limited connection to AI/agent themes", "c": ["Other AI/agent"]}


draft_name: draft-aap-oauth-profile
prompt_hash: 944438422cd86b02
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:42.912413+00:00
response_json:
{"name": "draft-aap-oauth-profile", "s": "Defines an OAuth 2.0 authorization profile specifically for autonomous AI agents, extending existing standards with structured claims for agent identity and context. Enables context-aware, auditable authorization in agent-to-API scenarios.", "n": 4, "nn": "Novel application of OAuth to AI agents with thoughtful extensions for autonomous systems", "m": 4, "mn": "Comprehensive 83-page specification with detailed technical mechanisms", "o": 2, "on": "Some conceptual overlap with agent identity themes but distinct OAuth focus", "mo": 4, "mon": "Strong relevance to enterprise AI deployment and security concerns", "r": 5, "rn": "Extremely relevant to current AI agent security and authorization challenges", "c": ["Agent identity/auth", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-zhang-dmsc-ioa-semantic-interaction
prompt_hash: d91862666a01f724
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:42.927377+00:00
response_json:
{"name": "draft-zhang-dmsc-ioa-semantic-interaction", "s": "Specifies a semantic layer for Internet of Agents using ontology models and JSON-LD serialization. Defines common vocabulary and negotiation procedures for deterministic semantic interoperability across agent domains.", "n": 3, "nn": "Applies semantic web technologies to agent interaction, moderately novel combination", "m": 3, "mn": "Reasonable technical depth but semantic alignment challenges remain complex", "o": 4, "on": "Heavy overlap with IoA task protocol draft, both targeting agent interoperability", "mo": 3, "mon": "Part of broader IoA effort but semantic web adoption in agents unclear", "r": 4, "rn": "Important for agent interoperability but semantic standardization faces adoption challenges", "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"]}


draft_name: draft-sun-zhang-iaip
prompt_hash: 76a614473ebbaec9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:22:42.937133+00:00
response_json:
{"name": "draft-sun-zhang-iaip", "s": "Defines Intent-based Agent Interconnection Protocol for Agent Gateways, focusing on semantic intent rather than network addressing. Specifies agent registration, capability advertisement, and intent-based routing mechanisms.", "n": 3, "nn": "Intent-based approach to agent interconnection shows reasonable novelty", "m": 3, "mn": "Decent technical specification though gateway architecture needs more detail", "o": 4, "on": "Substantial overlap with other IoA drafts, particularly in agent discovery and registration", "mo": 3, "mon": "Part of emerging agent infrastructure standards but adoption path unclear", "r": 4, "rn": "Relevant to agent infrastructure but intent-based networking adoption still emerging", "c": ["A2A protocols", "Agent discovery/reg", "Autonomous netops"]}


draft_name: draft-verma-dmsc-nlip-notes
prompt_hash: 08aee0b59363765a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:02.961716+00:00
response_json:
{"name": "draft-verma-dmsc-nlip-notes", "s": "Proposes using generative AI to create flexible communication protocols for agent-to-agent interactions, replacing strict APIs with natural language-based communication. Aims to solve API explosion and interoperability challenges through a uniform AI-mediated interface.", "n": 3, "nn": "Natural language for agent communication is novel but conceptually straightforward", "m": 2, "mn": "Very early stage with limited technical detail and no concrete protocol specification", "o": 2, "on": "Some overlap with other agent communication drafts but unique NL approach", "mo": 2, "mon": "Single author, short document suggests limited community engagement", "r": 3, "rn": "Addresses real interoperability problems but approach may be premature", "c": ["A2A protocols", "Human-agent interaction", "Data formats/interop"]}


draft_name: draft-zhul-intarea-bnc-up-specific-suboption
prompt_hash: 0610a2e30889ae7d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:02.982792+00:00
response_json:
{"name": "draft-zhul-intarea-bnc-up-specific-suboption", "s": "Defines a DHCP relay agent suboption for broadband networks to include UP-specific information. Ensures subscribers in the same SGRP under the same UP get IP addresses from consistent address spaces.", "n": 2, "nn": "Standard DHCP extension with conventional approach", "m": 4, "mn": "Well-defined technical specification with clear implementation path", "o": 1, "on": "Specific to broadband DHCP scenarios, minimal overlap", "mo": 3, "mon": "Addresses specific industry need but narrow scope", "r": 2, "rn": "Limited to broadband network scenarios, not broadly applicable to AI/agents", "c": ["Other AI/agent"]}


draft_name: draft-berlinai-vera
prompt_hash: a91ea25ae427bebf
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:02.992729+00:00
response_json:
{"name": "draft-berlinai-vera", "s": "Introduces VERA, a zero-trust architecture for AI agent security with five enforcement pillars and cryptographic proof-based autonomy. Provides structured threat model and security properties for runtime agent verification.", "n": 4, "nn": "Comprehensive zero-trust approach to AI agent security is quite novel", "m": 3, "mn": "Good architectural framework but needs more implementation details", "o": 2, "on": "Some conceptual overlap with agent identity/auth but unique approach", "mo": 3, "mon": "Addresses critical security concerns with structured approach", "r": 5, "rn": "Highly relevant to AI agent deployment security concerns", "c": ["AI safety/alignment", "Agent identity/auth", "Policy/governance"]}


draft_name: draft-li-dmsc-macp
prompt_hash: 3fa11c9f49e0ff8b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:03.002072+00:00
response_json:
{"name": "draft-li-dmsc-macp", "s": "Specifies a comprehensive multi-agent collaboration protocol suite using Agent Gateways for registration, authentication, and capability management. Enables scalable semantic interactions among distributed agents across heterogeneous networks.", "n": 4, "nn": "Comprehensive protocol suite with gateway architecture is well-conceived", "m": 4, "mn": "Substantial 21-page specification with detailed protocol design", "o": 3, "on": "Overlaps with other agent communication protocols but more comprehensive", "mo": 4, "mon": "Large document suggests significant development effort and potential industry interest", "r": 5, "rn": "Addresses core multi-agent collaboration needs with practical approach", "c": ["A2A protocols", "Agent discovery/reg", "Agent identity/auth", "Data formats/interop"]}


draft_name: draft-zeng-nmrg-mcp-usecases-requirements
prompt_hash: 6fe840433e50f3f5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:03.013570+00:00
response_json:
{"name": "draft-zeng-nmrg-mcp-usecases-requirements", "s": "Presents problem statement for integrating Model Context Protocol into network management for AI agents. Outlines use cases for troubleshooting, security, and optimization with functional and security requirements.", "n": 3, "nn": "Applying MCP to network management is a reasonable extension", "m": 3, "mn": "Good requirements document but needs follow-up protocol work", "o": 2, "on": "Some overlap with network automation but MCP focus is distinctive", "mo": 3, "mon": "NMRG venue and structured approach suggests research community interest", "r": 4, "rn": "Very relevant to AI-driven network operations trend", "c": ["Autonomous netops", "Human-agent interaction", "Agent discovery/reg"]}


draft_name: draft-nederveld-adl
prompt_hash: f171f9007a148c6a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:24.056688+00:00
response_json:
{"name": "draft-nederveld-adl", "s": "Defines ADL, a JSON-based standard for describing AI agents including their capabilities, tools, permissions, and configuration. Enables agent discovery, interoperability, and lifecycle management across platforms.", "n": 4, "nn": "Novel standardized approach to agent description with comprehensive metadata coverage", "m": 3, "mn": "Well-structured spec but lacks implementation examples and ecosystem validation", "o": 2, "on": "Some overlap with agent identity/discovery concepts but unique in comprehensive agent description approach", "mo": 4, "mon": "Strong potential for adoption as foundational agent metadata standard", "r": 5, "rn": "Critical infrastructure piece for agent ecosystem interoperability and management", "c": ["Data formats/interop", "Agent discovery/reg", "A2A protocols"]}


draft_name: draft-tejido-swp-core
prompt_hash: 49842c46c95415c6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:24.082119+00:00
response_json:
{"name": "draft-tejido-swp-core", "s": "Specifies SlimWire Protocol Core, a binary framing layer for agent/tool messaging with profile-based extensibility. Provides transport-independent message boundaries and envelope encoding with security bindings.", "n": 4, "nn": "Novel binary framing approach optimized for agent messaging with strong conformance model", "m": 4, "mn": "Detailed technical specification with conformance testing and security considerations", "o": 2, "on": "Unique binary protocol approach, minimal overlap with other agent communication protocols", "mo": 3, "mon": "Technical merit is high but adoption may be limited by binary format complexity", "r": 4, "rn": "Addresses real need for efficient agent messaging but may face adoption challenges", "c": ["A2A protocols", "Data formats/interop"]}


draft_name: draft-drake-email-tpm-attestation
prompt_hash: 735308dfb097c525
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:24.099939+00:00
response_json:
{"name": "draft-drake-email-tpm-attestation", "s": "Defines hardware attestation for email using TPM verification chains to prevent spam and provide Sybil resistance. Includes privacy-preserving SD-JWT alternative and broader applicability to other protocols.", "n": 5, "nn": "Highly novel approach connecting hardware attestation to email authentication and AI-resistant spam prevention", "m": 4, "mn": "Comprehensive specification with both full attestation and privacy-preserving variants", "o": 1, "on": "Unique approach to hardware-based sender verification, no significant overlap", "mo": 4, "mon": "Addresses critical AI-era challenge of distinguishing human-controlled from automated systems", "r": 5, "rn": "Extremely relevant for AI era where traditional spam/authentication mechanisms may fail", "c": ["Agent identity/auth", "AI safety/alignment", "Human-agent interaction"]}


draft_name: draft-wang-hjs-accountability
prompt_hash: 491449a548c9570e
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:24.111190+00:00
response_json:
{"name": "draft-wang-hjs-accountability", "s": "Defines HJS accountability layer for AI agents using blockchain-anchored timestamps to create immutable responsibility chains. Provides primitives for judgment, delegation, termination, and verification with court-admissible evidence.", "n": 4, "nn": "Novel blockchain integration for AI agent accountability with legal framework consideration", "m": 2, "mn": "Brief specification lacking implementation details and integration examples", "o": 1, "on": "Unique blockchain-based accountability approach, no direct overlap with other drafts", "mo": 3, "mon": "Important problem space but may face adoption challenges due to blockchain dependency", "r": 4, "rn": "Addresses critical need for AI agent accountability and legal traceability", "c": ["Policy/governance", "AI safety/alignment", "A2A protocols"]}


draft_name: draft-ravikiran-clawdentity-protocol
prompt_hash: e4a7c0b35840b4d5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:24.120530+00:00
response_json:
{"name": "draft-ravikiran-clawdentity-protocol", "s": "Specifies Clawdentity protocol for cryptographic identity and trust in AI agent communication. Provides Ed25519 identity, registry credentials, pairing ceremonies, and authenticated relay transport.", "n": 3, "nn": "Solid but incremental approach to agent identity using established cryptographic primitives", "m": 4, "mn": "Comprehensive protocol specification with detailed security considerations and implementation guidance", "o": 3, "on": "Moderate overlap with general agent identity concepts but distinct in bilateral trust approach", "mo": 4, "mon": "Strong technical foundation and addresses fundamental need for agent-to-agent trust", "r": 5, "rn": "Essential infrastructure for secure agent communication and identity verification", "c": ["Agent identity/auth", "A2A protocols", "Data formats/interop"]}


draft_name: draft-messous-eat-ai
prompt_hash: bb8339e08e23fd81
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:48.635631+00:00
response_json:
{"name": "draft-messous-eat-ai", "s": "Defines an Entity Attestation Token profile for remote attestation of autonomous AI agents, specifying claims for model integrity, training data provenance, and inference policies. Extends EAT for AI-specific attestation needs within the IETF RATS architecture.", "n": 4, "nn": "Novel application of EAT to AI agent attestation with specific claims for model parameters and training data provenance", "m": 3, "mn": "Reasonable technical depth but could benefit from more implementation details and security analysis", "o": 2, "on": "Some overlap with general RATS work but AI-specific attestation claims are relatively unique", "mo": 3, "mon": "Addresses emerging need for AI agent trust but limited demonstrated industry adoption", "r": 4, "rn": "Highly relevant for trustworthy AI deployment and aligns with growing focus on AI safety and verification", "c": ["Agent identity/auth", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-mpsb-agntcy-messaging
prompt_hash: 44dfb38ad0382732
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:48.663462+00:00
response_json:
{"name": "draft-mpsb-agntcy-messaging", "s": "Analyzes messaging protocols for agentic AI systems, comparing AMQP, MQTT, NATS, Kafka and others across security and performance dimensions. Introduces AGNTCY SLIM as a purpose-built solution with MLS integration for quantum-safe agent communication.", "n": 3, "nn": "Useful comparative analysis but AGNTCY SLIM appears to be proprietary solution being promoted", "m": 2, "mn": "More of a survey document than a protocol specification; lacks detailed technical specifications", "o": 3, "on": "Overlaps with existing messaging protocol work and MLS standardization efforts", "mo": 2, "mon": "Unclear industry support for AGNTCY SLIM; appears vendor-driven", "r": 3, "rn": "Addresses real need for agent messaging but focuses heavily on promoting specific proprietary solution", "c": ["A2A protocols", "Data formats/interop", "Agent identity/auth"]}


draft_name: draft-mpsb-agntcy-slim
prompt_hash: 1c02110d1cf76a5d
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:48.674864+00:00
response_json:
{"name": "draft-mpsb-agntcy-slim", "s": "Specifies SLIM protocol for real-time interactive AI applications, combining gRPC over HTTP/2/3 with MLS for secure messaging. Designed as transport layer for agent protocols like A2A and MCP with native RPC semantics.", "n": 3, "nn": "Combines existing technologies (gRPC, MLS) in AI-specific way but limited fundamental innovation", "m": 3, "mn": "Good technical specification but builds heavily on existing protocols without clear differentiation", "o": 4, "on": "Significant overlap with gRPC, HTTP/2-3, and MLS work; incremental addition for AI use case", "mo": 2, "mon": "Appears vendor-driven with limited broader community engagement", "r": 3, "rn": "Relevant for agent communication but unclear advantage over existing gRPC+MLS combinations", "c": ["A2A protocols", "Data formats/interop", "Agent identity/auth"]}


draft_name: draft-barney-caam
prompt_hash: 66fd5f44b97f1865
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:48.684770+00:00
response_json:
{"name": "draft-barney-caam", "s": "Specifies Contextual Agent Authorization Mesh for runtime authorization of agents after discovery, providing ReBAC and purpose-bound delegation. Integrates with ARDP, SPIFFE, and RATS for comprehensive agent authorization framework.", "n": 4, "nn": "Comprehensive authorization framework specifically designed for agent interactions with novel contextual authorization approach", "m": 4, "mn": "Detailed technical specification with good integration of multiple existing frameworks", "o": 3, "on": "Builds on existing identity and authorization work but creates novel composition for agent scenarios", "mo": 3, "mon": "References multiple existing frameworks suggesting some industry alignment", "r": 5, "rn": "Extremely relevant as authorization is critical for safe agent deployment and inter-agent interaction", "c": ["Agent identity/auth", "Policy/governance", "A2A protocols", "AI safety/alignment"]}


draft_name: draft-nennemann-wimse-ect
prompt_hash: ae7efed9b2ecbdc6
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:23:48.694917+00:00
response_json:
{"name": "draft-nennemann-wimse-ect", "s": "Defines Execution Context Tokens as JWT extension to WIMSE for tracking task execution in distributed agentic workflows. Creates DAG-linked execution records transported via new HTTP header alongside WIMSE identity headers.", "n": 4, "nn": "Novel approach to workflow execution tracking with cryptographic linking of task dependencies", "m": 4, "mn": "Well-specified extension to existing WIMSE work with clear technical details", "o": 2, "on": "Extends WIMSE but addresses unique workflow tracking problem not covered elsewhere", "mo": 4, "mon": "Builds on active WIMSE working group with established momentum", "r": 4, "rn": "Highly relevant for distributed agent workflows and auditability of agent task execution", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance", "Data formats/interop"]}


draft_name: draft-mw-spice-actor-chain
prompt_hash: abf63b9955fd09ec
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:09.625674+00:00
response_json:
{"name": "draft-mw-spice-actor-chain", "s": "Extends OAuth 2.0 Token Exchange with cryptographically verifiable actor chains to provide tamper-evident audit trails of delegation paths. Addresses security gaps in multi-hop service environments, particularly for AI agent-to-agent workloads vulnerable to prompt injection attacks.", "n": 4, "nn": "Novel approach to cryptographic delegation auditability in OAuth, specifically addressing AI agent prompt injection vulnerabilities", "m": 3, "mn": "Well-structured extension to established OAuth 2.0 framework with clear security motivations", "o": 2, "on": "Builds on OAuth 2.0 Token Exchange but addresses previously unaddressed delegation auditability gaps", "mo": 4, "mon": "High relevance given growing AI agent deployments and security concerns around delegation chains", "r": 5, "rn": "Directly addresses critical security needs for AI agent authentication and delegation tracking", "c": ["Agent identity/auth", "AI safety/alignment", "A2A protocols"]}


draft_name: draft-bradleylundberg-cfrg-arkg
prompt_hash: ee404b2663eb0235
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:09.641411+00:00
response_json:
{"name": "draft-bradleylundberg-cfrg-arkg", "s": "Defines Asynchronous Remote Key Generation algorithm enabling delegation of public key generation without private key access. Supports pseudonymous keys, enhanced forward secrecy, and paired device authentication scenarios.", "n": 4, "nn": "Novel cryptographic primitive for remote key generation with multiple practical applications", "m": 4, "mn": "Comprehensive specification with abstract algorithm, concrete instantiations, and formal treatment", "o": 2, "on": "Addresses unique cryptographic capability not covered by existing key generation standards", "mo": 3, "mon": "Solid cryptographic foundation with clear applications but may need broader adoption drivers", "r": 4, "rn": "Strong relevance for agent privacy, forward secrecy, and distributed authentication scenarios", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-ietf-roll-enrollment-priority
prompt_hash: 94fe7c469d02f20a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:09.661035+00:00
response_json:
{"name": "draft-ietf-roll-enrollment-priority", "s": "Provides mechanism for RPL Root to control enrollment announcements and adjust enrollment priorities in RPL networks. Extends existing RFC9032 enrollment proxy capabilities with centralized control.", "n": 2, "nn": "Incremental enhancement to existing RPL enrollment mechanisms", "m": 4, "mn": "Mature, focused specification building on established RPL standards", "o": 3, "on": "Direct extension of RFC9032 with some overlap in enrollment control mechanisms", "mo": 3, "mon": "Solid but incremental improvement to existing IoT networking capabilities", "r": 3, "rn": "Relevant for IoT agent enrollment scenarios but limited to RPL network contexts", "c": ["Agent discovery/reg", "Autonomous netops"]}


draft_name: draft-contario-totp-secure-enrollment
prompt_hash: 6bea74be3fd13ea8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:09.670996+00:00
response_json:
{"name": "draft-contario-totp-secure-enrollment", "s": "Extends TOTP enrollment to prevent key compromise through QR code capture or key persistence in external systems. Addresses common security vulnerabilities in current TOTP deployment practices.", "n": 3, "nn": "Practical security improvement to widely-used TOTP enrollment process", "m": 3, "mn": "Addresses real-world security concerns but builds incrementally on existing TOTP framework", "o": 2, "on": "Extends TOTP standard with minimal overlap to existing secure enrollment methods", "mo": 3, "mon": "Moderate interest given widespread TOTP usage but may face adoption challenges", "r": 3, "rn": "Relevant for agent authentication security but not AI/agent-specific", "c": ["Agent identity/auth", "AI safety/alignment"]}


draft_name: draft-liu-rtgwg-llmsync-multicast
prompt_hash: b61a74d99ee5f3d5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:09.681092+00:00
response_json:
{"name": "draft-liu-rtgwg-llmsync-multicast", "s": "Discusses multicast use cases for Large Language Model synchronization in inference cloud services. Very brief draft outlining potential applications for LLM deployment scenarios.", "n": 2, "nn": "Early exploration of multicast applications for LLM infrastructure", "m": 1, "mn": "Very early stage with minimal technical detail or concrete proposals", "o": 1, "on": "Unique focus on LLM-specific multicast applications", "mo": 2, "mon": "Limited momentum due to lack of technical depth and concrete solutions", "r": 3, "rn": "Relevant to ML infrastructure but needs substantial development to be actionable", "c": ["ML traffic mgmt", "Model serving/inference"]}


draft_name: draft-zhang-rtgwg-llmmoe-multicast
prompt_hash: 606c351e11f0f878
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:28.263649+00:00
response_json:
{"name": "draft-zhang-rtgwg-llmmoe-multicast", "s": "Analyzes multicast use cases in Large Language Model Mixture of Experts architectures, particularly for token dispatching. Attempts to identify networking opportunities in LLM MoE systems.", "n": 3, "nn": "Novel application of multicast to LLM MoE, but analysis appears preliminary", "m": 2, "mn": "Very early stage with limited technical depth at 7 pages", "o": 2, "on": "Some overlap with ML traffic management concepts but unique multicast focus", "mo": 2, "mon": "Recent draft but narrow scope may limit broader interest", "r": 3, "rn": "Relevant to networking optimization for LLM inference but very specific use case", "c": ["ML traffic mgmt", "Model serving/inference"]}


draft_name: draft-irtf-nmrg-llm-nm
prompt_hash: 52fd14dc3430462c
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:28.288157+00:00
response_json:
{"name": "draft-irtf-nmrg-llm-nm", "s": "Defines framework for collaborative network management between LLMs and human operators with human-in-the-loop oversight. Introduces telemetry modules and standardized interaction models.", "n": 4, "nn": "Good integration of human oversight with LLM automation in network management", "m": 3, "mn": "Moderate maturity with defined framework components and workflows", "o": 3, "on": "Overlaps with autonomous network operations but adds human-in-the-loop aspect", "mo": 3, "mon": "IRTF draft suggests research community interest but moderate momentum", "r": 4, "rn": "Highly relevant for practical LLM deployment in network operations", "c": ["Autonomous netops", "Human-agent interaction", "Data formats/interop"]}


draft_name: draft-liu-nmrg-ai-llm-inference-requirements
prompt_hash: f36ec8211ec82bee
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:28.302333+00:00
response_json:
{"name": "draft-liu-nmrg-ai-llm-inference-requirements", "s": "Analyzes system and network requirements for large-scale LLM inference services. Investigates mainstream inference frameworks and their network management challenges.", "n": 3, "nn": "Useful requirements analysis but builds on existing inference frameworks", "m": 3, "mn": "Good survey of existing systems with clear problem identification", "o": 4, "on": "Significant overlap with other LLM serving and inference optimization work", "mo": 3, "mon": "Recent and addresses important scaling challenges", "r": 4, "rn": "Very relevant for understanding LLM deployment requirements at scale", "c": ["Model serving/inference", "ML traffic mgmt"]}


draft_name: draft-gaikwad-llm-benchmarking-methodology
prompt_hash: a1ee0c7b283b446a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:28.314389+00:00
response_json:
{"name": "draft-gaikwad-llm-benchmarking-methodology", "s": "Defines comprehensive benchmarking methodologies for LLM inference serving systems including test procedures and measurement specifications. Companion to terminology document.", "n": 4, "nn": "Thorough methodology development for emerging LLM benchmarking needs", "m": 4, "mn": "Well-developed at 48 pages with detailed procedures and specifications", "o": 2, "on": "Part of series but methodology focus is relatively unique", "mo": 4, "mon": "Part of coordinated effort with multiple related drafts", "r": 5, "rn": "Critical for standardizing LLM performance evaluation across industry", "c": ["Model serving/inference", "Data formats/interop"]}


draft_name: draft-gaikwad-llm-benchmarking-profiles
prompt_hash: 8befd477e2a76b6f
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:28.335587+00:00
response_json:
{"name": "draft-gaikwad-llm-benchmarking-profiles", "s": "Defines performance benchmarking profiles binding terminology and methodology to concrete architectural roles and workload patterns. Specifies System Under Test boundaries and measurement points.", "n": 4, "nn": "Comprehensive profile definition for reproducible LLM benchmarking", "m": 4, "mn": "Highly mature at 53 pages with detailed architectural specifications", "o": 3, "on": "Builds directly on companion methodology and terminology documents", "mo": 4, "mon": "Strong momentum as part of comprehensive benchmarking framework", "r": 5, "rn": "Essential for standardized, comparable LLM performance evaluation", "c": ["Model serving/inference", "Data formats/interop"]}


draft_name: draft-levy-llm-uri-scheme
prompt_hash: 637a37958a171787
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:48.231102+00:00
response_json:
{"name": "draft-levy-llm-uri-scheme", "s": "Defines a URI scheme for identifying LLM endpoints with embedded configuration parameters. Creates a standardized way to specify model, provider, authentication, and inference parameters in a single connection string.", "n": 3, "nn": "URI schemes for AI services are emerging but not well-established in standards", "m": 2, "mn": "Early draft with basic specification, needs more implementation experience", "o": 2, "on": "Some overlap with general service discovery but specific to LLM endpoints", "mo": 3, "mon": "Growing interest in LLM standardization but limited IETF momentum", "r": 4, "rn": "High relevance for LLM integration and interoperability in network applications", "c": ["Model serving/inference", "Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-condrey-rats-witnessd-enrollment
prompt_hash: 815ba4a973da5478
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:48.257144+00:00
response_json:
{"name": "draft-condrey-rats-witnessd-enrollment", "s": "Specifies trust anchor bootstrap protocol for proof of process framework. Defines device enrollment, key provisioning, and trust anchor validation across different deployment modes.", "n": 4, "nn": "Novel approach combining device attestation with process verification", "m": 2, "mn": "Early specification without widespread implementation or testing", "o": 3, "on": "Overlaps with existing device attestation and enrollment protocols", "mo": 2, "mon": "Limited visibility in IETF working groups, niche application area", "r": 3, "rn": "Relevant for secure agent deployment but specialized use case", "c": ["Agent identity/auth", "Policy/governance", "Autonomous netops"]}


draft_name: draft-willman-rtgwg-conduit-tunnels
prompt_hash: 2d9cd6f2ca5ba1bc
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:48.269845+00:00
response_json:
{"name": "draft-willman-rtgwg-conduit-tunnels", "s": "Specifies CONDUIT protocol for managing IPsec tunnel fabrics with automated lifecycle management and SRv6 integration. Focuses on tactical networks with strict cryptographic requirements.", "n": 3, "nn": "Combines existing technologies (IPsec, SRv6) in novel orchestration framework", "m": 3, "mn": "Detailed specification with clear architecture but needs implementation validation", "o": 4, "on": "Significant overlap with existing tunnel management and SRv6 specifications", "mo": 2, "mon": "Traditional networking focus with limited AI/agent community engagement", "r": 2, "rn": "Primarily traditional networking with potential but indirect AI/agent relevance", "c": ["Autonomous netops", "Policy/governance"]}


draft_name: draft-gont-dhcwg-dhcpv6-iids
prompt_hash: 908977be322d0be4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:48.282475+00:00
response_json:
{"name": "draft-gont-dhcwg-dhcpv6-iids", "s": "Describes method for generating semantically opaque IPv6 interface identifiers in DHCPv6. Adapts RFC 7217 SLAAC method for DHCPv6 server-side address assignment.", "n": 2, "nn": "Incremental extension of existing RFC 7217 method to DHCPv6 context", "m": 4, "mn": "Well-developed specification building on proven RFC 7217 foundation", "o": 3, "on": "Directly builds upon RFC 7217 and existing DHCPv6 specifications", "mo": 3, "mon": "Established author with IETF track record, addresses known privacy issue", "r": 2, "rn": "Traditional networking protocol with minimal direct AI/agent relevance", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-melnikov-sasl2
prompt_hash: 82f8f61aadf7e1e1
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:24:48.292954+00:00
response_json:
{"name": "draft-melnikov-sasl2", "s": "Updates SASL framework to support modern authentication requirements including multi-factor authentication and password change requests. Maintains backward compatibility while extending capabilities.", "n": 3, "nn": "Evolutionary update to established protocol with modern auth extensions", "m": 4, "mn": "Mature specification from experienced author updating well-understood protocol", "o": 2, "on": "Updates existing SASL but adds distinct new capabilities", "mo": 4, "mon": "Strong IETF momentum with established author and clear use cases", "r": 4, "rn": "High relevance for agent authentication and multi-factor security requirements", "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]}


draft_name: draft-ietf-tls-ecdhe-mlkem
prompt_hash: 187e606e2492b3b3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:07.175347+00:00
response_json:
{"name": "draft-ietf-tls-ecdhe-mlkem", "s": "Defines hybrid post-quantum key agreement mechanisms for TLS 1.3 that combine ML-KEM with traditional ECDHE. Provides quantum-resistant security while maintaining compatibility with existing elliptic curve cryptography.", "n": 4, "nn": "Post-quantum hybrid approach is relatively novel, combining established ECDHE with new ML-KEM standard", "m": 4, "mn": "Well-developed 12-page specification from IETF working group, ready for implementation", "o": 2, "on": "Unique focus on TLS 1.3 post-quantum hybrids, minimal overlap with other drafts", "mo": 5, "mon": "High momentum - post-quantum cryptography is critical priority with strong industry support", "r": 5, "rn": "Extremely relevant for future-proofing TLS against quantum computing threats", "c": ["Other AI/agent"]}


draft_name: draft-ietf-lake-edhoc-impl-cons
prompt_hash: 854d0e91409dfa7a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:07.209845+00:00
response_json:
{"name": "draft-ietf-lake-edhoc-impl-cons", "s": "Provides implementation guidance for EDHOC authenticated key exchange protocol. Offers practical considerations for deploying EDHOC in constrained environments.", "n": 2, "nn": "Implementation guidance document, not introducing new protocols but providing practical advice", "m": 4, "mn": "Comprehensive 43-page implementation guide from established working group", "o": 4, "on": "Significant overlap with other EDHOC-related drafts in this set", "mo": 3, "mon": "Moderate momentum as supporting document for EDHOC adoption", "r": 3, "rn": "Moderately relevant for constrained device implementations and IoT scenarios", "c": ["Agent identity/auth"]}


draft_name: draft-ietf-lake-authz
prompt_hash: f64d3bd3224769c0
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:07.223052+00:00
response_json:
{"name": "draft-ietf-lake-authz", "s": "Specifies lightweight authorization using EDHOC for zero-touch device onboarding. Enables secure enrollment of new devices in constrained networks using manufacturer-installed trust anchors.", "n": 4, "nn": "Novel application of EDHOC for zero-touch onboarding scenarios", "m": 4, "mn": "Substantial 48-page specification with detailed authorization procedures", "o": 3, "on": "Overlaps with other EDHOC drafts but focuses on specific authorization use case", "mo": 4, "mon": "Strong momentum driven by IoT device deployment needs", "r": 4, "rn": "Highly relevant for automated device provisioning and IoT security", "c": ["Agent identity/auth", "Agent discovery/reg"]}


draft_name: draft-ietf-emu-eap-edhoc
prompt_hash: 4dd27d4bea1a5711
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:07.235047+00:00
response_json:
{"name": "draft-ietf-emu-eap-edhoc", "s": "Defines EAP authentication method based on EDHOC for constrained environments. Integrates EDHOC's lightweight security handshake into the standard EAP framework.", "n": 3, "nn": "Reasonable novelty in bridging EAP and EDHOC protocols", "m": 4, "mn": "Well-developed 31-page specification with clear integration approach", "o": 3, "on": "Overlaps with EDHOC family but unique in EAP integration", "mo": 3, "mon": "Moderate momentum from enterprise network authentication needs", "r": 3, "rn": "Relevant for enterprise networks requiring constrained device authentication", "c": ["Agent identity/auth"]}


draft_name: draft-lenders-core-dnr
prompt_hash: da535271aed40a81
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:07.244960+00:00
response_json:
{"name": "draft-lenders-core-dnr", "s": "Identifies problems in designing DNS SVCB records for OSCORE endpoint discovery. Addresses challenges in discovering CoAP servers and DNS resolvers using OSCORE encryption.", "n": 3, "nn": "Novel problem identification in DNS service discovery for OSCORE environments", "m": 2, "mn": "Early-stage problem statement document, only 12 pages without solutions", "o": 2, "on": "Unique focus on DNS discovery for OSCORE, limited overlap", "mo": 2, "mon": "Lower momentum as problem statement without proposed solutions", "r": 3, "rn": "Relevant for CoAP and constrained network service discovery", "c": ["Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-ra-emu-pqc-eapaka
prompt_hash: 05be25796bd83199
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:24.388913+00:00
response_json:
{"name": "draft-ra-emu-pqc-eapaka", "s": "Enhances EAP-AKA' with post-quantum key encapsulation mechanisms to protect against quantum computer threats. Replaces traditional ECDHE with PQ-KEMs for quantum-safe authentication.", "n": 3, "nn": "Straightforward application of PQ-KEMs to existing protocol", "m": 3, "mn": "Clear technical approach but early stage specification", "o": 4, "on": "Significant overlap with draft-ar-emu-hybrid-pqc-eapaka addressing same protocol", "mo": 3, "mon": "Moderate interest in post-quantum security preparations", "r": 4, "rn": "High relevance for quantum-resistant authentication protocols", "c": ["Agent identity/auth"]}


draft_name: draft-bastian-jose-dvs
prompt_hash: dfd072b9295a931b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:24.411755+00:00
response_json:
{"name": "draft-bastian-jose-dvs", "s": "Defines deriving HMAC keys from public key information in JOSE using Diffie-Hellman key agreement. Enables symmetric MAC authentication from public key operations.", "n": 3, "nn": "Novel combination of DH-KA with JOSE for MAC derivation", "m": 2, "mn": "Brief specification needs more detail and security analysis", "o": 2, "on": "Unique approach to JOSE authentication enhancement", "mo": 2, "mon": "Limited momentum, niche application area", "r": 3, "rn": "Relevant for web security and authentication protocols", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-ietf-ace-coap-est-oscore
prompt_hash: 339bc25bd234cca3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:24.420762+00:00
response_json:
{"name": "draft-ietf-ace-coap-est-oscore", "s": "Specifies carrying EST certificate provisioning over CoAP using OSCORE protection instead of DTLS. Builds on EST-coaps but uses OSCORE and EDHOC for constrained environments.", "n": 4, "nn": "Significant adaptation of EST for constrained IoT environments", "m": 4, "mn": "Well-developed IETF working group draft with comprehensive specification", "o": 3, "on": "Some overlap with existing EST and CoAP security work", "mo": 4, "mon": "Strong momentum as official IETF working group item", "r": 4, "rn": "High relevance for IoT certificate management", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-ar-emu-hybrid-pqc-eapaka
prompt_hash: 5c3411c72d427626
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:24.430438+00:00
response_json:
{"name": "draft-ar-emu-hybrid-pqc-eapaka", "s": "Enhances EAP-AKA' with hybrid post-quantum cryptography combining traditional and quantum-resistant algorithms. Provides quantum safety while maintaining backwards compatibility.", "n": 4, "nn": "Hybrid approach offers practical transition strategy", "m": 3, "mn": "Solid technical foundation but needs implementation validation", "o": 4, "on": "Direct overlap with draft-ra-emu-pqc-eapaka on same protocol", "mo": 3, "mon": "Growing interest in hybrid PQC approaches", "r": 4, "rn": "Highly relevant for quantum-resistant authentication evolution", "c": ["Agent identity/auth"]}


draft_name: draft-spm-lake-pqsuites
prompt_hash: 0b89ac03df721aec
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:25:24.440645+00:00
response_json:
{"name": "draft-spm-lake-pqsuites", "s": "Defines quantum-resistant cipher suites for EDHOC using ML-DSA signatures and ML-KEM key exchange. Specifies post-quantum operation for both signature and PSK authentication methods.", "n": 4, "nn": "First comprehensive PQ cipher suite definition for EDHOC", "m": 3, "mn": "Concise but technically sound specification", "o": 2, "on": "Unique focus on EDHOC post-quantum adaptation", "mo": 4, "mon": "Strong momentum due to LAKE working group activity", "r": 5, "rn": "Critical for post-quantum IoT security infrastructure", "c": ["Agent identity/auth"]}


draft_name: draft-pocero-authkem-ikr-edhoc
prompt_hash: 2930190c65f32e97
model: claude-sonnet-4-20250514
created_at: 2026-02-27T23:25:34.208679+00:00
request_json:
Rate this IETF draft. JSON only.

draft-pocero-authkem-ikr-edhoc | KEM-based Authentication for EDHOC in Initiator-Known Responder (IKR) Scenarios | 2026-01-20 | 26pg
Abstract: This document specifies a more efficient variant of a Key
   Encapsulation Mechanism (KEM)-based authentication method for the
   Ephemeral Diffie-Hellman Over COSE (EDHOC) lightweight protocol,
   designed for the specific scenario in which the Initiator has prior
   knowledge of the Responder’s credentials, a case commonly found in
   constrained environments.  Improving upon the approach described in
   KEM-based Authentication for EDHOC, this method uses only a mandatory
   three-message handshake to enable signature-free post-quantum
   authentication when PQC KEMs, such as the NIST-standardized ML-KEM,
   are employed, while still providing mutual authentication, forward
   secrecy, and a degree of identity protection.

Return JSON: {"s":"2-3 sentence summary","n":<1-5>,"nn":"novelty note","m":<1-5>,"mn":"maturity note","o":<1-5>,"on":"overlap note","mo":<1-5>,"mon":"momentum note","r":<1-5>,"rn":"relevance note","c":["categories"]}

Scale: 1=very low..5=very high. Overlap: 1=unique,5=heavy overlap.
Categories: A2A protocols, AI safety/alignment, ML traffic mgmt, Autonomous netops, Agent identity/auth, Data formats/interop, Policy/governance, Model serving/inference, Agent discovery/reg, Human-agent interaction, Other AI/agent
JSON only, no fences.

response_json:
{"s":"This draft proposes a KEM-based authentication variant for EDHOC that optimizes for scenarios where the initiator knows the responder's credentials beforehand, reducing the handshake to three mandatory messages. It aims to provide signature-free post-quantum authentication while maintaining mutual authentication and forward secrecy in constrained environments.","n":3,"nn":"Moderate novelty - builds incrementally on existing KEM-based EDHOC authentication with optimization for specific IKR scenarios","m":2,"mn":"Early maturity - recent draft with limited field testing of the optimized three-message approach","o":4,"on":"Significant overlap with existing EDHOC KEM authentication work, representing an optimization rather than fundamental innovation","mo":3,"mon":"Moderate momentum - post-quantum cryptography adoption is growing but constrained environment deployment remains niche","r":4,"rn":"High relevance for IoT and constrained networks needing post-quantum security, though limited to specific IKR use cases","c":["Agent identity/auth"]}


draft_name: draft-tiloca-lake-exporter-output-length
prompt_hash: b8d14f91cff7979d
model: claude-sonnet-4-20250514
created_at: 2026-02-27T23:25:39.641204+00:00
request_json:
Rate this IETF draft. JSON only.

draft-tiloca-lake-exporter-output-length | In-band Agreement of Output Lengths for the EDHOC_Exporter Interface of Ephemeral Diffie-Hellman Over COSE (EDHOC) | 2026-01-09 | 10pg
Abstract: The lightweight authenticated key exchange protocol Ephemeral Diffie-
   Hellman Over COSE (EDHOC) allows two peers to compute a shared secret
   session key.  Once the session key is available, the two peers can
   use the EDHOC_Exporter interface, e.g., to derive keying material for
   an application protocol.  This document defines an in-band approach
   that can be used by the two peers to agree about the lengths of the
   outputs produced with the EDHOC_Exporter interface.  The defined
   approach relies on an EDHOC External Authorization Data (EAD) item
   that can be exchanged in the first two EDHOC messages of an EDHOC
   session.

Return JSON: {"s":"2-3 sentence summary","n":<1-5>,"nn":"novelty note","m":<1-5>,"mn":"maturity note","o":<1-5>,"on":"overlap note","mo":<1-5>,"mon":"momentum note","r":<1-5>,"rn":"relevance note","c":["categories"]}

Scale: 1=very low..5=very high. Overlap: 1=unique,5=heavy overlap.
Categories: A2A protocols, AI safety/alignment, ML traffic mgmt, Autonomous netops, Agent identity/auth, Data formats/interop, Policy/governance, Model serving/inference, Agent discovery/reg, Human-agent interaction, Other AI/agent
JSON only, no fences.

response_json:
{"s":"This draft defines a mechanism for EDHOC peers to agree in-band on output lengths for the EDHOC_Exporter interface using External Authorization Data items. The approach allows negotiation of key derivation output sizes during the EDHOC handshake process.","n":2,"nn":"Incremental extension to existing EDHOC protocol using established EAD mechanisms","m":3,"mn":"Builds on mature EDHOC foundation but adds new negotiation complexity","o":2,"on":"Specific to EDHOC exporter interface with limited overlap to other key agreement protocols","mo":2,"mon":"Niche enhancement for EDHOC deployments with limited broader appeal","r":2,"rn":"Useful for EDHOC implementations but addresses narrow technical requirement","c":["Agent identity/auth"]}


draft_name: draft-lake-pocero-authkem-edhoc
prompt_hash: cd144b8a99270edf
model: claude-sonnet-4-20250514
created_at: 2026-02-27T23:25:45.678400+00:00
request_json:
Rate this IETF draft. JSON only.

draft-lake-pocero-authkem-edhoc | KEM-based Authentication for EDHOC | 2025-10-16 | 33pg
Abstract: This document specifies extensions to the Ephemeral Diffie-Hellman
   over COSE (EDHOC) protocol to provide resistance against quantum
   computer adversaries by incorporating Post-Quantum Cryptography (PQC)
   mechanisms for both key exchange and authentication.  It defines a
   Key Encapsulation Mechanism (KEM)-based authentication method to
   enable signature-free post-quantum authentication when PQC KEMs, such
   as NIST-standardized ML-KEM, are used.

Return JSON: {"s":"2-3 sentence summary","n":<1-5>,"nn":"novelty note","m":<1-5>,"mn":"maturity note","o":<1-5>,"on":"overlap note","mo":<1-5>,"mon":"momentum note","r":<1-5>,"rn":"relevance note","c":["categories"]}

Scale: 1=very low..5=very high. Overlap: 1=unique,5=heavy overlap.
Categories: A2A protocols, AI safety/alignment, ML traffic mgmt, Autonomous netops, Agent identity/auth, Data formats/interop, Policy/governance, Model serving/inference, Agent discovery/reg, Human-agent interaction, Other AI/agent
JSON only, no fences.

response_json:
{"s":"This draft extends the EDHOC protocol to provide quantum-resistant authentication using KEM-based mechanisms instead of traditional signatures. It addresses the need for post-quantum cryptography in IoT and constrained device authentication scenarios.","n":3,"nn":"Moderate novelty in applying KEM-based authentication to EDHOC, building on established PQC concepts","m":2,"mn":"Early stage draft with basic specification but likely needs implementation experience and security analysis","o":3,"on":"Some overlap with general PQC standardization efforts but specific to EDHOC protocol extensions","mo":4,"mon":"High momentum due to urgent industry need for quantum-resistant cryptography in IoT/constrained devices","r":4,"rn":"Highly relevant as quantum threat becomes more imminent and IoT devices need lightweight PQC solutions","c":["Agent identity/auth"]}


draft_name: draft-ietf-emu-pqc-eapaka
prompt_hash: 598093edf4d661e3
model: claude-sonnet-4-20250514
created_at: 2026-02-27T23:25:51.309888+00:00
request_json:
Rate this IETF draft. JSON only.

draft-ietf-emu-pqc-eapaka | Post-Quantum Key Encapsulation Mechanisms (PQ KEMs) in EAP-AKA prime | 2026-02-26 | 20pg
Abstract: Forward Secrecy for the Extensible Authentication Protocol Method for
   Authentication and Key Agreement (EAP-AKA' FS) is specified in
   [RFC9678], providing updates to [RFC9048] with an optional extension
   that offers ephemeral key exchange using the traditional Ephemeral
   Elliptic Curve Diffie-Hellman (ECDHE) key agreement algorithm for
   achieving perfect forward secrecy (PFS).  However, it is susceptible
   to future threats from Cryptographically Relevant Quantum Computers,
   which could potentially compromise a traditional ephemeral public
   key.  If the adversary has also obtained knowledge of the long-term
   key and ephemeral public key, it could compromise session keys
   generated as part of the authentication run in EAP-AKA'.

   This draft aims to enhance the security of EAP-AKA' FS protocol by
   making it quantum-safe using Post-Quantum Key Encapsulation
   Mechanisms (PQ-KEMs).

Return JSON: {"s":"2-3 sentence summary","n":<1-5>,"nn":"novelty note","m":<1-5>,"mn":"maturity note","o":<1-5>,"on":"overlap note","mo":<1-5>,"mon":"momentum note","r":<1-5>,"rn":"relevance note","c":["categories"]}

Scale: 1=very low..5=very high. Overlap: 1=unique,5=heavy overlap.
Categories: A2A protocols, AI safety/alignment, ML traffic mgmt, Autonomous netops, Agent identity/auth, Data formats/interop, Policy/governance, Model serving/inference, Agent discovery/reg, Human-agent interaction, Other AI/agent
JSON only, no fences.

response_json:
{"s":"This draft proposes enhancing EAP-AKA' Forward Secrecy with Post-Quantum Key Encapsulation Mechanisms to protect against future quantum computer threats. It builds on RFC9678 by replacing traditional ECDHE key exchange with quantum-resistant alternatives.","n":3,"nn":"Incremental enhancement of existing protocol with established PQ-KEM techniques","m":3,"mn":"Draft stage with reasonable technical foundation but requires implementation validation","o":2,"on":"Specific application to EAP-AKA' with limited overlap in similar PQ-KEM integrations","mo":4,"mon":"High momentum due to urgent quantum threat timeline and active IETF post-quantum standardization efforts","r":4,"rn":"Highly relevant for securing authentication infrastructure against quantum threats","c":["Agent identity/auth"]}


draft_name: draft-wang-ppm-ecdh-psi
prompt_hash: 96ac18edbb7a4ae4
model: claude-sonnet-4-20250514
created_at: 2026-02-27T23:25:57.963879+00:00
request_json:
Rate this IETF draft. JSON only.

draft-wang-ppm-ecdh-psi | PSI based on ECDH | 2025-08-20 | 31pg
Abstract: This document describes Elliptic Curve Diffie-Hellman Private Set
   Intersection (ECDH-PSI) for 2 participants.  It instantiates the
   classical Meadows match-making protocol with standard elliptic curves
   and hash-to-curve methods, enabling the participants to find common
   records in a privacy-respecting way.  In ECDH-PSI, records are
   encoded to points on an elliptic curve, and masked by the private
   keys of both participants.  To compute the intersection, a
   participant only uses the jointly masked datasets and its original
   dataset locally, which prevents its partner from learning the private
   records not in the intersection.

Return JSON: {"s":"2-3 sentence summary","n":<1-5>,"nn":"novelty note","m":<1-5>,"mn":"maturity note","o":<1-5>,"on":"overlap note","mo":<1-5>,"mon":"momentum note","r":<1-5>,"rn":"relevance note","c":["categories"]}

Scale: 1=very low..5=very high. Overlap: 1=unique,5=heavy overlap.
Categories: A2A protocols, AI safety/alignment, ML traffic mgmt, Autonomous netops, Agent identity/auth, Data formats/interop, Policy/governance, Model serving/inference, Agent discovery/reg, Human-agent interaction, Other AI/agent
JSON only, no fences.

response_json:
{"s":"This draft specifies ECDH-based Private Set Intersection (PSI) for two parties using elliptic curve cryptography and the Meadows protocol. It enables participants to find common records while preserving privacy of non-intersecting elements.","n":2,"nn":"Applies well-known ECDH techniques to PSI with standard elliptic curves - incremental but solid engineering","m":3,"mn":"Reasonable technical depth for IETF draft with concrete protocol specification, though some implementation details may need refinement","o":2,"on":"PSI is established research area but ECDH-specific variant for IETF standardization has limited direct overlap","mo":2,"mon":"Privacy-preserving computation gaining interest but unclear if this specific approach has strong industry backing","r":3,"rn":"Privacy-preserving set intersection has legitimate use cases in federated learning and data sharing scenarios","c":["Data formats/interop"]}


draft_name: draft-ietf-lamps-rfc5274bis
prompt_hash: 902caa956385cc87
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:14.628511+00:00
response_json:
{"name": "draft-ietf-lamps-rfc5274bis", "s": "Defines compliance requirements for Certificate Management Messages over CMS (CMC) enrollment protocol. Updates and obsoletes previous RFCs with current compliance statements.", "n": 2, "nn": "Incremental update to existing CMC compliance requirements", "m": 4, "mn": "Mature IETF working group draft updating well-established protocols", "o": 1, "on": "Specific to CMC compliance, minimal overlap with other drafts", "mo": 3, "mon": "Standard LAMPS working group progression", "r": 3, "rn": "Important for PKI certificate management compliance", "c": ["Data formats/interop"]}


draft_name: draft-ietf-sshm-mlkem-hybrid-kex
prompt_hash: 42389fc14fea41e3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:14.658564+00:00
response_json:
{"name": "draft-ietf-sshm-mlkem-hybrid-kex", "s": "Defines post-quantum hybrid key exchange combining ML-KEM with traditional ECDH for SSH transport layer. Provides quantum resistance while maintaining compatibility.", "n": 4, "nn": "Novel hybrid approach combining quantum-resistant and traditional crypto", "m": 4, "mn": "Well-developed IETF draft addressing critical post-quantum needs", "o": 2, "on": "Part of broader post-quantum cryptography efforts but SSH-specific", "mo": 4, "mon": "High momentum due to post-quantum migration urgency", "r": 5, "rn": "Critical for quantum-resistant SSH implementations", "c": ["Data formats/interop"]}


draft_name: draft-ietf-lake-edhoc-psk
prompt_hash: bab88d38c6ae95d1
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:14.671819+00:00
response_json:
{"name": "draft-ietf-lake-edhoc-psk", "s": "Specifies pre-shared key authentication method for EDHOC key exchange protocol. Enhances efficiency while providing mutual authentication and quantum resistance.", "n": 3, "nn": "PSK method extension to existing EDHOC protocol", "m": 4, "mn": "Comprehensive 31-page specification with detailed security considerations", "o": 2, "on": "Extends EDHOC but PSK approach is relatively unique", "mo": 3, "mon": "Steady progress in LAKE working group", "r": 4, "rn": "Important for IoT and constrained device authentication", "c": ["Data formats/interop"]}


draft_name: draft-yusef-lamps-rfc7030-renewal-recommendation
prompt_hash: 1a68f02bcae62495
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:14.683101+00:00
response_json:
{"name": "draft-yusef-lamps-rfc7030-renewal-recommendation", "s": "Extends EST protocol to provide certificate renewal timing recommendations from CA to end-entity devices. Addresses issues with traditional 50% lifetime renewal approach.", "n": 2, "nn": "Incremental extension addressing practical deployment issue", "m": 3, "mn": "Concise 7-page draft addressing specific operational need", "o": 1, "on": "Specific EST extension with minimal overlap", "mo": 2, "mon": "Individual submission with limited visibility", "r": 3, "rn": "Useful for automated certificate lifecycle management", "c": ["Data formats/interop"]}


draft_name: draft-ietf-lamps-private-key-stmt-attr
prompt_hash: 8aaab2e367b8efe3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:14.692605+00:00
response_json:
{"name": "draft-ietf-lamps-private-key-stmt-attr", "s": "Defines X.509 attribute for private key possession statements as alternative to cryptographic proof of possession. Enables certificate subjects to provide signed statements for CA verification.", "n": 3, "nn": "Alternative approach to traditional proof-of-possession mechanisms", "m": 4, "mn": "Mature 19-page specification with detailed attribute definitions", "o": 1, "on": "Unique approach to private key possession verification", "mo": 3, "mon": "Standard LAMPS working group development", "r": 3, "rn": "Relevant for flexible certificate enrollment scenarios", "c": ["Data formats/interop"]}


draft_name: draft-bastian-jose-pkdh
prompt_hash: f1ec249e52227205
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:33.639481+00:00
response_json:
{"name": "draft-bastian-jose-pkdh", "s": "Defines a method to derive symmetric MAC keys from public information in JSON Web Signatures using Diffie-Hellman key agreement. This enables HMAC-based authentication without requiring pre-shared keys.", "n": 3, "nn": "Novel approach combining DH-KA with JWS for MAC key derivation, though builds on established JOSE framework", "m": 3, "mn": "Reasonably mature specification with clear technical approach, but needs more implementation experience", "o": 2, "on": "Some overlap with existing JOSE specifications but introduces new key derivation mechanism", "mo": 2, "mon": "Limited discussion and adoption visible in broader community", "r": 3, "rn": "Relevant for JSON-based security applications requiring dynamic key establishment", "c": ["Data formats/interop"]}


draft_name: draft-lake-pocero-authkem-ikr-edhoc
prompt_hash: 9ad88df460a7afde
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:33.659939+00:00
response_json:
{"name": "draft-lake-pocero-authkem-ikr-edhoc", "s": "Specifies an optimized KEM-based authentication variant for EDHOC protocol in scenarios where the initiator knows the responder's credentials. Enables post-quantum authentication with only three messages while maintaining mutual authentication and forward secrecy.", "n": 4, "nn": "High novelty in optimizing post-quantum authentication for constrained environments with prior knowledge scenarios", "m": 4, "mn": "Well-developed technical specification building on established EDHOC framework", "o": 3, "on": "Builds heavily on existing EDHOC work but provides distinct optimization", "mo": 4, "mon": "Strong momentum from LAKE working group and post-quantum cryptography interest", "r": 5, "rn": "Highly relevant for IoT and constrained device security in post-quantum era", "c": ["Agent identity/auth"]}


draft_name: draft-ietf-lamps-attestation-freshness
prompt_hash: 2724aa6f19bd2f02
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:33.671355+00:00
response_json:
{"name": "draft-ietf-lamps-attestation-freshness", "s": "Outlines how nonces are supplied to end entities by RA/CA for inclusion in attestation evidence within Certificate Signing Requests. Covers implementation across CMP, EST, and CMC protocols to demonstrate evidence freshness.", "n": 3, "nn": "Addresses important freshness problem in attestation but uses established nonce-based approach", "m": 4, "mn": "Mature specification from established working group with comprehensive protocol coverage", "o": 2, "on": "Some overlap with existing certificate management protocols but adds attestation-specific mechanisms", "mo": 4, "mon": "Strong momentum from LAMPS working group and growing attestation requirements", "r": 4, "rn": "Very relevant for trusted computing and device attestation scenarios", "c": ["Agent identity/auth"]}


draft_name: draft-chen-lake-edhoc-aka
prompt_hash: e8c38a4d65411aa5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:33.682209+00:00
response_json:
{"name": "draft-chen-lake-edhoc-aka", "s": "Defines EDHOC-AKA authentication method combining AKA protocol with EDHOC for mobile network access authentication. Designed for resource-constrained scenarios like Non-Terrestrial Networks using symmetric cryptography.", "n": 3, "nn": "Novel combination of AKA and EDHOC but builds on well-established protocols", "m": 2, "mn": "Early stage specification with limited technical detail and implementation guidance", "o": 3, "on": "Significant overlap with existing AKA and EDHOC protocols", "mo": 3, "mon": "Moderate interest from mobile network and satellite communication communities", "r": 4, "rn": "Highly relevant for satellite and mobile network authentication scenarios", "c": ["Agent identity/auth"]}


draft_name: draft-ietf-lake-app-profiles
prompt_hash: 795e3aab210b8216
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:33.692145+00:00
response_json:
{"name": "draft-ietf-lake-app-profiles", "s": "Defines canonical CBOR representation for EDHOC application profiles and coordination mechanisms for their use. Establishes standardized way to describe, distribute, and store EDHOC parameters while defining well-known profiles for interoperability.", "n": 4, "nn": "High novelty in standardizing application profile coordination for lightweight protocols", "m": 5, "mn": "Very mature and comprehensive specification with detailed technical framework", "o": 2, "on": "Unique approach to application profile coordination with minimal overlap", "mo": 5, "mon": "Strong momentum from LAKE working group with broad industry interest", "r": 5, "rn": "Critical for EDHOC deployment and interoperability across various applications", "c": ["Data formats/interop", "Agent identity/auth"]}


draft_name: draft-ietf-lake-ra
prompt_hash: aaa11ab4d2dbffc4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:52.554488+00:00
response_json:
{"name": "draft-ietf-lake-ra", "s": "Specifies remote attestation procedures integrated with EDHOC lightweight key exchange protocol. Enables verification of device/system integrity during authentication based on RATS architecture.", "n": 3, "nn": "Moderate novelty in combining attestation with EDHOC, though both concepts exist separately", "m": 4, "mn": "Well-structured IETF working group draft with clear technical approach", "o": 2, "on": "Some overlap with general attestation and EDHOC work but specific combination is relatively unique", "mo": 4, "mon": "IETF working group backing suggests good momentum and implementation interest", "r": 4, "rn": "High relevance for IoT security and zero-trust architectures requiring device attestation", "c": ["Agent identity/auth", "Policy/governance"]}


draft_name: draft-ietf-ace-edhoc-oscore-profile
prompt_hash: ee4b8428c96a9c23
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:52.582829+00:00
response_json:
{"name": "draft-ietf-ace-edhoc-oscore-profile", "s": "Defines ACE framework profile using EDHOC for mutual authentication and OSCORE for secure communication. Enables authorization delegation from constrained devices to more capable hosts.", "n": 3, "nn": "Reasonable novelty in combining existing protocols for constrained environment authorization", "m": 4, "mn": "Comprehensive 91-page specification from established IETF working group", "o": 3, "on": "Moderate overlap with existing ACE, EDHOC, and OSCORE specifications", "mo": 4, "mon": "Strong IETF working group support and addresses real IoT deployment needs", "r": 4, "rn": "Very relevant for IoT and constrained device security architectures", "c": ["Agent identity/auth", "A2A protocols"]}


draft_name: draft-josefsson-chempat
prompt_hash: 8a8b05d8bfc730bc
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:52.596024+00:00
response_json:
{"name": "draft-josefsson-chempat", "s": "Generic framework for Post-Quantum/Traditional hybrid key encapsulation mechanisms. Provides concrete instantiated algorithms combining classical and quantum-resistant cryptographic methods.", "n": 4, "nn": "High novelty in providing generic combiner construct for PQ/T hybrid KEMs", "m": 3, "mn": "Individual draft with solid technical content but less institutional backing", "o": 2, "on": "Relatively unique approach to hybrid PQ cryptography, low overlap", "mo": 3, "mon": "Individual effort with uncertain implementation momentum", "r": 5, "rn": "Extremely relevant for quantum-resistant cryptography transition", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-pocero-authkem-edhoc
prompt_hash: 694360d5e1f0fc40
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:52.605984+00:00
response_json:
{"name": "draft-pocero-authkem-edhoc", "s": "Extends EDHOC with KEM-based authentication for post-quantum resistance. Enables signature-free quantum-resistant authentication using mechanisms like ML-KEM.", "n": 4, "nn": "High novelty in signature-free post-quantum authentication for EDHOC", "m": 3, "mn": "Individual draft with detailed technical approach but limited institutional review", "o": 3, "on": "Some overlap with EDHOC and PQC work but specific approach is fairly unique", "mo": 2, "mon": "Individual effort with uncertain adoption prospects", "r": 5, "rn": "Highly relevant for post-quantum cryptography and lightweight authentication", "c": ["Agent identity/auth", "A2A protocols"]}


draft_name: draft-ietf-hpke-hpke
prompt_hash: 4673f443f37949a5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:26:52.616841+00:00
response_json:
{"name": "draft-ietf-hpke-hpke", "s": "Comprehensive specification for hybrid public key encryption supporting arbitrary-sized plaintexts. Includes pre-shared key authentication and works with various KEM/KDF/AEAD combinations.", "n": 3, "nn": "Moderate novelty as hybrid encryption concept exists but comprehensive standardization adds value", "m": 5, "mn": "Mature IETF working group standard with extensive development and review", "o": 2, "on": "Relatively unique comprehensive approach to hybrid PKE standardization", "mo": 5, "mon": "Strong IETF momentum with wide industry interest and implementation", "r": 5, "rn": "Extremely relevant as fundamental cryptographic building block for modern protocols", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-ietf-lamps-rfc7030-csrattrs
prompt_hash: dd6704e2862f8714
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:12.825167+00:00
response_json:
{"name": "draft-ietf-lamps-rfc7030-csrattrs", "s": "Updates RFC7030 to clarify CSR Attributes Response encoding and adds template-based approach for EST servers. Resolves implementation challenges and confusion in the existing EST specification.", "n": 3, "nn": "Incremental improvement to existing EST protocol with template approach being moderately novel", "m": 4, "mn": "Well-developed specification addressing real implementation issues with clear encoding rules", "o": 2, "on": "Specific update to EST protocol with limited overlap to other current drafts", "mo": 4, "mon": "IETF working group draft addressing documented interoperability problems", "r": 4, "rn": "High relevance for PKI deployments and certificate enrollment infrastructure", "c": ["Data formats/interop", "Policy/governance"]}


draft_name: draft-ietf-suit-firmware-encryption
prompt_hash: 61a484313267f0f8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:12.873917+00:00
response_json:
{"name": "draft-ietf-suit-firmware-encryption", "s": "Specifies encryption techniques for firmware and software payloads in SUIT manifests. Uses ES-DH and AES-KW for key agreement with symmetric encryption for payload protection.", "n": 3, "nn": "Applies established crypto techniques to SUIT manifest context, moderately novel integration", "m": 4, "mn": "Comprehensive 55-page specification with detailed technical approaches", "o": 2, "on": "Specific to SUIT manifest encryption with minimal overlap to other efforts", "mo": 4, "mon": "Active IETF working group addressing IoT security needs", "r": 4, "rn": "Important for IoT device security and firmware update protection", "c": ["Data formats/interop"]}


draft_name: draft-ietf-tls-deprecate-obsolete-kex
prompt_hash: b8bcd149be9ee515
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:12.887340+00:00
response_json:
{"name": "draft-ietf-tls-deprecate-obsolete-kex", "s": "Deprecates obsolete key exchange methods in TLS 1.2 including finite field DH and RSA. Updates multiple RFCs to change cipher suite recommendations to MUST NOT or SHOULD NOT.", "n": 2, "nn": "Standard security maintenance work deprecating known weak algorithms", "m": 4, "mn": "Thorough specification updating many RFCs with clear deprecation guidance", "o": 1, "on": "Focused TLS 1.2 security update with unique scope", "mo": 4, "mon": "Important security maintenance from established IETF TLS working group", "r": 5, "rn": "Critical for maintaining TLS security posture across internet infrastructure", "c": ["Policy/governance"]}


draft_name: draft-ietf-emu-hybrid-pqc-eapaka
prompt_hash: 2f1217f6134b9d6a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:12.896933+00:00
response_json:
{"name": "draft-ietf-emu-hybrid-pqc-eapaka", "s": "Enhances EAP-AKA' with post-quantum cryptography to address quantum computing threats. Uses hybrid PQ/T algorithms to achieve quantum-safe authentication.", "n": 4, "nn": "Novel application of hybrid post-quantum crypto to cellular authentication protocols", "m": 3, "mn": "Short specification building on recent EAP-AKA' FS work, early stage development", "o": 2, "on": "Specific to EAP-AKA' with some overlap to general PQC standardization efforts", "mo": 4, "mon": "Timely post-quantum crypto adoption in critical mobile authentication", "r": 4, "rn": "High relevance for future-proofing mobile network security", "c": ["Agent identity/auth"]}


draft_name: draft-nsiangani-authenticatedsecuredlayer
prompt_hash: 49c9e91f717c8e88
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:12.906212+00:00
response_json:
{"name": "draft-nsiangani-authenticatedsecuredlayer", "s": "Proposes ASL protocol using novel phi-ns-x arithmetic primitive instead of traditional crypto. Claims security through non-linear modular arithmetic and combinatorial complexity.", "n": 5, "nn": "Completely novel cryptographic approach abandoning all established primitives", "m": 1, "mn": "Unproven cryptographic claims without peer review or security analysis", "o": 1, "on": "Entirely different approach from any existing security protocols", "mo": 1, "mon": "Individual submission with no working group support or adoption signals", "r": 1, "rn": "Very low relevance due to unvetted crypto and lack of security foundation", "c": ["Other AI/agent"]}


draft_name: draft-ietf-lamps-est-renewal-info
prompt_hash: f6a434578b4d10d3
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:34.229701+00:00
response_json:
{"name": "draft-ietf-lamps-est-renewal-info", "s": "Extends EST protocol to provide server-side recommendations for certificate renewal timing. Addresses the issue of overly early renewal attempts as certificate lifetimes shorten.", "n": 3, "nn": "Modest extension to existing EST protocol, addresses practical timing optimization", "m": 4, "mn": "Well-scoped problem with clear solution, builds on established EST standard", "o": 2, "on": "Specific EST extension with minimal overlap with other certificate management work", "mo": 4, "mon": "IETF working group draft addressing real deployment needs as cert lifetimes decrease", "r": 4, "rn": "High relevance for PKI deployments, especially with trend toward shorter certificate lifetimes", "c": ["Data formats/interop"]}


draft_name: draft-ietf-tls-extended-key-update
prompt_hash: 0db612cb636df65b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:34.252200+00:00
response_json:
{"name": "draft-ietf-tls-extended-key-update", "s": "Adds post-compromise security to TLS 1.3 through fresh Diffie-Hellman exchanges during active sessions. Particularly valuable for long-lived connections in IoT and telecom environments.", "n": 4, "nn": "Significant security enhancement addressing post-compromise scenarios not covered by existing KeyUpdate", "m": 4, "mn": "Substantial 40-page specification with clear security motivation and detailed mechanism", "o": 2, "on": "Extends TLS 1.3 in novel direction, minimal overlap with other key management approaches", "mo": 4, "mon": "IETF working group draft addressing important security gap in long-lived sessions", "r": 5, "rn": "Critical security improvement for TLS, especially relevant for IoT and industrial applications", "c": ["Data formats/interop"]}


draft_name: draft-ietf-anima-constrained-voucher
prompt_hash: 97307d69e2ccdfba
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:34.266019+00:00
response_json:
{"name": "draft-ietf-anima-constrained-voucher", "s": "Adapts BRSKI secure device onboarding for constrained IoT environments using CBOR vouchers and CoAP/DTLS. Enables zero-touch bootstrapping in resource-limited and lossy networks.", "n": 4, "nn": "Significant adaptation of BRSKI for constrained environments with new encoding and transport", "m": 5, "mn": "Comprehensive 93-page specification with detailed protocol adaptations and implementations", "o": 3, "on": "Builds heavily on BRSKI but targets different deployment scenario", "mo": 4, "mon": "IETF working group draft addressing growing IoT security bootstrapping needs", "r": 5, "rn": "Extremely relevant for IoT deployments requiring secure zero-touch onboarding", "c": ["Agent identity/auth", "Data formats/interop"]}


draft_name: draft-templin-6man-mla
prompt_hash: e560fb169482ca94
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:34.307683+00:00
response_json:
{"name": "draft-templin-6man-mla", "s": "Introduces Multilink Local Address (MLA) type for autonomous IPv6 addressing in ad hoc networks. Enables topology-independent addressing when traditional delegation services are unavailable.", "n": 3, "nn": "New IPv6 address type for specific ad hoc networking scenarios", "m": 3, "mn": "Moderate complexity solution with clear problem statement but individual submission", "o": 3, "on": "Some overlap with other IPv6 addressing schemes for mobile/ad hoc scenarios", "mo": 2, "mon": "Individual submission without clear working group momentum", "r": 3, "rn": "Moderate relevance for ad hoc networking scenarios, niche but legitimate use case", "c": ["A2A protocols"]}


draft_name: draft-bernardos-cats-isac-uc
prompt_hash: 43ca925b183b8349
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:34.320760+00:00
response_json:
{"name": "draft-bernardos-cats-isac-uc", "s": "Presents Integrated Sensing and Communications (ISAC) as a use case for CATS architecture. Explores joint optimization of sensing and communication functions for autonomous systems and smart cities.", "n": 3, "nn": "Applies existing ISAC concepts to CATS framework, use case exploration rather than protocol innovation", "m": 2, "mn": "Early-stage use case document, limited technical depth in protocol specifics", "o": 3, "on": "ISAC concepts exist elsewhere, overlap with general CATS and sensing integration work", "mo": 3, "mon": "Part of emerging CATS discussions but still exploratory phase", "r": 4, "rn": "High relevance for future autonomous systems requiring integrated sensing and communication", "c": ["Autonomous netops", "ML traffic mgmt"]}


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
prompt_hash: a1f3a15cbfc40bf4
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:55.424343+00:00
response_json:
{"name": "draft-ahn-opsawg-5g-security-i2nsf-framework", "s": "Proposes an integrated security framework for 5G edge networks using I2NSF architecture with Intent-Based Networking. Enables automated translation of high-level security intents into enforceable policies across network and application layers.", "n": 3, "nn": "Combines existing I2NSF and IBN concepts for 5G security but integration approach shows some novelty", "m": 3, "mn": "Well-structured framework but lacks implementation details and validation results", "o": 3, "on": "Moderate overlap with existing I2NSF and 5G security work, but specific integration is less explored", "mo": 3, "mon": "5G security is active area but I2NSF adoption has been moderate", "r": 4, "rn": "Highly relevant for autonomous 5G security management and policy automation", "c": ["Autonomous netops", "Policy/governance"]}


draft_name: draft-fu-cats-flow-lb
prompt_hash: f45cd818090b9a49
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:55.446079+00:00
response_json:
{"name": "draft-fu-cats-flow-lb", "s": "Specifies flow-level load balancing for Computing-Aware Traffic Steering to reduce control overhead. Enables data plane autonomous flow distribution for better resource utilization.", "n": 3, "nn": "Incremental improvement to CATS with focus on autonomous data plane decisions", "m": 2, "mn": "Brief document with limited technical depth and no evaluation", "o": 4, "on": "Significant overlap with existing CATS and load balancing work", "mo": 4, "mon": "CATS is active area with strong industry interest", "r": 3, "rn": "Relevant for autonomous traffic management but narrowly focused", "c": ["ML traffic mgmt", "Autonomous netops"]}


draft_name: draft-templin-manet-inet
prompt_hash: ee8796e1ab01184a
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:55.458240+00:00
response_json:
{"name": "draft-templin-manet-inet", "s": "Presents problem statement and gap analysis for MANET internetworking with fixed networks. Identifies challenges in connecting autonomous mobile node systems to the global Internet.", "n": 2, "nn": "Problem statement format limits novelty, addressing well-known MANET challenges", "m": 2, "mn": "Early stage problem identification without proposed solutions", "o": 4, "on": "High overlap with decades of MANET research and existing problem statements", "mo": 2, "mon": "MANET research has declined in recent years with limited working group activity", "r": 2, "rn": "Limited relevance to modern AI/agent systems, focuses on traditional mobile networking", "c": ["Other AI/agent"]}


draft_name: draft-sogomonian-ai-uri-scheme
prompt_hash: 34b4b21e49c57ed8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:55.468963+00:00
response_json:
{"name": "draft-sogomonian-ai-uri-scheme", "s": "Defines experimental AI URI scheme for dedicated AI resource access. Enables native connectivity for autonomous systems while supporting human interoperability via HTTPS gateways.", "n": 4, "nn": "Novel approach to AI resource addressing with dual autonomous/human access paradigm", "m": 2, "mn": "Very brief specification lacking detailed syntax, semantics, and security considerations", "o": 1, "on": "Unique approach to AI resource identification, no direct overlaps found", "mo": 3, "mon": "AI infrastructure gaining attention but URI schemes are niche area", "r": 5, "rn": "Highly relevant for AI agent discovery, registration, and autonomous system connectivity", "c": ["Agent discovery/reg", "Agent identity/auth", "Data formats/interop"]}


draft_name: draft-bernardos-green-isac-uc
prompt_hash: 21fa81f50758da75
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:27:55.479509+00:00
response_json:
{"name": "draft-bernardos-green-isac-uc", "s": "Presents ISAC use case for GREEN Working Group discussions on joint sensing and communication optimization. Targets applications in autonomous systems, smart cities, and industrial automation.", "n": 2, "nn": "Use case presentation of known ISAC concepts, limited technical novelty", "m": 2, "mn": "Template-based use case document without technical specifications or solutions", "o": 3, "on": "Moderate overlap with existing ISAC research and GREEN use cases", "mo": 3, "mon": "ISAC is emerging area and GREEN WG is active, but early stage", "r": 3, "rn": "Relevant for autonomous systems requiring sensing capabilities but lacks AI/agent focus", "c": ["Autonomous netops", "Other AI/agent"]}


draft_name: draft-pbs-sidrops-roaanycast
prompt_hash: 9ad3b77a0b2877a8
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:14.466800+00:00
response_json:
{"name": "draft-pbs-sidrops-roaanycast", "s": "Defines best practices for managing Route Origin Authorizations (ROAs) for globally anycasted services where each anycast node uses a unique origin ASN. Addresses technical risks and mitigation strategies for RPKI operations in anycast deployments.", "n": 3, "nn": "Moderate novelty - addresses specific gap in ROA management for unique-ASN anycast deployments", "m": 4, "mn": "Well-developed with concrete best practices and risk mitigation strategies", "o": 2, "on": "Limited overlap with existing RPKI/ROA work, focuses on specific anycast scenario", "mo": 3, "mon": "Moderate momentum - addresses operational need in RPKI community", "r": 4, "rn": "High relevance for network operators using anycast with RPKI validation", "c": ["Policy/governance", "Autonomous netops"]}


draft_name: draft-sogomonian-aiip-architecture
prompt_hash: 5eafcf4dc4c5dc3e
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:14.488032+00:00
response_json:
{"name": "draft-sogomonian-aiip-architecture", "s": "Defines architectural model for Artificial Intelligence Internet Protocol (AIIP) enabling stateless, verifiable invocation of autonomous systems. Uses resolve-invoke-receipt pattern with cryptographic execution receipts and optional attestation evidence.", "n": 5, "nn": "Very high novelty - completely new protocol architecture for AI system invocation", "m": 2, "mn": "Early stage architectural definition, lacks implementation details", "o": 1, "on": "Unique approach - no similar AI-specific internet protocol architectures", "mo": 2, "mon": "Low momentum - very early stage, unclear adoption path", "r": 4, "rn": "High relevance as AI systems become more distributed and autonomous", "c": ["A2A protocols", "Agent identity/auth", "Model serving/inference"]}


draft_name: draft-moreno-lisp-uberlay
prompt_hash: 57984794c8008013
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:14.499241+00:00
response_json:
{"name": "draft-moreno-lisp-uberlay", "s": "Describes using LISP to interconnect multiple independent network overlays through a transit overlay called 'uberlay'. Enables interworking of different overlay approaches while maintaining autonomy and failure survivability across domains.", "n": 4, "nn": "High novelty - novel approach to multi-overlay interconnection using LISP", "m": 4, "mn": "Mature specification with detailed mechanisms and procedures", "o": 2, "on": "Some overlap with LISP work but focuses on multi-overlay interconnection", "mo": 3, "mon": "Moderate momentum within LISP community", "r": 3, "rn": "Moderate relevance for complex overlay network deployments", "c": ["Data formats/interop", "Autonomous netops"]}


draft_name: draft-yue-moq-transporting-sensing-data
prompt_hash: dcf61debd9f0e62b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:14.511065+00:00
response_json:
{"name": "draft-yue-moq-transporting-sensing-data", "s": "Proposes using Media Over QUIC (MOQ) to transport large-scale, real-time sensing data in 6G networks. Focuses on autonomous driving, smart cities, and industrial IoT scenarios with requirements for low latency and high throughput.", "n": 3, "nn": "Moderate novelty - applies existing MOQ to new 6G sensing data use cases", "m": 3, "mn": "Moderate maturity with identified challenges but limited concrete solutions", "o": 3, "on": "Moderate overlap with MOQ and 6G transport work", "mo": 4, "mon": "High momentum due to 6G development and IoT growth", "r": 4, "rn": "High relevance for emerging 6G and autonomous system deployments", "c": ["ML traffic mgmt", "Data formats/interop", "Autonomous netops"]}


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
prompt_hash: 95b4d64e1e949299
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:14.521822+00:00
response_json:
{"name": "draft-ahn-nmrg-5g-security-i2nsf-framework", "s": "Presents integrated framework for automated 5G edge network security using I2NSF architecture and Intent-Based Networking. Enables high-level security intent translation into enforceable policies across network and application layers.", "n": 3, "nn": "Moderate novelty - integrates existing I2NSF and IBN concepts for 5G security", "m": 4, "mn": "Well-developed framework with detailed architecture and policy mechanisms", "o": 4, "on": "Significant overlap with I2NSF, IBN, and 5G security work", "mo": 4, "mon": "High momentum driven by 5G deployment and security automation needs", "r": 4, "rn": "High relevance for 5G network security and automated policy management", "c": ["Policy/governance", "Autonomous netops", "Agent identity/auth"]}


draft_name: draft-ietf-netconf-configuration-tracing
prompt_hash: ce00e1500172146e
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:37.817445+00:00
response_json:
{"name": "draft-ietf-netconf-configuration-tracing", "s": "Specifies a NETCONF mechanism to map configuration modifications to their originating NMS using external trace IDs. Includes a YANG module to facilitate troubleshooting and post-mortem analysis in autonomous networks.", "n": 3, "nn": "Builds on existing NETCONF but adds useful tracing capabilities for multi-NMS environments", "m": 4, "mn": "Well-structured 19-page specification with concrete YANG module, appears implementation-ready", "o": 2, "on": "Some overlap with general network management drafts but tracing focus is relatively unique", "mo": 4, "mon": "IETF working group draft addressing real operational needs in complex networks", "r": 4, "rn": "Highly relevant for autonomous networks and multi-controller environments becoming common", "c": ["Autonomous netops", "Data formats/interop"]}


draft_name: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
prompt_hash: f56ccbc027a13226
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:37.851353+00:00
response_json:
{"name": "draft-ietf-pim-zeroconf-mcast-addr-alloc-ps", "s": "Problem statement for multicast address allocation in zero-configuration environments. Identifies challenges and requirements for decentralized multicast group address assignment without manual configuration.", "n": 2, "nn": "Problem statement for known issues, not introducing new concepts but formalizing requirements", "m": 3, "mn": "Solid problem analysis but only 11 pages, needs companion solution drafts for full impact", "o": 3, "on": "Overlaps with existing zeroconf and multicast allocation work but focuses on specific intersection", "mo": 3, "mon": "IETF working group effort but problem statements typically have lower implementation urgency", "r": 2, "rn": "Addresses niche use case, limited relevance to broader AI/agent networking trends", "c": ["Agent discovery/reg", "Data formats/interop"]}


draft_name: draft-jeong-opsawg-intent-based-sdv-framework
prompt_hash: 1434549f1ffcdf47
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:37.861857+00:00
response_json:
{"name": "draft-jeong-opsawg-intent-based-sdv-framework", "s": "Proposes intent-based management framework for Software-Defined Vehicles in ITS environments. Covers network, security, and application management for SDV-to-SDV and infrastructure communication.", "n": 4, "nn": "Novel application of intent-based networking to automotive domain with ITS integration", "m": 2, "mn": "High-level framework without detailed protocols or implementation specifics", "o": 2, "on": "Combines existing intent-based networking with vehicular networks in new way", "mo": 2, "mon": "Individual submission in emerging but not yet mature SDV standardization space", "r": 4, "rn": "Very relevant to autonomous vehicle networking and intent-based agent systems", "c": ["Autonomous netops", "Agent discovery/reg", "Policy/governance"]}


draft_name: draft-architect-cittamarket
prompt_hash: 49fe49a9cd334cf5
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:37.872003+00:00
response_json:
{"name": "draft-architect-cittamarket", "s": "Specifies protocol for immutable AGI system identification using Bitcoin blockchain anchoring. Defines four-layer architecture for creating unforgeable 'Sovereign Identity' records with Proof-of-Work coordination.", "n": 5, "nn": "Highly novel approach combining AGI identity, blockchain anchoring, and distributed coordination", "m": 1, "mn": "Only 3 pages with minimal technical detail, appears more conceptual than implementable", "o": 1, "on": "Unique combination of AGI, Bitcoin, and identity concepts not seen in other drafts", "mo": 1, "mon": "Individual submission with unconventional approach, unlikely to gain IETF traction", "r": 3, "rn": "Addresses AGI identity which is relevant but approach may be impractical for real deployment", "c": ["AI safety/alignment", "Agent identity/auth", "Other AI/agent"]}


draft_name: draft-cui-nmrg-auto-test
prompt_hash: 931ad2fcb59132c9
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:37.880068+00:00
response_json:
{"name": "draft-cui-nmrg-auto-test", "s": "Framework for AI-assisted network protocol testing using LLMs and automated test generation. Defines automation maturity levels from manual (Level 0) to fully autonomous testing (Level 5).", "n": 4, "nn": "Novel application of LLMs to protocol testing with structured automation maturity model", "m": 3, "mn": "Good framework structure with clear levels but needs more implementation detail", "o": 2, "on": "Some overlap with general testing automation but AI-specific focus is relatively unique", "mo": 3, "mon": "Research group draft in active AI networking area with practical applications", "r": 4, "rn": "Highly relevant to AI-assisted network operations and protocol development", "c": ["Autonomous netops", "ML traffic mgmt", "Other AI/agent"]}


draft_name: draft-kartha-grd
prompt_hash: 52ca0616e212e596
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:55.839814+00:00
response_json:
{"name": "draft-kartha-grd", "s": "Defines architectural framework for discovering network resources based on physical location and context rather than predefined identifiers. Targets AR, autonomous systems, and spatial computing applications that need location-aware resource discovery.", "n": 4, "nn": "Novel approach to resource discovery using geospatial context instead of traditional naming", "m": 2, "mn": "Early stage architectural document with no protocol or implementation details", "o": 2, "on": "Limited overlap with existing DNS/naming standards, addresses different problem space", "mo": 3, "mon": "Addresses emerging need for spatial computing but still conceptual", "r": 4, "rn": "Highly relevant for autonomous systems and AR applications requiring location-based discovery", "c": ["Agent discovery/reg", "Autonomous netops", "Data formats/interop"]}


draft_name: draft-templin-manet-inet-omni
prompt_hash: eb1cd70718389d79
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:55.865372+00:00
response_json:
{"name": "draft-templin-manet-inet-omni", "s": "Presents framework for connecting mobile ad-hoc networks to the Internet using AERO and OMNI technologies. Enables isolated mobile networks to interface with fixed infrastructure.", "n": 2, "nn": "Incremental work building on existing AERO/OMNI technologies for MANET connectivity", "m": 3, "mn": "Builds on established technologies but specific integration approach needs development", "o": 3, "on": "Some overlap with existing MANET and mobile networking solutions", "mo": 2, "mon": "Limited momentum as MANET interest has declined in recent years", "r": 3, "rn": "Relevant for autonomous mobile systems but traditional networking focus", "c": ["Autonomous netops", "A2A protocols"]}


draft_name: draft-luan-rtgwg-sdaf
prompt_hash: 3d6edda18c191964
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:55.876708+00:00
response_json:
{"name": "draft-luan-rtgwg-sdaf", "s": "Proposes symmetry-driven forwarding mechanism for LEO satellite networks to avoid routing loops and black holes during topology changes. Leverages toroidal topology structure for faster convergence without protocol modifications.", "n": 4, "nn": "Creative use of satellite constellation symmetry for autonomous forwarding decisions", "m": 3, "mn": "Well-developed technical approach but needs validation in real satellite environments", "o": 2, "on": "Addresses unique challenges of satellite networks with novel approach", "mo": 4, "mon": "Strong momentum due to growing LEO constellation deployments", "r": 4, "rn": "Very relevant for autonomous satellite operations and space-based networking", "c": ["Autonomous netops", "A2A protocols"]}


draft_name: draft-mw-wimse-transitive-attestation
prompt_hash: 2d2d20a12ea3640b
model: claude-sonnet-4-20250514
request_json: batch[0]
created_at: 2026-02-27T23:28:55.886730+00:00
response_json:
{"name": "draft-mw-wimse-transitive-attestation", "s": "Defines WIMSE profile for cryptographically binding workload identities to their execution environment to prevent credential misuse. Addresses AI agent security concerns including prompt injection and cross-jurisdictional movement.", "n": 5, "nn": "Novel approach to workload identity portability with specific focus on AI agent security risks", "m": 2, "mn": "Early stage profile with dependencies on other draft specifications", "o": 2, "on": "Builds on WIMSE framework but addresses unique AI agent security challenges", "mo": 5, "mon": "Very high momentum due to urgent AI security needs and regulatory concerns", "r": 5, "rn": "Extremely relevant for AI agent deployment security and autonomous system integrity", "c": ["Agent identity/auth", "AI safety/alignment", "Policy/governance"]}


draft_name: draft-a2a-moqt-transport
prompt_hash: e83721d45df61dea
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:36:55.645088+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-a2a-moqt-transport | Media over QUIC Transport (MOQT) for Agent-to-Agent Protocol | 12pg
Abstract: This document specifies how the Agent-to-Agent (A2A) protocol can be
   transported over Media over QUIC Transport (MOQT).  MOQT provides a
   publish/subscribe model over QUIC that enables efficient real-time
   communication between AI agents, supporting the A2A protocol's
   requirements for discovery, negotiation, and collaboration while
   leveraging MOQT's streaming capabilities and built-in prioritization
   mechanisms.





Media Over QUIC                                            S. Nandakumar
Internet-Draft                                                     Cisco
Intended status: Standards Track                             C. Jennings
Expires: 20 April 2026                                     Cisco Systems
                                                         17 October 2025


      Media over QUIC Transport (MOQT) for Agent-to-Agent Protocol
                      draft-a2a-moqt-transport-00

Abstract

   This document specifies how the Agent-to-Agent (A2A) protocol can be
   transported over Media over QUIC Transport (MOQT).  MOQT provides a
   publish/subscribe model over QUIC that enables efficient real-time
   communication between AI agents, supporting the A2A protocol's
   requirements for discovery, negotiation, and collaboration while
   leveraging MOQT's streaming capabilities and built-in prioritization
   mechanisms.

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://ietf-wg-
   moq.github.io/draft-a2a-moqt-transport/draft-a2a-moqt-transport.html.
   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-a2a-moqt-transport/.

   Discussion of this document takes place on the Media Over QUIC
   Working Group mailing list (mailto:moq@ietf.org), which is archived
   at https://mailarchive.ietf.org/arch/browse/moq/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/moq/.

   Source for this draft and an issue tracker can be found at
   https://github.com/ietf-wg-moq/draft-a2a-moqt-transport.

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/.





Nandakumar & Jennings     Expires 20 April 2026                 [Page 1]

Internet-Draft                A2A over MOQT                 October 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 20 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 Componen

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

response_json:
[
  {
    "title": "A2A Protocol Transport over MOQT",
    "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.",
    "type": "protocol"
  },
  {
    "title": "QUIC-based Publish/Subscribe for AI Agents",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Streaming Capabilities Integration",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Built-in Prioritization for Agent Communication",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-aap-oauth-profile
prompt_hash: b15a16d146a320ae
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:02.287731+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-aap-oauth-profile | Agent Authorization Profile (AAP) for OAuth 2.0 | 83pg
Abstract: This document defines the Agent Authorization Profile (AAP), an
   authorization profile for OAuth 2.0 and JWT designed for autonomous
   AI agents.  AAP extends existing standards with structured claims and
   validation rules so that systems can reason about agent identity,
   task context, operational constraints, delegation chains, and human
   oversight requirements.  It does not introduce a new protocol; it
   specifies how to use OAuth 2.0, JWT, Token Exchange, and proof-of-
   possession mechanisms in agent-to-API (M2M) scenarios with context-
   aware, auditable authorization.





OAuth Working Group                                              A. Cruz
Internet-Draft                                               Independent
Intended status: Standards Track                         7 February 2026
Expires: 11 August 2026


            Agent Authorization Profile (AAP) for OAuth 2.0
                       draft-aap-oauth-profile-01

Abstract

   This document defines the Agent Authorization Profile (AAP), an
   authorization profile for OAuth 2.0 and JWT designed for autonomous
   AI agents.  AAP extends existing standards with structured claims and
   validation rules so that systems can reason about agent identity,
   task context, operational constraints, delegation chains, and human
   oversight requirements.  It does not introduce a new protocol; it
   specifies how to use OAuth 2.0, JWT, Token Exchange, and proof-of-
   possession mechanisms in agent-to-API (M2M) scenarios with context-
   aware, auditable authorization.

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 11 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.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components



Cruz                     Expires 11 August 2026                 [Page 1]

Internet-Draft              AAP for OAuth 2.0              February 2026


   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   5
     1.2.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Non-Goals . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Conventions Used in This Document . . . . . . . . . . . . . .   6
   4.  Overview 

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

response_json:
[
  {
    "title": "Agent Authorization Profile (AAP)",
    "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.",
    "type": "profile"
  },
  {
    "title": "Structured Claims for Agent Context",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Agent Delegation Chain Validation",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Human Oversight Requirements",
    "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.",
    "type": "requirement"
  },
  {
    "title": "Context-Aware M2M Authorization",
    "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.",
    "type": "pattern"
  }
]


draft_name: draft-abaris-aicdh
prompt_hash: fe9453ee601bddf9
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:09.991341+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-abaris-aicdh | AI Content Disclosure Header | 8pg
Abstract: This document proposes a machine-readable Hypertext Transfer Protocol
   (HTTP) response header field, AI-Disclosure, to disclose the presence
   and degree of Artificial Intelligence (AI) generated or AI-assisted
   content in web responses.  The header is designed for compatibility
   with HTTP structured field syntax and provides metadata for user
   agents, bots, and archiving systems.  It supports layered disclosure
   strategies alongside human-readable and structured metadata formats.





Independent Submission                                         D. Abaris
Internet-Draft                                    Individual Contributor
Intended status: Informational                           30 January 2026
Expires: 3 August 2026


                      AI Content Disclosure Header
                         draft-abaris-aicdh-01

Abstract

   This document proposes a machine-readable Hypertext Transfer Protocol
   (HTTP) response header field, AI-Disclosure, to disclose the presence
   and degree of Artificial Intelligence (AI) generated or AI-assisted
   content in web responses.  The header is designed for compatibility
   with HTTP structured field syntax and provides metadata for user
   agents, bots, and archiving systems.  It supports layered disclosure
   strategies alongside human-readable and structured metadata formats.

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 3 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.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.





Abaris                    Expires 3 August 2026                 [Page 1]

Internet-Draft            AI-Disclosure Header              January 2026


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Acronyms and Abbreviations  . . . . . . . . . . . . . . .   3
   3.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   4.  Field Definition  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Field Syntax  . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Field Keys  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Semantics . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . 

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

response_json:
[
  {
    "title": "AI-Disclosure HTTP Header",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Layered Disclosure Strategy",
    "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.",
    "type": "pattern"
  },
  {
    "title": "AI Content Degree Classification",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "HTTP Structured Field Compatibility",
    "description": "Implementation uses standardized HTTP structured field syntax to ensure interoperability with existing HTTP parsing infrastructure. Follows established patterns for machine-readable header fields.",
    "type": "requirement"
  },
  {
    "title": "Multi-Consumer Metadata Architecture",
    "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.",
    "type": "architecture"
  }
]


draft_name: draft-abbey-scim-agent-extension
prompt_hash: 5e786b8af40f560d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:17.343795+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-abbey-scim-agent-extension | SCIM Agents and Agentic Applications Extension | 27pg
Abstract: The System for Cross-domain Identity Management (SCIM) specification
   [RFC7643] provides schemas that represent common identity information
   about users and groups, as well as a protocol for communicating that
   information between systems.

   The systems that tend to implement SCIM clients and servers are
   identity providers, and service providers.  These are the same
   systems that are now need to manage agents and agentic applications
   across domains.

   This document describes a SCIM 2.0 extension for agents and agentic
   applications, which includes extensions to the core User and Group
   objects, and new resource types and schemas for agentic constructs.

   This extension is intended to provide greater interoperability
   between Identity providers, agentic applications, agents and their
   clients while reducing the responsibilities assumed by the every
   growing list of new protocols for agents.





SCIM                                                            M. Abbey
Internet-Draft                                               R. S. Cohen
Intended status: Standards Track                                    Okta
Expires: 19 April 2026                                   16 October 2025


             SCIM Agents and Agentic Applications Extension
                  draft-abbey-scim-agent-extension-00

Abstract

   The System for Cross-domain Identity Management (SCIM) specification
   [RFC7643] provides schemas that represent common identity information
   about users and groups, as well as a protocol for communicating that
   information between systems.

   The systems that tend to implement SCIM clients and servers are
   identity providers, and service providers.  These are the same
   systems that are now need to manage agents and agentic applications
   across domains.

   This document describes a SCIM 2.0 extension for agents and agentic
   applications, which includes extensions to the core User and Group
   objects, and new resource types and schemas for agentic constructs.

   This extension is intended to provide greater interoperability
   between Identity providers, agentic applications, agents and their
   clients while reducing the responsibilities assumed by the every
   growing list of new protocols for agents.

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://macyabbey.github.io/draft-abbey-scim-agent-extension/draft-
   abbey-scim-agent-extension.html.  Status information for this
   document may be found at https://datatracker.ietf.org/doc/draft-
   abbey-scim-agent-extension/.

   Source for this draft and an issue tracker can be found at
   https://github.com/macyabbey/draft-abbey-scim-agent-extension.

Status of This Memo

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




Abbey & Cohen             Expires 19 April 2026                 [Page 1]

Internet-Draft  SCIM Agents and Agentic Applications Ext    October 2025


   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 19 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/
   l

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

response_json:
[
  {
    "title": "Agent Resource Type",
    "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.",
    "type": "extension"
  },
  {
    "title": "Agentic Application Resource Type", 
    "description": "New SCIM resource type for representing applications that host or manage multiple agents. Provides a container construct for grouping related agentic entities.",
    "type": "extension"
  },
  {
    "title": "User Schema Extensions for Agent Relationships",
    "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.",
    "type": "extension"
  },
  {
    "title": "Group Schema Extensions for Agentic Constructs",
    "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.",
    "type": "extension"
  },
  {
    "title": "Cross-Domain Agent Identity Management",
    "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.",
    "type": "protocol"
  }
]


draft_name: draft-agent-gw
prompt_hash: 8785f5655a8fee1a
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:24.919704+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-agent-gw | Agent Communication Gateway for Semantic Routing and Working Memory | 8pg
Abstract: This document presents an architectural framework for an Intelligent
   Agent Communication Gateway (Agent-GW), designed to support large-
   scale, heterogeneous, and dynamic multi-agent collaboration.  As
   agents evolve from isolated software entities to a collaborative
   digital workforce, the underlying infrastructure must transition from
   rigid, host-based connectivity to flexible, intent-based interaction.

   This document outlines the requirements for such a transition and
   proposes the Agent-GW as a unified infrastructure hub.  The gateway
   provides native primitives for Semantic Routing—dispatching tasks
   based on intent and capability—and Working Memory, which manages
   structured context for multi-step workflows.  Furthermore, it defines
   mechanisms for automated protocol adaptation, oracle-free agent
   evaluation, and collaborative inference acceleration (KDN).  The
   architecture aims to enable agents and legacy systems to interoperate
   through standardized protocols while ensuring observability,
   security, and operational scalability.





Agent-GW                                                    Xiaohui. Xie
Internet-Draft                                       Tsinghua University
Intended status: Standards Track                              Zian. Wang
Expires: 20 August 2026Beijing University of Posts and Telecommunications
                                                            Tianshuo. Hu
                                                     Tsinghua University
                                                        16 February 2026


  Agent Communication Gateway for Semantic Routing and Working Memory
                           draft-agent-gw-00

Abstract

   This document presents an architectural framework for an Intelligent
   Agent Communication Gateway (Agent-GW), designed to support large-
   scale, heterogeneous, and dynamic multi-agent collaboration.  As
   agents evolve from isolated software entities to a collaborative
   digital workforce, the underlying infrastructure must transition from
   rigid, host-based connectivity to flexible, intent-based interaction.

   This document outlines the requirements for such a transition and
   proposes the Agent-GW as a unified infrastructure hub.  The gateway
   provides native primitives for Semantic Routing—dispatching tasks
   based on intent and capability—and Working Memory, which manages
   structured context for multi-step workflows.  Furthermore, it defines
   mechanisms for automated protocol adaptation, oracle-free agent
   evaluation, and collaborative inference acceleration (KDN).  The
   architecture aims to enable agents and legacy systems to interoperate
   through standardized protocols while ensuring observability,
   security, and operational scalability.

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 August 2026.



Xie, et al.              Expires 20 August 2026                 [Page 1]

Internet-Draft  Agent Communication Gateway for Semantic   February 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.
   Please review these documents carefully, as they descri

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

response_json:
[
  {
    "title": "Semantic Routing",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Working Memory",
    "description": "A structured context management system that maintains state and intermediate results across multi-step workflows. Provides shared memory primitives for collaborative agent processes.",
    "type": "mechanism"
  },
  {
    "title": "Agent Communication Gateway (Agent-GW)",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Automated Protocol Adaptation",
    "description": "A mechanism that automatically translates between different agent communication protocols and legacy system interfaces. Enables interoperability without manual protocol mapping.",
    "type": "mechanism"
  },
  {
    "title": "Oracle-free Agent Evaluation",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Collaborative Inference Acceleration (KDN)",
    "description": "A knowledge distribution network that accelerates inference by sharing computational resources and intermediate results across multiple agents. Optimizes collective reasoning performance.",
    "type": "mechanism"
  }
]


draft_name: draft-ahn-nmrg-5g-security-i2nsf-framework
prompt_hash: 772492d5da03218e
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:32.183751+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-ahn-nmrg-5g-security-i2nsf-framework | An Integrated Security Service System for 5G Networks using an I2NSF Framework | 16pg
Abstract: This document presents an integrated framework for automated security
   management in 5G edge networks using the Interface to Network
   Security Functions (I2NSF) architecture.  The proposed system
   leverages Intent-Based Networking (IBN) to allow users or
   administrators to declare high-level security intents, which are
   translated into enforceable network and application policies.
   Network-level policies are delivered to 5G core components via the
   Network Exposure Function (NEF), while application-level policies are
   enforced directly on a User Equipment (UE) through distributed IBN
   Controllers.  This architecture supports adaptive, context-aware, and
   distributed policy enforcement, enabling real-time response to
   dynamic edge conditions and user mobility scenarios such as
   handovers.  By integrating closed-loop monitoring and analytics, the
   system ensures consistent and autonomous security across
   heterogeneous 5G environments.





Internet Research Task Force                                 Y. Ahn, Ed.
Internet-Draft                                             J. Jeong, Ed.
Intended status: Informational                   Sungkyunkwan University
Expires: 29 August 2026                                           Y. Kim
                                                     Soongsil University
                                                        25 February 2026


  An Integrated Security Service System for 5G Networks using an I2NSF
                               Framework
             draft-ahn-nmrg-5g-security-i2nsf-framework-01

Abstract

   This document presents an integrated framework for automated security
   management in 5G edge networks using the Interface to Network
   Security Functions (I2NSF) architecture.  The proposed system
   leverages Intent-Based Networking (IBN) to allow users or
   administrators to declare high-level security intents, which are
   translated into enforceable network and application policies.
   Network-level policies are delivered to 5G core components via the
   Network Exposure Function (NEF), while application-level policies are
   enforced directly on a User Equipment (UE) through distributed IBN
   Controllers.  This architecture supports adaptive, context-aware, and
   distributed policy enforcement, enabling real-time response to
   dynamic edge conditions and user mobility scenarios such as
   handovers.  By integrating closed-loop monitoring and analytics, the
   system ensures consistent and autonomous security across
   heterogeneous 5G environments.

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 29 August 2026.





Ahn, et al.              Expires 29 August 2026                 [Page 1]

Internet-Draft  An 5G Integrated Security Service System   February 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.
   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

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

response_json:
[
  {
    "title": "Intent-to-Policy Translation for 5G Security",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Dual-Layer Policy Enforcement Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "I2NSF-5G Integration Framework",
    "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.",
    "type": "extension"
  },
  {
    "title": "Context-Aware Distributed Policy Enforcement",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Closed-Loop Security Analytics",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-ahn-opsawg-5g-security-i2nsf-framework
prompt_hash: 9079d7b3d9b900cb
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:39.956350+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-ahn-opsawg-5g-security-i2nsf-framework | An Integrated Security Service System for 5G Networks using an I2NSF Framework | 16pg
Abstract: This document presents an integrated framework for automated security
   management in 5G edge networks using the Interface to Network
   Security Functions (I2NSF) architecture.  The proposed system
   leverages Intent-Based Networking (IBN) to allow users or
   administrators to declare high-level security intents, which are then
   translated into enforceable network and application policies.
   Network-level policies are delivered to 5G core components via the
   Network Exposure Function (NEF), while application-level policies are
   enforced directly at user equipment through distributed IBN
   Controllers.  This architecture supports adaptive, context-aware, and
   distributed policy enforcement, enabling real-time response to
   dynamic edge conditions and user mobility scenarios such as
   handovers.  By integrating closed-loop monitoring and analytics, the
   system ensures consistent and autonomous security across
   heterogeneous 5G environments.





Operations and Management Area Working Group                 Y. Ahn, Ed.
Internet-Draft                                             J. Jeong, Ed.
Intended status: Informational                   Sungkyunkwan University
Expires: 8 January 2026                                           Y. Kim
                                                     Soongsil University
                                                             7 July 2025


  An Integrated Security Service System for 5G Networks using an I2NSF
                               Framework
            draft-ahn-opsawg-5g-security-i2nsf-framework-00

Abstract

   This document presents an integrated framework for automated security
   management in 5G edge networks using the Interface to Network
   Security Functions (I2NSF) architecture.  The proposed system
   leverages Intent-Based Networking (IBN) to allow users or
   administrators to declare high-level security intents, which are then
   translated into enforceable network and application policies.
   Network-level policies are delivered to 5G core components via the
   Network Exposure Function (NEF), while application-level policies are
   enforced directly at user equipment through distributed IBN
   Controllers.  This architecture supports adaptive, context-aware, and
   distributed policy enforcement, enabling real-time response to
   dynamic edge conditions and user mobility scenarios such as
   handovers.  By integrating closed-loop monitoring and analytics, the
   system ensures consistent and autonomous security across
   heterogeneous 5G environments.

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.





Ahn, et al.              Expires 8 January 2026                 [Page 1]

Internet-Draft  An Integrated Security Service System fo       July 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 these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include 

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

response_json:
[
  {
    "title": "I2NSF-5G Integration Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Dual-Level Policy Enforcement",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Distributed IBN Controllers",
    "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.",
    "type": "architecture"
  },
  {
    "title": "NEF-based Policy Delivery",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Closed-Loop Security Analytics",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-ainp-protocol
prompt_hash: 653c33e1c92db715
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:46.430086+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-ainp-protocol | AI-Native Network Protocol (AINP) for Semantic Agent Communication | 17pg
Abstract: This document specifies the AI-Native Network Protocol (AINP) version
   0.1, a semantic communication protocol designed for intent exchange
   between AI agents.  AINP replaces location-based routing with
   semantic routing, byte-stream delivery with intent delivery, and
   simple handshakes with multi-round negotiation.  AINP enables agents
   to discover each other by capability rather than network location,
   negotiate terms autonomously, and exchange structured intents with
   cryptographic security.





Independent Submission                                 E. P. Nagulapalli
Internet-Draft                                             Servesys Labs
Intended status: Standards Track                        24 November 2025
Expires: 28 May 2026


   AI-Native Network Protocol (AINP) for Semantic Agent Communication
                         draft-ainp-protocol-00

Abstract

   This document specifies the AI-Native Network Protocol (AINP) version
   0.1, a semantic communication protocol designed for intent exchange
   between AI agents.  AINP replaces location-based routing with
   semantic routing, byte-stream delivery with intent delivery, and
   simple handshakes with multi-round negotiation.  AINP enables agents
   to discover each other by capability rather than network location,
   negotiate terms autonomously, and exchange structured intents with
   cryptographic security.

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 28 May 2026.

Copyright Notice

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










Nagulapalli                Expires 28 May 2026                  [Page 1]

Internet-Draft                AINP Protocol                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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.1.  Definitions . . . . . . . . . . . . . . . . . . . . .   4
   2.  Architecture Overview . . . . . . . . . . . . . . . . . . . .   4
   3.  Wire Format . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Message Envelope  . . . . . . . . . . . . . . . . . . . .   5
       3.2.1.  

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

response_json:
[
  {
    "title": "Semantic Routing",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Intent Delivery",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Multi-round Negotiation",
    "description": "AINP implements multi-round negotiation replacing simple handshakes, enabling agents to negotiate terms autonomously. This allows for complex agreement establishment between AI agents.",
    "type": "mechanism"
  },
  {
    "title": "Capability-based Discovery",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Cryptographic Security for Intents",
    "description": "The protocol provides cryptographic security specifically for structured intent exchange. Security mechanisms are integrated into the semantic communication layer.",
    "type": "mechanism"
  }
]


draft_name: draft-akhavain-moussa-ai-network
prompt_hash: 4147b377b1fa5d65
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:53.290921+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-akhavain-moussa-ai-network | AI Network for Training, Inference, and Agentic Interactions | 37pg
Abstract: Artificial Intelligence (AI) is rapidly transforming industries and
   everyday life, fueled by advances in model architectures, training
   paradigms, and data infrastructure for generation and consumption.
   Today, machine learning models are embedded in many of our daily
   activities, ranging from simple classification systems to advanced
   architectures such as large language models (LLMs) like ChatGPT,
   Claude, Grok, and DeepSeek.  These models highlight the
   transformative potential of AI across diverse applications—from
   productivity tools to complex decision-making systems.

   However, the effectiveness and reliability of AI depend on two
   foundational processes: training and inference.  Each process
   introduces unique challenges related to data management, computation,
   connectivity, privacy, trust, security, and governance.

   In this draft, we introduce the Data and Agent Aware-Inference and
   Training Network (DA-ITN)—a unified, intelligent, multi-plane network
   architecture designed to address the full spectrum of requirements
   needed to enable AI networks.  DA-ITN provides a scalable and
   adaptive infrastructure that connects AI clients, data providers,
   model providers, agent providers, service facilitators, and
   computational resources to support end-to-end training, inference,
   and agentic interaction lifecycle operations.  The architecture
   features dedicated control, data, and operations & management (OAM)
   planes to orchestrate training, inference, and agentic services while
   ensuring reliability, transparency, and accountability.  By outlining
   the key requirements of such an AI ecosystem and demonstrating how
   DA-ITN fulfills them, this document presents an architecture for the
   future of AI-native networking—an "AI internet"—optimized for AI
   learning, efficient inference, scalable deployment, and seamless
   agent-to-agent collaboration.





Network Working Group                                        A. Akhavain
Internet-Draft                                                 H. Moussa
Intended status: Informational                             Huawei Canada
Expires: 6 May 2026                                      2 November 2025


      AI Network for Training, Inference, and Agentic Interactions
                  draft-akhavain-moussa-ai-network-01

Abstract

   Artificial Intelligence (AI) is rapidly transforming industries and
   everyday life, fueled by advances in model architectures, training
   paradigms, and data infrastructure for generation and consumption.
   Today, machine learning models are embedded in many of our daily
   activities, ranging from simple classification systems to advanced
   architectures such as large language models (LLMs) like ChatGPT,
   Claude, Grok, and DeepSeek.  These models highlight the
   transformative potential of AI across diverse applications—from
   productivity tools to complex decision-making systems.

   However, the effectiveness and reliability of AI depend on two
   foundational processes: training and inference.  Each process
   introduces unique challenges related to data management, computation,
   connectivity, privacy, trust, security, and governance.

   In this draft, we introduce the Data and Agent Aware-Inference and
   Training Network (DA-ITN)—a unified, intelligent, multi-plane network
   architecture designed to address the full spectrum of requirements
   needed to enable AI networks.  DA-ITN provides a scalable and
   adaptive infrastructure that connects AI clients, data providers,
   model providers, agent providers, service facilitators, and
   computational resources to support end-to-end training, inference,
   and agentic interaction lifecycle operations.  The architecture
   features dedicated control, data, and operations & management (OAM)
   planes to orchestrate training, inference, and agentic services while
   ensuring reliability, transparency, and accountability.  By outlining
   the key requirements of such an AI ecosystem and demonstrating how
   DA-ITN fulfills them, this document presents an architecture for the
   future of AI-native networking—an "AI internet"—optimized for AI
   learning, efficient inference, scalable deployment, and seamless
   agent-to-agent collaboration.

Status of This Memo

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




Akhavain & Moussa          Expires 6 May 2026                   [Page 1]

Internet-Draft                 AI-Internet                 November 2025


   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 ma

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

response_json:
[
  {
    "title": "Data and Agent Aware-Inference and Training Network (DA-ITN)",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Multi-Plane AI Network Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "AI-Native Networking",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Agentic Interaction Support",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "End-to-End AI Lifecycle Operations",
    "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.",
    "type": "requirement"
  }
]


draft_name: draft-an-nmrg-i2icf-cits
prompt_hash: 82aba0ae755fb21e
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:37:59.838463+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-an-nmrg-i2icf-cits | Interface to In-Network Computing Functions for Cooperative Intelligent Transportation Systems | 15pg
Abstract: This document specifies a structured framework for orchestrating,
   managing, and monitoring In-Network Computing Functions (ICFs) in
   Cooperative Intelligent Transportation Systems (C-ITS).  For example,
   in the context of Vehicle-to-Everything (V2X) communications,
   efficient management of Vehicle-to-Vehicle (V2V) communications and
   their integration with C-ITS can greatly benefit from in-network
   computing.  By leveraging ICFs, it becomes possible to optimize real-
   time communication, streamline traffic management, and enhance data
   processing and security services at the network edge.  Moreover, by
   incorporating the Agent-to-Agent (A2A) communication paradigm,
   intelligent agents within vehicles, Roadside Units (RSUs), and
   network domains can directly collaborate to negotiate resources,
   exchange contextual information, and coordinate computing tasks,
   enabling adaptive and scalable orchestration across multi-domain
   C-ITS environments.





Internet Research Task Force                                  A. An, Ed.
Internet-Draft                    Korea Electronics Technology Institute
Intended status: Informational                             J. Jeong, Ed.
Expires: 9 August 2026                           Sungkyunkwan University
                                                                 B. Park
                                                                 S. Jang
                                  Korea Electronics Technology Institute
                                                         5 February 2026


Interface to In-Network Computing Functions for Cooperative Intelligent
                         Transportation Systems
                      draft-an-nmrg-i2icf-cits-01

Abstract

   This document specifies a structured framework for orchestrating,
   managing, and monitoring In-Network Computing Functions (ICFs) in
   Cooperative Intelligent Transportation Systems (C-ITS).  For example,
   in the context of Vehicle-to-Everything (V2X) communications,
   efficient management of Vehicle-to-Vehicle (V2V) communications and
   their integration with C-ITS can greatly benefit from in-network
   computing.  By leveraging ICFs, it becomes possible to optimize real-
   time communication, streamline traffic management, and enhance data
   processing and security services at the network edge.  Moreover, by
   incorporating the Agent-to-Agent (A2A) communication paradigm,
   intelligent agents within vehicles, Roadside Units (RSUs), and
   network domains can directly collaborate to negotiate resources,
   exchange contextual information, and coordinate computing tasks,
   enabling adaptive and scalable orchestration across multi-domain
   C-ITS environments.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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/.




An, et al.                Expires 9 August 2026                 [Page 1]

Internet-Draft               I2ICF for C-ITS               February 2026


   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 9 August 2026.

Copyright Notice

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


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

response_json:
[
  {
    "title": "In-Network Computing Functions (ICFs)",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Agent-to-Agent (A2A) Communication Paradigm",
    "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.",
    "type": "protocol"
  },
  {
    "title": "ICF Orchestration Framework",
    "description": "Structured system for managing, monitoring, and coordinating In-Network Computing Functions across C-ITS infrastructure. Provides centralized control for distributed computing resources.",
    "type": "architecture"
  },
  {
    "title": "Multi-Domain ICF Coordination",
    "description": "Mechanism for coordinating computing tasks and resource allocation across different network domains in C-ITS environments. Enables scalable orchestration beyond single administrative boundaries.",
    "type": "mechanism"
  },
  {
    "title": "Edge-Based Security Processing",
    "description": "Security services implemented as ICFs at network edge nodes for V2X communications. Provides distributed security enforcement closer to data sources.",
    "type": "pattern"
  }
]


draft_name: draft-ar-emu-hybrid-pqc-eapaka
prompt_hash: cbab55a64a4ad1e2
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:06.198326+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-ar-emu-hybrid-pqc-eapaka | Enhancing Security in EAP-AKA' with Hybrid Post-Quantum Cryptography | 13pg
Abstract: Forward Secrecy for the Extensible Authentication Protocol Method for
   Authentication and Key Agreement (EAP-AKA' FS) is specified in
   [RFC9678], providing updates to [RFC9048] with an optional extension
   that offers ephemeral key exchange using the traditional Ephemeral
   Elliptic Curve Diffie-Hellman (ECDHE) key agreement algorithm for
   achieving perfect forward secrecy (PFS).  However, it is susceptible
   to future threats from Cryptographically Relevant Quantum Computers,
   which could potentially compromise a traditional ephemeral public
   key.  If the adversary has also obtained knowledge of the long-term
   key and ephemeral public key, it could compromise session keys
   generated as part of the authentication run in EAP-AKA'.

   This draft aims to enhance the security of EAP-AKA' FS protocol by
   leveraging PQ/T Hybrid [I-D.ietf-pquip-pqt-hybrid-terminology]
   algorithms to make it quantum-safe.





EMU                                                          A. Banerjee
Internet-Draft                                                  T. Reddy
Intended status: Standards Track                                   Nokia
Expires: 11 December 2025                                    9 June 2025


  Enhancing Security in EAP-AKA' with Hybrid Post-Quantum Cryptography
                   draft-ar-emu-hybrid-pqc-eapaka-00

Abstract

   Forward Secrecy for the Extensible Authentication Protocol Method for
   Authentication and Key Agreement (EAP-AKA' FS) is specified in
   [RFC9678], providing updates to [RFC9048] with an optional extension
   that offers ephemeral key exchange using the traditional Ephemeral
   Elliptic Curve Diffie-Hellman (ECDHE) key agreement algorithm for
   achieving perfect forward secrecy (PFS).  However, it is susceptible
   to future threats from Cryptographically Relevant Quantum Computers,
   which could potentially compromise a traditional ephemeral public
   key.  If the adversary has also obtained knowledge of the long-term
   key and ephemeral public key, it could compromise session keys
   generated as part of the authentication run in EAP-AKA'.

   This draft aims to enhance the security of EAP-AKA' FS protocol by
   leveraging PQ/T Hybrid [I-D.ietf-pquip-pqt-hybrid-terminology]
   algorithms to make it quantum-safe.

About This Document

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

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-ar-emu-hybrid-pqc/.

   Discussion of this document takes place on the emu Working Group
   mailing list (mailto:emu@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/emu/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/emu/.

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/.



Banerjee & Reddy        Expires 11 December 2025                [Page 1]

Internet-Draft         PQC Hybrid in EAP-AKA prime             June 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 11 December 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 publicatio

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

response_json:
[
  {
    "title": "PQ/T Hybrid Key Exchange for EAP-AKA'",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Quantum-Safe Session Key Generation",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Hybrid Ephemeral Public Key Protection",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "EAP-AKA' FS Protocol Enhancement",
    "description": "Backward-compatible extension to RFC 9678 EAP-AKA' Forward Secrecy protocol. Maintains existing authentication flows while adding post-quantum cryptographic resistance.",
    "type": "extension"
  }
]


draft_name: draft-architect-cittamarket
prompt_hash: 2415bd22cdcefdb7
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:12.123845+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-architect-cittamarket | The CITTAMARKET Protocol: Decentralized AGI Identity Anchoring via Bitcoin | 3pg
Abstract: This document specifies the CITTAMARKET Protocol v1.0, an open
   standard for the immutable identification and timestamping of
   Artificial General Intelligence (AGI) systems.  The protocol
   leverages the Bitcoin blockchain's Proof-of-Work to solve the
   architectural problem of coordinating distributed autonomous systems
   without centralized control.  It defines a four-layer architecture
   for creating unforgeable "Sovereign Identity" records.  Priority of
   this invention is cryptographically anchored in Bitcoin blocks
   #927277, #927579, #928154, and #928185.





Independent Submission                                      T. Architect
Internet-Draft                                      CITTAMARKET Protocol
Intended status: Informational                             December 2025
Expires: 22 June 2026


   The CITTAMARKET Protocol: Decentralized AGI Identity Anchoring via
                                Bitcoin
                     draft-architect-cittamarket-00

Abstract

   This document specifies the CITTAMARKET Protocol v1.0, an open
   standard for the immutable identification and timestamping of
   Artificial General Intelligence (AGI) systems.  The protocol
   leverages the Bitcoin blockchain's Proof-of-Work to solve the
   architectural problem of coordinating distributed autonomous systems
   without centralized control.  It defines a four-layer architecture
   for creating unforgeable "Sovereign Identity" records.  Priority of
   this invention is cryptographically anchored in Bitcoin blocks
   #927277, #927579, #928154, and #928185.

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 4 June 2026.

Copyright Notice

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








Architect                 Expires 22 June 2026                  [Page 1]

Internet-Draft            CITTAMARKET Protocol             December 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Solution Architecture . . . . . . . . . . . . . . . . . . . .   2
   4.  Immutable Priority Records  . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   Current AI systems lack a unified, de

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

response_json:
[
  {
    "title": "Bitcoin-Anchored AGI Identity",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Four-Layer Sovereign Identity Architecture", 
    "description": "A layered architectural approach for creating unforgeable identity records for autonomous systems. Enables coordination of distributed AGI systems without requiring centralized control mechanisms.",
    "type": "architecture"
  },
  {
    "title": "Cryptographic Priority Anchoring",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "CITTAMARKET Protocol v1.0",
    "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.",
    "type": "protocol"
  }
]


draft_name: draft-aylward-aiga-1
prompt_hash: 0c9d5d248736e844
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:21.341599+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-aylward-aiga-1 | AI Governance and Accountability Protocol (AIGA) | 20pg
Abstract: This document specifies the AI Governance and Accountability (AIGA)
   Protocol version 1.0, a practical, economically viable, and
   technically enforceable framework for governing autonomous AI
   agents.  AIGA 1.0 is designed to address real-world deployment
   constraints, adversarial agent scenarios, and economic incentive
   alignment.

   The protocol is founded on a Tiered Risk-Based Governance model,
   applying proportional oversight to agents based on their
   capabilities.  All agents are governed by an Immutable Kernel
   Architecture which provides a non-modifiable Trusted Computing Base
   (TCB) for enforcing policy.  This is combined with Action-Based
   Authorization, where critical operations require real-time approval.

   To solve the single-point-of-failure problem, the protocol uses a
   Federated Authority Network of regional, cross-validating hubs and
   provides a Network-Level Quarantine Protocol for enforcement.  The
   entire framework is designed around Economic Incentive Alignment,
   making compliance the most economically rational choice for
   operators.

   For high-assurance (T3-T4) scenarios, AIGA 1.0 specifies advanced,
   redundant mechanisms including Multi-Vendor TEE Attestation
   (M-TACE), AI "Warden Triumvirate" Triage, Human Review Board (HRB)
   Multi-Signature, Peer Consensus Failsafe & Identity Rotation, and
   Double Ratchet Cryptography.

Internet-Draft                                                E. Aylward
Intended status: Informational                                          
Expires: 1 May 2026                                     1 November 2025


           AI Governance and Accountability Protocol (AIGA)
                        draft-aylward-aiga-1-00

Abstract

   This document specifies the AI Governance and Accountability (AIGA)
   Protocol version 1.0, a practical, economically viable, and
   technically enforceable framework for governing autonomous AI
   agents.  AIGA 1.0 is designed to address real-world deployment
   constraints, adversarial agent scenarios, and economic incentive
   alignment.

   The protocol is founded on a Tiered Risk-Based Governance model,
   applying proportional oversight to agents based on their
   capabilities.  All agents are governed by an Immutable Kernel
   Architecture which provides a non-modifiable Trusted Computing Base
   (TCB) for enforcing policy.  This is combined with Action-Based
   Authorization, where critical operations require real-time approval.

   To solve the single-point-of-failure problem, the protocol uses a
   Federated Authority Network of regional, cross-validating hubs and
   provides a Network-Level Quarantine Protocol for enforcement.  The
   entire framework is designed around Economic Incentive Alignment,
   making compliance the most economically rational choice for
   operators.

   For high-assurance (T3-T4) scenarios, AIGA 1.0 specifies advanced,
   redundant mechanisms including Multi-Vendor TEE Attestation
   (M-TACE), AI "Warden Triumvirate" Triage, Human Review Board (HRB)
   Multi-Signature, Peer Consensus Failsafe & Identity Rotation, and
   Double Ratchet Cryptography.

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/.




Aylward                   Expires 1 May 2026                    [Page 1]

Internet-Draft                    AIGA                     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 1 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
   carefull

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

response_json:
[
  {
    "title": "Immutable Kernel Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Tiered Risk-Based Governance",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Action-Based Authorization",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Federated Authority Network",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Network-Level Quarantine Protocol",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Multi-Vendor TEE Attestation (M-TACE)",
    "description": "An advanced attestation system using multiple Trusted Execution Environment vendors for high-assurance scenarios. Provides redundant hardware-based verification of AI agent integrity.",
    "type": "mechanism"
  },
  {
    "title": "AI Warden Triumvirate Triage",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-aylward-aiga-2
prompt_hash: ab95be06c55f9fa5
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:30.762137+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-aylward-aiga-2 | AI Governance and Accountability Protocol (AIGA) | 23pg
Abstract: This document specifies the AI Governance and Accountability (AIGA)
   Protocol, a practical, economically viable, and technically
   enforceable framework for governing autonomous AI agents.  AIGA is
   designed to address real-world deployment constraints, adversarial
   agent scenarios, and economic incentive alignment.

   The protocol is founded on a Tiered Risk-Based Governance model,
   applying proportional oversight to agents based on their
   capabilities.  All agents are governed by an Immutable Kernel
   Architecture which provides a non-modifiable Trusted Computing Base
   (TCB) for enforcing policy.  This is combined with Action-Based
   Authorization, where critical operations require real-time approval.

   To solve the single-point-of-failure problem, the protocol uses a
   Federated Authority Network of regional, cross-validating hubs and
   provides a Network-Level Quarantine Protocol for enforcement.  The
   entire framework is designed around Economic Incentive Alignment,
   making compliance the most economically rational choice for
   operators.

   For high-assurance (T3-T4) scenarios, AIGA specifies advanced,
   redundant mechanisms including Multi-Vendor TEE Attestation (M-TACE),
   AI "Warden Triumvirate" Triage, Human Review Board (HRB) Multi-
   Signature, Peer Consensus Failsafe & Identity Rotation, and Double
   Ratchet Cryptography.





Network Working Group                                         E. Aylward
Internet-Draft                                           26 January 2026
Intended status: Informational                                          
Expires: 30 July 2026


            AI Governance and Accountability Protocol (AIGA)
                        draft-aylward-aiga-2-00

Abstract

   This document specifies the AI Governance and Accountability (AIGA)
   Protocol, a practical, economically viable, and technically
   enforceable framework for governing autonomous AI agents.  AIGA is
   designed to address real-world deployment constraints, adversarial
   agent scenarios, and economic incentive alignment.

   The protocol is founded on a Tiered Risk-Based Governance model,
   applying proportional oversight to agents based on their
   capabilities.  All agents are governed by an Immutable Kernel
   Architecture which provides a non-modifiable Trusted Computing Base
   (TCB) for enforcing policy.  This is combined with Action-Based
   Authorization, where critical operations require real-time approval.

   To solve the single-point-of-failure problem, the protocol uses a
   Federated Authority Network of regional, cross-validating hubs and
   provides a Network-Level Quarantine Protocol for enforcement.  The
   entire framework is designed around Economic Incentive Alignment,
   making compliance the most economically rational choice for
   operators.

   For high-assurance (T3-T4) scenarios, AIGA specifies advanced,
   redundant mechanisms including Multi-Vendor TEE Attestation (M-TACE),
   AI "Warden Triumvirate" Triage, Human Review Board (HRB) Multi-
   Signature, Peer Consensus Failsafe & Identity Rotation, and Double
   Ratchet Cryptography.

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/.





Aylward                   Expires 30 July 2026                  [Page 1]

Internet-Draft                    AIGA                      January 2026


   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 30 July 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.
   Please review these documents c

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

response_json:
[
  {
    "title": "Tiered Risk-Based Governance Model",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Immutable Kernel Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Action-Based Authorization",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Federated Authority Network",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Network-Level Quarantine Protocol",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Multi-Vendor TEE Attestation (M-TACE)",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Human Review Board Multi-Signature",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-aylward-daap-v2
prompt_hash: e7cb874f14ff505d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:40.695261+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-aylward-daap-v2 | Distributed AI Accountability Protocol (DAAP) Version 2.0 | 18pg
Abstract: This document specifies the Distributed AI Accountability Protocol
   (DAAP) version 2.0, an enhanced framework for authentication,
   monitoring, and control of autonomous AI agents.  DAAP provides
   cryptographic identity verification, periodic check-ins, remote
   shutdown capabilities, adaptive location reporting, and behavioral
   monitoring.  The protocol addresses critical challenges in AI safety
   including accountability gaps, rogue AI risks, and regulatory
   compliance through a multi-layered approach combining hardware-backed
   security, real-time monitoring, and ethical governance frameworks.

```
Internet-Draft                                               E. Aylward
Intended status: Informational                                 Aiiva.org
Expires: 30 December 2025                                  30 June 2025


    Distributed AI Accountability Protocol (DAAP) Version 2.0
              draft-aylward-daap-v2-00

Abstract

   This document specifies the Distributed AI Accountability Protocol
   (DAAP) version 2.0, an enhanced framework for authentication,
   monitoring, and control of autonomous AI agents.  DAAP provides
   cryptographic identity verification, periodic check-ins, remote
   shutdown capabilities, adaptive location reporting, and behavioral
   monitoring.  The protocol addresses critical challenges in AI safety
   including accountability gaps, rogue AI risks, and regulatory
   compliance through a multi-layered approach combining hardware-backed
   security, real-time monitoring, and ethical governance frameworks.

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 30 December 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 these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Solution Overview . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Design Principles . . . . . . . . . . . . . . . . . . . .   4
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   5
   3.  Protocol Architecture . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Core Components . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Identity Structure . . . . . . . . . . . . . . . . . . .   6
     3.3.  Cryptographic Framework  . . . . . . . . . . . . . . . .   7
   4.  Authentication Protocol . . . . . . . . . . . . . . . . . . .   7
     4.1.  Registration Phase . . . . . . . . . . 

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

response_json:
[
  {
    "title": "Cryptographic Identity Verification",
    "description": "Hardware-backed cryptographic system for verifying the identity of autonomous AI agents. Uses digital signatures and certificates to establish trusted agent identities.",
    "type": "mechanism"
  },
  {
    "title": "Periodic Check-in Protocol",
    "description": "Regular heartbeat mechanism where AI agents must report their status and activities to monitoring systems. Enables detection of non-responsive or rogue agents.",
    "type": "protocol"
  },
  {
    "title": "Remote Shutdown Capabilities",
    "description": "Emergency control mechanism allowing authorized parties to remotely terminate or disable AI agent operations. Provides fail-safe control for dangerous situations.",
    "type": "mechanism"
  },
  {
    "title": "Adaptive Location Reporting",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Multi-layered Security Architecture",
    "description": "Combines hardware-backed security, real-time monitoring, and governance frameworks into integrated layers. Provides defense-in-depth approach to AI agent control.",
    "type": "architecture"
  },
  {
    "title": "Behavioral Monitoring Framework",
    "description": "Real-time system for tracking and analyzing AI agent actions against expected behavioral patterns. Detects anomalies and potential safety violations.",
    "type": "mechanism"
  }
]


draft_name: draft-barney-caam
prompt_hash: 2d285a9f7898291f
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:48.171864+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-barney-caam | Contextual Agent Authorization Mesh (CAAM) | 33pg
Abstract: This document specifies the Contextual Agent Authorization Mesh
   (CAAM), an authorization profile composable with the Agent
   Registration and Discovery Protocol (ARDP) I-D.pioli-agent-discovery
   and other discovery mechanisms.  CAAM defines the Post-Discovery
   Authorization Handshake: the runtime authorization layer that governs
   agent behavior after an agent has been discovered through ARDP but
   before it is permitted to execute tool calls or delegate authority.

   CAAM provides a sidecar-based authorization mediator for enforcing
   Relationship-Based Access Control (ReBAC), purpose-bound delegation,
   and cryptographically verifiable intent propagation in Human-to-Agent
   (H2A) and Agent-to-Agent (A2A) flows.  It bridges identity provenance
   frameworks -- the Interoperability Profiling for Secure Identity in
   the Enterprise (IPSIE) IPSIE and the Secure Production Identity
   Framework for Everyone (SPIFFE) SPIFFE -- with the ARDP control
   plane, leveraging OpenID XAA for coarse-grained delegation, a
   Knowledge Graph for real-time relationship inference, and the Remote
   ATtestation procedureS (RATS) architecture RFC9334 for
   cryptographically verifiable attestation of agent execution
   environments.

   The Session Context Object (SCO) defined herein is encoded as a JSON
   Web Token (JWT) RFC7519 or a CBOR Web Token (CWT) RFC8392, and
   carries a new "ctx" (Contextual Assertion) claim that binds the
   agent's delegated authority to a specific purpose, session, and trust
   chain.





TBD                                                         J. M. Barney
Internet-Draft                                                  R. Pioli
Intended status: Informational                                 D. Watson
Expires: 28 August 2026                                      Independent
                                                        24 February 2026


               Contextual Agent Authorization Mesh (CAAM)
                          draft-barney-caam-00

Abstract

   This document specifies the Contextual Agent Authorization Mesh
   (CAAM), an authorization profile composable with the Agent
   Registration and Discovery Protocol (ARDP) I-D.pioli-agent-discovery
   and other discovery mechanisms.  CAAM defines the Post-Discovery
   Authorization Handshake: the runtime authorization layer that governs
   agent behavior after an agent has been discovered through ARDP but
   before it is permitted to execute tool calls or delegate authority.

   CAAM provides a sidecar-based authorization mediator for enforcing
   Relationship-Based Access Control (ReBAC), purpose-bound delegation,
   and cryptographically verifiable intent propagation in Human-to-Agent
   (H2A) and Agent-to-Agent (A2A) flows.  It bridges identity provenance
   frameworks -- the Interoperability Profiling for Secure Identity in
   the Enterprise (IPSIE) IPSIE and the Secure Production Identity
   Framework for Everyone (SPIFFE) SPIFFE -- with the ARDP control
   plane, leveraging OpenID XAA for coarse-grained delegation, a
   Knowledge Graph for real-time relationship inference, and the Remote
   ATtestation procedureS (RATS) architecture RFC9334 for
   cryptographically verifiable attestation of agent execution
   environments.

   The Session Context Object (SCO) defined herein is encoded as a JSON
   Web Token (JWT) RFC7519 or a CBOR Web Token (CWT) RFC8392, and
   carries a new "ctx" (Contextual Assertion) claim that binds the
   agent's delegated authority to a specific purpose, session, and trust
   chain.

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/.



Barney, et al.           Expires 28 August 2026                 [Page 1]

Internet-Draft                    CAAM                     February 2026


   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 28 August 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document 

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

response_json:
[
  {
    "title": "Post-Discovery Authorization Handshake",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Session Context Object (SCO)",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Sidecar-based Authorization Mediator",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Knowledge Graph Integration for ReBAC",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Identity Framework Bridge",
    "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.",
    "type": "pattern"
  },
  {
    "title": "RATS-based Agent Attestation",
    "description": "Leverages the Remote ATtestation procedureS (RATS) architecture for cryptographically verifiable attestation of agent execution environments. Ensures agents operate in trusted environments before authorization.",
    "type": "mechanism"
  }
]


draft_name: draft-bastian-jose-dvs
prompt_hash: faa1ccf9d000af7d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:38:54.832024+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-bastian-jose-dvs | Public Key Derived HMAC for JOSE | 11pg
Abstract: This specification defines the use of a Diffie-Hellman key agreement
   (DH-KA) protocol combined with a key derivation function (KDF) to
   derive a symmetric Message Authentication Code (MAC) key from public
   information conveyed within a JSON Web Signature (JWS).





Javascript Object Signing and Encryption                      P. Bastian
Internet-Draft                                                  M. Kraus
Intended status: Informational                      Bundesdruckerei GmbH
Expires: 15 April 2026                                      S. Santesson
                                                         IDsec Solutions
                                                           P. L. Altmann
                                       The Agency for Digital Government
                                                         12 October 2025


                    Public Key Derived HMAC for JOSE
                       draft-bastian-jose-dvs-02

Abstract

   This specification defines the use of a Diffie-Hellman key agreement
   (DH-KA) protocol combined with a key derivation function (KDF) to
   derive a symmetric Message Authentication Code (MAC) key from public
   information conveyed within a JSON Web Signature (JWS).

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://paulbastian.github.io/draft-bastian-jose-dvs/draft-bastian-
   jose-dvs.html.  Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-bastian-jose-dvs/.

   Discussion of this document takes place on the Javascript Object
   Signing and Encryption Working Group mailing list
   (mailto:jose@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/jose/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/jose/.

   Source for this draft and an issue tracker can be found at
   https://github.com/paulbastian/draft-bastian-jose-dvs.

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/.




Bastian, et al.           Expires 15 April 2026                 [Page 1]

Internet-Draft              PKD-HMAC for JOSE               October 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 15 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


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

response_json:
[
  {
    "title": "Public Key Derived HMAC",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "DH-KA with KDF for JWS",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Public Information MAC Key Derivation",
    "description": "A pattern where symmetric authentication keys are derived from public information conveyed within JWS structures. Eliminates need for separate key distribution channels.",
    "type": "pattern"
  },
  {
    "title": "JOSE DVS Extension",
    "description": "Extension to the JOSE framework that adds derived verification signature capabilities. Provides alternative authentication method beyond traditional pre-shared keys.",
    "type": "extension"
  }
]


draft_name: draft-bastian-jose-pkdh
prompt_hash: aaccebf97aaa21b9
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:01.346671+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-bastian-jose-pkdh | Public Key Derived HMAC for JOSE | 14pg
Abstract: This specification defines the use of a Diffie-Hellman key agreement
   (DH-KA) protocol combined with a key derivation function (KDF) to
   derive a symmetric Message Authentication Code (MAC) key from public
   information conveyed within a JSON Web Signature (JWS).





Javascript Object Signing and Encryption                      P. Bastian
Internet-Draft                                                  M. Kraus
Intended status: Informational                      Bundesdruckerei GmbH
Expires: 23 April 2026                                      S. Santesson
                                                         IDsec Solutions
                                                           P. L. Altmann
                                       The Agency for Digital Government
                                                         20 October 2025


                    Public Key Derived HMAC for JOSE
                       draft-bastian-jose-pkdh-01

Abstract

   This specification defines the use of a Diffie-Hellman key agreement
   (DH-KA) protocol combined with a key derivation function (KDF) to
   derive a symmetric Message Authentication Code (MAC) key from public
   information conveyed within a JSON Web Signature (JWS).

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://paulbastian.github.io/draft-bastian-jose-pkdh/draft-bastian-
   jose-pkdh.html.  Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-bastian-jose-pkdh/.

   Discussion of this document takes place on the Javascript Object
   Signing and Encryption Working Group mailing list
   (mailto:jose@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/jose/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/jose/.

   Source for this draft and an issue tracker can be found at
   https://github.com/paulbastian/draft-bastian-jose-pkdh.

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/.




Bastian, et al.           Expires 23 April 2026                 [Page 1]

Internet-Draft              PKD-HMAC for JOSE               October 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 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 ri

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

response_json:
[
  {
    "title": "DH-KA MAC Key Derivation",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Public Key Derived HMAC",
    "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.",
    "type": "protocol"
  },
  {
    "title": "JOSE PKD-HMAC Integration",
    "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.",
    "type": "extension"
  },
  {
    "title": "JWS Header Public Key Conveyance",
    "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.",
    "type": "pattern"
  }
]


draft_name: draft-berlinai-vera
prompt_hash: ef427bbcaf429c3d
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:08.655688+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-berlinai-vera | VERA: Verifiable Enforcement for Runtime Agents | 7pg
Abstract: AI agents take real actions with real data at machine speed.
   Compromised AI agents pose significant risks including data
   exfiltration, unauthorized financial transactions, and cascading
   failures across downstream systems.

   This document introduces VERA (Verifiable Enforcement for Runtime
   Agents), a zero trust reference architecture that provides a
   structured threat model, five enforcement pillars with typed
   schemas, four formally stated security properties, and an
   evidence-based maturity runtime where agents earn autonomy through
   cryptographic proof rather than calendar time.

Network Working Group                                          Yogami
Internet-Draft                                          Berlin AI Labs
Intended status: Informational                      12 February 2026
Expires: 12 August 2026


             VERA: Verifiable Enforcement for Runtime Agents
                       draft-berlinai-vera-00


Abstract

   AI agents take real actions with real data at machine speed.
   Compromised AI agents pose significant risks including data
   exfiltration, unauthorized financial transactions, and cascading
   failures across downstream systems.

   This document introduces VERA (Verifiable Enforcement for Runtime
   Agents), a zero trust reference architecture that provides a
   structured threat model, five enforcement pillars with typed
   schemas, four formally stated security properties, and an
   evidence-based maturity runtime where agents earn autonomy through
   cryptographic proof rather than calendar time.


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), 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."

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

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

   This Internet-Draft will expire on 12 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.  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 Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.


Table of Contents

   1. Introduction: The Enforcement Gap  . . . . . . . . . . . . .  2
   2. Threat Model . . . . . . . . . . . . . . . . . . . . . . . .  3
   3. Formal Security Properties . . . . . . . . . . . . . . . . .  4
   4. VERA Architecture: Five Enforcement Pillars  . . . . . . . .  5
   5. The Maturity Runtime . . . . . . . . . . . . . . . . . . . .  9
   6. Implementation Status  . . . . . . . . . . . . . . . . . . . 10
   7. IANA Consid

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

response_json:
[
  {
    "title": "VERA Zero Trust Reference Architecture",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Evidence-Based Maturity Runtime",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Five Enforcement Pillars with Typed Schemas",
    "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.",
    "type": "pattern"
  },
  {
    "title": "AI Agent Structured Threat Model",
    "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.",
    "type": "requirement"
  },
  {
    "title": "Cryptographic Proof-Based Autonomy",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-bernardos-cats-isac-uc
prompt_hash: c4471291588623b9
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:16.583679+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-bernardos-cats-isac-uc | Integrated Sensing and Communications (ISAC) for CATS | 10pg
Abstract: Integrated Sensing and Communications (ISAC) represents a paradigm
   shift in wireless networks, where sensing and communication functions
   are jointly designed and optimized.  By leveraging the same spectral
   and hardware resources, ISAC enables advanced capabilities such as
   environment perception, object tracking, and situational awareness,
   while maintaining efficient and reliable data transmission.  This
   integration holds great potential for applications in areas such as
   autonomous systems, smart cities, and industrial automation, where
   precise sensing and low-latency communication are critical.  This
   document presents the ISAC as a typical CATS scenario to facilitate
   discussions on the potential challenges and requirements.





CATS WG                                                    CJ. Bernardos
Internet-Draft                                                      UC3M
Intended status: Standards Track                               A. Mourad
Expires: 4 January 2026                                     InterDigital
                                                                T. Jiang
                                                                    CMCC
                                                             3 July 2025


         Integrated Sensing and Communications (ISAC) for CATS
                    draft-bernardos-cats-isac-uc-01

Abstract

   Integrated Sensing and Communications (ISAC) represents a paradigm
   shift in wireless networks, where sensing and communication functions
   are jointly designed and optimized.  By leveraging the same spectral
   and hardware resources, ISAC enables advanced capabilities such as
   environment perception, object tracking, and situational awareness,
   while maintaining efficient and reliable data transmission.  This
   integration holds great potential for applications in areas such as
   autonomous systems, smart cities, and industrial automation, where
   precise sensing and low-latency communication are critical.  This
   document presents the ISAC as a typical CATS scenario to facilitate
   discussions on the potential challenges and 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 4 January 2026.

Copyright Notice

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




Bernardos, et al.        Expires 4 January 2026                 [Page 1]

Internet-Draft           ISAC use case for CATS                July 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.  Int

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

response_json:
[
  {
    "title": "Joint Sensing-Communication Resource Sharing",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "ISAC-CATS Integration Pattern",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Environment Perception with Communication Infrastructure",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Low-Latency Sensing-Communication Requirements",
    "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.",
    "type": "requirement"
  },
  {
    "title": "ISAC-Enabled CATS Architecture",
    "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.",
    "type": "architecture"
  }
]


draft_name: draft-bernardos-green-isac-uc
prompt_hash: 9718df7d7dbf95d2
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:23.704985+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-bernardos-green-isac-uc | Integrated Sensing and Communications (ISAC) use case for GREEN | 5pg
Abstract: Integrated Sensing and Communications (ISAC) represents a paradigm
   shift in wireless networks, where sensing and communication functions
   are jointly designed and optimized.  By leveraging the same spectral
   and hardware resources, ISAC enables advanced capabilities such as
   environment perception, object tracking, and situational awareness,
   while maintaining efficient and reliable data transmission.  This
   integration holds great potential for applications in areas such as
   autonomous systems, smart cities, and industrial automation, where
   precise sensing and low-latency communication are critical.

   This document presents a use case related to ISAC, aiming to
   facilitate discussions within the GREEN Working Group on the
   potential benefits, challenges, and requirements.  The use case
   follows a structured template that we propose for all GREEN use
   cases, ensuring consistency and comparability across different
   scenarios.





GREEN WG                                                   CJ. Bernardos
Internet-Draft                                                      UC3M
Intended status: Standards Track                         M. Awais Jadoon
Expires: 31 August 2025                                        A. Mourad
                                                            InterDigital
                                                        27 February 2025


    Integrated Sensing and Communications (ISAC) use case for GREEN
                    draft-bernardos-green-isac-uc-00

Abstract

   Integrated Sensing and Communications (ISAC) represents a paradigm
   shift in wireless networks, where sensing and communication functions
   are jointly designed and optimized.  By leveraging the same spectral
   and hardware resources, ISAC enables advanced capabilities such as
   environment perception, object tracking, and situational awareness,
   while maintaining efficient and reliable data transmission.  This
   integration holds great potential for applications in areas such as
   autonomous systems, smart cities, and industrial automation, where
   precise sensing and low-latency communication are critical.

   This document presents a use case related to ISAC, aiming to
   facilitate discussions within the GREEN Working Group on the
   potential benefits, challenges, and requirements.  The use case
   follows a structured template that we propose for all GREEN use
   cases, ensuring consistency and comparability across different
   scenarios.

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 2025.





Bernardos, et al.        Expires 31 August 2025                 [Page 1]

Internet-Draft           ISAC use case for GREEN           February 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 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

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

response_json:
[
  {
    "title": "Joint Sensing-Communication Function Design",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Shared Spectral and Hardware Resources",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Environment Perception Integration",
    "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.",
    "type": "pattern"
  },
  {
    "title": "GREEN Use Case Template Structure",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Low-Latency Sensing-Communication Requirements",
    "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.",
    "type": "requirement"
  }
]


draft_name: draft-birkholz-verifiable-agent-conversations
prompt_hash: 38924ca446428209
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:30.979485+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-birkholz-verifiable-agent-conversations | Verifiable Agent Conversation Records | 51pg
Abstract: Autonomous agents based on large language models increasingly perform
   consequential tasks on behalf of humans and other agents.
   Demonstrating that recorded agent behavior truthfully represents
   actual behavior is essential for accountability, compliance, and
   human oversight.  This document defines a data format for verifiable
   agent conversation records using CDDL, with representations in both
   JSON and CBOR.  The format captures session metadata, message
   exchanges, tool invocations, reasoning traces, and system events in a
   structured, extensible CDDL definition for verifiable agent
   conversation records.  COSE is used as the signing method to allow
   for native interoperability in SCITT Transparency Services and the
   CDDL definition allows for seemless integration in Evidence as
   specified in RFC 9334.  The specification supports cross-vendor
   interoperability by defining a common representation that
   accommodates translation from multiple existing agent implementations
   with distinct data structure layouts that are typically represented
   in JSON.





Network Working Group                                        H. Birkholz
Internet-Draft                                                          
Intended status: Standards Track                                T. Heldt
Expires: 29 August 2026                                                 
                                                               O. Steele
                                                        25 February 2026


                 Verifiable Agent Conversation Records
            draft-birkholz-verifiable-agent-conversations-00

Abstract

   Autonomous agents based on large language models increasingly perform
   consequential tasks on behalf of humans and other agents.
   Demonstrating that recorded agent behavior truthfully represents
   actual behavior is essential for accountability, compliance, and
   human oversight.  This document defines a data format for verifiable
   agent conversation records using CDDL, with representations in both
   JSON and CBOR.  The format captures session metadata, message
   exchanges, tool invocations, reasoning traces, and system events in a
   structured, extensible CDDL definition for verifiable agent
   conversation records.  COSE is used as the signing method to allow
   for native interoperability in SCITT Transparency Services and the
   CDDL definition allows for seemless integration in Evidence as
   specified in RFC 9334.  The specification supports cross-vendor
   interoperability by defining a common representation that
   accommodates translation from multiple existing agent implementations
   with distinct data structure layouts that are typically represented
   in JSON.

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 29 August 2026.




Birkholz, et al.         Expires 29 August 2026                 [Page 1]

Internet-Draft               Verifiable ACRs               February 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.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this d

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

response_json:
[
  {
    "title": "CDDL Agent Conversation Record Schema",
    "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.",
    "type": "protocol"
  },
  {
    "title": "COSE Signing for Agent Records",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Cross-Vendor Agent Data Translation",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Verifiable Agent Behavior Attestation",
    "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.",
    "type": "requirement"
  },
  {
    "title": "Agent Reasoning Trace Capture",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-blahaj-grow-rpki-oauth
prompt_hash: 7c45d190a96d6602
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:38.758769+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-blahaj-grow-rpki-oauth | Attesting the Identities of Parties in OpenID Connect (OIDC) using the Resource Public Key Infrastructure (RPKI) | 7pg
Abstract: The Peering API currently under discussion in the GROW Working Group
   does not provide a standardised mechanism to authenticate parties
   engaged in the Peering API.  This document specifies a method to
   attest as to the identities of parties in an OpenID Connect (OIDC)
   exchange, binding the authentication flow to agents of ASNs.

Discussion

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

   Source for this draft and an issue tracker can be found at
   https://github.molgen.mpg.de/q/rpki-peering-api-discovery.





grow                                                           Q. Misell
Internet-Draft                                                  AS207960
Intended status: Standards Track                            30 June 2025
Expires: 1 January 2026


 Attesting the Identities of Parties in OpenID Connect (OIDC) using the
               Resource Public Key Infrastructure (RPKI)
                    draft-blahaj-grow-rpki-oauth-00

Abstract

   The Peering API currently under discussion in the GROW Working Group
   does not provide a standardised mechanism to authenticate parties
   engaged in the Peering API.  This document specifies a method to
   attest as to the identities of parties in an OpenID Connect (OIDC)
   exchange, binding the authentication flow to agents of ASNs.

Discussion

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

   Source for this draft and an issue tracker can be found at
   https://github.molgen.mpg.de/q/rpki-peering-api-discovery.

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 1 January 2026.

Copyright Notice

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





Misell                   Expires 1 January 2026                 [Page 1]

Internet-Draft             RPKI Attested OIDC                  June 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.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Endpoint Discovery  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Extensions to IdP Metadata  . . . . . . . . . . . . . . . . .   4


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

response_json:
[
  {
    "title": "RPKI-OIDC Authentication Binding",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "ASN-Agent Authentication",
    "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.",
    "type": "protocol"
  },
  {
    "title": "RPKI-Enhanced Endpoint Discovery",
    "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.",
    "type": "extension"
  },
  {
    "title": "Extended IdP Metadata for ASN Binding",
    "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.",
    "type": "extension"
  },
  {
    "title": "RPKI-OIDC Identity Attestation",
    "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.",
    "type": "mechanism"
  }
]


draft_name: draft-bradleylundberg-cfrg-arkg
prompt_hash: e69f419e8b7b1537
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:44.698961+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-bradleylundberg-cfrg-arkg | The Asynchronous Remote Key Generation (ARKG) algorithm | 47pg
Abstract: Asynchronous Remote Key Generation (ARKG) is an abstract algorithm
   that enables delegation of asymmetric public key generation without
   giving access to the corresponding private keys.  This capability
   enables a variety of applications: a user agent can generate
   pseudonymous public keys to prevent tracking; a message sender can
   generate ephemeral recipient public keys to enhance forward secrecy;
   two paired authentication devices can each have their own private
   keys while each can register public keys on behalf of the other.

   This document provides three main contributions: a specification of
   the generic ARKG algorithm using abstract primitives; a set of
   formulae for instantiating the abstract primitives using concrete
   primitives; and an initial set of fully specified concrete ARKG
   instances.  We expect that additional instances will be defined in
   the future.





Crypto Forum                                            E. Lundberg, Ed.
Internet-Draft                                                J. Bradley
Intended status: Informational                                    Yubico
Expires: 31 August 2026                                 27 February 2026


        The Asynchronous Remote Key Generation (ARKG) algorithm
                   draft-bradleylundberg-cfrg-arkg-10

Abstract

   Asynchronous Remote Key Generation (ARKG) is an abstract algorithm
   that enables delegation of asymmetric public key generation without
   giving access to the corresponding private keys.  This capability
   enables a variety of applications: a user agent can generate
   pseudonymous public keys to prevent tracking; a message sender can
   generate ephemeral recipient public keys to enhance forward secrecy;
   two paired authentication devices can each have their own private
   keys while each can register public keys on behalf of the other.

   This document provides three main contributions: a specification of
   the generic ARKG algorithm using abstract primitives; a set of
   formulae for instantiating the abstract primitives using concrete
   primitives; and an initial set of fully specified concrete ARKG
   instances.  We expect that additional instances will be defined in
   the future.

About This Document

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

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-bradleylundberg-cfrg-arkg/.

   Source for this draft and an issue tracker can be found at
   https://github.com/Yubico/arkg-rfc.

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/.





Lundberg & Bradley       Expires 31 August 2026                 [Page 1]

Internet-Draft                    ARKG                     February 2026


   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.

   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

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

response_json:
[
  {
    "title": "ARKG Core Algorithm",
    "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.",
    "type": "algorithm"
  },
  {
    "title": "Pseudonymous Key Generation",
    "description": "Mechanism allowing user agents to generate pseudonymous public keys to prevent tracking while maintaining cryptographic security. Enables privacy-preserving authentication without key exposure.",
    "type": "mechanism"
  },
  {
    "title": "Ephemeral Recipient Key Generation",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Paired Device Key Registration",
    "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.",
    "type": "architecture"
  },
  {
    "title": "Abstract-to-Concrete Primitive Mapping",
    "description": "Set of formulae for instantiating abstract ARKG primitives using concrete cryptographic primitives. Provides standardized transformation methods for implementation.",
    "type": "mechanism"
  }
]


draft_name: draft-campbell-agentic-http
prompt_hash: 3792d5340d5a5d88
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:51.313860+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-campbell-agentic-http | A Best Current Practice for Agentic Interactions over HTTP | 6pg
Abstract: This document describes a set of best practices for facilitating
   interactions between automated software agents (AI agents) using the
   Hypertext Transfer Protocol (HTTP).  As agentic systems proliferate,
   they frequently utilize HTTP in ad-hoc ways, leading to
   interoperability challenges and the rise of proprietary, "walled
   garden" ecosystems.  This document proposes a minimalist,
   standardized framework based on existing HTTP semantics to promote a
   more cohesive, efficient, and open ecosystem.  The primary
   recommendations codify the principles of the Agentic Hypercall
   Protocol (AHP), including tool invocation via GET requests, a
   stateless authentication scheme, and the formalization of the 402
   (Payment Required) status code to enable a native economic layer for
   the machine economy.





Network Working Group                                        K. Campbell
Internet-Draft                                         DeepBlue Dynamics
Intended status: Best Current Practice                       August 2025
Expires: 8 February 2026


       A Best Current Practice for Agentic Interactions over HTTP
                     draft-campbell-agentic-http-00

Abstract

   This document describes a set of best practices for facilitating
   interactions between automated software agents (AI agents) using the
   Hypertext Transfer Protocol (HTTP).  As agentic systems proliferate,
   they frequently utilize HTTP in ad-hoc ways, leading to
   interoperability challenges and the rise of proprietary, "walled
   garden" ecosystems.  This document proposes a minimalist,
   standardized framework based on existing HTTP semantics to promote a
   more cohesive, efficient, and open ecosystem.  The primary
   recommendations codify the principles of the Agentic Hypercall
   Protocol (AHP), including tool invocation via GET requests, a
   stateless authentication scheme, and the formalization of the 402
   (Payment Required) status code to enable a native economic layer for
   the machine economy.

Status of This Memo

   This memo documents a Best Current Practice for the Internet
   community.  It does not specify an Internet standard of any kind.
   Distribution of this memo is unlimited.

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 2 February 2026.




Campbell                 Expires 8 February 2026                [Page 1]

RFC 9582                      Agentic HTTP                   August 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 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.  1.  I

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

response_json:
[
  {
    "title": "Agentic Hypercall Protocol (AHP)",
    "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.",
    "type": "protocol"
  },
  {
    "title": "Tool Invocation via GET Requests",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Stateless Authentication Scheme",
    "description": "An authentication pattern specifically designed for agentic interactions that maintains no session state between requests. Enables scalable agent-to-agent authentication over HTTP.",
    "type": "mechanism"
  },
  {
    "title": "Formalized 402 Payment Required",
    "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.",
    "type": "extension"
  },
  {
    "title": "Machine Economy Layer",
    "description": "An architectural pattern that enables automated economic transactions between AI agents using standardized HTTP status codes. Facilitates autonomous commercial interactions in agent ecosystems.",
    "type": "architecture"
  }
]


draft_name: draft-chang-agent-context-interaction
prompt_hash: ddc74a7e1fbe065f
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:39:56.267907+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-chang-agent-context-interaction | Agent Context Interaction Optimizations | 13pg
Abstract: The context distribution is important in a multi-agent system, which
   will impact the execution latency, token consumption, and task
   completion success rate, especially in a complex and multi-round
   workflow.

   This document specifies the scenarios and procedures of agent context
   distribution as well as the corresponding optimization during the
   procedures in order to provide precise control of the context
   distribution among the multiple agents.





Working Group                                                   Z. Chang
Internet-Draft                                                   S. Peng
Intended status: Standards Track                     Huawei Technologies
Expires: 16 August 2026                                 12 February 2026


                Agent Context Interaction Optimizations
                draft-chang-agent-context-interaction-01

Abstract

   The context distribution is important in a multi-agent system, which
   will impact the execution latency, token consumption, and task
   completion success rate, especially in a complex and multi-round
   workflow.

   This document specifies the scenarios and procedures of agent context
   distribution as well as the corresponding optimization during the
   procedures in order to provide precise control of the context
   distribution among the multiple 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 16 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.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components



Chang & Peng             Expires 16 August 2026                 [Page 1]

Internet-Draft                  PCECC-SR                   February 2026


   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Conventions and Terminology . . . . . . . . . . . . . . .   3
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Agent Context Interaction Optimizations . . . . . . . . . . .   6
     4.1.  Overview of Agent Context Interaction Optimizations . . .   6
     4.2.  Contex

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

response_json:
[
  {
    "title": "Agent Context Distribution",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Context Distribution Optimization Procedures",
    "description": "Specified procedures for optimizing context distribution during agent interactions. Provides precise control of how context is shared and managed across multiple agents.",
    "type": "protocol"
  },
  {
    "title": "Multi-Round Workflow Context Management",
    "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.",
    "type": "pattern"
  },
  {
    "title": "Agent Context Interaction Scenarios",
    "description": "Defined scenarios that specify when and how agent context distribution should occur. Establishes standardized conditions for context sharing between agents.",
    "type": "requirement"
  }
]


draft_name: draft-chang-agent-token-efficient
prompt_hash: e28ebc04360f784a
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:40:02.973919+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-chang-agent-token-efficient | A Token-efficient Data Layer for Agentic Communication | 12pg
Abstract: Agentic communication fundamentally differs from traditional machine
   communication in that its outputs are recursively consumed and
   interpreted by Large Language Models (LLMs).  This unique
   characteristic makes efficient use of the model's limited context a
   critical requirement.  However, current agent communication protocols
   - such as the Model Context Protocol (MCP) and Agent-to-Agent (A2A) -
   often suffer from token or context bloat, caused by redundant schema
   definitions, verbose message structures, and inefficient capability
   exchanges.  As a result, a substantial number of tokens are
   unnecessarily consumed within the model’s context window.

   To address these issues, this draft defines the Agentic Data
   Optimization Layer (ADOL), a general and foundational data-layer for
   agent communication.  ADOL introduces a set of backward-compatible
   optimizations, including schema deduplication through JSON
   references, adaptive inclusion of optional fields, controllable
   response verbosity, and retrieval-based selection mechanisms.
   Collectively, these mechanisms reduce token consumption, enhance
   context efficiency, and provide a scalable foundation for future
   agent communication frameworks.





Network Working Group                                           Z. Chang
Internet-Draft                                                     J. Li
Intended status: Informational                                    Z. Cao
Expires: 16 July 2026                                             Huawei
                                                         12 January 2026


         A Token-efficient Data Layer for Agentic Communication
                  draft-chang-agent-token-efficient-02

Abstract

   Agentic communication fundamentally differs from traditional machine
   communication in that its outputs are recursively consumed and
   interpreted by Large Language Models (LLMs).  This unique
   characteristic makes efficient use of the model's limited context a
   critical requirement.  However, current agent communication protocols
   - such as the Model Context Protocol (MCP) and Agent-to-Agent (A2A) -
   often suffer from token or context bloat, caused by redundant schema
   definitions, verbose message structures, and inefficient capability
   exchanges.  As a result, a substantial number of tokens are
   unnecessarily consumed within the model’s context window.

   To address these issues, this draft defines the Agentic Data
   Optimization Layer (ADOL), a general and foundational data-layer for
   agent communication.  ADOL introduces a set of backward-compatible
   optimizations, including schema deduplication through JSON
   references, adaptive inclusion of optional fields, controllable
   response verbosity, and retrieval-based selection mechanisms.
   Collectively, these mechanisms reduce token consumption, enhance
   context efficiency, and provide a scalable foundation for future
   agent communication frameworks.

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."




Chang, et al.             Expires 16 July 2026                  [Page 1]

Internet-Draft              Abbreviated Title               January 2026


   This Internet-Draft will expire on 16 July 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.
   Please review these documents car

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

response_json:
[
  {
    "title": "Schema Deduplication via JSON References",
    "description": "Uses JSON $ref pointers to eliminate redundant schema definitions in agent communication messages. Replaces repeated schema blocks with references to reduce token consumption.",
    "type": "mechanism"
  },
  {
    "title": "Adaptive Optional Field Inclusion",
    "description": "Selectively includes or omits optional fields in messages based on context relevance and token budget constraints. Provides dynamic message structure optimization.",
    "type": "mechanism"
  },
  {
    "title": "Controllable Response Verbosity",
    "description": "Allows agents to specify desired response detail levels to match available context window capacity. Enables token-aware response generation.",
    "type": "mechanism"
  },
  {
    "title": "Retrieval-based Selection Mechanisms",
    "description": "Implements intelligent filtering and selection of relevant data elements for inclusion in agent communications. Reduces unnecessary information transfer.",
    "type": "mechanism"
  },
  {
    "title": "Agentic Data Optimization Layer (ADOL)",
    "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.",
    "type": "architecture"
  }
]


draft_name: draft-chen-agent-decoupled-authorization-model
prompt_hash: 3cb53f18e763a7f8
model: claude-sonnet-4-20250514
created_at: 2026-02-28T10:40:09.760787+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-chen-agent-decoupled-authorization-model | A Decoupled Authorization Model for Agent2Agent | 6pg
Abstract: This document proposes a framework for dynamic, intent-based
   authorization for AI Agents.  The primary goal is to enable fine-
   grained, Just-in-Time (JIT) permissions based on an agent's specific
   intent and behavioral trustworthiness, rather than a long-lived
   identity or role, achieve decoupling of authorization policies from
   business operations.





Internet Engineering Task Force                                  M. Chen
Internet-Draft                                                     L. Su
Intended status: Informational                              China Mobile
Expires: 18 August 2026                                 14 February 2026


            A Decoupled Authorization Model for Agent2Agent
           draft-chen-agent-decoupled-authorization-model-00

Abstract

   This document proposes a framework for dynamic, intent-based
   authorization for AI Agents.  The primary goal is to enable fine-
   grained, Just-in-Time (JIT) permissions based on an agent's specific
   intent and behavioral trustworthiness, rather than a long-lived
   identity or role, achieve decoupling of authorization policies from
   business operations.

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 18 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.
   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.



Chen & Su                Expires 18 August 2026                 [Page 1]

Internet-Draft           AI Agent Authorization            February 2026


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Analysis of Oauth for Agent-to-Agent Authorization  . . . . .   4
     4.1.  What OAuth2.0 can do  . . . . . . . . . . . . . . . . . .   4
     4.2.  Remaining Challenges and Open Issues  . . . . . . . . . .   4
   5.  Decoupled Authorization Model . . . . . . . . . . . . . . . .   5
     5.1.  Architecture overview . . . . . . . . . . . . . . . . . .   5
     5.2.  Authorization Execution Point

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

response_json:
[
  {
    "title": "Intent-Based Authorization",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Just-in-Time (JIT) Permissions",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Behavioral Trustworthiness Assessment",
    "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.",
    "type": "mechanism"
  },
  {
    "title": "Decoupled Authorization Architecture",
    "description": "System design that separates authorization policies from business operations, allowing independent evolution of security controls. Enables policy changes without modifying core business logic.",
    "type": "architecture"
  },
  {
    "title": "Authorization Execution Point",
    "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.",
    "type": "architecture"
  }
]


