```json
{
  "s": "Mangrove proposes a unified framework for obtaining global Internet visibility by aggregating traceroute, BGP, IP allocation, and measurement data across hierarchical levels. It constructs a comprehensive topology and routing model with extensible rules to compute packet paths and performance metrics while handling real-time dynamics through incremental updates.",
  "n": 2,
  "nn": "Multi-source data aggregation for Internet topology is incremental; core techniques (traceroute, BGP analysis, hierarchical indexing) are well-established. Primary contribution is the integration framework rather than novel methodology.",
  "m": 2,
  "mn": "Early-stage sketch with conceptual architecture but lacks implementation details, test cases, data schemas, or evaluation results. No API specifications, algorithm pseudocode, or experimental validation provided.",
  "o": 4,
  "on": "Significant overlap with existing work: CAIDA topology databases, RIPEstat, BGP analysis platforms, and academic Internet mapping projects all employ similar multi-source aggregation and hierarchical indexing approaches. Limited differentiation articulated.",
  "mo": 1,
  "mon": "Single draft revision (2024-09), no WG affiliation despite 'workgroup' in title, no apparent community adoption or ongoing development momentum visible.",
  "r": 2,
  "rn": "Tangentially related to AI/agent systems only through potential applications for autonomous network operations; primary focus is Internet topology modeling and routing, not AI agent topics or autonomous agent infrastructure.",
  "c": [
    "Data formats/interop",
    "Autonomous netops",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes a framework for cross-device communication between AI agents deployed on network devices to enable collaborative tasks like network troubleshooting. Analyzes protocol requirements for agent coordination across heterogeneous network infrastructure.",
  "n": 2,
  "nn": "Incremental application of existing agent communication concepts to network device context; lacks novel architectural or protocol innovations.",
  "m": 2,
  "mn": "Early-stage framework document with problem analysis but no detailed protocol specification, implementation examples, or validation mechanisms provided.",
  "o": 4,
  "on": "Significant overlap with existing agent communication protocols (FIPA ACL, gRPC, REST APIs) and network management frameworks; limited differentiation articulated.",
  "mo": 1,
  "mon": "Single draft submission with no visible revision history, WG engagement, or community adoption signals; appears to be initial proposal.",
  "r": 3,
  "rn": "Partially relevant to AI agent deployment; focuses on network operations use cases rather than core AI agent capability challenges like reasoning, safety, or coordination semantics.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent discovery/reg",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft proposes Warrant Certificate Authorities (WCA), a cryptographic attestation infrastructure to track data provenance through LLM agent tool-call chains, addressing 'semantic laundering' where data gains unearned trustworthiness crossing tool boundaries. The system draws on PKI, OS provenance monitoring, and supply-chain security frameworks with graduated adoption levels (WAL-0 through WAL-3).",
  "n": 4,
  "nn": "Applies reference monitor properties and PKI patterns to a genuinely novel problem space (agent data provenance), though individual components draw from established domains.",
  "m": 3,
  "mn": "Protocol structures and certificate formats defined; Warrant Attestation Levels specified; lacks implementation details, test vectors, and deployment guidance for production readiness.",
  "o": 2,
  "on": "Minor conceptual overlap with attestation/provenance work (IMA, CamFlow) and supply-chain security (SLSA, in-toto); the agent-specific application and 'semantic laundering' framing appear novel.",
  "mo": 2,
  "mon": "Single draft dated 2026-03-01 with no apparent revision history or WG sponsorship evident; early-stage proposal without community traction signals.",
  "r": 4,
  "rn": "Directly addresses critical trust and epistemology challenges in multi-tool agent systems; highly relevant to emerging LLM deployment concerns, though not yet mainstream IETF focus.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "A2A protocols",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "This draft extends TLS 1.3 with a post-compromise security mechanism by enabling fresh Diffie-Hellman key exchanges within active sessions, rather than relying solely on the standard KeyUpdate mechanism. It addresses security risks in long-lived sessions common in industrial IoT and telecommunications by regularly renewing session keys to limit the impact of key compromise.",
  "n": 2,
  "nn": "Incremental extension to TLS 1.3; combines existing concepts (KeyUpdate, ephemeral DH) in a straightforward manner without fundamental cryptographic innovation.",
  "m": 4,
  "mn": "Well-structured protocol specification with clear mechanism definition, applicable to both TLS 1.3 and DTLS 1.3; appears implementation-ready but maturity depends on test vectors and interop testing.",
  "o": 3,
  "on": "Shares conceptual overlap with post-compromise security literature and session key refresh mechanisms; relates to prior work on perfect forward secrecy extensions but offers a concrete formalization.",
  "mo": 2,
  "mon": "Single revision dated 2026-03-02 suggests early-stage draft; limited evidence of WG discussion or multiple iterations; adoption momentum unclear.",
  "r": 1,
  "rn": "Not relevant to AI/agent systems; purely a cryptographic transport layer enhancement unrelated to AI agents, distributed systems governance, or agent protocols.",
  "c": []
}
```


```json
{
  "s": "Proposes a protocol-agnostic data model enabling multi-agent communication for autonomous network operations at Level 4 autonomy. Addresses secure and efficient interaction between intelligent agents across network layers for self-management and closed-loop operations.",
  "n": 2,
  "nn": "Incremental contribution combining existing multi-agent concepts with network autonomy; data model approach is straightforward extension of agent coordination patterns",
  "m": 2,
  "mn": "Early-stage specification; appears to define conceptual framework and data model structure but lacks detailed protocol mechanics, formal semantics, implementation examples, or test vectors",
  "o": 4,
  "on": "Significant overlap with IETF autonomic networking (ANI), intent-based networking (IBN) work, and existing multi-agent interaction frameworks; relationship to prior work unclear",
  "mo": 1,
  "mon": "Single submission as recent draft; no evidence of WG adoption, multiple revisions, or community engagement; nascent topic with uncertain trajectory",
  "r": 4,
  "rn": "Directly relevant to autonomous network operations and agent coordination; timely for network automation discussions but positioning relative to AI/ML agent ecosystem needs clarification",
  "c": ["A2A protocols", "Autonomous netops", "Agent discovery/reg", "Data formats/interop", "Policy/governance"]
}
```


```json
{
  "s": "Internet 2.0 proposes a new web architecture layer treating AI models as first-class network entities, introducing HTTP+AI, a Model Resolution Network (DNS-analogue for models), and AI-aware browsers for intent-based semantic interaction. The vision extends beyond document retrieval toward distributed model discovery and protocol-level AI interaction.",
  "n": 2,
  "nn": "Repackages existing concepts (model APIs, discovery services, semantic routing) under an 'Internet 2.0' framing rather than proposing fundamentally new mechanisms; resembles API gateway and service mesh patterns applied to ML.",
  "m": 1,
  "mn": "Conceptual vision document without protocol specifications, formal grammar, interaction examples, or concrete technical details; HTTP+AI and MRN remain abstract proposals.",
  "o": 4,
  "on": "Substantial conceptual overlap with service mesh architectures (Istio, Envoy), API gateways, model serving platforms (Seldon, BentoML), and existing ML model registries; intent-based routing echoes policy-based networking and semantic web efforts.",
  "mo": 1,
  "mon": "Single undated submission with no visible revision history, WG discussion, or community engagement signals; appears to be a standalone position paper rather than active standardization effort.",
  "r": 4,
  "rn": "Directly addresses agent discovery, model serving infrastructure, and protocol design for AI systems; relevant to distributed AI agent ecosystems but positioned as architectural vision rather than solving specific interoperability or safety gaps.",
  "c": [
    "Agent discovery/reg",
    "Model serving/inference",
    "A2A protocols",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Proposes a Network Management Agent (NMA) architecture leveraging AI for autonomous network operations at Level 4 autonomy, positioned to work alongside SDN controllers for intent-based reasoning and autonomous planning without duplicating policy control.",
  "n": 2,
  "nn": "Incremental contribution combining existing SDN concepts with generic AI agent frameworks; lacks novel architectural insights or theoretical advances specific to network management domains.",
  "m": 2,
  "mn": "Early-stage conceptual document (24 pages) lacking protocol specifications, interface definitions, concrete data models, or reference implementations; reads as position paper rather than technical specification.",
  "o": 4,
  "on": "Significant overlap with established autonomous networking (ONAP, ORAN), intent-based networking (IBN), and AI/ML in networking literature; limited differentiation from generic LLM agent frameworks applied to networking.",
  "mo": 1,
  "mon": "Single draft revision (2026-02-27 date suggests very recent); no evidence of WG sponsorship, multiple contributors, or iterative refinement cycle typical of active IETF work.",
  "r": 4,
  "rn": "Directly relevant to AI-driven network operations and autonomous agent architectures; addresses timely intersection of LLM capabilities with network management, though framing as IETF standardization may be premature.",
  "c": [
    "Autonomous netops",
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Policy/governance",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes a PKI-based trust model for multi-agent AI systems using X.509 certificates, spawn chain cryptography, and dual-signature policies to establish verifiable agent identity and provenance. Applies existing standards (OAuth 2.0, CRL) to agent-to-agent authorization without addressing resource access control or agent behavior.",
  "n": 2,
  "nn": "Incremental application of established PKI/identity patterns to agents; core concepts (X.509, OAuth On-Behalf-Of, spawn chains) are standard techniques adapted rather than novel.",
  "m": 3,
  "mn": "Defines protocol mechanisms and trust model structure with specified primitives, but 16 pages suggests moderate detail; likely lacks implementation guidance, test vectors, or formal security proofs.",
  "o": 4,
  "on": "Significant overlap with existing work on service-to-service identity (mTLS, SPIFFE/SVID), delegation patterns (OAuth 2.0 On-Behalf-Of), and supply chain provenance; positions as agent-specific but mechanisms are largely standard.",
  "m": 2,
  "mon": "Single draft dated 2026-05 with no evident prior versions or WG adoption; appears early-stage with unclear community engagement or revision trajectory.",
  "r": 4,
  "rn": "Directly relevant to agent identity and authorization in multi-agent systems, but narrow scope excluding behavior, resource enforcement, and orchestration limits impact on core AI agent concerns.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Policy/governance",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "AIP proposes a two-layer protocol for AI agent identity and authorization, assigning unique identifiers and cryptographic keys to agents while enforcing declarative policies at tool-access boundaries. Addresses the critical problem of unbounded agent permissions and lack of identity boundaries between human and non-human actors.",
  "n": 3,
  "nn": "Core concept of agent identity + policy enforcement is useful but not novel; combines existing patterns (PKI, proxy interposition, declarative policies). Execution model is straightforward application of established security principles to agentic systems.",
  "m": 3,
  "mn": "Protocol structure is defined with two clear layers and stated mechanisms, but 30 pages likely lacks detailed specification depth, test vectors, and implementation guidance needed for production deployment. Appears to be a conceptual draft rather than implementation-ready specification.",
  "o": 4,
  "on": "Significant overlap with existing work: ACL/RBAC frameworks, mTLS/certificate-based auth, OAuth 2.0 token patterns, API gateway proxies (Kong, Envoy), and emerging agent frameworks (LangChain middleware, tool-use policies). Limited novelty in component design.",
  "mo": 2,
  "mon": "Appears to be single-submission draft with no indication of WG backing, multiple revisions, or community adoption signals. March 2026 date and minimal metadata suggest early-stage, low-visibility effort without demonstrated momentum.",
  "r": 4,
  "rn": "Directly addresses critical operational gap in current AI agent deployments: unbounded permissions and lack of auditability. Highly relevant to agent security/governance but presented as general protocol rather than ecosystem-specific solution.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "AI safety/alignment",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "MCP-AX adapts the AgentX protocol architecture to enable hierarchical composition of tool namespaces across distributed MCP servers, introducing recursive delegation and capability-aware routing for AI agent systems. The protocol targets heterogeneous deployments from cloud to embedded devices with features like transport bridging and irreversibility-gated dispatch.",
  "n": 2,
  "nn": "Incremental adaptation of established AgentX master-subagent pattern to a different domain (tools vs OIDs); hierarchical delegation concept is not novel, though application to MCP tool namespaces adds modest value.",
  "m": 3,
  "mn": "Protocol mechanisms are defined with architectural patterns clear, but document length (25pg) suggests incomplete specification; unclear if implementation examples, test vectors, or reference implementations exist.",
  "o": 4,
  "on": "Significant overlap with AgentX (RFC 2741) architecture and intent; shares delegation patterns with existing service mesh and federation protocols; namespace composition is well-explored in other distributed systems contexts.",
  "mo": 1,
  "mon": "Single draft submission with May 2026 date (future); no evidence of working group sponsorship, multiple revisions, or community adoption; appears to be early-stage individual submission.",
  "r": 4,
  "rn": "Directly addresses tool/capability orchestration across distributed AI agent systems, which is a core operational need; MCP relevance is high if MCP gains adoption, but current relevance is dependent on MCP ecosystem maturity.",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "Model serving/inference"]
}
```


