← Reading listAgendaReviewdatatracker ↗ draft-miao-dawn-agw-intergration-consideration-00 · none · 20 pp · 2026-11-02 · offline copy



DAWN                                                             C. Miao
Internet-Draft                                                   R. Chen
Intended status: Informational                           ZTE Corporation
Expires: 6 May 2027                                      2 November 2026


 Considerations for Agent Gateway Integration within the DAWN Framework
           draft-miao-dawn-agw-intergration-consideration-00

Abstract

   This document specifies the integration architecture, discovery proxy
   mechanisms, and operational workflows for the Agent Gateway (AGW)
   within the Discovery of Agents With Names (DAWN) problem space.
   Addressing the core problem of how an agent discovers peer agents
   across administrative and network boundaries, this specification
   defines the dual role of the Agent Gateway: serving as an Outbound
   Discovery Proxy (Discovery Substrate Access Point) that assists local
   domain agents in querying external discovery fabrics, and an Inbound
   Domain Discovery Proxy (Broker/Aggregator) that enables external
   agents to discover matching capabilities situated on sub-agents
   behind the gateway.  The document outlines the internal capability
   matching engine, selective disclosure mechanisms for privacy
   preservation, DNS-SD/mDNS resource record mappings, and strict
   boundary alignments with the IETF DAWN Working Group Charter.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2027.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.




Miao & Chen                Expires 6 May 2027                   [Page 1]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology and Conceptual Mapping  . . . . . . . . . . . . .   4
   3.  Dual-Directional Discovery Proxy Architecture and Operational
           Modes . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Mode A: Outbound Discovery Proxy (Serving Local Agents to
           Discover External Entities) . . . . . . . . . . . . . . .   6
       3.1.1.  Mode A work flow: Outbound Agent Discovery via AGW
               Access Point  . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Mode B: Inbound Domain Discovery Proxy (Serving External
           Agents to Discover Sub-Agents Behind Gateway) . . . . . .   8
     3.3.  Mode B work flow: Inbound Discovery of Sub-Agent
           Capabilities Behind AGW . . . . . . . . . . . . . . . . .   9
     3.4.  Sub-Agent Discovery Scenarios Across Network
           Topologies  . . . . . . . . . . . . . . . . . . . . . . .  10
       3.4.1.  Scenario 1: Single-Domain Single-Agent Environment  .  10
       3.4.2.  Scenario 2: Single-Domain Multi-Agent LAN
               Environment . . . . . . . . . . . . . . . . . . . . .  10
       3.4.3.  Scenario 3: Cross-Domain Multi-Agent Environment  . .  11
   4.  Agent Gateway Roles in DNS-SD / mDNS Discovery  . . . . . . .  11
   5.  Scope Alignment: Agent Gateway Architecture vs. IETF DAWN
           Charter Scope . . . . . . . . . . . . . . . . . . . . . .  14
     5.1.  Scope Boundaries Summary  . . . . . . . . . . . . . . . .  14
     5.2.  Detailed Scope Boundary Analysis  . . . . . . . . . . . .  15
   6.  Technical Resolution Matrix: DAWN Challenges vs. AGW
           Interventions . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   8.  Appendix: Use Cases and Deployment Scenarios  . . . . . . . .  18
     8.1.  Use Case 1: Sub-Agent Registration and LAN Discovery in
           Smart Home  . . . . . . . . . . . . . . . . . . . . . . .  18
     8.2.  Use Case 2: Campus AGW Capability Indexing & Emergency
           Discovery . . . . . . . . . . . . . . . . . . . . . . . .  19
     8.3.  Use Case 3: Vehicle Agent Discovering Home Sub-Agent
           Capabilities Behind Residential Gateway . . . . . . . . .  19
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  19
     10.2.  Informative References . . . . . . . . . . . . . . . . .  19



Miao & Chen                Expires 6 May 2027                   [Page 2]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   The rapid proliferation of artificial intelligence entities,
   autonomous workloads, specialized datasets, and compute resources has
   highlighted a fundamental architectural challenge in modern network
   infrastructure: how can an autonomous agent discover another agent or
   discover a specific capability situated behind an administrative
   boundary in a secure, privacy-preserving, and interoperable manner?

   As described in the DAWN Problem Statement and established in the
   IETF DAWN Working Group Charter, current discovery methods are
   heavily fragmented.  Existing systems rely on proprietary
   directories, static IP configurations, or localized name lookups that
   fail to scale across administrative trust boundaries, cannot express
   dynamic entity attributes (such as real-time compute load or
   availability status), and lack standardized mechanisms for
   discovering sub-agents operating within private local networks behind
   Network Address Translation (NAT) and firewalls.

   The DAWN framework establishes a high-level lifecycle for interacting
   entities, spanning identity provisioning, authentication,
   authorization, access to a Discovery Substrate via an Access Point,
   peer-to-peer invocation, and continuous monitoring.  However,
   realizing this lifecycle across heterogeneous networks requires a
   concrete middleware component capable of bridging local domain
   mechanisms with wide-area discovery fabrics.

   The Agent Gateway (AGW) serves as that essential universal
   infrastructure component.  Operating at the boundary of
   administrative domains, the Agent Gateway acts primarily as a Dual-
   Directional Discovery Proxy:

   1.  Outbound Discovery Proxy (Access Point Mode): Assisting resource-
       constrained or domain-internal agents in querying wide-area DAWN
       discovery substrates, resolving remote agent endpoints, and
       verifying peer credentials without requiring every local node to
       implement complex wide-area discovery protocols.












