Jan, Fair point. AID doesn't define "agent" because the term means different things depending on the protocol (MCP servers, A2A agents, OpenAPI services etc.). What AID discovers is an endpoint that speaks one of those protocols (and future protocols that will come around). On the wire it's a server, but the AI ecosystem loosely calls them "agents" regardless. I'll tighten the glossary in -01. Dave flagged the same thing.
On Wed, Mar 18, 2026 at 1:02 AM Jan Schaumann <jschauma= [email protected]> wrote: > Balazs Nemethi <[email protected]> wrote: > > > We submitted an Internet-Draft for Agent Identity & Discovery (AID) last > > weekend: > > > > > https://datatracker.ietf.org/doc/draft-nemethi-aid-agent-identity-discovery/ > > > > AID does one thing: given a domain, find the agent endpoint and figure > out > > which protocol to speak. One TXT record at _agent.<domain>: > > I think the document could benefit from a very quick > definition of "agent", "agent endpoint", and "agent > service" (or a reference to where these are clearly > defined). > > Not knowing what exact definition they might have, I > can only interpret this to mean "special endpoints > that AI driven bots could (should?) access", but it's > not clear to me how those differ from other endpoints, > or whether the "agent" acts as a client or a server > (it sounds like "agents" are servers, but that > conflicts with my current image of what an "agent" > is or does). > > -Jan > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- *Balazs Nemethi* Founder, Agent Community <http://agentcommunity.org>
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
