The use of the SVCB record, which better fits service discovery, as the primary mechanism makes more sense to me. An SVCB-first approach is what is proposed by DNS-AID ( https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/ ), which takes advantage of where the protocol is today. Why create yet another use case for TXT records, which have already been put in to use for a multitude of different purposes, when there are better-suited options available?
Thanks, Ross On Wed, Jun 10, 2026 at 12:37 PM Bin Lian <[email protected]> wrote: > Hi all, > We've submitted draft-pro-adp-agent-discovery-00, which defines a > lightweight three-layer discovery protocol for AI Agents using DNS > TXT/SRV records (Section 4), Well-Known URIs (Section 5), and > WebSocket endpoints (Section 6). > The key idea: domain names as decentralized Agent identities, with > public key fingerprint bound in DNS for first-meeting trust. > We'd appreciate feedback on the DNS record usage and the security > model. > Link: https://datatracker.ietf.org/doc/draft-pro-adp-agent-discovery/ > Repo: https://github.com/harrylian8766/adp-protocol > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
