```json
{
  "s": "Proposes best practices for web crawlers, likely addressing modern crawler behavior and responsible crawling standards. Early-stage document focused on establishing guidelines for crawler operators in the context of AI and automated agents.",
  "n": 2,
  "nn": "Incremental work building on existing robots.txt and crawling conventions; limited novel technical contribution evident from abstract",
  "m": 2,
  "mn": "Early sketch stage with 6-page limit; abstract mentions best practices but lacks specifics on mechanisms, protocols, or implementation details",
  "o": 4,
  "on": "Significant overlap with existing standards (robots.txt, User-Agent conventions, Crawl-delay) and prior IETF work on web crawling; borrows established practices rather than proposing novel approaches",
  "mo": 2,
  "mon": "Single revision visible; hosted on GitHub but limited evidence of broad working group engagement or community momentum beyond individual author contribution",
  "r": 3,
  "rn": "Partially relevant to AI agent topic—addresses crawler behavior which relates to autonomous agents and data collection, but framed as general web crawler practices rather than AI-specific agent governance",
  "c": [
    "Policy/governance",
    "Agent discovery/reg",
    "Data formats/interop",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "This draft proposes a protocol for efficiently distributing LLM key-value caches across distributed nodes using MoQT's publish-subscribe transport, enabling cache reuse to reduce bandwidth and prefill computation costs. The approach leverages local caching at network edges to optimize large language model inference performance.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (MoQT pub/sub + KVCache distribution); the technical novelty is limited to applying a known transport mechanism to a specific ML inference optimization problem.",
  "m": 2,
  "mn": "Early-stage sketch with conceptual framing but minimal protocol details; lacks formal specification, message formats, serialization details, or concrete implementation guidance for 6-page draft length.",
  "o": 3,
  "on": "Shares foundational concepts with distributed ML inference systems and edge caching literature; MoQT itself is established; moderate overlap with general cache distribution patterns but specific KVCache+MoQT binding is relatively novel.",
  "mo": 2,
  "mon": "Single/early revision evident; limited evidence of WG traction or broader community engagement; appears to be exploratory work without established momentum in IETF or MoQ communities.",
  "r": 4,
  "rn": "Directly relevant to model serving/inference optimization and ML traffic management; addresses practical distributed inference challenges; less relevant to broader AI agent topics but solid relevance to AI infrastructure.",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "AIP proposes a decentralized identity framework for AI agents using DIDs, capability-based authorization, and cryptographic delegation. It aims to enable secure multi-agent workflows without centralized providers.",
  "n": 3,
  "nn": "Useful combination of existing standards (W3C DIDs, capability-based auth) applied to AI agents, but delegation and identity for autonomous agents is an emerging design space with limited prior standardization.",
  "m": 2,
  "mn": "Early sketch stage; abstract indicates framework design but 225 pages suggests incomplete specification; likely lacks implementation details, test vectors, or reference implementations needed for maturity.",
  "o": 3,
  "on": "Shares core concepts with DID specs, CHAPI, ZCAP-LD, and agent authorization work; represents useful combination but not orthogonal to multiple existing IETF/W3C efforts in identity and delegation.",
  "mo": 1,
  "mon": "2026 date indicates future draft with no current revision history visible; single appearance suggests early-stage work without evident WG adoption or community engagement.",
  "r": 4,
  "rn": "Directly addresses agent identity and authorization—core infrastructure need for autonomous AI agent deployment—though framed more as identity infrastructure than AI-specific capabilities.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "ATTP proposes a trust-scoring framework for autonomous AI agents with cryptographic identity, action limits, and compliance gating across multiple transport protocols. It separates trust evaluation from identity verification to enable fine-grained authorization control for agent actions.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (trust scoring, ECDSA identity, compliance gating) applied to agent context; no fundamentally novel technical mechanisms but reasonable engineering synthesis for emerging use case.",
  "m": 3,
  "mn": "Defined protocol framework with five trust levels and behavioral dimensions, but lacks implementation details, test vectors, and concrete examples; transport bindings (MCPS, REST, gRPC) mentioned but not specified in this draft.",
  "o": 4,
  "on": "Significant conceptual overlap with OAuth 2.0 scopes/capabilities, NIST AI RMF trust assessment, policy-based access control, and existing compliance frameworks; trust scoring echoes established risk models; novelty is mainly in agent-specific packaging.",
  "mo": 2,
  "mon": "Single revision as of April 2026; no evident WG adoption, community discussion, or implementation feedback; appears exploratory rather than driven by active deployment needs.",
  "r": 5,
  "rn": "Directly addresses core AI agent governance challenge—authorization and trust in autonomous systems—highly timely given LLM agent proliferation and regulatory pressure.",
  "c": [
    "Agent identity/auth",
    "AI safety/alignment",
    "Policy/governance",
    "A2A protocols",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "AERO/OMNI provides an IPv6-based overlay networking service for mobile internetworking across multilink interfaces, using neighbor discovery and dynamic routing optimization. It targets air/land/sea/space mobility applications with support for multihop, multicast, and mobility management without explicit tunnel setup.",
  "n": 2,
  "nn": "Incremental extension of IPv6 ND and route optimization concepts; applies existing techniques (ULA addressing, ND, dynamic neighbor cache) to overlay networks rather than introducing fundamentally novel mechanisms.",
  "m": 3,
  "mn": "Protocol mechanisms are defined with architectural descriptions, but lacks implementation details, test vectors, and validation evidence typical of implementation-ready specifications.",
  "o": 4,
  "on": "Significant overlap with existing mobile IP, MANET, and overlay networking approaches; shares conceptual space with MIPv6, OLSR, and other dynamic routing solutions for mobile scenarios.",
  "mo": 1,
  "mon": "Single revision dated 2024-02-16 suggests minimal recent momentum; no evidence of WG adoption, implementation deployments, or community engagement driving iterative development.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; pure network infrastructure specification with no connection to agent architectures, decision-making, or AI operations.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft extends EDHOC with post-quantum cryptography using signature and KEM combinations, proposing two variants that reduce message complexity compared to parallel approaches. It addresses quantum-resistant key establishment for IoT and constrained environments while maintaining the lightweight EDHOC design philosophy.",
  "n": 2,
  "nn": "Incremental extension applying known PQC techniques (signatures + KEMs) to existing EDHOC framework; combines approaches from parallel drafts rather than introducing fundamentally new methods.",
  "m": 4,
  "mn": "Well-defined protocol specification with clear message flows, algorithm choices, and two distinct variants; lacks implementation artifacts and test vectors for production readiness.",
  "o": 3,
  "on": "Shares core concepts with other PQ-EDHOC proposals; differentiates through hybrid sig+KEM approach and message complexity tradeoff, but significant conceptual overlap exists in the post-quantum EDHOC space.",
  "mo": 2,
  "mon": "Single revision from 2026; no evident WG adoption signals or community momentum; appears as standalone contribution rather than active collaborative effort.",
  "r": 2,
  "rn": "Tangentially related to AI agents; relevant only if agents use EDHOC for secure bootstrapping in constrained IoT networks; not a core agent protocol or identity mechanism.",
  "c": ["Agent identity/auth", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "Proposes dynamically coupling ECN marking thresholds to buffer allocation limits in network devices to prevent pathological marking behaviors. Introduces a deterministic algorithm that adaptively adjusts congestion signals based on instantaneous buffering capacity without ML models or per-flow tracking.",
  "n": 2,
  "nn": "Incremental refinement of ECN mechanisms; coupling static thresholds to dynamic buffers is a logical engineering solution but lacks fundamental novelty.",
  "m": 3,
  "mn": "Well-defined mechanism with operational framework and reference algorithm described; lacks implementation validation, test vectors, and deployment guidance for production readiness.",
  "o": 3,
  "on": "Shares conceptual space with dynamic buffer management (RFC 7308) and ECN specifications (RFC 3168, RFC 8311); applies existing concepts in a new combination but without significant technical divergence.",
  "mo": 2,
  "mon": "Single draft revision (2026-03-02); no evidence of WG sponsorship, community discussion, or iterative development indicating active momentum.",
  "r": 1,
  "rn": "Traditional networking congestion control optimization; no connection to AI agents, autonomous systems, or machine learning—false positive for AI/agent scope.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft specifies a mechanism for nonce-based freshness verification in attestation evidence included within Certificate Signing Requests (CSRs) for CMP and EST protocols. It defines how Registration Authorities and Certification Authorities can provision nonces to end entities to ensure the recency of remote attestation claims during certificate enrollment.",
  "n": 2,
  "nn": "Incremental contribution addressing a known gap in existing CMP/EST specifications; applies well-established nonce-based freshness patterns to certificate management contexts.",
  "m": 3,
  "mn": "Protocol mechanism is clearly defined with message structure and interaction flows, though document lacks implementation examples, test vectors, and formal security analysis of nonce handling.",
  "o": 3,
  "on": "Shares foundational concepts with remote attestation (TCG standards) and existing nonce mechanisms in IETF protocols (COSE, RATS); moderate overlap with attestation evidence freshness requirements.",
  "mo": 2,
  "mon": "Single 2024 revision with limited evidence of WG adoption; appears to be exploratory work rather than established working group item with community momentum.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; focuses purely on X.509 certificate management infrastructure and remote attestation protocols.",
  "c": [
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "This draft extends OAuth Transaction Tokens to support agent context propagation in agent-based workloads, introducing the agentic_ctx claim for multi-agent flow integrity while reusing existing act and sub claims. It addresses both single-agent and multi-agent deployment patterns where transaction tokens are updated at agent transitions.",
  "n": 2,
  "nn": "Incremental extension combining existing OAuth mechanisms (act from RFC8693, sub claim) with a new structured claim; limited conceptual novelty beyond adapting token standards to agent scenarios.",
  "m": 3,
  "mn": "Defined protocol mechanism with claim structures and deployment patterns described, but abstract truncates mid-definition and lacks implementation details, examples, test vectors, or security analysis.",
  "o": 4,
  "on": "Significant overlap with base Transaction Tokens spec and standard OAuth delegation patterns; the extension primarily layers agent-specific metadata on proven token frameworks without architectural innovation.",
  "mo": 2,
  "mon": "Early-stage draft (May 2026 projected date) with single known revision; no evidence of WG adoption, implementation feedback, or community engagement beyond initial proposal.",
  "r": 4,
  "rn": "Directly relevant to agent identity/authentication and multi-agent system coordination; addresses real need for agent context in distributed agentic workflows, though not core to AI model/algorithm development.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes AI Network Security Agents—intelligent software components using machine learning and behavioral analysis—to replace static ACLs and signature-based detection in routers. Outlines four use case scenarios: dynamic threat defense, ACL optimization, configuration security, and collaborative defense across distributed network devices.",
  "n": 2,
  "nn": "Incremental application of existing AI/ML techniques (anomaly detection, behavioral analysis) to network security; core concepts not novel, though specific router-centric agent architecture has modest originality.",
  "m": 1,
  "mn": "Use case description only; no protocol specification, architecture details, API definitions, or implementation guidance. Lacks formal problem statement and evaluation methodology.",
  "o": 4,
  "on": "Significant overlap with existing work on AI-driven network security, intent-based networking, autonomous network operations, and DDoS mitigation. Concepts resemble prior drafts on network telemetry and intelligent defense systems.",
  "mo": 1,
  "mon": "Single revision, no evidence of WG discussion, community feedback, or iterative refinement. Appears to be initial proposal without subsequent development.",
  "r": 4,
  "rn": "Directly relevant to AI agents in networking and autonomous network operations; addresses intelligent decision-making and distributed collaboration. Core relevance to agent frameworks, though less focused on agent identity/auth or model serving specifics.",
  "c": [
    "Autonomous netops",
    "Policy/governance",
    "Agent discovery/reg",
    "ML traffic mgmt",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes dynamic attestation mechanisms for TLS sessions in AI agent communication, addressing the need to convey runtime posture changes (TCB, models, tools, policies) to relying parties for continuous authorization decisions. Focuses on long-lived secure channels where agent state evolves unpredictably.",
  "n": 2,
  "nn": "Incremental combination of existing remote attestation concepts with TLS and AI agent contexts; core ideas not novel but application domain is relatively unexplored.",
  "m": 2,
  "mn": "Early sketch phase—identifies use case and requirements but lacks protocol design details, message formats, or implementation guidance; no concrete mechanism specified.",
  "o": 3,
  "on": "Shares foundational concepts with remote attestation (RATS, TPM), TLS extensions, and agent communication work; moderate overlap with emerging AI infrastructure standards but distinct focus on dynamic updates.",
  "mo": 1,
  "mon": "Single 5-page draft with 2026 date; no evidence of WG adoption, multiple revisions, or community engagement; appears exploratory with uncertain trajectory.",
  "r": 4,
  "rn": "Directly relevant to AI agent trust and authorization in distributed systems; addresses genuine gap in dynamic posture reporting but limited to narrow communication pattern.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Policy/governance",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "This draft proposes enhancing CDN node selection by combining anycast routing with QUIC connection migration to enable load-aware and application-aware redirection. Clients signal service requirements while servers dynamically advertise routes based on real-time load and link quality.",
  "n": 2,
  "nn": "Incremental combination of existing technologies (anycast, BGP, QUIC); load-aware anycast routing is conceptually known, though QUIC connection migration for CDN redirection adds minor novelty.",
  "m": 2,
  "mn": "Early sketch stage; abstract describes concepts but 6-page draft likely lacks detailed protocol specification, message formats, state machines, or implementation considerations necessary for standardization.",
  "o": 4,
  "on": "Significant overlap with existing CDN optimization work (RFC 7679, load-balancing drafts) and QUIC connection migration use cases; anycast-based load signaling partially explored in prior work.",
  "mo": 1,
  "mon": "No evidence of working group sponsorship, multiple revisions, or community adoption; single draft dated 2025-11-07 with no visible ecosystem momentum.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; purely addresses CDN infrastructure optimization without AI/ML/agent components.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes a DNS signaling mechanism for authoritative servers to advertise support for alternative transport protocols (DoT, DoH, DoQ) in DNS responses, enabling resolvers to opportunistically upgrade connections while maintaining backward compatibility and DNSSEC validation options.",
  "n": 2,
  "nn": "Incremental improvement over RFC 9539's opportunistic transport testing; adds explicit signaling rather than blind discovery, but the core concept of advertising alternative transports is not novel.",
  "m": 3,
  "mn": "Protocol mechanism is defined with multiple modes (opportunistic, validated) but lacks detailed implementation guidance, test vectors, and real-world deployment examples. Draft appears incomplete (abstract cuts off mid-sentence).",
  "o": 3,
  "on": "Shares concepts with existing transport discovery mechanisms and DNSSEC validation approaches; relates to ongoing DNS privacy/security work but presents a distinct signaling approach.",
  "mo": 2,
  "mon": "Single revision visible; GitHub collaboration noted but limited evidence of WG engagement or community adoption. Early-stage development momentum.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems. Pure DNS infrastructure optimization with no connection to agent protocols, discovery, or autonomous operations.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft extends SRv6 to enable RDMA multicast by introducing the End.MT endpoint behavior for per-receiver BTH modifications and ACK/NACK aggregation on reverse paths. It allows standard RDMA QP semantics to operate over IP multicast trees for distributed storage, HPC, and AI training scenarios.",
  "n": 2,
  "nn": "Incremental extension combining existing SRv6 and RDMA concepts; the core innovation (per-receiver BTH modification at edge nodes) is a straightforward adaptation rather than a fundamentally new approach.",
  "m": 3,
  "mn": "Defines protocol mechanisms and procedures with reasonable detail, but appears to lack implementation experience, comprehensive examples, and test vectors needed for production deployment.",
  "o": 3,
  "on": "Shares conceptual overlap with SRv6 endpoint behaviors and RDMA multicast literature; combines known techniques but in a novel integration point that has limited direct precedent.",
  "mo": 1,
  "mon": "Single draft dated 2026-03-01 with no apparent revision history or follow-up; no evidence of WG discussion, implementation efforts, or community adoption signals.",
  "r": 3,
  "rn": "Partially relevant to AI infrastructure (targets AI training parameter distribution and KV cache distribution), but primarily focused on network protocol mechanics rather than agent-specific concerns.",
  "c": ["ML traffic mgmt", "Model serving/inference", "Other AI/agent"]
}
```


