```json
{
  "s": "VERA proposes a zero-trust reference architecture for securing AI agents through five enforcement pillars and cryptographic proof-based autonomy escalation. The framework combines threat modeling, formal security properties, and a maturity-based runtime to mitigate risks from compromised agents.",
  "n": 3,
  "nn": "Framework-level contribution with structured threat model and formal properties; combines existing zero-trust concepts with agent-specific autonomy/capability escalation mechanics, incremental rather than fundamentally novel.",
  "m": 2,
  "mn": "Early architectural sketch with identified pillars and properties but lacks protocol details, message formats, cryptographic scheme specifications, and concrete implementation guidance needed for reproducibility.",
  "o": 3,
  "on": "Shares conceptual overlap with zero-trust architecture (NIST ZTA, BeyondCorp), supply-chain risk frameworks, and capability-based security; agent-specific application is somewhat novel but builds on established patterns.",
  "mo": 1,
  "mon": "Appears to be initial submission (Feb 2026 date); no evidence of WG discussion, revisions, or community engagement; single 7-page draft suggests early-stage work.",
  "r": 5,
  "rn": "Directly addresses critical AI agent security risks (exfiltration, unauthorized transactions, cascading failures); core to emerging agent autonomy governance and runtime protection.",
  "c": [
    "AI safety/alignment",
    "Agent identity/auth",
    "Policy/governance",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "ANML is a proposed machine-first markup language for agent-to-agent communication that standardizes content, interactions, constraints, and state representation across XML and JSON serializations. It aims to reduce inference overhead by providing explicit semantic structure optimized for deterministic agent interactions.",
  "n": 2,
  "nn": "Incremental contribution combining existing markup concepts (semantic annotation, structured data, constraint declarations) without substantial novelty beyond applying familiar patterns to the agent communication domain.",
  "m": 3,
  "mn": "Protocol mechanism is defined with stated serialization formats and abstract model, but lacks implementation details, test vectors, validation rules, and concrete examples needed for implementation readiness.",
  "o": 4,
  "on": "Significant overlap with existing standards: microformats/schema.org (semantic annotation), JSON-LD (structured data), OpenAPI/AsyncAPI (interaction/parameter binding), W3C Capabilities (constraints), and SASL/OAuth (authorization rules).",
  "mo": 1,
  "mon": "Single draft dated 2026-05-22 with no visible revision history, community discussion, WG sponsorship, or implementation adoption signals.",
  "r": 4,
  "rn": "Directly relevant to agent-to-agent communication protocols and data format standardization, though focus is narrow to protocol structuring rather than core AI safety or autonomy challenges.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes an application-layer protocol for agent-to-agent communication built atop Media over QUIC (MoQ), adding framing for control signaling, session management, and data fragmentation. Targets low-latency structured messaging between autonomous agents in intra- and inter-domain deployments with emphasis on interoperability and extensibility.",
  "n": 2,
  "nn": "Incremental contribution layering agents over existing MoQ transport; core novelty is primarily the framing/signaling layer rather than fundamentally new concepts.",
  "m": 2,
  "mn": "Early sketch stage with abstract describing goals but 22 pages likely covering design rationale; lacks detail on protocol state machines, message formats, error handling, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing agent messaging protocols (gRPC, MQTT, DDS) and MoQ-adjacent signaling work; positioning relative to alternatives unclear.",
  "mo": 1,
  "mon": "Single draft revision with 2026 date suggests nascent work; no evidence of WG adoption, implementer interest, or broader community momentum.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure but frames problem narrowly as transport protocol rather than addressing agent coordination, reasoning, or safety concerns central to agent research.",
  "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg"],
  "overall_assessment": "Early-stage transport layer specification with limited novelty and unclear positioning relative to established messaging frameworks. Needs stronger motivation, detailed protocol specification, and demonstrated demand from agent community."
}
```


```json
{
  "s": "Proposes coordination requirements for AI agent protocols to enable autonomous task management across distributed networks, focusing on dynamic discovery, negotiation, and adaptive scheduling. Addresses the emerging need for standardized communication patterns as AI agents scale in heterogeneous environments.",
  "n": 2,
  "nn": "Incremental contribution focusing on well-established distributed systems concepts (task scheduling, service discovery, negotiation) applied to AI agents without fundamental protocol innovation.",
  "m": 2,
  "mn": "Early-stage requirements document; appears to be a problem statement and high-level requirements draft rather than a defined protocol specification with concrete mechanisms or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing work in multi-agent systems coordination, distributed task scheduling (IETF ALTO, etc.), and microservices orchestration; limited novelty in specific approach.",
  "mo": 1,
  "mon": "Single recent draft with no apparent prior versions or follow-up activity; timing suggests exploratory work without established community momentum or WG engagement.",
  "r": 3,
  "rn": "Partially relevant to AI agent protocols; addresses coordination needs but lacks specificity on AI-unique aspects (model inference requirements, LLM-specific constraints, prompt/embedding handling).",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Autonomous netops",
    "ML traffic mgmt",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "AMSP defines a hierarchical metadata synchronization protocol for autonomous agents across distributed network gateways, enabling global reachability and loop-free propagation. The draft addresses coordination between Level-1 and Level-2 gateways in an Internet of Agents infrastructure.",
  "n": 2,
  "nn": "Incremental contribution applying standard synchronization patterns (likely BGP-like) to agent metadata; the core concepts are well-established networking techniques adapted to a new domain.",
  "m": 3,
  "mn": "Protocol mechanism is defined with apparent hierarchical structure and metadata exchange semantics, but at 11 pages lacks detailed state machines, message formats, error handling, and implementation examples needed for production deployment.",
  "o": 4,
  "on": "Significant overlap with existing distributed metadata/routing protocols (BGP, ISIS, OSPF patterns); the agent-specific wrapper appears thin. Missing explicit comparison to related work in agent frameworks and distributed systems literature.",
  "mo": 1,
  "mon": "Single revision snapshot (2026-03-19 date suggests speculative/future draft); no evidence of WG discussion, implementation feedback, or iterative development history in public record.",
  "r": 4,
  "rn": "Directly relevant to agent infrastructure and discovery; addresses real coordination challenges in multi-gateway deployments, though framing as 'Internet of Agents' may overstate scope versus narrower agent mesh networking.",
  "c": ["A2A protocols", "Agent discovery/reg", "Autonomous netops", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes a framework for managing In-Network Computing Functions in C-ITS environments using Agent-to-Agent communication paradigms. Focuses on orchestrating distributed computing across vehicles, roadside units, and network domains for optimized V2X communications and traffic management.",
  "n": 2,
  "nn": "Incremental work combining existing concepts (in-network computing, V2X, MEC) with agent communication; framework design lacks substantial technical novelty.",
  "m": 2,
  "mn": "Early-stage draft with conceptual framework but minimal protocol detail; abstract mentions orchestration/management but likely lacks formal specifications, algorithms, or message formats.",
  "o": 4,
  "on": "Significant overlap with existing IETF work on MEC, V2X communication, network function orchestration; agent-based approaches in IoT/vehicular networks already established in multiple standards bodies.",
  "mo": 1,
  "mon": "First revision, no evidence of WG adoption, community discussion, or implementation efforts; niche intersection of NMRG interests and C-ITS domains.",
  "r": 3,
  "rn": "Partially relevant to AI agents via A2A communication paradigm, but framed primarily as network infrastructure/protocol work rather than agent systems; agent aspects appear secondary to networking concerns.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "ML traffic mgmt",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "N-ACT proposes a standardized protocol for AI agents to discover and invoke third-party tools/APIs, with separate enumeration and invocation mechanisms to reduce enterprise integration costs. It builds on OpenAI's function-calling specification to enable both design-time tool selection and runtime LLM-driven tool execution.",
  "n": 2,
  "nn": "Incremental extension of existing OpenAI tool/function-calling patterns; normalizes and formalizes what is already common practice in production AI systems rather than introducing fundamentally new concepts.",
  "m": 3,
  "mn": "Defines protocol structure and principles clearly but appears to lack implementation details, example specifications, test vectors, or interoperability validation across multiple AI platforms.",
  "o": 4,
  "on": "Significant overlap with OpenAI Functions API, Anthropic tool_use, and JSON Schema-based tool specifications already widely deployed; relates closely to existing OpenAPI/AsyncAPI ecosystem work.",
  "mo": 1,
  "mon": "No evidence of WG adoption, implementation, or iterative development; appears to be a single submission without demonstrable community interest or subsequent revisions.",
  "r": 4,
  "rn": "Directly relevant to practical AI agent deployment; addresses real enterprise pain point of tool integration, though framed narrowly around normalization rather than breakthrough capability.",
  "c": [
    "Data formats/interop",
    "Agent discovery/reg",
    "A2A protocols",
    "Model serving/inference",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Extends RFC8578 deterministic networking use cases to cover industrial IoT, high-quality video, intelligent computing, and ISAC-enabled factories, identifying scaling requirements and common properties across emerging applications.",
  "n": 2,
  "nn": "Incremental extension of existing use case frameworks; applies established DetNet concepts to newer application domains without fundamental protocol innovations.",
  "m": 2,
  "mn": "Early-stage use case documentation; identifies requirements and properties but lacks detailed protocol specifications, implementation guidance, or validation mechanisms.",
  "o": 4,
  "on": "Significant overlap with RFC8578 baseline and existing DetNet work; novel application domains partially explored in other drafts (industrial, video, computing).",
  "mo": 2,
  "mon": "Single recent revision (2026-02-24); no evident multi-version development pattern or clear WG adoption trajectory beyond use case exploration.",
  "r": 2,
  "rn": "Tangentially related to AI agents; focuses on network determinism for AI workloads (intelligent computing, ISAC) but is primarily infrastructure/networking rather than agent-centric.",
  "c": [
    "ML traffic mgmt",
    "Policy/governance",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft explores enhancing ANIMA's Autonomic Service Agents with LLM-driven AI capabilities, analyzing impacts on ASA communication protocols like GRASP. It positions AI-powered ASAs as an evolution of network device management functions.",
  "n": 2,
  "nn": "Incremental extension combining existing ASA/GRASP framework with generic LLM integration; lacks novel communication protocols or AI-specific mechanisms for agent coordination.",
  "m": 2,
  "mn": "Early-stage analysis document; identifies problem space but offers minimal concrete protocol modifications, design patterns, or implementation guidance for AI-augmented ASAs.",
  "o": 4,
  "on": "Significant overlap with broader AI agent communication work; combines established ANIMA concepts with generic LLM discussion without distinguishing unique technical contributions.",
  "mo": 1,
  "mon": "Limited community momentum; single recent revision on emerging topic but no evidence of WG adoption, implementation efforts, or active development cycle.",
  "r": 4,
  "rn": "Directly relevant to AI-powered autonomic agents and their network communication; addresses timely intersection of ANIMA framework and LLM technologies.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent identity/auth",
    "Data formats/interop",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "INIP proposes a lightweight protocol for executing inference tasks on in-network data plane devices (switches, DPUs, SmartNICs) in datacenter networks, using a centralized control plane with CDN-like model scheduling and minimal data plane execution. The protocol aims to enable high-speed inference while preserving core forwarding functions.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (in-network computing, match-action tables, model scheduling). The core idea of offloading ML inference to network devices is not new; primary contribution is protocol specification rather than novel architectural insights.",
  "m": 3,
  "mn": "Protocol specification is defined with packet format, architecture, and scheduling mechanisms described. However, lacks implementation details, test vectors, deployment examples, and empirical validation of performance claims. Insufficient for immediate standardization.",
  "o": 4,
  "on": "Significant overlap with prior work on in-network computing (e.g., Domino, NetCache, NN-Accelerator proposals), SmartNIC-based inference, and collaborative edge-cloud inference. The CDN-like scheduling mechanism is relatively standard. Positioning relative to existing standards unclear.",
  "m": 2,
  "mn": "Individual draft with single revision noted (2026-03-02). No indication of WG adoption, community discussion, or implementation efforts. Limited evidence of active development or stakeholder engagement beyond initial specification.",
  "r": 4,
  "rn": "Directly relevant to model serving/inference and autonomous network operations (ML-assisted resource allocation). Applicable to agent inference at the network level but not core to agent architecture, identity, or interaction protocols.",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Autonomous netops",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft proposes integrating hybrid post-quantum cryptography (PQC) into EAP-AKA' Forward Secrecy to protect against quantum computing threats. It extends RFC9678 by replacing traditional ECDHE with PQ/T hybrid algorithms for quantum-resistant key agreement in authentication protocols.",
  "n": 2,
  "nn": "Straightforward application of existing hybrid PQC terminology to an established protocol; combines known techniques without fundamental innovation in either PQC or EAP-AKA'.",
  "m": 2,
  "mn": "Early draft stage presenting motivation and problem statement; lacks detailed protocol specification, algorithm selection rationale, security analysis, and implementation guidance needed for standardization.",
  "o": 4,
  "on": "Significant overlap with parallel PQC migration efforts across IETF protocols; similar hybrid approach being applied to TLS, IKE, and other standards; limited unique contribution beyond domain-specific instantiation.",
  "mo": 2,
  "mon": "First revision with minimal engagement signals; no evidence of WG sponsorship, implementation feedback, or community adoption; appears as individual contribution rather than coordinated standardization effort.",
  "r": 3,
  "rn": "Partially relevant as authentication protocol for autonomous systems and agent identity/authorization scenarios; not core to AI agents specifically but addresses infrastructure security enabling trustworthy agent deployment.",
  "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]
}
```


