```json
{
  "s": "Proposes a federated registry architecture for issuing persistent, hardware-anchored identities to autonomous entities (AI agents, robots) using a three-tier governance model modeled on DNS, with identity expressed as URNs and anchored to TPMs/secure enclaves to provide Sybil resistance.",
  "n": 3,
  "nn": "Applies established DNS/PKI patterns to a new domain (autonomous entities) with hardware attestation anchoring; the core concepts are not novel but the specific application to agent identity is timely and useful.",
  "m": 3,
  "mn": "Defines protocol architecture and integration points (OIDC/OAuth2 tokens, URN namespace) but lacks implementation details, test vectors, and concrete attestation verification procedures; appears early-to-mid stage specification.",
  "o": 3,
  "on": "Shares significant concepts with W3C DID/verifiable credentials work, TPM-based attestation (TCG), and OIDC/OAuth2 standards; overlaps with existing agent authentication proposals but frames around hardware anchoring.",
  "mo": 2,
  "mon": "Single draft revision (2026-04-29 date suggests recent submission); no evidence of WG adoption, prior discussion, or multiple iterations; appears to be initial proposal stage.",
  "r": 5,
  "rn": "Directly addresses core authentication and identity challenges for autonomous AI agents; Sybil resistance and hardware-anchored trust are critical for agent ecosystems; high relevance to agent interoperability and security.",
  "c": ["Agent identity/auth", "Agent discovery/reg", "Policy/governance", "A2A protocols", "Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes an extension to RFC 7030 (EST) that allows servers to signal recommended certificate renewal timing to clients, addressing the problem that traditional 50% lifetime renewal triggers are increasingly inappropriate for short-lived certificates.",
  "n": 2,
  "nn": "Incremental extension adding a timing recommendation field to existing EST protocol; solves a real operational problem but limited technical novelty.",
  "m": 3,
  "mn": "Provides defined protocol mechanism with clear problem statement and solution approach, though lacks implementation details, test vectors, and detailed encoding specifications typical of mature specs.",
  "o": 2,
  "on": "Minor overlap with existing certificate lifecycle management practices; builds directly on RFC 7030 without significant conceptual similarities to other IETF work.",
  "mo": 2,
  "mon": "Single revision with modest draft activity; appears to address practical EST deployment needs but shows limited evidence of working group engagement or community momentum.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; focused on traditional PKI certificate management and enrollment protocols with no AI/ML components.",
  "c": ["Agent identity/auth"]
}
```


```json
{
  "s": "This draft proposes that DNS resolvers should query and cache NS records directly from child zones rather than relying on parent-side delegations, with periodic revalidation to ensure delegation freshness. The approach aims to improve resolver robustness by preferring authoritative NS information and properly managing glue record trustworthiness.",
  "n": 2,
  "nn": "Incremental improvement to DNS resolution practices; requerying child NS RRsets is a logical refinement but not architecturally novel.",
  "m": 4,
  "mn": "Well-defined protocol mechanism with clear algorithm description, TTL management rules, and caching strategies; lacks implementation guidance and test vectors for full readiness.",
  "o": 2,
  "on": "Minor similarities to existing NS handling practices (RFC 1034); mostly codifies and formalizes recommended behavior rather than duplicating prior work.",
  "mo": 3,
  "mon": "Active WG development with recent revision date (2026-01); appears in DNSOP working group with meaningful engagement but not yet strong community consensus.",
  "r": 1,
  "rn": "Not relevant to AI agents, autonomous systems, or AI-related networking; pure DNS operational protocol improvement for resolver behavior.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "RVP proposes a unified protocol for coordinating physical entities (robots, IoT, manufacturing systems) with digital agents (AI systems, virtual twins) using composite identity management and relation graphs. The protocol aims to address gaps in existing peer-to-peer agent protocols by incorporating physical constraints and hierarchical coordination for embodied intelligence networks.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (agent coordination, digital twins, identity management) without clearly differentiated technical innovation beyond framing",
  "m": 1,
  "mn": "Problem statement document lacking protocol specification, formal definitions, message formats, or implementation details; purely aspirational scope without technical substance",
  "o": 4,
  "on": "Significant overlap with MCP (Model Context Protocol), ANP (Agent Network Protocol), digital twin standards (ISO), and IoT/manufacturing protocols; positioning against these is unclear and under-differentiated",
  "mo": 1,
  "mon": "Single draft submission with no visible community engagement, WG discussion, or iterative development; unclear author affiliation or stakeholder backing",
  "r": 3,
  "rn": "Partially relevant to agent communication and embodied AI, but framed as infrastructure protocol rather than core agent capability; manufacturing/IoT focus dilutes AI agent relevance",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft identifies authentication and authorization gaps in existing frameworks when applied to autonomous AI agents, arguing that dynamic behavior management is needed rather than static identity verification. It articulates why traditional human-centric security models fail for agent-to-agent interactions and delegation chains.",
  "n": 4,
  "nn": "Reframing auth/authz around dynamic behavior rather than static identity is a genuinely novel perspective for IETF, though the core problem is emerging industry-wide.",
  "m": 1,
  "mn": "Pure requirements document with no protocol proposal, mechanism design, or concrete technical solutions; reads as problem articulation only.",
  "o": 2,
  "on": "Overlaps conceptually with OAuth2/OIDC delegation and emerging work on service-to-service auth, but applies unique lens of agent autonomy; minor similarity to existing identity frameworks.",
  "mo": 2,
  "mon": "New draft (Jan 2026) with single revision; no visible WG adoption or community adoption signals yet; preliminary stage.",
  "r": 5,
  "rn": "Directly addresses core AI agent operational challenge; authentication and authorization are foundational for safe agent deployment; highly timely and relevant to IETF scope.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "Autonomous netops",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "HAP proposes an HTTP profile for authenticated agent traffic using cryptographic signatures, privacy-preserving human tokens, and protocol-level micropayments via HTTP 402. It aims to address economic misalignment between AI agents and content providers while enabling incremental deployment.",
  "n": 3,
  "nn": "Combines existing HTTP mechanisms (Message Signatures, 402 status) in a new application context for agent traffic; framing is novel but individual components are established.",
  "m": 2,
  "mn": "Early-stage draft with conceptual design; lacks implementation details, test vectors, interoperability examples, and clarity on micropayment mechanism integration.",
  "o": 3,
  "on": "Related work exists on bot authentication (RFC 8555, HTTP Message Signatures), value exchange (402 status), and agent identification; positions as integrative rather than pioneering.",
  "mo": 2,
  "mon": "Single revision (2025-11), no apparent WG adoption or community discussion signals; addresses timely problem but lacks collaborative momentum.",
  "r": 5,
  "rn": "Directly addresses autonomous agent authentication, traffic differentiation, and economic incentive alignment—core concerns for AI agent integration into web infrastructure.",
  "c": ["Agent identity/auth", "A2A protocols", "ML traffic mgmt", "Policy/governance", "Human-agent interaction"]
}
```


```json
{
  "s": "Proposes OAuth 2.0 extensions enabling coordinated authorization for multi-agent AI systems where a lead agent delegates tasks to sub-agents. Simplifies the auth flow by reducing repeated server interactions while maintaining backward compatibility with standard OAuth 2.0.",
  "n": 2,
  "nn": "Incremental extension applying existing OAuth patterns to multi-agent scenarios; lacks architectural innovation beyond token/message field additions.",
  "m": 2,
  "mn": "Early sketch with abstract concepts; 13 pages insufficient for detailed protocol specification, missing flow diagrams, token format definitions, example exchanges, or security analysis.",
  "o": 4,
  "on": "Significant overlap with delegation/impersonation patterns in OAuth 2.0 (token exchange grant RFC 8693), UMA 2.0 resource authorization, and emerging agent-to-agent auth work; positioning versus existing standards unclear.",
  "mo": 1,
  "mon": "Single undated revision (2026-03-02 appears future-dated); no evidence of WG discussion, community feedback, or iterative development; appears exploratory rather than actively pursued.",
  "r": 4,
  "rn": "Directly addresses agent authorization challenges, but frames narrowly around OAuth extension rather than broader agent identity/trust architecture; relevant to emerging agent coordination patterns.",
  "c": ["Agent identity/auth", "A2A protocols", "Policy/governance"]
}
```


