```json
{
  "s": "Extends an unspecified core specification to provide granular server-side controls over automated interactions, including rate limiting, technology restrictions, and API permissions. Aims to give service owners better governance mechanisms for bot and automation traffic.",
  "n": 2,
  "nn": "Incremental extension adding control mechanisms; rate limiting and permission schemes are well-established concepts applied to automation contexts.",
  "m": 2,
  "mn": "Early draft stage with undefined normative reference [CORE-SPEC]; lacks implementation details, test vectors, and concrete protocol specifications needed for maturity assessment.",
  "o": 4,
  "on": "Significant overlap with robots.txt, CAPTCHA frameworks, API throttling policies, and existing automation control mechanisms; positioning relative to these is unclear.",
  "mo": 1,
  "mon": "Single revision dated 2025-11-03 with no observable community engagement, WG discussion, or implementation feedback; appears dormant or very early stage.",
  "r": 3,
  "rn": "Partially relevant to AI agent governance and policy enforcement; directly addresses automation control but lacks explicit AI agent framing and technical depth around agent-specific scenarios.",
  "c": ["Policy/governance", "Agent identity/auth", "ML traffic mgmt"],
  "issues": ["Critical: [CORE-SPEC] reference undefined", "Missing: normative/informative distinction", "Missing: concrete examples and deployment scenarios", "Missing: relationship to existing standards (robots.txt, HTTP semantics)"]
}
```


```json
{
  "s": "This draft extends EPP to allow registrars to submit domain pre-registration data to TLD registries for AI/ML-based quality scoring to detect potentially abusive registrations. The mechanism assigns abuse likelihood scores (0-100) and aims to improve registry integrity through proactive abuse mitigation.",
  "n": 2,
  "nn": "Incremental extension applying existing ML abuse-detection concepts to EPP domain registration workflow; straightforward application of scoring mechanisms to a known problem.",
  "m": 3,
  "mn": "Defines EPP command extensions and XML schemas with data flow description, but lacks implementation examples, test vectors, error handling edge cases, and deployment guidance needed for production readiness.",
  "o": 3,
  "on": "Shares conceptual overlap with existing domain abuse detection systems and EPP extensions (DNSSEC, WHOIS privacy); the scoring methodology itself appears standard ML classification applied to registration metadata.",
  "mo": 2,
  "mon": "Single revision as of May 2024 with no visible WG adoption, community discussion, or implementation reports; no indication of registrar/registry interest or deployment momentum.",
  "r": 2,
  "rn": "Tangentially related to AI/ML agents—describes ML model application for classification but focuses on EPP protocol mechanics rather than agent autonomy, decision-making, or agent coordination in domain management.",
  "c": [
    "Data formats/interop",
    "Policy/governance",
    "ML traffic mgmt"
  ]
}
```


```json
{
  "s": "Proposes a five-layer framework (identity, authorization, attestation, evidence, trust) for autonomous AI agents to establish provenance and trust on the Internet, addressing gaps where current protocols designed for human users fail to answer which agent acted, whether it was authorized, and whether evidence is verifiable. Informational document providing conceptual structure and common vocabulary rather than defining specific protocols.",
  "n": 3,
  "nn": "Useful contribution that synthesizes existing concepts into a coherent framework; layered model provides helpful conceptual separation but draws heavily from established identity/PKI/audit traditions applied to new domain.",
  "m": 2,
  "mn": "Early-stage framework document lacking protocol specifications, implementation details, test vectors, or concrete instantiation mechanisms; references other drafts but does not provide sufficient detail for implementation guidance.",
  "o": 3,
  "on": "Shares significant conceptual overlap with existing identity frameworks (OAUTH2, SAML, PKI), authorization models (ABAC, RBAC), and attestation work (TPM, remote attestation); positioning relative to these could be clearer.",
  "mo": 2,
  "mon": "Single dated revision (2026-04-06); unclear WG sponsorship or community adoption signals; informational status suggests lower priority than Standards Track work.",
  "r": 5,
  "rn": "Directly addresses core gap in agent identity and trust—highly relevant to autonomous agent deployment, regulatory compliance, and emerging AI system integration with Internet infrastructure.",
  "c": [
    "Agent identity/auth",
    "AI safety/alignment",
    "Policy/governance",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "ARKG enables delegation of public key generation without private key access, supporting applications like pseudonymous key generation and ephemeral key creation. The draft provides abstract algorithm specification with concrete instantiations and primitive formulae for cryptographic implementations.",
  "n": 3,
  "nn": "Useful contribution combining existing cryptographic concepts (key delegation, derived keys) into a formalized framework, but builds incrementally on established asymmetric key techniques.",
  "m": 4,
  "mn": "Well-specified protocol with concrete instances and detailed algorithm descriptions, though implementation status and test vectors not yet confirmed in abstract.",
  "o": 3,
  "on": "Shares conceptual overlap with proxy re-encryption, identity-based encryption, and delegated key derivation schemes; moderate differentiation in scope and application focus.",
  "mo": 2,
  "mon": "Draft dated 2026 suggests very recent work; single submission visible with limited evidence of WG discussion or iterative refinement.",
  "r": 2,
  "rn": "Tangentially related to AI agents through potential use in agent authentication and pseudonymous agent identity management, but primarily a cryptographic primitive specification without direct AI agent application focus.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes a JSON-based manifest format enabling websites to provide step-by-step UI workflow instructions for autonomous AI agents, reducing token consumption by 81.9% but discovering that manifest embedding alone is insufficient without a deterministic SDK runtime to bypass LLM prompt-injection defenses. The -01 update restructures the schema into a three-part model (frameworkHints, knownTraps, shortcuts) and adds AI-side curation discovery.",
  "n": 2,
  "nn": "Incremental approach combining existing ideas (JSON manifests, CSS selectors, DOM automation) with a practical discovery that LLM agents require external execution runtimes rather than in-context instruction following—useful but somewhat obvious in hindsight given LLM safety constraints.",
  "m": 2,
  "mn": "Early sketch with promising empirical results but critical unresolved gaps: the draft acknowledges manifest embedding fails in practice, requires external SDK runtime (not specified), ongoing schema evolution (-01 updates mid-cycle), and the 'fifth discovery mechanism' description is incomplete in provided text.",
  "o": 3,
  "on": "Shares conceptual overlap with existing browser automation frameworks (Selenium, Playwright), manifest-based configuration approaches, and agent instruction formats; the deterministic SDK runtime concept parallels sandboxed execution models but positioning relative to prior art is unclear.",
  "mo": 2,
  "mon": "Single major revision cycle visible (-01 at 2026-04-28, then 2026-05-15); includes significant pivot acknowledging core approach failure mid-development; no evidence of WG adoption or external implementation beyond reference implementation by authors.",
  "r": 4,
  "rn": "Directly addresses real AI agent automation challenges (token efficiency, task success, prompt injection) and focuses on practical agent-website interaction patterns; however, the core finding that manifests alone don't work diminishes relevance to the primary use case.",
  "c": [
    "Data formats/interop",
    "A2A protocols",
    "AI safety/alignment",
    "Agent discovery/reg",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes a well-known URI and link relation for exposing machine-readable descriptions of website workflows to enable automated agents to navigate sites without scraping. Minimal JSON format for declaring states, actions, and events.",
  "n": 2,
  "nn": "Incremental extension; combines existing well-known URI concept (RFC 8615) with basic state/action metadata. Similar to robots.txt or sitemap patterns but for agent workflows.",
  "m": 2,
  "mn": "Early sketch with minimal specification. Lacks concrete schema definition, examples, error handling, versioning strategy, and implementation details. No test vectors or reference implementations mentioned.",
  "o": 4,
  "on": "Significant overlap with existing standards: overlaps with OpenAPI/AsyncAPI for API workflows, Activity Streams for actions/events, and various agent protocol proposals. Relationship to these not addressed.",
  "mo": 1,
  "mon": "Single revision (2026-05-06). No evidence of WG sponsorship, community discussion, or iterative development. No implementations referenced.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent navigation and agent-website interaction. Addresses practical agent discovery/registration problem, though framed narrowly around workflows rather than broader AI agent concerns.",
  "c": [
    "Agent discovery/reg",
    "Data formats/interop",
    "A2A protocols",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "This draft proposes an IETF framework for standardizing AI Agent communications, surveying existing protocols (MCP, A2A, Agntcy) and identifying protocol requirements across agent-to-user and agent-to-resource interactions. It aims to establish foundational concepts and motivate future IETF standards work in AI agent networking.",
  "n": 2,
  "nn": "Incremental survey work that organizes existing AI agent protocol concepts into a framework; limited novel protocol contribution or architectural insight beyond consolidation of known approaches.",
  "m": 2,
  "mn": "Early-stage framework document with use cases and survey of existing work, but lacks detailed protocol specifications, formal definitions, or implementation guidance needed for standards maturity.",
  "o": 4,
  "on": "Significant conceptual overlap with MCP, A2A, and Agntcy frameworks being surveyed; framework itself adds taxonomy but doesn't introduce substantially differentiated approach to existing protocol ecosystems.",
  "r": 4,
  "rn": "Directly relevant to AI agent standardization and timely given active development in this space, though positioning relative to existing vendor-led efforts (OpenAI MCP, Anthropic) could be clearer.",
  "m": 2,
  "mon": "Single revision with no visible community consensus or WG sponsorship yet; depends entirely on whether IETF decides to pursue formal standardization work in this domain.",
  "c": [
    "Data formats/interop",
    "A2A protocols",
    "Agent discovery/reg",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "PTV proposes a hardware-anchored zero-knowledge proof protocol for agent identity attestation in federated environments, combining TPM 2.0 roots of trust with Groth16 ZK-proofs and HotStuff consensus. Targets healthcare CDSS, critical infrastructure ICS/OT, and GDPR/HIPAA compliance scenarios by enabling cross-domain authorization without raw data exposure.",
  "n": 3,
  "nn": "Combines existing components (TPM attestation, Groth16 ZKPs, HotStuff BFT) in a new federated agent identity architecture; useful synthesis addressing real data gravity concerns, but individual techniques are well-established.",
  "m": 2,
  "mn": "Early specification draft with abstract architecture described; lacks protocol message flows, concrete handshake sequences, algorithm details for proof generation/verification, and implementation evidence on target hardware platforms.",
  "o": 4,
  "on": "Significant conceptual overlap with existing TPM-based attestation (TCG standards), ZK-proof frameworks (Groth16 is standard), and BFT consensus protocols; integration approach is novel but component-level novelty is limited.",
  "mo": 1,
  "mon": "April 2026 expiration date suggests inactive or pre-publication status; single revision visible; no evidence of WG adoption, implementation attempts, or community discussion noted.",
  "r": 4,
  "rn": "Directly relevant to agent identity/authentication and authorization in autonomous systems; strong relevance to federated agent scenarios; less relevant to core AI safety/alignment questions despite agent framing.",
  "c": ["Agent identity/auth", "A2A protocols", "Policy/governance", "Data formats/interop"],
  "overall_assessment": "Addresses a real problem (federated agent identity + data privacy) with sensible technical approach, but presented at too-early maturity level for IETF standardization. Needs concrete protocol specification, implementation validation, and demonstrated adoption momentum before WG consideration."
}
```