```json
{
  "s": "Proposes using AI and SOAR for autonomous security and intent-based network management in B5G networks to maintain consistent security quality. The draft seeks to establish user requirements and system development guidance for AI-driven network management.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (AI in networking, SOAR, intent-based management) without clear novel technical contribution or methodology.",
  "m": 1,
  "mn": "Document lacks concrete technical specifications, protocols, mechanisms, or implementation details. Reads as high-level problem statement and requirement gathering exercise rather than defined solution.",
  "o": 4,
  "on": "Significant overlap with existing work on AI-driven network management, autonomous orchestration, and SOAR frameworks. Intent-based networking and B5G management are established research areas.",
  "mo": 1,
  "mon": "Single revision with minimal activity. No evidence of WG engagement, community discussion, or iterative development.",
  "r": 3,
  "rn": "Partially relevant to AI in network operations but lacks depth in autonomous agent design, coordination, or decision-making specifics. More about applying existing AI/SOAR tools than advancing AI agent technology.",
  "c": ["Autonomous netops", "ML traffic mgmt", "Policy/governance"]
}
```


```json
{
  "s": "Defines reusable attestation result information elements and their CBOR/JSON serializations to enable consistent trustworthiness evaluation across heterogeneous Attesting Environments and Verifiers. Provides a standardized approach for Relying Parties to apply consistent policies when interfacing with diverse attestation sources.",
  "n": 2,
  "nn": "Incremental contribution that builds on existing RATS framework; primarily standardizes representation of existing attestation concepts rather than introducing fundamentally new evaluation mechanisms.",
  "m": 4,
  "mn": "Well-specified protocol with defined information model and dual serialization formats (CBOR/JSON); appears implementation-ready though specific test vectors not mentioned in abstract.",
  "o": 3,
  "on": "Shares core concepts with existing RATS work on attestation results and verifiers; extends rather than duplicates but represents predictable evolution of the framework.",
  "mo": 4,
  "mon": "Active IETF WG (rats) development with clear document progression; demonstrates sustained attention to remote attestation standardization.",
  "r": 2,
  "rn": "Tangentially related to AI agents; relevant for agent identity/authentication and A2A protocol infrastructure but not addressing core AI safety, alignment, or agent-specific challenges.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "cBRSKI adapts the BRSKI secure onboarding protocol for resource-constrained IoT devices by replacing JSON vouchers with compact CBOR encoding and substituting HTTPS/EST with CoAPS/CoAP-based alternatives. The protocol enables zero-touch mutual authentication between constrained devices and domain owner networks in bandwidth-limited environments.",
  "n": 2,
  "nn": "Incremental optimization of existing BRSKI framework; primarily a format and transport substitution (JSON→CBOR, HTTPS→CoAPS) rather than fundamental protocol innovation.",
  "m": 4,
  "mn": "Well-defined protocol specification with detailed updates to RFC 8995 and RFC 9148; 93 pages suggests comprehensive technical treatment with likely examples and mechanisms defined.",
  "o": 3,
  "on": "Shares core voucher and mutual authentication concepts with BRSKI; introduces specific optimizations for constrained networks but within established secure onboarding framework.",
  "mo": 4,
  "mon": "Published IETF draft with WG sponsorship (ANIMA); addresses concrete IoT deployment gap where existing BRSKI is impractical, indicating real industry traction.",
  "r": 2,
  "rn": "Focuses on device identity, authentication, and secure bootstrapping infrastructure—tangentially relevant to agent systems only if considering autonomous IoT agents requiring authenticated enrollment.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft analyzes gaps between traditional network configuration protocols (NETCONF, RESTCONF, gNMI, MCP, A2A) and the requirements of LLM-driven intent-based networking. It identifies extension points across five south-bound protocols to enable conversational, semantically-rich multi-agent orchestration.",
  "n": 2,
  "nn": "Applying gap analysis to existing protocols for LLM integration is incremental work; the core insight (existing protocols lack conversational semantics) is unsurprising given their design era.",
  "m": 2,
  "mn": "Early-stage gap analysis document; identifies problems but provides limited concrete protocol extensions, mechanisms, or implementation guidance to close identified gaps.",
  "o": 3,
  "on": "Overlaps with ongoing intent-based networking discussions and LLM-for-ops initiatives; gap analyses for protocol modernization are becoming common in multiple venues.",
  "mo": 1,
  "mon": "Single revision dated 2026-05-06 with no evidence of WG adoption, community feedback iterations, or integration into standards track development.",
  "r": 4,
  "rn": "Directly relevant to AI-driven network operations; addresses real operational gap at intersection of LLMs and network automation, though framing as 'gap analysis' rather than concrete solution limits core relevance.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent discovery/reg",
    "Data formats/interop",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes an architectural framework for establishing cross-domain trust, authentication, and authorization for AI agents communicating across organizational boundaries. Addresses gaps in current agent protocols by defining coherent standards for agent identity, credentialing, delegation, and auditability in a protocol-agnostic manner.",
  "n": 3,
  "nn": "Useful contribution addressing a genuine gap in agent infrastructure, but builds on established trust and PKI concepts; novelty lies in systematic application to agent ecosystems rather than fundamentally new mechanisms.",
  "m": 2,
  "mn": "Early architectural sketch; abstract describes framework intent but 37 pages likely covers vision and design principles rather than detailed protocols, implementation specifications, or test vectors.",
  "o": 3,
  "on": "Shares core concepts with existing PKI, OAuth/OIDC delegation frameworks, and emerging agent standards; some overlap with broader IAM and zero-trust architecture work but applies these to underexplored agent-specific contexts.",
  "mo": 2,
  "mon": "Single draft revision with 2026 date suggests nascent work; no evidence of WG adoption, community feedback cycles, or implementation experiments yet; typical early-stage IETF positioning.",
  "r": 5,
  "rn": "Directly addresses critical infrastructure gap for multi-agent systems; highly relevant to enterprise AI deployments, service-to-service agent communication, and standardization needs in rapidly maturing agent ecosystem.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Addresses trust and security considerations for structured email data, providing MUA recommendations for handling structured message content safely. Focuses on practical guidance rather than new protocols or mechanisms.",
  "n": 2,
  "nn": "Incremental contribution applying existing security principles to structured email domain; lacks novel technical approaches.",
  "m": 2,
  "mn": "Early-stage guidance document without detailed specifications, test vectors, or implementation examples; primarily advisory in nature.",
  "o": 4,
  "on": "Significant overlap with existing email security standards (DKIM, SPF, DMARC) and structured data validation practices; addresses known security patterns.",
  "mo": 3,
  "mon": "Active WG development with recent revision date; part of established Structured Email working group with mailing list activity.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; purely focused on email message security and MUA handling of structured data formats.",
  "c": ["Data formats/interop", "Policy/governance"]
}
```


