I-D Action: draft-raskar-agentic-web-federated-resolution-01.txt

[email protected]
Newsgroups gmane.ietf.announce
Message-ID <178457463669.192809.6436042799285582696@dt-datatracker-d4d6ff9d9-fsx7d>
Internet-Draft draft-raskar-agentic-web-federated-resolution-01.txt is now
available.

   Title:   Registry-Assisted Discovery for AI Agents and Workloads Without DNS Discovery Anchors
   Authors: Ramesh Raskar
            Samuel Sharaf
            Pradyumna Chari
   Name:    draft-raskar-agentic-web-federated-resolution-01.txt
   Pages:   26
   Dates:   2026-07-20

Abstract:

   Many agent-discovery mechanisms assume that an organization controls
   a DNS domain and can publish a DNS record, a well-known catalog, or
   an organization gateway. That model works well for enterprises with
   operational DNS infrastructure, but it does not cover every agent or
   workload. Small businesses may own a domain yet lack the expertise or
   infrastructure to publish agent-specific DNS records. Individuals may
   have a globally scoped account identifier, such as an email address,
   while not controlling the provider domain. Personal agents and other
   workloads may run on a cloud service or local device while their
   public descriptor is hosted elsewhere.

   This document describes registry-assisted discovery for these cases.
   A NandaIndex registry binds a stable Subject Identity to a
   subject-authorized terminal object, such as an A2A Agent Card, an MCP
   server descriptor, a workload descriptor, a subject-owned AI Catalog,
   or a subject-authorized gateway. The binding includes authority,
   freshness, and revocation information. The identity owner, descriptor
   host, and runtime operator may be different parties.

   This document does not define a directory of discovery servers,
   directory federation, or a global switchboard. A NandaIndex response
   does not direct a client to another generic resolution or discovery
   service. DNS-anchored systems remain direct: when an authoritative AI
   Catalog, DNS-AID record, or organization gateway is already known,
   NandaIndex is not in the critical path. The focus is permissionless
   publication and discovery for agents and workloads that do not have a
   usable DNS Discovery Anchor.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-raskar-agentic-web-federated-resolution/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-raskar-agentic-web-federated-resolution-01

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-raskar-agentic-web-federated-resolution-01

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.