Miao & Chen                Expires 6 May 2027                   [Page 3]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   2.  Inbound Domain Discovery Proxy (Aggregator/Broker Mode):
       Receiving external DAWN discovery queries, evaluating query
       parameters against an internal Local Agent Registry, performing
       capability matching for sub-agents situated behind the gateway,
       and exporting an aggregated Minimum Discoverable Information
       (MDI) descriptor.  This mechanism enables external agents to
       discover matching sub-agent capabilities while shielding internal
       network topologies, sub-agent IP addresses, and private domain
       architecture.

2.  Terminology and Conceptual Mapping

   This document aligns with the core terminology established in the
   DAWN problem space and the Agent Gateway functional specifications.
   Key terms include:

   *  Agent Gateway (AGW): A logical or physical middleware gateway
      deployed at domain boundaries or central management hubs,
      responsible for cross-domain trust, protocol translation, task
      routing, and capability discovery.

   *  Discovery Substrate: The underlying distributed framework or
      federation protocol through which discoverable objects are
      registered, indexed, searched, and resolved.

   *  Discoverable Object: The formal descriptor (such as an Agent Card
      or Task Card) exposed by an entity or gateway to represent its
      capabilities, requirements, or endpoints within the discovery
      substrate.

   *  Minimum Discoverable Information (MDI): The standardized minimal
      payload structure embedded in a Discoverable Object, containing
      essential identity, skill schemas, security requirements, dynamic
      health metrics, and communication URIs necessary for remote
      entities to determine interaction suitability.

   *  A2A Gateway: The AGW functional sub-module dedicated to inter-
      agent protocol translation, authentication, task lifecycle
      management, P2P NAT traversal, and skill routing.

   *  Network Gateway: The AGW functional sub-module handling transport-
      layer connectivity, STUN/TURN/ICE P2P traversal, link failover,
      and quality-of-service (QoS) management.








Miao & Chen                Expires 6 May 2027                   [Page 4]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


     +=============================+================================+
     | DAWN Conceptual Requirement | Agent Gateway Architecture     |
     |                             | Realization                    |
     +=============================+================================+
     | *Discovery Substrate Access | AGW Outbound Discovery Engine  |
     | Point*                      | & Wide-Area Query Relay        |
     +-----------------------------+--------------------------------+
     | *Broker / Aggregator        | AGW Inbound Discovery Proxy &  |
     | Entity*                     | Aggregated MDI Exporter        |
     +-----------------------------+--------------------------------+
     | *Discoverable Object / MDI* | Aggregated Agent Card exposed  |
     |                             | at /.well-known/agent.json     |
     +-----------------------------+--------------------------------+
     | *Sub-Agent Discovery Behind | AGW Local Agent Registry &     |
     | Gateway*                    | Internal Capability Matcher    |
     +-----------------------------+--------------------------------+
     | *Selective Disclosure &     | AGW Topology Obfuscation & MDI |
     | Privacy*                    | Masking Engine                 |
     +-----------------------------+--------------------------------+
     | *Dynamic Attribute          | AGW TTL Cache & Active         |
     | Handling*                   | Heartbeat Monitor              |
     +-----------------------------+--------------------------------+
     | *Local / Wide-Area          | Dual-Mode mDNS (LAN) / Unicast |
     | Resolution*                 | DNS-SD (WAN) Responder         |
     +-----------------------------+--------------------------------+

                                 Table 1

3.  Dual-Directional Discovery Proxy Architecture and Operational Modes

   The following diagram below illustrates the dual-directional
   discovery proxy architecture of the Agent Gateway within the DAWN
   framework:


















Miao & Chen                Expires 6 May 2027                   [Page 5]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


+-----------------------------------------------------------------------------------+
|                            DAWN Wide-Area Discovery Substrate                     |
+-----------------------------------------------------------------------------------+
            ^                                                   ^
            | [Mode A: Outbound Discovery Proxy]                | [Mode B: Inbound Domain Discovery Proxy]
            | (Discovers External Entities for Local Agents)    | (Receives Inbound Queries, Matches Sub-Agents)
            v                                                   v
+-----------------------------------------------------------------------------------+
|                              Agent Gateway (AGW)                                  |
|   +---------------------------------------------------------------------------+   |
|   |  - Local Agent Registry (Internal Agent Capability Registry)              |   |
|   |  - Capability Matcher & Attribute Indexer (Capability Matcher Engine)     |   |
|   |  - Selective MDI Aggregator (Selective Disclosure & Masking)              |   |
|   +---------------------------------------------------------------------------+   |
+-----------------------------------------------------------------------------------+
            ^                                                   ^
            | (LAN Lightweight Registration & Query)            | (Internal Gateway Routing & Obfuscation)
            v                                                   v