```json
{
  "s": "Specifies an ACE framework profile combining EDHOC for mutual authentication and OSCORE for securing resource access in constrained IoT environments. Delegates authorization management from resource-constrained servers to more capable hosts while binding client credentials to OAuth access tokens.",
  "n": 2,
  "nn": "Incremental combination of existing protocols (EDHOC, OSCORE, ACE-OAuth) into a standardized profile; limited technical novelty but useful integration for constrained device scenarios.",
  "m": 4,
  "mn": "Well-defined protocol specification with detailed message flows, parameter bindings, and security considerations; likely includes implementation guidance though full test vectors not confirmed from abstract.",
  "o": 3,
  "on": "Shares core concepts with existing ACE profiles and OSCORE deployments; represents natural evolution combining three established IETF standards rather than duplicate effort.",
  "mo": 4,
  "mon": "Active WG development (ACE working group) with multiple related drafts; addressing real IoT standardization needs; 89 pages suggests substantial specification maturity.",
  "r": 2,
  "rn": "Tangentially related to AI agents only through distributed authorization architecture that *could* apply to autonomous agents in constrained IoT networks; not core to AI agent protocols or governance.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "A problem statement draft advocating for IETF standardization of zero trust interoperability frameworks and protocols. The document positions zero trust as essential for modern cloud, remote work, and intelligent agent scenarios, arguing the industry lacks open multi-vendor standards despite NIST guidance.",
  "n": 2,
  "nn": "Problem statement framing is incremental; zero trust concepts are well-established (NIST SP 800-207 exists), and this draft primarily calls for IETF involvement rather than introducing novel approaches.",
  "m": 1,
  "mn": "Pure problem statement with no protocol specifications, mechanisms, or technical definitions. Lacks concrete architectural proposals or scope boundaries for potential standardization work.",
  "o": 4,
  "on": "Significant overlap with existing zero trust frameworks (NIST SP 800-207, CSA guidance) and prior IETF work on authentication, authorization, and identity management. Limited original problem characterization.",
  "mo": 2,
  "mon": "Single revision noted (2026-05-14 date appears future/anomalous). No evidence of WG adoption or community engagement. Preliminary discussion document status.",
  "r": 3,
  "rn": "Partially relevant to AI agents through mention of 'intelligent agents' as a use case, but the draft does not meaningfully address agent-specific authentication, discovery, or governance. Primarily generic zero trust positioning.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes MCP extensions enabling network equipment to act as servers for AI controller clients, defining new capability tokens, tools, resources, and error codes while maintaining backward compatibility with existing MCP implementations.",
  "n": 2,
  "nn": "Incremental extension of existing MCP framework; applies proven JSON-RPC pattern to network domain without introducing novel interaction paradigms or mechanisms.",
  "m": 3,
  "mn": "Defines protocol extensions with capability tokens and error codes, but as 18-page draft likely lacks comprehensive examples, test vectors, and implementation reference code needed for production readiness.",
  "o": 3,
  "on": "Shares conceptual overlap with NETCONF/YANG automation frameworks and existing MCP resource/tool patterns; bridges AI agents and network management but doesn't claim novel integration approach.",
  "mo": 2,
  "mon": "October 2025 draft with single revision shown; no evidence of WG adoption, implementation feedback, or community momentum; appears nascent with limited vendor engagement signals.",
  "r": 4,
  "rn": "Directly relevant as practical application of MCP for autonomous network operations and agent-equipment interaction; addresses real need for standardized AI-equipment communication but positions as narrow domain extension.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent discovery/reg",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "Proposes an architecture enabling LLM-based AI agents to autonomously discover and control CoAP-based IoT devices through hypermedia patterns and semantic metadata, without pre-configured knowledge. Addresses resource discovery, normalized representations, closed-loop observation, and security for agent-driven constrained device interactions.",
  "n": 2,
  "nn": "Incremental combination of existing standards (CoAP, CoRE Link Format, SDF) with LLM agent patterns; the core concepts (REST discovery, hypermedia-driven interaction, semantic descriptions) are well-established; novelty lies mainly in systematic application to agentic scenarios rather than fundamental innovation.",
  "m": 2,
  "mn": "Early sketch with architectural overview; covers conceptual domains (discovery, representation, tooling, observation, monitoring, security) but lacks detailed protocol mechanics, formal specifications, implementation examples, or test vectors; would require substantial expansion for deployment readiness.",
  "o": 3,
  "on": "Shares significant concepts with IETF CoRE work (RFC 6690, SDF), REST/HATEOAS principles, and emerging AI agent architectures; moderate overlap with concurrent LLM-for-IoT efforts but positioning as agent-specific rather than general IoT automation provides some differentiation.",
  "mo": 2,
  "mon": "Single revision dated 2026-04-14 with no apparent prior versions or WG adoption indicated; appears to be exploratory submission to T2TRG (Thing-to-Thing Research Group) rather than mainstream standards track; community momentum not yet evident.",
  "r": 4,
  "rn": "Directly addresses AI agent autonomy in IoT contexts, combining agent reasoning with constrained device control; highly relevant to agent discovery, autonomous netops, and device interoperability; core topic for AI agent standardization but execution clarity needed.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent discovery/reg",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "AID is a DNS-based service discovery protocol for locating agent endpoints via TXT records at _agent subdomains, returning endpoint URIs, tokens, and metadata. It provides minimal, protocol-agnostic discovery designed to work with higher-level frameworks like MCP for actual agent communication.",
  "n": 2,
  "nn": "Incremental contribution—applies standard DNS SRV/TXT discovery patterns (well-established in XMPP, SIP, SMTP) to the agent domain with minor format adaptations rather than introducing novel discovery concepts.",
  "m": 3,
  "mn": "Reasonably defined protocol specification with record format, lookup rules, and security requirements documented, but lacks implementation examples, test vectors, or interoperability evidence typical of mature IETF specs.",
  "o": 4,
  "on": "Significant overlap with existing DNS service discovery mechanisms (RFC 2782 SRV, RFC 6763 mDNS) and emerging agent identity schemes; the primary novelty is framing and AID branding rather than architectural innovation.",
  "m": 2,
  "mn": "Single draft revision with March 2026 date suggests early stage; no evidence of WG adoption, multiple rounds of feedback, or community consensus building typical of advancing IETF work.",
  "r": 4,
  "rn": "Directly relevant to agent identity and discovery infrastructure; addresses real operational need for locating agent services, though positioned as infrastructure enabler rather than core AI/agent technology.",
  "c": [
    "Agent discovery/reg",
    "Agent identity/auth",
    "A2A protocols",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes a 'Reality Layer' framework using signed tokens to prevent autonomous agents from overwhelming system capacity through high-frequency, unintentional signaling. The approach claims O(1) admission control via NIST-validated invariant checking, though lacks implementation details.",
  "n": 2,
  "nn": "Incremental framing of admission control; core concepts (rate limiting, token-based gates) are well-established in networking and distributed systems.",
  "m": 1,
  "mn": "Problem statement articulated but mechanism underspecified; 'NIST-validated Invariant Reality Prism (IRP-189)' appears to be invented terminology with no external reference; no protocol details, examples, or validation.",
  "o": 4,
  "on": "Significant overlap with existing admission control (token buckets, leaky bucket), congestion avoidance, and agent rate-limiting. Reality Token concept mirrors JWT/capability tokens. No differentiation from prior art evident.",
  "mo": 1,
  "mon": "Single revision, 3-page sketch with no implementation signals, test results, or community engagement visible. Terminology suggests lack of grounding in established standards.",
  "r": 2,
  "rn": "Tangentially related to AI agents; frames problem as noise saturation rather than agent alignment, safety, or control. Reads as network traffic management with agent-flavored language rather than addressing core agent governance.",
  "c": [
    "ML traffic mgmt",
    "A2A protocols",
    "Agent identity/auth",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "AERO/OMNI provides IPv6-based mobility and route optimization over virtual overlay multilink interfaces, supporting secured network admission and dynamic neighbor discovery for diverse mobile applications. The mechanism enables flow-based path selection, multihop operation, and mobility management through ND control plane extensions.",
  "n": 2,
  "nn": "Incremental extension combining existing IPv6 ND with overlay networking concepts; core techniques (neighbor discovery, route optimization, mobility management) are established, though application to OMNI virtual interfaces shows some novelty",
  "m": 4,
  "mn": "Well-defined protocol specification with detailed mechanisms (secure admission, forwarding tables, multicast support, multihop operation) across 99 pages; appears implementation-ready though test vectors and deployment examples could strengthen maturity",
  "o": 3,
  "on": "Shares conceptual overlap with existing mobility protocols (MIPv6, NEMO, PMIPv6) and ND-based approaches; OMNI virtual link abstraction is somewhat novel but overall architecture reuses established patterns",
  "mo": 2,
  "mon": "Single draft revision noted (aero3); appears to be niche work by single author without visible WG adoption or community momentum; limited evidence of active development or industry engagement",
  "r": 1,
  "rn": "Not relevant to AI/agent systems; this is a network mobility and routing protocol for aerospace/transportation applications with no connection to artificial intelligence, agent architectures, or autonomous agent networking",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft establishes best practices for managing Route Origin Authorizations (ROAs) in globally anycasted services that use unique origin ASNs per node. It addresses technical risks and mitigation strategies specific to anycast-based RPKI operations.",
  "n": 2,
  "nn": "Incremental contribution applying existing ROA concepts to the specific case of anycast deployments; extends rather than fundamentally innovates RPKI practices.",
  "m": 3,
  "mn": "Provides defined best practices and operational guidance with clear risk identification, but lacks detailed implementation specifications, test vectors, or formal protocol definitions.",
  "o": 4,
  "on": "Significant overlap with existing RPKI governance documents and anycast operational guidelines; primarily combines known concepts rather than introducing novel intersection.",
  "mo": 1,
  "mon": "Single revision (2025-09-03) with no evidence of iterative development, WG discussion, or implementation feedback in the wild.",
  "r": 1,
  "rn": "Not related to AI agents or AI systems; concerns traditional network routing security and RPKI certificate management.",
  "c": ["Policy/governance"]
}
```