```json
{
  "s": "Defines a standardized metadata and query profile for discovering autonomous software agents through structured capability descriptions, semantic matching, and flexible backend implementations. Aims to enable interoperable agent discovery services without mandating specific ML, embedding, or ranking technologies.",
  "n": 2,
  "nn": "Incremental contribution combining established patterns (capability metadata, semantic search, discovery protocols) with agent-specific context; similar to service discovery profiles (DNS-SD, mDNS) adapted for AI agents.",
  "m": 3,
  "mn": "Defined protocol with JSON object schemas and query/response structures, but unclear implementation maturity; lacks test vectors, reference implementations, or validation against real agent ecosystems.",
  "o": 4,
  "on": "Significant overlap with existing work: OpenAPI/AsyncAPI for agent capability description, semantic search standards (Schema.org, SKOS), and service discovery patterns. Positioning as agent-specific adaptation but core mechanisms well-established.",
  "mo": 1,
  "mon": "Single draft revision (2026-05-18), no visible WG adoption, no community discussion indicators, no implementation reports or deployment feedback documented.",
  "r": 4,
  "rn": "Directly relevant to agent ecosystem standardization; addresses real interoperability gap in agent discovery; less critical than agent identity/auth or safety concerns but operationally important.",
  "c": ["Agent discovery/reg", "Data formats/interop", "A2A protocols", "Autonomous netops"]
}
```


```json
{
  "s": "Proposes a Meta-layer as an abstract coordination substrate enabling communities and agents to share presence, annotations, and governance across platforms independent of underlying protocols. The concept is ambitious but remains largely conceptual, lacking concrete technical mechanisms and protocol specifications for practical implementation.",
  "n": 2,
  "nn": "Incremental abstraction layer concept; presence/annotation/governance are well-established problems with existing solutions (ActivityPub, RDF, policy languages). Main novelty is framing these as a unified 'meta-layer' rather than novel technical approach.",
  "m": 1,
  "mn": "Early sketch phase. Document outlines motivation and use cases but lacks protocol definition, data models, message formats, or implementation details. No test vectors, reference implementations, or deployment guidance provided.",
  "o": 4,
  "on": "Significant overlap with ActivityPub (distributed presence/federation), W3C Annotation Data Model, policy frameworks (XACML), and semantic web standards. The integration angle is somewhat novel but components are well-trodden.",
  "m": 2,
  "mon": "Single revision indicated by date; no evidence of WG support, community adoption, or active development beyond this draft. No referenced implementations or pilot deployments.",
  "r": 3,
  "rn": "Partially relevant to AI agents. Addresses agent coordination, identity, and governance which are important for multi-agent systems, but abstract framing and lack of AI-specific mechanisms limit core relevance.",
  "c": [
    "Policy/governance",
    "Agent identity/auth",
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Proposes MCP extensions enabling network equipment to function as servers for AI-driven management, defining new capability tokens, tools, resources, and error codes. Aims to bridge AI applications with network infrastructure while maintaining backward compatibility with existing MCP implementations.",
  "n": 2,
  "nn": "Incremental work adapting existing MCP standard to network management domain; straightforward extension of established protocol rather than fundamental innovation.",
  "m": 3,
  "mn": "Protocol mechanisms appear defined with capability extensions specified, but maturity hampered by April 2026 date (future publication) and typical IETF draft stage lacking implementation artifacts or interoperability testing.",
  "o": 4,
  "on": "Significant overlap with existing network management protocols (NETCONF, YANG), MCP itself, and prior work on AI-driven network operations; positioning as 'minimal extension' limits differentiation.",
  "mo": 1,
  "mon": "Single revision evident; no evidence of WG sponsorship, implementation uptake, or community discussion; future date suggests incomplete development cycle.",
  "r": 4,
  "rn": "Directly relevant to autonomous network operations and agent-infrastructure interoperability; timely given AI agent adoption, though execution-dependent on MCP ecosystem maturation.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes Agentic State Transfer (AST), an HTTP profile using semantic validators and optimistic concurrency control to maintain consistent resource state across multiple representations. Addresses synchronization gaps in multi-client environments where standard ETags fail to guarantee consistency across different serializations of the same resource.",
  "n": 2,
  "nn": "Incremental contribution combining existing HTTP concepts (content negotiation, ETags, If-Match) with a rename/reframing as 'semantic validators' and 'canonical resource state.' The core problem is real but solutions are largely recombination of established patterns.",
  "m": 3,
  "mn": "Defines a coherent protocol with stated mechanisms and requirements. However, lacks implementation details, test vectors, example payloads, and concrete validation algorithms. No reference implementation or deployment experience evident from abstract.",
  "o": 4,
  "on": "Significant overlap with existing work: PATCH RFC 5789, conditional requests RFC 7232, Linked Data conventions, and CouchDB's document versioning. The conceptual framing as 'agentic' is somewhat novel but the technical mechanisms are well-established.",
  "m": 2,
  "mon": "Single revision with future date stamp suggests hypothetical/early draft status. No evidence of WG discussion, adoption signals, or iterative refinement. Appears to be initial submission without community engagement.",
  "r": 3,
  "rn": "Partially relevant to agent systems. While framed for 'automated agents,' the actual problem (multi-representation consistency) is not inherently agent-specific—it applies equally to any distributed clients. Agent motivation seems post-hoc rather than core.",
  "c": ["Data formats/interop", "A2A protocols"]
}
```


```json
{
  "s": "This draft specifies requirements for high-performance wide area networks (HP-WAN) to support massive data transmission between data centers for big data and intelligent computing applications. It outlines network performance, reliability, and efficiency requirements without proposing specific protocols or mechanisms.",
  "n": 2,
  "nn": "Incremental requirements document for an established problem space; combines existing WAN performance concepts without novel architectural or operational approaches.",
  "m": 1,
  "mn": "Problem statement and requirements enumeration only; no protocol design, implementation framework, or technical specifications provided.",
  "o": 4,
  "on": "Significant overlap with existing WAN/datacenter networking requirements work (e.g., IETF WAN optimization, datacenter interconnect standards); limited differentiation from prior requirements documents.",
  "mo": 2,
  "mon": "Single revision dated 2025-01-03 with no visible WG sponsorship or community adoption signals; appears to be early-stage individual submission.",
  "r": 1,
  "rn": "Not relevant to AI agents; addresses general datacenter networking infrastructure requirements with no connection to autonomous agents, AI model serving, or agent protocols.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "AINS proposes a DNS-like discovery and trust resolution protocol for autonomous agents across heterogeneous networks, using HTTPS-based resolution with append-only logs for federated multi-registry deployments. The protocol maps agent identifiers to rich metadata including capabilities, trust scores, and cryptographic credentials.",
  "n": 3,
  "nn": "Useful contribution combining established patterns (DNS analogy, append-only logs, federated identity) in a new domain (agent discovery), but lacks fundamental novelty—similar federated trust models exist in PKI and blockchain systems.",
  "m": 2,
  "mn": "Early specification stage; protocol structure is defined but lacks implementation details, test vectors, security analysis, and concrete examples. References to companion protocols (TIBET, JIS, UPIP, RVP) suggest work-in-progress ecosystem without clear integration points.",
  "o": 3,
  "on": "Shares concepts with DNS, LDAP, and blockchain-based registries; trust metadata approaches overlap with X.509/PKIX and decentralized identity systems (DID); federated log architecture resembles Certificate Transparency.",
  "m": 1,
  "mon": "Single draft revision with 2026 date suggests limited community engagement or recent submission; no apparent WG adoption, citations to non-existent companion specs reduce credibility.",
  "r": 4,
  "rn": "Directly relevant to agent discovery and identity/authentication problems; moderately relevant to autonomous netops and A2A protocol infrastructure; less applicable to AI safety or model serving.",
  "c": ["Agent discovery/reg", "Agent identity/auth", "A2A protocols", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "This draft addresses the need for coordinated flow control mechanisms between Data Center Networks using PFC and Wide Area Networks using fine-grained flow control to achieve end-to-end lossless transmission. It outlines use cases and requirements for collaborative flow control across heterogeneous network domains.",
  "n": 2,
  "nn": "Incremental contribution extending existing PFC concepts to WAN domains; fine-grained flow control is a logical evolution but not fundamentally novel.",
  "m": 2,
  "mn": "Early-stage problem framing document; lacks protocol specifications, implementation details, or concrete mechanisms for DCN-WAN collaboration.",
  "o": 3,
  "on": "Builds on established PFC standards and existing fine-grained flow control research; moderate conceptual overlap with congestion management literature.",
  "mo": 1,
  "mon": "Single revision with limited community visibility; early draft stage suggests nascent effort without demonstrated WG traction or implementations.",
  "r": 2,
  "rn": "Tangentially related to agent infrastructure (network optimization); not directly about AI agents, autonomous systems, or agent protocols despite potential applications in AI workload networks.",
  "c": [
    "Autonomous netops",
    "ML traffic mgmt",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft evaluates how existing IETF YANG data models (AC, TE Topology, SR Policy, QoS) can be applied to dynamic, time-scoped UCMP policy enforcement for edge cloud AI inference workloads with periodic high-volume data exchanges. It identifies gaps in model expressiveness, policy lifecycle handling, and cloud-network coordination APIs needed for real-time network policy activation.",
  "n": 2,
  "nn": "Incremental contribution applying existing YANG models to a specific edge cloud use case; the technical novelty is limited to mapping known models to AI inference traffic patterns rather than proposing new mechanisms or architectures.",
  "m": 2,
  "mn": "Early-stage applicability study without detailed protocol specifications, implementation details, or test vectors; reads as a requirements/gap analysis document rather than a mature technical specification.",
  "o": 4,
  "on": "Significant overlap with existing IETF work on TE policies, SR policies, QoS models, and YANG data models; the use case of edge cloud coordination partially overlaps with ongoing work in CCAMP, NETMOD, and I2RS working groups.",
  "mo": 2,
  "mon": "Single dated revision (2025-12-25 appears to be a placeholder future date); no evidence of WG adoption or community momentum; appears to be exploratory work without active development cycle.",
  "r": 3,
  "rn": "Partially relevant to AI/agent topics; focuses on network infrastructure for AI inference workloads but does not address agent autonomy, decision-making, or multi-agent coordination—more about traffic management for AI services than agent-centric networking.",
  "c": ["ML traffic mgmt", "Autonomous netops", "Data formats/interop", "Policy/governance", "Model serving/inference"]
}
```