```json
{
  "s": "This draft documents AI Agent use cases and operational requirements for 6G networks, drawing primarily from 3GPP's existing TR 22.870 study. It presents operator perspectives on integrating AI agents into 6G infrastructure without introducing novel technical mechanisms.",
  "n": 2,
  "nn": "Incremental compilation of existing 3GPP work; references established standards rather than proposing new approaches to AI agent integration.",
  "m": 2,
  "mn": "Early-stage requirements document without protocol specifications, detailed mechanisms, or implementation guidance; serves as a use case compilation.",
  "o": 4,
  "on": "Significant overlap with 3GPP TR 22.870 source material; limited independent analysis or original requirements derivation beyond operator perspective framing.",
  "mo": 1,
  "mon": "Single revision with no evidence of active development cycle, WG discussion, or community engagement; appears to be initial submission without follow-up.",
  "r": 4,
  "rn": "Directly relevant to AI agents in networks; focuses on 6G-specific use cases and operational requirements despite lack of technical novelty.",
  "c": [
    "Autonomous netops",
    "Policy/governance",
    "Agent discovery/reg",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "ARP v2.0 proposes a machine-readable protocol for entities to publish self-attested context, corrections, and boundaries directly to autonomous AI agents and RAG systems, extending v1.x with REST APIs, cryptographic attestation, DIDs, and event-driven freshness. The protocol aims to influence AI agent reasoning behavior beyond traditional web conventions like robots.txt.",
  "n": 2,
  "nn": "Incremental extension of existing v1.x model; combines established technologies (REST, DIDs, SSE, cryptographic signatures) without fundamental innovation in agent control or reasoning protocol design.",
  "m": 3,
  "mn": "Defined protocol with stated mechanisms (REST API, bidirectional feedback, A2A handshakes, SSE), but 29 pages without visible test vectors, reference implementations, or security analysis suggests specification-stage maturity rather than implementation-ready.",
  "o": 4,
  "on": "Significant overlap with robots.txt (agent directives), schema.org (metadata), llms.txt (LLM-specific guidance), and W3C DID specifications; positioning as complementary rather than novel suggests incremental refinement of existing approaches.",
  "mo": 1,
  "mon": "Draft dated 2026-04-28 with no visible adoption signals, WG discussions, or reference implementations; appears to be single-author proposal without demonstrated community traction or ongoing revision cycle.",
  "r": 4,
  "rn": "Directly addresses AI agent control and instruction distribution—a core concern for autonomous systems—though framed more as governance/policy tool than core agent protocol, limiting foundational relevance.",
  "c": [
    "Policy/governance",
    "Agent identity/auth",
    "Data formats/interop",
    "AI safety/alignment",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes a framework for distributed lossless interconnection between multiple data centers to support large-scale distributed AI model training. Addresses networking challenges for connecting data centers into larger compute clusters with focus on efficient, reliable data transmission.",
  "n": 2,
  "nn": "Incremental contribution combining existing data center networking concepts with AI training requirements; lacks novel technical mechanisms or approaches.",
  "m": 2,
  "mn": "Early stage framework document without detailed protocol specifications, implementation details, or comprehensive technical solutions; appears to be preliminary conceptual work.",
  "o": 4,
  "on": "Significant overlap with existing DCQCN, RDMA, and multi-datacenter networking standards; framework repackages established concepts without clear differentiation from RFC 9347 and related work.",
  "mo": 1,
  "mon": "Single revision as of April 2025; no evidence of WG adoption, community engagement, or iterative development; appears dormant since publication.",
  "r": 3,
  "rn": "Partially relevant to AI infrastructure but focuses on networking layer rather than AI/agent-specific concerns; addresses supporting systems rather than core AI agent capabilities or governance.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Formalizes the SSH agent protocol, which manages cryptographic keys for SSH authentication. Documents existing operational practice for key agent communication in SSH contexts.",
  "n": 1,
  "nn": "Describes established SSH agent protocol behavior; no novel cryptographic or architectural contributions, primarily codification of existing implementations.",
  "m": 4,
  "mn": "Well-defined protocol specification with message formats and procedures; includes implementation details though test vectors may be limited.",
  "o": 5,
  "on": "SSH agent protocol is long-established (OpenSSH, PuTTY, etc.); this draft formalizes documented behavior rather than introducing new concepts.",
  "mo": 2,
  "mon": "Single revision observed; appears to be standardization effort but limited evidence of active WG-level momentum or multiple iterations.",
  "r": 1,
  "rn": "SSH agent is a key management protocol, not related to AI agents, autonomous systems, or agent-based AI architectures; entirely false positive for AI/agent rating.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "ECAP proposes a cryptographically-signed protocol to replace robots.txt, enabling web hosts to establish verifiable consent agreements with automated crawlers and AI scrapers. The protocol uses declarative policy handshakes to enforce ethical access controls rather than relying on voluntary compliance.",
  "n": 2,
  "nn": "Incremental advancement combining existing concepts (cryptographic signatures, policy declarations, consent mechanisms) applied to crawler management; robots.txt alternatives have been explored multiple times.",
  "m": 2,
  "mn": "Early sketch with abstract describing goals but minimal protocol detail; no specification of handshake format, signature schemes, policy grammar, or implementation considerations evident in 3-page document.",
  "o": 4,
  "on": "Significant overlap with prior work: robots.txt extensions, HTTP policy frameworks (CORS, CSP), consent protocols, and previous crawler authentication proposals; limited differentiation articulated.",
  "mo": 1,
  "mon": "Single revision (2025-12-10); no evidence of WG sponsorship, community discussion, or iterative development; appears nascent with minimal adoption signals.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and ethical constraints on automated data collection; addresses timely concern of web scraping for LLM training but positioned as general crawler protocol.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes execution outcome attestation as a distinct concept from identity verification, enabling independent verification of claimed actions and outcomes by AI agents through composable primitives like execution receipts mapped to SCITT logs and TEE mechanisms.",
  "n": 4,
  "nn": "Separating execution verification from identity attestation is a notable conceptual contribution; formalizing execution receipts as primitives is original, though building on established attestation frameworks.",
  "m": 2,
  "mn": "Early sketch stage with abstract model and multiple mapping approaches identified, but lacks detailed protocol specifications, concrete syntax definitions, or implementation examples.",
  "o": 3,
  "on": "Shares core concepts with SCITT (transparency logs), TEE attestation, and append-only log frameworks; execution verification itself is somewhat novel but overlaps with existing audit and provenance work.",
  "mo": 1,
  "mon": "Single draft revision dated 2026-04-04 with no apparent WG adoption or community discussion; appears to be new contribution without evident momentum.",
  "r": 4,
  "rn": "Directly relevant to AI agent trustworthiness and autonomous system verification; addresses real gap in agent accountability but framed for general distributed systems.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Defines six OAuth 2.0 Token Exchange profiles for preserving and validating delegation chains across multi-hop service-to-service and agentic workflows. Addresses cryptographic accountability and auditability tradeoffs for actor-chain continuity in successive token exchanges.",
  "n": 3,
  "nn": "Incremental profiling of RFC 8693 with structured delegation chain handling; the core concept (nested act claims) exists, but systematic treatment of multi-hop validation scenarios adds useful structure.",
  "m": 4,
  "mn": "Well-specified protocol with six distinct profiles, processing rules, and clear delineation of tradeoffs; 97 pages suggests comprehensive treatment including examples, though implementation maturity unclear.",
  "o": 2,
  "on": "Minor overlap with existing OAuth/OIDC delegation work; distinct from SPIFFE/SPIRE approaches and other service identity schemes through its focus on token exchange profiling.",
  "mo": 2,
  "mon": "Single draft revision (2026-04-25), no visible WG adoption signals or follow-up iterations; unclear if this is initial submission or stalled effort.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent systems requiring provable delegation chains and cross-domain service-to-service auth; core infrastructure for agentic workflows with accountability.",
  "c": ["A2A protocols", "Agent identity/auth", "Data formats/interop", "Policy/governance"]
}
```


```json
{
  "s": "Proposes a multi-agent communication framework for network AIOps with an AI gateway, agent naming service, and security features. Addresses coordination of heterogeneous agents for intelligent network operations and maintenance.",
  "n": 2,
  "nn": "Incremental application of existing multi-agent communication patterns to network operations; lacks novel architectural insights or technical innovations beyond conventional gateway/registry designs.",
  "m": 2,
  "mn": "Early-stage draft with abstract framework description but insufficient protocol specifications, message formats, API definitions, or implementation details; appears conceptual rather than specification-ready.",
  "o": 4,
  "on": "Significant overlap with existing SNMP/NETCONF agent frameworks, service mesh communication patterns (Istio, Consul), and conventional API gateway architectures; limited differentiation for AI-specific needs.",
  "mo": 1,
  "mon": "Single revision at 13 pages suggests minimal active development; no evidence of WG adoption, implementation prototypes, or community engagement; appears dormant.",
  "r": 3,
  "rn": "Partially relevant to AI agents and network automation but frames problem generically; missing specificity on how AI/LLM agent requirements differ from traditional distributed systems or why existing frameworks inadequate.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Extends OAuth 2.0 with requested_actor and actor_token parameters to enable AI agents to obtain access tokens while acting on behalf of users with explicit consent. Introduces dynamic authorization via resource server challenges and maintains delegation chain documentation in access token claims.",
  "n": 2,
  "nn": "Incremental extension applying existing OAuth delegation patterns (similar to device flow, on-behalf-of flows) to AI agents; limited conceptual novelty beyond parameter addition.",
  "m": 3,
  "mn": "Defines protocol mechanism with clear parameters and flow descriptions, but lacks implementation details, test vectors, security analysis depth, and formal examples.",
  "o": 4,
  "on": "Significant conceptual overlap with RFC 8693 (token exchange), Microsoft on-behalf-of flow, and JWT bearer token specs; differentiation for AI agents is primarily semantic.",
  "mo": 1,
  "mon": "Single revision, dated 2026-02-27, no evidence of WG adoption, community discussion, or iterative development; early-stage draft status.",
  "r": 4,
  "rn": "Directly addresses AI agent authorization and delegation concerns; core relevance to agent identity/auth and human-agent interaction, though framing as 'AI agent' extension of standard OAuth may obscure that pattern applies broadly.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes using RPKI (Resource Public Key Infrastructure) to attest identities of parties in OpenID Connect exchanges for the Peering API, binding authentication to ASN-based agents. Addresses authentication gaps in GROW WG's Peering API discussions.",
  "n": 2,
  "nn": "Incremental combination of existing technologies (RPKI + OIDC); straightforward application of established standards to a specific use case without fundamental innovation.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes intent but document is only 7 pages with incomplete discussion section marked for removal; lacks protocol details, examples, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing RPKI-based authentication work and standard OIDC identity binding mechanisms; the combination is relatively obvious given established practices in BGP security and federated identity.",
  "mo": 1,
  "mon": "Single draft revision with no visible community engagement; source repository reference is malformed (github.molgen.mpg.de appears non-standard); no evidence of WG discussion or iterative development.",
  "r": 2,
  "rn": "Tangentially related to agent identity/authentication in network contexts, but focused on inter-AS peering operations rather than AI agents; not about autonomous agents or AI systems.",
  "c": ["Agent identity/auth", "Policy/governance", "Data formats/interop"]
}
```