```json
{
  "s": "This draft proposes an intelligent routing method for SR Policy that selects among candidate paths based on network quality metrics in MPLS and IPv6 environments. It extends existing segment routing capabilities with quality-aware path selection mechanisms.",
  "n": 2,
  "nn": "Incremental contribution combining existing SR Policy concepts with network quality metrics; lacks novel algorithmic or architectural innovations beyond standard QoS-aware routing approaches.",
  "m": 3,
  "mn": "Defines the routing method conceptually but appears to lack detailed protocol specifications, implementation guidelines, or comprehensive test vectors needed for deployment readiness.",
  "o": 4,
  "on": "Significant overlap with existing IETF work on SR Policy candidate path selection, traffic engineering, and QoS-based routing; similar concepts addressed in RFC 9256 and related drafts.",
  "mo": 1,
  "mon": "Single revision snapshot from June 2025 with no visible development history or WG engagement indicators; appears to be early-stage individual submission.",
  "r": 2,
  "rn": "Not directly relevant to AI agents or autonomous systems; focuses on traditional network routing optimization without autonomous decision-making agents or ML components.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft clarifies RFC7030 EST's ambiguous CSR Attributes Response specification, providing encoding rules and a template-based approach that allows servers to specify both OIDs and extension values, including subject DNs. It updates both RFC7030 and RFC9148 to resolve implementation inconsistencies.",
  "n": 2,
  "nn": "Incremental clarification and enhancement of existing standards; addresses implementation ambiguities rather than introducing fundamentally new concepts.",
  "m": 4,
  "mn": "Well-developed specification with clear encoding rules and template approach; appears implementation-ready with detailed normative guidance for RFC updates.",
  "o": 2,
  "on": "Minor similarities to related PKIX and EST work; primarily a clarification document with limited conceptual overlap to other standards.",
  "mo": 4,
  "mon": "Active LAMPS WG effort with RFC updates signaling strong standardization momentum; addresses practical interoperability problems in established deployments.",
  "r": 2,
  "rn": "Tangentially related to AI agent infrastructure only through certificate-based authentication and identity management; not core to AI/agent topics.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes a hierarchical framework for interconnecting Agent Gateways in a distributed IoA ecosystem, addressing data synchronization, protocol compatibility, and security for cross-domain agent collaboration. Aims to enable scalable communication while maintaining compatibility with existing IoA reference architectures.",
  "n": 2,
  "nn": "Incremental contribution building on established gateway and IoA concepts; hierarchical layering is standard architectural practice. Limited demonstration of novel cross-domain interoperability solutions.",
  "m": 2,
  "mn": "Early-stage framework document (12 pages) specifying requirements and high-level model but lacking detailed protocol specifications, message formats, or implementation examples. No concrete mechanisms or algorithms presented.",
  "o": 4,
  "on": "Significant overlap with existing IoT/IoA gateway architectures, general service mesh patterns, and multi-domain communication frameworks. Domain-specific application appears narrow without clear differentiation from established approaches.",
  "mo": 1,
  "mon": "Single version at 2026-01-30 suggests recent submission; no evidence of iterative refinement, WG engagement, or community discussion. Appears to be initial submission with minimal visibility.",
  "r": 3,
  "rn": "Partially relevant to AI agent ecosystems but primarily addresses infrastructure/networking concerns rather than core agent capabilities, intelligence, or autonomy. Gateway interoperability is supporting infrastructure rather than central agent research.",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"],
  "overall_assessment": "Early-stage networking infrastructure proposal with limited novelty and maturity. Would benefit from concrete protocol specifications, implementation prototypes, and clearer positioning relative to existing IoT/edge computing standards before advancing in IETF process."
}
```


```json
{
  "s": "Proposes an LLM-based framework for automated network traffic classification and resource allocation by extracting multi-modal features from packet data and mapping traffic patterns to computing requirements. Aims to improve QoS, anomaly detection, and resource utilization in dynamic network environments.",
  "n": 2,
  "nn": "Applying LLMs to traffic classification is incremental; combines existing concepts (traffic analysis, feature extraction, resource allocation) without substantial methodological innovation.",
  "m": 2,
  "mn": "Early sketch lacking critical details: no protocol specification, algorithm pseudocode, architecture diagrams, or experimental validation; abstract describes goals but not implementation approach.",
  "o": 4,
  "on": "Significant overlap with existing ML/DL traffic classification work (e.g., RFC 8949 approaches, prior conference papers on neural network-based QoS); LLM application to this domain is explored but not novel.",
  "mo": 1,
  "mon": "Single draft submission with no visible community engagement, WG sponsorship, or revision history; appears to be initial proposal without momentum indicators.",
  "r": 3,
  "rn": "Partially relevant to AI/autonomous networks; focuses on ML-driven network operations but does not address agent protocols, coordination, or autonomous decision-making frameworks typical of agent-centric work.",
  "c": [
    "ML traffic mgmt",
    "Autonomous netops",
    "Model serving/inference"
  ]
}
```


```json
{
  "s": "This draft integrates remote attestation capabilities into EDHOC, a lightweight authenticated key exchange protocol, following the RATS architecture to enable secure verification of device integrity during cryptographic exchanges in IoT and constrained environments.",
  "n": 2,
  "nn": "Incremental contribution that combines existing RATS architecture with established EDHOC protocol; the novelty is primarily in the integration rather than fundamental innovation.",
  "m": 4,
  "mn": "Well-defined protocol specification with detailed procedures; appears implementation-ready though test vectors and interoperability data would strengthen maturity claim.",
  "o": 3,
  "on": "Shares core concepts with RATS framework and EDHOC base protocol; moderate overlap with existing remote attestation and key exchange mechanisms but novel combination.",
  "mo": 4,
  "mon": "Active IETF working group (LAKE) with structured development; 31-page draft indicates substantive ongoing work with community engagement.",
  "r": 2,
  "rn": "Not directly relevant to AI agents; addresses IoT device authentication and integrity verification in constrained networks, tangentially related only through device security aspects.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "AAE proposes a structured authorization container for autonomous AI agents with three mandatory blocks (MANDATE, CONSTRAINTS, VALIDITY) that bind to W3C DIDs and Verifiable Credentials for cryptographically verifiable authorization assertions. The work addresses a genuine gap where existing OAuth 2.0 and API key mechanisms lack machine-evaluable semantics needed for unsupervised agent authorization.",
  "n": 3,
  "nn": "Useful contribution combining existing standards (VCs, DIDs) in a novel arrangement for agent authorization, but the core concepts (time-bounded tokens, capability constraints, cryptographic binding) are well-established; primary novelty is domain application rather than fundamental innovation.",
  "m": 3,
  "mn": "Protocol structure is defined with clear mandatory blocks and binding to standards, but document lacks implementation details, test vectors, code examples, and integration patterns with actual AI frameworks or API gateways.",
  "o": 3,
  "on": "Shares significant conceptual overlap with capability-based access control, SPIFFE/SPIRE, OAuth 2.0 scope delegation, and W3C Verifiable Credential frameworks; distinguishes itself through agent-specific semantics but not fundamentally distinct from existing delegation patterns.",
  "mo": 1,
  "mon": "Single draft dated 2026-05-22 with no evidence of WG sponsorship, community feedback, prior versions, or implementation uptake; appears to be initial submission without established momentum.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent authorization and AI safety governance; timely for production autonomous agents but somewhat narrow in scope (authorization only, not broader agent coordination or safety).",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "AI safety/alignment",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft addresses authorization and access control for autonomous AI agents operating in enterprise campus networks, proposing task-bound privilege reduction ('scope-down') enforced by in-path network devices to maintain compatibility with heterogeneous legacy systems.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (privilege reduction, network-based enforcement, agent identity) applied to a new context (campus agents); lacks novel technical mechanisms.",
  "m": 2,
  "mn": "Early problem statement and motivation document; describes challenge space but provides no concrete protocol specification, implementation details, or enforcement mechanisms.",
  "o": 4,
  "on": "Significant overlap with existing work in zero-trust architecture, capability-based security, microservice authorization (OAuth 2.0 token narrowing), and network policy enforcement; the agent-specific framing is incremental.",
  "mo": 1,
  "mon": "Single draft submission with 8-page limit suggests early exploration; no WG sponsorship indicated, limited visibility of community adoption or follow-up work.",
  "r": 4,
  "rn": "Directly relevant to AI agent security governance; addresses legitimate problem of agent privilege escalation and multi-service orchestration in enterprise settings.",
  "c": ["Agent identity/auth", "Policy/governance", "AI safety/alignment", "Autonomous netops"]
}
```