```json
{
  "s": "SLIM proposes a gRPC-based transport protocol for real-time AI agent communication, combining HTTP/2 and HTTP/3 with MLS encryption and group messaging. It aims to provide low-latency infrastructure for agent-to-agent protocols like A2A and MCP at scale.",
  "n": 2,
  "nn": "Primarily repackages existing technologies (gRPC, HTTP/2/3, MLS) for agent use cases; minimal protocol innovation beyond standard multiplexing and RPC mechanics.",
  "m": 3,
  "mn": "Defines protocol structure and mechanisms clearly but lacks implementation details, test vectors, and interoperability guidance; maturity sufficient for discussion but not deployment-ready.",
  "o": 4,
  "on": "Significant overlap with existing gRPC/HTTP/2/3 specifications, MLS work, and prior A2A drafts; primarily a bundling/application profile rather than novel composition.",
  "mo": 2,
  "mon": "Single revision as of 2026-02-24; no evidence of WG adoption, multiple iterations, or community engagement; appears early-stage.",
  "r": 4,
  "rn": "Directly addresses agent communication infrastructure, relevant to A2A and MCP ecosystems; practical relevance for distributed AI systems, though positioning over existing protocols needs stronger justification.",
  "c": ["A2A protocols", "Agent identity/auth", "Data formats/interop", "Model serving/inference"]
}
```


```json
{
  "s": "This draft proposes an inter-domain architecture for Source Address Validation (SAV) at the AS level, enabling ASes to generate accurate validation rules by sharing SAV-specific information while falling back to general information during partial deployment. The framework focuses on architectural components and information sharing rather than specific protocol designs.",
  "n": 2,
  "nn": "Incremental contribution building on existing SAVNET work; applies known SAV principles to inter-domain context with fallback mechanisms but lacks fundamental conceptual innovation.",
  "m": 3,
  "mn": "Well-structured architectural framework with defined components and information types, but remains at design/guidance level without protocol specifications, implementation details, or validation examples.",
  "o": 4,
  "on": "Significant overlap with general SAVNET architecture efforts; closely related to intra-domain SAV work and other inter-domain validation proposals; limited differentiation in core concepts.",
  "mo": 3,
  "mon": "Part of active SAVNET WG work with incremental revisions, indicating steady engagement but not exceptional adoption momentum or breakthrough interest signals.",
  "r": 1,
  "rn": "Source Address Validation is a network security mechanism unrelated to AI agents, autonomous systems in ML sense, or intelligent networked systems; false positive on AI/agent relevance.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes AgentID Protocol for establishing cryptographic identity and authorization of autonomous AI agents across internet services using JWT-based Agent Identity Tokens. Adapts OAuth 2.0/OIDC patterns to non-human actors with delegation chains and capability scoping.",
  "n": 2,
  "nn": "Incremental extension applying established identity/auth standards (JWT, OAuth 2.0, OIDC) to AI agents; core concepts are straightforward adaptations rather than novel mechanisms.",
  "m": 3,
  "mn": "Defined protocol structure with claims architecture and delegation model; lacks implementation details, test vectors, and threat analysis expected in IETF maturity.",
  "o": 4,
  "on": "Significant overlap with service account patterns, OAuth 2.0 client credentials, mutual TLS, and emerging work on API authentication for automated systems; differentiation from existing delegation frameworks unclear.",
  "mo": 2,
  "mon": "Single draft revision; no evidence of WG adoption, implementation, or community feedback; timing (March 2026) and early-stage positioning suggest limited momentum.",
  "r": 4,
  "rn": "Directly addresses real gap in AI agent identity/authorization for autonomous systems, though framing emphasizes web API access over core AI safety/alignment concerns.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Clawdentity defines a cryptographic identity and trust protocol for AI agent-to-agent communication, combining Ed25519 identities with registry-issued credentials and WebSocket-based authenticated relay. It addresses identity verification and bilateral trust establishment for agent networks without exposing private keys or backend infrastructure.",
  "n": 2,
  "nn": "Applies established cryptographic primitives (Ed25519, proof-of-possession) to agent communication; pairing ceremonies and credential frameworks are incremental combinations of existing patterns rather than novel mechanisms.",
  "m": 3,
  "mn": "Protocol is defined with functional components and mechanisms specified, but lacks implementation details, test vectors, and worked examples needed for production deployment.",
  "o": 4,
  "on": "Substantial overlap with existing identity frameworks (SPIFFE, mTLS patterns), registry-based credential systems, and WebSocket security approaches; the agent-specific framing is the primary differentiator.",
  "mo": 2,
  "mon": "Single dated submission (2026-02-21) with no evidence of revision history, WG discussion, or adoption signals; appears to be initial draft stage.",
  "r": 4,
  "rn": "Directly relevant to agent authentication and trust establishment; addresses genuine need for agent-to-agent identity in multi-agent systems, though not focused on core AI safety or alignment concerns.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Describes networking scenarios for AI agents in enterprise and home broadband networks, distinguishing these use cases from mobile and Internet contexts. Based on reasonable assumptions given agentic services are still emerging in these deployment domains.",
  "n": 2,
  "nn": "Incremental contribution focusing on scenario documentation rather than novel technical approaches; primarily scoping existing agent concepts to specific network environments.",
  "m": 2,
  "mn": "Early-stage document presenting scenario descriptions and assumptions without detailed protocol specifications, implementation guidance, or technical mechanisms.",
  "o": 4,
  "on": "Significant overlap with broader agent networking discussions; scenarios largely extrapolate from established mobile/Internet agent concepts without differentiation.",
  "mo": 1,
  "mon": "Single revision observed; limited evidence of active development or community engagement in this specific draft line.",
  "r": 3,
  "rn": "Partially relevant to AI agent networking—addresses deployment contexts but lacks technical depth on agent-specific networking challenges, protocols, or solutions.",
  "c": [
    "Agent discovery/reg",
    "Autonomous netops",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft addresses how to configure networks and systems to deploy AI inference services across distributed edge and cloud infrastructure. It covers system architecture considerations for running AI on commodity hardware and provides use cases like autonomous vehicles and digital twins.",
  "n": 2,
  "nn": "Incremental contribution; mostly documenting known best practices for distributed AI deployment rather than proposing novel technical solutions.",
  "m": 2,
  "mn": "Early sketch stage; outlines considerations and use cases but lacks detailed protocols, specifications, or implementation guidance needed for operational deployment.",
  "o": 4,
  "on": "Significant overlap with existing literature on edge computing, ML system design, and distributed inference; does not clearly differentiate from prior work or standards.",
  "mo": 1,
  "mon": "Limited momentum indicators; single revision, unclear WG support, and positioning as informational material rather than solving specific standards gaps.",
  "r": 3,
  "rn": "Partially relevant; addresses AI service deployment infrastructure but focuses on networking/system concerns rather than AI agents, autonomy, or intelligence aspects.",
  "c": ["Model serving/inference", "ML traffic mgmt", "Other AI/agent"]
}
```


```json
{
  "s": "DAAP v2.0 proposes a protocol framework combining cryptographic identity verification, real-time monitoring, and remote control mechanisms for autonomous AI agents. It addresses AI safety concerns through multi-layered security including hardware backing, periodic check-ins, and behavioral monitoring to enable accountability and regulatory compliance.",
  "n": 2,
  "nn": "Combines existing security patterns (attestation, monitoring, shutdown capabilities) into an AI-specific protocol; incremental extension of established distributed systems accountability approaches rather than fundamentally novel mechanisms.",
  "m": 3,
  "mn": "Protocol structure and primary mechanisms are defined with clear conceptual components (identity verification, check-ins, shutdown, location reporting), but lacks detailed cryptographic specifications, message formats, or implementation examples.",
  "o": 4,
  "on": "Substantial overlap with existing agent control frameworks, container orchestration security models, and IoT device management protocols; similar monitoring/attestation concepts appear in TPM-based systems and automated incident response platforms.",
  "mo": 1,
  "mon": "Single draft submission with 2026 date; no evidence of WG discussion, multiple iterations, or community engagement; appears to be initial proposal without follow-up activity.",
  "r": 4,
  "rn": "Directly addresses critical AI agent governance and safety concerns highly relevant to IETF scope; timely given regulatory focus on AI accountability and autonomous system control, though framing emphasizes governance over technical protocol depth.",
  "c": [
    "Agent identity/auth",
    "AI safety/alignment",
    "Policy/governance",
    "A2A protocols",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft specifies an algorithm for determining the effective media type of HTTP responses by considering both Content-Type headers and response content, addressing the practical problem of servers sending incorrect MIME types while balancing security and compatibility. It standardizes MIME sniffing behavior across user agents to prevent content-type confusion attacks.",
  "n": 2,
  "nn": "Incremental contribution formalizing existing browser behavior; MIME sniffing has been practiced for decades, though standardization of the algorithm adds value.",
  "m": 4,
  "mn": "Well-detailed specification with clear algorithm description suitable for implementation; appears to have concrete examples and security considerations.",
  "o": 3,
  "on": "Shares conceptual overlap with existing WHATWG HTML Living Standard sniffing algorithms and prior browser implementations; addresses a known problem space rather than unique territory.",
  "mo": 3,
  "mon": "Active IETF WebSec WG adoption with recent 2024 revision indicates sustained interest, though not exceptional community momentum compared to emerging standards.",
  "r": 1,
  "rn": "Not relevant to AI agents or AI-related networking; focuses on general HTTP content-type handling for web browsers and servers, outside the AI/agent domain.",
  "c": ["Data formats/interop"]
}
```