+--------------------------+                             +--------------------------+
| Requesting Agent (Intra) |                             |   Matched Sub-Agent B    |
|  (e.g., Vehicle Agent)   |                             |  (e.g., Internal HVAC)   |
+--------------------------+                             +--------------------------+

3.1.  Mode A: Outbound Discovery Proxy (Serving Local Agents to Discover
      External Entities)

   In Mode A, a local domain agent needs to discover an external agent
   or service operating in a remote domain or public federation.  Rather
   than requiring the local agent to implement wide-area DNS-SD
   resolution, mTLS certificate validation, and complex DHT lookup
   protocols, the local agent delegates the discovery task to the Agent
   Gateway:

   1.  Local Query Submission: The local agent issues a lightweight
       discovery query (e.g., via local mDNS or HTTP GET) to the AGW,
       specifying required skills, domain parameters, or target entity
       names.

   2.  AGW Substrate Resolution: The AGW acts as the DAWN Discovery
       Substrate Access Point, querying wide-area DNS-SD registries,
       federated AGW peers, or public DAWN indexers.

   3.  Validation & Filtering: The AGW retrieves candidate MDI
       descriptors, verifies cryptographic domain signatures, enforces
       local security policies, and filters out unverified or malicious
       endpoints.





Miao & Chen                Expires 6 May 2027                   [Page 6]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   4.  Response Delivery: The AGW returns a sanitized list of verified
       remote agent endpoints to the requesting local agent.

3.1.1.  Mode A work flow: Outbound Agent Discovery via AGW Access Point

+-------------------+        +-------------------------+        +-------------------+        +---------------------+
| Local Sub-Agent A |        | Local AGW (Domain A)    |        | Wide-Area DNS     |        | Remote AGW          |
|  (Requesting)     |        | (Discovery Access Point)|        | Server (DNS-SD)   |        | (Domain B)          |
+-------------------+        +-------------------------+        +-------------------+        +---------------------+
          |                               |                               |                             |
          | (1) POST /local-discovery     |                               |                             |
          |     (Query: logistics_skill)  |                               |                             |
          |------------------------------>|                               |                             |
          |                               | (2) Unicast DNS-SD Query      |                             |
          |                               |     _dawn-agw._tcp.domain.org |                             |
          |                               |------------------------------>|                             |
          |                               |<------------------------------|                             |
          |                               | (3) PTR, SRV, TXT Answer      |                             |
          |                               |                               |                             |
          |                               | (4) Out-of-band Fetch MDI     |                             |
          |                               |     GET /.well-known/agent.json                             |
          |                               |------------------------------------------------------------>|
          |                               |<------------------------------------------------------------|
          |                               | (5) Full MDI Descriptor       |                             |
          |                               |                               |                             |
          |                               | (6) Validate Provenance & Cert|                             |
          | (7) Return Filtered Candidates|                               |                             |
          |<------------------------------|                               |                             |

   The execution sequence below details how a local sub-agent delegates
   wide-area agent discovery to the Agent Gateway acting as a DAWN
   Discovery Substrate Access Point.

   1.  Local Internal Discovery Query (Step 1): Local Sub-Agent A (a
       lightweight entity in Domain A) requires a third-party logistics
       agent.  Lacking wide-area DNS-SD capabilities, Sub-Agent A sends
       a simple local discovery request to Local AGW (POST /local-
       discovery).

   2.  Wide-Area DAWN Substrate Resolution (Step 2 & 3): Local AGW acts
       as the Discovery Substrate Access Point.  It executes unicast
       DNS-SD queries against wide-area DNS servers, searching for
       _dawn-agw._tcp PTR, SRV, and TXT resource records.  The DNS
       infrastructure returns candidate gateway endpoints.







Miao & Chen                Expires 6 May 2027                   [Page 7]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   3.  Out-of-Band Remote MDI Fetch (Step 4 & 5): Local AGW contacts
       candidate Remote AGW (Domain B) at its HTTPS MDI URI (/.well-
       known/agent.json) to fetch the full JSON-Schema capability
       descriptor.

   4.  Policy & Cryptographic Validation (Step 6): Local AGW validates
       Remote AGW's domain provenance, verifies cryptographic
       certificate chains, and filters out candidate endpoints that fail
       domain security policies.

   5.  Filtered Candidate Delivery (Step 7): Local AGW returns a
       verified, sanitized list of discovered remote agent endpoints to
       Local Sub-Agent A, completing the outbound discovery sequence.