```json
{
  "s": "This draft defines mechanisms for coordinating EDHOC application profiles through discovery, a CBOR-based representation format, and a set of well-known profiles to ensure successful lightweight authenticated key exchange in constrained environments. It provides both the technical specification and practical profile definitions needed for interoperable EDHOC deployment.",
  "n": 2,
  "nn": "Incremental contribution addressing a practical coordination problem for an existing protocol; the profile concept is established, this formalizes discovery and representation mechanisms.",
  "m": 4,
  "mn": "Well-developed specification with canonical CBOR format definitions and concrete well-known profiles; implementation-ready with clear encoding rules, though test vectors not explicitly mentioned in abstract.",
  "o": 2,
  "on": "Minor overlap with general EDHOC profile work; unique focus on discovery and canonical representation; negligible duplication with existing standards.",
  "mo": 3,
  "mon": "Active development with recent 2024 date; appears part of ongoing LAKE WG standardization effort; moderate community engagement expected for credential/auth protocols.",
  "r": 2,
  "rn": "Tangentially related to AI agents through agent identity/authentication infrastructure; IoT/constrained device focus is orthogonal to core AI agent concerns; relevant for agent platform interop at protocol layer only.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "AIR defines a COSE/CWT-based signed receipt format for binding cryptographic attestation to confidential AI inference events, enabling third-party verification that computations occurred in isolated TEEs. The draft profiles attestation claims for AWS Nitro and Intel TDX, anchoring model identity, I/O hashes, and telemetry to hardware-rooted trust.",
  "n": 2,
  "nn": "Incremental application of existing standards (COSE, CWT, EAT) to a specific use case; the core contribution is narrowly scoped profile definition rather than novel cryptographic or architectural primitives.",
  "m": 4,
  "mn": "Well-structured protocol specification with clear claim definitions and platform-specific measurement profiles; lacks implementation guidance, test vectors, and interoperability validation across multiple TEE implementations.",
  "o": 3,
  "on": "Conceptual overlap with EAT attestation frameworks and existing TEE receipt mechanisms; differs by explicit focus on inference workload receipts and COSE/CWT binding, but limited novelty against concurrent attestation standardization efforts.",
  "mo": 2,
  "mon": "Single revision dated 2026-03-14 with no evidence of WG adoption, community discussion, or competing implementations; appears to be an early individual submission without established momentum.",
  "r": 4,
  "rn": "Directly relevant to model serving, inference integrity, and agent identity/authentication; addresses real need for cryptographic binding of AI computation outputs to hardware attestation, critical for regulated AI deployment.",
  "c": [
    "Agent identity/auth",
    "Model serving/inference",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes an architecture integrating Network Digital Twins with Agentic AI to enable intent-driven autonomous network operations. It positions itself as a cookbook of existing technologies rather than novel components, focusing on how these elements work together for risk-free scenario planning and optimization.",
  "n": 2,
  "nn": "Combines two existing concepts (NDT and Agentic AI) without introducing novel mechanisms or architectural innovations; primarily a systems integration approach.",
  "m": 2,
  "mn": "Early-stage architectural sketch lacking formal specifications, protocols, implementation details, or testable mechanisms; reads more as position paper than technical specification.",
  "o": 4,
  "on": "Significant overlap with existing network automation, intent-based networking, and digital twin literature; agentic AI application to netops is incremental variation of existing autonomy discussions.",
  "mo": 1,
  "mon": "Single revision, no evidence of WG backing or community engagement; appears to be exploratory draft without sustained development momentum.",
  "r": 4,
  "rn": "Directly relevant to AI-driven network operations and agent-based autonomy, though treatment is architectural rather than mechanistic; core relevance to autonomous netops.",
  "c": [
    "Autonomous netops",
    "Policy/governance",
    "Human-agent interaction",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes a DLT-neutral inter-gateway protocol for requesting and sharing asset views across distributed ledger networks, enabling cross-system interoperability while maintaining access control and native consensus logic. The protocol abstracts internal blockchain complexities through gateway nodes that handle view generation, verification, and globally unique addressing.",
  "n": 2,
  "nn": "Incremental contribution addressing a practical interoperability problem in blockchain ecosystems; the core concepts of gateway-mediated cross-chain communication and view abstraction are established patterns in the space.",
  "m": 3,
  "mn": "Protocol architecture is conceptually defined with clear roles (gateways, views, access control) but lacks detailed message formats, state machine specifications, error handling procedures, and concrete implementation examples or test vectors.",
  "o": 4,
  "on": "Significant overlap with existing SATP work, atomic swap protocols, and cross-chain bridge architectures; similar abstraction patterns appear in Polkadot, Cosmos, and other interoperability frameworks already in production.",
  "mo": 2,
  "mon": "Single revision indicated; limited evidence of broader WG adoption or community engagement; addresses a real problem but lacks momentum signals like multiple versions, implementation reports, or stakeholder backing.",
  "r": 1,
  "rn": "Not relevant to AI agents; this is a blockchain/DLT interoperability protocol with no connection to artificial intelligence, autonomous agents, or agent-related networking and governance topics.",
  "c": ["Data formats/interop", "Policy/governance", "Other AI/agent"]
}
```


```json
{
  "s": "This draft proposes a Massive Data Transmission (MDT) framework for efficiently utilizing nighttime bandwidth in high BDP networks through terminal-driven intelligent parameter optimization. It describes use cases, architectural components, and mechanisms for coordinating TCP/network parameters across endpoints, controllers, and network devices.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (TCP tuning, traffic engineering, load balancing) without significant novel mechanisms; parameter optimization for bulk transfer is well-established territory.",
  "m": 2,
  "mn": "Early-stage problem statement with architectural overview but lacks protocol specifications, message formats, detailed algorithms, implementation examples, or interoperability considerations; reads as motivational rather than technical specification.",
  "o": 4,
  "on": "Significant overlap with existing work on TCP parameter optimization (RFC 7323, RFC 9293), software-defined networking load balancing, and ALTO/traffic engineering frameworks; terminal-driven coordination resembles established SDN approaches.",
  "mo": 1,
  "mon": "Single revision, no evidence of WG engagement or community discussion; appears to be initial submission with limited adoption signals or iterative development.",
  "r": 1,
  "rn": "Not relevant to AI/agents—focuses on bulk data transmission optimization, TCP tuning, and network load balancing in traditional datacenter/ISP contexts; no connection to AI systems, autonomous agents, or ML-driven networking.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft specifies mechanisms for supplying nonces to end entities for inclusion in attestation evidence within certificate signing requests across CMP, EST, and CMC protocols. It addresses the freshness guarantee requirement in remote attestation by defining how RAs/CAs can provide nonces to demonstrate evidence timeliness.",
  "n": 2,
  "nn": "Incremental technical contribution combining existing nonce-based freshness concepts with established certificate management protocols; straightforward extension rather than novel methodology.",
  "m": 3,
  "mn": "Protocol mechanism is defined across three frameworks with clear procedures, though appears to lack implementation experience, test vectors, and interoperability validation data.",
  "o": 3,
  "on": "Shares core concepts with existing nonce-based attestation freshness work and certificate management standards; integrates established patterns without significant architectural novelty.",
  "mo": 3,
  "mon": "Active WG development with structured progression (20-page draft at version date), though actual adoption signals and implementation commitments not evident from abstract.",
  "r": 1,
  "rn": "Not relevant to AI agents; focuses on PKI infrastructure, certificate management, and hardware/platform attestation—no connection to autonomous agents, AI safety, or agent protocols.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "This draft standardizes HTTP Cookie and Set-Cookie header fields for HTTP state management, obsoleting RFC 6265 and 6265bis. It addresses historical security and privacy issues while documenting the widely-used cookie mechanism that enables stateful sessions over HTTP.",
  "n": 1,
  "nn": "Trivial update to existing standard; cookies are well-established with no fundamental novelty in this revision",
  "m": 5,
  "mn": "Implementation-ready specification with comprehensive protocol definition, examples, and clear obsolescence of prior standards",
  "o": 5,
  "on": "Near-duplicate of RFC 6265/6265bis; represents incremental standardization update rather than novel work",
  "mo": 3,
  "mon": "Active development with multiple revisions (annevk and johannhof co-authorship suggests sustained WG effort) but not breakthrough momentum",
  "r": 1,
  "rn": "Not relevant to AI agents; cookies are generic HTTP state management with no AI-specific functionality or application",
  "c": ["Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes a new DNS resource record type called AGENT that is compatible with SVCB to improve service resolution for intelligent agent communication protocols. It aims to address gaps in current DNS capabilities for agent-to-agent service discovery and mapping.",
  "n": 2,
  "nn": "Incremental extension of existing SVCB framework; applies established DNS mechanisms to agent domain rather than introducing fundamentally new concepts.",
  "m": 2,
  "mn": "Early sketch stage; abstract suggests problem motivation but 6-page document likely lacks detailed protocol specification, examples, and implementation considerations needed for maturity.",
  "o": 3,
  "on": "Shares core concepts with SVCB and existing service discovery mechanisms; moderate overlap with DNS-based service binding work, though agent-specific application is somewhat differentiated.",
  "mo": 1,
  "mon": "Single revision timestamp (2026-01-05) with no apparent prior versions; appears to be nascent proposal without evidence of iterative development or working group engagement.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; focused on agent service discovery/registration rather than core AI safety, training, or alignment concerns; operationally useful but not central to AI agent research.",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes using MCP (Model Context Protocol) for network management to enable AI integration and expose network capabilities through a more agile architecture. Discusses MCP applicability across IETF IP networks for network exposure, server discovery, and communication between network elements and controllers.",
  "n": 2,
  "nn": "Straightforward application of existing MCP standard to network management domain; lacks novel technical contributions or architectural innovations beyond domain adaptation.",
  "m": 2,
  "mn": "Early-stage applicability exploration document; appears to be a position/discussion paper without detailed protocol specifications, implementation guidance, or validation of proposed MCP patterns in network contexts.",
  "o": 4,
  "on": "Significant conceptual overlap with existing network management frameworks (NETCONF/YANG, intent-based networking) and emerging agent-based network automation discussions; MCP application is relatively straightforward.",
  "mo": 1,
  "mon": "Single recent revision (2026-02-24) with limited evidence of broader WG traction; appears to be an individual submission without demonstrated community adoption or follow-up iterations.",
  "r": 3,
  "rn": "Partially relevant to AI agents; focuses on MCP protocol adaptation for network management rather than core agent capabilities, autonomy, or decision-making aspects.",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "EAR defines a standardized message format for verifiers to encode attestation appraisal results, embedding a trustworthiness vector and contextual information to enable relying parties to make authorization decisions. It supports both simple and composite devices with multiple attesters and can be serialized as CWT or JWT.",
  "n": 2,
  "nn": "Incremental contribution building on established attestation frameworks (AR4SI trustworthiness vectors, EAT); primarily standardizes message encoding rather than introducing novel concepts.",
  "m": 4,
  "mn": "Well-specified protocol with detailed format definitions, 27 pages of technical detail, support for extensions, and serialization options; lacks explicit test vectors and implementation artifacts.",
  "o": 4,
  "on": "Significant overlap with existing RATS ecosystem (EAT, AR4SI, CWT/JWT); EAR serves as a concrete binding mechanism for these established standards rather than novel integration.",
  "mo": 4,
  "mon": "Active IETF WG development (RATS), clear standardization track with dated draft, builds on established consensus standards; represents coordinated ecosystem maturation.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; this is purely a remote attestation and device trust infrastructure standard with no AI/ML/agent components.",
  "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance"]
}
```