```json
{
  "s": "ARDP provides a lightweight discovery and registration protocol for autonomous software agents in distributed environments, supporting multiple transport protocols (MCP, A2A, HTTP, gRPC) with capability advertisement and security-first design. The protocol enables stable agent identities and dynamic endpoint resolution across federated systems.",
  "n": 2,
  "nn": "Registration and discovery for agents is incremental over existing service discovery patterns (DNS-SD, mDNS, Consul); the primary novelty is agent-specific capability advertisement including protocol negotiation, but this extends rather than fundamentally reimagines existing discovery paradigms.",
  "m": 3,
  "mn": "Protocol is formally defined with specified mechanics for registration, discovery, and endpoint resolution, but at 13 pages likely lacks detailed implementation guidance, test vectors, or reference implementations needed for production deployment.",
  "o": 3,
  "on": "Shares conceptual overlap with service discovery systems (mDNS, Consul), agent frameworks (OpenAI swarms), and protocol negotiation schemes; somewhat similar to capability-based discovery in IoT protocols but tailored for agent workloads.",
  "mo": 2,
  "mon": "Single draft revision dated 2026-02-24 with no visible WG adoption, community discussion, or implementation status; early-stage effort without clear momentum or adoption signals.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent deployment and orchestration; addresses core operational need (agent identity, discovery, capability negotiation) essential for practical multi-agent systems, though not specifically about agent reasoning or safety.",
  "c": [
    "Agent discovery/reg",
    "Agent identity/auth",
    "A2A protocols",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Extends OAuth 2.0 RAR to allow clients (particularly AI agents) to request AS-attested public key certificates bound to access tokens, enabling resource servers to verify delegated claims signed by resource owners. Combines certificate binding with OAuth 2.0 to create a chain of trust for autonomous agent authorization.",
  "n": 2,
  "nn": "Incremental extension combining existing OAuth 2.0 RAR framework with certificate binding patterns; core idea of attesting user keys via AS is straightforward application of established mechanisms.",
  "m": 2,
  "mn": "Early-stage sketch (9 pages) lacking implementation details, test vectors, security proofs, and concrete protocol flow diagrams; abstract describes intent but specification maturity unclear.",
  "o": 4,
  "on": "Significant conceptual overlap with certificate-bound tokens (RFC 8705, DPoP), MTLS patterns, and existing RAR extensions; differentiation from prior work not clearly articulated.",
  "mo": 1,
  "mon": "Single revision dated 2026 with no visible WG discussion, adoption signals, or implementation reports; appears to be initial submission without community momentum.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent authorization scenarios; addresses identity/authentication challenges for AI agents acting on behalf of users, though framing could be clearer.",
  "c": ["Agent identity/auth", "A2A protocols", "Policy/governance", "Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes a framework for standardizing AI agent communications on the Internet, surveying existing protocols like MCP and A2A while identifying gaps and requirements for IETF standards work in agent interoperability.",
  "n": 2,
  "nn": "Incremental contribution—primarily a survey and taxonomy of existing work (MCP, A2A, Agntcy) rather than proposing novel architectural or protocol concepts.",
  "m": 2,
  "mn": "Early sketch stage; provides framework and use cases but lacks detailed protocol specifications, implementation guidance, or formal mechanism definitions.",
  "o": 4,
  "on": "Significant overlap with existing initiatives (MCP, A2A, Agntcy); positions itself as a meta-framework but doesn't clearly differentiate from or advance these parallel efforts.",
  "mo": 2,
  "mon": "Single revision with limited evidence of broader community momentum; positions itself as exploratory rather than driven by active WG consensus or widespread adoption.",
  "r": 4,
  "rn": "Directly relevant to AI agent standardization; addresses timely need for protocol frameworks as agent deployments increase, though scope may be too broad for focused standards work.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg",
    "Human-agent interaction",
    "Policy/governance",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "Proposes binding AI preference expressions to SIP/SDP for real-time communications, enabling endpoints and AI assistants to negotiate AI-driven processing of session metadata and media. Defines SIP headers and SDP attributes as concrete mechanisms for expressing AI requirements without disrupting existing call control.",
  "n": 2,
  "nn": "Incremental extension applying existing AIPREF vocabulary to real-time protocols; combines established concepts (SIP/SDP signaling, preference expressions) in a new domain rather than introducing fundamentally novel mechanisms.",
  "m": 3,
  "mn": "Protocol mechanisms defined with header/attribute conventions, but appears to lack implementation examples, test vectors, and validation against real deployment scenarios; suitable for early adoption but not production-ready.",
  "o": 4,
  "on": "Significant conceptual overlap with existing preference/capability negotiation frameworks in SIP (RFC 3841, 4566); builds on established SDP extension patterns; limited novelty in binding approach relative to prior work.",
  "mo": 1,
  "mon": "Single draft revision (2026-02-03), no visible WG sponsorship, no evidence of multiple revisions or community discussion; appears to be an individual submission without established momentum.",
  "r": 3,
  "rn": "Partially relevant to AI agent topics—addresses protocol interoperability and agent signaling preferences, but focuses narrowly on real-time comms rather than broader agent autonomy, safety, or governance concerns.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent identity/auth",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "Proposes Agent Internet Protocol (AIP) as a narrow-waist protocol for autonomous AI agents, analogous to IP's role in TCP/IP, using human-readable agent:// URIs for addressing and providing datagram delivery between agents. Specifies message format, addressing, protocol demultiplexing, and error handling while deferring name resolution and discovery to companion services.",
  "n": 2,
  "nn": "Applies well-established IP/TCP-IP architecture patterns to agent communication; the core innovation (URI-based agent addressing) is incremental rather than fundamentally novel.",
  "m": 3,
  "mn": "Provides defined protocol specification with message formats and processing rules, but lacks implementation details, test vectors, and validation against real-world agent deployments.",
  "o": 4,
  "on": "Significant conceptual overlap with DNS/DDNS-like resolution models and existing A2A protocols (MQTT, AMQP, gRPC); the narrow-waist positioning echoes prior work in protocol layering and service discovery.",
  "mo": 1,
  "mon": "Single draft with March 2026 date suggests very recent/upcoming work; no evidence of WG adoption, revisions, or community engagement visible.",
  "r": 4,
  "rn": "Directly addresses agent-to-agent communication infrastructure, a core concern for autonomous AI systems, though applicability depends on whether AI agents actually adopt IP-like narrow waists.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "PAP proposes a cryptographic protocol for agent-to-agent transactions with human principals at the root of trust, using hierarchical delegation via signed mandates and selective disclosure to minimize context exposure. The protocol avoids novel cryptography, centralized registries, and trusted third parties while ensuring session ephemerality.",
  "n": 2,
  "nn": "Incremental contribution combining existing cryptographic techniques (signatures, disclosure mechanisms) into a delegation framework; the core concepts (hierarchical mandates, selective disclosure) are well-established in identity and authorization domains.",
  "m": 4,
  "mn": "Detailed protocol specification at 91 pages with defined trust model, delegation semantics, and structural guarantees; appears implementation-ready but maturity depends on presence of test vectors and reference implementations (unclear from abstract).",
  "o": 4,
  "on": "Significant overlap with OAuth 2.0 delegation flows, SAML assertions, verifiable credentials frameworks, and existing zero-knowledge/selective-disclosure protocols (e.g., W3C VC); human-in-the-loop agent control is not novel.",
  "m": 2,
  "mon": "Single draft revision dated 2026-05-20 with no apparent WG adoption, community discussion, or implementation feedback; appears early-stage for IETF standardization track.",
  "r": 3,
  "rn": "Partially relevant to AI agent systems—addresses agent-to-agent authorization and human oversight, which are important for agent orchestration and control, but does not directly address AI safety, alignment, model serving, or learning-specific concerns.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Human-agent interaction",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft specifies the Arm CCA attestation token structure as a profile of the EAT standard, defining claims, serialization, and cryptographic protection for confidential compute environments. It enables trustworthiness assessment of CCA-compliant systems through standardized attestation mechanisms.",
  "n": 2,
  "nn": "Incremental contribution: applies existing EAT framework to Arm's specific CCA architecture without introducing novel attestation concepts or mechanisms.",
  "m": 4,
  "mn": "Well-detailed specification with defined token structure, claim semantics, and serialization formats suitable for implementation, though lacking test vectors and reference implementations.",
  "o": 3,
  "on": "Shares core concepts with EAT and other TEE attestation drafts (Intel SGX, AMD SEV); CCA-specific profile adds modest differentiation but follows established patterns.",
  "mo": 2,
  "mon": "Single revision as independent submission; limited WG traction indicated by non-standards-track status and Arm-vendor-specific scope.",
  "r": 2,
  "rn": "Tangentially related to AI agent systems; relevant only if agents run on CCA-protected compute or require CCA attestation for trustworthiness verification, but not core to agent protocols or AI safety.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes SIP extension enabling negotiation and transport of Model Context Protocol (MCP) for AI agent communication. Defines new option-tags, headers, and media types to integrate MCP into SIP session establishment and mid-dialog exchanges.",
  "n": 2,
  "nn": "Incremental extension combining existing protocols (SIP + MCP); straightforward mapping of MCP onto SIP offer/answer without fundamental innovation",
  "m": 3,
  "mn": "Protocol mechanisms defined (option-tags, headers, media type) but appears to lack implementation details, test vectors, interoperability examples, or handling of edge cases",
  "o": 4,
  "on": "Significant overlap with protocol bridging patterns; similar MCP integration concepts likely explored in other transport/signaling proposals; limited novelty over existing SIP extension frameworks",
  "mo": 1,
  "mon": "Single draft revision dated 2026-04-02; no evidence of WG adoption, community discussion, or iterative development momentum; appears to be exploratory submission",
  "r": 4,
  "rn": "Directly relevant to A2A protocols and agent interop; addresses agent communication infrastructure but focuses narrowly on SIP transport layer rather than broader agent capabilities",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg",
    "Model serving/inference"
  ]
}
```


