diff --git a/data/drafts.db b/data/drafts.db index 5631315..b8a7b83 100644 Binary files a/data/drafts.db and b/data/drafts.db differ diff --git a/docs/data/drafts.json b/docs/data/drafts.json index 93b1381..ddae230 100644 --- a/docs/data/drafts.json +++ b/docs/data/drafts.json @@ -139,10 +139,10 @@ { "name": "draft-ietf-lake-app-profiles", "title": "Coordinating the Use of Application Profiles for Ephemeral Diffie-Hellman Over COSE (EDHOC)", - "date": "2025-11-21", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-app-profiles/", - "pages": 48, + "pages": 61, "group": "individual", "score": 4.6, "novelty": 4, @@ -162,6 +162,32 @@ "relevance_note": "Critical for EDHOC deployment and interoperability across various applications", "doc_status": "" }, + { + "name": "draft-ietf-lake-edhoc", + "title": "Ephemeral Diffie-Hellman Over COSE (EDHOC)", + "date": "2024-03-21", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-edhoc/", + "pages": 113, + "group": "individual", + "score": 4.6, + "novelty": 4, + "maturity": 5, + "overlap": 2, + "momentum": 5, + "relevance": 5, + "categories": [ + "A2A protocols", + "Agent identity/auth" + ], + "summary": "Specifies EDHOC, a compact authenticated Diffie-Hellman key exchange protocol for constrained environments. Provides mutual authentication, forward secrecy, and identity protection using COSE, CBOR, and CoAP.", + "novelty_note": "Strong novelty in creating lightweight authenticated key exchange for constrained devices", + "maturity_note": "Mature 113-page specification from IETF working group, well-developed protocol", + "overlap_note": "Unique approach to lightweight authenticated key exchange, minimal overlap", + "momentum_note": "Official IETF working group draft with strong momentum and adoption", + "relevance_note": "Extremely relevant for IoT security and constrained device communications", + "doc_status": "" + }, { "name": "draft-goswami-agentic-jwt", "title": "Secure Intent Protocol: JWT Compatible Agentic Identity and Workflow Management", @@ -432,7 +458,7 @@ { "name": "draft-ietf-hpke-hpke", "title": "Hybrid Public Key Encryption", - "date": "2025-11-04", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-hpke-hpke/", "pages": 85, @@ -674,7 +700,7 @@ { "name": "draft-ietf-sshm-mlkem-hybrid-kex", "title": "PQ/T Hybrid Key Exchange with ML-KEM in SSH", - "date": "2026-02-26", + "date": "2026-03-03", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-sshm-mlkem-hybrid-kex/", "pages": 15, @@ -699,10 +725,10 @@ { "name": "draft-ietf-tls-extended-key-update", "title": "Extended Key Update for Transport Layer Security (TLS) 1.3", - "date": "2026-02-19", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-tls-extended-key-update/", - "pages": 40, + "pages": 41, "group": "individual", "score": 4.25, "novelty": 4, @@ -800,6 +826,58 @@ "relevance_note": "Extremely relevant for emerging interactive AI applications requiring real-time multimodal delivery", "doc_status": "" }, + { + "name": "draft-barnes-hpke-hpke", + "title": "Hybrid Public Key Encryption", + "date": "2025-05-11", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-barnes-hpke-hpke/", + "pages": 125, + "group": "individual", + "score": 4.25, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 5, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Defines hybrid public key encryption scheme supporting authenticated variants and flexible cryptographic primitives. Provides framework for secure encryption with multiple authentication modes.", + "novelty_note": "Novel hybrid approach combining multiple cryptographic primitives with authentication options", + "maturity_note": "Comprehensive specification with detailed instantiations using standard primitives", + "overlap_note": "Unique hybrid approach with limited overlap to existing encryption schemes", + "momentum_note": "CFRG product with strong cryptographic research backing", + "relevance_note": "Very high relevance as fundamental cryptographic building block for secure communications", + "doc_status": "" + }, + { + "name": "draft-ietf-grow-va", + "title": "FIB Suppression with Virtual Aggregation", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-grow-va/", + "pages": 24, + "group": "individual", + "score": 4.25, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 5, + "categories": [ + "Autonomous netops", + "ML traffic mgmt" + ], + "summary": "Virtual Aggregation (VA) enables FIB suppression to reduce routing table size in routers by an order of magnitude. The approach can be deployed autonomously by ISPs without inter-ISP cooperation and coexists with legacy equipment.", + "novelty_note": "Novel approach to addressing DFRT growth through FIB suppression", + "maturity_note": "Well-developed 24-page document from established IETF working group", + "overlap_note": "Some related work on routing table optimization but unique approach", + "momentum_note": "IETF working group draft with strong institutional backing", + "relevance_note": "Directly addresses critical Internet scaling challenges", + "doc_status": "" + }, { "name": "draft-narajala-ans", "title": "Agent Name Service (ANS): A Universal Directory for Secure AI Agent Discovery and Interoperability", @@ -911,7 +989,7 @@ { "name": "draft-li-dmsc-macp", "title": "Multi-agent Collaboration Protocol Suite", - "date": "2026-02-26", + "date": "2026-02-28", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-li-dmsc-macp/", "pages": 21, @@ -1016,10 +1094,10 @@ { "name": "draft-cui-dns-native-agent-naming-resolution", "title": "DNS-Native AI Agent Naming and Resolution", - "date": "2025-12-22", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-cui-dns-native-agent-naming-resolution/", - "pages": 26, + "pages": 31, "group": "individual", "score": 4.1, "novelty": 4, @@ -1040,13 +1118,66 @@ "relevance_note": "Extremely relevant for scalable agent ecosystems and internet integration", "doc_status": "" }, + { + "name": "draft-cowles-aee", + "title": "Agent Envelope Exchange (AEE): A Minimal JSON Envelope Format for Inter-Agent Communication", + "date": "2026-02-28", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-cowles-aee/", + "pages": 21, + "group": "individual", + "score": 4.1, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 5, + "categories": [ + "A2A protocols", + "Data formats/interop", + "Agent identity/auth" + ], + "summary": "Agent Envelope Exchange defines a minimal 14-field JSON envelope format for inter-agent communication. It separates message routing concerns from payload semantics to enable portable workflows across heterogeneous agent frameworks.", + "novelty_note": "Clean separation of envelope and payload is novel for agent communication", + "maturity_note": "Comprehensive 21-page specification with clear conformance levels", + "overlap_note": "Some overlap with messaging standards but agent-specific focus is unique", + "momentum_note": "Individual submission but addresses emerging need for agent interop", + "relevance_note": "Highly relevant as foundational infrastructure for agent ecosystems", + "doc_status": "" + }, + { + "name": "draft-annevk-johannhof-httpbis-cookies", + "title": "Cookies: HTTP State Management Mechanism", + "date": "2025-04-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-annevk-johannhof-httpbis-cookies/", + "pages": 43, + "group": "individual", + "score": 4.1, + "novelty": 2, + "maturity": 5, + "overlap": 1, + "momentum": 5, + "relevance": 5, + "categories": [ + "Data formats/interop", + "Policy/governance" + ], + "summary": "Comprehensive revision of HTTP cookie mechanism, updating RFC 6265. Addresses security and privacy issues while maintaining backward compatibility for widely deployed technology.", + "novelty_note": "Incremental update to existing standard rather than novel approach", + "maturity_note": "Mature 43-page specification ready to obsolete existing RFCs", + "overlap_note": "Direct successor to RFC 6265, minimal overlap with other efforts", + "momentum_note": "Critical web infrastructure update with broad industry impact", + "relevance_note": "Essential for web security and privacy, affects all web interactions", + "doc_status": "" + }, { "name": "draft-liu-agent-operation-authorization", "title": "Agent Operation Authorization", - "date": "2025-11-25", + "date": "2026-02-28", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-liu-agent-operation-authorization/", - "pages": 15, + "pages": 24, "group": "individual", "score": 4.05, "novelty": 4, @@ -1283,6 +1414,84 @@ "relevance_note": "Extremely relevant for optimizing distributed AI inference systems", "doc_status": "" }, + { + "name": "draft-rosenberg-ai-protocols", + "title": "Framework, Use Cases and Requirements for AI Agent Protocols", + "date": "2025-05-05", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-rosenberg-ai-protocols/", + "pages": 26, + "group": "individual", + "score": 4.05, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 5, + "categories": [ + "A2A protocols", + "Agent discovery/reg", + "Policy/governance" + ], + "summary": "Establishes framework for AI agent communications on the Internet, surveying existing protocols like MCP and A2A. Defines use cases and requirements to guide future IETF standardization efforts.", + "novelty_note": "First comprehensive framework for AI agent protocol standardization", + "maturity_note": "Framework document with clear structure but early stage", + "overlap_note": "Some overlap with existing AI protocol efforts but unique in scope", + "momentum_note": "High interest area with strong industry momentum", + "relevance_note": "Directly addresses core AI agent communication needs", + "doc_status": "" + }, + { + "name": "draft-tschofenig-lamps-nonce-cmp-est", + "title": "Nonce-based Freshness for Remote Attestation in Certificate Signing Requests (CSRs) for the Certification Management Protocol (CMP) and for Enrollment over Secure Transport (EST)", + "date": "2024-04-03", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-tschofenig-lamps-nonce-cmp-est/", + "pages": 12, + "group": "individual", + "score": 4.05, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 5, + "categories": [ + "Agent identity/auth" + ], + "summary": "Specifies nonce mechanisms for demonstrating freshness of attestation evidence in certificate signing requests. Covers both CMP and EST protocols.", + "novelty_note": "Novel integration of attestation freshness with certificate protocols", + "maturity_note": "Building on established protocols but new use case", + "overlap_note": "Some overlap with general attestation work", + "momentum_note": "Growing interest in attestation and zero-trust architectures", + "relevance_note": "Highly relevant for secure device provisioning and attestation", + "doc_status": "" + }, + { + "name": "draft-papon-lake-pq-edhoc", + "title": "Post-Quantum EDHOC - Initiator and Responder using signature and/or KEM", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-papon-lake-pq-edhoc/", + "pages": 49, + "group": "individual", + "score": 4.05, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 5, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Extends EDHOC protocol with quantum-resistant features using post-quantum signatures and KEMs. Provides 3-message and 3-or-4-message variants balancing security and complexity.", + "novelty_note": "Novel hybrid approach combining signatures and KEMs for quantum resistance in EDHOC", + "maturity_note": "Solid technical approach but needs implementation validation and interoperability testing", + "overlap_note": "Some overlap with other post-quantum EDHOC proposals but unique hybrid approach", + "momentum_note": "Strong momentum given urgency of post-quantum cryptography adoption", + "relevance_note": "Highly relevant for securing IoT and constrained device communications against quantum threats", + "doc_status": "" + }, { "name": "draft-steele-agent-considerations", "title": "Agent Considerations", @@ -1340,10 +1549,10 @@ { "name": "draft-mishra-oauth-agent-grants", "title": "Delegated Agent Authorization Protocol (DAAP)", - "date": "2026-02-27", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-mishra-oauth-agent-grants/", - "pages": 27, + "pages": 40, "group": "individual", "score": 4.0, "novelty": 4, @@ -1474,6 +1683,110 @@ "relevance_note": "High relevance for scalable AI agent communication infrastructure", "doc_status": "" }, + { + "name": "draft-nandakumar-ai-agent-moq-transport", + "title": "MOQ Transport for Agent Protocols", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-nandakumar-ai-agent-moq-transport/", + "pages": 23, + "group": "individual", + "score": 4.0, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 4, + "categories": [ + "A2A protocols", + "Data formats/interop" + ], + "summary": "Defines abstraction layer for using MOQ Transport as unified substrate for inter-agent communication. Demonstrates application to A2A and MCP protocols.", + "novelty_note": "Novel application of MOQT to agent protocols with specific abstraction layer design", + "maturity_note": "Detailed technical specification with concrete protocol mappings and examples", + "overlap_note": "Builds on MOQT but creates new abstraction specifically for agent communication", + "momentum_note": "Strong technical foundation and addresses real interoperability challenges", + "relevance_note": "Important for standardizing agent communication transport with real-time requirements", + "doc_status": "" + }, + { + "name": "draft-ietf-dnsop-dnssec-bootstrapping", + "title": "Automatic DNSSEC Bootstrapping using Authenticated Signals from the Zone's Operator", + "date": "2024-07-16", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-bootstrapping/", + "pages": 18, + "group": "individual", + "score": 4.0, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 4, + "categories": [ + "Autonomous netops", + "Policy/governance" + ], + "summary": "Introduces automated DNSSEC bootstrapping using authenticated signals from zone operators. Enables cryptographic validation of CDS/CDNSKEY records without out-of-band processes.", + "novelty_note": "Novel in-band method for DNSSEC bootstrapping replacing manual processes", + "maturity_note": "Mature specification from established working group with clear implementation path", + "overlap_note": "Updates existing RFCs but provides unique automated approach", + "momentum_note": "Active IETF working group item with collaborative development on GitHub", + "relevance_note": "Highly relevant for DNS infrastructure automation and security", + "doc_status": "" + }, + { + "name": "draft-kwiatkowski-tls-ecdhe-mlkem", + "title": "Post-quantum hybrid ECDHE-MLKEM Key Agreement for TLSv1.3", + "date": "2025-02-26", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-kwiatkowski-tls-ecdhe-mlkem/", + "pages": 9, + "group": "individual", + "score": 4.0, + "novelty": 3, + "maturity": 4, + "overlap": 3, + "momentum": 5, + "relevance": 5, + "categories": [ + "Other AI/agent" + ], + "summary": "Defines three hybrid key agreement methods for TLS 1.3 combining post-quantum ML-KEM with elliptic curve Diffie-Hellman. Provides concrete ciphersuites for quantum-safe TLS.", + "novelty_note": "Standard application of established hybrid approach to TLS, well-executed but incremental", + "maturity_note": "Mature specification with clear definitions and practical focus", + "overlap_note": "Moderate overlap with other TLS post-quantum proposals but different KEM choices", + "momentum_note": "Very high momentum due to NIST ML-KEM standardization and TLS deployment needs", + "relevance_note": "Extremely relevant for widespread TLS quantum readiness", + "doc_status": "" + }, + { + "name": "draft-mapmw-task-discovery", + "title": "Task discovery in agentic networks", + "date": "2026-03-01", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-mapmw-task-discovery/", + "pages": 21, + "group": "individual", + "score": 4.0, + "novelty": 4, + "maturity": 4, + "overlap": 3, + "momentum": 3, + "relevance": 5, + "categories": [ + "Agent discovery/reg", + "A2A protocols", + "Human-agent interaction" + ], + "summary": "Defines an architectural framework for task-centric agent discovery where task owners publish structured task cards to platforms. Autonomous agents can discover tasks, negotiate terms, and coordinate multi-agent collaboration through defined functional layers.", + "novelty_note": "Task-centric approach is novel complement to agent-to-agent discovery", + "maturity_note": "Thorough 21-page architecture with survey of existing approaches", + "overlap_note": "Acknowledges and builds on existing agent discovery mechanisms", + "momentum_note": "Individual submission but addresses clear gap in current approaches", + "relevance_note": "Essential for enabling open agent marketplaces and collaboration", + "doc_status": "" + }, { "name": "draft-dunbar-neotec-ac-te-applicability", "title": "Applying Attachmet Circuit and Traffic Engineering YANG Data Model to Edge AI Use Case", @@ -1584,10 +1897,10 @@ { "name": "draft-ietf-lake-authz", "title": "Lightweight Authorization using Ephemeral Diffie-Hellman Over COSE (ELA)", - "date": "2025-11-21", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-authz/", - "pages": 48, + "pages": 44, "group": "individual", "score": 3.9, "novelty": 4, @@ -1610,7 +1923,7 @@ { "name": "draft-ietf-ace-coap-est-oscore", "title": "Protecting EST Payloads with OSCORE", - "date": "2025-10-20", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-ace-coap-est-oscore/", "pages": 23, @@ -1661,11 +1974,11 @@ }, { "name": "draft-nandakumar-agent-sd-jwt", - "title": "Selective Disclosure for Agent Discovery and Identity Management (SD- Agent)", - "date": "2025-10-20", + "title": "SD Agent: Selective Disclosure for Agent Discovery and Identity Management", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-nandakumar-agent-sd-jwt/", - "pages": 31, + "pages": 30, "group": "individual", "score": 3.9, "novelty": 4, @@ -2007,6 +2320,32 @@ "relevance_note": "Relevant for AI applications requiring low latency, but general networking improvement", "doc_status": "" }, + { + "name": "draft-klrc-aiagent-auth", + "title": "AI Agent Authentication and Authorization", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-klrc-aiagent-auth/", + "pages": 26, + "group": "individual", + "score": 3.85, + "novelty": 3, + "maturity": 4, + "overlap": 3, + "momentum": 4, + "relevance": 5, + "categories": [ + "Agent identity/auth", + "A2A protocols" + ], + "summary": "Describes authentication and authorization framework for AI agents using existing standards like WIMSE and OAuth 2.0. Focuses on applying current protocols rather than creating new ones.", + "novelty_note": "Practical approach leveraging existing standards, though AI agent auth is increasingly studied", + "maturity_note": "Well-developed framework building on established protocols with clear implementation path", + "overlap_note": "Builds heavily on WIMSE and OAuth but applies them to new AI agent context", + "momentum_note": "Strong foundation in existing IETF work with clear industry need", + "relevance_note": "Critical need as AI agents proliferate and require secure authentication mechanisms", + "doc_status": "" + }, { "name": "draft-jurkovikj-httpapi-agentic-state", "title": "HTTP Profile for Synchronized Resource State (Agentic State Transfer)", @@ -2140,6 +2479,57 @@ "relevance_note": "Highly relevant for mobility and multi-transport scenarios, addresses real operational needs", "doc_status": "" }, + { + "name": "draft-ietf-dtn-dtnma", + "title": "DTN Management Architecture", + "date": "2024-11-07", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-dtn-dtnma/", + "pages": 59, + "group": "individual", + "score": 3.85, + "novelty": 4, + "maturity": 4, + "overlap": 1, + "momentum": 4, + "relevance": 3, + "categories": [ + "Autonomous netops", + "A2A protocols" + ], + "summary": "Defines management architecture for Delay-Tolerant Networks operating in challenged environments with long delays and frequent disruptions. Emphasizes asynchronous transport and autonomous local control.", + "novelty_note": "Novel approach to network management for extremely challenging network conditions", + "maturity_note": "Comprehensive 59-page specification with detailed architecture and technical depth", + "overlap_note": "Unique focus on DTN management with little overlap in existing network management approaches", + "momentum_note": "IETF working group draft with specialized but dedicated community support", + "relevance_note": "Relevant for specialized environments like space networks but limited general applicability", + "doc_status": "" + }, + { + "name": "draft-yang-dynamic-ecn-threshold", + "title": "Coupling ECN Marking Thresholds with Dynamic Buffer Allocation", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-yang-dynamic-ecn-threshold/", + "pages": 12, + "group": "individual", + "score": 3.85, + "novelty": 4, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "ML traffic mgmt" + ], + "summary": "Proposes coupling ECN marking thresholds with dynamic buffer allocation to prevent misalignment issues. Provides deterministic algorithm to maintain adaptive relationship between marking thresholds and buffer capacity.", + "novelty_note": "Novel approach to ECN threshold management addressing real operational problems", + "maturity_note": "Well-defined problem with concrete solution and reference algorithm", + "overlap_note": "Limited overlap with existing ECN work, addresses specific dynamic buffer scenario", + "momentum_note": "Addresses practical network operations issue but narrow deployment scope", + "relevance_note": "Highly relevant for modern network equipment with dynamic buffer management", + "doc_status": "" + }, { "name": "draft-ramadan-mboned-sonar", "title": "SONAR: Statistical Observation Network for Attestation and Reach", @@ -2218,6 +2608,57 @@ "relevance_note": "Very relevant for autonomous satellite operations and space-based networking", "doc_status": "" }, + { + "name": "draft-ar-emu-pqc-eapaka", + "title": "Enhancing Security in EAP-AKA' with Hybrid Post-Quantum Cryptography", + "date": "2025-03-17", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ar-emu-pqc-eapaka/", + "pages": 13, + "group": "individual", + "score": 3.8, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 4, + "categories": [ + "Other AI/agent" + ], + "summary": "Enhances EAP-AKA' forward secrecy with post-quantum/traditional hybrid cryptography to protect against future quantum computer threats. Builds on RFC9678 by replacing ECDHE with quantum-safe algorithms.", + "novelty_note": "Novel application of PQ/T hybrid approach to EAP-AKA', addressing specific quantum threats to cellular authentication", + "maturity_note": "Early draft with clear problem statement but implementation details need refinement", + "overlap_note": "Some overlap with general PQ hybrid work but specific to EAP-AKA' protocol", + "momentum_note": "Strong momentum given urgent need for post-quantum migration in cellular networks", + "relevance_note": "High relevance for mobile network security and quantum readiness", + "doc_status": "" + }, + { + "name": "draft-ietf-core-oscore-edhoc", + "title": "Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)", + "date": "2024-11-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-core-oscore-edhoc/", + "pages": 33, + "group": "individual", + "score": 3.8, + "novelty": 3, + "maturity": 4, + "overlap": 1, + "momentum": 4, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Specifies how to run EDHOC over CoAP to establish OSCORE security contexts for constrained environments. Includes optimizations to combine EDHOC execution with first OSCORE transaction.", + "novelty_note": "Good integration work with useful optimization for reducing round trips", + "maturity_note": "Well-developed specification with comprehensive coverage of integration scenarios", + "overlap_note": "Unique integration of EDHOC with CoAP/OSCORE", + "momentum_note": "Strong momentum in IoT security standardization", + "relevance_note": "High relevance for IoT and constrained device security", + "doc_status": "" + }, { "name": "draft-chen-ai-agent-auth-new-requirements", "title": "New requirements for Authentication and Authorization in the AI Agents era", @@ -2484,6 +2925,33 @@ "relevance_note": "Highly relevant for ensuring standards consider broader stakeholder impacts", "doc_status": "" }, + { + "name": "draft-lkspa-wimse-verifiable-geo-fence", + "title": "Privacy Preserving Verifiable Geofencing with Residency Proofs for Sovereign Workloads", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-lkspa-wimse-verifiable-geo-fence/", + "pages": 22, + "group": "individual", + "score": 3.75, + "novelty": 5, + "maturity": 2, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Policy/governance", + "AI safety/alignment" + ], + "summary": "Defines hardware-rooted cryptographic framework for verifying workload location without compromising privacy using zero-knowledge proofs. Establishes silicon-to-workload chain of trust for sovereign computing environments.", + "novelty_note": "Novel combination of hardware attestation, geofencing, and ZK proofs", + "maturity_note": "Complex early-stage proposal requiring significant development", + "overlap_note": "Some overlap with attestation work but unique privacy approach", + "momentum_note": "Growing interest in sovereign computing and privacy-preserving location", + "relevance_note": "Highly relevant for secure AI workload deployment and compliance", + "doc_status": "" + }, { "name": "draft-scim-agent-extension", "title": "SCIM Agents and Agentic Applications Extension", @@ -2673,10 +3141,10 @@ { "name": "draft-ietf-lake-ra", "title": "Remote attestation over EDHOC", - "date": "2025-11-21", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-ra/", - "pages": 30, + "pages": 31, "group": "individual", "score": 3.7, "novelty": 3, @@ -2825,6 +3293,58 @@ "relevance_note": "Moderately relevant to AI agents in communication systems but different domain", "doc_status": "" }, + { + "name": "draft-ietf-websec-mime-sniff", + "title": "Media Type Sniffing", + "date": "2024-09-24", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-websec-mime-sniff/", + "pages": 24, + "group": "individual", + "score": 3.7, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 4, + "categories": [ + "Data formats/interop", + "Policy/governance" + ], + "summary": "Describes algorithm for determining effective media type of HTTP responses. Balances security and compatibility when Content-Type headers are incorrect.", + "novelty_note": "Formalizes existing browser behavior into standard algorithm", + "maturity_note": "Well-developed specification addressing real interoperability issues", + "overlap_note": "Related to HTTP and web security standards", + "momentum_note": "Active IETF working group with recent updates", + "relevance_note": "High relevance for web security and interoperability", + "doc_status": "" + }, + { + "name": "draft-song-lake-ra", + "title": "Remote attestation over EDHOC", + "date": "2025-01-13", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-song-lake-ra/", + "pages": 26, + "group": "individual", + "score": 3.7, + "novelty": 4, + "maturity": 3, + "overlap": 3, + "momentum": 4, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "A2A protocols" + ], + "summary": "Specifies how to perform remote attestation as part of the EDHOC key exchange protocol. Based on the RATS architecture for lightweight authenticated key exchange.", + "novelty_note": "Good novelty in integrating remote attestation with EDHOC protocol", + "maturity_note": "Well-developed 26-page specification building on established protocols", + "overlap_note": "Overlaps with general remote attestation work but specific EDHOC integration", + "momentum_note": "Recent draft with active development, builds on mature EDHOC work", + "relevance_note": "Very relevant for IoT and constrained device security requiring attestation", + "doc_status": "" + }, { "name": "draft-gaikwad-south-authorization", "title": "SOUTH: Stochastic Authorization for Agent and Service Requests", @@ -2908,10 +3428,10 @@ { "name": "draft-ni-a2a-ai-agent-security-requirements", "title": "Security Requirements for AI Agents", - "date": "2025-11-02", + "date": "2026-02-28", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ni-a2a-ai-agent-security-requirements/", - "pages": 11, + "pages": 14, "group": "individual", "score": 3.65, "novelty": 3, @@ -2988,10 +3508,10 @@ { "name": "draft-pocero-authkem-edhoc", "title": "KEM-based Authentication for EDHOC", - "date": "2025-10-25", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-pocero-authkem-edhoc/", - "pages": 41, + "pages": 42, "group": "individual", "score": 3.65, "novelty": 4, @@ -3442,6 +3962,138 @@ "relevance_note": "Highly relevant as AI assistants become integrated into communication systems", "doc_status": "" }, + { + "name": "draft-liu-agent-protocol-over-moq", + "title": "Agent Protocol over MoQ", + "date": "2026-03-03", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-liu-agent-protocol-over-moq/", + "pages": 22, + "group": "individual", + "score": 3.65, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "A2A protocols", + "Data formats/interop" + ], + "summary": "Specifies agent-to-agent communication framework over Media over QUIC protocol. Provides structured, low-latency communication with session management and data fragmentation.", + "novelty_note": "Novel application of MoQ for agent communication with comprehensive framework", + "maturity_note": "Well-detailed at 22 pages but still emerging technology", + "overlap_note": "Builds on MoQ but provides unique agent communication layer", + "momentum_note": "Good technical depth suggests active development", + "relevance_note": "Highly relevant for emerging agent communication needs", + "doc_status": "" + }, + { + "name": "draft-chen-oauth-scope-agent-extensions", + "title": "Structured and Constraint Extensions for OAuth Scopes", + "date": "2026-03-01", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-chen-oauth-scope-agent-extensions/", + "pages": 12, + "group": "individual", + "score": 3.65, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Policy/governance" + ], + "summary": "Extends OAuth 2.0 scope parameter with structured syntax for fine-grained authorization of AI agent capabilities. Addresses permission management for modular agent components.", + "novelty_note": "Novel structured approach to OAuth scopes for agent authorization", + "maturity_note": "Well-developed specification with detailed syntax and use cases", + "overlap_note": "Extends OAuth but provides unique agent-specific capabilities", + "momentum_note": "Detailed specification suggests good development momentum", + "relevance_note": "Highly relevant for agent security and authorization needs", + "doc_status": "" + }, + { + "name": "draft-dunbar-agent-attachment", + "title": "Agent Attachment Protocol", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-dunbar-agent-attachment/", + "pages": 15, + "group": "individual", + "score": 3.65, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent discovery/reg", + "Agent identity/auth", + "Autonomous netops" + ], + "summary": "Describes protocol for autonomous agents to securely attach to overlay network infrastructure. Covers identity validation, capability exchange, and session establishment.", + "novelty_note": "Network attachment specifically designed for autonomous agents is a new concept", + "maturity_note": "Clear protocol definition but needs more detail on security and scalability aspects", + "overlap_note": "Some similarity to general attachment protocols but specifically designed for agents", + "momentum_note": "Addresses fundamental need but limited visible industry adoption yet", + "relevance_note": "Essential capability as agents become more autonomous and network-distributed", + "doc_status": "" + }, + { + "name": "draft-ietf-vwrap-authentication", + "title": "VWRAP Trust Model and User Authentication", + "date": "2024-09-24", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-vwrap-authentication/", + "pages": 16, + "group": "individual", + "score": 3.65, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "A2A protocols", + "Human-agent interaction" + ], + "summary": "Establishes authentication for Virtual World Region Agent Protocol. Verifies user credentials before granting control over user's agent and digital assets.", + "novelty_note": "Novel application of authentication to virtual world agents", + "maturity_note": "Solid specification but limited to virtual world domain", + "overlap_note": "Some overlap with general authentication protocols", + "momentum_note": "IETF working group but specialized application area", + "relevance_note": "Highly relevant for virtual world and metaverse applications", + "doc_status": "" + }, + { + "name": "draft-tiloca-lake-app-profiles", + "title": "Coordinating the Use of Application Profiles for Ephemeral Diffie-Hellman Over COSE (EDHOC)", + "date": "2024-12-09", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-tiloca-lake-app-profiles/", + "pages": 32, + "group": "individual", + "score": 3.65, + "novelty": 4, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Data formats/interop", + "Agent discovery/reg" + ], + "summary": "Defines coordination mechanisms for EDHOC application profiles including discovery, canonical representation, and well-known profiles. Addresses out-of-band parameter agreement challenges.", + "novelty_note": "Novel approach to profile coordination and discovery for EDHOC deployments", + "maturity_note": "Comprehensive specification but implementation experience limited", + "overlap_note": "Complements other EDHOC work without significant duplication", + "momentum_note": "Recent activity and detailed specification suggests moderate momentum", + "relevance_note": "Addresses important operational deployment challenges for EDHOC", + "doc_status": "" + }, { "name": "draft-mozleywilliams-dnsop-dnsaid", "title": "DNS for AI Discovery", @@ -3497,10 +4149,10 @@ { "name": "draft-ietf-ace-edhoc-oscore-profile", "title": "Ephemeral Diffie-Hellman Over COSE (EDHOC) and Object Security for Constrained Environments (OSCORE) Profile for Authentication and Authorization for Constrained Environments (ACE)", - "date": "2025-10-20", + "date": "2026-03-01", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-ace-edhoc-oscore-profile/", - "pages": 91, + "pages": 89, "group": "individual", "score": 3.6, "novelty": 3, @@ -3547,6 +4199,33 @@ "relevance_note": "Very relevant for AI workload management and network optimization", "doc_status": "" }, + { + "name": "draft-ietf-anima-brski-ae", + "title": "BRSKI-AE: Alternative Enrollment Protocols in BRSKI", + "date": "2025-03-03", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-anima-brski-ae/", + "pages": 43, + "group": "individual", + "score": 3.6, + "novelty": 3, + "maturity": 4, + "overlap": 3, + "momentum": 4, + "relevance": 4, + "categories": [ + "Autonomous netops", + "Agent identity/auth", + "Agent discovery/reg" + ], + "summary": "Extends BRSKI protocol to support alternative certificate enrollment mechanisms beyond EST, particularly CMP. Enables more flexible automated device onboarding in enterprise networks.", + "novelty_note": "Incremental enhancement to existing BRSKI with alternative enrollment options", + "maturity_note": "Comprehensive specification with clear architecture updates to established protocol", + "overlap_note": "Builds directly on BRSKI with some overlap to certificate enrollment protocols", + "momentum_note": "IETF working group item with strong industry backing for device onboarding", + "relevance_note": "High relevance for automated network device deployment and IoT scenarios", + "doc_status": "" + }, { "name": "draft-gaikwad-aps-profile", "title": "Agent Persistent State Profile", @@ -3708,7 +4387,7 @@ { "name": "draft-ietf-lake-edhoc-psk", "title": "EDHOC Authenticated with Pre-Shared Keys (PSK)", - "date": "2025-11-21", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-edhoc-psk/", "pages": 31, @@ -3783,6 +4462,57 @@ "relevance_note": "Extremely relevant to current debates over AI training data rights and consent", "doc_status": "" }, + { + "name": "draft-allman-tcp-early-rexmt", + "title": "Early Retransmit for TCP and SCTP", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-allman-tcp-early-rexmt/", + "pages": 12, + "group": "individual", + "score": 3.55, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Other AI/agent" + ], + "summary": "Proposes Early Retransmit mechanism for TCP and SCTP to recover lost segments when congestion window is small. Reduces duplicate ACKs needed for fast retransmission to avoid lengthy timeouts.", + "novelty_note": "Incremental improvement to existing TCP recovery mechanisms", + "maturity_note": "Well-established problem space with clear technical approach", + "overlap_note": "Some overlap with other TCP optimization drafts but specific focus", + "momentum_note": "TCP improvements have steady interest but not high priority", + "relevance_note": "Addresses real performance issues in low-bandwidth scenarios", + "doc_status": "" + }, + { + "name": "draft-wu-sidr-aspa-validation-signaling", + "title": "BGP AS_PATH Validation State Extended Community", + "date": "2024-09-01", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-wu-sidr-aspa-validation-signaling/", + "pages": 6, + "group": "individual", + "score": 3.55, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Policy/governance", + "Data formats/interop" + ], + "summary": "Defines BGP extended community to carry AS_PATH validation state based on ASPA. Enables IBGP speakers to use validation state in local policy decisions.", + "novelty_note": "Incremental but useful extension to existing ASPA validation mechanisms", + "maturity_note": "Well-defined technical solution building on established BGP mechanisms", + "overlap_note": "Complements existing ASPA work without significant overlap", + "momentum_note": "Steady progress in BGP security space with industry interest", + "relevance_note": "Important for BGP security and route validation in internet infrastructure", + "doc_status": "" + }, { "name": "draft-liu-agent-context-protocol", "title": "Agent Context Protocol", @@ -3838,11 +4568,11 @@ }, { "name": "draft-song-oauth-ai-agent-collaborate-authz", - "title": "OAuth2.0 Extension for Multi-AI Agent Collaboration: Applier-On-Behalf-Of Authorization", - "date": "2025-11-06", + "title": "OAuth2.0 Extension for Multi-AI Agent Collaboration", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-song-oauth-ai-agent-collaborate-authz/", - "pages": 8, + "pages": 13, "group": "individual", "score": 3.55, "novelty": 4, @@ -4049,6 +4779,31 @@ "relevance_note": "High relevance for 5G network security and automated policy management", "doc_status": "" }, + { + "name": "draft-ietf-httpbis-zstd-window-size", + "title": "Window Sizing for Zstandard Content Encoding", + "date": "2024-09-27", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-httpbis-zstd-window-size/", + "pages": 5, + "group": "individual", + "score": 3.5, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 4, + "relevance": 4, + "categories": [ + "Data formats/interop" + ], + "summary": "Updates RFC8878 to make Zstandard window size limits a requirement rather than recommendation for HTTP contexts. Addresses interoperability issues caused by browser memory limitations.", + "novelty_note": "Incremental update to existing compression standard, limited novelty", + "maturity_note": "Well-defined problem with clear solution, appears ready for implementation", + "overlap_note": "Specific update to compression standard, minimal overlap with other work", + "momentum_note": "IETF working group draft with recent updates, good standardization momentum", + "relevance_note": "High relevance for web performance and interoperability", + "doc_status": "" + }, { "name": "draft-jia-oauth-scope-aggregation", "title": "OAuth 2.0 Scope Aggregation for Multi-Step AI Agent Workflows", @@ -4127,6 +4882,31 @@ "relevance_note": "Highly relevant for securing authentication infrastructure against quantum threats", "doc_status": "" }, + { + "name": "draft-ietf-idr-bgp-metrics", + "title": "BGP AS Path Metrics", + "date": "2024-08-23", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-metrics/", + "pages": 8, + "group": "individual", + "score": 3.5, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 4, + "categories": [ + "A2A protocols" + ], + "summary": "Proposes extended per-hop BGP metrics to enable common routing policies that currently require complex configurations. Supplements BGP-4 with globally significant metrics.", + "novelty_note": "Per-hop BGP metrics provide useful extension but build incrementally on existing BGP framework", + "maturity_note": "Technical specification appears solid but references very old BGP RFCs suggesting dated approach", + "overlap_note": "Some overlap with BGP extensions but specific per-hop metrics approach is distinctive", + "momentum_note": "IETF working group draft with established routing community backing", + "relevance_note": "Addresses practical operational needs for BGP policy implementation", + "doc_status": "" + }, { "name": "draft-chen-agent-decoupled-authorization-model", "title": "A Decoupled Authorization Model for Agent2Agent", @@ -4312,6 +5092,32 @@ "relevance_note": "Highly relevant for quantum-resistant authentication evolution", "doc_status": "" }, + { + "name": "draft-ietf-sip-location-conveyance", + "title": "Location Conveyance for the Session Initiation Protocol", + "date": "2024-09-24", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-sip-location-conveyance/", + "pages": 46, + "group": "individual", + "score": 3.45, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 4, + "relevance": 3, + "categories": [ + "A2A protocols", + "Agent discovery/reg" + ], + "summary": "Defines SIP extension for conveying geographic location information between entities. Covers end-to-end conveyance and location-based routing decisions.", + "novelty_note": "Applies established location concepts to SIP protocol", + "maturity_note": "Comprehensive 46-page specification with detailed procedures", + "overlap_note": "Some overlap with existing location and SIP work", + "momentum_note": "Active IETF working group draft with recent updates", + "relevance_note": "Useful for location-aware SIP applications", + "doc_status": "" + }, { "name": "draft-yuan-rtgwg-security-agent-usecase", "title": "Use cases of the AI Network Security Agent", @@ -4740,6 +5546,56 @@ "relevance_note": "Highly relevant for standardizing AI content usage preference communication", "doc_status": "" }, + { + "name": "draft-mandel-lamps-rfc5274bis", + "title": "Certificate Management Messages over CMS (CMC): Compliance Requirements", + "date": "2024-09-05", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-mandel-lamps-rfc5274bis/", + "pages": 14, + "group": "individual", + "score": 3.35, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth" + ], + "summary": "Updates compliance requirements for Certificate Management Messages over CMS protocol. Obsoletes previous RFCs 5274 and 6402 with current best practices.", + "novelty_note": "Maintenance update rather than novel contribution", + "maturity_note": "Mature protocol area with clear requirements", + "overlap_note": "Direct replacement for obsoleted RFCs", + "momentum_note": "PKI standards have consistent but modest momentum", + "relevance_note": "Important for PKI interoperability and compliance", + "doc_status": "" + }, + { + "name": "draft-tiloca-lake-edhoc-implem-cons", + "title": "Implementation Considerations for Ephemeral Diffie-Hellman Over COSE (EDHOC)", + "date": "2024-02-13", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-tiloca-lake-edhoc-implem-cons/", + "pages": 25, + "group": "individual", + "score": 3.35, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth" + ], + "summary": "Provides implementation guidance for EDHOC authenticated key exchange protocol. Offers practical considerations for deploying Ephemeral Diffie-Hellman Over COSE.", + "novelty_note": "Implementation guide rather than protocol innovation", + "maturity_note": "Based on established EDHOC protocol specification", + "overlap_note": "Complementary to main EDHOC specification", + "momentum_note": "IoT security protocols have steady interest", + "relevance_note": "Important for correct EDHOC deployment in IoT scenarios", + "doc_status": "" + }, { "name": "draft-stephan-ai-agent-6g", "title": "AI Agent protocols for 6G systems", @@ -4848,6 +5704,86 @@ "relevance_note": "Very relevant to current data center and cloud networking evolution", "doc_status": "" }, + { + "name": "draft-ietf-dnsop-dns-error-reporting", + "title": "DNS Error Reporting", + "date": "2024-04-26", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/", + "pages": 12, + "group": "individual", + "score": 3.35, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Autonomous netops", + "Policy/governance" + ], + "summary": "Defines a lightweight mechanism for DNS resolvers to report resolution/validation errors to authoritative servers. Uses extended DNS errors and encodes reports in QNAMEs for automatic signaling.", + "novelty_note": "Novel approach to DNS error feedback using QNAME encoding for reporting", + "maturity_note": "Reasonably mature with clear protocol design, builds on established DNS error extensions", + "overlap_note": "Related to DNS monitoring but uses unique QNAME-based reporting approach", + "momentum_note": "IETF working group draft with steady progress", + "relevance_note": "High relevance for DNS operations and security, addresses real operational need", + "doc_status": "" + }, + { + "name": "draft-illyes-rep-purpose", + "title": "Robots Exclusion Protocol User Agent Purpose Extension", + "date": "2025-04-21", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-illyes-rep-purpose/", + "pages": 4, + "group": "individual", + "score": 3.35, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Policy/governance", + "Agent discovery/reg" + ], + "summary": "Extends the Robots Exclusion Protocol to target automatic clients based on their access purpose rather than just user-agent strings. Provides more granular control over automated access.", + "novelty_note": "Logical extension to existing robots.txt with purpose-based targeting", + "maturity_note": "Concise extension with clear scope, builds on established RFC", + "overlap_note": "Extends RFC9309 but addresses different targeting mechanism", + "momentum_note": "Moderate interest from web operators dealing with diverse automated clients", + "relevance_note": "Highly relevant as AI agents and web crawlers proliferate", + "doc_status": "" + }, + { + "name": "draft-yang-alto-multi-domain", + "title": "ALTO Multi-Domain Use Cases and Services", + "date": "2024-01-11", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/", + "pages": 12, + "group": "individual", + "score": 3.35, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "ML traffic mgmt", + "Data formats/interop", + "Policy/governance" + ], + "summary": "Identifies use cases and challenges for ALTO in multi-domain environments where paths span multiple autonomous networks. Provides preliminary implementation approaches.", + "novelty_note": "Addresses known gap in ALTO multi-domain scenarios with structured analysis", + "maturity_note": "Good problem analysis and use cases but implementation solutions need more detail", + "overlap_note": "Builds on ALTO foundation with some overlap but addresses specific multi-domain gap", + "momentum_note": "ALTO has established community with interest in multi-domain extensions", + "relevance_note": "Highly relevant for CDN optimization and application-layer traffic engineering", + "doc_status": "" + }, { "name": "draft-cosmos-protocol-specification", "title": "The Cosmos Protocol Specification (Trust-Native Semantic Protocol)", @@ -4956,6 +5892,33 @@ "relevance_note": "Directly addresses intelligent computing network requirements and resource optimization", "doc_status": "" }, + { + "name": "draft-yan-anima-brski-cle", + "title": "BRSKI-CLE: A Certificateless Enrollment framework in BRSKI", + "date": "2024-04-25", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-yan-anima-brski-cle/", + "pages": 10, + "group": "individual", + "score": 3.35, + "novelty": 4, + "maturity": 2, + "overlap": 3, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Autonomous netops", + "Agent discovery/reg" + ], + "summary": "Defines a certificateless enrollment framework for constrained IoT devices in BRSKI. Uses Key Encapsulation Mechanism (KEM) for quantum-safe algorithms and lightweight credentials like CWTs.", + "novelty_note": "High novelty in combining certificateless enrollment with quantum-safe KEM for IoT", + "maturity_note": "Early stage 10-page draft, references other work but lacks implementation details", + "overlap_note": "Overlaps with BRSKI and IoT enrollment work but unique certificateless approach", + "momentum_note": "Part of ANIMA working group but relatively new approach", + "relevance_note": "Highly relevant for constrained IoT device bootstrapping and quantum-safe security", + "doc_status": "" + }, { "name": "draft-mcp-over-moqt", "title": "Model Context Protocol over Media over QUIC Transport", @@ -5033,6 +5996,58 @@ "relevance_note": "Relevant for VoIP systems and call centers, but limited to SIP-based communications", "doc_status": "" }, + { + "name": "draft-vesely-dmarc-mlm-transform", + "title": "Mailing List Manager (MLM) Transformations", + "date": "2024-11-22", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-vesely-dmarc-mlm-transform/", + "pages": 17, + "group": "individual", + "score": 3.3, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 3, + "categories": [ + "Data formats/interop", + "Policy/governance" + ], + "summary": "Proposes method to revert mailing list transformations of From headers caused by DMARC adoption. Uses author-centric strategy to restore original sender information.", + "novelty_note": "Addresses real problem created by DMARC deployment, novel restoration approach", + "maturity_note": "Well-developed 17-page specification with detailed technical approach", + "overlap_note": "Unique approach to DMARC-MLM compatibility issue", + "momentum_note": "Important for email infrastructure but affects specific operator segment", + "relevance_note": "Addresses ongoing email authentication challenges", + "doc_status": "" + }, + { + "name": "draft-housley-lamps-private-key-attest-attr", + "title": "An Attribute for Statement of Possession of a Private Key", + "date": "2025-01-09", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-housley-lamps-private-key-attest-attr/", + "pages": 18, + "group": "individual", + "score": 3.3, + "novelty": 3, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 3, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Defines an X.509 attribute that allows certificate subjects to make signed statements proving possession of private keys. Enables CAs to accept attestations instead of direct proof-of-possession during certificate enrollment.", + "novelty_note": "Moderate novelty in formalizing private key attestation as X.509 attribute", + "maturity_note": "Well-defined specification building on established X.509 and PKI standards", + "overlap_note": "Some overlap with general PKI enrollment but specific attestation approach is distinct", + "momentum_note": "Standard PKI evolution with practical deployment potential", + "relevance_note": "Relevant for PKI deployments but limited to certificate enrollment scenarios", + "doc_status": "" + }, { "name": "draft-zheng-dispatch-agent-identity-management", "title": "Agent Identity Managenment", @@ -5141,6 +6156,31 @@ "relevance_note": "Relevant for specific sensing applications but narrower scope", "doc_status": "" }, + { + "name": "draft-ietf-lake-traces", + "title": "Traces of EDHOC", + "date": "2024-03-21", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-traces/", + "pages": 61, + "group": "individual", + "score": 3.25, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 4, + "relevance": 3, + "categories": [ + "Data formats/interop" + ], + "summary": "Contains example protocol traces and test vectors for the EDHOC protocol. Serves as implementation guidance and verification material for EDHOC developers.", + "novelty_note": "Documentation of examples rather than novel protocol development", + "maturity_note": "Well-developed traces document from established IETF working group", + "overlap_note": "Unique traces document, no significant overlap with other drafts", + "momentum_note": "Strong momentum as official IETF working group item with recent updates", + "relevance_note": "Important for EDHOC implementation but primarily developer-focused utility", + "doc_status": "" + }, { "name": "draft-chuyi-nmrg-ai-agent-network", "title": "Large Model based Agents for Network Operation and Maintenance", @@ -5357,6 +6397,57 @@ "relevance_note": "Directly applies AI/ML to traffic management and network resource optimization", "doc_status": "" }, + { + "name": "draft-nourse-scep", + "title": "Simple Certificate Enrollment Protocol", + "date": "2025-05-01", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-nourse-scep/", + "pages": 43, + "group": "individual", + "score": 3.25, + "novelty": 2, + "maturity": 5, + "overlap": 4, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Specifies the Simple Certificate Enrollment Protocol using PKCS#7 and PKCS#10 over HTTP. Formalizes the widely deployed protocol originally developed by VeriSign for Cisco.", + "novelty_note": "Standardizing existing widely-deployed protocol rather than new innovation", + "maturity_note": "Mature protocol with extensive real-world deployment and implementation experience", + "overlap_note": "Significant overlap with other certificate enrollment protocols like EST and CMP", + "momentum_note": "Steady momentum for standardizing de facto standard protocol", + "relevance_note": "High practical relevance due to widespread existing deployment", + "doc_status": "" + }, + { + "name": "draft-ietf-idr-bgp-dpa", + "title": "Destination Preference Attribute for BGP", + "date": "2024-08-23", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-dpa/", + "pages": 4, + "group": "individual", + "score": 3.25, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 4, + "relevance": 3, + "categories": [ + "A2A protocols" + ], + "summary": "Introduces Destination Preference Attribute for BGP to enable autonomous systems to specify globally transitive metrics. Aims to facilitate symmetric routing and load sharing in multi-provider environments.", + "novelty_note": "New BGP attribute with specific application for return traffic preferences shows moderate novelty", + "maturity_note": "Well-defined technical specification but compact at only 4 pages, may need more detail", + "overlap_note": "Some overlap with BGP traffic engineering but specific DPA approach is relatively unique", + "momentum_note": "IETF working group draft with established BGP community interest", + "relevance_note": "Relevant to BGP operations but addresses specific use case rather than broad applicability", + "doc_status": "" + }, { "name": "draft-tong-network-agent-use-cases-in-6g", "title": "Network AI Agent Use Cases and Requirements in 6G", @@ -5621,6 +6712,32 @@ "relevance_note": "Highly relevant for automated client identification and traffic management", "doc_status": "" }, + { + "name": "draft-chu-oauth-as-attested-user-cert", + "title": "OAuth 2.0 Rich Authorization Requests for AS-Attested User Certificates", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-chu-oauth-as-attested-user-cert/", + "pages": 9, + "group": "individual", + "score": 3.2, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 2, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "A2A protocols" + ], + "summary": "Extends OAuth 2.0 Rich Authorization Requests to allow clients like AI agents to request AS-attested user certificates in access tokens. This enables resource servers to verify delegation evidence signed by resource owners.", + "novelty_note": "Extends existing OAuth RAR framework for agent-specific use case", + "maturity_note": "Concise 9-page specification but could benefit from more examples", + "overlap_note": "Builds on OAuth standards but agent certificate binding is unique", + "momentum_note": "Individual submission with narrow scope may limit adoption", + "relevance_note": "Important for agent authentication and delegation scenarios", + "doc_status": "" + }, { "name": "draft-kale-agntcy-federated-privacy", "title": "Privacy-Preserving Federated Learning Architecture for Multi-Tenant AI Agent Systems", @@ -6021,6 +7138,84 @@ "relevance_note": "Addresses important WAN flow control needs for distributed AI", "doc_status": "" }, + { + "name": "draft-hw-protocol-agent", + "title": "AI Agent Protocols for Multi-modality", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-hw-protocol-agent/", + "pages": 12, + "group": "individual", + "score": 3.15, + "novelty": 3, + "maturity": 2, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "ML traffic mgmt", + "A2A protocols" + ], + "summary": "Proposes network-level recognition of AI agent multi-modal data transmission requirements. Aims to improve quality of service for diverse data types within agent traffic flows.", + "novelty_note": "Network awareness of multi-modal AI traffic is emerging but not deeply explored in IETF context", + "maturity_note": "Early stage work with broad scope but limited technical detail on implementation", + "overlap_note": "Some overlap with general QoS and traffic management but specific to AI agents", + "momentum_note": "Growing interest in AI traffic optimization but limited industry engagement visible", + "relevance_note": "Highly relevant as AI agent traffic becomes dominant network workload", + "doc_status": "" + }, + { + "name": "draft-peterson-mimi-idprover", + "title": "An Identitifier Proof-of-Possession Mechanism", + "date": "2024-09-05", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-peterson-mimi-idprover/", + "pages": 7, + "group": "individual", + "score": 3.15, + "novelty": 3, + "maturity": 2, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Defines a mechanism for third-party services to prove and attest the association between communication platforms and users' telephone numbers. Supports secure enrollment for messaging platforms requiring verified phone number identifiers.", + "novelty_note": "Moderate novelty in combining proof-of-possession with phone number attestation for messaging interoperability", + "maturity_note": "Early stage draft with basic specification, needs more implementation details", + "overlap_note": "Some overlap with general identity attestation work but specific to messaging platforms", + "momentum_note": "Part of active MIMI working group efforts for messaging interoperability", + "relevance_note": "Highly relevant for secure messaging and identity verification in communication systems", + "doc_status": "" + }, + { + "name": "draft-amsuess-ace-brski-ace", + "title": "Provisioning ACE credentials through BRSKI", + "date": "2024-01-08", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-amsuess-ace-brski-ace/", + "pages": 7, + "group": "individual", + "score": 3.15, + "novelty": 4, + "maturity": 2, + "overlap": 1, + "momentum": 2, + "relevance": 3, + "categories": [ + "Agent identity/auth", + "Autonomous netops" + ], + "summary": "Extends BRSKI voucher mechanism to provision ACE credentials for domain onboarding. Bridges PKI-managed and ACE-managed domain authentication.", + "novelty_note": "Creative integration of two different authentication frameworks", + "maturity_note": "Early stage work needing more detailed protocol specification and validation", + "overlap_note": "Unique combination of BRSKI and ACE with minimal existing overlap", + "momentum_note": "Limited adoption momentum, niche use case", + "relevance_note": "Relevant for IoT device onboarding but serves specific architectural scenarios", + "doc_status": "" + }, { "name": "draft-mvieuille-kerpass-ephemsec", "title": "KerPass EPHEMSEC One-Time Password Algorithm", @@ -6203,6 +7398,32 @@ "relevance_note": "Relevant for network security and BGP operations, though somewhat specialized", "doc_status": "" }, + { + "name": "draft-ingles-eap-edhoc", + "title": "Using the Extensible Authentication Protocol with Ephemeral Diffie-Hellman over COSE (EDHOC)", + "date": "2024-06-13", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/", + "pages": 22, + "group": "individual", + "score": 3.1, + "novelty": 3, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 3, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "Specifies how to use EDHOC (Ephemeral Diffie-Hellman Over COSE) as an authentication method within the Extensible Authentication Protocol framework. Provides lightweight authenticated key exchange for network access scenarios.", + "novelty_note": "Combines existing EAP framework with EDHOC protocol in a straightforward integration", + "maturity_note": "Reasonable specification but limited implementation experience evident", + "overlap_note": "Some overlap with other EAP methods but EDHOC integration is relatively unique", + "momentum_note": "Part of broader EDHOC ecosystem but individual draft momentum unclear", + "relevance_note": "Relevant for IoT and constrained device authentication scenarios", + "doc_status": "" + }, { "name": "draft-zw-nmrg-mcp-network-mgmt", "title": "Model Context Protocol (MCP) Extensions for Network Equipment Management", @@ -6286,10 +7507,10 @@ { "name": "draft-ni-wimse-ai-agent-identity", "title": "WIMSE Applicability for AI Agents", - "date": "2025-10-20", + "date": "2026-02-28", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ni-wimse-ai-agent-identity/", - "pages": 10, + "pages": 14, "group": "individual", "score": 3.05, "novelty": 3, @@ -6439,6 +7660,32 @@ "relevance_note": "Very relevant for scaling agent communications to massive deployments", "doc_status": "" }, + { + "name": "draft-patwhite-aauth", + "title": "AAuth - Agentic Authorization OAuth 2.1 Extension", + "date": "2025-05-13", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-patwhite-aauth/", + "pages": 6, + "group": "individual", + "score": 3.05, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Human-agent interaction" + ], + "summary": "Defines OAuth 2.1 extension for AI agents to obtain user consent and access tokens through polling or real-time channels. Adapts device flow for long-lived agent identities with natural language descriptions.", + "novelty_note": "Novel adaptation of OAuth device flow specifically for AI agents", + "maturity_note": "Early stage specification, needs more detail and security analysis", + "overlap_note": "Builds heavily on OAuth 2.0 device flow but for different use case", + "momentum_note": "Moderate interest as agent authorization becomes more important", + "relevance_note": "Addresses critical agent authorization gap in current standards", + "doc_status": "" + }, { "name": "draft-wendt-stir-vesper", "title": "VESPER - Framework for VErifiable STI Personas", @@ -6815,7 +8062,7 @@ { "name": "draft-pocero-authkem-ikr-edhoc", "title": "KEM-based Authentication for EDHOC in Initiator-Known Responder (IKR) Scenarios", - "date": "2026-01-20", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-pocero-authkem-ikr-edhoc/", "pages": 26, @@ -6943,6 +8190,32 @@ "relevance_note": "Relevant to AI training governance and rights management debates", "doc_status": "" }, + { + "name": "draft-herbert-fast", + "title": "Firewall and Service Tickets", + "date": "2024-04-09", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-herbert-fast/", + "pages": 24, + "group": "individual", + "score": 2.95, + "novelty": 4, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Agent identity/auth", + "Policy/governance" + ], + "summary": "Introduces Firewall and Service Tickets protocol for hosts to request network services and admission. Uses IPv6 Hop-by-Hop options to carry tickets that grant traversal rights or specify service requirements.", + "novelty_note": "Novel approach to network admission control and service signaling using ticket-based system", + "maturity_note": "Comprehensive but early-stage proposal, needs more implementation experience", + "overlap_note": "Some conceptual overlap with network access control and QoS signaling mechanisms", + "momentum_note": "Individual submission with limited broader community engagement", + "relevance_note": "Potentially relevant for zero-trust networking and service mesh architectures", + "doc_status": "" + }, { "name": "draft-happel-structured-email-trust", "title": "Trust and security considerations for Structured Email", @@ -7020,6 +8293,32 @@ "relevance_note": "Relevant for JSON-based security applications requiring dynamic key establishment", "doc_status": "" }, + { + "name": "draft-miller-ssh-agent", + "title": "SSH Agent Protocol", + "date": "2024-11-07", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-miller-ssh-agent/", + "pages": 24, + "group": "individual", + "score": 2.95, + "novelty": 1, + "maturity": 4, + "overlap": 2, + "momentum": 3, + "relevance": 4, + "categories": [ + "Agent identity/auth", + "Data formats/interop" + ], + "summary": "This draft documents the SSH agent protocol for secure key management. It provides standardization for an existing widely-used protocol.", + "novelty_note": "Documents existing SSH agent protocol with minimal novelty", + "maturity_note": "Well-established protocol with extensive real-world deployment", + "overlap_note": "Some overlap with existing SSH specifications but fills documentation gap", + "momentum_note": "Moderate momentum as it standardizes existing practice", + "relevance_note": "Highly relevant for SSH ecosystem standardization", + "doc_status": "" + }, { "name": "draft-ietf-roll-enrollment-priority", "title": "Controlling Secure Network Enrollment in RPL networks", @@ -7072,6 +8371,32 @@ "relevance_note": "Relevant to growing focus on network energy efficiency and sustainability", "doc_status": "" }, + { + "name": "draft-ounsworth-lamps-cms-dhkem", + "title": "Use of the DH-Based KEM (DHKEM) in the Cryptographic Message Syntax (CMS)", + "date": "2024-02-25", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ounsworth-lamps-cms-dhkem/", + "pages": 8, + "group": "individual", + "score": 2.9, + "novelty": 3, + "maturity": 3, + "overlap": 4, + "momentum": 3, + "relevance": 3, + "categories": [ + "Data formats/interop", + "A2A protocols" + ], + "summary": "Defines mechanism to use DHKEM algorithm within CMS for one-pass key establishment. Wraps Ephemeral-Static DH and ECDH for KEM interfaces in cryptographic messaging.", + "novelty_note": "Moderate novelty in adapting DHKEM for CMS, incremental improvement", + "maturity_note": "Concise 8-page specification with clear technical approach", + "overlap_note": "Significant overlap with existing KEM work and CMS specifications", + "momentum_note": "Part of established LAMPS working group efforts", + "relevance_note": "Moderately relevant for secure messaging but more focused on cryptographic infrastructure", + "doc_status": "" + }, { "name": "draft-zhang-rtgwg-ai-agents-troubleshooting", "title": "Use Cases and Requirements of Communication Protocol for Troubleshooting Agents on Network Devices", @@ -7257,6 +8582,58 @@ "relevance_note": "Highly relevant to CDN performance optimization and modern application delivery", "doc_status": "" }, + { + "name": "draft-chen-nmrg-ibn-management", + "title": "Network Management Intent -One of IBN Use Cases", + "date": "2024-09-04", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-chen-nmrg-ibn-management/", + "pages": 10, + "group": "individual", + "score": 2.9, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 4, + "categories": [ + "Autonomous netops", + "Policy/governance" + ], + "summary": "Proposes an intent-based network management architecture with five levels of autonomous operation. Focuses on reducing complexity and achieving fully automated network management with humans out of the loop.", + "novelty_note": "Intent-based networking concepts exist but specific five-level autonomous management framework shows some novelty", + "maturity_note": "High-level architectural proposal lacking detailed technical specifications and implementation details", + "overlap_note": "Moderate overlap with existing IBN and autonomous network management research", + "momentum_note": "Individual submission with limited apparent industry backing or working group adoption", + "relevance_note": "Highly relevant to current trends in network automation and autonomous operations", + "doc_status": "" + }, + { + "name": "draft-mangrove-workgroup-mangrove", + "title": "Mangrove: A Unified Framework for Internet Topology, Routing Abstraction, and Modeling", + "date": "2024-09-06", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-mangrove-workgroup-mangrove/", + "pages": 13, + "group": "individual", + "score": 2.9, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 4, + "categories": [ + "Autonomous netops", + "Data formats/interop" + ], + "summary": "Mangrove proposes a unified framework for Internet topology and routing modeling by aggregating diverse data sources like traceroute, BGP, and allocation records. It constructs hierarchical representations to compute packet paths and performance metrics across geographic regions, autonomous systems, and IP prefixes.", + "novelty_note": "Novel unified approach but builds on established topology mapping concepts", + "maturity_note": "Early stage with incomplete abstract and limited implementation details", + "overlap_note": "Some overlap with existing topology discovery and routing analysis work", + "momentum_note": "New workgroup with single draft, unclear community support", + "relevance_note": "High relevance for network operations and autonomous network management", + "doc_status": "" + }, { "name": "draft-jain-lisp-network-ai-infra", "title": "LISP-Based Network for AI Infrastructure", @@ -7464,6 +8841,31 @@ "relevance_note": "Traditional networking problem, not directly related to AI/ML agent systems", "doc_status": "" }, + { + "name": "draft-ietf-dtn-bpv7-admin-iana", + "title": "Bundle Protocol Version 7 Administrative Record Types Registry", + "date": "2025-01-17", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-dtn-bpv7-admin-iana/", + "pages": 5, + "group": "individual", + "score": 2.85, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 3, + "relevance": 2, + "categories": [ + "Data formats/interop" + ], + "summary": "Updates Bundle Protocol Version 7 to clarify use of IANA registry for Administrative Record types. Reserves code points for private and experimental use.", + "novelty_note": "Registry clarification rather than new protocol features", + "maturity_note": "Well-defined registry update with clear IANA considerations", + "overlap_note": "Specific to Bundle Protocol administrative records", + "momentum_note": "IETF working group draft with focused scope", + "relevance_note": "Limited to DTN Bundle Protocol implementations", + "doc_status": "" + }, { "name": "draft-blahaj-grow-rpki-oauth", "title": "Attesting the Identities of Parties in OpenID Connect (OIDC) using the Resource Public Key Infrastructure (RPKI)", @@ -7543,10 +8945,10 @@ { "name": "draft-ietf-lake-edhoc-impl-cons", "title": "Implementation Considerations for Ephemeral Diffie-Hellman Over COSE (EDHOC)", - "date": "2026-01-07", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-lake-edhoc-impl-cons/", - "pages": 43, + "pages": 45, "group": "individual", "score": 2.8, "novelty": 2, @@ -7617,6 +9019,31 @@ "relevance_note": "Traditional web technology, limited relevance to AI/agent systems", "doc_status": "" }, + { + "name": "draft-serafin-lake-ta-hint", + "title": "Trust Anchor Hints in Ephemeral Diffie-Hellman Over COSE (EDHOC)", + "date": "2025-04-24", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-serafin-lake-ta-hint/", + "pages": 9, + "group": "individual", + "score": 2.8, + "novelty": 2, + "maturity": 3, + "overlap": 2, + "momentum": 3, + "relevance": 3, + "categories": [ + "Agent identity/auth" + ], + "summary": "Defines trust anchor hint format for EDHOC protocol to help identify trusted third parties. Provides optimization for certificate chain discovery in constrained environments.", + "novelty_note": "Incremental improvement to existing EDHOC protocol, addressing practical deployment issue", + "maturity_note": "Early stage but builds on solid EDHOC foundation", + "overlap_note": "Specific to EDHOC, minimal overlap with other trust anchor mechanisms", + "momentum_note": "Moderate momentum tied to EDHOC adoption in IoT", + "relevance_note": "Relevant for IoT security but limited scope", + "doc_status": "" + }, { "name": "draft-du-ai-agent-communication-6g-aspect", "title": "Use Cases and Requirements of AI Agent Communication from 6G Aspect", @@ -7674,7 +9101,7 @@ { "name": "draft-ietf-sshm-ssh-agent", "title": "SSH Agent Protocol", - "date": "2026-02-24", + "date": "2026-03-03", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-ietf-sshm-ssh-agent/", "pages": 31, @@ -7879,6 +9306,31 @@ "relevance_note": "Very relevant to current AI training infrastructure requirements for MoE models", "doc_status": "" }, + { + "name": "draft-jaju-httpbis-zstd-window-size", + "title": "Window Sizing for Zstandard Content Encoding", + "date": "2024-06-11", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-jaju-httpbis-zstd-window-size/", + "pages": 4, + "group": "individual", + "score": 2.75, + "novelty": 2, + "maturity": 5, + "overlap": 4, + "momentum": 3, + "relevance": 2, + "categories": [ + "Data formats/interop" + ], + "summary": "Updates RFC8878 to make window size limits for Zstandard compression a requirement rather than recommendation. Addresses browser interoperability issues.", + "novelty_note": "Incremental update to existing standard addressing known interoperability issue", + "maturity_note": "Mature, focused fix to specific technical problem with clear implementation guidance", + "overlap_note": "Direct update to existing RFC8878 with minimal scope changes", + "momentum_note": "Addresses real deployment issues but limited scope for broader impact", + "relevance_note": "Important for HTTP compression but not directly related to AI/agent protocols", + "doc_status": "" + }, { "name": "draft-zhang-rtgwg-ai-agents-measurement", "title": "Use Cases and Requirements of Communication Protocol for Measurement Agents on Network Devices", @@ -8090,13 +9542,39 @@ "relevance_note": "Addresses real need for efficient bulk data transfer but may be too application-specific for IETF", "doc_status": "" }, + { + "name": "draft-wang-lisp-ai-agent", + "title": "Using LISP as a Network Substrate for AI Agent Communication", + "date": "2026-02-28", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-wang-lisp-ai-agent/", + "pages": 9, + "group": "individual", + "score": 2.75, + "novelty": 3, + "maturity": 2, + "overlap": 2, + "momentum": 2, + "relevance": 3, + "categories": [ + "A2A protocols", + "Autonomous netops" + ], + "summary": "Explores using LISP protocol as network substrate for AI agent communication. Addresses location transparency, mobility, and multi-homing for distributed AI systems.", + "novelty_note": "Interesting application of existing LISP technology to AI agent networking", + "maturity_note": "Conceptual work at 9 pages, needs more technical development", + "overlap_note": "Leverages LISP but applies it to new AI agent domain", + "momentum_note": "Limited momentum, appears exploratory", + "relevance_note": "Moderately relevant for AI agent infrastructure needs", + "doc_status": "" + }, { "name": "draft-zhao-ccamp-actn-optical-network-agent", "title": "Integration of Network Management Agent (NMA) into ACTN-Based Optical Network", - "date": "2025-10-20", + "date": "2026-02-28", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-zhao-ccamp-actn-optical-network-agent/", - "pages": 10, + "pages": 18, "group": "individual", "score": 2.7, "novelty": 3, @@ -8167,6 +9645,81 @@ "relevance_note": "Relevant to broadband operators but limited connection to AI/agent themes", "doc_status": "" }, + { + "name": "draft-moonesamy-rfc2369bis", + "title": "The Use of URIs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-moonesamy-rfc2369bis/", + "pages": 14, + "group": "individual", + "score": 2.7, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 2, + "relevance": 2, + "categories": [ + "Other AI/agent" + ], + "summary": "Updates RFC 2369 to define standardized email header fields for mailing list commands like subscribe, unsubscribe, and help. Enables mail clients to provide automated tools for common mailing list operations.", + "novelty_note": "Incremental update to existing RFC with minor refinements", + "maturity_note": "Well-established concept being refined, clear specification", + "overlap_note": "Unique update to specific RFC, no overlap with other drafts", + "momentum_note": "Limited community interest in mailing list standards", + "relevance_note": "Relevant to email systems but not AI/agent focused", + "doc_status": "" + }, + { + "name": "draft-moonesamy-rfc2919bis", + "title": "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-moonesamy-rfc2919bis/", + "pages": 12, + "group": "individual", + "score": 2.7, + "novelty": 2, + "maturity": 4, + "overlap": 1, + "momentum": 2, + "relevance": 2, + "categories": [ + "Other AI/agent" + ], + "summary": "Updates RFC 2919 to define the List-Id header field for uniquely identifying mailing lists. Provides namespace based on domain names to ensure global uniqueness.", + "novelty_note": "Standard maintenance update with minimal new concepts", + "maturity_note": "Mature specification being updated, well-defined scope", + "overlap_note": "Companion to RFC 2369bis but addresses different aspect", + "momentum_note": "Limited broader community engagement expected", + "relevance_note": "Email infrastructure relevant but not AI/agent specific", + "doc_status": "" + }, + { + "name": "draft-ma-v6ops-pe-ipv6only-reqs", + "title": "Requirements for Provider Edge in IPv6-only Underlay Networks", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ma-v6ops-pe-ipv6only-reqs/", + "pages": 9, + "group": "individual", + "score": 2.7, + "novelty": 2, + "maturity": 3, + "overlap": 3, + "momentum": 3, + "relevance": 3, + "categories": [ + "Other AI/agent" + ], + "summary": "Defines requirements for Provider Edge devices in IPv6-only underlay networks supporting multi-domain operations. Focuses on service delivery and interoperability while providing IPv4-as-a-Service capabilities.", + "novelty_note": "Incremental work on IPv6-only deployment scenarios, building on existing PE requirements", + "maturity_note": "Requirements document with clear scope but needs implementation validation", + "overlap_note": "Moderate overlap with existing IPv6 transition and PE requirements drafts", + "momentum_note": "IPv6-only deployments gaining traction but not urgent priority", + "relevance_note": "Relevant for service providers transitioning to IPv6-only infrastructure", + "doc_status": "" + }, { "name": "draft-zeng-mcp-network-mgmt", "title": "Model Context Protocol (MCP) Extensions for Network Equipment Management", @@ -8379,6 +9932,84 @@ "relevance_note": "Addresses real need for agent messaging but focuses heavily on promoting specific proprietary solution", "doc_status": "" }, + { + "name": "draft-zhao-nmrg-ai-agent-for-ndt", + "title": "AI Agent Architecture for Network Digital Twin", + "date": "2026-03-02", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-zhao-nmrg-ai-agent-for-ndt/", + "pages": 8, + "group": "individual", + "score": 2.65, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Autonomous netops", + "Other AI/agent" + ], + "summary": "Proposes AI agent architecture for Network Digital Twin systems. Integrates AI agents with digital twin technology for network management.", + "novelty_note": "Novel combination of AI agents with network digital twin concepts", + "maturity_note": "Early stage work with limited technical depth at 8 pages", + "overlap_note": "Some overlap with existing digital twin and AI networking research", + "momentum_note": "Limited momentum, appears to be early research work", + "relevance_note": "Moderately relevant to emerging AI-driven network operations", + "doc_status": "" + }, + { + "name": "draft-bernardos-anima-fog-monitoring", + "title": "Autonomic setup of fog monitoring agents", + "date": "2024-01-05", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-bernardos-anima-fog-monitoring/", + "pages": 14, + "group": "individual", + "score": 2.65, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Autonomous netops", + "Agent discovery/reg" + ], + "summary": "Proposes using GRASP for autonomic setup of monitoring agents in dynamic fog computing environments. Addresses the challenge of managing volatile, heterogeneous fog resources through self-configuring monitoring infrastructure.", + "novelty_note": "Applies existing autonomic networking concepts to fog monitoring, reasonable novelty in the specific use case", + "maturity_note": "Early stage draft with basic framework outlined but lacks detailed protocol specifications", + "overlap_note": "Some overlap with general autonomic networking and GRASP usage patterns", + "momentum_note": "Limited recent activity, fog computing adoption has been slower than anticipated", + "relevance_note": "Relevant for IoT and edge computing scenarios where dynamic resource management is needed", + "doc_status": "" + }, + { + "name": "draft-he-yi-srv6ops-ipv6-enhancemnet-in-cloud-uc", + "title": "Use Cases and Requirements for IPv6 enhancement techniques in cloud.", + "date": "2024-07-05", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-he-yi-srv6ops-ipv6-enhancemnet-in-cloud-uc/", + "pages": 4, + "group": "individual", + "score": 2.65, + "novelty": 3, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Agent identity/auth", + "Autonomous netops" + ], + "summary": "Outlines use cases for IPv6 enhancement techniques in cloud environments. Proposes Virtual Incloud Router as agent for end-to-end IPv6 capabilities.", + "novelty_note": "Combines existing IPv6 enhancement with cloud integration", + "maturity_note": "Use case document with spelling errors and unclear requirements", + "overlap_note": "Overlaps with SRv6 and cloud networking work", + "momentum_note": "Individual submission with limited recent updates", + "relevance_note": "Relevant to cloud-network integration trends", + "doc_status": "" + }, { "name": "draft-yu-dmsc-ai-agent-use-cases-in-6g", "title": "AI Agent Use Cases and Requirements in 6G Network", @@ -8984,6 +10615,31 @@ "relevance_note": "Relevant topic but potentially superseded by working group efforts", "doc_status": "" }, + { + "name": "draft-ecdh-psi", + "title": "PSI based on ECDH", + "date": "2024-10-21", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ecdh-psi/", + "pages": 25, + "group": "individual", + "score": 2.45, + "novelty": 2, + "maturity": 3, + "overlap": 4, + "momentum": 2, + "relevance": 3, + "categories": [ + "Data formats/interop" + ], + "summary": "Describes ECDH-based Private Set Intersection protocol using elliptic curves and hash-to-curve methods. Implements classical Meadows protocol with modern cryptographic primitives.", + "novelty_note": "Standard implementation of known PSI techniques, not particularly novel", + "maturity_note": "Reasonably detailed but lacks implementation guidance and security analysis depth", + "overlap_note": "Significant overlap with existing PSI literature and protocols", + "momentum_note": "Limited momentum, niche application area", + "relevance_note": "Moderate relevance for privacy-preserving applications", + "doc_status": "" + }, { "name": "draft-zl-agents-networking-framework", "title": "Agents Networking Framework for Enterprise and Broadband", @@ -9061,6 +10717,32 @@ "relevance_note": "Useful for EDHOC implementations but addresses narrow technical requirement", "doc_status": "" }, + { + "name": "draft-ietf-bgp-idrp-usage", + "title": "Application of the Border Gateway Protocol and IDRP for IP in the Internet", + "date": "2024-08-23", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ietf-bgp-idrp-usage/", + "pages": 21, + "group": "individual", + "score": 2.35, + "novelty": 2, + "maturity": 3, + "overlap": 4, + "momentum": 3, + "relevance": 2, + "categories": [ + "A2A protocols", + "Policy/governance" + ], + "summary": "Describes usage guidelines for BGP and IDRP protocols in Internet inter-autonomous system routing. Serves as companion document defining practical application of these routing protocols.", + "novelty_note": "Usage document for existing protocols with limited novel technical contribution", + "maturity_note": "Comprehensive usage guide but references very dated protocol versions and email lists", + "overlap_note": "Significant overlap with existing BGP deployment and usage documentation", + "momentum_note": "IETF draft but appears to cover legacy protocols with questionable current relevance", + "relevance_note": "Limited relevance due to focus on dated protocol versions and deployment scenarios", + "doc_status": "" + }, { "name": "draft-liu-rtgwg-llmsync-multicast", "title": "Multicast Use Cases for Large Language Model Synchronization", @@ -9244,6 +10926,82 @@ "relevance_note": "Moderately relevant for AI crawler behavior but lacks technical depth", "doc_status": "" }, + { + "name": "draft-hy-srv6ops-sfc-in-cloud-uc", + "title": "Use Cases and Requirements for Service Function Chaining based on SRv6 in cloud.", + "date": "2025-04-19", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-hy-srv6ops-sfc-in-cloud-uc/", + "pages": 5, + "group": "individual", + "score": 2.35, + "novelty": 2, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Autonomous netops", + "Data formats/interop" + ], + "summary": "Defines use cases for implementing Service Function Chaining using SRv6 in cloud environments. Proposes virtual routers as agents to enable SRv6 capabilities in cloud services.", + "novelty_note": "SRv6 and SFC are established technologies, limited novelty in cloud application", + "maturity_note": "Early draft with basic use case outline, lacks detailed technical specifications", + "overlap_note": "Overlaps with existing SRv6 and SFC standardization efforts", + "momentum_note": "Niche cloud-network integration topic with limited broad appeal", + "relevance_note": "Relevant to cloud-network convergence but serves specific operator needs", + "doc_status": "" + }, + { + "name": "draft-allman-tcpx2-hack", + "title": "TCPx2: Don't Fence Me In", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-allman-tcpx2-hack/", + "pages": 9, + "group": "individual", + "score": 2.35, + "novelty": 2, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Other AI/agent" + ], + "summary": "Proposes increasing TCP header size without changing protocol semantics. Aims to solve problems caused by TCP's lack of header space for certain values.", + "novelty_note": "Header extension concept exists, specific approach may be novel", + "maturity_note": "Early stage work, deployment challenges unclear", + "overlap_note": "Multiple TCP extension mechanisms already proposed", + "momentum_note": "Limited community momentum for TCP header changes", + "relevance_note": "Addresses known limitation but deployment barriers high", + "doc_status": "" + }, + { + "name": "draft-lopez-lake-edhoc-psk", + "title": "EDHOC PSK authentication", + "date": "2025-01-21", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-lopez-lake-edhoc-psk/", + "pages": 10, + "group": "individual", + "score": 2.35, + "novelty": 2, + "maturity": 2, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Agent identity/auth" + ], + "summary": "Defines Pre-Shared Key authentication method for EDHOC protocol. Specifies message flows and security considerations for PSK-based EDHOC authentication.", + "novelty_note": "Extends existing EDHOC with well-known PSK authentication approach", + "maturity_note": "Recent draft with limited detail and implementation maturity", + "overlap_note": "Moderate overlap with core EDHOC specification and other auth methods", + "momentum_note": "Individual contribution with uncertain working group adoption prospects", + "relevance_note": "Useful for scenarios requiring PSK authentication with EDHOC", + "doc_status": "" + }, { "name": "draft-hong-nmrg-ai-deploy", "title": "Considerations of network/system for AI services", @@ -9270,10 +11028,36 @@ "relevance_note": "Addresses relevant distributed AI deployment challenges but at a high level", "doc_status": "" }, + { + "name": "draft-ruas-cfrg-ecdp", + "title": "ECDP: Elliptic Curve Data Protocol", + "date": "2025-05-19", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-ruas-cfrg-ecdp/", + "pages": 11, + "group": "individual", + "score": 2.25, + "novelty": 2, + "maturity": 2, + "overlap": 4, + "momentum": 2, + "relevance": 3, + "categories": [ + "A2A protocols", + "Agent identity/auth" + ], + "summary": "Specifies peer-to-peer communication protocol for decentralized networks using elliptic curve cryptography. Combines ECDSA authentication with ECDH key exchange over TCP/UDP.", + "novelty_note": "Combines existing ECC techniques without significant cryptographic innovation", + "maturity_note": "Basic specification with limited implementation details and security analysis", + "overlap_note": "Heavy overlap with existing P2P protocols and standard ECC applications", + "momentum_note": "Limited momentum as individual submission without working group support", + "relevance_note": "Moderate relevance for decentralized applications but competes with established solutions", + "doc_status": "" + }, { "name": "draft-kompella-lsr-mptecap", "title": "Multipath Traffic Engineering Capabilities", - "date": "2026-01-09", + "date": "2026-03-02", "source": "ietf", "url": "https://datatracker.ietf.org/doc/draft-kompella-lsr-mptecap/", "pages": 6, @@ -9321,6 +11105,32 @@ "relevance_note": "Peripherally relevant to AI agents needing to understand domain relationships", "doc_status": "" }, + { + "name": "draft-daviel-html-geo-tag", + "title": "Geographic registration of HTML documents", + "date": "2024-12-18", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-daviel-html-geo-tag/", + "pages": 11, + "group": "individual", + "score": 2.2, + "novelty": 2, + "maturity": 3, + "overlap": 4, + "momentum": 2, + "relevance": 2, + "categories": [ + "Data formats/interop", + "Agent discovery/reg" + ], + "summary": "Defines method for embedding geographic location in HTML documents using META tags. Enables automated resource discovery based on latitude, longitude and civic location.", + "novelty_note": "Geographic tagging concept exists, limited novelty in HTML META approach", + "maturity_note": "Complete specification but addresses legacy HTML approach", + "overlap_note": "Significant overlap with existing geolocation and metadata standards", + "momentum_note": "Limited momentum given modern geolocation alternatives", + "relevance_note": "Low relevance due to superior modern geolocation methods", + "doc_status": "" + }, { "name": "draft-dunbar-neotec-ac-pe2pe-ucmp-applicability", "title": "Applying Attachmet Circuit and PE2PE YANG Data Model to dynamic policies Use Case", @@ -9348,6 +11158,58 @@ "relevance_note": "Relevant for understanding current model limitations in dynamic policy scenarios", "doc_status": "" }, + { + "name": "w3c-web-user-agents", + "title": "Web User Agents", + "date": "20260120", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/w3c-web-user-agents/", + "pages": 0, + "group": "individual", + "score": 2.15, + "novelty": 2, + "maturity": 1, + "overlap": 3, + "momentum": 2, + "relevance": 3, + "categories": [ + "Policy/governance", + "Human-agent interaction" + ], + "summary": "Establishes duties and responsibilities of web user agents (browsers and intermediaries) toward their users. Proposes that user agents should prioritize user interests over other constituencies through collectively-discussed standards.", + "novelty_note": "Basic concept of user agent duties exists, but formal standardization approach is somewhat novel", + "maturity_note": "Very early stage with minimal detail on implementation or specific requirements", + "overlap_note": "Moderate overlap with existing W3C browser standards and user agent specifications", + "momentum_note": "Uncertain momentum without clear working group or implementation commitments", + "relevance_note": "Relevant to web standards but limited direct connection to AI/agent networking focus", + "doc_status": "" + }, + { + "name": "draft-vattaparambil-positioning-of-poa", + "title": "Positioning of PoA", + "date": "2024-04-20", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-vattaparambil-positioning-of-poa/", + "pages": 11, + "group": "individual", + "score": 2.15, + "novelty": 3, + "maturity": 2, + "overlap": 4, + "momentum": 1, + "relevance": 2, + "categories": [ + "Agent identity/auth", + "Policy/governance" + ], + "summary": "Positions Power of Attorney based authorization as a decentralized subgranting technique for constrained environments. Compares PoA with existing authorization protocols and identity solutions.", + "novelty_note": "Interesting application of legal concept to technical authorization, moderate novelty", + "maturity_note": "Positioning paper rather than detailed protocol specification, needs more technical depth", + "overlap_note": "Significant overlap with OAuth, delegation protocols, and capability-based security", + "momentum_note": "Individual submission with minimal recent activity or community interest", + "relevance_note": "Limited immediate relevance, more academic positioning than practical protocol", + "doc_status": "" + }, { "name": "draft-wang-data-transmission-security-irii", "title": "Data Transmission Security of Identity Resolution in Industrial Internet", @@ -9400,6 +11262,33 @@ "relevance_note": "IoT security is relevant but approach seems disconnected from current IETF IoT work", "doc_status": "" }, + { + "name": "draft-kim-nmrg-2nmai5g", + "title": "Native Network Management using Artificial Intelligence over an Adaptive B5G Network", + "date": "2024-01-10", + "source": "ietf", + "url": "https://datatracker.ietf.org/doc/draft-kim-nmrg-2nmai5g/", + "pages": 11, + "group": "individual", + "score": 2.05, + "novelty": 2, + "maturity": 1, + "overlap": 4, + "momentum": 2, + "relevance": 3, + "categories": [ + "Autonomous netops", + "AI safety/alignment", + "ML traffic mgmt" + ], + "summary": "Proposes AI-driven autonomous security and network management for B5G networks using SOAR principles. Focuses on maintaining constant security quality through intent-based management.", + "novelty_note": "Combines existing concepts (AI, SOAR, intent-based networking) without clear innovation", + "maturity_note": "Very early conceptual stage with unclear technical specifications and requirements", + "overlap_note": "Significant overlap with existing AI-driven network management proposals", + "momentum_note": "Limited technical detail suggests low implementation momentum", + "relevance_note": "Relevant topic area but lacks concrete technical contributions", + "doc_status": "" + }, { "name": "draft-steckbeck-ua-conn-sec", "title": "User Agent Connection Security", diff --git a/docs/data/gaps.json b/docs/data/gaps.json index bceec3b..52c7332 100644 --- a/docs/data/gaps.json +++ b/docs/data/gaps.json @@ -1,101 +1,314 @@ { "current": [ { - "id": 25, - "topic": "Agent Behavior Verification", - "description": "While many drafts address agent identity and authentication, few tackle how to verify that an agent is actually behaving according to its declared capabilities and policies. There's a critical gap in runtime behavioral attestation and compliance monitoring mechanisms.", - "category": "AI safety/alignment", - "evidence": "High overlap in identity/auth (108 drafts) but only 44 drafts on safety/alignment, with no specific focus on behavioral verification", - "severity": "critical" - }, - { - "id": 26, - "topic": "Cross-Domain Agent Liability", - "description": "When autonomous agents operate across organizational boundaries and cause harm or make decisions with legal implications, there's no standardized framework for liability attribution. The policy/governance drafts don't address cross-jurisdictional legal accountability.", - "category": "Policy/governance", - "evidence": "91 policy/governance drafts but legal liability for cross-domain autonomous actions remains unaddressed", - "severity": "critical" - }, - { - "id": 27, - "topic": "Agent Resource Exhaustion Protection", - "description": "Missing standardized mechanisms to prevent malicious or poorly designed agents from consuming excessive network, compute, or storage resources. Current drafts focus on traffic management but not on agent-specific resource quotas and enforcement.", - "category": "Autonomous netops", - "evidence": "93 autonomous netops drafts and 73 ML traffic management drafts lack agent-specific resource protection mechanisms", - "severity": "high" - }, - { - "id": 28, - "topic": "Human Override Protocols", - "description": "Critical gap in standardized protocols for humans to safely interrupt, override, or take control of autonomous agents in emergency situations. Only 30 drafts address human-agent interaction, with no focus on emergency takeover procedures.", - "category": "Human-agent interaction", - "evidence": "Only 30 human-agent interaction drafts compared to 213+ autonomous operation drafts, with no emergency override standards", - "severity": "critical" - }, - { - "id": 29, - "topic": "Agent-Generated Data Provenance", - "description": "While 145 drafts address data formats for AI interop, there's insufficient attention to tracking the provenance and lineage of data generated by agents. This creates trust and auditability issues in agent-to-agent data exchanges.", - "category": "Data formats/interop", - "evidence": "145 data format drafts with high overlap but no clear standards for agent-generated data provenance tracking", - "severity": "high" - }, - { - "id": 30, - "topic": "Agent Capability Degradation Handling", - "description": "No standardized approaches for detecting and handling when an agent's capabilities degrade due to model drift, data corruption, or hardware issues. Systems need graceful degradation protocols rather than silent failures.", - "category": "AI safety/alignment", - "evidence": "Only 44 safety/alignment drafts don't address capability degradation, while 213+ drafts assume stable agent performance", - "severity": "high" - }, - { - "id": 31, - "topic": "Multi-Agent Coordination Deadlocks", - "description": "With 120+ A2A protocol drafts, there's insufficient attention to preventing deadlock situations where multiple agents create circular dependencies or resource conflicts. Missing are standardized deadlock detection and resolution mechanisms.", + "id": 37, + "topic": "Multi-Agent Consensus Protocols", + "description": "While A2A protocols exist, there's no standardized approach for multiple AI agents to reach consensus on shared decisions or conflicting objectives. This becomes critical when agents must coordinate on resource allocation or policy enforcement across domains.", "category": "A2A protocols", - "evidence": "120 A2A protocol drafts with high internal overlap but no systematic deadlock prevention frameworks", + "evidence": "High overlap in A2A protocols suggests fragmented approaches without consensus mechanisms, critical for autonomous system coordination", "severity": "high" }, { - "id": 32, - "topic": "Agent Privacy Preservation", - "description": "Agents often process sensitive data but current drafts don't adequately address privacy-preserving computation, differential privacy, or secure multi-party computation for agent interactions. This is critical for deployment in regulated industries.", - "category": "Agent identity/auth", - "evidence": "108 identity/auth drafts focus on authentication but lack privacy preservation mechanisms for agent data processing", - "severity": "high" + "id": 38, + "topic": "Agent Behavioral Verification", + "description": "No drafts address how to verify that deployed AI agents are actually behaving according to their declared policies or specifications. This creates a gap between policy definition and runtime assurance.", + "category": "AI safety/alignment", + "evidence": "Only 47 drafts on AI safety despite 433 total drafts, and behavioral verification is fundamental to autonomous system trust", + "severity": "critical" }, { - "id": 33, - "topic": "Real-time Agent Debugging", - "description": "Missing standardized protocols for debugging autonomous agents in production environments. When agents make unexpected decisions, there are no standard interfaces for real-time introspection without disrupting operations.", - "category": "Other AI/agent", - "evidence": "26 other AI/agent drafts suggest various approaches but no standardized debugging protocols for production agents", - "severity": "medium" - }, - { - "id": 34, - "topic": "Agent Firmware/Model Update Security", - "description": "While model serving is addressed in 42 drafts, there's insufficient focus on secure update mechanisms for agent models and firmware. Missing are standards for cryptographically verified, rollback-capable agent updates.", - "category": "Model serving/inference", - "evidence": "42 model serving drafts but no comprehensive security standards for agent software/model updates", - "severity": "high" - }, - { - "id": 35, + "id": 39, "topic": "Cross-Protocol Agent Migration", - "description": "No standardized mechanisms for migrating agent state and context when moving between different A2A protocols or infrastructure providers. This creates vendor lock-in and limits agent mobility.", - "category": "A2A protocols", - "evidence": "120 A2A protocol drafts with high overlap suggest competing approaches but no migration standards between them", + "description": "Agents need to migrate between different network protocols, domains, or infrastructure providers while maintaining state and identity. Current drafts focus on registration but not migration continuity.", + "category": "Agent discovery/reg", + "evidence": "Agent registration servers exist but no migration protocols, essential for dynamic edge deployments mentioned in technical ideas", "severity": "medium" }, { - "id": 36, - "topic": "Agent Energy Consumption Optimization", - "description": "Missing standards for energy-aware agent deployment and operation. As AI workloads are energy-intensive, there's no framework for agents to optimize their energy consumption or for infrastructure to enforce energy budgets.", - "category": "ML traffic mgmt", - "evidence": "73 ML traffic management drafts focus on performance but lack energy consumption considerations for sustainable AI deployment", + "id": 40, + "topic": "Real-Time Agent Rollback Mechanisms", + "description": "When autonomous agents make incorrect decisions, there's no standardized protocol for quickly rolling back their actions across distributed systems. This is critical for network operations and safety.", + "category": "Autonomous netops", + "evidence": "114 autonomous netops drafts but no rollback mechanisms, critical for production network safety", + "severity": "high" + }, + { + "id": 41, + "topic": "Agent Resource Accounting and Billing", + "description": "Multi-tenant environments need standardized ways to track and bill for AI agent resource consumption across compute, network, and storage. Current drafts define resources but not accounting mechanisms.", + "category": "new", + "evidence": "Edge AI placement and resource types defined but no economic models for multi-tenant agent deployments", + "severity": "medium" + }, + { + "id": 42, + "topic": "Federated Agent Learning Privacy", + "description": "While federated architectures exist, there's insufficient specification for privacy-preserving agent learning that prevents data leakage between federated participants during model updates.", + "category": "Policy/governance", + "evidence": "Federated AI architectures mentioned but private data training requirements suggest unresolved privacy challenges", + "severity": "high" + }, + { + "id": 43, + "topic": "Agent Capability Negotiation", + "description": "Agents need standardized protocols to negotiate their capabilities and limitations before collaboration. Tool enumeration exists but not dynamic capability negotiation during runtime.", + "category": "A2A protocols", + "evidence": "Tool enumeration APIs exist but no dynamic capability negotiation, needed for heterogeneous agent coordination", + "severity": "medium" + }, + { + "id": 44, + "topic": "Cross-Domain Agent Audit Trails", + "description": "When agents operate across multiple domains or organizations, there's no standardized format for maintaining audit trails that satisfy different regulatory requirements simultaneously.", + "category": "Agent identity/auth", + "evidence": "Cross-domain identity management exists but audit requirements vary by jurisdiction, creating compliance gaps", + "severity": "high" + }, + { + "id": 45, + "topic": "Agent Failure Cascade Prevention", + "description": "No protocols exist to prevent agent failures from cascading across interconnected autonomous systems. This is critical as agent interdependencies increase in production deployments.", + "category": "AI safety/alignment", + "evidence": "Limited AI safety focus (47 drafts) despite high interconnectivity implied by A2A protocols and autonomous netops", + "severity": "critical" + }, + { + "id": 46, + "topic": "Human Override Standardization", + "description": "While human-agent interaction exists, there's no standardized protocol for human operators to override autonomous agent decisions across different vendor implementations and domains.", + "category": "Human-agent interaction", + "evidence": "Only 33 human-agent interaction drafts suggest limited focus on human control mechanisms essential for safe deployment", + "severity": "high" + }, + { + "id": 47, + "topic": "Agent Performance Benchmarking", + "description": "No standardized metrics or protocols exist for comparing agent performance across different implementations, making it difficult to evaluate and select appropriate agents for specific tasks.", + "category": "new", + "evidence": "AI workload characterization mentioned but no performance comparison frameworks, needed for agent selection and optimization", "severity": "medium" } ], - "history": [] + "history": [ + { + "id": 2, + "snapshot_id": 1, + "gap_topic": "Agent Behavioral Verification", + "gap_description": "No drafts address how to verify that deployed AI agents are actually behaving according to their declared policies or specifications. This creates a gap between policy definition and runtime assurance.", + "severity": "critical", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 7, + "snapshot_id": 1, + "gap_topic": "Agent Capability Negotiation", + "gap_description": "Agents need standardized protocols to negotiate their capabilities and limitations before collaboration. Tool enumeration exists but not dynamic capability negotiation during runtime.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 9, + "snapshot_id": 1, + "gap_topic": "Agent Failure Cascade Prevention", + "gap_description": "No protocols exist to prevent agent failures from cascading across interconnected autonomous systems. This is critical as agent interdependencies increase in production deployments.", + "severity": "critical", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 11, + "snapshot_id": 1, + "gap_topic": "Agent Performance Benchmarking", + "gap_description": "No standardized metrics or protocols exist for comparing agent performance across different implementations, making it difficult to evaluate and select appropriate agents for specific tasks.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 5, + "snapshot_id": 1, + "gap_topic": "Agent Resource Accounting and Billing", + "gap_description": "Multi-tenant environments need standardized ways to track and bill for AI agent resource consumption across compute, network, and storage. Current drafts define resources but not accounting mechanisms.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 8, + "snapshot_id": 1, + "gap_topic": "Cross-Domain Agent Audit Trails", + "gap_description": "When agents operate across multiple domains or organizations, there's no standardized format for maintaining audit trails that satisfy different regulatory requirements simultaneously.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 3, + "snapshot_id": 1, + "gap_topic": "Cross-Protocol Agent Migration", + "gap_description": "Agents need to migrate between different network protocols, domains, or infrastructure providers while maintaining state and identity. Current drafts focus on registration but not migration continuity.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 6, + "snapshot_id": 1, + "gap_topic": "Federated Agent Learning Privacy", + "gap_description": "While federated architectures exist, there's insufficient specification for privacy-preserving agent learning that prevents data leakage between federated participants during model updates.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 10, + "snapshot_id": 1, + "gap_topic": "Human Override Standardization", + "gap_description": "While human-agent interaction exists, there's no standardized protocol for human operators to override autonomous agent decisions across different vendor implementations and domains.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 1, + "snapshot_id": 1, + "gap_topic": "Multi-Agent Consensus Protocols", + "gap_description": "While A2A protocols exist, there's no standardized approach for multiple AI agents to reach consensus on shared decisions or conflicting objectives. This becomes critical when agents must coordinate on resource allocation or policy enforcement across domains.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 4, + "snapshot_id": 1, + "gap_topic": "Real-Time Agent Rollback Mechanisms", + "gap_description": "When autonomous agents make incorrect decisions, there's no standardized protocol for quickly rolling back their actions across distributed systems. This is critical for network operations and safety.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:06:32.803029+00:00", + "snapshot_at": "2026-03-03T23:59:47.420517+00:00" + }, + { + "id": 13, + "snapshot_id": 2, + "gap_topic": "Agent Behavioral Verification", + "gap_description": "No drafts address how to verify that deployed AI agents are actually behaving according to their declared policies or specifications. This creates a gap between policy definition and runtime assurance.", + "severity": "critical", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 18, + "snapshot_id": 2, + "gap_topic": "Agent Capability Negotiation", + "gap_description": "Agents need standardized protocols to negotiate their capabilities and limitations before collaboration. Tool enumeration exists but not dynamic capability negotiation during runtime.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 20, + "snapshot_id": 2, + "gap_topic": "Agent Failure Cascade Prevention", + "gap_description": "No protocols exist to prevent agent failures from cascading across interconnected autonomous systems. This is critical as agent interdependencies increase in production deployments.", + "severity": "critical", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 22, + "snapshot_id": 2, + "gap_topic": "Agent Performance Benchmarking", + "gap_description": "No standardized metrics or protocols exist for comparing agent performance across different implementations, making it difficult to evaluate and select appropriate agents for specific tasks.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 16, + "snapshot_id": 2, + "gap_topic": "Agent Resource Accounting and Billing", + "gap_description": "Multi-tenant environments need standardized ways to track and bill for AI agent resource consumption across compute, network, and storage. Current drafts define resources but not accounting mechanisms.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 19, + "snapshot_id": 2, + "gap_topic": "Cross-Domain Agent Audit Trails", + "gap_description": "When agents operate across multiple domains or organizations, there's no standardized format for maintaining audit trails that satisfy different regulatory requirements simultaneously.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 14, + "snapshot_id": 2, + "gap_topic": "Cross-Protocol Agent Migration", + "gap_description": "Agents need to migrate between different network protocols, domains, or infrastructure providers while maintaining state and identity. Current drafts focus on registration but not migration continuity.", + "severity": "medium", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 17, + "snapshot_id": 2, + "gap_topic": "Federated Agent Learning Privacy", + "gap_description": "While federated architectures exist, there's insufficient specification for privacy-preserving agent learning that prevents data leakage between federated participants during model updates.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 21, + "snapshot_id": 2, + "gap_topic": "Human Override Standardization", + "gap_description": "While human-agent interaction exists, there's no standardized protocol for human operators to override autonomous agent decisions across different vendor implementations and domains.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 12, + "snapshot_id": 2, + "gap_topic": "Multi-Agent Consensus Protocols", + "gap_description": "While A2A protocols exist, there's no standardized approach for multiple AI agents to reach consensus on shared decisions or conflicting objectives. This becomes critical when agents must coordinate on resource allocation or policy enforcement across domains.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + }, + { + "id": 15, + "snapshot_id": 2, + "gap_topic": "Real-Time Agent Rollback Mechanisms", + "gap_description": "When autonomous agents make incorrect decisions, there's no standardized protocol for quickly rolling back their actions across distributed systems. This is critical for network operations and safety.", + "severity": "high", + "status": "open", + "recorded_at": "2026-03-04T00:09:12.383015+00:00", + "snapshot_at": "2026-03-04T00:09:01.501362+00:00" + } + ] } \ No newline at end of file diff --git a/docs/data/meta.json b/docs/data/meta.json index c00103b..fdd5e45 100644 --- a/docs/data/meta.json +++ b/docs/data/meta.json @@ -1,5 +1,5 @@ { - "generated_at": "2026-03-03T23:32:29.056739+00:00", + "generated_at": "2026-03-04T00:09:19.610824+00:00", "version": "0.3.0", "project": "IETF Living Standards Observatory" } \ No newline at end of file diff --git a/docs/data/observatory.json b/docs/data/observatory.json index bf3f6ed..bd26db8 100644 --- a/docs/data/observatory.json +++ b/docs/data/observatory.json @@ -1,9 +1,12 @@ { - "total_docs": 361, - "sources": {}, - "gaps_count": 12, + "total_docs": 434, + "sources": { + "ietf": 433, + "w3c": 0 + }, + "gaps_count": 11, "unrated": 0, - "ideas": 1780, + "ideas": 1907, "authors": 557, - "last_update": null + "last_update": "2026-03-04T00:09:01.501362+00:00" } \ No newline at end of file diff --git a/docs/data/timeline.json b/docs/data/timeline.json index 6816317..b599ec6 100644 --- a/docs/data/timeline.json +++ b/docs/data/timeline.json @@ -2,11 +2,18 @@ "months": [ "2024-01", "2024-02", + "2024-03", "2024-04", + "2024-06", + "2024-07", + "2024-08", "2024-09", "2024-10", + "2024-11", "2024-12", "2025-01", + "2025-02", + "2025-03", "2025-04", "2025-05", "2025-06", @@ -18,56 +25,115 @@ "2025-12", "2026-01", "2026-02", - "2026-03" + "2026-03", + "2026012" ], "by_category": { "2024-01": { - "Agent identity/auth": 1, - "Policy/governance": 1, - "Other AI/agent": 1, - "Data formats/interop": 1, - "AI safety/alignment": 1 + "Autonomous netops": 3, + "Agent discovery/reg": 1, + "Agent identity/auth": 2, + "AI safety/alignment": 2, + "ML traffic mgmt": 2, + "Policy/governance": 2, + "Data formats/interop": 2, + "Other AI/agent": 1 }, "2024-02": { + "Agent identity/auth": 1, "Autonomous netops": 1, - "ML traffic mgmt": 1 + "ML traffic mgmt": 1, + "Data formats/interop": 1, + "A2A protocols": 1 }, - "2024-04": { + "2024-03": { "A2A protocols": 1, - "Autonomous netops": 1, + "Agent identity/auth": 1, "Data formats/interop": 1 }, + "2024-04": { + "Agent identity/auth": 4, + "A2A protocols": 1, + "Autonomous netops": 3, + "Data formats/interop": 1, + "Policy/governance": 3, + "Agent discovery/reg": 1 + }, + "2024-06": { + "Data formats/interop": 2, + "Agent identity/auth": 1 + }, + "2024-07": { + "Agent identity/auth": 1, + "Autonomous netops": 2, + "Policy/governance": 1 + }, + "2024-08": { + "A2A protocols": 3, + "Policy/governance": 1 + }, "2024-09": { - "Autonomous netops": 1, - "Policy/governance": 1, + "Autonomous netops": 3, + "Policy/governance": 4, + "Data formats/interop": 5, + "Agent identity/auth": 3, + "A2A protocols": 2, + "Agent discovery/reg": 1, + "Human-agent interaction": 1, "ML traffic mgmt": 1 }, "2024-10": { "ML traffic mgmt": 1, - "Model serving/inference": 1 + "Model serving/inference": 1, + "Data formats/interop": 1 + }, + "2024-11": { + "Agent identity/auth": 2, + "Data formats/interop": 3, + "Autonomous netops": 1, + "A2A protocols": 1, + "Policy/governance": 1 }, "2024-12": { - "Other AI/agent": 1 + "Data formats/interop": 2, + "Agent discovery/reg": 2, + "Other AI/agent": 5, + "Autonomous netops": 1, + "ML traffic mgmt": 1 }, "2025-01": { - "Data formats/interop": 2, + "Data formats/interop": 4, "ML traffic mgmt": 4, - "Model serving/inference": 2 + "Model serving/inference": 2, + "Agent identity/auth": 3, + "A2A protocols": 1 + }, + "2025-02": { + "Other AI/agent": 1 + }, + "2025-03": { + "Autonomous netops": 1, + "Agent identity/auth": 1, + "Agent discovery/reg": 1, + "Other AI/agent": 1 }, "2025-04": { - "Policy/governance": 3, - "Agent identity/auth": 1, - "Data formats/interop": 2, + "Policy/governance": 5, + "Agent identity/auth": 3, + "Data formats/interop": 4, "AI safety/alignment": 1, - "Autonomous netops": 1, + "Autonomous netops": 2, + "Agent discovery/reg": 1, "Model serving/inference": 1, "ML traffic mgmt": 1 }, "2025-05": { - "Policy/governance": 2, - "Agent discovery/reg": 1, - "Data formats/interop": 1, - "Human-agent interaction": 1 + "Agent identity/auth": 4, + "Data formats/interop": 3, + "A2A protocols": 2, + "Agent discovery/reg": 2, + "Policy/governance": 3, + "Human-agent interaction": 2 }, "2025-06": { "Agent identity/auth": 2, @@ -109,50 +175,50 @@ }, "2025-10": { "Policy/governance": 10, - "Data formats/interop": 36, + "Data formats/interop": 35, "Model serving/inference": 9, "ML traffic mgmt": 13, - "Autonomous netops": 19, - "Agent discovery/reg": 15, - "Agent identity/auth": 24, + "Autonomous netops": 18, + "Agent discovery/reg": 14, + "Agent identity/auth": 19, "Human-agent interaction": 7, - "A2A protocols": 28, + "A2A protocols": 25, "AI safety/alignment": 5, - "Other AI/agent": 5 + "Other AI/agent": 4 }, "2025-11": { - "A2A protocols": 29, + "A2A protocols": 28, "Autonomous netops": 18, - "Data formats/interop": 25, + "Data formats/interop": 22, "ML traffic mgmt": 9, - "Agent discovery/reg": 18, - "Agent identity/auth": 23, - "AI safety/alignment": 7, - "Policy/governance": 15, - "Human-agent interaction": 9, + "Agent discovery/reg": 17, + "Agent identity/auth": 16, + "AI safety/alignment": 5, + "Policy/governance": 12, + "Human-agent interaction": 8, "Model serving/inference": 4, "Other AI/agent": 2 }, "2025-12": { "Policy/governance": 6, - "Data formats/interop": 6, + "Data formats/interop": 5, "Human-agent interaction": 1, - "Agent identity/auth": 8, + "Agent identity/auth": 7, "Autonomous netops": 4, "Other AI/agent": 2, "A2A protocols": 2, "ML traffic mgmt": 3, "AI safety/alignment": 3, - "Agent discovery/reg": 4, + "Agent discovery/reg": 3, "Model serving/inference": 1 }, "2026-01": { - "Agent identity/auth": 18, + "Agent identity/auth": 16, "AI safety/alignment": 8, "Policy/governance": 14, "A2A protocols": 22, "Agent discovery/reg": 15, - "ML traffic mgmt": 8, + "ML traffic mgmt": 7, "Data formats/interop": 17, "Autonomous netops": 16, "Model serving/inference": 5, @@ -160,59 +226,84 @@ "Human-agent interaction": 2 }, "2026-02": { - "A2A protocols": 38, + "A2A protocols": 40, "Human-agent interaction": 6, - "Data formats/interop": 32, - "Agent identity/auth": 34, + "Data formats/interop": 31, + "Agent identity/auth": 36, "Policy/governance": 24, - "Autonomous netops": 18, + "Autonomous netops": 20, "ML traffic mgmt": 15, "Agent discovery/reg": 19, - "Other AI/agent": 8, - "AI safety/alignment": 13, + "Other AI/agent": 9, + "AI safety/alignment": 15, "Model serving/inference": 8 }, "2026-03": { - "ML traffic mgmt": 11, - "A2A protocols": 9, + "ML traffic mgmt": 14, + "A2A protocols": 19, + "Agent identity/auth": 23, + "Policy/governance": 11, + "Agent discovery/reg": 8, + "Human-agent interaction": 3, "Model serving/inference": 9, - "Agent identity/auth": 3, - "Data formats/interop": 5, - "Autonomous netops": 8, - "Policy/governance": 6, - "Agent discovery/reg": 3, - "Human-agent interaction": 1, - "Other AI/agent": 1, - "AI safety/alignment": 1 + "Data formats/interop": 15, + "AI safety/alignment": 2, + "Autonomous netops": 10, + "Other AI/agent": 3 + }, + "2026012": { + "Policy/governance": 1, + "Human-agent interaction": 1 } }, "by_source": { "2024-01": { - "ietf": 3 + "ietf": 7 }, "2024-02": { - "ietf": 1 + "ietf": 3 + }, + "2024-03": { + "ietf": 2 }, "2024-04": { - "ietf": 1 + "ietf": 6 + }, + "2024-06": { + "ietf": 2 + }, + "2024-07": { + "ietf": 2 + }, + "2024-08": { + "ietf": 3 }, "2024-09": { - "ietf": 2 + "ietf": 11 }, "2024-10": { - "ietf": 1 + "ietf": 2 }, - "2024-12": { - "ietf": 1 - }, - "2025-01": { + "2024-11": { "ietf": 4 }, + "2024-12": { + "ietf": 8 + }, + "2025-01": { + "ietf": 8 + }, + "2025-02": { + "ietf": 1 + }, + "2025-03": { + "ietf": 2 + }, "2025-04": { - "ietf": 5 + "ietf": 9 }, "2025-05": { - "ietf": 2 + "ietf": 7 }, "2025-06": { "ietf": 5 @@ -227,22 +318,25 @@ "ietf": 17 }, "2025-10": { - "ietf": 67 - }, - "2025-11": { "ietf": 61 }, + "2025-11": { + "ietf": 53 + }, "2025-12": { - "ietf": 16 + "ietf": 15 }, "2026-01": { - "ietf": 54 + "ietf": 51 }, "2026-02": { - "ietf": 86 + "ietf": 88 }, "2026-03": { - "ietf": 22 + "ietf": 53 + }, + "2026012": { + "ietf": 1 } }, "categories": [ diff --git a/src/ietf_analyzer/sources/w3c.py b/src/ietf_analyzer/sources/w3c.py index 1e45d77..a48fa7d 100644 --- a/src/ietf_analyzer/sources/w3c.py +++ b/src/ietf_analyzer/sources/w3c.py @@ -22,6 +22,23 @@ W3C_API = "https://api.w3.org" console = Console() +# AI/agent-relevant W3C groups with their full API type prefix +W3C_AI_GROUPS = { + "webagents": "cg/webagents", # Autonomous Agents on the Web + "agentprotocol": "cg/agentprotocol", # AI Agent Protocol + "agentic-arbitration": "cg/agentic-arbitration", # Agentic Arbitration Protocol + "ai-content-disclosure": "cg/ai-content-disclosure", + "aikr": "cg/aikr", # AI Knowledge Representation + "ai-web-visibility": "cg/ai-web-visibility", + "aiwss": "cg/aiwss", # AI-Driven Web Standards + "cogai": "cg/cogai", # Cognitive AI + "credentials": "cg/credentials", # Credentials CG + "did": "wg/did", # Decentralized Identifier WG + "vc": "wg/vc", # Verifiable Credentials WG + "webmachinelearning": "wg/webmachinelearning", # Web Machine Learning WG + "wot": "wg/wot", # Web of Things WG +} + def _strip_html(html: str) -> str: """Minimal HTML tag stripper — no heavy dependencies.""" @@ -38,20 +55,31 @@ def _strip_html(html: str) -> str: class W3CFetcher: - """Fetch specs from the W3C public API (no auth needed).""" + """Fetch specs from the W3C public API (no auth needed). + + Two strategies: + 1. Browse /specifications paginated, filter client-side by keywords + 2. Fetch specs linked from known AI-relevant groups + Both are combined for maximum coverage. + """ def __init__(self, config: Config | None = None): self.config = config or Config.load() self.client = httpx.Client(timeout=30, follow_redirects=True) - self.groups = self.config.w3c_groups def search( self, keywords: list[str], since: str | None = None ) -> list[SourceDocument]: - """Fetch specs from AI-relevant W3C groups, filtered by keywords.""" + """Fetch AI-relevant W3C specs via keyword search over /specifications.""" seen: dict[str, SourceDocument] = {} kw_lower = [k.lower() for k in keywords] + # Strategy 1: Paginate through /specifications, filter client-side + console.print(" Searching W3C specifications catalog...") + page = 1 + max_pages = 17 # ~1679 specs total + checked = 0 + with Progress( SpinnerColumn(), TextColumn("[progress.description]{task.description}"), @@ -59,93 +87,72 @@ class W3CFetcher: MofNCompleteColumn(), console=console, ) as progress: - task = progress.add_task("Fetching W3C specs...", total=len(self.groups)) + task = progress.add_task("W3C catalog...", total=max_pages) - for group in self.groups: - progress.update(task, description=f"W3C group: {group}") - specs = self._fetch_group_specs(group) - for spec in specs: - # Client-side keyword filter on title + description - haystack = (spec.title + " " + spec.abstract).lower() - if any(kw in haystack for kw in kw_lower): - if since and spec.time and spec.time < since: - continue - if spec.name not in seen: - seen[spec.name] = spec - progress.advance(task) + while page <= max_pages: + progress.update(task, description=f"W3C catalog page {page}/{max_pages}") + try: + resp = self.client.get( + f"{W3C_API}/specifications", + params={"format": "json", "page": page}, + headers={"Accept": "application/json"}, + ) + resp.raise_for_status() + data = resp.json() + except httpx.HTTPError as e: + console.print(f"[yellow]W3C API error on page {page}: {e}[/]") + break - console.print(f"Found [bold green]{len(seen)}[/] W3C specs matching keywords") - return list(seen.values()) - - def _fetch_group_specs(self, group_shortname: str) -> list[SourceDocument]: - """Fetch all specifications for a W3C group.""" - url = f"{W3C_API}/groups/{group_shortname}/specifications" - specs: list[SourceDocument] = [] - - try: - page = 1 - while True: - resp = self.client.get( - url, - params={"format": "json", "page": page}, - headers={"Accept": "application/json"}, - ) - resp.raise_for_status() - data = resp.json() - - spec_list = data if isinstance(data, list) else data.get("_links", {}).get("specifications", []) - if not spec_list: - # Try alternate response shape - spec_list = data.get("specifications", []) + spec_list = data.get("_links", {}).get("specifications", []) if not spec_list: break + max_pages = data.get("pages", max_pages) + progress.update(task, total=max_pages) + for item in spec_list: + title = item.get("title", "") href = item.get("href", "") - shortname = item.get("shortname", "") - title = item.get("title", shortname) - - if not shortname and href: - # Extract shortname from href like /specifications/webnn - parts = href.rstrip("/").split("/") - shortname = parts[-1] if parts else "" - + shortname = href.rstrip("/").split("/")[-1] if href else "" if not shortname: continue + checked += 1 - # Fetch spec detail for abstract/description + # Quick keyword check on title + if not any(kw in title.lower() for kw in kw_lower): + continue + + # Fetch detail for description, URL, dates detail = self._fetch_spec_detail(shortname) - abstract = detail.get("description", title) - spec_url = detail.get("editor-draft", detail.get("url", f"https://www.w3.org/TR/{shortname}/")) - status = detail.get("status", "") + abstract = _strip_html(detail.get("description", title)) + spec_url = detail.get("editor-draft") or detail.get("url") or f"https://www.w3.org/TR/{shortname}/" date = detail.get("date", "") + status = detail.get("status", "") - specs.append( - SourceDocument( - name=f"w3c-{shortname}", - title=title, + if since and date and date < since: + continue + + name = f"w3c-{shortname}" + if name not in seen: + seen[name] = SourceDocument( + name=name, + title=detail.get("title", title), abstract=abstract, source="w3c", source_id=shortname, source_url=spec_url, time=date, doc_status=status, - extra={"group": group_shortname}, ) - ) - time_mod.sleep(0.3) - # Check pagination - pages = data.get("pages", 1) if isinstance(data, dict) else 1 - if page >= pages: - break + time_mod.sleep(0.15) + + progress.advance(task) page += 1 - time_mod.sleep(0.3) + time_mod.sleep(0.2) - except httpx.HTTPError as e: - console.print(f"[yellow]W3C API error for {group_shortname}: {e}[/]") - - return specs + console.print(f" Checked {checked} W3C specs, found [bold green]{len(seen)}[/] matching keywords") + return list(seen.values()) def _fetch_spec_detail(self, shortname: str) -> dict: """Fetch detail for a single spec.""" @@ -156,13 +163,14 @@ class W3CFetcher: ) resp.raise_for_status() data = resp.json() + latest = data.get("_links", {}).get("latest-version", {}) return { "description": data.get("description", ""), "title": data.get("title", shortname), "editor-draft": data.get("editor-draft", ""), - "url": data.get("_links", {}).get("latest-version", {}).get("href", ""), - "status": data.get("_links", {}).get("latest-version", {}).get("status", ""), - "date": data.get("_links", {}).get("latest-version", {}).get("date", ""), + "url": latest.get("href", ""), + "status": latest.get("title", ""), + "date": latest.get("href", "").rstrip("/").split("/")[-1] if latest.get("href") else "", } except httpx.HTTPError: return {}