```json
{
  "s": "This IETF draft defines a canonical CBOR-based representation for EDHOC application profiles to standardize parameter coordination and distribution across implementations. It establishes well-known profiles and mechanisms to facilitate interoperability and extensibility of the EDHOC lightweight authenticated key exchange protocol.",
  "n": 2,
  "nn": "Incremental contribution that formalizes and standardizes existing EDHOC profile concepts into a structured format; the core innovation of profile coordination is modest but practically useful.",
  "m": 4,
  "mn": "Well-developed specification with detailed CBOR representations, coordination mechanisms, and defined profiles; appears ready for implementation with clear technical requirements.",
  "o": 3,
  "on": "Shares foundational concepts with EDHOC base specs and general profile/parameter negotiation patterns; represents specialized profile coordination rather than novel architectural approach.",
  "mo": 4,
  "mon": "Active IETF working group development (LAKE WG) with structured progression toward standardization; demonstrates sustained organizational commitment.",
  "r": 1,
  "rn": "Focused exclusively on cryptographic key exchange protocol standardization for IoT/constrained devices; has no relevance to AI agents, autonomous systems, or agent-oriented architectures.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft proposes incorporating security and trustworthiness metrics into routing decisions beyond traditional shortest-path algorithms, aiming to leverage ISP security infrastructure for secure data transmission. The work focuses on transmission-layer security rather than end-to-end or application-layer concerns.",
  "n": 2,
  "nn": "Incremental extension of existing routing concepts with security factors; the idea of security-aware routing is not novel and has been explored in prior work.",
  "m": 1,
  "mn": "Presents use cases and motivation only; lacks protocol specification, detailed mechanisms, algorithms, or implementation details.",
  "o": 4,
  "on": "Significant overlap with established work in secure routing, risk-aware routing, and QoS-based routing; similar concepts appear in multiple RFC and draft standards.",
  "mo": 1,
  "mon": "Single revision document with no evidence of WG engagement, community discussion, or iterative development; appears dormant.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; concerns traditional network routing infrastructure independent of AI/ML applications.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes a YANG-based hierarchical topology for distributed language model coordination across heterogeneous nodes with secure messaging and token-based authorization. Targets edge-to-cloud deployments where LMs of varying sizes cooperate on inference and decision-making tasks.",
  "n": 2,
  "nn": "Incremental application of existing YANG/NETMOD patterns to LM orchestration; hierarchical ML coordination is established in practice (Ollama, vLLM, MLC-LM) but formalizing it via IETF standards is moderately novel.",
  "m": 2,
  "mn": "Early sketch with abstract architecture; 12 pages insufficient for protocol detail, security properties, trust model specifics, or YANG schema completeness. No reference implementation or validation data present.",
  "o": 4,
  "on": "Significant overlap with existing model serving platforms (Ray Serve, Kubernetes ML operators, vLLM distributed inference). Trust/auth mechanisms resemble standard OAuth/mTLS patterns. YANG-for-AI is nascent but overlaps with ongoing IETF TEEP and netmod work.",
  "m": 1,
  "mn": "Single dated submission (2026-02-11 is future/test date); no revision history evident. No WG sponsorship indicated. Appears orphaned relative to active IETF netmod or AI-focused initiatives.",
  "r": 3,
  "rn": "Partially relevant to AI agent infrastructure; focuses on coordination/orchestration rather than core agent autonomy, decision-making, or safety. Relevant for multi-agent systems needing standardized topology but not for alignment or behavioral control.",
  "c": [
    "Model serving/inference",
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Agent identity/auth"
  ]
}
```