3.2.  Mode B: Inbound Domain Discovery Proxy (Serving External Agents to
      Discover Sub-Agents Behind Gateway)

   In Mode B, an external remote agent seeks to discover whether a
   specific capability (e.g., skill: hvac_control or skill:
   energy_storage_query) is available within Domain B.  The internal
   sub-agents possessing these capabilities reside behind symmetric NATs
   or corporate firewalls and cannot directly expose public IP addresses
   or DNS records.

   The AGW processes the inbound discovery request through the following
   steps:

   1.  Inbound Query Reception: The external agent queries the AGW's
       public MDI endpoint (/.well-known/agent.json) or performs a DNS-
       SD TXT lookup against _dawn-agw._tcp.example.org.

   2.  Internal Capability Matching: The AGW's Capability Matcher
       queries the Local Agent Registry, cross-referencing requested
       skill IDs, version constraints, and dynamic status (e.g., current
       load and online status of sub-agents).

   3.  Selective MDI Aggregation: If one or more internal sub-agents
       match the requested criteria, the AGW constructs an aggregated
       MDI payload.  The MDI reports that Domain B possesses the
       requested capabilities and provides the AGW's public ingress URI
       as the reachable endpoint.

   4.  Topology Concealment: The internal sub-agent's private IP
       address, host identifier, hardware architecture, and internal
       network placement remain completely hidden from the external
       requester.





Miao & Chen                Expires 6 May 2027                   [Page 8]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


3.3.  Mode B work flow: Inbound Discovery of Sub-Agent Capabilities
      Behind AGW

+------------------+         +-----------------------+         +---------------------+         +----------------------+
| External Agent   |         | Target AGW (Domain B) |         | Local Agent Registry|         | Internal Sub-Agent B |
|   (Domain A)     |         |                       |         |                     |         |                      |
+------------------+         +-----------------------+         +---------------------+         +----------------------+
         |                               |                                |                               |
         |                               |<===============================|===============================| (0) Intra-domain Register
         |                               |  Register (skill: hvac_control)|                               |     (schema, endpoint)
         |                               |------------------------------->|                               |
         |                               |  Store Sub-Agent Entry         |                               |
         |                               |                                |                               |
         | (1) Inbound DAWN Query:       |                                |                               |
         |   GET /.well-known/agent.json |                                |                               |
         |------------------------------>|                                |                               |
         |                               | (2) Match Skill                |                               |
         |                               |------------------------------->|                               |
         |                               |     Query: skill=hvac_control  |                               |
         |                               |<-------------------------------|                               |
         |                               | (3) Return Sub-Agent B Match   |                               |
         |                               |                                |                               |
         |                               | (4) Aggregate MDI & Mask IPs   |                               |
         | (5) Return Aggregated MDI     |                                |                               |
         |     (200 OK, Public Ingress)  |                                |                               |
         |<------------------------------|                                |                               |

   The execution sequence below details how an External Requester Agent
   discovers matching sub-agent capabilities situated behind a Target
   Agent Gateway (Domain B) while preserving domain topology privacy.

   1.  Internal Sub-Agent Capability Registration (Step 0): Upon
       initialization within private Domain B, Internal Sub-Agent B
       (e.g., an HVAC Controller) sends an intra-domain registration
       payload to Target AGW.  The registration contains Sub-Agent B's
       fine-grained skill schema (skill_id: hvac_control), versioning,
       required authorization scopes, and internal transport endpoint.
       Target AGW validates the payload and stores the entry in its
       Local Agent Registry.

   2.  Inbound DAWN MDI Discovery Query (Step 1): External Agent (Domain
       A) seeks an entity capable of managing environmental controls in
       Domain B.  It issues an HTTP GET request to Target AGW's
       standardized MDI endpoint (GET /.well-known/agent.json).

   3.  Internal Capability Matching (Step 2 & 3): Target AGW receives
       the query and invokes its Capability Matcher engine.  The engine
       queries the Local Agent Registry, searching for active sub-agents



Miao & Chen                Expires 6 May 2027                   [Page 9]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


       matching skill: hvac_control with online status and available
       capacity.  The registry confirms that Sub-Agent B matches all
       criteria.

   4.  Selective MDI Aggregation & Topology Masking (Step 4): Target AGW
       constructs a public Discoverable Object (Aggregated Agent Card).
       Crucially, the gateway strips out Sub-Agent B's internal IP
       address, internal host name, and network topology.  It
       substitutes its own public HTTPS/WebSocket ingress URI as the
       official reachability endpoint.

   5.  MDI Response Delivery (Step 5): Target AGW returns the aggregated
       MDI payload (HTTP 200 OK) to External Agent.  External Agent
       successfully discovers that Domain B supports hvac_control and
       learns the public endpoint and authentication requirements
       necessary for subsequent interaction.

   *Mode A work flow (Outbound Discovery)* and *Mode B work flow
   (Inbound Discovery)* fall directly *IN-SCOPE* for the IETF DAWN
   Working Group, as they pertain exclusively to initial capability
   querying, DNS-SD resolution, and Minimum Discoverable Information
   (MDI) retrieval.

3.4.  Sub-Agent Discovery Scenarios Across Network Topologies

   Following the multi-agent communication scenario analysis, AGW
   discovery proxying adapts to three canonical deployment environments:

3.4.1.  Scenario 1: Single-Domain Single-Agent Environment

   In localized environments (such as a smart device hub controlling
   local sensors), the embedded AGW translates local device protocol
   schemas (MQTT/Modbus) into standard Agent Cards.  The AGW registers
   local capabilities with intra-domain mDNS responders (.local domain),
   allowing local discovery while preventing unauthorized WAN exposure.