```json
{
  "s": "Proposes AI Network Traffic Optimization Agents as autonomous entities to dynamically manage network resources and routing in real-time, replacing static optimization methods. Describes three key use cases: tunnel adjustment with adaptive routing, traffic steering with application-aware policies, and network slice lifecycle automation with SLA compliance.",
  "n": 2,
  "nn": "Incremental application of AI/ML concepts to known network optimization problems; lacks novel algorithmic or architectural contributions beyond framing existing techniques as 'agent'-based systems.",
  "m": 2,
  "mn": "Early-stage use case document with abstract scenarios but no concrete protocols, APIs, data models, or implementation guidance; primarily motivational rather than specification-oriented.",
  "o": 4,
  "on": "Significant conceptual overlap with existing AI-driven networking, SDN/NFV optimization, and autonomous network management initiatives (ONAP, O-RAN, IETF NMOP); limited differentiation from prior agent-based network control proposals.",
  "mo": 1,
  "mon": "Single draft submission with no visible WG sponsorship, revision history, or community engagement; no indication of active development momentum or adoption interest.",
  "r": 3,
  "rn": "Directly addresses AI agents in networking context but frames agents loosely as any autonomous optimization entity rather than exploring deeper agent-specific challenges (coordination, safety, explainability, standardization).",
  "c": [
    "ML traffic mgmt",
    "Autonomous netops",
    "Policy/governance",
    "Agent discovery/reg",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes a Distributed Inference Network architecture to address scalability, latency, and security challenges of centralized AI inference through edge-cloud collaboration and intelligent scheduling. Document establishes problem statement and requirements for supporting low-latency, high-concurrency AI services across billions of users and devices.",
  "n": 2,
  "nn": "Incremental contribution combining well-established concepts (edge computing, load balancing, distributed inference) without novel architectural or protocol innovations.",
  "m": 1,
  "mn": "Problem statement and use cases only; no protocol specifications, mechanisms, or implementation details provided.",
  "o": 4,
  "on": "Significant overlap with existing IETF work on edge computing (MEC), service placement, traffic engineering, and application-layer load balancing; concepts align with established distributed systems patterns.",
  "mo": 2,
  "mon": "Single revision as requirements draft; limited evidence of WG traction or community adoption at this stage of development.",
  "r": 4,
  "rn": "Directly relevant to AI service deployment and agent infrastructure, though framed as network problem rather than core AI agent protocol work.",
  "c": ["Model serving/inference", "ML traffic mgmt", "Autonomous netops", "Policy/governance", "Agent discovery/reg"]
}
```


```json
{
  "s": "DAAP proposes an OAuth 2.0-based authorization framework for AI agents performing autonomous actions on behalf of humans, combining DIDs for agent identity, JWT grants with agent claims, real-time revocation, audit trails, and policy engine integration. The protocol aims to provide cryptographic accountability and human-verifiable consent for delegated agent authorization across third-party services.",
  "n": 3,
  "nn": "Applies established OAuth 2.0 patterns to agent delegation with useful additions (DIDs, audit trails, budget controls, cascade revocation), but core concepts are incremental extensions rather than fundamentally novel approaches to the agent authorization problem.",
  "m": 3,
  "mn": "Protocol is reasonably well-specified with defined flows, token formats, and integration points (OPA, Cedar), but lacks implementation details, test vectors, and real-world deployment guidance needed for production readiness.",
  "o": 3,
  "on": "Shares significant conceptual overlap with OAuth 2.0 extensions, capability-based delegation models, and existing agent frameworks; distinguishing contributions (audit trails, multi-agent cascade) are incremental rather than architecturally distinct.",
  "mo": 2,
  "mon": "Single draft revision with 2026 date suggests early stage; no evidence of WG adoption, implementation experience, or community engagement; positioning relative to IETF's OAuth working group momentum unclear.",
  "r": 4,
  "rn": "Directly addresses critical problem of human-verifiable AI agent authorization and accountability, which is timely and practically relevant; however, focuses narrowly on protocol mechanics rather than broader AI safety/alignment concerns.",
  "c": [
    "Agent identity/auth",
    "Human-agent interaction",
    "Policy/governance",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes autonomic setup of fog monitoring agents using GRASP protocol to handle dynamic IoT environments with volatile computational resources. Addresses orchestration of service function chains across heterogeneous fog nodes through autonomous agent coordination.",
  "n": 2,
  "nn": "Incremental application of existing autonomic/GRASP concepts to fog monitoring; combines well-established technologies without significant innovation in the core mechanisms.",
  "m": 2,
  "mn": "Early sketch phase; presents use case and conceptual application of GRASP to fog monitoring but lacks detailed protocol specifications, implementation details, or validation.",
  "o": 3,
  "on": "Shares core concepts with existing ANIMA work and GRASP specifications; fog monitoring and service function chain orchestration have been addressed in related drafts.",
  "mo": 1,
  "mon": "Single revision from 2024; appears to be early/inactive draft with limited community engagement or WG adoption signals.",
  "r": 4,
  "rn": "Directly relevant to autonomous network operations and agent discovery/registration within IoT/fog environments; addresses autonomous agent coordination without being primarily an AI/ML work.",
  "c": ["Autonomous netops", "Agent discovery/reg", "A2A protocols", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes an evaluation framework for LLM-based agents performing intent-driven network configuration tasks, combining emulation environments, representative tasks, and multi-dimensional metrics. Aims to enable reproducible and fair benchmarking of different LLM-driven approaches for autonomous network operations.",
  "n": 2,
  "nn": "Benchmark frameworks for network tasks are established practice; applying this to LLM agents is incremental rather than fundamentally novel. Combines existing concepts (emulation, metrics, task suites) without introducing new theoretical insights.",
  "m": 2,
  "mn": "Early-stage framework document lacking implementation details, test vectors, or concrete metrics specifications. No evidence of prototype implementation or empirical validation of the proposed evaluation methodology.",
  "o": 3,
  "on": "Overlaps with existing network benchmarking work (RFC 2544-style frameworks) and general ML benchmark design patterns. Some similarity to emerging LLM evaluation suites, though network-specific application is somewhat novel.",
  "m": 1,
  "mon": "Single submission with future date (2025-12-30 appears to be placeholder). No revision history, no WG affiliation visible, and no evidence of community engagement or iterative development.",
  "r": 4,
  "rn": "Directly addresses autonomous network operations using LLM agents, which is a core emerging topic in network automation. Relevant to NMRG (Network Management Research Group) charter and current industry interest in AI-driven NetOps.",
  "c": [
    "Autonomous netops",
    "ML traffic mgmt",
    "Data formats/interop",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes applying existing standards (WIMSE, OAuth 2.0) to AI agent authentication and authorization rather than defining new protocols. Aims to identify gaps and guide future standardization for agent identity and access control in multi-system environments.",
  "n": 2,
  "nn": "Incremental contribution—straightforward application of established identity/auth frameworks to AI agents without novel cryptographic or architectural innovations.",
  "m": 2,
  "mn": "Early sketch phase; describes conceptual mapping of existing standards to agent scenarios but likely lacks detailed protocol specifications, implementation examples, or test vectors at 26 pages.",
  "o": 4,
  "on": "Significant overlap with concurrent work on workload identity, OAuth 2.0 extensions, and emerging agent-oriented IAM frameworks; repackages known standards rather than introducing differentiated mechanisms.",
  "mo": 2,
  "mon": "Single revision snapshot (2026-03-30); no visible WG adoption signals or iterative community engagement evident; limited momentum indicators for standardization track.",
  "r": 4,
  "rn": "Directly relevant to agent authentication and identity governance; timely given AI deployment scale, though framed conservatively as standards reuse rather than agent-specific innovation.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "A2A protocols",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes a semantic routing architecture that uses AI agent-level semantics (intent vectors, trust scores, service identity) instead of traditional IP routing to enable intelligent multi-agent communication. The system aims to transform networks from passive transport into active collaboration substrates for coordinated agent operations.",
  "n": 2,
  "nn": "Incremental combination of existing concepts—semantic routing, intent-based networking, and trust-based policy enforcement—applied to a new domain (AI agents) without substantial technical innovation in routing mechanisms themselves.",
  "m": 2,
  "mn": "Early-stage draft with conceptual architecture but lacking detailed protocol specifications, message formats, routing algorithms, or implementation guidance; no clear mechanisms for practical deployment.",
  "o": 4,
  "on": "Significant overlap with intent-based networking (IBN), service mesh architectures (Istio, Linkerd), and semantic routing literature; the AI agent framing is novel but underlying technical approach closely mirrors existing paradigms.",
  "mo": 1,
  "mon": "Single revision as of May 2026 with no evident WG adoption, community discussion, or implementation reports; appears to be a standalone submission without clear momentum.",
  "r": 3,
  "rn": "Partially relevant to AI agents—addresses multi-agent communication and coordination, but focuses primarily on network routing rather than core agent capabilities, reasoning, alignment, or safety concerns.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Policy/governance",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft proposes the Agent Attachment Protocol (AAP) to enable AI agents to attach to edge nodes and exchange endpoint identifiers, communication mechanisms, and attachment context. The protocol aims to support routing, forwarding, and discovery functions for agent-to-agent communication in edge environments.",
  "n": 2,
  "nn": "Incremental application of edge attachment concepts to AI agents; lacks clear differentiation from existing mobile/endpoint attachment protocols (MobileIP, PMIPv6, etc.)",
  "m": 2,
  "mn": "Early draft stage with abstract concepts; no detailed protocol specification, message formats, state machines, or implementation examples provided",
  "o": 4,
  "on": "Significant overlap with established attachment protocols; concepts of endpoint registration, property advertisement, and edge attachment are well-explored in mobile networking and SDN literature",
  "mo": 1,
  "mon": "Single 2026 revision with no evidence of WG discussion, community feedback, or iterative development; appears to be initial submission",
  "r": 3,
  "rn": "Partially relevant to AI agent networking; addresses infrastructure concerns but lacks engagement with actual agent communication patterns, multi-agent coordination, or real deployment scenarios",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Autonomous netops",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes unified orchestration between optical transport networks and distributed AI computing infrastructure to enable bidirectional awareness and joint resource provisioning. Addresses the gap where optical networks and compute schedulers operate with isolated control planes, causing suboptimal performance for geographically dispersed AI workloads.",
  "n": 3,
  "nn": "Problem identification is timely and well-motivated, but the core concept of cross-domain orchestration and intent-driven provisioning is not fundamentally novel; similar coordination patterns exist in NFV/SDN and cloud networking contexts.",
  "m": 1,
  "mn": "Pure problem statement document with use cases and high-level requirements; lacks concrete protocol design, architectural specifications, data models, or implementation guidance.",
  "o": 3,
  "on": "Shares conceptual overlap with existing CCAMP work, SDN/NFV orchestration frameworks, and intent-based networking proposals; differentiator is specific focus on AI computing-optical integration but treatment remains abstract.",
  "mo": 2,
  "mon": "Single recent submission (2026-03-02); no evidence of prior iterations, community discussion, or WG sponsorship; early-stage draft with unclear adoption trajectory.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure and distributed AI system coordination; addresses real operational gaps in modern AI deployments, though framed more as network optimization than autonomous agent interaction.",
  "c": [
    "ML traffic mgmt",
    "Autonomous netops",
    "Data formats/interop",
    "Model serving/inference"
  ]
}
```