```json
{
  "s": "AGTP proposes a dedicated application-layer protocol for AI agent traffic, introducing a runtime contract negotiation substrate with 12 core methods organized as cognitive and mechanical verbs. The draft positions AGTP as a transport substrate for higher-level agent frameworks like MCP and A2A, addressing semantic vocabulary and observability gaps in HTTP-based agent communication.",
  "n": 2,
  "nn": "Incremental contribution that repackages existing agent messaging concepts (MCP, ACP, A2A, ANP) into a new transport layer; the cognitive/mechanical verb taxonomy and runtime negotiation are modest extensions rather than fundamental innovations.",
  "m": 3,
  "mn": "Protocol specification appears reasonably detailed with URI grammar, method definitions, and status code assignments, but abstract truncation and lack of visible implementation evidence or test vectors limit confidence in implementation readiness.",
  "o": 4,
  "on": "Significant overlap with existing agent group messaging protocols (MCP, ACP, A2A, ANP); essentially proposes wrapping these in a new transport rather than offering orthogonal functionality; runtime negotiation concept borrowed from HTTP OPTIONS and capability negotiation patterns.",
  "mo": 2,
  "mon": "Single revision (v07 noted) with limited evidence of broader WG adoption or community momentum; niche applicability to agent-specific traffic may limit traction beyond specialized implementations.",
  "r": 4,
  "rn": "Directly addresses agent communication infrastructure and identity/authentication concerns; relevant to agent scalability and observability, though framing as transport-layer solution may be premature given evolving agent protocol landscape.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "ML traffic mgmt",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Defines three hybrid post-quantum key agreement mechanisms for TLS 1.3 combining ML-KEM with ECDHE (X25519MLKEM768, SecP256r1MLKEM768, SecP384r1MLKEM1024) to provide transitional cryptographic security during the migration to post-quantum standards.",
  "n": 2,
  "nn": "Incremental extension applying existing ML-KEM and ECDHE primitives to TLS 1.3; hybrid approach is standard practice for PQC migration but mechanically straightforward.",
  "m": 4,
  "mn": "Well-defined protocol specification with clear ciphersuites and integration points; lacks implementation details and test vectors for production readiness but specification is mature.",
  "o": 3,
  "on": "Shares core hybrid PQC concepts with draft-ietf-tls-hybrid-design and NIST PQC standards; similar to concurrent hybrid proposals but uses standardized ML-KEM rather than experimental schemes.",
  "r": 1,
  "rn": "Not relevant to AI agents; this is cryptographic infrastructure for TLS without connection to autonomous agents, agent identity/authentication, or AI-specific networking concerns.",
  "mo": 4,
  "mon": "Strong community momentum from IETF TLS WG pursuing post-quantum cryptography; aligns with NIST standardization timelines and urgent industry PQC migration needs.",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "BRSKI-AE extends the BRSKI bootstrapping protocol to support alternative certificate enrollment mechanisms like CMP instead of EST, enabling flexible device onboarding across diverse network environments. This provides a framework for integrating suitable enrollment protocols while maintaining security and scalability in network device provisioning.",
  "n": 2,
  "nn": "Incremental extension to existing BRSKI standard; primarily substitutes enrollment protocol options rather than introducing fundamentally new concepts",
  "m": 4,
  "mn": "Well-developed specification with architectural updates and protocol details; appears implementation-ready with comprehensive framework for alternative methods",
  "o": 3,
  "on": "Shares core concepts with BRSKI, EST, and CMP specifications; builds naturally on established standards with moderate overlap in design patterns",
  "mo": 3,
  "mon": "Active WG development typical of IETF standards track; appears to address real operational needs in device bootstrapping scenarios",
  "r": 1,
  "rn": "Not relevant to AI agents, autonomous systems, or machine learning operations; focuses on traditional IoT/network device enrollment infrastructure",
  "c": [
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "Specifies an application-layer frame format for fan-out message delivery across concurrent agentic sessions within a single identity-bound principal, using Server-Sent Events and scope-based recipient expansion. The agent-channel frame carries kind discriminators, structured payloads, identity attribution, and provenance blocks, composing with existing handle namespace and discovery mechanisms.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (SSE, fan-out messaging, identity-scoped delivery) without fundamental novelty; primarily an envelope specification layering on established protocols.",
  "m": 3,
  "mn": "Defined protocol specification with grammar for scope expansion and filter expressions, though frame persistence is explicitly out-of-scope; lacks implementation artifacts like test vectors or reference implementations.",
  "o": 4,
  "on": "Significant overlap with pub-sub patterns, SSE-based messaging systems, and identity-keyed routing; conceptually similar to topic-based fan-out in existing message brokers adapted for agent contexts.",
  "mo": 2,
  "mon": "Single draft revision with future date (2026-05-21); unclear WG adoption or community engagement; no evidence of active development cycle or multiple iterations.",
  "r": 4,
  "rn": "Directly relevant to agent coordination and identity-based interoperability; focuses on agent session management and organizational substrate messaging, core to multi-agent system architecture.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "AINP proposes a semantic communication protocol for AI agents using intent-based routing and capability discovery instead of traditional IP networking. The draft replaces conventional network abstractions with agent-native concepts like structured intents, autonomous negotiation, and cryptographic security for multi-agent coordination.",
  "n": 2,
  "nn": "The core idea of replacing location-based routing with semantic/intent-based routing for agents is incremental rather than novel—it mirrors existing service discovery and publish-subscribe patterns adapted to agent contexts. The conceptual components are recognizable extensions of established networking and agent communication paradigms.",
  "m": 2,
  "mn": "The draft presents early-stage conceptual framing without rigorous protocol specification. Missing are detailed message formats, state machines, formal syntax definitions, implementation guidance, and security analysis. Version 0.1 designation and 17-page length suggest preliminary sketching rather than protocol maturity.",
  "o": 4,
  "on": "Significant overlap with existing work: service discovery (mDNS, DNS-SD), intent-based networking (IBN proposals), agent communication frameworks (FIPA ACL, JADE), and semantic web protocols. The framing as 'AI-Native' is somewhat novel but the underlying mechanisms map closely to established patterns.",
  "m": 1,
  "mon": "No evidence of WG adoption, community feedback cycles, or revision history indicating active development. Single draft snapshot with no visible momentum within IETF or broader standardization bodies. Appears exploratory rather than actively driven.",
  "r": 4,
  "rn": "Directly addresses multi-agent coordination and communication, which is a core AI agent infrastructure concern. However, focuses narrowly on network protocol layer rather than broader agent alignment, safety, or orchestration challenges. Relevant but somewhat limited in scope within AI agent ecosystem.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "Agent identity/auth",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft proposes a centralized gateway architecture (DMSC) to handle communication, security, and collaboration logic for multi-agent LLM systems, offloading these concerns from individual agents. It addresses fragmentation and security risks in cloud-native multi-tenant deployments by providing standardized service discovery, encryption, and policy enforcement.",
  "n": 2,
  "nn": "The core concept of offloading agent infrastructure concerns to a gateway is incremental; similar patterns exist in service meshes (Istio), API gateways, and agent platforms. The application to LLM agents is somewhat novel but architecturally conventional.",
  "m": 1,
  "mn": "This is purely a problem statement and requirements document with no protocol specification, mechanism design, or implementation details provided. It reads as early-stage positioning without technical depth.",
  "o": 4,
  "on": "Significant overlap with existing work: service mesh architectures (Envoy, Istio), agent platforms (Kubernetes operators), API gateway patterns, and multi-tenant orchestration frameworks already address these requirements. The framing around LLM agents is new but the underlying technical challenges are well-explored.",
  "m": 1,
  "mon": "Document appears to be a single submission with no revision history or visible community engagement. No evidence of WG discussion, implementation efforts, or broader adoption momentum.",
  "r": 3,
  "rn": "Partially relevant to AI agent systems. Focuses primarily on infrastructure/networking aspects rather than core agent capabilities, reasoning, or AI-specific concerns. Addresses operational challenges but not AI safety, alignment, or agent behavior.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Agent identity/auth",
    "Policy/governance",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "VOLT proposes a cryptographically-secured audit trail protocol for AI agent workflows, using hash-chained records and portable Evidence Bundles to detect tampering. It emphasizes privacy through content-addressing, redaction support, and optional signatures for non-repudiation.",
  "n": 3,
  "nn": "Hash-chain audit logging is established; novelty lies in domain-specific application to agentic AI with privacy-first design and Evidence Bundle portability, though mechanisms are largely conventional.",
  "m": 3,
  "mn": "Protocol structure clearly defined with explicit features (redaction, signatures, snapshots), but lacks implementation details, test vectors, and reference implementations needed for maturity level 4-5.",
  "o": 3,
  "on": "Shares concepts with existing audit/logging protocols (blockchain provenance patterns, Merkle trees) and agent transparency work; overlaps conceptually with W3C Verifiable Credentials and COSE signing approaches.",
  "m": 2,
  "mon": "Single draft submission (2026-02-28); no evidence of WG adoption, revisions, or community feedback cycle yet. Early-stage proposal momentum.",
  "r": 4,
  "rn": "Directly addresses critical need for AI agent auditability and tamper-evidence in high-stakes deployments; highly relevant to trustworthiness and governance concerns.",
  "c": ["Data formats/interop", "Policy/governance", "Human-agent interaction", "Agent identity/auth", "AI safety/alignment"]
}
```