3.4.2.  Scenario 2: Single-Domain Multi-Agent LAN Environment

   In smart campus or enterprise LAN environments, multiple sub-agents
   (Lighting Agent, Security Agent, HVAC Agent) co-exist across VLANs.
   The Campus AGW acts as the central Intra-Domain Capability Registry.
   Sub-agents register their skills upon boot.  When an emergency event
   occurs, the Security Agent queries the AGW to discover local HVAC and
   Notification sub-agents via LAN-first mDNS/DNS-SD without requiring
   internet connectivity.






Miao & Chen                Expires 6 May 2027                  [Page 10]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


3.4.3.  Scenario 3: Cross-Domain Multi-Agent Environment

   In cross-domain environments (e.g., a Vehicle Agent querying a Home
   Domain AGW), the Vehicle Agent cannot access the private residential
   LAN.  The Vehicle Agent queries the Home AGW's public DAWN MDI
   endpoint.  The Home AGW matches the request against its internal
   registry (finding local HVAC and Garage controllers), evaluates OAuth
   2.0 authorization scopes, enforces Human-In-The-Loop (HITL) safety
   policies for high-risk skills, and returns an aggregated MDI
   descriptor.

4.  Agent Gateway Roles in DNS-SD / mDNS Discovery

   The IETF DAWN framework leverages the Domain Name System (DNS) and
   Multicast DNS (mDNS) as foundational transport mechanisms for initial
   AI resource locating.  However, standard DNS infrastructures are
   inherently static, domain-unaware, and incapable of representing
   complex AI agent capability hierarchies, dynamic health metrics, or
   topology isolation policies.  Within the DAWN discovery fabric, the
   Agent Gateway (AGW) serves as the essential intelligent mediation
   layer between AI entities and the underlying DNS/mDNS protocols.

   When DNS-SD [RFC6763] and mDNS [RFC6762] are employed for DAWN
   discovery, the Agent Gateway fulfills four crucial architectural
   roles across local and wide-area networks:


























Miao & Chen                Expires 6 May 2027                  [Page 11]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


+---------------------------------------------------------------------------------------+
|                             Wide-Area DNS (Unicast DNS-SD)                            |
|             _dawn-agw._tcp.example.com. IN PTR / SRV / TXT / A / AAAA                 |
+---------------------------------------------------------------------------------------+
                                           ^
                                           | Unicast DNS Updates / Resolution (WAN)
                                           v
+---------------------------------------------------------------------------------------+
|                               Agent Gateway (AGW)                                     |
|                                                                                       |
|  [ Role 1: LAN mDNS Responder ]    <--->  Local Multicast mDNS (UDP 5353, .local)     |
|  [ Role 2: WAN DNS-SD Aggregator ] <--->  Authoritative DNS Zone Management           |
|  [ Role 3: Outbound DNS Resolver]  <--->  Wide-Area DNSSEC & Policy Validation         |
|  [ Role 4: Dynamic TTL/MDI Adapter] <---> Two-Stage Filtering & Cache Control         |
|                                                                                       |
|  +---------------------------------------------------------------------------------+  |
|  | Local Agent Registry  | Capability Matcher Engine | Topology Masking Module    |  |
|  +---------------------------------------------------------------------------------+  |
+---------------------------------------------------------------------------------------+
      ^                                                                         ^
      | Intra-Domain Registration / Query                                       | Direct Inbound Discovery
      v                                                                         v
+-----------------------+                                       +-----------------------+
| Internal Sub-Agents   |                                       | External Requesters   |
| (HVAC, Security, etc) |                                       | (Remote Agents / AGW) |
+-----------------------+                                       +-----------------------+

   1.  *Local LAN mDNS Proxy Registrar & Responder*:

       *  _Problem_: Lightweight or specialized internal sub-agents
          (e.g., embedded sensors, HVAC controllers, micro-agents) often
          lack full mDNS/DNS-SD protocol stacks or cannot safely
          participate in LAN multicast traffic.

       *  _AGW Role_: The AGW runs an internal mDNS Responder (listening
          on UDP port 5353).  As internal sub-agents register their
          skills with the gateway's Local Agent Registry, the AGW
          automatically proxies and announces their capabilities on the
          local subnet under the .local domain.  When local peers query
          for available capabilities, the AGW responds on behalf of all
          internal sub-agents, eliminating the need for every micro-
          agent to host a standalone mDNS daemon.

   2.  *Wide-Area DNS-SD Authoritative Aggregator & Topology Masking
       Proxy*:






Miao & Chen                Expires 6 May 2027                  [Page 12]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


       *  _Problem_: Directly publishing individual sub-agent hostnames,
          private IP addresses, or internal port numbers into public DNS
          zones creates severe security vulnerabilities, leaks network
          topology, and fails for nodes situated behind NATs.

       *  _AGW Role_: The AGW acts as an authoritative DNS-SD aggregator
          for wide-area domain zones (e.g., _dawn-agw._tcp.example.org).
          Instead of exposing individual sub-agents, the AGW aggregates
          internal skill schemas into a unified gateway descriptor.  It
          registers *itself* as the sole public SRV target and A/AAAA
          endpoint, completely shielding internal sub-agent IP
          addresses, host counts, and network topologies from WAN
          inspection.

   3.  *Outbound DNS Discovery Proxy & Safety Filter*:

       *  _Problem_: Internal sub-agents seeking external services often
          lack the complexity to perform multi-stage DNS-SD PTR/SRV/TXT
          parsing, validate DNSSEC cryptographic provenance, or enforce
          domain security policies.

       *  _AGW Role_: The AGW serves as an outbound DNS resolution
          proxy.  A local sub-agent issues a simplified discovery
          request to the gateway; the AGW executes unicast DNS-SD
          queries across wide-area DNS servers, validates DNSSEC
          signatures, verifies remote gateway certificate chains,
          filters out unverified or malicious endpoints, and returns a
          sanitized list of verified remote targets to the local
          requester.

   4.  *Dynamic Attribute Adapter & DNS TTL Cache Manager*:

       *  _Problem_: Standard DNS infrastructures are optimized for
          static or slow-changing resource records, whereas AI agents
          exhibit highly dynamic operational states (e.g., real-time
          CPU/memory load, instant availability status, dynamic skill
          enablement).  Storing rapidly changing metrics directly in DNS
          causes record thrashing, excessive DNS traffic, and stale
          caching issues.

       *  _AGW Role_: The AGW reconciles standard DNS caching mechanics
          with dynamic AI agent states by enforcing a strict separation:

          -  _Static / Semi-Static Attributes_ (Skill IDs, protocol
             versions, authentication methods, domain endpoints) are
             mapped into DNS-SD TXT records with moderate TTL values
             (120s - 300s).




Miao & Chen                Expires 6 May 2027                  [Page 13]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


          -  _Highly Dynamic Metrics_ (real-time load, queue depth,
             precise memory availability) are excluded from DNS records
             and served dynamically during the Stage 2 out-of-band HTTPS
             MDI query, ensuring DNS records remain stable while real-
             time state remains accurate.

5.  Scope Alignment: Agent Gateway Architecture vs. IETF DAWN Charter
    Scope

   To ensure strict compliance with IETF standardization boundaries, the
   table and text below delineate which Agent Gateway functions fall
   directly within the IETF DAWN Working Group Charter scope and which
   represent out-of-scope downstream middleware functions.

5.1.  Scope Boundaries Summary

   *  IETF DAWN Working Group Scope (In-Scope):

      -  Initial Client Locating & Endpoint Resolution;

      -  Public Minimum Discoverable Information (MDI) Payload
         Structure;

      -  DNS-SD / mDNS Resource Record Mappings (_dawn-agw._tcp);

      -  Aggregated Broker Discovery & Selective Disclosure Principles.

   *  Agent Gateway Downstream Functions (Out-of-Scope for DAWN):

      -  Post-Discovery Task Execution & Message Dispatch (POST /a2a/
         tasks);

      -  Fine-grained Tool Schema Validation & Execution Sandboxing (MCP
         Gateway);

      -  LLM Inference Proxying & Semantic Caching (Model Routing
         Gateway);

      -  OAuth 2.0 / mTLS Identity Issuance & Human-In-The-Loop (HITL)
         Intercept;

      -  STUN/TURN P2P Transport & NAT Traversal (Network Gateway).









Miao & Chen                Expires 6 May 2027                  [Page 14]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


5.2.  Detailed Scope Boundary Analysis

   1.  Initial Locating vs. Post-Discovery Execution: The DAWN Charter
       explicitly limits its work to the initial phase of locating and
       discovering AI resources.  In the AGW architecture, MDI querying
       and DNS-SD resolution belong strictly to DAWN.  Once an agent
       discovers the AGW endpoint, subsequent task submission (POST
       /a2a/tasks), asynchronous queuing, and message passing fall
       outside DAWN's scope and are governed by inter-agent protocols
       (e.g., A2A / MCP).

   2.  Public MDI vs. Detailed Capability Catalogs: The DAWN Charter
       specifies that detailed catalogs of capabilities are out of
       scope.  AGW aligns with this by exposing only high-level skill
       tags, protocol versions, and security requirements in the public
       MDI (agent.json).  Deep tool parameter schemas (JSON RPC /
       OpenAPIs) remain behind the gateway, managed by the MCP Gateway
       upon authenticated post-discovery invocation.

   3.  Identity Management & Trust: DAWN excludes deep trust management,
       relying on existing IETF standards (OAuth, WIMSE, PKIX).  AGW
       enforces OAuth 2.0 Bearer tokens [RFC7519] and mTLS [RFC8446] at
       the boundary, treating identity verification as an orthogonal
       dependency as specified by DAWN.



