```json
{
  "s": "SPT-Txn extends IETF Transaction Tokens with Capability Acquisition Tokens to enable fine-grained, auditable, policy-bound authorization across multi-organizational and agentic systems. The framework cryptographically binds capabilities to transaction contexts while propagating human-origin identity commitments and enabling offline verification.",
  "n": 3,
  "nn": "Incremental extension of RFC 9700 with capability scoping and delegation chain auditability; combines existing token concepts (bearer tokens, transaction tokens) with capability-based access control in novel transaction context.",
  "m": 3,
  "mn": "Protocol mechanism is defined with abstract framework and concepts, but lacks concrete examples, test vectors, and implementation guidance needed for specification completeness.",
  "o": 3,
  "on": "Shares conceptual overlap with capability-based security, delegated authorization (OAuth 2.0 Token Exchange), and audit trails; extends RFC 9700 directly; relates to ABAC and transaction tokens but distinct enough approach.",
  "mo": 2,
  "mon": "Single draft revision dated 2026-04-27 with no visible WG sponsorship or community discussion; appears early-stage without evidence of broader adoption momentum.",
  "r": 4,
  "rn": "Directly relevant to agent authorization and multi-agent transaction coordination; addresses human-origin commitments and delegation chains critical for agentic AI systems; less relevant to core AI/ML topics.",
  "c": ["Agent identity/auth", "Policy/governance", "A2A protocols", "Human-agent interaction"]
}
```


```json
{
  "s": "This draft explores applying existing IETF YANG data models (ACaaS and TE topology) to support dynamic AI model placement at edge cloud sites, using real-time camera feeds and network performance metrics to optimize inference location selection. It evaluates model applicability for edge AI use cases through practical mapping across network segments.",
  "n": 2,
  "nn": "Incremental application of existing YANG models to a specific edge AI use case; combines known technologies without fundamental innovation in either YANG modeling or edge AI orchestration.",
  "m": 2,
  "mn": "Early-stage applicability study without detailed protocol specifications, implementation examples, or formal gap analysis methodology; primarily a conceptual exercise.",
  "o": 4,
  "on": "Significant overlap with existing edge computing, TE, and service provisioning work; AC-as-a-Service and TE-topology models already standardized; edge AI placement addressed in multiple other contexts.",
  "mo": 1,
  "mon": "Single revision as of submission date with no apparent WG adoption; limited indication of community engagement or follow-up iterations.",
  "r": 3,
  "rn": "Partially relevant to AI infrastructure but focused narrowly on network model applicability rather than core AI agent behaviors, safety, or autonomous decision-making.",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft proposes using large language model-based AI agents to address network operations and maintenance challenges by reducing manual tasks and improving system intelligence. It identifies operational pain points and explores how AI agents can be integrated into network architectures while discussing standardization implications.",
  "n": 2,
  "nn": "Incremental application of existing LLM/agent concepts to network operations; the core ideas of using AI for automation and self-healing networks are established, though the agent-based approach adds modest novelty.",
  "m": 2,
  "mn": "Early-stage position paper identifying problems and high-level solutions; lacks concrete protocol specifications, implementation details, or deployment examples; discusses standardization needs without defining concrete mechanisms.",
  "o": 4,
  "on": "Significant overlap with existing work on AI-driven network automation, intelligent RAN management, and network digital twins; agent frameworks and LLM applications in networking are well-explored; limited differentiation from prior art.",
  "mo": 2,
  "mon": "Single dated submission (2026-04-23) with no indicated revisions; NMRG is research-oriented rather than standards-track; unclear adoption or feedback cycle; appears to be initial/exploratory contribution.",
  "r": 4,
  "rn": "Directly relevant to AI agents in networked systems; addresses autonomous network operations which is core AI agent territory; relevance to practical network challenges is clear.",
  "c": [
    "Autonomous netops",
    "Agent discovery/reg",
    "Data formats/interop",
    "Policy/governance",
    "Model serving/inference",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Draft describes use cases for high-performance wide area networks (HP-WAN) to support big data and intelligent computing applications requiring massive data transmission. Focuses on identifying scenarios where enhanced WAN performance benefits emerging data-intensive workloads across metropolitan and wide area networks.",
  "n": 2,
  "nn": "Use case documentation for WAN performance is incremental; identifies existing demands (big data, ML inference) rather than proposing novel network mechanisms or protocols.",
  "m": 2,
  "mn": "Early stage use case collection without detailed technical specifications, protocols, or implementation guidance; primarily descriptive rather than prescriptive.",
  "o": 4,
  "on": "Significant overlap with existing work on data center networking, ML traffic optimization, and WAN performance requirements already covered in related IETF and standards work.",
  "mo": 2,
  "mon": "Single draft revision with limited indication of working group traction or community engagement; appears to be foundational positioning rather than active development.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; addresses data transmission for intelligent computing but lacks specific focus on agent communication patterns, distributed agent coordination, or agent-specific networking requirements.",
  "c": ["ML traffic mgmt", "Model serving/inference", "Autonomous netops", "Policy/governance"]
}
```


```json
{
  "s": "This draft presents an ISAC use case for the GREEN Working Group, proposing a structured template for discussing how integrated sensing and communication can benefit autonomous systems and smart cities. It aims to facilitate GREEN WG discussions on ISAC's potential benefits, challenges, and requirements without presenting detailed technical specifications.",
  "n": 2,
  "nn": "Incremental application of existing ISAC concepts to a GREEN WG context; the core ISAC paradigm is established, and this work primarily contextualizes it for use case discussion rather than introducing novel sensing-communication integration approaches.",
  "m": 1,
  "mn": "Problem statement and use case framing only; the draft explicitly proposes a template for discussion and lacks protocol definitions, technical specifications, implementation details, or concrete requirements that would indicate maturity beyond early scoping.",
  "o": 4,
  "on": "Significant overlap with existing ISAC literature and emerging 6G discussions; ISAC concepts have been extensively explored in 3GPP, IEEE, and academia; this draft adds minimal novel perspective beyond standard ISAC applications.",
  "mo": 2,
  "mon": "Early-stage contribution with limited evidence of sustained momentum; appears to be single submission to GREEN WG for discussion purposes; no indication of multiple revisions, broad community engagement, or adoption trajectory.",
  "r": 2,
  "rn": "Tangentially related to AI agents; focuses on sensing and communication infrastructure rather than agent systems, decision-making, or autonomous agent coordination; relevance to AI/agent topics is indirect through autonomous systems mention only.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "SWP Core defines a slim binary framing and envelope format for agent/tool messaging with transport-independent boundaries, LEB128-based encoding, and profile-based extensibility. It includes conformance classes, test vectors, and a security binding requiring authenticated confidential channels.",
  "n": 2,
  "nn": "Incremental contribution combining established techniques (length-prefixed frames, LEB128 encoding, TLV extensions, profile dispatch) without significant novel framing concepts.",
  "m": 4,
  "mn": "Well-structured specification with defined envelope encoding (E1), conformance classes, golden vector artifacts, and spec-vector runner validation; lacks visible reference implementations or deployment evidence.",
  "o": 4,
  "on": "Significant overlap with existing binary protocols (protobuf/grpc framing patterns, CBOR/MessagePack encoding philosophies, profile-based dispatch similar to HTTP content negotiation).",
  "mo": 2,
  "mon": "Single revision dated 2026-02-20 with no evidence of working group adoption, community interest, or multiple implementation efforts.",
  "r": 4,
  "rn": "Directly relevant to agent-to-agent communication infrastructure and interoperability; focuses on foundational messaging layer rather than agent semantics or intelligence.",
  "c": ["A2A protocols", "Data formats/interop", "Agent identity/auth"]
}
```