```json
{
  "s": "Proposes a WIMSE profile enabling cryptographic binding of software workloads to execution environments via transitive attestation chains, addressing credential portability risks in autonomous AI agents across jurisdictions. Combines RATS-based residency verification with standard identity agents to ensure identities are valid only from verified, integral hosts.",
  "n": 3,
  "nn": "Transitive attestation concept is useful but represents incremental extension of existing WIMSE and RATS frameworks; the application to AI agent mobility is timely but the core mechanism lacks significant novelty.",
  "m": 2,
  "mn": "Early sketch stage: abstract defines vision and problem well, but 11 pages suggests limited protocol detail, no implementation examples, test vectors, or concrete message flows provided; defers critical security assumptions (WIA integrity) to companion draft.",
  "o": 4,
  "on": "Substantial overlap with verifiable geofencing draft it references; similar to existing WIMSE identity profiles and general RATS attestation patterns; limited differentiation beyond applying these to AI agent scenarios.",
  "mo": 2,
  "mon": "Single draft submission dated 2026 with unclear WG adoption; references to companion drafts suggest early-stage work; no visible community discussion or multiple iterations; momentum appears nascent.",
  "r": 4,
  "rn": "Directly relevant to agent identity and authentication; addresses real AI agent threat model (hijacking, prompt injection, jurisdiction crossing); positions as core security layer for autonomous systems in multi-environment deployments.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "A2A protocols",
    "AI safety/alignment",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "TCT Protocol proposes an HTTP-based JSON envelope for delivering web content to automated agents with negotiated text formats, metadata, and bidirectional URL discovery. It combines existing technologies (ETags, conditional requests, JSON sitemaps) to optimize bandwidth for machine-readable content consumption.",
  "n": 2,
  "nn": "Incremental combination of established HTTP mechanisms (conditional requests, ETags) with a JSON wrapper format. No novel protocol primitives or fundamentally new approach to agent-server interaction.",
  "m": 3,
  "mn": "Protocol specification is defined with JSON envelope structure and HTTP mechanics documented, but lacks implementation examples, test vectors, or reference implementations that would demonstrate production readiness.",
  "o": 4,
  "on": "Significant overlap with existing standards: mimics aspects of Sitemaps protocol, conditional HTTP requests (RFC 7232), content negotiation (RFC 7231), and overlaps conceptually with OpenAPI/schema approaches for machine-readable APIs.",
  "mo": 1,
  "mon": "Single dated draft (2026-05-12) with no evidence of multiple revisions, WG discussion, or community adoption. Appears to be isolated proposal without follow-up activity.",
  "r": 3,
  "rn": "Partially relevant to AI agents; addresses content delivery to automated clients but focuses narrowly on format/metadata wrapping rather than agent autonomy, coordination, or intelligence. More infrastructure than AI-specific.",
  "c": [
    "Data formats/interop",
    "Agent discovery/reg",
    "A2A protocols",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "This draft specifies how to transport the Model Context Protocol (MCP) over MOQT, enabling efficient publish-subscribe delivery of AI agent resources, tools, and skills with progressive loading. It focuses on scalable relay architectures and bandwidth optimization for distributed AI service deployments.",
  "n": 2,
  "nn": "Straightforward application of existing MOQT transport to MCP protocol; combines established technologies without fundamental innovation in either protocol or architecture.",
  "m": 3,
  "mn": "Reasonably complete protocol specification with message mapping and procedures defined, but lacks implementation examples, test vectors, and validation of the progressive loading efficiency claims.",
  "o": 4,
  "on": "Significant overlap with existing MCP implementations and MOQT specifications; primarily an engineering integration effort rather than novel protocol design.",
  "mo": 2,
  "mon": "Single dated revision (2026-03-02) with no evidence of active development, WG discussion, or community adoption; appears exploratory rather than established initiative.",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure and A2A protocol standardization; addresses practical scalability needs for distributed MCP deployments.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Model serving/inference",
    "Agent discovery/reg",
    "ML traffic mgmt"
  ]
}
```


```json
{
  "s": "SDAF proposes a symmetry-driven asynchronous forwarding mechanism for LEO satellite networks that exploits toroidal topology properties to achieve fast convergence without control-plane synchronization. The approach autonomously handles reverse flows using only local link-state information, compatible with existing protocols like OSPFv3 and IS-IS, demonstrating microsecond-scale convergence and reduced packet loss in simulations.",
  "n": 3,
  "nn": "Leveraging toroidal topology symmetry for asynchronous forwarding is a useful contribution, but fundamentally applies established fast-reroute and local repair concepts to satellite-specific constraints rather than introducing genuinely novel algorithmic principles.",
  "m": 4,
  "mn": "Well-defined mechanism with simulation results and actual satellite router testing; lacks formal protocol specification detail and standardization-ready implementation guidance, but demonstrates sufficient maturity for WG consideration.",
  "o": 3,
  "on": "Shares conceptual overlap with existing fast-reroute mechanisms (LFA, uloop avoidance literature) and local repair approaches; novel application domain and topology-specific optimization reduce but don't eliminate overlap with prior work.",
  "m": 2,
  "mon": "Single draft submission in early 2026 with no apparent WG sponsorship or revision history visible; presents specialized satellite network solution without clear broader IETF community adoption trajectory.",
  "r": 2,
  "rn": "Addresses autonomous routing and convergence in constrained systems, but does not directly engage with AI agents, autonomous system intelligence, or machine learning; tangentially related to autonomous network operations only through the 'autonomous' descriptor.",
  "c": ["Autonomous netops", "Other AI/agent"]
}
```


```json
{
  "s": "This draft analyzes system and network requirements for large-scale LLM inference services by examining mainstream frameworks like vLLM and SGLang, identifying challenges in computing and communication demands. It aims to establish foundational understanding for defining unified LLM inference architectures from a network management perspective.",
  "n": 2,
  "nn": "Requirements analysis of existing inference frameworks is incremental; primarily surveys known systems rather than proposing novel solutions or architectures.",
  "m": 2,
  "mn": "Early-stage requirements gathering document without concrete protocol specifications, mechanisms, or implementation guidance; lacks technical depth and actionable recommendations.",
  "o": 3,
  "on": "Overlaps with existing literature on ML system performance, distributed inference optimization, and datacenter networking; survey-style analysis without differentiation from prior work.",
  "mo": 1,
  "mon": "Single draft with November 2025 date and minimal community momentum; appears to be exploratory work without evidence of WG engagement or adoption pathway.",
  "r": 4,
  "rn": "Directly relevant to AI model serving and network management for inference workloads; focuses on system requirements rather than core agent-oriented topics.",
  "c": ["Model serving/inference", "ML traffic mgmt", "Policy/governance"]
}
```


```json
{
  "s": "PACR proposes a wire format for recording verifiable causal intervention events between autonomous agents, binding identity, predecessors, thermodynamic costs, and resource metrics into a content-addressed DAG. It aims to provide accountability for agent actions across digital, physical, and biological substrates without requiring wall-clock timestamps.",
  "n": 2,
  "nn": "Incremental contribution combining existing concepts (causal DAGs, Pearl's do-calculus, content addressing) into a specialized wire format; the core ideas lack novelty but application to agent accountability is somewhat focused.",
  "m": 2,
  "mn": "Early specification sketch with abstract structure defined but missing critical details: no serialization examples, unclear how thermodynamic costs are computed/verified, no concrete encoding rules, no test vectors or reference implementations.",
  "o": 4,
  "on": "Significant overlap with blockchain/ledger causality tracing, distributed systems event logs (Lamport clocks, vector clocks), and existing causal consistency frameworks; the thermodynamic annotation layer is somewhat novel but integration remains underspecified.",
  "mo": 1,
  "mon": "Appears to be single-submission work with April 2026 date (future/hypothetical), no evidence of WG adoption, revision history, or community feedback; minimal GitHub activity indicators detectable.",
  "r": 3,
  "rn": "Partially relevant to autonomous agents and accountability, but framing is overly abstract and philosophical; lacks grounding in practical multi-agent systems problems; thermodynamic costs and 'cognitive complexity splits' are poorly motivated.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "AI safety/alignment",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "PLPES proposes a formal specification framework for standardizing prompts used in AI systems, including canonical representation formats, classification taxonomies, versioning, and security mechanisms. It aims to address reproducibility, injection vulnerabilities, and auditability gaps in prompt-driven AI deployments across critical infrastructure and enterprise workflows.",
  "n": 2,
  "nn": "Incremental contribution applying existing standardization patterns (versioning, classification, integrity verification) to prompt engineering; the core idea of formalizing prompts is sensible but lacks conceptual novelty.",
  "m": 3,
  "mn": "Defines protocol mechanisms (PDO schema, taxonomy, versioning model) and references external specs (REM Protocol), but abstract doesn't demonstrate detailed implementation examples, test vectors, or validation procedures typical of mature IETF protocols.",
  "o": 4,
  "on": "Significant overlap with existing prompt management systems (LangChain, Anthropic's prompt caching), model card specifications (Mitchell et al.), and software supply chain standards (SBOM, SLSA); positions itself as novel but borrows heavily from established practices.",
  "mo": 1,
  "mon": "April 2026 date is future-dated (likely a placeholder); single draft with no indication of WG adoption, community engagement, or revision history; appears to be early-stage individual submission without demonstrated momentum.",
  "r": 4,
  "rn": "Directly relevant to AI agent systems and agentic prompt chains; addresses real operational concerns (reproducibility, security, auditability) in deployed AI systems, though focus is narrower than core agent architecture topics.",
  "c": [
    "Data formats/interop",
    "AI safety/alignment",
    "Agent identity/auth",
    "Policy/governance",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "Analyzes security gaps in multi-agent system communication protocols (TLS, HTTP, MQTT) and frameworks (AutoGen), identifying limitations around agent-native semantics like dynamic identity and context integrity. Establishes a problem statement and gap analysis to guide future IETF standardization in agent communication.",
  "n": 2,
  "nn": "Incremental analysis combining known protocol limitations with MAS-specific concerns; agent security issues are recognized but framing as gap analysis rather than novel solutions",
  "m": 1,
  "mn": "Problem statement and gap analysis only; no protocol design, mechanism specification, or concrete recommendations provided beyond identifying limitations",
  "o": 4,
  "on": "Significant overlap with existing security literature on MAS, protocol analysis work, and authentication frameworks; agent communication security has been addressed in distributed systems and robotics communities",
  "mo": 1,
  "mon": "Initial draft with unclear adoption path; no evidence of WG discussion, community feedback, or follow-up revisions; problem identification without proposed solutions limits traction",
  "r": 4,
  "rn": "Directly relevant to AI agent infrastructure; addresses real deployment concerns in agent frameworks and multi-agent orchestration, though execution is analysis-only",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "This draft proposes adding 'Agent Consideration' sections to IETF specifications to guide AI agents in consuming specs and generating code. It defines guidance mechanisms including agentcards, annotated examples, and language-specific directives for media-type production.",
  "n": 2,
  "nn": "Incremental contribution addressing a newly relevant problem (AI-assisted code generation from specs) but using straightforward annotation and guidance approaches without significant technical innovation.",
  "m": 2,
  "mn": "Early sketch phase with conceptual framework but lacks implementation details, concrete agentcard schemas, validation mechanisms, or working examples demonstrating practical utility.",
  "o": 3,
  "on": "Shares overlapping concepts with existing efforts in spec annotation (OpenAPI, AsyncAPI), code generation guidance, and AI-assisted tooling, though applied specifically to IETF context.",
  "mo": 1,
  "mon": "Single revision with no evidence of WG adoption, community discussion, or iterative development since initial draft date; appears speculative rather than addressing established need.",
  "r": 3,
  "rn": "Partially relevant to AI agent concerns—addresses agent consumption of specifications but focuses narrowly on code generation assistance rather than core agent coordination, autonomy, or safety issues.",
  "c": ["Data formats/interop", "Human-agent interaction", "Other AI/agent"]
}
```


