The Scope Creep Automated reviews of new AI-related working group submissions

Review · August 21, 2026

DAWN Gap Analysis

draft-moussa-dawn-gap-analysis -01View on Datatracker →

Problem Statement

DAWN (Discovery of Agents, Workloads, and Named entities) is a proposed IETF effort to define interoperable mechanisms for discovering AI agents, tools, compute resources, datasets, and other entities across administrative and network boundaries. This draft is a gap analysis — it does not propose any new protocol. Instead, it evaluates roughly 15 existing discovery mechanisms (DNS, mDNS, WebFinger, A2A Agent Cards, CATS, SSDP, manual configuration, and others) against the emerging DAWN requirements to identify what is missing and motivate future standards work.

How the Spec Fits In

This is an informational document, not a standards-track specification. It has no direct relationship to OAuth or the OAuth working group — it lives in the AI/networking space around multi-domain agent discovery. It does not define new mechanisms, extend any existing RFC, or create new protocol behaviors. Its role is to survey the existing landscape and justify the need for new work that the DAWN effort would produce.

The spec depends on three other DAWN individual drafts (problem statement, requirements, use cases) that are themselves not yet adopted working group documents.

High-Level Summary

The draft reviews each discovery mechanism across five dimensions: security, privacy, applicability to DAWN, operational cost, and mitigation cost. Every mechanism evaluated receives a DAWN suitability score of 1–2 out of 3, meaning none fully meets DAWN requirements. The consistent finding is that existing mechanisms were built for narrower use cases — DNS resolves names, WebFinger resolves identifiers, mDNS serves local networks, A2A Agent Cards handle agent-centric deployments — and none supports the combination of federated, semantically rich, privacy-preserving, cross-domain discovery of heterogeneous entities (agents, tasks, datasets, sensors) that DAWN envisions.

The analysis also consistently identifies a need for a separate "catalog layer" on top of these resolution mechanisms to support capability-based search, which no existing protocol provides.

Interoperability and Necessity of the Spec

As an informational gap analysis, interoperability is not directly applicable. However, the quality of the analysis matters for whether it will successfully justify and guide future DAWN protocol work.

Significant completeness concerns: At revision -01, roughly half the mechanisms listed in the scope are marked "To be completed," including DNS-AID, MCP, AGNTCY, service registries (Kubernetes/Consul), HTTP well-known, search/crawling, centralized marketplaces, and P2P/DHT. The security considerations section is also unfinished, and the use-cases summary section is entirely absent pending an upstream draft. This significantly limits the document's current utility.

Evaluation methodology is sound but somewhat circular: The scoring framework is well-structured, but mechanisms predictably score low (1/3) because they were never designed to meet DAWN requirements. The more interesting analysis would be identifying which combinations of existing mechanisms come closest to meeting DAWN requirements and which specific gaps remain unbridgeable without new protocol work — the draft gestures at this but doesn't fully deliver it.

Mechanisms that could be streamlined: The mitigation tables for each mechanism are extensive and fairly repetitive — nearly every mechanism ends up needing "signed descriptors + a separate catalog layer + rate limiting." These could be consolidated into a single cross-cutting section rather than repeated per mechanism.

Writing Quality

The completed sections are generally well-written with clear structure, consistent use of IETF terminology, and appropriate hedging. The evaluation tables are useful and readable. However, the large number of "To be completed" stubs gives the document an unfinished feel that is unusual for a -01 submission. A gap analysis with half its gaps unanalyzed is difficult to evaluate or act on. The scoring rubric (0–3) is defined clearly but applied inconsistently — mDNS scores 2/3 while DNS scores 1/3, but the reasoning for the difference is not made crisp.

The document is appropriately scoped as informational and does not overreach into normative territory.

Background of the Authors

Hesham Moussa (Huawei Technologies Canada)

  • RFCs published: 0
  • Active Internet-Drafts: 5 (all co-authored with Akhavain, all focused on AI discovery and networking)
  • Assessment: New IETF participant with no prior RFC publication history. All active work is clustered in the DAWN/AI-networking space, suggesting a coordinated push rather than broad IETF engagement.

Arashmid Akhavain (Huawei Technologies Canada)

  • RFCs published: 0
  • Active Internet-Drafts: 5 (same set as Moussa)
  • Expired drafts: 5 (from mobile/DMM and sensing-data spaces, suggesting broader prior IETF activity)
  • Assessment: Has more IETF history than Moussa through the expired drafts, but no RFC publications. The expired drafts span different working groups (DMM, MoQ), indicating the current DAWN focus is a newer direction.

Both authors are from the same Huawei Canada team and appear to be driving a coordinated set of DAWN-related individual submissions alongside the DAWN problem statement draft. Their IETF experience is limited but Akhavain has some prior engagement across working groups.