Service Binding Mapping for Agents
draft-zhang-aiproto-svcb-mapping-for-agents-01

Network Working Group                                           M. Zhang
Internet-Draft                                                  Z.W. Yan
Intended status: Informational                                 K.J. Dong
Expires: 6 July 2026                                             H.T. Li
                                                                   CNNIC
                                                          2 January 2026

                   Service Binding Mapping for Agents
             draft-zhang-aiproto-svcb-mapping-for-agents-01

Abstract

   With the continuous introduction of intelligent agent communication
   and interaction protocols, the current DNS cannot adequately meet the
   requirements for agent service resolution.  This document defines a
   new DNS resource record type, AGENT, which is a SVCB-compatible RR
   type, and specifies the mapping specifications.

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 6 July 2026.

Copyright Notice

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

Zhang, et al.              Expires 6 July 2026                  [Page 1]
Internet-Draft     Service Binding Mapping for Agents       January 2026

   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.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Basic requirements  . . . . . . . . . . . . . . . . . . . . .   3
   4.  SvcParamKeys defined by SVCB  . . . . . . . . . . . . . . . .   3
     4.1.  "alpn"  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  "port"  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.3.  "ipv4hint" and "ipv6hint" . . . . . . . . . . . . . . . .   4
   5.  Definition of the New SvcParamKeys  . . . . . . . . . . . . .   4
     5.1.  "apn" . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  "agentpath" . . . . . . . . . . . . . . . . . . . . . . .   4
     5.3.  "descpath"  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Requirements notation

   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

   Building on the existing DNS, SVCB records provide additional
   convenience for clients to select different services and obtain the
   parameters required for connections.

Zhang, et al.              Expires 6 July 2026                  [Page 2]
Internet-Draft     Service Binding Mapping for Agents       January 2026

   With the rapid development of artificial intelligence, various
   communication and interaction protocols related to agents are
   currently being developed.  Agents have put forward new technical
   requirements in terms of session, communication, service invocation,
   and collaboration, and existing DNS cannot adequately meet the needs
   of agent service resolution.

   This document defines a new DNS resource record type, AGENT, which is
   a SVCB-compatible RR type, and specifies the mapping specifications
   required by SVCB.

3.  Basic requirements

   To provide special handling for agent service use cases, the AGENT RR
   type is defined as a SVCB-compatible RR type, specific to the "agent"
   scheme.

   The presentation format of the record is: Name TTL IN AGENT
   SvcPriority TargetName SvcParams

4.  SvcParamKeys defined by SVCB

   The SVCB record [RFC9460] defines a set of initial SvcParamKeys,
   which are applicable to the AGENT scheme.

4.1.  "alpn"

   This key indicates the set of protocols supported by the endpoint.

   When a specific protocol is designated, corresponding configurations
   shall be implemented via other parameters in accordance with the
   usage requirements and specifications of that protocol, so as to
   provide a complete protocol suite supporting it.

   Otherwise, setting only this value without specifying other necessary
   parameters for the protocol shall be considered an error.

4.2.  "port"

   The "port" SvcParamKey defines the port number to be used for
   connecting to this alternative endpoint.

   If this key is not present, the client shall use the default port
   number of the transport protocol.

Zhang, et al.              Expires 6 July 2026                  [Page 3]
Internet-Draft     Service Binding Mapping for Agents       January 2026

4.3.  "ipv4hint" and "ipv6hint"

   The "ipv4hint" and "ipv6hint" keys convey the IP addresses that the
   client may use to access the agent service.

5.  Definition of the New SvcParamKeys

   In addition to the aforementioned SvcParamKeys defined by SVCB, this
   document specifies new SvcParamKeys for agent service usage.

5.1.  "apn"

   The "apn" SvcParamKey is used to indicate the protocol employed for
   agent communication and interaction, where "apn" refers to Agent
   Protocol Negotiation.

   When a specific protocol is designated, other parameters must be
   configured in accordance with the usage requirements and
   specifications of that protocol to provide a complete protocol suite
   supporting it.

   Otherwise, setting only this value without specifying other necessary
   parameters for the protocol shall be considered an error.

   The "apn" key shall be used in conjunction with the "alpn" key.

   Since some agent-related protocols are currently in the stage of
   discussion and revision, the usage and supporting requirements of
   this parameter will be updated accordingly based on the release of
   future protocols.

5.2.  "agentpath"

   The value of the "agentpath" SvcParamKey is the URI template of the
   agent.

5.3.  "descpath"

   Agent description information includes attribute details such as
   agent identity, authentication, capabilities, and collaboration
   mechanisms.  Currently, its specific form varies across different
   protocols.

   The "descpath" SvcParamKey is used to identify the access address
   (e.g., the URL) of the agent's detailed information.

Zhang, et al.              Expires 6 July 2026                  [Page 4]
Internet-Draft     Service Binding Mapping for Agents       January 2026

6.  Security Considerations

   The use of DNSSEC is optional for AGENT records.

   The downgrade attacks relevant to the SVCB record are also applicable
   to this document.

7.  IANA Considerations

   To be determined.

8.  Acknowledgments

   To be determined.

9.  References

9.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

9.2.  Informative References

   [RFC9460]  Schwartz, B., Bishop, M., and E. Nygren, "Service Binding
              and Parameter Specification via the DNS (SVCB and HTTPS
              Resource Records)", RFC 9460, DOI 10.17487/RFC9460,
              November 2023, <https://www.rfc-editor.org/info/rfc9460>.

Authors' Addresses

   Man Zhang
   CNNIC
   Email: zmjy_9@163.com

   Zhiwei Yan
   CNNIC
   Email: yan@cnnic.cn

Zhang, et al.              Expires 6 July 2026                  [Page 5]
Internet-Draft     Service Binding Mapping for Agents       January 2026

   Kejun Dong
   CNNIC
   Email: dongkejun@cnnic.cn

   Hongtao Li
   CNNIC
   Email: lihongtao@cnnic.cn

Zhang, et al.              Expires 6 July 2026                  [Page 6]