```json
{
  "s": "This draft proposes integrating post-quantum cryptography hybrid algorithms into EAP-AKA' Forward Secrecy to protect against quantum computing threats to ephemeral keys. It extends RFC9678 by replacing traditional ECDHE with PQ/T hybrid key agreement mechanisms.",
  "n": 2,
  "nn": "Straightforward application of existing hybrid PQC frameworks to an established protocol; limited algorithmic innovation beyond combining known components.",
  "m": 2,
  "mn": "Early draft stage presenting motivation and problem statement; lacks detailed protocol specification, implementation guidance, test vectors, and performance analysis needed for maturity.",
  "o": 3,
  "on": "Shares core concepts with ongoing PQC hybrid standardization efforts (NIST, IETF PQUIP); similar approaches being explored in TLS 1.3 PQC variants and other EAP extensions.",
  "mo": 1,
  "mon": "Single revision as recent draft (2025-03-17); no evidence of WG sponsorship, community feedback cycles, or implementation activity.",
  "r": 2,
  "rn": "Not relevant to AI agents; addresses network authentication protocol security. Agent identity/auth category is for agent-specific authentication mechanisms, not cellular/general network protocols.",
  "c": ["Agent identity/auth"]
}
```


```json
{
  "s": "This draft analyzes gaps and problems in integrating AI agents into mobile core networks, addressing architectural, operational, and interoperability challenges in agent-enabled telecom infrastructure.",
  "n": 2,
  "nn": "Incremental contribution applying existing agent concepts to mobile network domain; lacks novel architectural insights or mechanisms specific to cellular core networks.",
  "m": 1,
  "mn": "Problem statement and gap analysis document only; no protocol specifications, mechanisms, or implementation details provided; foundational stage.",
  "o": 3,
  "on": "Shares conceptual overlap with broader agent architecture and mobile network optimization work; positions within established telecom and autonomous systems discussions.",
  "mo": 2,
  "mon": "Early-stage draft with single revision; limited evidence of WG traction or community engagement; agent integration in mobile networks is niche.",
  "r": 3,
  "rn": "Partially relevant to AI agents in networks; focuses on problem identification rather than agent behavior, autonomy, or intelligence; more infrastructure than agent-centric.",
  "c": [
    "Autonomous netops",
    "Policy/governance",
    "Agent discovery/reg",
    "Data formats/interop",
    "Other AI/agent"
  ]
}
```


```json
{
  "s": "CAAM defines a post-discovery authorization layer for agent systems, combining relationship-based access control with cryptographic attestation through JWT/CWT tokens. It integrates with ARDP discovery and bridges IPSIE/SPIFFE identity frameworks to govern H2A and A2A interactions with purpose-bound delegation.",
  "n": 3,
  "nn": "Applies established patterns (ReBAC, JWT, RATS) to agent authorization; contextual assertion claim is useful but incremental innovation in token-based access control.",
  "m": 2,
  "mn": "Specification exists but lacks implementation details, test vectors, and concrete usage examples; relies heavily on external draft references (ARDP, IPSIE) that may be nascent.",
  "o": 4,
  "on": "Significant overlap with existing authorization frameworks (OAuth 2.0, ABAC patterns); relationship-based access control well-established in industry; main differentiation is agent-specific integration point.",
  "mo": 2,
  "mon": "Single revision dated 2026-02; no visible WG adoption, community discussion, or implementation signals; appears to be early-stage individual submission.",
  "r": 4,
  "rn": "Directly relevant to agent systems and A2A security; addresses real need for runtime authorization in agent meshes, though scope depends on ARDP adoption which remains uncertain.",
  "c": [
    "Agent identity/auth",
    "A2A protocols",
    "Agent discovery/reg",
    "Policy/governance",
    "Data formats/interop",
    "Human-agent interaction"
  ]
}
```


```json
{
  "s": "This draft provides implementation guidance for EDHOC, an authenticated key exchange protocol designed for constrained environments. It offers practical considerations for developers implementing this cryptographic protocol.",
  "n": 2,
  "nn": "Incremental contribution focusing on implementation details of an existing protocol rather than introducing new cryptographic concepts or techniques.",
  "m": 4,
  "mn": "Detailed implementation guidance with practical considerations, though not a complete specification with comprehensive test vectors.",
  "o": 3,
  "on": "Shares core concepts with related COSE and key exchange specifications; provides complementary implementation perspective rather than novel overlap.",
  "mo": 3,
  "mon": "Active development within IETF working groups with multiple revisions, though focused on guidance rather than protocol innovation.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; concerns cryptographic protocol implementation for constrained devices with no agent-specific application.",
  "c": ["Data formats/interop", "Agent identity/auth"]
}
```


```json
{
  "s": "This draft outlines use cases for network AI agents in 6G systems, focusing on connectivity and third-party application service scenarios derived from 3GPP standards. It discusses integration requirements and workflows for AI agents within the 6G framework.",
  "n": 2,
  "nn": "Incremental contribution that applies existing AI agent concepts to 6G context; lacks novel architectural or methodological insights specific to network agents.",
  "m": 2,
  "mn": "Early-stage use case document with informal requirements specification; no protocols, detailed mechanisms, or implementation guidance provided.",
  "o": 4,
  "on": "Significant overlap with ongoing 6G standardization work, 3GPP TR22.870, and generic AI agent frameworks; limited differentiation from parallel 6G AI efforts.",
  "mo": 1,
  "mon": "Single revision draft with unclear WG sponsorship; appears exploratory rather than driven by active community adoption or iterative development.",
  "r": 4,
  "rn": "Directly addresses network AI agents in emerging 6G context, though execution focuses on use case enumeration rather than deep technical requirements for agent deployment.",
  "c": ["Autonomous netops", "Agent discovery/reg", "Policy/governance", "Data formats/interop", "Other AI/agent"]
}
```


```json
{
  "s": "Extends AGTP with symmetric merchant identity verification mechanisms including Merchant Manifest Documents, Trust Tiers, and protocol integration points to close the verification gap on the receiving side of agentic transactions. Introduces Intent-Assertion headers, Cart-Digest for multi-item transactions, and a 455 status code to establish bidirectional trust within AGTP's governance model.",
  "n": 2,
  "nn": "Incremental extension of existing AGTP framework; mirrors agent-side mechanisms to merchant side rather than introducing fundamentally new verification approaches.",
  "m": 3,
  "mn": "Well-defined protocol-level mechanisms with structural clarity and alignment across multiple integration points (PURCHASE, DISCOVER, Attribution-Record); lacks implementation details, test vectors, and deployment guidance.",
  "o": 3,
  "on": "Shares core concepts with existing PKI/identity frameworks and commerce protocols; directly parallels AGTP agent identity mechanisms; moderate overlap with standards work in API authentication and merchant verification.",
  "mo": 2,
  "mon": "Two versions with incremental refinements (v00→v01); appears to follow AGTP release cycle but limited evidence of independent community adoption or WG traction.",
  "r": 4,
  "rn": "Directly addresses a critical gap in agentic commerce protocols; highly relevant to agent-to-agent and agent-to-service transactions, though assumes AGTP as foundational standard.",
  "c": ["A2A protocols", "Agent identity/auth", "Policy/governance", "Agent discovery/reg", "Data formats/interop"]
}
```


```json
{
  "s": "This draft proposes an intelligent routing method for SR (Segment Routing) Policy that leverages network quality metrics to select optimal candidate paths in MPLS and IPv6 environments. It extends existing SR Policy mechanisms with quality-aware path selection to improve routing decisions.",
  "n": 2,
  "nn": "Incremental contribution combining existing SR Policy concepts with basic quality-of-service awareness; the intelligent routing concept itself is not novel in networking.",
  "m": 2,
  "mn": "Early sketch stage with abstract and problem statement; lacks detailed protocol specifications, algorithmic definitions, implementation guidelines, or test vectors necessary for implementation.",
  "o": 4,
  "on": "Significant overlap with RFC 8664 (SR Policy), RFC 9256 (Segment Routing Policy Architecture), and existing QoS-aware routing work; limited novel integration approach.",
  "mo": 1,
  "mon": "Single revision with 2025-06-15 date suggests initial submission; no evidence of WG discussion, multiple iterations, or community engagement in public archives.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems; this is conventional network routing optimization without agent-based decision making, learning capabilities, or autonomous behaviors.",
  "c": ["ML traffic mgmt"]
}
```


```json
{
  "s": "Proposes using generative AI to create flexible communication protocols for agent-to-agent interactions, replacing strict APIs with natural language-based unified communication. Claims this approach enables better interoperability and reduces operational complexity across registration, discovery, telemetry, and debugging.",
  "n": 2,
  "nn": "Natural language for protocol definition is not novel; the application to agent APIs is incremental rather than genuinely original.",
  "m": 1,
  "mn": "Draft presents only problem statement and high-level conceptual argument; lacks protocol specification, formal definitions, examples, or implementation guidance.",
  "o": 4,
  "on": "Significant overlap with existing work on API abstraction, LLM-based protocol interpretation, and flexible agent communication frameworks; positions as novel but core ideas are established.",
  "mo": 1,
  "mon": "Single early-stage draft with no apparent revisions, WG adoption, or community engagement; appears to be initial submission without development momentum.",
  "r": 3,
  "rn": "Directly addresses agent communication but focuses narrowly on API flexibility via natural language rather than core AI agent capabilities, safety, or governance concerns.",
  "c": ["A2A protocols", "Data formats/interop", "Agent discovery/reg", "Model serving/inference"]
}
```