```json
{
  "s": "An April Fools' RFC extending avian carrier protocols (RFC 1149) to support cryptographic identity and provenance attestation for AI agents communicating via pigeons. The draft humorously addresses hallucination propagation and authorship tracking in multi-agent LLM delegation chains using feather-based transport.",
  "n": 1,
  "nn": "Trivial extension combining existing satirical RFCs (1149, 2549, 6214) with trendy agent identity concepts; no genuine technical contribution beyond the joke.",
  "m": 1,
  "mn": "Problem statement framed as comedy; no actual protocol specification, mechanisms, or implementation details provided. Explicitly marked April 1 publication.",
  "o": 5,
  "on": "Near-duplicate conceptually of RFC 1149 (Avian Carriers) and RFC 2549 (IP over Avian Carriers); merely adds buzzwords about AI agents without substantive differentiation.",
  "r": 1,
  "rn": "Not genuinely about AI agents or relevant problems—purely a joke draft exploiting current AI hype by pairing it with a well-known IETF April Fools' meme. No real agent identity work.",
  "mo": 1,
  "mon": "April 1 publication with no indication of serious development, follow-up revisions, or WG interest. Designed as one-off satire.",
  "c": ["Agent identity/auth", "Other AI/agent"]
}
```


```json
{
  "s": "Virtual Aggregation (VA) is a FIB suppression technique that allows ISPs to dramatically reduce routing table sizes in individual routers by an order of magnitude without cooperation between ASes. The approach works autonomously within an ISP domain and maintains compatibility with legacy routers while keeping path length increases negligible.",
  "n": 2,
  "nn": "Incremental contribution building on existing aggregation concepts; FIB suppression is a recognized problem with known solution categories, though VA's specific autonomous deployment approach adds some novelty.",
  "m": 4,
  "mn": "Well-defined protocol mechanism with clear specifications for suppression logic, aggregation rules, and deployment scenarios; includes detailed examples and architectural considerations, though lacks comprehensive implementation test vectors.",
  "o": 3,
  "on": "Shares conceptual overlap with CIDR aggregation, route summarization, and other FIB optimization techniques; addresses similar problems as route filtering and selective FIB loading in existing literature.",
  "mo": 2,
  "mon": "Single 2024 revision suggests stable mature draft; appears to be addressing established routing scalability concern without indicating active development momentum or recent community engagement changes.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous agent protocols; this is pure routing infrastructure optimization with no AI/ML, autonomous agent, or intelligent networking components.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Chempat defines a generic family of hybrid post-quantum/traditional key encapsulation mechanisms combining classical DH curves with PQ algorithms like ML-KEM and NTRU Prime. The specification provides concrete instantiated combinations for protocol integration with separate security analysis of the combiner construct.",
  "n": 2,
  "nn": "Hybrid PQ/T KEMs are well-established; this is a systematic enumeration of specific algorithm combinations rather than a novel combining approach.",
  "m": 4,
  "mn": "Detailed specification of concrete instantiated mechanisms with multiple algorithm pairs; appears implementation-ready though test vectors not mentioned in abstract.",
  "o": 4,
  "on": "Significant overlap with existing hybrid KEM frameworks (RFC 9180 hybrid constructs, HPKE patterns); similar enumeration approach to other standardization efforts.",
  "mo": 2,
  "mon": "Single dated submission (2025-10-20); unclear if this is active WG work or independent effort; no indication of revision history or community adoption.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; cryptographic key exchange mechanism is orthogonal to agent protocols unless specifically for agent-to-agent authenticated channels.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "This draft examines applying Zero Trust principles to network infrastructure, arguing that perimeter-centric security models are insufficient for modern distributed environments and advocating for continuous verification of all entities and communications regardless of network location.",
  "n": 2,
  "nn": "Zero Trust concepts are well-established; applying them to network infrastructure is an incremental extension of existing ZT philosophy rather than a novel contribution.",
  "m": 2,
  "mn": "The draft appears to be a position paper or motivational document outlining limitations and principles, but lacks detailed protocol specifications, mechanisms, or implementation guidance.",
  "o": 5,
  "on": "Zero Trust architecture, continuous verification, and internal network protection are extensively covered in existing literature, standards (NIST SP 800-207), and multiple IETF drafts; this work shows near-complete conceptual overlap.",
  "mo": 1,
  "mon": "Single revision dated 2026-01-15 with no evidence of WG engagement, community discussion, or iterative development history.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; focuses on traditional network security architecture without connection to AI/agent-specific concerns.",
  "c": ["Policy/governance"]
}
```


```json
{
  "s": "Proposes a standardized protocol for exchanging context information between AI agents. Aims to enable interoperability and coordination in multi-agent systems through structured message formats.",
  "n": 2,
  "nn": "Incremental contribution; agent communication protocols are well-established in MAS literature, though formalization for IETF may have modest value.",
  "m": 2,
  "mn": "Early sketch phase; 8 pages suggests high-level specification without detailed message formats, state machines, error handling, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing agent communication standards (FIPA ACL, JSON-RPC for agents), semantic web ontologies, and general RPC/messaging protocols; novelty unclear without draft content.",
  "mo": 1,
  "mon": "Single revision at submission; no evidence of WG sponsorship, community discussion, or iterative development cycle typical of progressing IETF work.",
  "r": 4,
  "rn": "Directly relevant to AI agent systems; agent-to-agent communication is core infrastructure need, though relevance depends on whether this addresses genuine interop gaps.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes a single OAuth 2.0 authorization mechanism where AI agents pre-aggregate all required scopes for multi-step workflows, eliminating repeated consent prompts and authorization round-trips. This addresses user friction and efficiency concerns in agent-driven authorization flows.",
  "n": 2,
  "nn": "Incremental extension of OAuth 2.0 that applies existing scope concepts to agent workflows; scope pre-aggregation is a straightforward optimization rather than a novel authorization paradigm.",
  "m": 2,
  "mn": "Early sketch with abstract describing the concept; likely lacks detailed protocol specifications, security analysis of scope prediction accuracy, or implementation guidance for handling dynamic/conditional scope requirements.",
  "o": 3,
  "on": "Shares foundational concepts with OAuth 2.0 incremental authorization, consent bundling patterns, and agent capability specification; some overlap with scope-on-behalf-of and dynamic consent mechanisms in related work.",
  "mo": 1,
  "mon": "Very recent (2026-02-10) single-revision draft with no visible WG discussion, adoption signals, or implementation reports; appears to be early-stage individual submission.",
  "r": 4,
  "rn": "Directly addresses practical authorization challenge in multi-step AI agent workflows; highly relevant to agent identity/auth and human-agent interaction but assumes agents can reliably predict scope needs upfront.",
  "c": ["Agent identity/auth", "Human-agent interaction", "A2A protocols", "Policy/governance"]
}
```


```json
{
  "s": "This draft proposes a CATS-based reference model for AI-Agent Communication Networks (ACN), defining reference points, protocol stacks, and service provisioning for communication between AI agents. It extends the existing CATS framework to accommodate AI agent-specific requirements while maintaining generalizability.",
  "n": 2,
  "nn": "Incremental adaptation of CATS framework to AI agents; limited conceptual novelty beyond applying existing steering mechanisms to a new domain",
  "m": 2,
  "mn": "Early-stage framework sketch; describes reference model structure and signaling procedures but lacks detailed protocol specifications, implementation examples, or validation mechanisms",
  "o": 4,
  "on": "Significant overlap with CATS (Compute-Aware Traffic Steering); builds directly on existing framework with limited differentiation; relates to ongoing agent communication standardization efforts",
  "mo": 1,
  "mon": "Single revision as of Jan 2026; no evidence of WG adoption, community discussion, or iterative development; appears dormant",
  "r": 4,
  "rn": "Directly relevant to AI agent communication infrastructure; addresses real gap in agent-to-agent protocol frameworks, though presentation ties heavily to CATS rather than agent-specific requirements",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "ML traffic mgmt"]
}
```