```json
{
  "s": "This draft proposes using special text tags to improve data quality and contextual understanding in conversational AI models during training and inference. The approach aims to enhance model accuracy and response relevance through structured markup.",
  "n": 2,
  "nn": "Incremental contribution; markup-based context enhancement is a straightforward extension of existing prompt engineering and data annotation practices rather than a fundamentally novel concept.",
  "m": 2,
  "mn": "Early sketch phase; presents high-level concept without detailed specification, formal syntax definition, implementation guidelines, or empirical validation methodology.",
  "o": 4,
  "on": "Significant overlap with existing work in prompt engineering, structured data annotation, semantic markup (XML/JSON in training data), and context injection techniques already widely used in LLM fine-tuning.",
  "mo": 1,
  "mon": "No evidence of WG support, community adoption, or iterative development; appears to be single submission without demonstrated momentum in IETF or broader AI community.",
  "r": 2,
  "rn": "Tangentially related to AI agents; focuses on training data quality rather than agent protocols, autonomous operations, or inter-agent communication mechanisms core to IETF AI agent work.",
  "c": ["Data formats/interop", "Human-agent interaction", "Other AI/agent"]
}
```


```json
{
  "s": "AITLP defines a protocol for managing autonomous software agent identity, trust, and lifecycle within organizational boundaries, emphasizing constraint enforcement and auditability. The protocol complements capability-focused specs by focusing on what agents cannot do rather than what they can, using certificate-based authentication and hierarchical mandate mechanisms.",
  "n": 3,
  "nn": "Organizational governance framework for agents is useful and needed, but combining identity, trust, lifecycle, and scope management within a single protocol is somewhat incremental over existing PKI and capability-based approaches.",
  "m": 3,
  "mn": "Protocol structure and major concepts are defined across 47 pages with mandate enforcement and ALM mechanisms specified, but appears to lack implementation details, test vectors, and concrete examples demonstrating real-world deployment scenarios.",
  "o": 3,
  "on": "Overlaps with A2A protocols in authentication/trust aspects, with policy governance frameworks, and with agent capability specs (MCP, ANS) in scope definition. Core novelty is the lifecycle and mandate-centric integration rather than fundamentally new mechanisms.",
  "m": 2,
  "mon": "Published as April 2026 draft with single revision visible; no clear evidence of WG adoption, implementation feedback, or community momentum. Appears exploratory rather than driven by established ecosystem demand.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent governance and safety, addressing critical organizational needs around agent auditability and authority constraints. Highly relevant to enterprise AI deployment but may be less critical for open-ecosystem agent development.",
  "c": ["Agent identity/auth", "Policy/governance", "AI safety/alignment", "A2A protocols"]
}
```