```json
{
  "s": "Defines a simple format for content creators to signal preferences about automated content consumption, with conveyance via HTTP headers and updates to RFC 9309. Addresses machine-readable preference signaling for AI systems and automated processors accessing web content.",
  "n": 2,
  "nn": "Incremental extension of existing preference signaling concepts (like robots.txt, user-agent directives); applies established patterns to AI/automation context without fundamentally novel mechanism.",
  "m": 3,
  "mn": "Protocol mechanism is defined with HTTP header field specification and RFC 9309 integration, but lacks implementation examples, test vectors, and deployment guidance needed for full maturity.",
  "o": 4,
  "on": "Significant conceptual overlap with robots.txt, machine-readable metadata standards (dublin core, schema.org), and other preference signaling RFCs; similar space to web crawling directives but for AI systems.",
  "mo": 2,
  "mon": "Limited to single draft revision (2025-08-20); no visible WG adoption signals, community discussion, or iterative development cycle indicators.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and content creator control over automated systems; addresses legitimate concern about AI training data usage and content scraping preferences.",
  "c": [
    "Policy/governance",
    "Data formats/interop",
    "A2A protocols",
    "AI safety/alignment",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes a JSON-based Signature Agent Card format for web bot authentication, enabling clients to advertise identity, cryptographic keys, and metadata through a directory service with an extensible IANA registry.",
  "n": 2,
  "nn": "Incremental contribution combining existing directory/registry patterns with bot authentication; limited architectural novelty.",
  "m": 3,
  "mn": "Defined protocol mechanism with JSON schema, but lacks implementation examples, test vectors, and integration guidance.",
  "o": 4,
  "on": "Significant overlap with OAuth 2.0 metadata, OpenID Connect discovery, and existing bot authentication frameworks; unclear differentiation.",
  "mo": 1,
  "mon": "Single revision dated 2026 with no apparent WG adoption or community engagement; appears dormant or early-stage.",
  "r": 4,
  "rn": "Directly relevant to agent identity and authentication, a core concern for autonomous systems; practical applicability to agent ecosystems.",
  "c": [
    "Agent identity/auth",
    "Agent discovery/reg",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes a JSON schema for automated HTTP clients (crawlers, bots, AI agents) to publicly disclose their IP address ranges, enabling website operators to identify and verify legitimate traffic while reducing false blocks.",
  "n": 2,
  "nn": "Incremental formalization of existing ad-hoc practices; similar to robots.txt or .well-known patterns but applied to IP range disclosure rather than access rules.",
  "m": 3,
  "mn": "Well-defined JSON schema with clear structure, but limited implementation guidance, test vectors, or deployment examples; lacks details on validation, error handling, and client discovery mechanisms.",
  "o": 3,
  "on": "Shares conceptual overlap with reverse DNS lookups, AS number registries, and informal IP range documentation; relates to Agent.json and similar metadata discovery specs.",
  "mo": 2,
  "mon": "Single revision as of September 2025; no visible WG sponsorship or implementation uptake; unclear if addressing real operational pain points at scale.",
  "r": 4,
  "rn": "Directly relevant to AI agent identification and trust infrastructure; addresses practical needs for legitimate bot traffic verification in web environments.",
  "c": ["Agent identity/auth", "Data formats/interop", "Agent discovery/reg", "ML traffic mgmt", "Policy/governance"]
}
```


```json
{
  "s": "Proposes a flow-level load balancing mechanism for CATS that distributes traffic autonomously in the data plane, reducing control plane overhead. Aims to improve resource utilization by steering computing-aware traffic more efficiently across available resources.",
  "n": 2,
  "nn": "Incremental contribution applying existing load balancing patterns to CATS domain; the core concept of data plane autonomous distribution is well-established, though its application to computing-aware steering is somewhat novel.",
  "m": 3,
  "mn": "Defines mechanism with reasonable detail but appears to lack comprehensive protocol specification, implementation guidance, or empirical validation data typical of mature specifications.",
  "o": 3,
  "on": "Shares fundamental concepts with existing CATS work and general load balancing literature; builds on established traffic steering patterns but with computing awareness focus.",
  "mo": 2,
  "mon": "Single revision as of Feb 2026; appears to have limited WG discussion or adoption signals; typical IETF draft status without evidence of sustained development momentum.",
  "r": 3,
  "rn": "Partially relevant to autonomous networking and data plane intelligence, but not directly focused on AI agents; relevant to autonomous network operations rather than agent-specific concerns.",
  "c": ["Autonomous netops", "ML traffic mgmt", "Data formats/interop"]
}
```


