Agent Directory Service

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 28 September 2025.¶

Copyright Notice

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

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.¶

Table of Contents

1. Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

2. Introduction

The Agent Directory Service (ADS) provides a mechanism for discovering AI agent applications based on their capabilities. It uses a distributed directory architecture to map agent skills to directory record identifiers and maintains a list of directory servers hosting those records.¶

Directory records are identified by globally unique names that are routable within a DHT (Distributed Hash Table) to locate peer directory servers. The skill taxonomy is also routable in the DHT to map skillsets to records that announce those skills.¶

Each directory record includes skills from a defined taxonomy, as specified in the [Taxonomy of AI Agent Skills] from [OASF]. While all record data is modeled using [OASF], only skills are leveraged for content routing in the distributed network of directory servers.¶

This document describes the core concepts and architecture of the Agent Directory Service.¶

3. Naming

In distributed systems, a reliable and collision-resistant naming scheme is crucial. The agent directory uses cryptographic hashes [RFC7838] to generate globally unique identifiers for data records.¶

ADS leverages OCI as object storage, and therefore identifiers are made available as described in [OCI digest].¶

4. Content Routing

ADS implements capability-based record discovery through a hierarchical skill taxonomy. This architecture enables:¶

                             +----------------+
                             |    DHT Node    |
                             | Content Index  |
                             +----------------+
                                    ^
                                    |
                   +----------------+-----------------+
                   |                |                |
           +-------v------+  +------v-------+  +-----v--------+
           | Server Node A |  | Server Node B|  | Server Node C|
           |   Content X  |  |   Content Y  |  |   Content Z  |
           +-------+------+  +------+-------+  +------+-------+
                   |               |                  |
                   |        Content Exchange          |
                   +---------------+------------------+
                                  |
                          Content Replication

Flow:
1. Servers register content with DHT
2. DHT maintains content-to-server mappings
3. Servers query DHT to locate content
4. DHT returns list of servers hosting content
5. Servers download content from peers

5. IANA Considerations

This document has no IANA actions.¶

6. References

Authors' Addresses