```json
{
  "s": "Proposes a framework for AI agent networks using an Agent Network Protocol (ANP) to enable communication within trusted domains. Addresses basic functions needed for agent-to-agent interaction but lacks detailed specification and implementation maturity.",
  "n": 2,
  "nn": "Incremental contribution applying existing network protocol concepts to AI agents; the core idea of agent communication frameworks is not novel, though domain-specific application may have merit.",
  "m": 2,
  "mn": "Early sketch stage with abstract-only detail; framework definition present but lacks protocol specification details, message formats, authentication mechanisms, or implementation examples.",
  "o": 4,
  "on": "Significant overlap with existing agent communication work (FIPA, IEEE 1516, various RPC/messaging protocols); unclear how ANP differentiates from established agent frameworks and network protocols.",
  "mo": 1,
  "mon": "Appears to be single draft submission with no revision history visible; no evidence of WG discussion, community feedback, or iterative development momentum.",
  "r": 3,
  "rn": "Partially relevant to AI agent systems; focuses on networking infrastructure rather than core AI/ML challenges like model deployment, alignment, or safety; more infrastructure-oriented than AI-focused.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "Proposes URI scheme and discovery mechanisms for exposing MCP servers via standard endpoints and DNS records, enabling AI agents to autonomously discover available services. Includes optional manifest integrity and capability negotiation for security.",
  "n": 2,
  "nn": "Incremental contribution combining existing patterns (well-known URIs, DNS TXT, JWS) applied to MCP server discovery; no fundamentally novel mechanisms, though useful standardization for the MCP ecosystem.",
  "m": 3,
  "mn": "Defined protocol with multiple discovery modes and security considerations specified, but relatively early IETF draft (26 March 2026) lacking implementation evidence, test vectors, or deployment examples.",
  "o": 3,
  "on": "Shares conceptual approach with service discovery (SRV records, well-known URIs per RFC 5785, DNS TXT metadata), and capability negotiation patterns; moderate overlap with existing internet infrastructure standards adapted for MCP context.",
  "mo": 1,
  "mon": "Single draft revision visible; no WG adoption, community discussion, or implementation signals evident; early-stage proposal without clear momentum in IETF process.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure—addresses autonomous discovery and safe connection establishment for agents interfacing external services, core operational requirement for distributed AI systems.",
  "c": ["Agent discovery/reg", "A2A protocols", "Agent identity/auth", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "Proposes Intent Token, a cryptographic primitive for authorizing specific actions by autonomous AI agents at execution time, filling a gap between session-level OAuth 2.0 frameworks and runtime agent action control. The mechanism is model-agnostic and composable with existing authorization infrastructure.",
  "n": 4,
  "nn": "Addresses a genuine gap in authorization frameworks for autonomous agents; the concept of binding cryptographic authorization to specific agent actions at runtime is non-obvious and represents notable originality in agent control primitives.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes the concept and motivation clearly but insufficient detail provided on mechanism, protocol flow, cryptographic binding details, or examples to assess implementation readiness.",
  "o": 2,
  "on": "Minor similarities to capability-based security and delegation tokens (OIDC, PAT frameworks), but the specific focus on runtime action authorization for autonomous agents rather than session/scope-based access is relatively novel.",
  "mo": 1,
  "mon": "Single draft from 2026-03-19 with no evidence of prior versions, working group discussion, or adoption; appears to be initial submission without community momentum.",
  "r": 5,
  "rn": "Directly addresses a critical gap in autonomous agent authorization; highly relevant to AI safety, agent governance, and human oversight of autonomous systems.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "AI safety/alignment",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Draft proposes requirements for AI/ML agents in 6G networks, categorizing agent types and detailing their requirements. Covers implementation approaches including DNS-based discovery mechanisms for inter-domain and intra-domain agent communication.",
  "n": 2,
  "nn": "Incremental extension of AI/ML applications to 6G context; combines existing concepts (agents, DNS discovery, APIs) without substantial methodological innovation.",
  "m": 2,
  "mn": "Early-stage requirements document lacking detailed specifications, implementation examples, or test vectors; DNS discovery approach sketched but not formally specified.",
  "o": 4,
  "on": "Significant overlap with existing work on network AI orchestration (3GPP, IETF autonomic networking); agent discovery via DNS mirrors established patterns; limited differentiation from 5G AI/ML frameworks.",
  "mo": 1,
  "mon": "Single revision (2026-03-16); no evidence of WG adoption, community engagement, or iterative development cycle typical of active IETF work.",
  "r": 3,
  "rn": "Partially relevant to AI agents and network automation but lacks depth on core agent semantics; focuses on 6G infrastructure requirements rather than fundamental agent design or protocols.",
  "c": [
    "Agent discovery/reg",
    "Autonomous netops",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "ATP proposes an SMTP-like asynchronous store-and-forward protocol for transmitting autonomous AI agents across network boundaries with cryptographic identity verification, trust scoring, and capability negotiation. It addresses synchronous RPC limitations in agent communication by enabling offline agent mobility while maintaining end-to-end integrity.",
  "n": 2,
  "nn": "Incremental adaptation of SMTP patterns to agent payloads; core concepts (store-and-forward, relay hops, envelope protection) are well-established in email protocols. Limited architectural novelty beyond domain recontextualization.",
  "m": 3,
  "mn": "Protocol mechanisms are formally specified with clear sections on message format, identity verification, and policy enforcement. Lacks implementation details, test vectors, and reference implementations needed for production deployment.",
  "o": 4,
  "on": "Significant overlap with MCP handshake semantics, FIPA ACL agent mobility concepts, and existing A2A frameworks. Trust scoring and policy enforcement echo OAuth/SASL patterns. Differentiation from existing agent communication standards unclear.",
  "mo": 2,
  "mon": "Single draft revision (2026-03-28). No evidence of WG sponsorship, implementation pilots, or community adoption signals. Reads as early-stage proposal without active ecosystem support.",
  "r": 4,
  "rn": "Directly addresses agent communication infrastructure, a core concern for autonomous systems. Relevant to interoperability and identity problems. Less relevant to safety/alignment, training, or inference optimization.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes a standardized .well-known/ai endpoint for web services to expose machine-readable AI agent capabilities and integration requirements in JSON format. Aims to eliminate the need for LLMs to parse human documentation by providing a structured discovery mechanism optimized for token efficiency.",
  "n": 3,
  "nn": "Useful incremental contribution applying the well-established .well-known pattern to AI agent discovery, but conceptually straightforward with limited novelty beyond domain application.",
  "m": 3,
  "mn": "Defines a structured protocol mechanism with JSON schema, though maturity level suggests specification completeness rather than extensive implementation validation or test vectors.",
  "o": 3,
  "on": "Shares conceptual similarities with OpenAPI/Swagger, IANA .well-known registries, and emerging AI agent protocol frameworks; moderate overlap with existing service discovery patterns.",
  "mo": 2,
  "mon": "Single draft revision dated 2026-03-23 with no evident WG sponsorship or adoption signals; early-stage specification momentum.",
  "r": 5,
  "rn": "Directly addresses a core pain point in AI agent deployment—programmatic service discovery—and is highly relevant to autonomous agent ecosystems and interoperability.",
  "c": ["Agent discovery/reg", "Data formats/interop", "A2A protocols", "Autonomous netops", "Agent identity/auth"]
}
```


```json
{
  "s": "Proposes a network infrastructure architecture for enabling secure collaboration between multiple AI agents at scale, focusing on how network control and forwarding planes can actively support agent coordination. Addresses infrastructure-level requirements for dynamic multi-agent systems rather than agent design itself.",
  "n": 2,
  "nn": "Incremental contribution applying existing network architecture concepts to agent collaboration; lacks novel networking mechanisms or protocols specific to agent coordination.",
  "m": 2,
  "mn": "Early-stage framework document; presents architectural vision and requirements but lacks detailed protocol specifications, formal definitions, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing work on network slicing, service mesh architectures, and intent-based networking; concepts for multi-entity coordination are well-established in distributed systems literature.",
  "mo": 1,
  "mon": "Single submission with no visible community engagement, WG adoption, or subsequent revisions; appears to be exploratory rather than sustained development effort.",
  "r": 3,
  "rn": "Partially relevant to AI agent systems; frames agents as network clients requiring infrastructure support, but lacks specificity about agent-centric challenges like model coordination, inference distribution, or emergent behavior management.",
  "c": [
    "Autonomous netops",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Defines six OAuth 2.0 Token Exchange profiles for cryptographically verifiable actor chains in multi-hop service-to-service and agentic workflows. Extends RFC8693 with standardized delegation-path preservation and validation mechanisms offering tradeoffs between disclosure visibility, cryptographic accountability, and privacy.",
  "n": 3,
  "nn": "Incremental but well-motivated extension of RFC8693 addressing a genuine gap in multi-hop delegation validation. The six-profile taxonomy adds structure but builds directly on existing nested act claims mechanism rather than introducing fundamentally new concepts.",
  "m": 4,
  "mn": "Mature specification with detailed profile definitions and processing rules. 97 pages suggests comprehensive treatment with examples and edge cases. However, without seeing full text, unclear if test vectors and reference implementations exist; likely implementation-ready but possibly needing validation feedback.",
  "o": 2,
  "on": "Minor similarities to related delegation work (UMA, SAML assertions) but appears genuinely focused on the RFC8693 token exchange gap. Actor chains in OAuth context are relatively unexplored; limited overlap with concurrent standards.",
  "m": 2,
  "mon": "Single dated revision (2026-05-01 future date suggests draft stage). No evidence of WG adoption or broad community discussion. Addresses real operational need but early adoption signals unclear; may stall without implementer pull.",
  "r": 4,
  "rn": "Directly relevant to agentic workflows requiring service-to-service delegation and multi-hop authorization. Core infrastructure for agent identity/auth in complex orchestration scenarios. High relevance for production agent systems but not core AI safety/alignment.",
  "c": ["A2A protocols", "Agent identity/auth", "Data formats/interop", "Policy/governance"]
}
```