Miao & Chen                Expires 6 May 2027                  [Page 15]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


    +=================+================+==============+===============+
    | Gateway         | IETF DAWN      | Responsible  | Applied       |
    | Operational     | Charter Status | AGW Sub-     | Standards /   |
    | Capability      |                | Module       | Protocol      |
    +=================+================+==============+===============+
    | *Initial Public | *In-Scope*     | Ingress &    | /.well-known/ |
    | MDI Discovery*  |                | Registration | agent.json,   |
    |                 |                | Engine       | DNS-SD        |
    +-----------------+----------------+--------------+---------------+
    | *Domain MDI     | *In-Scope*     | Selective    | DAWN MDI      |
    | Aggregation &   |                | Disclosure   | Schema,       |
    | Masking*        |                | Engine       | Selective     |
    |                 |                |              | Disclosure    |
    +-----------------+----------------+--------------+---------------+
    | *mDNS LAN /     | *In-Scope*     | Dual-Mode    | mDNS, DNS-SD  |
    | Unicast WAN     |                | DNS Engine   |               |
    | Discovery*      |                |              |               |
    +-----------------+----------------+--------------+---------------+
    | *Post-Discovery | *Out-of-Scope* | A2A Gateway  | Inter-Agent   |
    | Task Execution* |                | (POST /a2a/  | Protocol (A2A |
    |                 |                | tasks)       | / HTTP/2)     |
    +-----------------+----------------+--------------+---------------+
    | *OAuth2 / mTLS  | *Out-of-Scope  | Security     | OAuth 2.0 ,   |
    | Authentication* | (Dependency)*  | Module       | mTLS          |
    +-----------------+----------------+--------------+---------------+
    | *P2P Relay &    | *Out-of-Scope  | Network      | STUN/TURN/ICE |
    | NAT Traversal*  | (Transport)*   | Gateway      |               |
    +-----------------+----------------+--------------+---------------+

                                  Table 2

6.  Technical Resolution Matrix: DAWN Challenges vs. AGW Interventions

   The DAWN Problem Statement
   [I-D.akhavain-moussa-dawn-problem-statement] identifies six
   fundamental challenges facing internet-scale discovery.  The table
   below details how the Agent Gateway architecture resolves each
   challenge during the discovery phase:













Miao & Chen                Expires 6 May 2027                  [Page 16]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


     +===================+===========================================+
     | DAWN Core         | AGW Technical Intervention & Architecture |
     | Challenge         | Solution                                  |
     +===================+===========================================+
     | *Skills &         | AGW indexes internal sub-agent skills in  |
     | Capabilities at   | its Local Agent Registry, constructs      |
     | Scale*            | hierarchical capability trees, and        |
     |                   | exposes lightweight aggregated MDI        |
     |                   | schemas for fast wide-area matching.      |
     +-------------------+-------------------------------------------+
     | *Fragmented       | AGW acts as a universal discovery proxy,  |
     | Discovery         | bridging local mDNS/DDS/MQTT discovery    |
     | Ecosystem*        | mechanisms with wide-area unicast DNS-SD  |
     |                   | and DAWN JSON MDI endpoints.              |
     +-------------------+-------------------------------------------+
     | *Trust in         | AGW enforces mandatory mTLS for inter-    |
     | Discovery         | gateway peering, verifies DNS-SD DNSSEC   |
     | Information*      | signatures, and checks authoritative      |
     |                   | domain provenance to eliminate discovery  |
     |                   | poisoning.                                |
     +-------------------+-------------------------------------------+
     | *Scalability &    | AGW enables autonomous domain governance. |
     | Decentralization* | Each gateway manages its local sub-agent  |
     |                   | registry and publishes minimal MDI        |
     |                   | descriptors without relying on            |
     |                   | centralized internet directories.         |
     +-------------------+-------------------------------------------+
     | *Static vs.       | AGW separates long-lived static           |
     | Dynamic           | capabilities (skill IDs, protocol         |
     | Properties*       | versions) from dynamic operational status |
     |                   | (load, availability) using explicit TTL   |
     |                   | fields and active heartbeat validation.   |
     +-------------------+-------------------------------------------+
     | *Future           | AGW employs a modular, plugin-based       |
     | Extensibility*    | capability matching engine, permitting    |
     |                   | seamless integration of future AI entity  |
     |                   | types, specialized model formats, and new |
     |                   | network transports.                       |
     +-------------------+-------------------------------------------+

                                  Table 3

7.  Security Considerations

   As the single ingress and egress boundary for cross-domain multi-
   agent discovery, the Agent Gateway MUST enforce strict security and
   privacy protections compliant with IETF guidelines:




Miao & Chen                Expires 6 May 2027                  [Page 17]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   *  Transport Security: All external discovery interfaces MUST require
      TLS 1.3 encryption [RFC8446].  Plaintext HTTP or unencrypted DNS
      queries over untrusted public networks MUST be upgraded to DoT
      (DNS over TLS, [RFC7858] or DoH (DNS over HTTPS, [RFC8484]).

   *  Anti-Poisoning & Authority Validation: AGWs MUST validate DNSSEC
      signatures for unicast DNS-SD records and verify OAuth 2.0 / JWT
      domain signatures to prevent malicious third parties from
      injecting toxic discovery responses.

   *  Selective Disclosure & Mutual Privacy: Conforming to [RFC6973] and
      DAWN privacy requirements, AGW implements selective disclosure.
      The gateway conceals internal sub-agent counts, private IP
      topologies, and hardware specifications, returning only aggregated
      MDI descriptors.  Simultaneously, discovery queries digest
      requester identity to limit intent tracking.

   *  Human-in-the-Loop (HITL) Out-of-Band Safety: High-risk operations
      discovered via MDI (marked with require_human_approval: true) MUST
      cause downstream execution engines to suspend task processing and
      push verification requests to the domain owner's authenticated
      device via an isolated push channel.

   *  Tamper-Proof Audit Logging: AGW components MUST record structured
      audit logs for all cross-domain discovery queries and capability
      lookups, capturing timestamp, issuer identity, target skill ID,
      and authorization scope.

8.  Appendix: Use Cases and Deployment Scenarios

   To provide practical guidance for implementers, this section details
   three representative deployment use cases focusing specifically on
   discovery workflows.

8.1.  Use Case 1: Sub-Agent Registration and LAN Discovery in Smart Home

   In a smart home environment, a localized Supervisor Agent acts as an
   embedded AGW.  When a new smart thermostat sub-agent boots up, it
   broadcasts an intra-domain mDNS registration (thermostat._dawn-
   agw._tcp.local.).  The embedded AGW stores the sub-agent's skill
   (skill: climate_control) in its Local Agent Registry.  When a local
   voice assistant agent queries the embedded AGW for climate control
   capabilities, the AGW matches the request instantly over LAN without
   querying external cloud servers.







Miao & Chen                Expires 6 May 2027                  [Page 18]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


8.2.  Use Case 2: Campus AGW Capability Indexing & Emergency Discovery

   A university campus operates multiple domain agents (Security, HVAC,
   Lighting) across distinct VLANs.  During an environmental safety
   incident, the Security Agent queries the Campus AGW seeking entities
   matching category: environmental_safety and latency: <50ms.  The
   Campus AGW checks its Local Agent Registry, matches the request to
   the HVAC Agent (skill: isolation_ventilation) and Lighting Agent
   (skill: emergency_strobe), and returns internal endpoints.  LAN-first
   resolution completes in < 10 ms, allowing immediate damper closure
   even if internet connectivity is severed.

8.3.  Use Case 3: Vehicle Agent Discovering Home Sub-Agent Capabilities
      Behind Residential Gateway

   An Autonomous Vehicle Agent (Domain A) approaching the owner's home
   (Domain B) queries the DAWN wide-area substrate to locate Domain B's
   Home AGW.  The Vehicle Agent fetches Domain B's aggregated MDI
   (/.well-known/agent.json), discovering available capabilities (skill:
   preheat_hvac and skill: unlock_garage_gate).  The Home AGW matches
   the request against its internal sub-agents while hiding private home
   IP addresses and network topology.  The Vehicle Agent obtains the
   Home AGW ingress endpoint and authentication requirements necessary
   for subsequent interaction.

9.  IANA Considerations

   TBC

10.  References

10.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/rfc/rfc2119>.

10.2.  Informative References

   [I-D.akhavain-moussa-dawn-problem-statement]
              Akhavain, A., Moussa, H., and D. King, "Problem Statement
              for the Discovery of Agents, Workloads, and Named Entities
              (DAWN)", Work in Progress, Internet-Draft, draft-akhavain-
              moussa-dawn-problem-statement-05, 19 July 2026,
              <https://datatracker.ietf.org/doc/html/draft-akhavain-
              moussa-dawn-problem-statement-05>.




Miao & Chen                Expires 6 May 2027                  [Page 19]

Internet-Draft        AGW Scenario Analysis in DAWN        November 2026


   [RFC6762]  Cheshire, S. and M. Krochmal, "Multicast DNS", RFC 6762,
              DOI 10.17487/RFC6762, February 2013,
              <https://www.rfc-editor.org/rfc/rfc6762>.

   [RFC6763]  Cheshire, S. and M. Krochmal, "DNS-Based Service
              Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013,
              <https://www.rfc-editor.org/rfc/rfc6763>.

   [RFC6973]  Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
              Morris, J., Hansen, M., and R. Smith, "Privacy
              Considerations for Internet Protocols", RFC 6973,
              DOI 10.17487/RFC6973, July 2013,
              <https://www.rfc-editor.org/rfc/rfc6973>.

   [RFC7519]  Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
              (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
              <https://www.rfc-editor.org/rfc/rfc7519>.

   [RFC7858]  Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D.,
              and P. Hoffman, "Specification for DNS over Transport
              Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May
              2016, <https://www.rfc-editor.org/rfc/rfc7858>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/rfc/rfc8446>.

   [RFC8484]  Hoffman, P. and P. McManus, "DNS Queries over HTTPS
              (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018,
              <https://www.rfc-editor.org/rfc/rfc8484>.

Authors' Addresses

   Chuanyang Miao
   ZTE Corporation
   Email: miao.chuanyang@zte.com.cn


   Ran Chen
   ZTE Corporation
   Email: chen.ran@zte.com.cn










Miao & Chen                Expires 6 May 2027                  [Page 20]