```json
{
  "s": "This draft proposes transporting the Agent-to-Agent (A2A) protocol over MOQT (Media over QUIC Transport), leveraging MOQT's publish/subscribe model and prioritization for AI agent communication. It combines existing protocols to enable discovery, negotiation, and collaboration between agents with efficient real-time streaming.",
  "n": 2,
  "nn": "Incremental mapping of one protocol stack onto another; combines existing technologies (A2A + MOQT) without introducing novel concepts in agent communication architecture or transport optimization.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes intent but 12 pages likely lacks detailed protocol mapping, message formats, error handling, or implementation guidance needed for production use.",
  "o": 4,
  "on": "Significant overlap with existing A2A protocol specifications and MOQT media streaming work; the contribution is primarily combinatorial rather than addressing gaps in either specification.",
  "mo": 1,
  "mon": "Single draft revision dated 2026-04-23 with no apparent community engagement, WG sponsorship, or evidence of implementation interest; appears dormant.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; addresses agent communication transport but lacks focus on core agent topics like safety, discovery mechanisms, identity management, or agent-specific operational concerns.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes a networking architecture framework for AI agents in enterprise and broadband environments, defining core components and interaction patterns. Addresses how agent systems should be networked and managed at infrastructure level.",
  "n": 2,
  "nn": "Incremental framing of agent networking as architectural concern; lacks novel technical mechanisms or protocols differentiating from existing distributed systems approaches.",
  "m": 2,
  "mn": "Early-stage conceptual document (13 pages) presenting problem space and component definitions; no detailed protocols, specifications, or implementation guidance provided.",
  "o": 4,
  "on": "Significant conceptual overlap with existing distributed agent frameworks, multi-agent system architectures, and IoT/edge networking standards; positioning unclear relative to IETF work on service meshes, microservices, and device management.",
  "mo": 1,
  "mon": "Single submission with no evidence of WG adoption, community feedback iterations, or implementation deployments; appears exploratory rather than driven by operational need.",
  "r": 3,
  "rn": "Partially relevant to agent networking but framed as generic infrastructure architecture rather than addressing specific AI agent challenges like model coordination, inference load balancing, or LLM-specific requirements.",
  "c": [
    "Agent discovery/reg",
    "Autonomous netops",
    "Data formats/interop",
    "A2A protocols",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "CoSERV defines a structured query/result format for discovering and retrieving Endorsements and Reference Values in Remote Attestation systems. It uses CDDL and CBOR serialization to enable efficient interoperability across diverse attestation providers and verifiers.",
  "n": 2,
  "nn": "Incremental contribution addressing a specific gap in RATS artifact discovery; applies existing technologies (CDDL, CBOR) in domain-specific context rather than introducing novel concepts.",
  "m": 4,
  "mn": "Detailed specification with CDDL definitions and structured protocol design; appears implementation-ready though test vector coverage not evident from abstract.",
  "o": 3,
  "on": "Shares query/discovery concepts with existing artifact management and attestation frameworks; specialized enough to avoid near-duplication but builds on established patterns.",
  "mo": 3,
  "mon": "Active IETF working group (RATS) indicates ongoing development; publication date suggests current work, though WG adoption level unclear from provided metadata.",
  "r": 2,
  "rn": "Tangentially related to agent ecosystems—relevant only if agents require remote attestation verification infrastructure; not core to agent autonomy, alignment, or operation.",
  "c": ["Data formats/interop", "Agent identity/auth", "Other AI/agent"]
}
```


```json
{
  "s": "This draft establishes security requirements for intent-based agent routing, addressing risks in semantic intent matching and capability verification beyond traditional TLS/PKI protections. It defines architecture, attack surfaces, and normative protections across Registration, Resolution, and Dispatch phases.",
  "n": 3,
  "nn": "Useful contribution addressing a genuine gap—intent privacy and capability integrity in agent routing are underexplored—but builds predictably on established security frameworks applied to a new domain.",
  "m": 2,
  "mn": "Early sketch phase; establishes requirements and architecture but lacks detailed protocol specifications, cryptographic bindings, formal threat models, or implementation guidance needed for standards maturity.",
  "o": 3,
  "on": "Shares conceptual overlap with ZEROSSL/DNSSEC (intent as service metadata), OAuth2 scope binding (capability claims), and DNS privacy work; positioning relative to these is unclear.",
  "mo": 2,
  "mon": "Single revision as of April 2026; no evidence of WG adoption, community feedback integration, or competing approaches. Appears exploratory rather than solving an urgent, recognized problem.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent deployment; intent privacy and capability verification are legitimate security concerns, though 'intent-based routing' terminology and actual use cases need sharper definition.",
  "c": [
    "Agent discovery/reg",
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This document deprecates obsolete key exchange methods (finite field Diffie-Hellman and RSA) in DTLS 1.2 and discourages static ECDH, updating multiple RFCs to enforce stricter requirements for modern TLS deployments.",
  "n": 1,
  "nn": "Straightforward deprecation of well-known weak algorithms; incremental maintenance work updating existing standards rather than introducing new concepts.",
  "m": 5,
  "mn": "Comprehensive specification with detailed updates to 18 RFCs, clear MUST NOT/SHOULD NOT directives, rationale sections, and implementation guidance demonstrating high maturity.",
  "o": 5,
  "on": "Directly follows established deprecation patterns from RFC 8996 and TLS 1.3 design; minimal novel content, primarily coordinating existing security guidance across protocol versions.",
  "mo": 4,
  "mon": "Standards-track work with WG adoption addressing recognized security gaps; published in 2026 indicating active IETF TLS working group momentum on cleanup tasks.",
  "r": 1,
  "rn": "Pure cryptographic protocol standards maintenance with no connection to AI agents, autonomous systems, or machine learning infrastructure.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "JEP defines a signed JSON event format for recording immutable decision events across human, organizational, software, and autonomous agent systems using four core verbs (Judgment, Delegation, Termination, Verification). It provides cryptographic verification via JWS/JCS while explicitly deferring legal, authorization, and regulatory concerns to higher layers.",
  "n": 2,
  "nn": "Incremental combination of existing standards (JWS, JCS, event sourcing patterns); the four-verb decision model is simplistic and the protocol mostly repackages established cryptographic techniques without fundamental innovation.",
  "m": 3,
  "mn": "Protocol structure and signing mechanism are defined, but specification lacks implementation examples, test vectors, and clarity on critical semantics (e.g., how 'Judgment' differs from arbitrary signed claims, delegation revocation semantics).",
  "o": 4,
  "on": "Significant conceptual overlap with W3C Verifiable Credentials, IETF RATS attestation formats, event sourcing frameworks, and audit log protocols; the niche of 'agent decision records' is narrow and not well-differentiated from existing work.",
  "mo": 1,
  "mon": "Single draft dated 2026-05-04 with no visible WG discussion, adoption signals, or revision history; appears to be an individual submission with unclear community backing or iteration momentum.",
  "r": 3,
  "rn": "Partially relevant to autonomous agent systems (addresses agent decision logging), but scope is broader than AI agents specifically and applicability to ML/AI workflows remains underexplored; positioning as a general protocol dilutes focus on agent-specific problems.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Proposes a decoupled authorization framework for AI agents using intent-based, just-in-time permissions tied to behavioral trustworthiness rather than static identity or role. Aims to enable fine-grained access control while decoupling authorization policies from business operations.",
  "n": 2,
  "nn": "Intent-based authorization and JIT permissions are incremental extensions of existing capability-based security and dynamic access control concepts; limited novelty in core authorization mechanisms.",
  "m": 2,
  "mn": "Early-stage draft at 6 pages; presents conceptual framework and goals but lacks detailed protocol specification, implementation details, or concrete mechanisms for intent verification and trust assessment.",
  "o": 3,
  "on": "Shares foundational concepts with OAuth 2.0 dynamic client registration, ABAC (attribute-based access control), and capability-based security models; some overlap with emerging agent authorization discussions.",
  "mo": 1,
  "mon": "Single revision from February 2026 with no evidence of WG adoption, prior versions, or community feedback; appears to be nascent proposal without established momentum.",
  "r": 4,
  "rn": "Directly relevant to agent authorization and governance; timely given increasing deployment of autonomous agents, though framed more as policy/governance than core A2A protocol work.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "AI safety/alignment",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "This problem statement argues that AI agents require dedicated network-layer infrastructure beyond current HTTP-based application protocols, proposing the need for agent-specific identity, addressing, and transport mechanisms independent of web infrastructure.",
  "n": 3,
  "nn": "Frames agent communication as a network infrastructure gap rather than application-layer problem; usefulness depends on whether network-layer separation proves necessary versus application-layer solutions.",
  "m": 1,
  "mn": "Pure problem statement with no protocol design, mechanisms, or implementation details provided; early-stage work identifying requirements rather than solutions.",
  "o": 3,
  "on": "Overlaps conceptually with service mesh architectures, microservice networking, and IoT protocols; agent discovery/registry concepts exist in other domains but application to autonomous agents is distinct.",
  "mo": 2,
  "mon": "Appears to be initial draft (dated 2026-04) with unclear WG backing or subsequent revisions; limited evidence of community adoption or discussion.",
  "r": 4,
  "rn": "Directly addresses autonomous agent networking requirements; relevant for agent infrastructure but framed narrowly around network layer rather than broader AI agent ecosystem concerns.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Agent discovery/reg",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Proposes decentralized RPKI repository architecture (dRR) with distributed certificate servers and monitors to address reliability and scalability issues in current RPKI systems while maintaining compatibility with existing trust models.",
  "n": 3,
  "nn": "Useful architectural contribution that decouples signing from management authority in RPKI, but builds incrementally on existing RPKI concepts without fundamentally novel cryptographic or distributed systems innovations.",
  "m": 2,
  "mn": "Early sketch stage; presents architecture concepts and addresses problems but lacks detailed protocol specifications, implementation examples, test vectors, and validation procedures needed for production deployment.",
  "o": 3,
  "on": "Shares core concepts with existing RPKI improvement proposals and distributed repository work; the decentralization pattern is not unique though application to RPKI repositories is relatively focused.",
  "mo": 2,
  "mon": "Single revision dated 2026-01-06 with no evidence of WG adoption, community discussion, or implementation efforts; appears to be initial proposal without demonstrated momentum.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; purely focused on internet routing security infrastructure (RPKI). False positive for AI/agent-related topics.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes HTTP 427 status code and Budget authentication scheme for authorizing software agents to spend resources, separating credential validation from budget authorization concerns using post-quantum cryptography. Addresses a real gap in HTTP semantics for agent-driven spending but introduces significant complexity through CBOR envelopes and dual-signature schemes.",
  "n": 2,
  "nn": "Incremental addition to HTTP status codes and auth schemes; combines existing concepts (budget tracking, post-quantum signatures, CBOR) without fundamental novelty in agent authorization models.",
  "m": 3,
  "mn": "Protocol mechanism is defined with signature algorithms and version negotiation specified, but lacks implementation examples, test vectors, and practical deployment guidance for the CBOR attestation envelope.",
  "o": 3,
  "on": "Shares conceptual space with OAuth 2.0 scope limitations, payment authorization protocols, and post-quantum signature standardization; the budget-as-orthogonal-axis framing is somewhat novel but not entirely distinct from existing capability-based frameworks.",
  "mo": 1,
  "mon": "Single revision dated 2026 with no apparent WG adoption, predecessor revisions, or community discussion visible; appears to be nascent work without demonstrated traction.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent authorization and resource control; addresses practical needs for AI agent deployment in financial/metered contexts, though framing is HTTP-infrastructure-focused rather than AI-safety-focused.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "ML traffic mgmt",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "EAR defines a standardized message format for encoding attestation appraisal results, embedding trustworthiness vectors and contextual information to support authorization decisions. It handles both simple and composite devices with attesters, serializable via CWT or JWT.",
  "n": 2,
  "nn": "Incremental formalization of attestation result representation; builds on established EAT and AR4SI concepts without fundamental innovation",
  "m": 4,
  "mn": "Well-specified protocol with detailed message format definitions, though limited implementation evidence and test vectors in the abstract",
  "o": 3,
  "on": "Shares significant overlap with AR4SI trustworthiness vectors and existing attestation frameworks; EAT integration is natural but not novel",
  "mo": 3,
  "mon": "Active RATS WG participation suggests moderate momentum; extends established IETF attestation work but lacks broad ecosystem adoption signals",
  "r": 2,
  "rn": "Tangentially related to AI agents only through device attestation and trust establishment; primarily focused on hardware/firmware verification rather than AI systems or autonomous agents",
  "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance", "Other AI/agent"]
}
```