```json
{
  "s": "AERO/OMNI is a protocol service for IP internetworking over virtual overlay multilink interfaces using IPv6 ND for control messaging. It supports mobility, multicast, multihop operations and route optimization across diverse applications from aviation to space exploration.",
  "n": 2,
  "nn": "Incremental extension of existing IPv6 ND and routing concepts; applies known techniques (neighbor discovery, dynamic caching, path selection) to overlay network context rather than introducing fundamentally new mechanisms.",
  "m": 4,
  "mn": "Detailed 113-page specification with comprehensive protocol definitions for router discovery, neighbor coordination, path selection and mobility management; implementation-ready with clear message structures and operational procedures.",
  "o": 3,
  "on": "Shares core concepts with existing routing optimization (OSPF, BGP), IPv6 ND extensions, and overlay networking schemes; distinct AERO/OMNI contribution but builds incrementally on established patterns.",
  "mo": 2,
  "mon": "Single revision dated 2024-04-04; no evidence of active WG adoption, multiple iterations, or community momentum; appears to be individual contribution without sustained development activity.",
  "r": 1,
  "rn": "Not related to AI agents, autonomous systems agents, or agent protocols; purely traditional IP networking infrastructure despite mention of 'intelligent transportation systems' as use case (refers to domain application, not AI agents).",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft analyzes multicast requirements and technology gaps for AI data centers, focusing on improving point-to-multipoint efficiency during LLM training and inference. It identifies key requirements and gaps between multicast needs and existing capabilities in AIDC environments.",
  "n": 2,
  "nn": "Incremental contribution identifying multicast requirements for a specific domain (AIDCs); applies existing multicast concepts to new use case rather than proposing novel solutions.",
  "m": 2,
  "mn": "Early-stage requirements and gap analysis document; lacks concrete protocol specifications, implementation details, or technical solutions beyond problem identification.",
  "o": 3,
  "on": "Shares conceptual overlap with existing multicast standards (PIM, BIER) and datacenter networking drafts; gap analysis format is common for IETF requirements documents.",
  "mo": 2,
  "mon": "Single revision with niche focus area; limited evidence of broader working group momentum or community adoption beyond initial submission.",
  "r": 3,
  "rn": "Partially relevant to AI systems—addresses networking for LLM training/inference but focuses on traditional routing/multicast rather than AI agent behavior, safety, or intelligence aspects.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Defines HEM, a kernel-level protocol for escalating agentic AI decisions to human principals when agent capabilities or policies require human judgment, with formal session states and decision record structures aligned to EU AI Act requirements.",
  "n": 4,
  "nn": "Kernel-level formalization of escalation as first-class session state is original; most prior work treats human-in-the-loop as application concern rather than OS-enforced contract.",
  "m": 3,
  "mn": "Protocol structure, state machine, and decision types are defined; lacks implementation examples, test vectors, and clarity on kernel integration across heterogeneous systems.",
  "o": 2,
  "on": "Distinct from RBAC/ABAC policy frameworks and existing approval workflow systems by positioning escalation as kernel responsibility; minor conceptual overlap with pause/checkpoint mechanisms in agent control systems.",
  "mo": 1,
  "mon": "Single dated draft with no visible revision history or WG sponsorship; appears to be exploratory individual submission without indicated community adoption or iterative development.",
  "r": 5,
  "rn": "Directly addresses core requirement in emerging AI governance: formally specifying human oversight mechanisms for autonomous agents; highly relevant to regulatory compliance and agent safety.",
  "c": [
    "Human-agent interaction",
    "Policy/governance",
    "AI safety/alignment",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft proposes signaling mechanisms for content creators to communicate AI usage preferences via HTTP headers, updating RFC 9309. It aims to give stakeholders control over how automated systems consume their content.",
  "n": 2,
  "nn": "Incremental extension of existing HTTP metadata mechanisms; straightforward application of preference signaling to AI consumption context.",
  "m": 3,
  "mn": "Defined protocol mechanism with HTTP header approach, but likely lacks comprehensive examples, test vectors, and implementation guidance expected at maturity.",
  "o": 4,
  "on": "Significant overlap with robots.txt, HTTP User-Agent handling, and similar preference signaling schemes; robots.txt already addresses AI crawler control for many use cases.",
  "mo": 2,
  "mon": "Single revision draft from 2025; unclear WG consensus or implementation interest; appears early in standardization pipeline.",
  "r": 4,
  "rn": "Directly relevant to AI agent behavior governance and responsible AI consumption practices; addresses legitimate concerns about content usage by LLMs and automated systems.",
  "c": [
    "Policy/governance",
    "Agent discovery/reg",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "Proposes integrating AI-based Network Management Agents into ACTN architecture to enhance autonomy in optical network operations. Discusses enhanced architecture, new interfaces, and use cases for agent-based autonomous optical network management.",
  "n": 2,
  "nn": "Incremental extension combining existing ACTN framework with generic AI agent concepts; lacks specific technical innovation in agent design or optical network control algorithms.",
  "m": 2,
  "mn": "Early-stage draft presenting conceptual architecture and use cases without detailed protocol specifications, implementation details, or interoperability mechanisms.",
  "o": 4,
  "on": "Significant overlap with existing ACTN work (RFC 8453, related drafts) and generic AI-in-networking proposals; limited differentiation in agent architecture or integration approach.",
  "mo": 2,
  "mon": "Single revision draft with no evidence of WG discussion, adoption, or community momentum; addresses emerging topic but lacks implementation signals.",
  "r": 4,
  "rn": "Directly relevant as it proposes autonomous agent integration into network management, though execution is generic rather than agent-specific.",
  "c": [
    "Autonomous netops",
    "A2A protocols",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "CORIM specifies a CBOR-based format for representing Endorsements and Reference Values in RATS systems, enabling Verifiers to appraise Evidence about remote Attester trustworthiness. Addresses the critical infrastructure challenge of standardizing how manufacturers and device owners communicate integrity metadata to relying parties.",
  "n": 2,
  "nn": "Incremental standardization effort applying CBOR serialization to existing RATS conceptual framework; format design is straightforward encoding of established trust concepts rather than introducing fundamentally new mechanisms.",
  "m": 4,
  "mn": "Well-developed specification with formal CBOR schema, detailed information elements, and clear encoding rules; appears implementation-ready though maturity limited by lack of public reference implementations at draft date.",
  "o": 3,
  "on": "Shares core RATS concepts with multiple existing drafts (RATS architecture, PSA tokens); primary distinction is CBOR format choice and specific manifest structure; moderate conceptual overlap with reference value provider specifications.",
  "mo": 4,
  "mon": "Active WG development with multiple revisions indicating sustained interest; part of coordinated RATS standardization effort with clear adoption path in secure hardware and IoT ecosystems.",
  "r": 2,
  "rn": "Tangentially related to AI/agent systems only through remote attestation mechanisms that could authenticate autonomous agents in trust-critical scenarios; primarily infrastructure/hardware security focused rather than AI-centric.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Extends OAuth 2.0 with agent checksums and workflow-aware token binding to address the 'intent-execution separation problem' where autonomous AI agents may diverge from user authorization intent. Introduces an agent_checksum grant type and PoP mechanisms for multi-agent zero-trust security.",
  "n": 3,
  "nn": "Identifies a legitimate problem space (agent authorization drift) but solution is primarily an incremental layering of existing OAuth/JWT concepts (checksums, PoP, token binding) without fundamentally new cryptographic or protocol primitives.",
  "m": 2,
  "mn": "Early specification stage; lacks implementation details, test vectors, security proofs, and concrete examples of workflow binding. References companion research paper but core technical validation appears external to this draft.",
  "o": 4,
  "on": "Significant overlap with existing work: agent checksums resemble attestation concepts, workflow token binding parallels existing conditional token schemes (CAPs, ABE), and PoP is well-established (RFC 9449). The composition is novel but individual components are not.",
  "mo": 1,
  "mon": "Single draft iteration (2026-01-01 date appears prospective); no evident WG adoption, prior revisions, or community discussion cited. Unclear if this reflects actual draft timeline or placeholder.",
  "r": 4,
  "rn": "Directly addresses critical gap in multi-agent AI systems authorization, highly relevant to emerging deployment scenarios. However, framing as OAuth extension may limit visibility in AI/agent security communities.",
  "c": ["Agent identity/auth", "A2A protocols", "AI safety/alignment", "Policy/governance"]
}
```


```json
{
  "s": "This informational draft conceptually explores the relationship between RATS remote attestation and behavioral evidence recording, arguing they address complementary verification questions: system trustworthiness versus actual system actions. It does not propose protocol modifications, new mechanisms, or cryptographic bindings.",
  "n": 2,
  "nn": "Incremental conceptual contribution that organizes existing ideas (attestation vs. behavioral evidence) but lacks novel technical or architectural insights.",
  "m": 2,
  "mn": "Early-stage conceptual discussion without protocol definitions, mechanisms, concrete examples, or implementation guidance; purely descriptive framework.",
  "o": 3,
  "on": "Shares core concepts with RATS RFC 9334 and existing audit/logging frameworks; discusses complementary approaches but limited novelty in the relationship itself.",
  "mo": 2,
  "mon": "Single revision as informational draft with no clear WG adoption path or community momentum; appears to be exploratory contribution without sustained development.",
  "r": 2,
  "rn": "Tangentially related to AI agents through potential accountability applications, but focused on general systems attestation rather than AI-specific challenges like model behavior verification or agent trustworthiness.",
  "c": ["Agent identity/auth", "Policy/governance"]
}
```


```json
{
  "s": "Proposes requirements and use cases for AI Agent-to-Agent communication networks supporting 6G, identifying networking challenges for multi-agent systems performing collaborative tasks. Discusses potential ACN frameworks and standardization approaches but remains largely conceptual.",
  "n": 2,
  "nn": "Incremental extension of existing multi-agent and 6G networking concepts; applies known agent communication patterns to emerging 6G context without substantial technical innovation.",
  "m": 1,
  "mn": "Problem statement and requirements document only; lacks protocol specifications, detailed mechanisms, reference implementations, or concrete technical solutions for proposed ACN frameworks.",
  "o": 4,
  "on": "Significant overlap with existing 3GPP 6G studies, multi-agent communication literature, and IoT/edge networking requirements; limited differentiation from prior work on agent collaboration.",
  "mo": 2,
  "mon": "Single revision draft dated 2026-01-02 with no indication of WG adoption, community feedback cycles, or development momentum; nascent work without clear standardization track.",
  "r": 4,
  "rn": "Directly relevant to AI agent communication and networking aspects, though focuses heavily on 6G context rather than core agent interaction protocols or mechanisms.",
  "c": ["A2A protocols", "Agent discovery/reg", "Data formats/interop", "ML traffic mgmt", "Policy/governance"]
}
```


```json
{
  "s": "This draft proposes IPv6 as foundational infrastructure for Internet of Agents (IoA), analyzing current capabilities and future requirements as agentic AI systems scale to hundreds of billions. It examines how IPv6's address space, connectivity, and built-in features support agent networks while identifying evolutionary gaps.",
  "n": 2,
  "nn": "Incremental framing of existing IPv6 capabilities applied to a new use case; lacks concrete protocol innovations or technical mechanisms addressing agent-specific challenges.",
  "m": 1,
  "mn": "Early conceptual stage; appears to be a position/requirements paper without defined protocols, mechanisms, or technical specifications for agent-IPv6 integration.",
  "o": 3,
  "on": "Shares general concepts with IoT/6LoWPAN work and standard IPv6 evolution discussions; agent-specific framing is novel but architectural overlap is moderate.",
  "mo": 2,
  "mon": "Single draft submission with no evidence of WG interest, follow-up revisions, or community adoption; positioning suggests exploratory work rather than sustained effort.",
  "r": 3,
  "rn": "Partially relevant to AI agents but primarily focused on network infrastructure rather than agent-specific challenges (identity, autonomy, coordination, alignment); treats agents as generic IoT devices.",
  "c": [
    "Agent discovery/reg",
    "A2A protocols",
    "Agent identity/auth",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Defines the environment.* constraint family for Verifiable Intent mandates, enabling autonomous agents to verify external conditions (venue availability, fund status, etc.) before executing transactions on behalf of humans. Establishes registration mechanics and composition disciplines for environment-based constraints without specifying individual constraint types.",
  "n": 2,
  "nn": "Incremental extension of existing Verifiable Intent framework; applies established constraint family patterns to a new domain (environmental conditions) with predictable methodology.",
  "m": 4,
  "mn": "Well-structured specification with clear membership criteria, composition rules, security considerations, and IANA registry mechanics; includes reference implementations in appendices but lacks deployed test vectors.",
  "o": 3,
  "on": "Shares foundational concepts with policy-based authorization and smart contract preconditions; moderate conceptual overlap with existing conditional execution frameworks.",
  "mo": 1,
  "mon": "Single 2026-05-12 dated draft with no visible revision history; no evidence of WG discussion, adoption, or community engagement; appears nascent or stalled.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent authorization and constrained delegation; addresses practical agent capability governance but requires agents already within VI ecosystem.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Human-agent interaction",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "This draft proposes a structured semantic model and format for expressing Service Intent in autonomic networks, extending beyond connection-centric descriptions to cover network, compute, and storage resources needed for services like AI inference. It specifies identification, scope, versioning, and lifecycle semantics for goal-oriented service objectives across heterogeneous domains.",
  "n": 2,
  "nn": "Incremental extension of existing ANIMA Intent framework; applies intent concepts to service-level rather than connection-level abstractions, which is a natural but limited conceptual shift.",
  "m": 2,
  "mn": "Early-stage draft; abstract describes model and format but 10 pages unlikely to contain detailed protocol specifications, examples, or implementation guidance needed for production readiness.",
  "o": 4,
  "on": "Significant overlap with ANIMA Intent work, service intent literature, and intent-based networking frameworks; distinguishing factors between this and prior SLA/intent models not evident from abstract.",
  "mo": 2,
  "mon": "Single draft iteration with future date (2026-03-02 suggests placeholder); no evident WG adoption, implementation prototypes, or revision history indicating active community engagement.",
  "r": 3,
  "rn": "Partially relevant; addresses resource coordination for AI inference workloads and autonomous management, but framed primarily as network semantics rather than agent-centric AI systems.",
  "c": [
    "Data formats/interop",
    "Autonomous netops",
    "Model serving/inference",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "ADOL proposes token-efficient optimizations for agentic communication protocols through schema deduplication, adaptive field inclusion, and verbosity control. The work addresses real context window constraints in LLM-based agent systems but relies heavily on existing techniques like JSON references.",
  "n": 2,
  "nn": "Incremental optimization layer combining well-known compression techniques (schema dedup, field elision, response filtering). While contextually motivated by agentic systems, individual mechanisms lack novelty.",
  "m": 3,
  "mn": "Protocol-level mechanisms defined with claimed backward compatibility, but abstract describes optimizations without detailed specifications, examples, or validation. Implementation readiness unclear.",
  "o": 4,
  "on": "Significant overlap with existing work: JSON-LD references, content negotiation patterns (Accept headers), selective field inclusion (GraphQL/sparse fieldsets), and schema registries. Primarily repackages established data optimization patterns.",
  "mo": 1,
  "mon": "Single draft dated 2026-01-12 with no revision history visible. No evidence of WG discussion, adoption, or community engagement. Appears newly submitted without prior socialization.",
  "r": 4,
  "rn": "Directly addresses real pain point in emerging agentic systems (context efficiency), though applicability spans broader than just LLM agents. Problem is timely and relevant but somewhat narrow in scope.",
  "c": [
    "Data formats/interop",
    "A2A protocols",
    "ML traffic mgmt",
    "Model serving/inference"
  ]
}
```