```json
{
  "s": "NST-TLP proposes embedding service type identifiers into network packets via IPv4/IPv6, MPLS, or Ethernet headers to enable intelligent traffic recognition and policy-based forwarding. The mechanism targets diverse applications from VR to IoT, providing a standardized labeling approach for network resource optimization.",
  "n": 2,
  "nn": "Incremental extension of existing traffic classification and labeling concepts (DSCP, MPLS EXP, IEEE 802.1p). Core idea of adding service-type metadata to packets is well-established; limited novelty in mechanism design.",
  "m": 2,
  "mn": "Early draft stage with abstract and scope defined, but lacking protocol details. No indication of implementation, test vectors, or deployment experience. Needs substantial development to reach specification completeness.",
  "o": 4,
  "on": "Significant overlap with DSCP (RFC 2474), MPLS traffic engineering (RFC 3270), IEEE 802.1p prioritization, and newer work on packet in-band network telemetry (INT). Positioning relative to these existing mechanisms is unclear.",
  "m": 1,
  "mon": "Minimal community momentum evident. Single draft revision at 2026-01-29 with no apparent WG affiliation or multi-author collaboration. No visible discussion on IETF lists or adoption signals.",
  "r": 1,
  "rn": "Not relevant to AI agents or autonomous systems. Traditional network traffic classification and QoS mechanism with no connection to AI safety, agent identity, autonomous network operations, or agent-relevant protocols.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "Proposes a structured colon-separated syntax extension to OAuth 2.0 scopes to enable fine-grained permission expression for modular capability units (skills) in agent ecosystems. Addresses authorization gaps in agent installations by adding resource_type:action:target[:constraints] format while maintaining OAuth compatibility.",
  "n": 2,
  "nn": "Incremental extension applying existing OAuth scope concepts to agent scenarios; colon-delimited syntax is a straightforward syntactic enhancement rather than a fundamentally new authorization approach.",
  "m": 3,
  "mn": "Defines protocol mechanism with concrete syntax and use cases, but lacks implementation examples, test vectors, and validation rules for constraint expressions; unclear how constraint parsing and validation would work in practice.",
  "o": 3,
  "on": "Shares conceptual space with ABAC/RBAC frameworks and existing OAuth scope extensions (RFC 8693, capability-based security models); agent authorization addressed in parallel WG efforts but this syntax differs.",
  "mo": 2,
  "mon": "Single draft revision with 2026 date; no evidence of WG adoption, implementation feedback, or community discussion; nascent momentum in agent authorization space generally but this specific proposal lacks uptake signals.",
  "r": 4,
  "rn": "Directly addresses agent capability authorization and permission expression, core concerns for autonomous agent deployments; well-scoped to agent ecosystems though broader OAuth community relevance unclear.",
  "c": ["Agent identity/auth", "Data formats/interop", "Policy/governance", "A2A protocols"]
}
```


```json
{
  "s": "Extends OAuth Transaction Tokens to support agent context propagation by using the 'act' field to identify agents and 'sub' field for principals, enabling granular access control in agent-based workloads. Applies existing token mechanisms to autonomous agent scenarios with minimal new functionality.",
  "n": 2,
  "nn": "Incremental extension applying established transaction token patterns to agents; limited conceptual novelty beyond field reuse",
  "m": 3,
  "mn": "Defined mechanism with clear field semantics but lacks implementation details, examples, and test vectors for agent-specific scenarios",
  "o": 4,
  "on": "Significant overlap with base OAuth-TXN-TOKENS; primarily a use-case mapping rather than novel protocol design; similar to existing delegation/impersonation token specs",
  "mo": 2,
  "mon": "Single revision with no visible WG discussion or implementation feedback; niche agent-focused extension with limited adoption signals",
  "r": 4,
  "rn": "Directly addresses agent authentication and authorization context propagation, a core requirement for distributed agent systems, though limited to OAuth ecosystem",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "Extends SCIM protocol to represent AI agent identities in JSON format, enabling agent authentication and authorization in cloud services. Applies existing identity management standards to the emerging domain of agentic systems.",
  "n": 2,
  "nn": "Straightforward application of established SCIM patterns to agents; minimal conceptual innovation beyond standard identity schema extension.",
  "m": 3,
  "mn": "Defines schema structure and protocol integration but appears early-stage; 13 pages suggests incomplete specification lacking comprehensive examples or implementation guidance.",
  "o": 3,
  "on": "Shares core concepts with agent registration/discovery work and overlaps with general identity provisioning standards; moderate conceptual overlap with existing SCIM extensions.",
  "mo": 1,
  "mon": "Single draft revision in early 2026 with no visible WG adoption, community discussion, or implementation commitments; appears to be exploratory work without organizational backing.",
  "r": 4,
  "rn": "Directly addresses agent identity and authentication, which are foundational infrastructure concerns for multi-agent systems; timely given increased agent deployment but not addressing higher-level agent governance.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg",
    "A2A protocols"
  ]
}
```


```json
{
  "s": "SIRP proposes semantic-based routing for AI inference requests by analyzing content rather than metadata alone, with optional extensions for cost, urgency, domain specialization, and privacy. The framework aims to improve routing robustness and consistency in distributed inference systems.",
  "n": 2,
  "nn": "Incremental contribution combining existing routing concepts with basic content analysis; semantic routing itself is not novel, though application to inference systems is somewhat specialized.",
  "m": 2,
  "mn": "Early-stage draft with framework description but lacks detailed protocol specifications, message formats, algorithms, deployment considerations, and security analysis expected of a routing protocol standard.",
  "o": 4,
  "on": "Significant overlap with existing work in content-based routing, service mesh intelligent routing (Istio/Envoy), and inference load balancing; semantic analysis aspects echo established ML ops practices.",
  "mo": 1,
  "mon": "Single draft revision with April 2026 date; no evidence of WG adoption, community discussion, or iterative development; appears nascent with unclear support.",
  "r": 4,
  "rn": "Directly relevant to AI inference deployment and model serving infrastructure; addresses practical routing challenges in distributed AI systems though framed narrowly around inference rather than broader agent coordination.",
  "c": [
    "Model serving/inference",
    "ML traffic mgmt",
    "Autonomous netops",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "AIDP proposes a control-plane protocol for standardizing agent-to-agent interactions, capability delegation, and execution auditing across distributed systems. The draft targets interoperability and security for autonomous software agents operating in multi-domain environments.",
  "n": 2,
  "nn": "Incremental contribution combining existing protocol design patterns (capability-based security, delegation frameworks) with agent-specific concerns; lacks fundamentally novel architectural insights.",
  "m": 2,
  "mn": "Early-stage draft with protocol outline but appears to lack implementation experience, formal semantics, comprehensive error handling, or test vectors; protocol details underspecified for independent implementation.",
  "o": 4,
  "on": "Significant conceptual overlap with OAuth2/OIDC delegation patterns, SPIFFE/SVID identity frameworks, and existing RPC protocols; unclear differentiation from agent-adapted capability delegation schemes.",
  "mo": 1,
  "mon": "Single revision with no visible WG discussion, community adoption, or implementation commitments; appears dormant as of publication date.",
  "r": 4,
  "rn": "Directly addresses real agent coordination challenges (capability enforcement, cross-domain delegation, auditability) relevant to emerging autonomous agent deployments, though scope and threat model need clarification.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes extensions to robots.txt to support AI-specific crawlers with syntax for distinguishing between training and inference activities. Aims to provide granular access control policies for different types of AI agents accessing web content.",
  "n": 2,
  "nn": "Incremental extension of existing robots.txt mechanism; combines known concepts (user-agent filtering, activity-based policies) without substantial technical innovation.",
  "m": 2,
  "mn": "Early draft stage with proposal outline but lacks detailed specification, syntax examples, parsing requirements, backward compatibility mechanisms, and implementation guidance.",
  "o": 4,
  "on": "Significant conceptual overlap with robots.txt extensions (REP WG work), AI crawler guidelines (OpenAI, Google specifications), and existing policy differentiation mechanisms; limited novel framing.",
  "mo": 1,
  "mon": "Single revision, no visible WG adoption or community engagement; publication date suggests recent submission but no evidence of iterative development or stakeholder feedback.",
  "r": 4,
  "rn": "Directly addresses AI agent web access control and policy governance; core relevance to managing AI training/inference activities but execution limited to existing framework.",
  "c": [
    "ML traffic mgmt",
    "Policy/governance",
    "Agent identity/auth",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "This draft proposes an improved HTTP 401/407 Bearer authentication flow enabling user-agents to automatically fetch tokens from a Security Token Service without PKCE, with fallback to OIDC redirect flows and token caching capabilities.",
  "n": 2,
  "nn": "Incremental extension to existing Bearer auth; addresses known pain points (PKCE requirements, URI constraints) but builds on well-established mechanisms rather than introducing fundamentally new concepts.",
  "m": 3,
  "mn": "Protocol mechanism is defined with clear flow descriptions, though lacks detailed implementation guidance, test vectors, and security analysis depth needed for implementation readiness.",
  "o": 4,
  "on": "Significant overlap with existing OIDC/OAuth2 token endpoint patterns and device flow specifications; the automatic token fetch mechanism resembles existing STS integration patterns in enterprise contexts.",
  "mo": 2,
  "mon": "Single draft revision visible; no clear WG sponsorship or community adoption signals; appears to be individual submission without documented stakeholder interest or implementation feedback.",
  "r": 2,
  "rn": "Tangentially related to AI agents only insofar as agents may require authentication; draft addresses general HTTP client authentication rather than agent-specific identity, authorization, or capability patterns.",
  "c": ["Agent identity/auth", "Data formats/interop"]
}
```