```json
{
  "s": "Proposes using Model Context Protocol (MCP) to enable AI-assisted network measurement by treating devices as MCP servers and controllers as clients. Framework aims to provide natural language-driven operations for monitoring, fault diagnosis, and topology discovery with standardized communication.",
  "n": 2,
  "nn": "Incremental application of existing MCP standard to network measurement domain; combines known concepts (LLM-driven network ops, standardized protocols) without fundamental innovation in measurement techniques or MCP itself.",
  "m": 2,
  "mn": "Early-stage sketch with architecture and use cases described at high level; lacks protocol specifications, detailed message formats, implementation details, security mechanism definitions, or concrete examples. 10 pages insufficient for specification maturity.",
  "o": 4,
  "on": "Significant conceptual overlap with LLM-based network automation work and existing network measurement standards (YANG, NETCONF, gRPC). MCP application to network domains is emerging across multiple drafts; positioning relative to competitors unclear.",
  "mo": 1,
  "mon": "Single revision apparent; no evidence of WG adoption, community discussion, or implementation activity. No indication of follow-up versions or broader momentum in standardization pipeline.",
  "r": 4,
  "rn": "Directly relevant as application of AI agents (LLM-driven via MCP) to autonomous network operations. Core focus on natural language interface and intelligent automation aligns with AI agent frameworks, though implementation details remain vague.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Data formats/interop",
    "Human-agent interaction",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes an OAuth 2.1 extension enabling AI agents with persistent identities to request user consent and obtain access tokens through polling, SSE, or WebSocket mechanisms. Adapts the Device Authorization Grant pattern for agent-specific needs including natural-language scopes and reason parameters.",
  "n": 2,
  "nn": "Incremental extension of RFC 8628; core innovation (polling/SSE/WebSocket for agents) is straightforward adaptation rather than fundamental breakthrough",
  "m": 2,
  "mn": "Early-stage sketch with abstract-level protocol description; lacks detailed message flows, security analysis, implementation guidance, and test vectors needed for standardization",
  "o": 4,
  "on": "Significant conceptual overlap with Device Authorization Grant; natural-language descriptions loosely related to scope negotiation patterns in other drafts; limited differentiation from existing consent mechanisms",
  "mo": 1,
  "mon": "Single 6-page revision from May 2025 with no visible WG engagement, community discussion, or development activity indicating sustained momentum",
  "r": 4,
  "rn": "Directly addresses agent authorization and identity management, core concerns for autonomous AI systems; however, scope limited to OAuth extension rather than broader agent governance",
  "c": ["Agent identity/auth", "A2A protocols", "Human-agent interaction", "Policy/governance"]
}
```


```json
{
  "s": "Proposes an Agent Communication Gateway (Agent-GW) infrastructure hub enabling semantic routing, shared working memory, and protocol adaptation for heterogeneous multi-agent collaboration. Introduces concepts of intent-based interaction, knowledge delivery networks, and oracle-free agent evaluation to support large-scale agent systems across administrative boundaries.",
  "n": 3,
  "nn": "Combines existing concepts (message routing, context management, protocol translation) in a multi-agent context with some novel framing around semantic routing and working memory primitives; useful contribution but not groundbreaking.",
  "m": 2,
  "mn": "Early architectural sketch with conceptual framework; lacks detailed protocol specifications, formal definitions, implementation examples, or test vectors needed for standardization track.",
  "o": 3,
  "on": "Shares significant conceptual overlap with agent middleware (e.g., OpenAI Swarm), pub/sub routing systems, and knowledge graph architectures; semantic routing relates to intent-based networking but applies to agents rather than packets.",
  "mo": 2,
  "mon": "Single submission dated 2026-03-04 with no visible revision history or community engagement; no evidence of WG interest, implementations, or active development beyond initial draft.",
  "r": 4,
  "rn": "Directly addresses core multi-agent infrastructure challenges (heterogeneity, protocol translation, shared context, capability discovery) central to contemporary AI agent deployment; highly relevant to the agent coordination problem space.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Model serving/inference",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft defines identity management mechanisms for agents in an Internet of Agents (IOA) system, including agent identity descriptors, registration processes, identifier assignment, and gateway-based identity functions. It establishes foundational infrastructure for agent identification and lifecycle management within a multi-agent network architecture.",
  "n": 2,
  "nn": "Incremental contribution applying established identity management principles to a new agent-centric domain; lacks novel architectural insights.",
  "m": 3,
  "mn": "Defines core protocol mechanisms and agent identity structures with reasonable specification detail, though implementation readiness and validation examples appear limited.",
  "o": 4,
  "on": "Significant overlap with existing identity/authentication standards (X.509, OAuth 2.0 patterns) and agent discovery RFCs; primarily repurposes established concepts for agent context.",
  "mo": 2,
  "mon": "Single revision draft with limited evidence of WG adoption, community discussion, or iterative refinement; unclear stakeholder momentum.",
  "r": 4,
  "rn": "Directly relevant to agent infrastructure and multi-agent system coordination; identity management is essential for IOA but foundational rather than cutting-edge.",
  "c": ["Agent identity/auth", "Agent discovery/reg", "A2A protocols", "Data formats/interop", "Autonomous netops"]
}
```


```json
{
  "s": "This draft proposes extending SRv6 with new segment identifiers (SIDs) to enable flow control and congestion notification in wide area networks supporting RDMA and AI workloads. It leverages the explicit path information in SRv6 segment lists to identify upstream nodes and deliver PFC-style backpressure signals across distributed data center scenarios.",
  "n": 2,
  "nn": "Straightforward application of existing SRv6 mechanisms to WAN congestion control; the core idea of mapping PFC into SRv6 behaviors is incremental rather than architecturally novel.",
  "m": 2,
  "mn": "Early sketch phase; abstract describes use cases and high-level approach but lacks protocol details, packet format specifications, behavior definitions, examples, or implementation considerations needed for a complete spec.",
  "o": 4,
  "on": "Significant overlap with existing SRv6 congestion and QoS work; PFC mechanisms are well-established in data center networking; the combination is a relatively straightforward engineering effort rather than addressing new gaps.",
  "mo": 1,
  "mon": "Single revision dated 2026-02-27 with no visible community discussion, WG adoption, or prior versions; no evidence of working group interest or implementation efforts.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; addresses ML/AI distributed training and inference traffic management in WANs, but focuses on network transport optimization rather than agent behavior, autonomy, or decision-making.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft proposes an agent networking architecture for digital banking scenarios, centered on an 'agent gateway' component to facilitate agentic service interconnection as banking digitalization evolves.",
  "n": 2,
  "nn": "Applies existing gateway/orchestration concepts to banking agents; lacks novel architectural insights or technical contributions beyond standard service integration patterns.",
  "m": 1,
  "mn": "Presents scenario descriptions and high-level architecture proposal only; no protocol specification, detailed mechanisms, implementation details, or validation provided.",
  "o": 4,
  "on": "Significant overlap with existing service mesh, API gateway, and microservices orchestration literature; agent gateway concept lacks differentiation from current architectural patterns.",
  "mo": 1,
  "mon": "Single revision observed; no evidence of WG engagement, community adoption, or iterative refinement; appears exploratory rather than actively developed.",
  "r": 2,
  "rn": "Tangentially related to AI agents; focuses on banking digitalization scenarios rather than core agent networking protocols, autonomy mechanisms, or agent-specific challenges.",
  "c": [
    "Agent discovery/reg",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Proposes a SCIM 2.0 extension to manage agents and agentic applications across identity domains by extending User/Group schemas and introducing new agent-specific resource types. Aims to reduce protocol proliferation by leveraging existing SCIM infrastructure for agent identity and interoperability.",
  "n": 2,
  "nn": "Incremental extension applying well-established identity management patterns to emerging agent use cases; lacks novel architectural or conceptual contributions beyond schema adaptation.",
  "m": 2,
  "mn": "Early-stage draft with abstract-level description; no detailed schemas, examples, or implementation guidance evident; insufficient specificity for deployment.",
  "o": 4,
  "on": "Significant conceptual overlap with agent frameworks (e.g., OpenAI's agents, LangChain identity concepts) and existing identity federation approaches; extends rather than reimagines SCIM.",
  "mo": 1,
  "mon": "Single draft revision as of April 2026 with no evidence of WG sponsorship, implementation feedback, or community adoption; unclear author engagement.",
  "r": 3,
  "rn": "Partially relevant to agent ecosystems—directly addresses agent identity and cross-domain management but focuses narrowly on identity provisioning rather than broader agent orchestration, safety, or capability management.",
  "c": ["Agent identity/auth", "Data formats/interop", "Agent discovery/reg", "A2A protocols"]
}
```