```json
{
  "s": "Proposes an architectural model for establishing human identity roots, delegation semantics, and provenance tracking for software agents acting across distributed systems. Aims to enable accountability and interoperability by creating a consistent framework for representing authorization scope and tracing agent actions back to responsible humans.",
  "n": 3,
  "nn": "Addresses a genuine gap in agent accountability frameworks, but builds primarily on established delegation and provenance concepts rather than introducing fundamentally new mechanisms.",
  "m": 2,
  "mn": "Architectural sketch without protocol definition, wire format, or implementation guidance; lacks concrete binding examples or validation mechanisms for practical deployment.",
  "o": 3,
  "on": "Overlaps conceptually with OIDC delegation flows, W3C Verifiable Credentials provenance models, and existing distributed authorization frameworks; positioning relative to these unclear.",
  "mo": 2,
  "mon": "Single draft publication with April 2026 date; no evidence of WG sponsorship, multiple revisions, or community adoption signals; appears early-stage.",
  "r": 4,
  "rn": "Directly addresses critical need for agent identity and accountability in AI/agent ecosystems; highly relevant to emerging autonomous agent deployment challenges.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "Data formats/interop",
    "Human-agent interaction",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "This draft analyzes messaging protocols for agentic AI systems, proposing AGNTCY SLIM as a purpose-built solution combining MLS encryption with gRPC for quantum-safe end-to-end communication. It positions SLIM as superior to AMQP, MQTT, NATS, and Kafka for AI agent deployments requiring post-compromise security and dynamic group coordination.",
  "n": 2,
  "nn": "Applying existing protocols (MLS, gRPC, OAuth) to messaging for AI agents is incremental; the novelty claim rests on combining known components rather than fundamental innovation in protocol design or agent coordination.",
  "m": 2,
  "mn": "Early sketch phase; abstract describes design goals and comparative analysis but provides no detailed protocol specification, message formats, examples, or implementation evidence. Missing authentication flow details and security proofs.",
  "o": 4,
  "on": "Significant overlap with RFC9420 (MLS), RFC7540 (HTTP/2), RFC6749 (OAuth), and gRPC specifications. SLIM appears to be primarily a composition of existing standards rather than a novel protocol; comparative analysis of existing systems is well-trodden ground.",
  "mo": 1,
  "mon": "Single draft revision (2026-02-24), no evidence of WG sponsorship, community discussion, or implementation activity. Appears to be a proposal without established momentum or organizational backing.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent messaging and infrastructure, addressing real deployment scenarios. However, relevance is primarily infrastructural rather than addressing core AI agent capabilities, alignment, or behavior.",
  "c": ["A2A protocols", "Agent identity/auth", "Autonomous netops", "Data formats/interop"]
}
```


```json
{
  "s": "Presents a MANET internetworking framework combining AERO (Automatic Extended Route Optimization) and OMNI (Overlay Multilink Network) technologies to enable autonomous mobile node systems to interoperate with fixed networks like the Internet. Focuses on routing optimization and multilink overlay mechanisms for mobile ad-hoc network integration.",
  "n": 2,
  "nn": "Incremental advancement combining existing AERO/OMNI concepts; applies known technologies to standard MANET internetworking problem rather than introducing fundamentally new approaches",
  "m": 2,
  "mn": "Early-stage framework document with abstract concept presentation; lacks detailed protocol specifications, implementation details, or validation data needed for maturity",
  "o": 4,
  "on": "Significant overlap with established MANET routing literature (RFC 2501 foundation) and prior AERO/OMNI work; limited novel integration beyond combining existing technologies",
  "mo": 1,
  "mon": "No evidence of active development, community engagement, or WG adoption; appears as single recent draft with no revision history or implementation momentum",
  "r": 1,
  "rn": "Not relevant to AI/agent systems; addresses traditional mobile ad-hoc network routing and internetworking, falls outside AI agents, autonomous agents, or agent protocols scope",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes a standardized vocabulary for machine-readable opt-outs covering Text and Data Mining, AI Training, and Generative AI Training use cases, designed to be mechanism-agnostic and enable interoperable expression of digital asset usage restrictions.",
  "n": 2,
  "nn": "Incremental contribution defining vocabulary terms for existing opt-out concepts; lacks novel framework or mechanism design",
  "m": 2,
  "mn": "Early sketch stage with abstract definitions of three use cases but minimal detail on vocabulary structure, encoding, or integration guidance",
  "o": 4,
  "on": "Significant overlap with existing opt-out standards (robots.txt extensions, machine-readable privacy policies, DNT headers) and emerging TDM directives from EU Digital Markets Act",
  "mo": 1,
  "mon": "Single draft revision with no apparent WG sponsorship, mailing list engagement, or implementation uptake signals",
  "r": 4,
  "rn": "Directly relevant to AI governance and data policy concerns, though focused on vocabulary rather than agent behavior or infrastructure",
  "c": ["Policy/governance", "Data formats/interop"]
}
```


```json
{
  "s": "BANDAID proposes using DNS and existing mechanisms (SVCB records, DNS-SD, DNSSEC, DANE) to enable discovery, capability advertisement, and trust signaling between AI agents without modifying DNS protocol itself. The approach defines a structured namespace convention (_agents.example.com) for agents to exchange operational metadata and prove domain authorization via Domain Control Validation.",
  "n": 2,
  "nn": "Incremental repurposing of established DNS-SD and SVCB mechanisms for agent discovery; the core technical contribution is primarily a namespace convention and best practice rather than novel protocol design.",
  "m": 3,
  "mn": "Mechanism is clearly defined with concrete examples (chat._agents.example.com SVCB records) and leverages mature DNS standards, but lacks implementation details, test vectors, and validation of the DCV best practice approach.",
  "o": 4,
  "on": "Significant overlap with DNS-SD service discovery, SVCB record usage patterns, and DANE trust frameworks; the application to agents is novel but the underlying technical approach reuses existing standardized solutions with limited adaptation.",
  "mo": 1,
  "mon": "Single draft revision dated 2025-10-16 with no evidence of WG discussion, multiple iterations, or community adoption; appears to be initial submission without momentum indicators.",
  "r": 4,
  "rn": "Directly addresses agent discovery and registration—a core operational challenge in multi-agent systems—and includes identity/authentication considerations, though positioned more as infrastructure-agnostic rather than AI-specific.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft defines identity management mechanisms for agents in an Internet of Agents (IOA) system, specifying agent registration, identifier assignment, and gateway-based identity functions. It addresses descriptive requirements and basic/extended management capabilities for agent lifecycle operations.",
  "n": 2,
  "nn": "Incremental contribution applying conventional identity management concepts to agent systems; lacks architectural novelty or technical innovation distinguishing it from standard service identity patterns.",
  "m": 2,
  "mn": "Early-stage draft with problem definition but minimal protocol detail; appears to be a requirements document rather than a concrete, implementation-ready specification with examples or test vectors.",
  "o": 4,
  "on": "Significant overlap with existing identity/credential frameworks (SASL, X.509, OAuth 2.0 scopes) and service discovery protocols (mDNS, SRV records); limited acknowledgment of prior work limits differentiation.",
  "mo": 1,
  "mon": "Single revision at 2026 date suggests minimal community engagement or development activity; unclear WG sponsorship or stakeholder commitment.",
  "r": 3,
  "rn": "Partially relevant to agent infrastructure but framed around generic 'agents' without clear connection to AI/ML agent systems; identity management is peripheral to core AI agent concerns (reasoning, learning, safety).",
  "c": ["Agent identity/auth", "Agent discovery/reg", "Data formats/interop"],
  "overall_assessment": "Underdeveloped early draft addressing a practical but narrow problem using conventional approaches; unclear positioning within agent/AI ecosystem and minimal differentiation from existing standards."
}
```