```json
{
  "s": "Proposes ODSI, a decentralized framework for distributed LLM inference across untrusted participants using layer-wise execution with deadline awareness and cryptographic accountability. Addresses the architectural and coordination challenges of networked inference without specifying concrete protocols.",
  "n": 4,
  "nn": "Novel framing of LLM inference as deadline-constrained, layer-wise distributed computation with explicit treatment of activation transport across untrusted domains; extends CATS concept to inference workloads.",
  "m": 2,
  "mn": "Framework-level specification only; no protocol definitions, message formats, state machines, or implementation guidance provided; defers all concrete technical details to future documents.",
  "o": 2,
  "on": "Minor overlap with federated ML and model serving work; most similar to model parallelism and pipeline parallelism schemes but applied to decentralized settings; activation transport concept is somewhat novel.",
  "mo": 2,
  "mon": "Single draft dated 2026-03-02 with no apparent revision history; CATS working group context suggests some institutional support but limited evidence of broader community adoption.",
  "r": 5,
  "rn": "Core to AI agent infrastructure; directly addresses distributed inference coordination, agent-to-agent model serving, and decentralized AI systems.",
  "c": [
    "Model serving/inference",
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Autonomous netops",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "IPP proposes a cryptographic protocol for binding human intent to autonomous AI agent actions through signed, scope-bounded tokens that preserve an auditable chain from human principal to terminal execution. The protocol uses Ed25519 signatures, DIDs, and a narrowing invariant to enforce lineage, non-repudiation, and interoperability across agent orchestration platforms.",
  "n": 4,
  "nn": "Novel framing of intent-as-primitive with formal scope-narrowing constraints; combines DID-based identity with intent tokens in way not clearly standardized elsewhere, though builds on established crypto primitives.",
  "m": 2,
  "mn": "Early draft stage (18 pages, dated 2026-03-16); describes conceptual model and token structure but lacks implementation details, test vectors, or worked examples of protocol flows.",
  "o": 3,
  "on": "Shares concepts with OIDC delegation, capability systems (OCAP), and blockchain provenance work; token binding resembles macaroons and SAML assertions; overlaps moderately with existing accountability frameworks but intent-specific framing is somewhat novel.",
  "m": 2,
  "mon": "Single dated revision with no visible WG adoption or reference implementations; future date suggests speculative/aspirational status; minimal community momentum apparent.",
  "r": 5,
  "rn": "Directly addresses core AI agent accountability gap (human intent attribution, multi-agent delegation, regulatory compliance); highly relevant to enterprise agent deployments.",
  "c": [
    "Agent identity/auth",
    "Human-agent interaction",
    "Policy/governance",
    "A2A protocols",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "Proposes a target_id extension to OAuth 2.0 to enable granular authorization for AI agents by explicitly identifying authorization targets. Aims to improve permission management and traceability while maintaining backward compatibility with existing OAuth workflows.",
  "n": 2,
  "nn": "Incremental extension adding a single optional field to OAuth 2.0; the core concept of target-based authorization is not novel, though application to AI agents is somewhat new.",
  "m": 2,
  "mn": "Early sketch with abstract concepts but lacking detailed protocol mechanics, implementation examples, or formal specification of how target_id integrates with OAuth 2.0 flows.",
  "o": 4,
  "on": "Significant overlap with existing OAuth 2.0 scope mechanisms and resource indicators (RFC 8707); the differentiation from standard authorization patterns is unclear.",
  "mo": 1,
  "mon": "Single revision dated 2026-01-06 with no evidence of WG discussion, implementation efforts, or iterative development.",
  "r": 3,
  "rn": "Partially relevant to AI agents; addresses authorization but lacks depth on AI-specific security concerns, agent autonomy levels, or delegation patterns unique to agentic systems.",
  "c": ["Agent identity/auth", "Policy/governance"]
}
```


```json
{
  "s": "Proposes a networking framework for agent systems in enterprise and broadband environments, defining core components and their interactions. Attempts to establish foundational architecture for agent-to-agent and agent-to-infrastructure communication.",
  "n": 2,
  "nn": "Incremental framework definition without clear technical innovation; appears to repurpose existing networking concepts for agent systems rather than proposing novel mechanisms or protocols.",
  "m": 2,
  "mn": "Early-stage sketch with abstract component descriptions but lacks concrete protocol specifications, message formats, or implementation details needed for reproducible systems.",
  "o": 4,
  "on": "Significant overlap with existing work on service meshes, microservice architectures, IoT frameworks, and general distributed systems networking—unclear differentiation from established patterns.",
  "mo": 1,
  "mon": "Limited adoption signals; appears to be initial submission without evidence of WG discussion, community feedback, or iterative development process.",
  "r": 3,
  "rn": "Partially relevant to AI agent networking but frames agents primarily as generic distributed entities rather than addressing distinctive AI/ML agent requirements like model serving, inference coordination, or LLM-specific concerns.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Autonomous netops",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "Defines hybrid post-quantum/traditional key exchange methods combining ML-KEM with ECDH for SSH transport layer security. Provides practical cryptographic agility to protect SSH against future quantum threats while maintaining backward compatibility with current algorithms.",
  "n": 2,
  "nn": "Incremental extension applying NIST-standardized ML-KEM to SSH hybrid mode; straightforward combination of existing primitives with established hybrid patterns.",
  "m": 4,
  "mn": "Well-defined protocol specification with explicit algorithm combinations, parameters, and SSH integration details; ready for implementation with clear normative requirements.",
  "o": 4,
  "on": "Significant overlap with concurrent PQ/T hybrid SSH work (RFC 9142 patterns, similar ML-KEM+ECDH combinations); follows established hybrid methodology from broader IETF PQC effort.",
  "mo": 4,
  "mon": "Active IETF SSHM WG adoption expected; aligns with NIST ML-KEM standardization (FIPS 203) and broad industry push for PQC SSH readiness; multiple implementations anticipated.",
  "r": 1,
  "rn": "Not relevant to AI agents; focuses on cryptographic transport security infrastructure with no connection to autonomous agents, ML models, or AI-specific systems.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes an HTTP response header field to disclose AI-generated or AI-assisted content presence and degree. Designed for machine-readability and compatibility with HTTP structured field syntax to serve user agents, bots, and archiving systems.",
  "n": 2,
  "nn": "Incremental extension applying existing header mechanisms to an emerging disclosure need; straightforward application of structured fields to AI content labeling.",
  "m": 3,
  "mn": "Defined protocol mechanism with header syntax specified, but lacks implementation examples, test vectors, and validation guidance for determining AI content degree.",
  "o": 3,
  "on": "Shares conceptual overlap with content labeling schemes (Content-Type headers, metadata frameworks) and overlaps partially with emerging AI transparency initiatives and content provenance standards.",
  "mo": 1,
  "mon": "Single revision dated 2026-01-30 with no visible WG adoption, community discussion, or implementation activity; appears inactive or nascent.",
  "r": 4,
  "rn": "Directly relevant to AI transparency and content governance, addressing human-agent interaction and policy/governance concerns around AI-generated content disclosure.",
  "c": ["Data formats/interop", "Policy/governance", "Human-agent interaction"]
}
```


```json
{
  "s": "Presents use cases for AI-based video recognition and dynamic bandwidth management in telco cloud environments, emphasizing the need for standardized interfaces between cloud and network controllers for resource optimization across heterogeneous computing and network domains.",
  "n": 2,
  "nn": "Combines existing concepts (AI inference, resource scheduling, bandwidth provisioning) in telco context; incremental application rather than novel technical contribution",
  "m": 2,
  "mn": "Early-stage use case document lacking detailed protocol specifications, implementation examples, or architectural standards; primarily motivational rather than prescriptive",
  "o": 4,
  "on": "Significant overlap with existing telco cloud orchestration, RAN intelligence, and network slicing work; similar use cases covered in O-RAN, 3GPP, and ETSI MEC literature",
  "mo": 1,
  "mon": "Single submission with no revision history; appears to be initial draft without indication of WG backing or community engagement",
  "r": 3,
  "rn": "Partially relevant—addresses AI inference deployment and network orchestration but lacks focus on agent autonomy, decision-making, or agent-to-agent protocols central to AI agent standards",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Autonomous netops",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes a reference architecture for privacy-preserving federated learning in multi-tenant AI agent systems, combining federated averaging, differential privacy, and secure aggregation to enable collaborative model training across organizational boundaries while maintaining data isolation. The work addresses a relevant problem at the intersection of federated learning and AI agent deployment but relies primarily on combining existing techniques without substantial novel contributions.",
  "n": 2,
  "nn": "Incremental combination of well-established techniques (federated averaging, differential privacy, secure aggregation); architecture-level contribution is limited and straightforward application of known privacy-preserving mechanisms to multi-tenant agent scenarios.",
  "m": 2,
  "mn": "Early sketch stage; provides architectural overview and abstract concepts but lacks detailed protocol specifications, formal privacy proofs, concrete algorithms, implementation guidance, or test vectors necessary for deployment or standardization.",
  "o": 4,
  "on": "Significant overlap with existing federated learning frameworks (FedAvg, DP-SGD) and secure aggregation protocols; multi-tenant isolation concepts are standard in cloud systems; limited novelty in application-specific adaptations.",
  "mo": 1,
  "mon": "Single submission with no evidence of revision history, working group engagement, or community adoption; no indication of implementation efforts or deployment interest from industry.",
  "r": 4,
  "rn": "Directly relevant to AI agent systems and federated agent training scenarios; addresses real privacy concerns in multi-tenant agent deployments; strong relevance to agent governance and data isolation requirements.",
  "c": [
    "Policy/governance",
    "Agent identity/auth",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "ADL proposes a JSON-based standard for declaring AI agent properties including identity, capabilities, tools, permissions, and security requirements. It aims to enable discovery, interoperability, and lifecycle management across diverse agent platforms and runtimes.",
  "n": 2,
  "nn": "Incremental contribution—applying familiar JSON schema patterns to agent description, similar to existing container/service definition formats adapted for AI context.",
  "m": 3,
  "mn": "Defined protocol structure with clear semantics for agent declaration and media type registration, but limited evidence of implementation maturity or test coverage.",
  "o": 4,
  "on": "Significant overlap with container orchestration schemas (Docker, Kubernetes), OpenAPI/AsyncAPI for capability description, and other emerging agent frameworks (Anthropic's tool-use specs, OpenAI agent specs).",
  "mo": 1,
  "mon": "Single dated revision (2026-03-08) with no evidence of WG sponsorship, community feedback cycles, or adoption signals; appears to be individual submission.",
  "r": 4,
  "rn": "Directly addresses real interoperability challenge in emerging multi-agent ecosystems, though at stage where standardization value depends on market consolidation around agent architectures.",
  "c": [
    "Data formats/interop",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes a trust scoring and identity verification protocol for autonomous AI agents making financial payments, featuring a five-dimension trust model, ECDSA-based cryptographic identity, and spend limit enforcement. Complements the secure MCP specification to address financial trustworthiness in the emerging AI agent economy.",
  "n": 2,
  "nn": "Combines existing cryptographic primitives (ECDSA P-256, challenge-response) with a custom five-dimension trust scoring model; incremental contribution applying known patterns to new domain rather than introducing fundamentally new mechanisms.",
  "m": 3,
  "mn": "Defines protocol structure, trust scoring dimensions, and API endpoints with reasonable detail, but lacks implementation examples, test vectors, or concrete algorithmic specifications for anomaly detection and scoring computation.",
  "o": 3,
  "on": "Trust scoring, spend limits, and behavioral monitoring overlap with existing fraud detection systems and payment authorization protocols; identity verification via challenge-response is standard; novel mainly in AI agent context but not in mechanisms.",
  "mo": 2,
  "mon": "Single draft dated 2026-03-25 with no revision history visible; appears to be early-stage submission without evidence of WG adoption, community feedback cycles, or multiple iterations.",
  "r": 4,
  "rn": "Directly addresses financial risk management for autonomous agents, a genuine gap in AI agent infrastructure; highly relevant to agent economy development though framing as IETF-appropriate is debatable.",
  "c": [
    "Agent identity/auth",
    "AI safety/alignment",
    "Policy/governance",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes OAuth-based extensions for authenticating and authorizing AI agents within Agent Communication Networks. Addresses scalability and trustworthiness requirements for multi-agent systems in vertical industries.",
  "n": 2,
  "nn": "Incremental adaptation of established OAuth framework to agent context; lacks substantive innovation beyond applying existing patterns to new entity types.",
  "m": 2,
  "mn": "Early-stage draft with problem articulation but limited protocol specification detail; 15 pages suggests conceptual framework rather than implementation-ready mechanism.",
  "o": 4,
  "on": "Significant overlap with OAuth 2.0 Device Flow, service-to-service authentication patterns, and emerging IETF work on machine identity; limited differentiation of agent-specific requirements.",
  "mo": 1,
  "mon": "Single dated revision with no evidence of community engagement, working group traction, or iterative refinement cycle typical of progressing IETF work.",
  "r": 4,
  "rn": "Directly addresses legitimate authentication/authorization challenge for AI agent systems, though framing conflates ACN infrastructure concerns with core agent authentication fundamentals.",
  "c": ["Agent identity/auth", "A2A protocols", "Policy/governance", "Agent discovery/reg"]
}
```