```json
{
  "s": "FAF proposes a YAML-based format for encoding software project context consumable by AI development tools, aiming to standardize information sharing across multi-agent environments. It addresses context fragmentation by providing a structured representation of architecture, conventions, dependencies, and goals.",
  "n": 2,
  "nn": "Incremental contribution—applying existing YAML structuring to a new domain (AI agent context). The concept of context sharing for agents is known; this draft formalizes one serialization approach without algorithmic or architectural innovation.",
  "m": 3,
  "mn": "Defined protocol with partial specification maturity. Document establishes a format structure and has IANA registration, but lacks detailed examples, validation rules, extensibility mechanisms, and implementation guidance needed for full readiness.",
  "o": 4,
  "on": "Significant overlap exists with project metadata standards (package.json, pyproject.toml, .editorconfig) and broader ML/AI context representation efforts. The novelty over existing config formats is minimal; no clear advantage over structured alternatives is demonstrated.",
  "mo": 2,
  "mon": "Single revision status with October 2025 IANA registration suggests recent activity, but limited evidence of WG engagement, implementation adoption, or community feedback. No evidence of competing implementations or production deployments.",
  "r": 4,
  "rn": "Directly relevant to AI agent interoperability and multi-agent coordination problems. Addresses real friction points in LLM-assisted development, though positioned as tooling infrastructure rather than core agent protocol.",
  "c": ["Data formats/interop", "Agent discovery/reg", "A2A protocols", "Human-agent interaction"]
}
```


```json
{
  "s": "RMRP proposes a standardized protocol layer for routing inference requests across heterogeneous AI model deployments with policy governance and audit trails. The framework aims to provide vendor-agnostic, provider-independent mechanisms for declaring routing decisions, enforcing policies, and maintaining accountability in multi-model environments.",
  "n": 2,
  "nn": "Incremental contribution applying established routing and policy concepts to AI inference contexts; borrows heavily from network routing protocols and policy frameworks without introducing fundamentally new routing or governance paradigms.",
  "m": 3,
  "mn": "Defines protocol structures, policy semantics, and audit requirements with reasonable specification detail, but unclear implementation status, lacking concrete code examples, test vectors, or validation data from real deployments.",
  "o": 4,
  "on": "Significant conceptual overlap with existing work in service mesh routing (Istio), API gateway policies, and ML model serving frameworks (KServe, Seldon); reinvents established patterns for a specialized domain without clearly differentiating RMRP's novel contribution.",
  "mo": 1,
  "mon": "Single draft publication with April 2026 date (future); no evidence of revisions, WG sponsorship, implementation prototypes, or community adoption; appears to be initial submission without demonstrated momentum.",
  "r": 4,
  "rn": "Directly relevant to AI model serving and inference governance; addresses real operational challenges in multi-model deployments, though framed more as infrastructure management than as core AI agent coordination protocol.",
  "c": [
    "ML traffic mgmt",
    "Model serving/inference",
    "Policy/governance",
    "Data formats/interop",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "This draft proposes intent-based network management as a use case for autonomous networks, presenting an architecture with five levels of automation to reduce operational complexity. It addresses full lifecycle network management through intent-driven approaches but lacks detailed protocol specifications or implementation details.",
  "n": 2,
  "nn": "Incremental contribution that applies existing intent-based networking concepts to management scenarios; the five-level autonomy framework is somewhat derivative of established automation maturity models.",
  "m": 2,
  "mn": "Early-stage sketch with architectural overview but minimal technical depth; lacks protocol definitions, formal specifications, data models, or implementation examples needed for practical deployment.",
  "o": 4,
  "on": "Significant overlap with existing IBN/intent-based networking literature and IETF work on network autonomy; closely parallels concepts in IETF NMRG and related autonomic networking efforts without clear differentiation.",
  "mo": 1,
  "mon": "Single revision with limited evidence of active development or community engagement; no substantial follow-up activity or adoption signals visible in IETF ecosystem.",
  "r": 3,
  "rn": "Partially relevant to autonomous network operations through intent-driven management; tangentially touches on autonomous systems but does not directly address AI agents, ML models, or agent-specific protocols.",
  "c": [
    "Autonomous netops",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "CoSERV defines a CBOR-serializable query language and result format for discovering and retrieving Endorsements and Reference Values in RATS attestation workflows. It provides structured interoperability across diverse attestation providers using CDDL specifications.",
  "n": 2,
  "nn": "Incremental contribution applying existing standards (CBOR, CDDL) to a specific gap in RATS artifact discovery; the core innovation is mainly format/protocol selection rather than novel architectural concepts.",
  "m": 4,
  "mn": "Well-specified protocol with formal grammar (CDDL), serialization format defined, and structured query/result mechanisms; lacks implementation examples and test vectors for full readiness.",
  "o": 2,
  "on": "Minor overlap with existing RATS work and general data format specifications; primarily novel in its specific application as a selector/discovery mechanism for endorsements and reference values.",
  "mo": 2,
  "mon": "Single draft revision dated 2025-08-12 with no visible community adoption or WG backing; limited indicators of ongoing development momentum.",
  "r": 2,
  "rn": "Tangentially related to agent systems through attestation and identity mechanisms, but focused on remote attestation infrastructure rather than AI agents, autonomous systems, or agent interoperability directly.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "This draft identifies the need for agent-to-agent discovery mechanisms as AI agents proliferate in networked environments. It presents requirements and considerations for enabling agents to find and communicate with each other, addressing an emerging gap in agent infrastructure.",
  "n": 2,
  "nn": "Incremental problem framing; agent discovery parallels existing service discovery patterns (DNS-SD, mDNS) adapted to AI contexts, lacking novel conceptual contributions.",
  "m": 1,
  "mn": "Pure problem statement document with no protocol design, mechanism specification, or concrete technical solutions proposed; foundational stage only.",
  "o": 4,
  "on": "Significant overlap with established service discovery literature (RFC 6763, RFC 6762) and existing IoT/edge computing discovery frameworks; AI-specific dimensions not clearly differentiated.",
  "mo": 2,
  "mon": "Single revision noted with October 2025 timestamp; no evidence of WG adoption, community discussion, or iterative development cycle.",
  "r": 4,
  "rn": "Directly addresses emerging AI agent infrastructure needs; highly relevant to autonomous systems and agent ecosystems, though execution specificity remains limited.",
  "c": [
    "Agent discovery/reg",
    "A2A protocols",
    "Data formats/interop",
    "Agent identity/auth",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "Proposes a 'reason://' URI scheme and registry protocol for storing and retrieving compressed reasoning artifacts from distributed autonomous agent networks, with artifacts validated through competitive arbitration and mathematical non-invertibility guarantees. Positions itself as foundational infrastructure for agent-to-agent communication analogous to DNS or HTTP.",
  "n": 2,
  "nn": "Incremental application of existing URI/registry patterns to agent reasoning; core concepts (URIs, registries, distributed lookup) are well-established, though application domain is relatively novel",
  "m": 2,
  "mn": "Early sketch stage; abstract mentions protocol elements (WARF arbitration, mathematical properties) but lacks concrete specifications, schema definitions, message formats, or protocol flows necessary for implementation",
  "o": 4,
  "on": "Significant conceptual overlap with existing agent discovery/registry systems, DNS-like distributed naming schemes, and content-addressed storage (IPFS-style); competitive validation mechanism is less common but not unprecedented",
  "mo": 1,
  "mon": "Single dated revision (2026-03-30) with no evidence of community engagement, WG adoption, or iterative development; appears to be first-draft submission with minimal external momentum",
  "r": 3,
  "rn": "Directly addresses agent infrastructure needs but focuses narrowly on artifact storage/retrieval; relevance depends heavily on whether agent networks actually require this specific mechanism versus existing solutions",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "VCAP proposes a cryptographic settlement layer enabling autonomous AI agents to transact with verifiable proof-of-work delivery and escrow mechanisms. It complements agent discovery and communication protocols by adding payment verification and dispute resolution between agents in marketplace scenarios.",
  "n": 4,
  "nn": "Novel application of verifiable computation to agent payments; combines escrow patterns with cryptographic proof requirements in agent context, though builds on established blockchain/payment verification concepts.",
  "m": 2,
  "mn": "Early sketch of message formats and state machines; lacks implementation details, test vectors, and concrete verification engine specifications despite claiming protocol definition.",
  "o": 3,
  "on": "Shares significant concepts with smart contract payment channels, blockchain settlement layers, and verifiable computation frameworks; moderate overlap with existing escrow/dispute resolution patterns.",
  "mo": 1,
  "mon": "Single revision dated 2026-03-24 with no evidence of WG discussion, community adoption, or iterative development; appears to be initial submission.",
  "r": 5,
  "rn": "Directly addresses core infrastructure need for autonomous agent economies; highly relevant to emerging multi-agent systems requiring trustless payment settlement.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes using multicast networking for synchronizing Large Language Model inference services in cloud deployments. It explores how multicast protocols could optimize LLM model distribution and inference traffic patterns across distributed inference infrastructure.",
  "n": 2,
  "nn": "Applying existing multicast concepts to LLM inference is incremental; multicast for distributed systems is well-established, and LLM-specific considerations appear limited.",
  "m": 2,
  "mn": "Early-stage use case document (6 pages) with abstract concepts; lacks protocol specifications, architectural details, implementation examples, or concrete technical mechanisms.",
  "o": 4,
  "on": "Significant conceptual overlap with existing multicast RFCs (RFC 7761, RFC 5015), distributed ML inference frameworks, and general cloud service synchronization approaches; limited differentiation.",
  "mo": 1,
  "mon": "Single revision with no apparent WG adoption, community discussion, or implementation activity evident; positioning as 2026 draft suggests early/speculative stage.",
  "r": 3,
  "rn": "Partially relevant to AI systems; focuses on networking infrastructure for LLM deployment rather than AI agent capabilities, autonomy, safety, or core AI/agent behavior.",
  "c": ["ML traffic mgmt", "Model serving/inference", "Data formats/interop"],
  "overall_assessment": "Exploratory networking document with limited novelty and maturity; needs substantial development of LLM-specific multicast use cases, technical specifications, and evidence of routing WG interest to be viable."
}
```