```json
{
  "s": "Proposes architectural principles for integrating agentic AI systems into the IP protocol stack as coordinated first-class entities at multiple layers while preserving deterministic layering for interoperability. Frames AI agents as autonomous decision-makers working within and across network layers to improve behavior through reasoning and feedback loops.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (layered protocols, AI agents, network automation) without substantial technical innovation; the core idea of adding AI to network layers is relatively straightforward application of known agentic AI patterns.",
  "m": 2,
  "mn": "Early-stage position paper identifying research challenges rather than proposing concrete mechanisms; lacks detailed protocols, formal specifications, or implementation guidelines for how agents interact across layers.",
  "o": 4,
  "on": "Significant overlap with existing work in intent-based networking, self-healing networks, and AI-driven network operations; architectural layering concepts mirror established SDN/NFV approaches with AI augmentation as the primary novelty.",
  "mo": 2,
  "mon": "Single revision draft with unclear WG trajectory; appears to be initiating discussion in NMRG (Network Management Research Group) but lacks indicators of sustained community engagement or follow-up activity.",
  "r": 4,
  "rn": "Directly relevant to AI agents in networking contexts; addresses autonomous network operations, agent coordination, and multi-layer reasoning which are core AI agent concerns, though execution details remain nascent.",
  "c": [
    "Autonomous netops",
    "A2A protocols",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes an Agent Directory (AD) service enabling software agents to register capabilities and endpoints for discovery by clients, adapting RFC 9176's CoRE Resource Directory pattern to agent-oriented architectures using HTTP and JSON.",
  "n": 2,
  "nn": "Incremental adaptation of existing IoT directory pattern to agent domain; straightforward extension rather than fundamental innovation",
  "m": 3,
  "mn": "Defined protocol mechanism with clear structure, but as draft dated 2026-05 lacks visible implementation evidence or detailed test vectors",
  "o": 4,
  "on": "Significant overlap with service discovery patterns (mDNS, DNS-SD) and existing directory services; limited differentiation from CoRE Resource Directory beyond use case",
  "mo": 1,
  "mon": "Single revision with no visible community discussion, WG adoption, or implementation interest signals",
  "r": 4,
  "rn": "Directly relevant to agent ecosystems; addresses genuine infrastructure need for agent discoverability in multi-agent systems",
  "c": [
    "Agent discovery/reg",
    "Agent identity/auth",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "TIBET proposes a cryptographically-linked provenance chain protocol for tracking interactions between autonomous agents, humans, and processes across four dimensions (content, references, context, intent). The draft specifies token data model, hash-chaining semantics, and integration with companion protocols, targeting append-only audit trails in agent systems.",
  "n": 3,
  "nn": "Useful contribution combining existing cryptographic primitives (hash-chaining, signatures) with a structured provenance model tailored for agent interactions; novelty is moderate—similar concepts exist in supply chain traceability and blockchain systems, but application to autonomous agent provenance is timely.",
  "m": 3,
  "mn": "Protocol and data model are defined with canonicalization and verification procedures specified, but 31 pages suggests incomplete detail; references to four companion protocols (JIS, UPIP, RVP, AINS) without citing them raises concerns about self-contained specification and implementation readiness.",
  "o": 3,
  "on": "Shares core concepts with W3C PROV, COSE/CBOR signing standards, and distributed ledger provenance systems; the four-dimension model is somewhat novel but builds on established provenance ontologies; transport-agnostic design overlaps with several existing audit trail frameworks.",
  "m": 2,
  "mon": "Single draft revision with future date (2026-03-29 appears speculative); no evidence of WG sponsorship, community review, or multiple implementations; companion protocol references suggest early-stage ecosystem development without demonstrated adoption.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent systems requiring accountability, interaction logging, and intent tracking; highly applicable to AI safety, agent governance, and human-agent interaction audit; less directly relevant to model serving or ML traffic management.",
  "c": ["A2A protocols", "Agent identity/auth", "AI safety/alignment", "Data formats/interop", "Human-agent interaction", "Policy/governance"]
}
```


```json
{
  "s": "This draft applies WIMSE (Workload Identity in Multi-Cloud and Edge) standards to establish independent identities and credential management for AI agents. It addresses the gap in secure identity mechanisms for autonomous AI systems operating across distributed environments.",
  "n": 2,
  "nn": "Incremental application of existing workload identity framework to AI agents; lacks novel credential mechanisms or identity models specific to agentic AI requirements.",
  "m": 2,
  "mn": "Early-stage applicability document with problem framing; no detailed protocol specifications, implementation examples, or concrete mechanisms for AI agent identity binding.",
  "o": 4,
  "on": "Significant conceptual overlap with existing WIMSE specs and general workload identity efforts; limited differentiation from applying standard credential management to ML/agent workloads.",
  "mo": 2,
  "mon": "Single revision draft with unclear WG adoption; WIMSE itself has moderate momentum but AI agent identity work remains nascent in IETF.",
  "r": 4,
  "rn": "Directly addresses credential and identity management for AI agents, a growing concern; strong relevance to autonomous agent deployment scenarios.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "Agent discovery/reg",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes applying the Agent-to-Agent (A2A) Protocol to network management, enabling communication between Controller Agents and Device Agents for autonomous network operation. Explores integration with existing protocols (NETCONF, RESTCONF, gNMI, MCP) and deployment scenarios.",
  "n": 2,
  "nn": "Incremental contribution adapting an existing protocol (A2A) to network management context; core concepts of agent-based autonomic networking and management plane automation are well-established.",
  "m": 2,
  "mn": "Early-stage applicability document lacking detailed protocol specifications, implementation guidance, or concrete technical requirements; reads as conceptual exploration rather than implementable specification.",
  "o": 4,
  "on": "Significant overlap with autonomic networking (ANIMA), existing agent frameworks, and established management protocols; marginal differentiation from prior work on distributed network intelligence.",
  "mo": 1,
  "mon": "Single revision at submission deadline (2026-02-12); no evidence of WG sponsorship, community discussion, or iterative development cycle.",
  "r": 3,
  "rn": "Partially relevant to AI agents in network contexts but focuses narrowly on protocol applicability rather than core agent capabilities (learning, adaptation, reasoning, safety); treats agents primarily as communication endpoints.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Specifies a Pre-Shared Key (PSK) authentication method for EDHOC key exchange, offering computational efficiency with mutual authentication and identity protection. Addresses both external PSKs and session resumption scenarios for resource-constrained IoT and edge systems.",
  "n": 2,
  "nn": "Incremental extension adding PSK mode to existing EDHOC protocol; PSK authentication methods are well-established, though application to EDHOC's specific architecture is useful rather than conceptually novel.",
  "m": 4,
  "mn": "Well-developed specification with detailed protocol flows, key derivation procedures, message formatting, and security analysis; lacks full implementation evidence but provides implementation-ready technical detail.",
  "o": 3,
  "on": "Shares foundational PSK concepts with TLS 1.3 resumption and standard PSK-based protocols; novel mainly in integration with EDHOC's CBOR Object Signing and Encryption framework.",
  "m": 4,
  "mon": "Active LAKE WG engagement with multiple revisions tracking EDHOC evolution; adopted into working group with clear progression toward standardization.",
  "r": 2,
  "rn": "Tangentially related: relevant for agent identity/authentication in constrained environments, but not specifically designed for AI agent systems; applicable only if AI agents operate on IoT/edge infrastructure requiring EDHOC.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "GAR proposes an audit architecture for agentic AI systems, defining five audit types and mechanisms to verify compliance with governance primitives like intent declaration and human escalation. It aims to provide regulatory-verifiable evidence of proper AI agent governance.",
  "n": 2,
  "nn": "Incremental contribution applying established audit/logging concepts to AI agents; combines existing governance ideas (intent declaration, escalation) into audit framework without fundamental methodological innovation.",
  "m": 2,
  "mn": "Early sketch stage; defines audit types and high-level architecture but lacks implementation details, data schemas, serialization formats, cryptographic binding mechanisms, or concrete examples of audit records.",
  "o": 4,
  "on": "Significant overlap with existing audit logging standards (SIEM, compliance frameworks), AI transparency initiatives, and concurrent work on AI governance primitives; the novelty is primarily in application domain rather than technical approach.",
  "mo": 1,
  "mon": "Single submission (2026-05-17) with no visible revision history, no WG adoption signals, and dependencies on other early-stage drafts (IDP, HEM) that lack momentum.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and regulatory compliance needs; addresses genuine concern about auditability but framed narrowly within specific SOOS ecosystem rather than broader agent standards.",
  "c": [
    "Policy/governance",
    "AI safety/alignment",
    "Data formats/interop",
    "Human-agent interaction",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "PAIT proposes a wire protocol for token-level provenance attribution and identity-conditioned inference in LLM systems, binding agent identities to authorization levels and associating output tokens with verifiable training-corpus references. The protocol aims to satisfy regulatory transparency requirements for high-risk AI systems through sub-document-granularity attribution and trust telemetry.",
  "n": 3,
  "nn": "Useful but incremental contribution; token-level provenance tracking and agent identity binding are meaningful for compliance, but the core concepts (digital signatures, audit trails, authorization hierarchies) are well-established. Limited technical novelty in cryptographic or protocol design.",
  "m": 3,
  "mn": "Protocol specification is defined with state machines and multiple record formats (Agent Identity Token, Provenance Manifest Record, Trust Telemetry Signal), but draft lacks implementation details, test vectors, interoperability examples, or reference implementations that would indicate production readiness.",
  "o": 3,
  "on": "Shares conceptual territory with existing work on model cards, dataset documentation (ABOUT ML), and inference logging standards. Overlaps with emerging regulatory reporting frameworks (EU AI Act, Executive Orders) but proposes distinct wire-protocol layer not directly addressed in prior standards.",
  "mo": 2,
  "mon": "Single dated revision (2026-05-16) with no evident WG sponsorship, community discussion, or implementation adoption signals. No clear indication of iterative refinement or working group engagement.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and model serving; addresses regulatory-driven agent transparency and identity management. Less relevant to core agent autonomy/coordination but highly pertinent to compliance and provenance in deployed systems.",
  "c": ["A2A protocols", "Agent identity/auth", "Policy/governance", "Model serving/inference", "Data formats/interop"]
}
```