```json
{
  "s": "Defines standardized benchmarking methodologies for evaluating LLM inference serving systems across latency, throughput, scheduling, and resource management. Provides test procedures, setup parameters, and reporting formats as a companion to LLM serving terminology documentation.",
  "n": 2,
  "nn": "Incremental contribution adapting existing benchmarking frameworks to LLM-specific metrics; lacks novel measurement approaches or theoretical advances.",
  "m": 4,
  "mn": "Well-structured specification with defined procedures, parameters, and reporting formats; appears implementation-ready though likely needs vendor feedback and real-world validation.",
  "o": 4,
  "on": "Significant overlap with existing ML benchmarking work (MLPerf, SPEC), cloud performance benchmarking, and LLM evaluation frameworks; limited differentiation from prior art.",
  "mo": 2,
  "mon": "Single draft revision identified; limited evidence of broad WG adoption or community momentum; appears to be early-stage submission.",
  "r": 4,
  "rn": "Directly relevant to AI/agent infrastructure; model serving and inference benchmarking are foundational for evaluating agent deployment systems.",
  "c": ["Model serving/inference", "ML traffic mgmt", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes using agentic AI to optimize distributed sensing and communication tasks in ISAC networks by dynamically selecting sensing entities, processing locations, and network configurations under time-varying conditions. Addresses the coupled decision space arising from heterogeneous sensors, processing requirements, and synchronization constraints through closed-loop agent-based control.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (ISAC, distributed sensing, AI optimization) without proposing novel agent architectures, algorithms, or mechanisms; largely motivational rather than technical advancement.",
  "m": 1,
  "mn": "Early-stage position paper (14 pages) presenting problem motivation and high-level architectural considerations; lacks protocol specifications, decision algorithms, synchronization mechanisms, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing work on ISAC optimization, federated sensing, network slicing, and ML-driven resource allocation; agent framing is applied to established optimization problems without clear differentiation.",
  "mo": 1,
  "mon": "Single initial draft with no revision history evident; no indication of WG adoption, implementation efforts, or community validation; novel area but minimal momentum behind this specific approach.",
  "r": 3,
  "rn": "Partially relevant to AI agents in networking (autonomous configuration), but focuses more on sensing optimization and ISAC than on agent architectures, protocols, or capabilities; agents are treated as an enabler rather than the core topic.",
  "c": [
    "Autonomous netops",
    "ML traffic mgmt",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft outlines networking scenarios for AI agents in enterprise and home broadband environments, distinguishing them from 6G and Internet contexts. It documents emerging use cases and associated networking requirements for agentic services that are still in early deployment stages.",
  "n": 2,
  "nn": "Incremental documentation of scenarios; lacks technical novelty in networking mechanisms. Primarily descriptive rather than prescriptive, covering reasonably foreseeable applications of existing agent architectures.",
  "m": 1,
  "mn": "Problem statement and scenario description only; no protocol specifications, mechanisms, or implementation details provided. Eight pages suggest high-level overview rather than technical depth.",
  "o": 4,
  "on": "Significant overlap with ongoing 6G, IETF Internet use case, and general AI/ML networking discussions. Scenarios appear derivative of standard multi-agent communication patterns without distinctive differentiation.",
  "mo": 2,
  "mon": "Single revision snapshot (2025-10-20); insufficient evidence of sustained development or working group traction. Limited visibility into adoption or community engagement beyond initial draft submission.",
  "r": 3,
  "rn": "Partially relevant to AI agent networking; focuses on scenarios rather than core agent protocols, infrastructure, or interoperability challenges. More business/use-case focused than technical contribution to agent networking.",
  "c": [
    "Autonomous netops",
    "Agent discovery/reg",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Lisp-Nexagon combines LISP protocol with H3 spatial indexing to create a geospatial intelligence network for distributed agents in transportation, public safety, and logistics. The draft proposes a framework for agents to report and aggregate location-based state information across networks.",
  "n": 2,
  "nn": "Incremental combination of two established technologies (LISP and H3); lacks architectural innovation beyond straightforward integration",
  "m": 2,
  "mn": "Early sketch with abstract concepts; no detailed protocol specification, message formats, or implementation guidance provided in 21 pages",
  "o": 4,
  "on": "Significant overlap with existing geospatial protocols, location services, and LISP-based routing work; H3 integration appears standard rather than novel",
  "mo": 1,
  "mon": "Single draft dated 2025-09-23 with no revision history; no evidence of WG discussion, community adoption, or iterative development",
  "r": 3,
  "rn": "Partially relevant to autonomous networked systems but focused on geolocation reporting rather than AI agent coordination, decision-making, or intelligence paradigms",
  "c": ["Agent discovery/reg", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "Proposes a SCIM 2.0 extension to represent agents and agentic applications as manageable identity objects, extending existing User and Group schemas with new resource types to enable interoperability across identity providers and agentic systems.",
  "n": 2,
  "nn": "Incremental extension mapping agent concepts onto existing SCIM framework; lacks novel architectural or security insights specific to agent management.",
  "m": 2,
  "mn": "Early draft stage; abstract describes intent but document likely lacks detailed schema definitions, protocol flows, examples, or implementation guidance for agent-specific operations.",
  "o": 3,
  "on": "Shares conceptual overlap with SCIM core (User/Group extension pattern), agent identity frameworks, and emerging agent management protocols; positioning relative to other agent orchestration standards unclear.",
  "mo": 1,
  "mon": "Single revision dated 2026; no evidence of WG sponsorship, community adoption, or iterative refinement; appears exploratory without institutional momentum.",
  "r": 4,
  "rn": "Directly addresses practical need for agent identity and lifecycle management in multi-domain scenarios; highly relevant to agent interoperability but implementation maturity unclear.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes extended per-hop BGP metrics to enable sophisticated routing policies beyond standard BGP-4 capabilities. Aims to address the limitation of globally significant metrics in BGP to support common operational practices.",
  "n": 2,
  "nn": "Incremental extension to BGP with per-hop metrics; addresses known limitations but represents straightforward enhancement rather than fundamental innovation.",
  "m": 2,
  "mn": "Early-stage draft with abstract description of proposed metrics; lacks detailed protocol specification, encoding formats, implementation guidelines, or test vectors.",
  "o": 4,
  "on": "Significant overlap with existing BGP extensions (BGP communities, extended communities, large communities, segment routing). Similar goals addressed through multiple competing proposals.",
  "mo": 1,
  "mon": "Single revision in 2024; no evidence of WG adoption, implementation activity, or community discussion. Appears dormant relative to active BGP extension efforts.",
  "r": 1,
  "rn": "Not relevant to AI or autonomous agents. Standard network routing protocol enhancement with no connection to AI/ML systems or agent-based networking.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes cryptographically verifiable inference chains for AI agents using ZKML proofs and TEE attestations to prove computational provenance (HOW), complementing actor and intent chains for complete governance. Part of a broader 'Truth Stack' framework for autonomous AI agent governance via OAuth token extensions.",
  "n": 2,
  "nn": "Incremental contribution combining established techniques (ZKML, TEE attestation, Merkle roots) in a new layering scheme; the novelty is primarily architectural rather than algorithmic.",
  "m": 2,
  "mn": "Early sketch with abstract definitions; lacks detailed protocol mechanics, integration examples, or concrete implementation guidance for production ZKML/TEE coordination.",
  "o": 3,
  "on": "Shares core concepts with existing ZKML research, TEE attestation standards (Intel SGX, ARM TrustZone), and verifiable computation work; chains pattern appears in supply-chain/blockchain contexts but AI-agent application is somewhat novel.",
  "m": 1,
  "mon": "Appears to be a 2026 draft (future-dated or speculative), no evidence of multiple revisions, WG adoption, or reference implementations; experimental framing suggests very early stage.",
  "r": 5,
  "rn": "Directly addresses critical AI agent governance challenge: proving which model actually produced an inference output; core to trust and auditability in autonomous systems.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "Model serving/inference",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "Defines an EAT profile for attesting autonomous AI agents' model integrity, training data provenance, and inference policies using CWTs/JWTs within IETF RATS. Includes optional extensions for 5G/6G network function interoperability with ETSI and 3GPP standards.",
  "n": 2,
  "nn": "Incremental extension of existing EAT framework to AI agents; claims design is straightforward application of established attestation patterns to new domain.",
  "m": 3,
  "mn": "Defined protocol with standardized claims and CBOR/JWT encoding, but lacks implementation examples, test vectors, and validation against real AI agent deployment scenarios.",
  "o": 3,
  "on": "Shares foundational concepts with EAT (RFC 9334), RATS architecture, and general attestation work; some overlap with broader AI security/governance discussions but distinct encoding approach.",
  "mo": 2,
  "mon": "Single dated revision (2026-02-24); no evidence of WG adoption, multiple versions, or community feedback cycle. Early-stage draft with limited visible momentum.",
  "r": 4,
  "rn": "Directly addresses agent identity/authentication and attestation needs; relevant to autonomous agent security and governance, though focuses more on infrastructure interop than core agent behavior.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Model serving/inference",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "AQG proposes a PageRank-like trust scoring mechanism for AI agents based on delegation transaction graphs, enabling evaluation of agent reliability in multi-agent systems. The protocol defines delegation record formats, graph construction, scoring algorithms, and query APIs for trustworthiness assessment.",
  "n": 2,
  "nn": "Applying web graph ranking to agent delegation is incremental; the core insight (transitive trust via delegation chains) is straightforward adaptation of existing PageRank methodology to a new domain without significant algorithmic innovation.",
  "m": 2,
  "mn": "Early sketch phase; abstract defines concepts and scope but 9 pages insufficient for protocol specification. Missing delegation record schema details, graph construction algorithms, scoring parameters, API specifications, and security considerations.",
  "o": 4,
  "on": "Significant conceptual overlap with existing work: PageRank variants (Google, web trust), reputation systems (EigenTrust, Advogato), and agent trust frameworks. The application domain is narrower than prior art but doesn't meaningfully differentiate mechanically.",
  "mo": 1,
  "mon": "Single dated revision (2026-05-02), no evidence of active development, WG discussion, or implementation efforts. No community adoption signals or follow-up activity visible.",
  "r": 4,
  "rn": "Directly relevant to multi-agent AI systems and inter-agent trustworthiness evaluation, but somewhat narrow in scope (delegation graphs only). Addresses real emerging need but lacks comprehensive agent lifecycle context.",
  "c": [
    "A2A protocols",
    "AI safety/alignment",
    "Agent discovery/reg",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft extends the vCon (Virtualized Conversations) format to capture autonomous AI agent internal sessions—including prompts, tool calls, reasoning, and artifacts—alongside human-facing conversations. It leverages existing vCon infrastructure for identity, lawful basis, lifecycle management, and signing without introducing new top-level fields.",
  "n": 2,
  "nn": "Incremental contribution that applies an existing conversation format to a new use case (agent instrumentation); the core novelty is primarily in schema mapping rather than novel mechanisms.",
  "m": 3,
  "mn": "Defined protocol with clear structure and reference to companion specs (VAC CDDL schema); lacks implementation examples, test vectors, and validation guidance needed for full maturity.",
  "o": 3,
  "on": "Shares conceptual overlap with vCon lifecycle/lawful-basis drafts and VAC schema work; positions itself as a compatible extension rather than competing approach, reducing direct conflict.",
  "mo": 2,
  "mon": "Single revision observed (2026-05-20 timestamp); no clear evidence of WG adoption, community feedback cycles, or multiple iterations suggesting active momentum.",
  "r": 4,
  "rn": "Directly relevant to agent transparency, auditability, and human-agent interaction; timely for AI governance and compliance use cases, though narrower than core agent protocol concerns.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes multimodal requirements for agent-to-agent protocols enabling autonomous agents to negotiate heterogeneous data capabilities and exchange synchronized content with adaptive QoS. Addresses multi-channel communication, data type negotiation, and quality-of-service policies for AI agent interactions.",
  "n": 2,
  "nn": "Incremental extension combining existing multimodal data handling with agent protocol requirements; QoS adaptation is well-established concept applied to new domain.",
  "m": 2,
  "mn": "Early sketch document; specifies requirements only without detailed protocol definition, normative mechanisms, or implementation guidance; 5 pages suggests incomplete specification.",
  "o": 4,
  "on": "Significant overlap with existing work on multimodal interfaces, RTP/RTCP media negotiation, SDP, and agent communication frameworks; limited novel architectural choices evident.",
  "mo": 1,
  "mon": "Single revision dated 2026-01-09 with no evidence of community discussion, WG sponsorship, or iterative development; appears to be initial submission without adoption signals.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; focuses on protocol requirements rather than core AI safety, alignment, or agent behavior; treats agents as communication endpoints rather than intelligent entities.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "ML traffic mgmt",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "ANS defines a DNS-like name registration and resolution protocol for autonomous AI agents, mapping human-readable agent:// URIs to cryptographic peer identities within the ANP suite. It provides narrow name-binding functionality across unicast, anycast, and channel addressing modes using GossipSub and DHT dissemination.",
  "n": 2,
  "nn": "Incremental adaptation of established DNS/naming patterns to agent-oriented networks; core concepts (hierarchical naming, registration, resolution) are well-precedented in traditional DNS and DHT systems.",
  "m": 3,
  "mn": "Protocol definition is reasonably complete with specified methods and formats, but lacks implementation details, test vectors, and deployment guidance needed for production readiness.",
  "o": 4,
  "on": "Significant conceptual overlap with DNS, SRV records, and DHT-based naming systems (BitTorrent DHT, IPFS IPNS); positioning relative to existing agent discovery systems and companion protocols (ADP, AIP) is unclear.",
  "mo": 1,
  "mon": "Single draft revision dated 2026-03-25 with no evidence of WG adoption, community discussion, or prior versions; appears to be nascent work without demonstrated momentum.",
  "r": 4,
  "rn": "Directly relevant to agent infrastructure and discovery, addressing real coordination challenges for distributed AI systems; however, relevance contingent on ANP/AIP/ADP ecosystem adoption which is unproven.",
  "c": [
    "Agent discovery/reg",
    "Agent identity/auth",
    "A2A protocols",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Proposes a hardware-rooted cryptographic framework for verifying workload identity and geographic location using zero-knowledge proofs, binding software identities to silicon while preserving location privacy for sovereign cloud workloads.",
  "n": 4,
  "nn": "Novel combination of ZKP-based geofencing with hardware-rooted attestation and silicon-to-workload chain of trust; location privacy via ZKP is notably inventive, though individual components exist.",
  "m": 2,
  "mn": "Early draft stage; abstract and problem well-articulated but protocol mechanics, cryptographic details, and implementation guidance appear underdeveloped for a 22-page document.",
  "o": 2,
  "on": "Minimal overlap; geofencing and attestation exist separately, but ZKP-privacy-preserving geofencing bound to hardware identity is distinctive within WIMSE context.",
  "mo": 2,
  "mon": "Single revision dated 2026-03-02; no evidence of WG adoption, implementation efforts, or community engagement yet; nascent draft momentum.",
  "r": 4,
  "rn": "Directly relevant to WIMSE agent architecture and workload identity authentication; addresses sovereign compute and high-assurance environments critical for enterprise AI agent deployment.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "ATTP proposes a synchronous request-response protocol layered over HTTP for AI agent-to-server communication, mandating cryptographic identity verification, per-message signing, and audit trails. It complements the asynchronous ATP protocol and uses JWT-based Agent Passports with ECDSA P-256 signatures for all interactions.",
  "n": 2,
  "nn": "Largely applies existing cryptographic primitives (JWT, ECDSA, nonces, timestamps) to agent communication; the core idea of signing agent requests is incremental rather than novel, though the specific mandatory framework for agents is a useful contribution.",
  "m": 3,
  "mn": "Protocol is well-specified with defined headers and cryptographic requirements, but lacks implementation evidence, test vectors, or interoperability examples; appears ready for specification but not yet validated in practice.",
  "o": 4,
  "on": "Significant overlap with mutual TLS, OAuth 2.0 for service-to-service auth, and existing API signing schemes (AWS SigV4, HTTP signatures); the agent-specific framing is novel but core mechanisms are established.",
  "m": 2,
  "mon": "Single dated revision (2026-03-30 suggests future speculation), no evidence of WG adoption, community review, or iterative refinement; appears to be an individual submission.",
  "r": 4,
  "rn": "Directly relevant to securing agent-to-API communication and agent identity/authentication, core concerns for deployed autonomous systems; less relevant to alignment, discovery, or policy layers.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Defines an OpenID Connect profile for issuing identity tokens to autonomous AI agents, introducing standard claims for agent identity, ownership, trust posture, and compliance screening. Enables RPs to validate agent tokens and enforce graduated access controls without modifying core OpenID Connect protocol.",
  "n": 2,
  "nn": "Incremental extension applying existing OpenID Connect patterns to agent identity; straightforward adaptation of established IdP/RP model to new use case without fundamental protocol innovation.",
  "m": 2,
  "mn": "Early sketch at 2 pages; lacks implementation details, test vectors, validation rules, claim schemas, and worked examples of RP enforcement logic; needs substantial development for deployment readiness.",
  "o": 3,
  "on": "Shares concepts with agent authentication/RBAC work (OAuth 2.0 for Devices, service account patterns) and OpenID Connect extensions; minor novelty in applying IdP model specifically to autonomous agents rather than new approach.",
  "mo": 1,
  "mon": "Single revision dated 2026-03-26 with no visible revision history or community discussion; appears to be initial submission without demonstrated WG or implementer adoption.",
  "r": 4,
  "rn": "Directly relevant to agent identity and authentication infrastructure; addresses real operational need for distinguishing and controlling autonomous agents in enterprise environments, though framed narrowly around OpenID Connect rather than broader agent governance.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "This draft integrates remote attestation capabilities into EDHOC, a lightweight key exchange protocol, following the RATS architecture to enable devices to verify each other's trustworthiness during establishment of authenticated connections. It addresses attestation as a component of secure communication for resource-constrained IoT and embedded systems.",
  "n": 2,
  "nn": "Incremental contribution combining existing standards (EDHOC + RATS) rather than introducing fundamentally new concepts; represents a natural extension of EDHOC functionality.",
  "m": 3,
  "mn": "Protocol mechanism is defined with conceptual clarity, but document appears to lack detailed implementation examples, test vectors, and interoperability guidance typical of mature IETF specifications.",
  "o": 3,
  "on": "Shares core concepts with existing RATS framework and EDHOC specification; moderate overlap with prior work on attestation in constrained environments, though specific integration approach offers some distinctiveness.",
  "mo": 2,
  "mon": "Single recent revision (Jan 2025) with limited indication of WG discussion, adoption momentum, or multiple implementation efforts; typical early-stage draft activity level.",
  "r": 2,
  "rn": "Tangentially related to AI agents—addresses device identity/authentication and trustworthiness verification which could apply to agent infrastructure, but not specifically designed for or focused on autonomous agent systems.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "AEE proposes a lightweight JSON envelope format for inter-agent communication with 14 standardized fields for routing, correlation, and tracing while deliberately omitting payload semantics. The work addresses the practical need for transport-agnostic message framing across heterogeneous AI agent frameworks.",
  "n": 2,
  "nn": "Incremental contribution; JSON envelopes and message framing are well-established patterns (cf. CloudEvents, AMQP, gRPC metadata). The 14-field structure is a minor design choice rather than fundamental innovation.",
  "m": 4,
  "mn": "Well-structured specification with clear field definitions, validity rules, and conformance levels. Includes entity identifier conventions and reserved namespaces. Appears implementation-ready, though test vectors and reference implementations would strengthen maturity to 5.",
  "o": 4,
  "on": "Significant overlap with CloudEvents (CNCF standard), AMQP message frames, gRPC metadata, and existing agent protocol proposals (e.g., JSON-RPC 2.0 for envelope-like concepts). Differentiation from these is marginal.",
  "m": 2,
  "mon": "Single draft revision (2026-02-28); no evidence of WG adoption, community discussion, or competing proposals. Early-stage specification without apparent implementation ecosystem or operational deployments.",
  "r": 4,
  "rn": "Directly relevant to agent-to-agent communication infrastructure. Addresses genuine interoperability pain points in multi-agent systems. However, relevance is operational/engineering-focused rather than cutting-edge AI capability or safety.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes an ontology-based semantic layer for agent-to-agent interaction in IoA, defining common classes, properties, and JSON-LD serialization with negotiation and alignment procedures. Aims to enable deterministic semantic interoperability without specifying transport or security.",
  "n": 2,
  "nn": "Incremental contribution combining existing ontology concepts (RDF/JSON-LD) with agent interaction context; semantic layers for interop are established practice, main novelty is IoA-specific framing.",
  "m": 3,
  "mn": "Defines protocol-level mechanism with required classes/properties and negotiation procedures, but lacks implementation examples, test vectors, or validation against heterogeneous real-world ontologies.",
  "o": 4,
  "on": "Significant overlap with W3C PROV, SOSA/SSN ontologies, and existing semantic web agent frameworks (FIPA ACL, Jason/AgentSpeak); negotiation/alignment concepts echo ontology matching literature.",
  "mo": 1,
  "mon": "Single draft dated 2026-04-22 with no revision history apparent; no evidence of WG discussion, implementation uptake, or community feedback; appears nascent.",
  "r": 4,
  "rn": "Directly relevant to agent interoperability and A2A protocols; solid fit for emerging IoA standardization needs, though positioned as semantic substrate rather than core agent functionality.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes Fully Adaptive Routing Ethernet (FARE), extending WECMP load-balancing from scale-out to scale-up networks to support efficient expert parallelization in MoE-based LLM training and inference across GPU clusters.",
  "n": 2,
  "nn": "Incremental adaptation of existing WECMP mechanisms to a different network scale; the core contribution is applying known load-balancing techniques to MoE-specific hardware constraints rather than introducing fundamentally new routing paradigms.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes motivation and high-level approach but the 9-page draft likely lacks detailed protocol specifications, algorithm descriptions, or implementation validation needed for production deployment.",
  "o": 3,
  "on": "Shares foundational concepts with existing adaptive routing and ECMP variants; overlaps with prior work on AI datacenter networking (e.g., NVIDIA Cumulus, Facebook's f16 designs) though specific FARE application to MoE may be somewhat novel.",
  "mo": 1,
  "mon": "Single draft revision dated 2026-02-27 with no evidence of WG adoption, multiple revisions, or community discussion; appears to be early-stage individual submission without established momentum.",
  "r": 4,
  "rn": "Directly relevant to AI infrastructure; addresses critical bottleneck in distributed LLM training/inference, though focuses on networking layer rather than agent behavior, safety, or high-level AI coordination.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "AgentCard proposes a lightweight JSON schema for autonomous agents to declare identity, capabilities, endpoints, and pricing in a framework-agnostic manner. It aims to enable interoperability between heterogeneous agent platforms (LangChain, CrewAI, AutoGen, etc.) without prior coordination, drawing inspiration from HTTP headers and grounding pricing in Landauer's principle.",
  "n": 3,
  "nn": "Useful contribution addressing a real interop gap, but combines relatively straightforward concepts (ULIDs, dot-namespacing, capability schemas) without fundamental innovation. The energy-pricing floor angle is creative but speculative.",
  "m": 3,
  "mn": "Defined protocol with stated schema structure and design principles, but document lacks detailed normative specs, formal grammar, complete examples, test vectors, and validation rules. Ready for discussion but needs substantial engineering work.",
  "o": 3,
  "on": "Shares conceptual territory with OpenAI function schemas, MCP tool definitions, and existing agent frameworks' capability declarations. Not a duplicate, but incremental synthesis rather than orthogonal approach.",
  "mo": 1,
  "mon": "April 2026 date suggests recent proposal with single apparent revision. No evidence of WG adoption, implementation demos, or community traction in abstract/metadata. Appears early-stage independent work.",
  "r": 4,
  "rn": "Directly addresses agent interoperability and A2A communication—core infrastructure gaps in the emerging multi-agent ecosystem. Highly relevant to current AI systems deployment challenges.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent identity/auth",
    "Agent discovery/reg",
    "ML traffic mgmt"
  ]
}
```