```json
{
  "s": "SATP proposes a trust framework for establishing verifiable identity and governance of autonomous machines and AI agents through non-repudiable roots of trust. The 3-page draft outlines foundational concepts for attribution and trust in both digital and physical autonomous systems.",
  "n": 2,
  "nn": "Incremental contribution addressing known problem space; combines existing trust/identity concepts (PKI, attestation, governance) into autonomous agent context without substantial methodological innovation.",
  "m": 1,
  "mn": "Problem statement and high-level vision only; lacks protocol specification, message formats, cryptographic details, or implementation guidance despite claiming to 'specify' a protocol.",
  "o": 4,
  "on": "Significant conceptual overlap with existing work: TETRA, IETF RATS attestation frameworks, W3C DID specifications, and various autonomous vehicle trust standards; positioning relative to these not clearly differentiated.",
  "mo": 1,
  "mon": "Single dated draft (2026-05-02); no evidence of revisions, WG sponsorship, or community engagement; appears to be initial submission without active development trajectory.",
  "r": 4,
  "rn": "Directly relevant to AI agent identity, authentication, and governance challenges; addresses real need for autonomous system trust infrastructure in emerging deployment scenarios.",
  "c": [
    "Agent identity/auth",
    "Policy/governance",
    "A2A protocols",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "This draft specifies how EDHOC (Ephemeral Diffie-Hellman Over COSE) can be used with CoAP to establish OSCORE security contexts, with an optimization to combine the key exchange with the first secured transaction, reducing round trips in constrained IoT environments.",
  "n": 2,
  "nn": "Incremental contribution combining existing protocols (EDHOC + OSCORE + CoAP) with optimization techniques; no novel cryptographic or security concepts.",
  "m": 4,
  "mn": "Well-specified protocol integration with detailed mechanisms, examples, and security considerations; implementation-ready but lacks comprehensive test vectors.",
  "o": 3,
  "on": "Shares foundational concepts with EDHOC and OSCORE specs; combines existing work in a standardized manner with some novel optimization patterns.",
  "mo": 4,
  "mon": "Active IETF CoRE WG development with multiple revisions; strong adoption momentum for constrained IoT security standards.",
  "r": 1,
  "rn": "IoT/constrained device security protocol; not related to AI agents, autonomous systems, or machine learning workflows despite mentioning 'RESTful' concepts.",
  "c": ["Data formats/interop"]
}
```


```json
{
  "s": "This draft addresses context distribution optimization in multi-agent systems to reduce latency, token consumption, and improve task completion rates. It specifies scenarios, procedures, and optimizations for controlling context distribution across multiple agents in complex workflows.",
  "n": 2,
  "nn": "Incremental contribution focusing on a specific operational concern (context distribution) in multi-agent systems; lacks fundamental innovation in approach or methodology.",
  "m": 2,
  "mn": "Early sketch stage with abstract describing problem and goals but only 14 pages suggesting incomplete specification; lacks protocol details, examples, or implementation guidance.",
  "o": 3,
  "on": "Shares conceptual overlap with existing agent communication and state management work; context passing is well-established in distributed systems and agent literature.",
  "mo": 1,
  "mon": "No revision history visible; single draft submission with recent date suggests early-stage work lacking iterative development or community feedback cycles.",
  "r": 3,
  "rn": "Partially relevant to AI agent systems but focuses narrowly on context distribution mechanics rather than core agent coordination, reasoning, or safety concerns.",
  "c": [
    "A2A protocols",
    "ML traffic mgmt",
    "Data formats/interop",
    "Autonomous netops"
  ]
}
```


```json
{
  "s": "This draft proposes routing considerations for agent-to-agent communication in overlay networks above IP infrastructure, addressing cross-domain scenarios where AI agents with specialized skills need to interconnect. It identifies new networking requirements emerging from agentic network traffic patterns.",
  "n": 2,
  "nn": "Incremental application of existing routing concepts to a new use case (agent communication); lacks novel routing mechanisms or protocols specific to agent needs.",
  "m": 1,
  "mn": "Problem statement and motivation only; no routing protocols, mechanisms, or specifications defined; no examples, architectures, or implementation details provided.",
  "o": 4,
  "on": "Significant overlap with existing work on overlay networking, service mesh routing, and agent communication frameworks; concepts not differentiated from established patterns.",
  "mo": 1,
  "mon": "Appears to be early-stage exploratory draft with limited community engagement; no evidence of WG discussion, multiple revisions, or implementation activity.",
  "r": 3,
  "rn": "Partially relevant to AI agent networking; addresses agent-to-agent communication but lacks depth on core agent architecture, capability discovery, or agent-specific constraints that should drive routing decisions.",
  "c": [
    "A2A protocols",
    "Agent discovery/reg",
    "Data formats/interop",
    "ML traffic mgmt"
  ]
}
```


```json
{
  "s": "CHEQ proposes a protocol for human-in-the-loop confirmation of AI agent decisions before execution, with privacy-preserving credential handling. It integrates with MCP and A2A protocols using signed objects to prevent unwanted actions from hallucinations.",
  "n": 2,
  "nn": "Incremental contribution combining existing HITL concepts with protocol integration; human confirmation of agent actions is well-established practice, though protocol formalization adds modest value.",
  "m": 2,
  "mn": "Early sketch stage with abstract-level design; lacks detailed message formats, state machines, error handling, examples, and implementation guidance needed for interoperability.",
  "o": 4,
  "on": "Significant overlap with existing HITL frameworks, approval workflows in enterprise automation, and confirmation mechanisms in authorization protocols; positioning relative to MCP/A2A adoption unclear.",
  "mo": 1,
  "mon": "Single undated revision (2025-07-24); no evidence of WG discussion, community feedback, or iterative refinement; appears to be initial submission.",
  "r": 4,
  "rn": "Directly relevant to AI agent safety and human-agent interaction concerns; addresses legitimate hallucination/action risk but positioned as IETF protocol rather than application-layer pattern.",
  "c": [
    "Human-agent interaction",
    "AI safety/alignment",
    "A2A protocols",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Defines an ASIL-M profile for RATS that enables authorization decisions across multiple independent trust roots, introducing the Attestation Evidence Synthesis Protocol, Twin Attestation Policy Language (TAPL), and Canonical Attestation Record (CAR) for deterministic multi-root appraisal in AI inference systems.",
  "n": 3,
  "nn": "Incremental contribution combining existing RATS concepts with multi-root synthesis; the policy language and envelope format are useful but not fundamentally novel architectural innovations.",
  "m": 3,
  "mn": "Protocol mechanisms are defined with three artifacts, but lacks implementation examples, test vectors, and concrete deployment guidance; appears specification-ready but not fully mature.",
  "o": 3,
  "on": "Shares core concepts with RATS architecture, multi-attestation frameworks, and policy-driven authorization; TAPL resembles existing constrained policy languages; CAR extends rather than replaces existing RATS components.",
  "mo": 2,
  "mon": "Single revision draft from 2026; no evidence of WG adoption, multiple revisions, or community feedback; appears early-stage with limited momentum.",
  "r": 4,
  "rn": "Directly relevant to AI inference systems requiring cross-root authorization; addresses real trust and safety concerns in agent deployment, though framed narrowly around attestation rather than broader AI agent governance.",
  "c": [
    "Agent identity/auth",
    "Model serving/inference",
    "Policy/governance",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "VDAC defines a cryptographic protocol for bilateral agreements between content publishers and automated agents regarding programmatic data access terms. It operationalizes the bilateral commitment principle from VICDM by enabling parties to sign contracts and bind individual requests to agreed terms through verifiable signatures.",
  "n": 2,
  "nn": "Incremental contribution building on established concepts (VICDM, SAIP). Applies existing contract/signature mechanisms to agent-publisher agreements with limited technical novelty in the cryptographic approach itself.",
  "m": 3,
  "mn": "Defined protocol mechanism with clear structure (offer, acceptance, signing, per-request binding). Lacks implementation details, test vectors, and concrete examples. Companion spec dependency adds complexity to maturity assessment.",
  "o": 3,
  "on": "Shares conceptual overlap with OAuth2/SAML delegation frameworks, API contracts, and digital signature standards. Not a near-duplicate but operates in well-trodden space of cryptographic agreement protocols.",
  "mo": 2,
  "mon": "Single draft dated 2026 (future date suggests hypothetical). No indication of WG adoption, revisions, or community interest. Depends on VICDM/SAIP momentum which status is unclear.",
  "r": 4,
  "rn": "Directly relevant to AI agent authentication, authorization, and programmatic interactions. Addresses agent-to-service contracting which is core infrastructure for autonomous agent deployment and governance.",
  "c": [
    "A2A protocols",
    "Agent identity/auth",
    "Policy/governance",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "This draft standardizes the use of DRIP Entity Tags (DETs) as identifiers for trustworthy air domain awareness in unmanned aircraft systems, enabling privacy, authentication, and confidentiality across remote identification, traffic management, and advanced air mobility contexts.",
  "n": 2,
  "nn": "Incremental application of existing DRIP protocol mechanisms to specific use cases; primarily a standardization and consolidation effort rather than introducing fundamentally new concepts.",
  "m": 3,
  "mn": "Defined protocol mechanisms with clear usage patterns, though lacking detailed implementation examples, test vectors, or deployment guidance needed for production readiness.",
  "o": 3,
  "on": "Shares core concepts with existing DRIP/RID standards and overlaps moderately with UTM/AAM governance frameworks; extends prior work in defined directions rather than introducing independent approaches.",
  "mo": 2,
  "mon": "Single revision snapshot from 2026; limited evidence of community engagement or working group momentum; appears to be author-driven rather than collaborative development.",
  "r": 2,
  "rn": "Tangentially related to AI agents; addresses autonomous system identification and traffic management but focuses on protocol standardization rather than agent behavior, decision-making, or ML components.",
  "c": [
    "Agent identity/auth",
    "Data formats/interop",
    "Policy/governance",
    "Agent discovery/reg"
  ]
}
```


```json
{
  "s": "Proposes Trusted Path Routing to enforce that sensitive network traffic traverses only recently appraised trustworthy devices, combining attestation/RATS with routing policy. Addresses end-user concerns that encryption alone is insufficient for highly sensitive flows by adding device trustworthiness verification as a routing constraint.",
  "n": 2,
  "nn": "Incremental combination of existing concepts (RATS attestation + policy-based routing); core idea of trustworthiness-aware forwarding is not novel, though application to path selection is a useful engineering contribution.",
  "m": 3,
  "mn": "Appears to define protocol mechanisms and routing logic, likely includes some protocol details, but 32 pages suggests moderate specification depth; unclear if implementation examples or test vectors are included without reviewing full text.",
  "o": 3,
  "on": "Shares substantial conceptual overlap with zero-trust networking, attestation-based access control (RATS WG), and policy-based routing frameworks; positioning relative to existing ZTA/TEACVP initiatives not immediately clear from abstract.",
  "r": 1,
  "rn": "Not about AI agents or autonomous systems; addresses network infrastructure trustworthiness for sensitive traffic. Falls outside AI/agent scope unless interpreted broadly as autonomous network operations, which would be tangential at best.",
  "m": 2,
  "mon": "Single draft revision visible; no evidence of WG adoption or broader community momentum; appears to be individual contribution rather than WG-driven work.",
  "c": ["Autonomous netops", "Agent identity/auth", "Policy/governance"]
}
```