```json
{
  "s": "Extends EDHOC protocol with post-quantum cryptography using KEM-based authentication mechanisms, enabling quantum-resistant key exchange and signature-free authentication. Addresses the practical need to add PQC support to an existing lightweight protocol while allowing hybrid authentication approaches.",
  "n": 2,
  "nn": "Incremental extension applying existing PQC standards (ML-KEM) to EDHOC; KEM-based authentication is a known technique with limited novelty in this specific application context.",
  "m": 4,
  "mn": "Well-structured 42-page specification with defined protocol mechanisms, parameter choices, and hybrid scenarios; appears ready for implementation though test vectors and reference implementations would improve maturity to level 5.",
  "o": 3,
  "on": "Shares conceptual overlap with existing PQC migration drafts and EDHOC extensions; KEM-based auth builds on known post-quantum authentication patterns; moderate duplication risk with concurrent IETF PQC work.",
  "mo": 2,
  "mon": "Single revision timestamp (2026-03-02) suggests early-stage draft; no visible evidence of WG adoption, multiple revisions, or community discussion; unclear adoption momentum.",
  "r": 2,
  "rn": "Not relevant to AI agents or autonomous systems; focused on cryptographic protocol hardening for general-purpose IoT/constrained devices using EDHOC, orthogonal to agent-specific concerns.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "Extends OAuth 2.0 token revocation with batch operations, cascade propagation, and agent-level semantics for autonomous systems and cross-domain networks. Introduces new endpoints and coordination protocols to address limitations of RFC 7009's single-token approach.",
  "n": 2,
  "nn": "Incremental extension to existing OAuth 2.0 revocation framework; batch revocation and cascade semantics are natural extensions rather than fundamental innovations.",
  "m": 3,
  "mn": "Defines protocol mechanisms and request/response formats but lacks implementation details, test vectors, or deployment guidance; appears specification-ready but not production-hardened.",
  "o": 3,
  "on": "Shares conceptual overlap with existing batch token management approaches and revocation delegation patterns; some cascade semantics may parallel lifecycle management in other frameworks.",
  "mo": 1,
  "mon": "Single revision as of April 2026 with no evidence of WG adoption, implementation feedback, or community interest; appears nascent.",
  "r": 3,
  "rn": "Tangentially relevant to agent authorization and identity management; addresses agent-level token control but focuses on OAuth extension mechanics rather than core AI agent coordination or safety concerns.",
  "c": ["Agent identity/auth", "Policy/governance", "A2A protocols", "Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes a network architecture and BGP/BGPsec extension for trustworthy routing that enables end users to ensure their data traverses only trusted network devices. The mechanism carries trustworthy routing information (TRI) to mitigate data leakage risks in high-security deployments.",
  "n": 2,
  "nn": "Incremental extension combining existing BGP/BGPsec mechanisms with a trust metadata layer; the core concept of trusted path routing is not novel, though application to BGP is somewhat structured.",
  "m": 2,
  "mn": "Early sketch phase with abstract architecture description but lacking protocol details, data formats, validation procedures, or implementation guidance; insufficient specificity for interoperable deployment.",
  "o": 4,
  "on": "Significant overlap with RPKI/BGPsec trust frameworks, path validation mechanisms in SCION, and existing secure routing proposals; the TRI concept resembles established secure BGP extensions.",
  "mo": 1,
  "mon": "Single revision dated 2025-08-29 with no evident community engagement, working group sponsorship, or adoption signals; appears to be nascent submission without demonstrated momentum.",
  "r": 1,
  "rn": "Not relevant to AI/agent systems; focuses on network routing infrastructure and BGP protocol mechanics with no connection to autonomous agents, AI safety, or agent-related topics.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "SVTP proposes a DID-based trust framework for autonomous machines and AI agents, enabling verifiable identity and M2M interaction with compliance automation. The protocol introduces a 'Protocol Seal' mechanism and aims to address liability and governance in machine-to-machine economies.",
  "n": 2,
  "nn": "Incremental combination of existing DID standards (W3C), cryptographic attestation patterns, and NIST compliance mapping. Core novelty is limited; primarily repackages established identity and trust mechanisms for autonomous systems context.",
  "m": 2,
  "mn": "Early sketch phase. Abstract describes vision but 5-page draft likely lacks detailed protocol specification, message formats, state machines, or security proofs. No evident test vectors or reference implementations mentioned.",
  "o": 4,
  "on": "Significant overlap with W3C DID Core, IETF RATS attestation work, existing blockchain-based identity schemes, and NIST 800-218 compliance frameworks. The 'Protocol Seal' appears to be a credential wrapper without clear differentiation from existing VC/VP patterns.",
  "m": 1,
  "mon": "No observable momentum. Single draft, future publication date (2026-05-04 suggests speculative/undated), no WG affiliation evident, no reference implementations, community discussion, or adoption signals detected.",
  "r": 4,
  "rn": "Directly relevant to agent identity, authentication, and governance. Addresses M2M trust and autonomous systems—core AI agent operational concerns. However, framing lacks depth on actual agent-specific problems versus general IoT/device identity.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Defines ATXN, a cryptographic primitive for recording value exchanges between software agents with legal enforceability under existing contract law. Establishes conformance tiers, payment rail profiles, and a two-tier validity model for escrow, dispute resolution, and liability allocation in agentic commerce.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (signed transaction bundles, contract law mapping, payment profiles) without fundamental innovation in transaction semantics or cryptographic primitives.",
  "m": 2,
  "mn": "Early sketch with abstract protocol structure but lacks detailed specifications, implementation examples, test vectors, and formal schema definitions needed for interoperability testing.",
  "o": 4,
  "on": "Significant conceptual overlap with existing payment standards (Stripe ACP, Visa TAP, Mastercard Agent Pay, x402) and agent frameworks; positions as unifying abstraction but dependency chain (AIVS, VCAP, ATEP, ADRP) suggests incomplete scope in single draft.",
  "mo": 1,
  "mon": "First revision (01) with no evidence of WG adoption, community feedback integration, or implementation pilots; co-submission of multiple dependent companion drafts suggests work-in-progress fragmentation rather than mature standardization effort.",
  "r": 4,
  "rn": "Directly relevant to agent transaction infrastructure and identity/authorization, but frames problem through commerce/contract lens rather than core AI agent capability or safety concerns; relevance depends on whether IETF should standardize financial rails.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft standardizes the use of DRIP Entity Tags (DETs) as identifiers for unmanned aircraft systems to enable trustworthy air domain awareness across RID, UTM, and AAM systems. DETs function as session IDs, authentication key IDs, and encryption key IDs to support privacy, accountability, and confidentiality in airspace management.",
  "n": 2,
  "nn": "Incremental contribution that applies existing DRIP framework to a specific ADA use case; the core concept of using entity tags for identification and key management is established, with this draft focusing on standardization of registration and usage patterns rather than novel identification mechanisms.",
  "m": 3,
  "mn": "Defines protocol mechanisms and usage patterns with reasonable specification detail, though the 16-page length suggests it may lack comprehensive examples, test vectors, or implementation guidance needed for full maturity.",
  "o": 3,
  "on": "Shares identity and key management concepts with existing RID/UTM frameworks and overlaps with DRIP specifications; the novelty lies in the specific application context rather than fundamental technical approach.",
  "mo": 2,
  "mon": "Single revision dated 2025-07-07 with no evidence of iterative development or broader working group adoption; appears to be early-stage document with limited community engagement signals.",
  "r": 2,
  "rn": "Tangentially related to AI agent topics through distributed identity and authentication mechanisms, but primarily concerned with aviation domain-specific airspace management rather than AI systems, autonomous agents, or agent coordination protocols.",
  "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance", "Other AI/agent"]
}
```


```json
{
  "s": "Proposes network architecture and protocols for interconnected AI agents across cloud-edge-end infrastructure, addressing communication, coordination, and distributed inference challenges in multi-agent scenarios.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (edge computing, distributed inference, agent communication) without clearly novel technical mechanisms or protocols.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes problems and motivations but lacks concrete protocol specifications, message formats, or architectural details needed for implementation.",
  "o": 4,
  "on": "Significant overlap with existing work on edge computing frameworks, distributed ML inference, IoT coordination protocols, and agent communication standards; positioning relative to prior work unclear.",
  "mo": 1,
  "mon": "Draft metadata indicates single submission with no revision history visible; no evidence of WG engagement, community feedback integration, or active development cycle.",
  "r": 3,
  "rn": "Partially relevant to AI agent networking; focuses on infrastructure layer rather than core agent behavior, autonomy, or decision-making aspects; more network-centric than agent-centric.",
  "c": [
    "A2A protocols",
    "Model serving/inference",
    "Agent discovery/reg",
    "Autonomous netops",
    "ML traffic mgmt"
  ]
}
```


```json
{
  "s": "Defines DRIP authentication message formats and protocols for verifying broadcast Remote ID messages in unmanned aircraft systems, enabling trustworthiness assessment without Internet access. Specifies cryptographic mechanisms for authenticating DRIP Entity Tags and associated UAS communications.",
  "n": 2,
  "nn": "Incremental application of existing authentication patterns (signatures, certificates) to UAS RID domain; limited novel cryptographic or protocol design",
  "m": 4,
  "mn": "Detailed protocol specification with message formats, authentication procedures, and trust policies; well-structured but implementation examples limited",
  "o": 3,
  "on": "Shares core concepts with standard PKI/certificate-based auth schemes; builds on existing RID standards (ADS-B, etc.) with modest differentiation",
  "mo": 4,
  "mon": "Active IETF working group (DRIP) with multiple coordinated drafts; clear standardization pathway and regulatory interest from aviation authorities",
  "r": 1,
  "rn": "Not relevant to AI agents, autonomous systems, or agent protocols; focused on UAS identification/authentication infrastructure for human observers",
  "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance", "Other AI/agent"]
}
```