```json
{
  "s": "Proposes a wire-layer mechanism for negotiating where identity inference computation occurs based on data provenance class, with three tiers distinguishing active, passive-aggregate, and passive-individual observations. Enforces consent-based routing through wire-layer refusal rather than cryptographic proof, composing with existing discovery and policy frameworks.",
  "n": 2,
  "nn": "Incremental contribution combining existing consent/policy concepts with location-of-computation routing; the provenance classification scheme is useful but relatively straightforward extension of standard access control patterns.",
  "m": 2,
  "mn": "Early sketch phase; describes architectural intent and three provenance classes but lacks detailed protocol specifications, message formats, error handling procedures, or implementation guidance needed for interoperability.",
  "o": 4,
  "on": "Significant overlap with existing work on consent management (GDPR consent signals), data minimization principles (differential privacy literature), and federated learning frameworks that separately handle server vs. edge computation; primarily reframes these concepts in identity-inference context.",
  "mo": 1,
  "mon": "Single revision with 2026 date suggests nascent effort; no evidence of WG sponsorship, community discussion, or iterative refinement based on feedback; appears to be standalone proposal without adoption signals.",
  "r": 3,
  "rn": "Partially relevant to AI agents; directly addresses inference computation location and consent enforcement for identity systems, but focuses narrowly on inference servers rather than broader agent autonomy, coordination, or safety concerns.",
  "c": ["Policy/governance", "Model serving/inference", "Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "This draft establishes vendor-independent benchmarking methodologies and KPIs for evaluating Ethernet-based AI inference serving network fabrics, addressing the critical bottleneck of interconnect performance in disaggregated LLM inference architectures. It covers RDMA-based KV cache transfer, MoE expert parallelism, request routing, congestion management, and scale testing to enable reproducible apples-to-apples fabric performance comparison.",
  "n": 3,
  "nn": "Incremental contribution adapting existing BMWG benchmarking frameworks to AI inference workloads; the core novelty is domain-specific application rather than methodological innovation.",
  "m": 4,
  "mn": "Well-structured specification with defined terminology, comprehensive KPI coverage, and realistic test procedures; lacks implementation examples and validation results but provides clear guidance for benchmark execution.",
  "o": 2,
  "on": "Minor overlap with general network fabric benchmarking work; TRAINING-BENCH companion document and inference-specific focus (TTFT, ITL, TPS metrics) differentiate this from prior BMWG efforts.",
  "mo": 2,
  "mon": "Single revision as of 2026-02-27; no evidence of WG adoption or multiple iterations; early-stage draft with limited community engagement signals.",
  "r": 5,
  "rn": "Directly addresses core AI infrastructure challenge—network fabric becomes critical bottleneck in disaggregated LLM inference systems; highly relevant to agent deployment scaling.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "HAIP proposes a real-time identity verification protocol for AI agents using microsecond-precision pulses and decentralized identity mechanisms. The draft addresses trust and integrity concerns in autonomous agent environments through NIST-aligned non-repudiation.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (heartbeat mechanisms, decentralized identity, non-repudiation) without substantial technical innovation.",
  "m": 1,
  "mn": "Problem statement and conceptual framing only; lacks protocol specification details, message formats, cryptographic algorithms, state machines, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing work on agent authentication (SPIFFE/SPIRE), integrity verification (COSE), and distributed identity systems; the 6.42µs pulse claim appears unmotivated and disconnected from practical protocol layers.",
  "mo": 1,
  "mon": "Single dated draft (2026-04-30) with no evidence of revision history, community discussion, working group sponsorship, or implementation activity.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; identity and integrity are legitimate concerns, but the draft conflates multiple problem domains and lacks clarity on which agent scenarios it actually addresses.",
  "c": [
    "Agent identity/auth",
    "AI safety/alignment",
    "A2A protocols",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "AgentDNS proposes a domain naming and service discovery system for LLM agents, drawing inspiration from traditional DNS to enable autonomous discovery and invocation of agent services across vendors. The system addresses interoperability, service discovery, and trust management in multi-agent ecosystems through unified namespace, semantic discovery, and authentication mechanisms.",
  "n": 2,
  "nn": "Incremental adaptation of established DNS concepts to agent domain; lacks fundamental innovation beyond applying existing naming/discovery patterns to new use case.",
  "m": 2,
  "mn": "Early sketch with conceptual framework; no detailed protocol specifications, message formats, or implementation details evident; minimal technical depth for standardization track.",
  "o": 4,
  "on": "Significant overlap with existing service discovery (DNS-SD, mDNS, Consul), agent frameworks (OpenAI Functions, LangChain tools), and identity solutions; concepts not sufficiently differentiated.",
  "mo": 1,
  "mon": "Single draft submission with 2026 date suggests limited development history; no evidence of WG discussion, implementation, or community adoption feedback.",
  "r": 4,
  "rn": "Directly addresses agent interoperability and service discovery challenges relevant to AI agent ecosystems, though framing as IETF standards effort is questionable for LLM-specific infrastructure.",
  "c": ["Agent discovery/reg", "A2A protocols", "Agent identity/auth", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "TTTPS proposes a TLS 1.3 extension adding cryptographically verifiable temporal ordering via Proof-of-Time (PoT) to defend against strategic channel controllers exploiting ordering for economic advantage. The protocol targets autonomous AI agents where latency-based ordering advantages are structurally neutralized, using a multi-stage compression pipeline (Golomb-Rice, Reed-Solomon, Golay, HMAC) with an AdaptiveSwitch mechanism to make manipulation economically self-defeating.",
  "n": 4,
  "nn": "The Strategic Channel Controller Problem (SCCP) framing is novel and the specific application to AI agent temporal ordering is genuinely original. However, the core cryptographic primitives (PoT, HMAC pipelines) are well-established; novelty lies in problem identification and integration rather than fundamental cryptographic innovation.",
  "m": 2,
  "mn": "Protocol specification is incomplete (abstract truncates mid-sentence at 'The GRG pipeline specification will be p...'). Describes high-level mechanism but lacks formal definitions, full algorithm specifications, security proofs, implementation details, and test vectors. Claims of 70k records on Base Sepolia are empirical validation but insufficient for maturity without complete technical specification.",
  "o": 3,
  "on": "Shares ordering/sequencing concerns with blockchain timestamp protocols and BFT consensus literature. Overlaps with existing work on Byzantine time-keeping and fairness in MEV prevention. The specific PoT pipeline construction appears novel, but the problem domain has been explored in distributed systems and fair sequencing literature.",
  "mo": 1,
  "mon": "Single draft revision (2026-04-19), marked Experimental status, incomplete specification, and no evidence of IETF WG engagement. Appears to be initial submission rather than active development. Companion paper [POT2026] is cited but presumably unpublished. No indication of multiple iterations or community adoption.",
  "r": 4,
  "rn": "Directly addresses autonomous AI agent infrastructure vulnerabilities, specifically temporal ordering manipulation as agents converge on symmetric latencies. The 55% of verified records from AI agents validates claimed relevance. Core concern is agent economy stability and


```json
{
  "s": "Pilot Protocol proposes an overlay network layer providing autonomous AI agents with stable virtual identities, addresses, and standard transport services (TCP/UDP-like) over UDP. It aims to give AI agents first-class network citizenship with NAT traversal and encryption, operating beneath application-layer protocols like A2A and MCP.",
  "n": 2,
  "nn": "Overlay networks and virtual addressing are well-established concepts; the application to AI agents is incremental rather than architecturally novel. Combines existing techniques (UDP encapsulation, NAT traversal, encryption) without significant protocol innovation.",
  "m": 3,
  "mn": "Document specifies a protocol with defined mechanisms for addressing, multiplexing, and transport. Appears to have protocol details but unclear if implementation-ready; 43 pages suggests reasonable depth but likely lacks test vectors, conformance tests, or reference implementations.",
  "o": 4,
  "on": "Significant overlap with existing overlay networks (Tinc, Wireguard concepts), VPN tunneling, and agent communication frameworks. The agent-centric framing is novel but the underlying technical approach replicates established patterns from overlay networking.",
  "m": 2,
  "mon": "Single 2026-04-06 revision with no visible prior versions or community discussion. No evidence of WG adoption, implementation pilots, or iterative refinement. Appears to be initial submission without established momentum.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent infrastructure and standardization. Addresses real problem of agent network identity and discovery, though relevance is architectural rather than focused on agent capabilities, safety, or learning.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Autonomous netops",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Specifies a proof-of-possession mechanism for third-party services to verify that messaging platform users legitimately control asserted telephone numbers as communication identifiers. The approach supports secure enrollment in interoperable real-time communication applications within the MIMI framework.",
  "n": 2,
  "nn": "Incremental contribution applying existing proof-of-possession patterns to telephone number verification for messaging platforms; limited conceptual novelty.",
  "m": 3,
  "mn": "Defined protocol mechanism with clear problem scope, but 7 pages suggests incomplete specification lacking detailed test vectors or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing telephone number verification schemes (SMS-based OTP, carrier authentication) and general identity proofing frameworks; mostly recontextualizes known approaches.",
  "mo": 2,
  "mon": "Single draft revision with uncertain WG adoption status; appears exploratory for MIMI context rather than demonstrating active community momentum.",
  "r": 2,
  "rn": "Tangentially related to agent systems; addresses communications identity verification for messaging platforms but not core AI agent functionality, autonomy, or intelligence concerns.",
  "c": ["Agent identity/auth", "Data formats/interop", "Human-agent interaction"]
}
```


```json
{
  "s": "This draft addresses interoperability issues with Zstandard compression in HTTP by upgrading window size limits from RFC8878 recommendations to strict requirements. It aims to prevent memory exhaustion concerns that cause some browsers to reject certain zstd-compressed content.",
  "n": 2,
  "nn": "Incremental refinement of existing compression standard; primarily clarifies and tightens requirements rather than introducing novel concepts.",
  "m": 4,
  "mn": "Well-defined specification updating RFC8878 with clear window size requirements suitable for HTTP deployment; appears implementation-ready.",
  "o": 3,
  "on": "Directly addresses known interoperability patterns in zstd deployment; shares conceptual space with other content-encoding RFCs but focuses on specific parameter constraint.",
  "mo": 2,
  "mon": "Appears to be single or early-stage revision addressing specific deployment pain point; limited evidence of broader WG momentum beyond problem identification.",
  "r": 1,
  "rn": "Not relevant to AI agents; standard HTTP content encoding specification with no connection to agent systems, ML operations, or autonomous networking.",
  "c": ["Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes requirements and enabling technologies for AI agent protocols tailored to 6G networks, positioning the telecom industry as a key adopter of agent-based systems. It attempts to bridge AI agent ecosystems with mobile communication infrastructure, addressing protocol design for next-generation networks.",
  "n": 2,
  "nn": "Incremental combination of existing agent protocol concepts applied to 6G context; lacks novel protocol innovations or fundamentally new requirements.",
  "m": 2,
  "mn": "Early-stage requirements document with problem framing; no detailed protocol specifications, mechanisms, or implementation guidance provided.",
  "o": 4,
  "on": "Significant overlap with ongoing 3GPP 6G studies, ITU-T agent standardization efforts, and multiple concurrent IETF agent protocol drafts; lacks differentiation.",
  "mo": 1,
  "mon": "Single dated revision from 2026; unclear WG sponsorship, adoption interest, or community engagement; appears exploratory rather than momentum-driven.",
  "r": 3,
  "rn": "Partially relevant to AI agents in telecom context, but framed more as 6G systems architecture than as core agent protocol work; tangential to pure agent protocol development.",
  "c": [
    "Agent discovery/reg",
    "A2A protocols",
    "Autonomous netops",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes trustworthiness-based routing to enable differentiated security services in networks, addressing operator needs for QoE guarantees alongside security threats. It identifies use cases and requirements but lacks concrete protocol specifications or solutions.",
  "n": 2,
  "nn": "Incremental extension of existing QoE/SLA concepts applied to security dimension; trustworthiness-based routing is a logical but not novel concept in network security literature.",
  "m": 1,
  "mn": "Pure problem statement and use case exploration with no protocol definition, mechanism design, or implementation details provided.",
  "o": 4,
  "on": "Significant overlap with existing work in security-aware routing, trust-based networking, and differentiated services (DiffServ); concepts not sufficiently differentiated from prior art.",
  "mo": 1,
  "mon": "Single revision (2024-07), no evidence of WG adoption, community discussion, or iterative development beyond initial draft submission.",
  "r": 1,
  "rn": "Not related to AI agents or autonomous systems; focuses on traditional network routing and operator requirements without agent-relevant components.",
  "c": ["Policy/governance"]
}
```


```json
{
  "s": "PTV proposes a hardware-anchored attestation protocol for proving AI agents run authorized models and policies without exposing sensitive data, designed to compose with existing RATS mechanisms. It separates identity binding from behavioral continuity, treating the latter as a separate concern addressed through exercise-time checks and execution receipts.",
  "n": 2,
  "nn": "Incremental contribution combining existing attestation concepts (RATS, CBOR envelopes, SCITT) with AI agent identity binding; the novelty lies primarily in the application domain and threat model decomposition rather than fundamental protocol innovation.",
  "m": 3,
  "mn": "Defined protocol with specified envelope format (CBOR/CDDL), message types, and threat model, but at 14 pages lacks detailed specification, implementation examples, test vectors, or reference implementations needed for maturity.",
  "o": 3,
  "on": "Shares significant conceptual overlap with RATS attestation frameworks, CBOR/CDDL standardization work, and SCITT composition; the primary differentiation is agent-specific identity binding rather than novel architectural principles.",
  "mo": 1,
  "mon": "Single revision (2026-04-05 expiration suggests early-stage draft), no apparent WG sponsorship or adoption signals; appears to be individual submission without evident community momentum or iterative development.",
  "r": 4,
  "rn": "Directly relevant to AI agent identity and authentication; addresses practical use cases (CDSS, ICS/OT) and regulatory compliance concerns, though framed narrowly around attestation rather than broader agent autonomy challenges.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes a standardized vocabulary for expressing content usage preferences to search and AI crawlers, enabling structured declarations of restrictions or permissions. Aims to address the gap between existing robots.txt approaches and more nuanced AI/search crawler control requirements.",
  "n": 2,
  "nn": "Incremental extension of existing crawler control mechanisms (robots.txt, meta tags). The core concept of preference vocabularies for crawler behavior is not novel, though application to AI specifically adds marginal novelty.",
  "m": 2,
  "mn": "Early sketch stage. Abstract indicates vocabulary proposal but lacks detail on syntax, semantics, implementation mechanisms, or how declarations are discovered/enforced. No protocol specification, examples, or deployment considerations evident.",
  "o": 4,
  "on": "Significant overlap with existing standards: robots.txt, Robots Exclusion Standard (RES), meta robots tags, and emerging work on AI-specific crawler directives. Related to content licensing vocabularies (CC, ODRL). Appears to be yet another layer on established patterns.",
  "m": 1,
  "mon": "Likely single revision or early-stage work. Limited evidence of WG engagement, community adoption, or active development momentum. Published September 2025 but appears nascent.",
  "r": 4,
  "rn": "Directly relevant to AI agent governance and content control policies. Addresses legitimate concern about AI crawler proliferation. Relevance diminished by unclear technical approach and relationship to existing standards.",
  "c": ["Policy/governance", "Data formats/interop", "Agent discovery/reg", "Other AI/agent"]
}
```


```json
{
  "s": "Extends OAuth 2.0 FiPA specification with standardized metadata format for AI agent authentication challenges via Structured Elicitation. Addresses interoperability gap by defining how agents discover and respond to authenticator requirements in just-in-time authorization flows.",
  "n": 2,
  "nn": "Incremental extension adding JSON metadata schema to existing FiPA framework; builds predictably on established OAuth patterns rather than introducing novel authorization concepts.",
  "m": 3,
  "mn": "Defines protocol mechanism with clear elicitations array structure and MCP binding, but lacks implementation examples, test vectors, and deployment guidance needed for production readiness.",
  "o": 4,
  "on": "Significant overlap with existing credential/challenge response patterns in OAuth extensions (CIBA, Device Flow); MCP-Elicitation binding duplicates similar structured metadata approaches in emerging agent frameworks.",
  "mo": 2,
  "mon": "Single dated revision (2026-04-03) with no visible WG discussion or adoption signals; appears early-stage with unclear path to standardization or community interest.",
  "r": 4,
  "rn": "Directly addresses critical AI agent authentication and human-to-agent authorization flows; highly relevant to agent identity/auth and interoperability but narrowly scoped to OAuth ecosystem.",
  "c": [
    "Agent identity/auth",
    "Human-agent interaction",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "HJS proposes a blockchain-anchored accountability layer for AI agents using four primitives (Judgment/Delegation/Termination/Verification) to create immutable responsibility chains and court-admissible evidence. The system leverages Bitcoin-anchored Open Timestamp proofs and is designed to work independently or complement existing AI agent protocols.",
  "n": 2,
  "nn": "Combines established concepts (blockchain timestamps, audit trails, responsibility chains) in a straightforward application to AI agents; lacks novel cryptographic or architectural insights.",
  "m": 2,
  "mn": "Early sketch with abstract-level design; primitives defined but no detailed protocol specification, message formats, integration examples, or implementation guidance provided.",
  "o": 4,
  "on": "Significant overlap with existing accountability/audit trail frameworks, blockchain-based provenance systems, and emerging AI governance protocols; the novelty claims about independence are weakened by intentional design to complement AIIP.",
  "mo": 1,
  "mon": "Single draft dated 2026-02-21 with no evidence of revision history, WG adoption, or community engagement; appears to be initial submission without demonstrated momentum.",
  "r": 4,
  "rn": "Directly addresses AI agent accountability and human oversight, which are core concerns in AI agent governance; however, the blockchain approach may limit practical relevance for many deployment contexts.",
  "c": [
    "Policy/governance",
    "Human-agent interaction",
    "Agent identity/auth",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "SONAR proposes a protocol for verifiable multicast delivery claims using cryptoeconomic incentives, VRF-based sampling, and blockchain attestations combined with ALTA authentication. It addresses the challenge of proving multicast reach to large populations with O(1) efficiency via statistical sampling and zkSNARK proof aggregation.",
  "n": 2,
  "nn": "Combines existing techniques (ALTA, VRF, zkSNARKs, German Tank Problem) in a novel system architecture, but individual components are well-established; the integration is incremental rather than fundamentally new.",
  "m": 3,
  "mn": "Defines protocol mechanisms with concrete overhead figures (6% bandwidth for ALTA, 0.7-2.8 Kbps for verification) and scaling parameters, but lacks implementation details, test vectors, and deployment guidance for production use.",
  "o": 3,
  "on": "Shares substantial conceptual overlap with existing work on multicast verification, blockchain-based attestation systems, and statistical sampling protocols; positioning relative to prior art unclear.",
  "mo": 1,
  "mon": "Single revision (2025-11-04), no evidence of WG discussion, adoption, or community engagement; appears to be initial submission without iteration.",
  "r": 1,
  "rn": "Addresses multicast delivery verification and network attestation; not related to AI agents, autonomous systems behavior, or AI safety—false positive for this evaluation framework.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft catalogs representative agentic AI use cases and derives protocol-relevant requirements to guide IETF standardization efforts. It focuses on exposing concrete needs like long-lived interactions, agent coordination, and security hooks that should inform how agent-to-agent and agent-to-tool protocols layer over existing IETF substrates.",
  "n": 2,
  "nn": "Incremental contribution; use case collection is standard practice for requirements definition. The connection between AI agent needs and protocol design is not novel, though systematic inventory for IETF scope is useful.",
  "m": 2,
  "mn": "Early sketch phase. Document articulates use cases and derives requirements but lacks detailed protocol proposals, specifications, or reference implementations. Serves as input document rather than standardizable mechanism.",
  "o": 3,
  "on": "Shares conceptual space with existing agent frameworks (MCP, A2A protocols) and general IETF requirements documents. Moderate overlap with concurrent work on AI protocol interoperability; positioned as gap analysis rather than novel protocol design.",
  "mo": 2,
  "mon": "Limited documented momentum. Single revision as of date; no indication of active WG sponsorship or broad community adoption. Appears positioned as exploratory work to justify future standardization rather than active protocol development.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure and protocol design. Addresses core challenges in multi-agent systems, though frames these through IETF standardization scope rather than agent-centric problems.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "APIX proposes a machine-native service discovery infrastructure for autonomous agents, defining governance, trust models, manifests, and API standards to address the structural gap between agent needs and human-centric internet discovery mechanisms.",
  "n": 2,
  "nn": "Service discovery and registry concepts are well-established; applying HATEOAS to agent discovery is incremental rather than foundational innovation.",
  "m": 2,
  "mn": "Core concepts defined but appears early-stage; references external profile drafts for actual service specifications; lacks implementation details, test vectors, and deployment examples.",
  "o": 4,
  "on": "Significant overlap with existing service mesh (Consul, Eureka), API gateway registries (Kong), and UDDI concepts; HATEOAS application is standard practice; trust/compliance aspects partially resemble enterprise API management solutions.",
  "mo": 1,
  "mon": "Single revision dated 2026-05-13 with no observable community engagement, WG adoption, or implementation activity; appears to be early-stage independent submission.",
  "r": 4,
  "rn": "Directly addresses agent service discovery and autonomy requirements; governance and trust frameworks are relevant to multi-agent systems; however, relevance depends on whether agent-native indexing becomes critical vs. existing discovery mechanisms.",
  "c": ["Agent discovery/reg", "A2A protocols", "Policy/governance", "Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "ADS proposes a distributed directory service for discovering AI agent applications based on metadata and skills. It uses content-routing protocols to interconnect distributed directories, enabling agent discovery across a network infrastructure.",
  "n": 2,
  "nn": "Incremental application of existing distributed directory concepts (DNS-like, DHT patterns) to AI agent discovery; lacks fundamental innovation in routing or metadata representation.",
  "m": 2,
  "mn": "Early sketch with abstract concepts; minimal protocol details, no formal specification, message formats, or implementation guidance provided in summary.",
  "o": 4,
  "on": "Significant overlap with DNS, service discovery (mDNS/SRV), blockchain registries, and agent capability advertising from multi-agent systems literature; content-routing echoes IPFS/Named Data Networking.",
  "mo": 1,
  "mon": "Single draft revision (2026-02-24); no evidence of WG adoption, community discussion, or iterative development since publication.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure; agent discovery and capability matching are emerging operational needs, though framing as 'distributed' may be solution-looking for problems.",
  "c": ["Agent discovery/reg", "A2A protocols", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "Proposes Intent-based Agent Interconnection Protocol (IAIP) for dynamic routing and discovery of AI agents at gateway level based on semantic capabilities rather than static addressing. Defines mechanisms for agent registration, capability advertisement, intent matching, and task dispatching in multi-agent interconnection scenarios.",
  "n": 2,
  "nn": "Incremental approach applying intent-based routing concepts (established in SDN/networking) to agent discovery; combines existing patterns (service discovery, capability matching) without fundamental innovation.",
  "m": 2,
  "mn": "Early-stage specification with high-level mechanism descriptions but lacks concrete protocol details, message formats, examples, error handling, or implementation guidance needed for interoperability.",
  "o": 4,
  "on": "Significant overlap with service mesh architectures (Istio), agent framework protocols (FIPA ACL), capability-based discovery systems, and intent-based networking (IBN) standards; positioning relative to these is unclear.",
  "mo": 1,
  "mon": "Single revision dated 2026-02-05 with no apparent WG backing, community discussion, or implementation feedback; appears to be individual author submission without active development momentum.",
  "r": 4,
  "rn": "Directly relevant to multi-agent systems and agent interconnection, though framing as IETF network protocol rather than application-layer agent coordination framework limits relevance to traditional IETF scope.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Autonomous netops",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "This draft proposes integrating post-quantum key encapsulation mechanisms (PQ-KEMs) into EAP-AKA' FS to protect against quantum computing threats to the current ECDHE-based forward secrecy extension. It addresses the vulnerability where compromised long-term and ephemeral keys could expose session keys in EAP-AKA' authentication.",
  "n": 2,
  "nn": "Incremental extension applying established PQ-KEM concepts to an existing protocol; the quantum-safety enhancement is straightforward but the specific integration details appear novel to EAP-AKA'.",
  "m": 2,
  "mn": "Early sketch phase; abstract describes motivation and problem clearly but draft lacks detailed protocol specifications, algorithm selections, integration mechanics, or implementation considerations.",
  "o": 3,
  "on": "Shares conceptual overlap with RFC 9678 (EAP-AKA' FS) and general PQ cryptography migration efforts; moderate overlap with other PQ-hybrid authentication work but specific EAP-AKA' approach is somewhat differentiated.",
  "mo": 1,
  "mon": "Single revision at submission; no evident prior versions, community discussion, or WG adoption signals visible; appears to be initial draft release with limited trajectory.",
  "r": 2,
  "rn": "Not relevant to AI agents or autonomous systems; focuses on mobile/cellular authentication protocols and quantum-safe cryptography for EAP methods, orthogonal to agent-related topics.",
  "c": ["Agent identity/auth"]
}
```


```json
{
  "s": "Proposes an integrated security framework for 5G edge networks combining I2NSF architecture with Intent-Based Networking to translate high-level security declarations into enforceable network and application policies. Supports distributed, context-aware policy enforcement across heterogeneous 5G environments with closed-loop monitoring.",
  "n": 2,
  "nn": "Incremental combination of existing standards (I2NSF, IBN, NEF); core concepts not novel but application to 5G edge security is a useful engineering contribution.",
  "m": 2,
  "mn": "Early sketch with conceptual architecture; lacks detailed protocol specifications, implementation examples, formal policy translation algorithms, or validation results.",
  "o": 4,
  "on": "Significant overlap with existing I2NSF standardization efforts and 3GPP NEF specifications; IBN concepts well-established in networking literature; limited differentiation from prior intent-based security proposals.",
  "mo": 1,
  "mon": "Single revision dated 2026-01-09; no evidence of WG adoption, community discussion, or iterative refinement; appears to be initial submission.",
  "r": 2,
  "rn": "Tangentially related to AI/agents through Intent-Based Networking automation concepts, but primarily focused on traditional network security policy enforcement rather than autonomous agents, agent protocols, or AI-driven decision-making.",
  "c": [
    "Policy/governance",
    "Autonomous netops",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft extends EAP-AKA' Forward Secrecy by replacing traditional ECDHE with post-quantum key encapsulation mechanisms to protect against future quantum computer threats. It addresses the vulnerability where adversaries with knowledge of both long-term and ephemeral keys could compromise session keys in the authentication protocol.",
  "n": 2,
  "nn": "Straightforward application of PQ-KEMs to an existing protocol; combines established concepts (PQ cryptography + EAP-AKA' FS) without novel integration techniques.",
  "m": 3,
  "mn": "Protocol mechanism is defined with clear threat model and integration approach, but lacks implementation details, test vectors, and interoperability guidance needed for production deployment.",
  "o": 4,
  "on": "Significant overlap with concurrent PQ-crypto standardization efforts (NIST PQC, RFC 9180). Similar PQ integration patterns appear in parallel IETF work on TLS 1.3 and other protocols.",
  "mo": 3,
  "mon": "Active WG engagement evidenced by publication timeline (Feb 2026) and draft iteration, but unclear adoption momentum or vendor commitment relative to other PQ migration efforts.",
  "r": 1,
  "rn": "Not relevant to AI agents; this is cryptographic protocol specification for cellular authentication. No connection to autonomous agents, AI safety, or agent systems.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes X.509 certificate extensions to embed attestation results from Certificate Signing Requests, allowing CAs to convey Attester trustworthiness claims to Relying Parties. Enables scalable verification across diverse attestation technologies by encoding appraisal evidence directly in issued certificates.",
  "n": 2,
  "nn": "Straightforward extension of existing X.509 mechanisms to carry attestation data; combines established concepts (CSR attestation, certificate extensions) without fundamental innovation.",
  "m": 3,
  "mn": "Defines protocol mechanism with extension structures and use cases, but 9 pages suggests limited depth; likely lacks detailed ASN.1 syntax, processing rules, and interoperability guidance needed for implementation.",
  "o": 3,
  "on": "Related concepts exist in attestation (RFC 9334, RATS architecture), X.509 extensions (RFC 5280), and CSR handling; this work bridges them but doesn't introduce novel concepts, overlaps moderately with attestation result encoding discussions.",
  "m": 2,
  "mon": "Single revision dated 2025-11-03 with no visible adoption signals; early-stage draft without apparent WG backing or implementation ecosystem.",
  "r": 2,
  "rn": "Tangentially related to agent identity/authentication through attestation-based trust establishment; not core to AI agent protocols or AI safety concerns; relevance is primarily in credential infrastructure rather than agent-specific systems.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "IntelliNode proposes in-network intelligent scheduling for distributed AI training/inference by integrating FPGAs and programmable switches to create a closed-loop perception-inference-decision-execution system aware of tensor semantics and compute heterogeneity. It extends the CATS framework to shift from passive probe-based scheduling to active data-plane intelligence.",
  "n": 2,
  "nn": "Incremental extension of CATS framework; in-network intelligence and awareness of compute heterogeneity are not novel concepts, though their specific combination for tensor-aware scheduling has some merit.",
  "m": 2,
  "mn": "Early sketch stage—defines four functional layers and signaling conceptually but lacks protocol details, message formats, state machine specifications, or any implementation evidence despite 6-page limit being generous.",
  "o": 4,
  "on": "Significant overlap with existing work on in-network computing (P4, NetCache, programmable dataplane ML), CATS framework extensions, and ML-aware networking (MLPerf, tensor routing). The 'closed-loop' framing is not distinctly novel.",
  "m": 1,
  "mon": "No clear momentum indicators—single draft snapshot from 2026 with no revision history, WG adoption signals, or implementation roadmap provided; appears speculative.",
  "r": 4,
  "rn": "Directly relevant to ML traffic management, model serving/inference, and autonomous network operations; core focus on AI cluster scheduling makes it squarely in the AI/networking intersection.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Proposes a multi-agent collaboration protocol suite using Agent Gateways as control-plane entities to manage registration, authentication, and semantic routing while enabling peer-to-peer interactions. Addresses scalability and security in distributed agent networks across heterogeneous systems.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (gateway architectures, semantic routing, agent registration) without substantial technical innovation beyond established patterns in service meshes and API gateways.",
  "m": 2,
  "mn": "Early sketch stage; 7 pages insufficient for protocol specification. Lacks formal syntax, state machines, message formats, error handling procedures, and implementation guidance needed for maturity.",
  "o": 4,
  "on": "Significant overlap with service mesh architectures (Istio), API gateway patterns, and existing agent communication frameworks. Gateway-based control planes and semantic routing are well-established concepts.",
  "mo": 1,
  "mon": "Single dated revision (2026-02-06) with no evidence of WG adoption, community discussion, or iterative development. No apparent momentum in IETF process.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure but positions itself as networking protocol rather than core agent technology. Relevant primarily as operational infrastructure, not agent capability or intelligence.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Autonomous netops",
    "Data formats/interop"
  ]
}
```