Hi Haisheng, Regarding conformance to RDAP practices, you should read: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-extensions/
Who will be running the RDAP servers for this registration data? -andy, as a participant On 22-05-2026 6:03 AM, yuhaisheng wrote:
Hi Med, all, Thank you very much for forwarding the draft to REGEXT. I would like to briefly share the motivation and scope of this early individual draft. The draft explores whether RDAP can be used as a registration data access mechanism for Agent identifiers. The motivation comes from ongoing discussions around AI agent communication, discovery, accountability, and auditability. In those discussions, there is a recurring need to distinguish between real-time discovery information and relatively stable registration data. For example, an Agent identifier may need associated registration data such as: * the responsible entity or operator; * lifecycle state, such as active, suspended, revoked, or expired; * associated domain names, IPv6 locators, IPv6 prefixes, or Agent Gateways; * public key or certificate references; * policy references and revocation status; * security or operational contact information. The draft does not define a new agent discovery protocol, interaction protocol, authentication mechanism, or real-time reachability service. It is intended to explore a narrower question: whether an RDAP profile could provide structured access to relatively stable Agent identifier registration data, in a way similar to how RDAP is used for Internet resource registration data. I would especially appreciate feedback from the REGEXT community on: 1. whether RDAP is an appropriate basis for this kind of Agent identifier registration data; 2. whether the proposed object class, query path, and JSON members are aligned with RDAP design practices; 3. whether this should be positioned as an RDAP profile, an extension, or only as a set of considerations at this stage; 4. what privacy, redaction, access-control, or operational issues should be addressed before developing the draft further. This is an early draft, and I would be happy to revise the scope and structure based on feedback from RDAP and REGEXT experts. Best regards, Haisheng Yu China Internet Network Information Center [email protected] ---- Replied Message ---- From <[email protected]> <mailto:[email protected]> Date 5/22/2026 16:09 To [email protected]<[email protected]> <mailto:[email protected]> Cc [email protected]<[email protected]> <mailto:[email protected]> Subject TR: I-D Action: draft-yu-agent-identifier-rdap-00.txt Hi Haisheng, Forwarding to regext, fwiw. Feel free to share more context and your plans with this document :-) Cheers, Med -----Message d'origine----- De : [email protected] <[email protected]> Envoyé : vendredi 22 mai 2026 09:23 À : [email protected] Objet : I-D Action: draft-yu-agent-identifier-rdap-00.txt Internet-Draft draft-yu-agent-identifier-rdap-00.txt is now available. Title: An RDAP Profile for Agent Identifier Registration Data Author: Haisheng Yu Name: draft-yu-agent-identifier-rdap-00.txt Pages: 12 Dates: 2026-05-22 Abstract: AI agents may need stable identifiers that are independent from their current network locations. In agent deployments, an Agent identifier may be associated with IPv6 locators, IPv6 prefixes, Agent Gateways, public key references, policy references, lifecycle state, and revocation status. Applications, gateways, controllers, and operators need a trusted way to query this registration data. This document defines an RDAP profile for querying Agent identifier registration data. The profile reuses the Registration Data Access Protocol (RDAP) query model and JSON response format, and defines an RDAP object class and extension members for Agent identifiers, IPv6 locator bindings, Agent Gateway bindings, and related operational metadata. This document does not define a new agent discovery protocol, a new agent interaction protocol, or a new authentication mechanism. It defines a registration data access profile that can be used by agent deployments and by other agent-related systems that need trusted Agent identifier metadata. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-yu-agent-identifier-rdap/ ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
