<?xml version="1.0" encoding="US-ASCII"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
     by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-wang-dmsc-terminology-ioa-networking-00"
     ipr="trust200902">
  <front>
    <title abbrev="IoA Networking Infra Terminology">Terminology for
    Networking Infrastructure in the Internet of Agents</title>

    <author fullname="Xianghua Wang" initials="X" surname="Wang">
      <organization>CAICT</organization>

      <address>
        <postal>
          <street>Huayuan North Road, HaiDian District</street>

          <city>Beijing</city>

          <region>Beijing</region>

          <code>100191</code>

          <country>China</country>
        </postal>

        <email>wangxianghua@caict.ac.cn</email>
      </address>
    </author>

    <author fullname="Yihe Yang" initials="Y" surname="Yang">
      <organization>CAICT</organization>

      <address>
        <postal>
          <street>Huayuan North Road, HaiDian District</street>

          <city>Beijing</city>

          <region>Beijing</region>

          <code>100191</code>

          <country>China</country>
        </postal>

        <email>liyyh2025@gmail.com</email>
      </address>
    </author>

    <author fullname="Zhe Li" initials="Z" surname="Li">
      <organization>CAICT</organization>

      <address>
        <postal>
          <street>Huayuan North Road, HaiDian District</street>

          <city>Beijing</city>

          <region>Beijing</region>

          <code>100191</code>

          <country>China</country>
        </postal>

        <email>lizhe@caict.ac.cn</email>
      </address>
    </author>

    <date day="26" month="May" year="2026"/>

    <abstract>
      <t>The emergence of the Internet of Agents (IoA) introduces new
      requirements for interoperable collaboration among autonomous agents
      across heterogeneous networks, platforms, and administrative domains.
      Supporting such environments requires common understanding of
      infrastructure functions, collaboration mechanisms, semantic
      interaction, and trust-related concepts.</t>

      <t>This document defines terminology for networking infrastructure in
      IoA environments, with a focus on Dynamic Multi-agent Secured
      Collaboration (DMSC). The terminology defined in this document is
      intended to support consistent usage across DMSC-related architecture,
      framework, and protocol specifications.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>The Internet of Agents is emerging as a distributed collaboration
      environment in which autonomous agents interact across heterogeneous
      networks, platforms, administrative domains, and trust boundaries.
      Unlike traditional service-oriented systems, agent-based collaboration
      introduces dynamic capability discovery, semantic interaction, task
      coordination, and cross-domain interoperability requirements among
      intelligent entities.</t>

      <t>To support scalable and interoperable collaboration, networking
      infrastructure functions are required to provide registration,
      discovery, capability management, semantic routing, trust establishment,
      and coordination mechanisms across intra-domain and inter-domain
      environments. As DMSC (Dynamic Multi-agent Secured Collaboration)
      evolves to address these infrastructure challenges, consistent
      terminology becomes necessary to describe architectural concepts,
      collaboration behaviors, functional entities, and interaction processes
      in a unified manner.</t>

      <t>This document defines terminology for networking infrastructure in
      the Internet of Agents, with a focus on DMSC-related collaboration
      environments and infrastructure functions. The terminology defined in
      this document is intended to support consistent usage across
      DMSC-related architecture, framework, and protocol specifications.</t>

      <t>The terms defined in this document cover collaboration domains,
      functional entities, registration and discovery procedures, capability
      management, semantic interaction mechanisms, and trust-related concepts
      for interoperable multi-agent collaboration.</t>

      <t>This document defines terminology only and does not specify
      protocols, message formats, or implementation requirements.</t>
    </section>

    <section anchor="s-Inter-functional-entities"
             title="Functional Entity Terms">
      <t>The following terms define functional entities that collectively
      constitute IoA networking infrastructures.</t>

      <t><list style="symbols">
          <t>Internet of Agents(IoA): An Internet-based architecture that
          extends the existing Internet by taking autonomous agents as
          first-class interaction entities, and supports scalable
          communication, coordination, and information exchange across
          heterogeneous networks, platforms, systems, and administrative
          domains.</t>

          <t>Agent: An autonomous software or hardware entity capable of
          perceiving its environment, processing information, and performing
          actions to achieve defined objectives, either independently or
          through interaction with other agents within IoA.</t>

          <t>Agent Identifier: An identifier that uniquely distinguishes an
          agent.</t>

          <t>Agent Gateway: A functional entity that supports distributed
          agent registration, discovery, request coordination, and
          cross-domain information exchange.</t>

          <t>Capability Directory: A functional entity that maintains and
          provides capability-related information used for discovery and
          matching of agents. The capability information may be organized in
          forms such as capability registries, metadata directories, or other
          discoverable capability description structures.</t>

          <t>Registry Entity: A functional entity responsible for registering
          agents and maintaining their registration information.</t>

          <t>Agent Credential Service: A functional entity responsible for
          issuing, maintaining, and revoking Agent Credentials associated with
          agents.</t>

          <t>Trust Service: A functional entity responsible for validating
          Agent Credentials and managing trust relationships and trust
          policies between entities within or across collaboration
          domains.</t>

          <t>IOA Protocol Suite: A collection of interoperable protocols and
          protocol components that support agent registration, discovery,
          coordination, secure communication, capability synchronization,
          semantic interoperability, and cross-domain collaboration within IoA
          environments.</t>
        </list></t>
    </section>

    <section anchor="s-operational-mechanisms"
             title="Infrastructure Operational Behaviors and Mechanisms Terms">
      <t>The following terms define operational processes, coordination
      behaviors, and collaboration mechanisms used by IoA networking
      infrastructures to support agent collaboration, synchronization,
      registration, discovery, and semantic interaction.</t>

      <t><list style="numbers">
          <t>Registration<list style="symbols">
              <t>Agent Registration: The process by which an agent is
              onboarded into a collaboration domain and recorded in the
              registry system.</t>

              <t>Registration Function: A protocol or mechanism used for
              registering and maintaining unique Agent Identifiers.</t>

              <t>Registration Synchronization: The process of maintaining
              consistent Agent Identifier information within a single
              collaboration domain.</t>
            </list></t>

          <t>Discovery &amp; Capability<list style="symbols">
              <t>Capability Discovery: The process of locating agents based on
              their advertised capabilities or semantic descriptions.</t>

              <t>Capability Discovery Function: A protocol or mechanism used
              for discovering agent capability information based on capability
              queries, and returning matching capability descriptions or
              associated agents. Such a function may be realized through agent
              gateway-based discovery, capability directory lookup, or
              naming-system-assisted resolution.</t>

              <t>Capability Synchronization: The process of maintaining
              consistent capability directory within a single collaboration
              domain.</t>

              <t>Semantic Capability Matching: The process of matching
              requested intent or constraints with available capabilities
              using semantic understanding.</t>
            </list></t>

          <t>Semantic Interaction<list style="symbols">
              <t>Semantic Representation: A structured representation of
              intent, capability, task, and contextual information used for
              semantic interpretation and interoperability among agents and
              infrastructure entities.</t>

              <t>Semantic Interaction: A cross-domain interaction paradigm in
              IoA. It allows agents and infrastructure entities to unify
              intent, capability, task and context via semantic comprehension,
              and facilitates coordinated collaboration among heterogeneous
              domains.</t>

              <t>Semantic Interaction Function: A set of functional mechanisms
              that realize Semantic Interaction by enabling intent
              coordination, task coordination, context translation, semantic
              routing, and context synchronization among agents and
              infrastructure entities across domains.</t>

              <t>Semantic Routing: A routing process that selects
              collaboration paths, agents, or infrastructure entities based on
              semantic understanding of capabilities, intent, context, or task
              requirements.</t>
            </list></t>
        </list></t>
    </section>

    <section anchor="sec-trust-concepts" title="Trust Terms">
      <t>The following terms define trust-related concepts used in IoA
      networking infrastructures, including credentials, authentication,
      authorization, and trust establishment mechanisms that support secure
      and interoperable collaboration among agents and infrastructure
      entities.</t>

      <t><list style="symbols">
          <t>Agent Credential: A data object associated with an agent identity
          and used to represent identity attributes, authentication
          information, or authorization information.</t>

          <t>Trust Establishment: The process of establishing trust
          relationships between entities or trust domains to support
          interoperable interactions.</t>

          <t>Agent Authentication: The process of verifying the authenticity
          of an agent based on Agent Credentials.</t>

          <t>Agent Authorization: The process of granting an agent permission
          to access resources, services, or collaboration functions according
          to applicable policies.</t>
        </list></t>
    </section>

    <section title="Security Considerations">
      <t>This document only defines a set of terms. It does not introduce any
      issues that require security consideration.</t>
    </section>

    <section title="Privacy Considerations">
      <t>This document only defines a set of terms. It does not introduce any
      issues that require privacy consideration.</t>
    </section>

    <section title="Operational Considerations">
      <t>This document only defines a set of terms. It does not introduce any
      issues that require operational consideration.</t>
    </section>

    <section anchor="s-IANA" title="IANA Considerations">
      <t>This document does not make any requests of IANA.</t>
    </section>
  </middle>

  <back/>
</rfc>