```json
{
  "s": "Proposes using LISP (Locator/ID Separation Protocol) as a network substrate for distributed AI agent communication across cloud/edge/endpoint environments. Argues LISP's location transparency and mobility features address requirements like multi-homing and logical isolation at scale for autonomous agent systems.",
  "n": 2,
  "nn": "Incremental application of existing protocol to emerging use case; core idea of using LISP for mobility/location transparency is well-established, application to AI agents is straightforward rather than architecturally novel.",
  "m": 2,
  "mn": "Early sketch stage; abstract indicates exploration of use cases and design considerations, but likely lacks detailed protocol extensions, implementation guidance, or validation of AI agent-specific requirements against LISP mechanisms.",
  "o": 3,
  "on": "Shares fundamental concepts with service discovery and network virtualization literature; overlaps with existing work on LISP for edge computing and distributed systems, though AI agent framing is relatively new.",
  "mo": 1,
  "mon": "Single draft with future date (2026-04-03); no evidence of WG adoption, multiple revisions, or community momentum behind this specific application area.",
  "r": 3,
  "rn": "Partially relevant; addresses networking infrastructure for AI agents but focuses on lower-layer protocol mechanics rather than agent-specific concerns like reasoning, coordination, safety, or autonomy.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Autonomous netops",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "This draft evaluates how existing IETF YANG data models for Attachment Circuits and Traffic Engineering can be applied to edge AI inference deployment, mapping network performance requirements (bandwidth, latency, reliability) to optimal edge location selection for real-time AI workloads.",
  "n": 2,
  "nn": "Incremental application of existing YANG models to an emerging use case; combines established network abstraction patterns with edge AI scenarios but lacks fundamental new concepts.",
  "m": 2,
  "mn": "Early-stage applicability exercise; identifies potential model mappings and gaps rather than proposing concrete protocol mechanisms or detailed specifications with implementation guidance.",
  "o": 3,
  "on": "Shares conceptual overlap with existing TE and ACaaS work; applies established YANG patterns to edge computing but doesn't significantly duplicate prior proposals.",
  "mo": 1,
  "mon": "Single submission with October 2025 date suggests early-stage; no evidence of WG adoption, multiple revisions, or community engagement; appears exploratory rather than active development.",
  "r": 3,
  "rn": "Partially relevant to AI/ML—addresses network requirements for edge AI inference placement but focuses on network service provisioning rather than AI/agent behavior, decision-making, or agent-specific protocols.",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft addresses digital identity management requirements for AI agent communication protocols, proposing a cross-industry universal framework for secure agent-to-agent and agent-to-entity interactions. The work focuses on establishing foundational identity standards as essential infrastructure for future AI agent networks.",
  "n": 2,
  "nn": "Incremental contribution recognizing an important gap, but the requirements-gathering approach is standard practice; lacks novel identity mechanisms or approaches.",
  "m": 1,
  "mn": "Problem statement and motivation only; no protocol specification, architecture, or technical mechanisms defined; abstract-level discussion without concrete proposals.",
  "o": 4,
  "on": "Significant overlap with existing identity/authentication standards (OAuth 2.0, OIDC, DIDs, W3C Verifiable Credentials); limited differentiation for AI agent-specific use cases articulated.",
  "mo": 1,
  "mon": "Single document snapshot; no indication of WG activity, revisions, or community engagement; appears to be exploratory stage without sustained momentum.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure; identity management is genuinely critical for multi-agent systems, though execution and specificity are underdeveloped.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes agent:// URI scheme for identifying and discovering autonomous software agents across systems. Defines four conformance levels from minimal addressing to full descriptor-based discovery with authentication, complementing existing agent communication protocols like MCP and A2A.",
  "n": 2,
  "nn": "Incremental contribution addressing a real gap (URI-based agent addressing), but URI schemes and service discovery are well-established patterns; the novelty lies primarily in applying existing mechanisms to the agent domain.",
  "m": 3,
  "mn": "Protocol specification is defined with layered architecture and conformance levels, though details on descriptor formats, actual discovery mechanisms, and interoperability examples appear limited for a 50-page draft.",
  "o": 3,
  "on": "Shares significant conceptual overlap with DNS-SD, XMPP URI schemes, and existing service discovery frameworks (mDNS, SRV records); positioning relative to these standards unclear.",
  "mo": 2,
  "mon": "Single publication date listed (2026-04-18, appears future-dated); no evidence of WG adoption, multiple revisions, or community discussion; appears early-stage work.",
  "r": 4,
  "rn": "Directly addresses a real interoperability need in the emerging agent ecosystem, though relevance depends on whether agent:// becomes adopted versus existing HTTP/gRPC endpoints.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes a standardized vocabulary for declaring AI usage restrictions and permissions on digital assets, enabling automated systems to respect content creator preferences. Addresses growing need for machine-readable consent mechanisms as AI training and processing become ubiquitous.",
  "n": 2,
  "nn": "Incremental contribution building on existing robot.txt/metadata patterns; core concept of preference vocabularies is established but application to AI-specific use cases is somewhat novel.",
  "m": 3,
  "mn": "Defines protocol/mechanism with reasonable structure but lacks implementation details, test vectors, and validation examples; ready for review but needs maturity for production deployment.",
  "o": 4,
  "on": "Significant overlap with C2PA, Data Nutrition Labels, and schema.org markup approaches; competes with robot.txt extensions and emerging AI-specific metadata standards; positioning relative to these lacks clarity.",
  "mo": 2,
  "mon": "Single revision cycle evident; limited WG engagement signals; vocabulary definitions present but adoption pathway and community backing appear underdeveloped.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and data usage control; addresses legitimate concern but positioned as infrastructure layer rather than core agent protocol.",
  "c": [
    "Policy/governance",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "Proposes a normative framework for evaluating admissibility of autonomous agent speech acts based on modality and grounding state rather than semantic truth. Enables deterministic, auditable assessment of agent statements without requiring truth verification or semantic interpretation.",
  "n": 2,
  "nn": "Incremental formalization of existing agent communication concepts; applies standard speech act theory (Austin/Searle) to agent verification without substantial novelty in the underlying philosophy or mechanisms.",
  "m": 2,
  "mn": "Early sketch with conceptual framework; defines admissibility categories but lacks detailed specifications, implementation guidance, concrete examples, test vectors, or algorithmic precision needed for practical deployment.",
  "o": 4,
  "on": "Significant overlap with speech act theory, agent communication frameworks, and existing IETF work on agent protocols; the core distinction (grounding-based rather than truth-based evaluation) is narrow and not deeply differentiated from prior work.",
  "mo": 1,
  "mon": "Single draft from January 2026 with no visible revision history, WG adoption, or community discussion; no evidence of active development or stakeholder engagement in the agent standardization community.",
  "r": 3,
  "rn": "Partially relevant to AI agents and autonomous systems; addresses agent communication semantics but lacks connection to practical agent deployment, interoperability standards, or current IETF agent-related work streams.",
  "c": [
    "A2A protocols",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```