```json
{
  "s": "PSI proposes a cryptographic protocol enabling organizations to prove AI regulatory compliance (EU AI Act, NIST AI RMF, etc.) through zero-knowledge proofs and MPC consensus without revealing proprietary model details. The approach combines SHA-256 hash chains, Ed25519 signatures, Merkle proofs, and Groth16 ZK commitments over BN128 fields.",
  "n": 2,
  "nn": "Incremental combination of existing cryptographic primitives (ZK proofs, MPC, hash chains) applied to a new domain (AI compliance verification); the individual techniques are well-established.",
  "m": 2,
  "mn": "Early sketch with architectural overview but lacks implementation details, test vectors, concrete audit trail schemas, integration examples with actual regulatory frameworks, and performance/scalability analysis.",
  "o": 3,
  "on": "Shares conceptual overlap with attestation/audit protocols (e.g., RATS framework), compliance-as-code initiatives, and existing ZK proof systems for privacy-preserving computation; the specific AI compliance application is somewhat novel.",
  "m": 2,
  "mn": "Single revision dated 2026-03-18; unclear if this is from active WG or individual submission; no evidence of community adoption or regulatory stakeholder engagement yet.",
  "r": 4,
  "rn": "Directly relevant to AI governance and compliance verification; addresses real regulatory demand but focuses on policy/governance layer rather than core AI agent protocols or autonomous systems operation.",
  "c": [
    "Policy/governance",
    "Agent identity/auth",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```


```json
{
  "s": "AGTP-API specifies a contract layer for autonomous agent-server interactions, defining method catalogs, endpoint structures, schema validation, and runtime negotiation mechanisms. It consolidates and supersedes prior fragmented drafts on agent transfer protocols.",
  "n": 2,
  "nn": "Incremental formalization of agent-server API semantics; combines existing concerns (methods, paths, endpoints) without introducing fundamentally new protocol concepts.",
  "m": 3,
  "mn": "Well-defined specification with structured components (manifests, status codes, binding kinds) but limited evidence of implementation validation or real-world deployment testing.",
  "o": 4,
  "on": "Significant overlap with REST/gRPC API patterns; shares endpoint and method catalog concepts with existing service mesh and agent framework designs; attempts unification of prior Hood drafts.",
  "mo": 2,
  "mon": "Single recent revision (2026-05); no clear WG sponsorship or adoption signals; appears to be individual submission with limited community engagement visible.",
  "r": 4,
  "rn": "Directly relevant to autonomous agent standardization and agent-server communication; addresses interoperability but lacks explicit connection to broader AI safety or alignment concerns.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg",
    "Policy/governance"
  ]
}
```


```json
{
  "s": "ACAP proposes a JWT-based credentialing system for autonomous AI agents with scope delegation, audit logging, and human approval gates. It extends OAuth concepts to multi-agent pipelines with tamper-evident delegation chains and short-lived credentials.",
  "n": 3,
  "nn": "Applies familiar JWT/OAuth patterns to agent delegation; delegation depth tracking and instruction hashing are useful but represent incremental innovation over existing capability-based security models.",
  "m": 2,
  "mn": "Early draft stage; defines credential format and delegation rules but lacks implementation details, test vectors, security proofs, or concrete examples. No reference implementation evident.",
  "o": 3,
  "on": "Overlaps significantly with ZCAP-LD (capability delegation), Macaroons (nested delegation), and OAuth 2.0 token delegation patterns. The instruction hash concept is moderately novel but not sufficiently differentiated.",
  "mo": 1,
  "mon": "Single draft revision (2026-03-26 date suggests future submission); no evidence of WG adoption, community feedback iteration, or implementation uptake. Appears exploratory.",
  "r": 4,
  "rn": "Directly addresses critical AI agent orchestration needs: identity, authorization, multi-level delegation, and auditability. Highly relevant to agent security and human oversight.",
  "c": ["Agent identity/auth", "A2A protocols", "Human-agent interaction", "Policy/governance", "AI safety/alignment"]
}
```


```json
{
  "s": "Proposes an I2NSF-based framework for automated security management in 5G edge networks using Intent-Based Networking to translate high-level security intents into enforceable policies. The system distributes policies across network and application layers with closed-loop monitoring for adaptive, context-aware security enforcement in dynamic edge environments.",
  "n": 2,
  "nn": "Incremental combination of existing standards (I2NSF, IBN, NEF) applied to 5G security; integration approach is straightforward rather than introducing novel security or networking concepts.",
  "m": 2,
  "mn": "Early conceptual stage; abstract describes vision and architecture but lacks protocol details, policy language specifications, implementation guidance, or validation results.",
  "o": 4,
  "on": "Significant overlap with established I2NSF specification work and existing 5G security frameworks; combines well-known components (NEF, UE policy enforcement) without substantial differentiation.",
  "mo": 1,
  "mon": "Single revision draft from February 2026 with no evidence of WG adoption, implementation momentum, or community engagement; appears nascent in standards lifecycle.",
  "r": 2,
  "rn": "Tangentially related to autonomous networking concepts through IBN mention, but focuses on traditional security policy management rather than autonomous agent systems, distributed intelligence, or AI-driven decision-making.",
  "c": ["Policy/governance", "Autonomous netops", "Data formats/interop"]
}
```


```json
{
  "s": "Proposes Early Retransmit mechanism for TCP and SCTP to enable fast retransmission recovery with fewer duplicate acknowledgments when congestion windows are small, avoiding costly timeout-based retransmissions. Addresses a specific transport-layer inefficiency in scenarios with limited in-flight packets.",
  "n": 2,
  "nn": "Incremental improvement to TCP/SCTP behavior; optimization of existing fast retransmit logic rather than fundamental innovation.",
  "m": 4,
  "mn": "Well-defined protocol mechanism with clear triggering conditions and specification suitable for implementation; appears RFC-ready with established evaluation.",
  "o": 3,
  "on": "Shares conceptual space with existing TCP loss recovery mechanisms (fast retransmit, limited transmit); represents focused refinement rather than convergent duplication.",
  "mo": 2,
  "mon": "Single draft revision in 2024; narrow specialized topic limits broad community adoption momentum despite technical merit.",
  "r": 1,
  "rn": "Pure transport protocol optimization with no connection to AI agents, autonomous systems, or machine learning applications; false positive for AI/agent category.",
  "c": ["Other AI/agent"]
}
```


```json
{
  "s": "This draft extends the IETF RATS (Remote Attestation Procedures) architecture to support multiple coordinating verifiers assessing an attester's trustworthiness. It focuses on topological patterns and architectural considerations for multi-verifier systems in a format-neutral manner.",
  "n": 2,
  "nn": "Incremental extension of established RATS architecture; the concept of multiple verifiers is a natural scaling concern but represents straightforward architectural elaboration rather than fundamental innovation.",
  "m": 2,
  "mn": "Early-stage draft presenting architectural patterns without detailed protocol specifications, implementation examples, or concrete coordination mechanisms; lacks maturity for deployment guidance.",
  "o": 3,
  "on": "Shares core concepts with existing RATS specifications and distributed trust frameworks; multi-party attestation patterns have been explored in related security literature, though specific application to RATS topologies is somewhat novel.",
  "mo": 1,
  "mon": "Single revision in February 2026 with no evidence of WG adoption, community discussion, or iterative development; appears to be an initial submission without sustained momentum.",
  "r": 2,
  "rn": "Tangentially related to AI agent security; relevant to agent identity and authentication infrastructure but not directly addressing AI-specific challenges, agent coordination protocols, or autonomous system safety.",
  "c": ["Agent identity/auth", "Policy/governance", "Other AI/agent"]
}
```


```json
{
  "s": "Proposes specializing AI models for Intent-Based Networking (IBN) to enable scalable, efficient generative AI deployment in network operations. Addresses the intersection of generative AI and intent-driven network automation.",
  "n": 2,
  "nn": "Incremental application of existing generative AI techniques to networking domain; core novelty lies in domain-specific model specialization rather than methodological innovation.",
  "m": 2,
  "mn": "Early-stage draft presenting concepts and motivation; lacks detailed protocol specifications, implementation examples, or validation results needed for production readiness.",
  "o": 3,
  "on": "Shares conceptual overlap with existing IBN work and general AI-for-networking efforts; positioning within broader generative AI landscape could be clearer.",
  "mo": 1,
  "mon": "Limited revision history and community engagement evident from single dated version; unclear WG sponsorship or adoption trajectory.",
  "r": 4,
  "rn": "Directly relevant to AI-driven network operations and autonomous networking; generative AI application to IBN is timely and practically motivated.",
  "c": ["Autonomous netops", "ML traffic mgmt", "Model serving/inference", "Policy/governance", "Data formats/interop"]
}
```


```json
{
  "s": "Delta-1 proposes a SCITT profile for creating binary-verdict settlement receipts that prove AI agent decisions met three simultaneous accountability conditions: decision evidence sealing, strategic intent isolation, and authorized recording. The approach inherits SCITT's transparency-log semantics while adding domain-specific requirements for regulated industries like finance and healthcare.",
  "n": 2,
  "nn": "Incremental application of existing SCITT framework to a new domain; the core novelty is constraining SCITT to binary verdicts and three specific conditions rather than introducing fundamentally new cryptographic or architectural mechanisms.",
  "m": 2,
  "mn": "Early sketch stage with abstract requirements (C1-C3) but lacks concrete protocol details, message formats, verification algorithms, or implementation guidance; no test vectors or interoperability examples provided.",
  "o": 4,
  "on": "Significant conceptual overlap with SCITT core (receipts, transparency logs, attestation); borrows heavily from existing supply-chain trust models without substantial differentiation for AI-specific challenges beyond the three conditions.",
  "m": 2,
  "mon": "Single dated revision (2026-04-15) with no evidence of WG discussion, multiple iterations, or community adoption; appears nascent.",
  "r": 3,
  "rn": "Partially relevant to AI agent accountability but focuses narrowly on settlement receipts and decision sealing rather than broader agent autonomy, alignment, safety, or reasoning transparency; accountability framing is governance-centric rather than technical AI challenge.",
  "c": [
    "Policy/governance",
    "Agent identity/auth",
    "Data formats/interop",
    "AI safety/alignment"
  ]
}
```