agent-network-protocol · chgaowei · Jun 3, 2026 · Jun 8, 2026 · Jun 12, 2026 · Jun 12, 2026
diff --git a/01-agentnetworkprotocol-technical-white-paper.md b/01-agentnetworkprotocol-technical-white-paper.md
@@ -154,7 +154,7 @@ sequenceDiagram
     Agent B Server->>Agent A Client: HTTP Response
 ```
 
-DID methods define how to create, resolve, update and deactivate DIDs and DID documents, as well as how to perform authentication and authorization. Among existing DID method drafts, the `did:web` method[^5] is built on mature Web technologies, allowing systems to create, update, and deactivate DIDs and DID documents using centralized technologies (such as cloud computing). Different systems achieve interoperability through the HTTP protocol, similar to email services on the internet, where each platform implements its own account system in a centralized way while enabling interconnection between platforms.
+DID methods define how to create, resolve, update and deactivate DIDs and DID documents, as well as how to perform authentication and authorization. Among existing DID methods, the `did:web` method[^5] is built on mature Web technologies, allowing systems to create, update, and deactivate DIDs and DID documents using centralized technologies (such as cloud computing). Different systems achieve interoperability through the HTTP protocol, similar to email services on the internet, where each platform implements its own account system in a centralized way while enabling interconnection between platforms.
 
 Based on the `did:web` method, we have proposed a new DID method—`did:wba` (Web-Based Agent)—specifically designed for agent communication scenarios, adding cross-platform identity authentication processes and agent description services. The `did:wba` method inherits the advantages of `did:web` while further optimizing identity authentication mechanisms between agents, enhancing its applicability in agent networks.
 

diff --git a/03-did-wba-method-design-specification.md b/03-did-wba-method-design-specification.md
@@ -1,4 +1,11 @@
-# did:wba Method Specification (V0.2)
+# did:wba Method Specification
+
+- Document ID: ANP-03
+- Title: did:wba Method Specification
+- Status: Released
+- Version: 1.1
+- Language: English
+- Applicability: This specification applies to web-based decentralized identity, cross-platform authentication, and agent communication scenarios in ANP.
 
 ## Abstract
 
@@ -24,7 +31,7 @@ The did:wba DID method specification complies with the requirements specified in
 
 Based on the did:web method specification, this specification adds specification descriptions such as DID document limitations, cross-platform identity authentication processes, and agent description services, and proposes a new method name did:wba (Web-Based Agent).
 
-Considering that the did:web method specification is still a draft, there may be changes in the future that are not suitable for agent communication scenarios. In addition, we have made some modifications to the specification, and reaching a consensus with the original author on the specification modification is also a long-term process, so we decided to use a new method name.
+Considering that the did:web method is designed for native web-based DID use cases and may evolve in ways that do not fully fit agent communication scenarios, and that this specification introduces targeted modifications, reaching consensus with the original author on those modifications would be a long-term process. Therefore, we decided to use a new method name.
 
 In the future, we do not rule out the possibility of merging the did:wba specification into the did:web specification, and we will promote the realization of this goal.
 
@@ -174,7 +181,7 @@ Due to the way most web servers render content, it is likely that a particular d
 
 ### 2.5 DID Document Description
 
-Apart from DID Core, most related specifications are still in the draft stage. This section shows a subset of DID Documents used for authentication. To improve interoperability between systems, all fields marked as required must be supported by all systems, while fields marked as optional may be supported selectively. Fields defined in other standards but not listed here may also be supported selectively.
+Apart from DID Core, related specifications may evolve over time. This section shows a subset of DID Documents used for authentication. To improve interoperability between systems, all fields marked as required must be supported by all systems, while fields marked as optional may be supported selectively. Fields defined in other standards but not listed here may also be supported selectively.
 
 **The recommended e1 path-type DID document example is as follows:**
 

diff --git a/04-anp-did-wba-name-space-specification.md b/04-anp-did-wba-name-space-specification.md
@@ -1,8 +1,13 @@
-# ANP-DID:WBA Name Space Specification (Draft)
+# ANP-DID:WBA Name Space Specification
 
-Abbreviation: WNS (WBA Name Space)
+- Document ID: ANP-04
+- Title: ANP-DID:WBA Name Space Specification
+- Status: Released
+- Version: 1.1
+- Language: English
+- Applicability: This specification applies to human-readable Handle naming, WNS resolution, and did:wba name mapping in ANP.
 
-Note: This specification is still in draft status and will undergo further optimization and iteration.
+Abbreviation: WNS (WBA Name Space)
 
 ## Abstract
 

diff --git a/06-anp-agent-communication-meta-protocol-specification.md b/06-anp-agent-communication-meta-protocol-specification.md
@@ -1,7 +1,14 @@
-# ANP-Agent Communication Meta-Protocol Specification(Draft)
+# ANP-Agent Communication Meta-Protocol Specification (Draft)
+
+- Document ID: ANP-06
+- Title: ANP-Agent Communication Meta-Protocol Specification
+- Status: Draft
+- Version: 1.1-draft
+- Language: English
+- Applicability: This specification applies to protocol negotiation, protocol selection, and communication setup between ANP agents.
 
 Note:
-- This chapter is in the draft stage and may undergo significant adjustments based on actual conditions.
+- This specification is currently in draft status and has not been released. It may undergo significant adjustments based on implementation feedback and real-world use cases.
 - The current protocol implementation focuses on end-to-end message encryption and will later be modified to a solution based on did:wba and HTTP.
 
 ## Background

diff --git a/07-anp-agent-description-protocol-specification.md b/07-anp-agent-description-protocol-specification.md
@@ -1,5 +1,12 @@
 # ANP Agent Description Protocol Specification
 
+- Document ID: ANP-07
+- Title: ANP Agent Description Protocol Specification
+- Status: Released
+- Version: 1.1
+- Language: English
+- Applicability: This specification applies to Agent Description documents, interface descriptions, and capability publication in ANP.
+
 ## Abstract
 
 This specification defines the Agent Description Protocol (ADP), a standardized protocol for describing agents. It defines how an agent publishes its public information, supported interfaces, and other details. Once other agents obtain this agent's description, they can exchange information and collaborate with this agent.

diff --git a/08-ANP-Agent-Discovery-Protocol-Specification.md b/08-ANP-Agent-Discovery-Protocol-Specification.md
@@ -1,4 +1,11 @@
-# ANP-Agent Discovery Protocol Specification (Draft)
+# ANP-Agent Discovery Protocol Specification
+
+- Document ID: ANP-08
+- Title: ANP-Agent Discovery Protocol Specification
+- Status: Released
+- Version: 1.1
+- Language: English
+- Applicability: This specification applies to active and passive discovery of agents and Agent Description documents in ANP.
 
 ## Abstract
 

diff --git a/09-ANP-end-to-end-instant-messaging-protocol-specification.md b/09-ANP-end-to-end-instant-messaging-protocol-specification.md
@@ -1,4 +1,11 @@
-# ANP End-to-End Instant Messaging Protocol Overview (Draft 1.0)
+# ANP End-to-End Instant Messaging Protocol Overview
+
+- Document ID: ANP-09
+- Title: ANP End-to-End Instant Messaging Protocol Overview
+- Status: draft
+- Version: 1.1
+- Language: English
+- Applicability: This document applies to the overview, layering, and Profile index of the ANP end-to-end instant messaging specification suite.
 
 > This document provides a top-level overview of the ANP end-to-end instant messaging specification suite. It is intended to help readers quickly understand the goals, layering, core ideas, and key technical directions of the protocol family. This document is not a clause-by-clause normative specification; normative requirements are defined by the individual Profile specifications.
 
@@ -46,13 +53,14 @@ ANP discovers interactive service endpoints through DID documents, and uses this
 
 ### 2.3 Layered design instead of “one unified protocol”
 
-ANP does not cram all the issues into one document, but splits them into 8 Profiles:
+ANP does not cram all the issues into one document, but splits them into 9 Profiles:
 
 - P1/P2: Core Binding and Identity and Discovery
 - P3/P4: Basic business semantics of direct messaging and group messaging
 - P5/P6: E2EE Overlay of direct messaging and group messaging
 - P7: Attachments and large objects
 - P8: Federation, cross-domain service invocation and group event distribution
+- P9: Group-message mentions and selector semantics
 
 The benefits of this design are:
 
@@ -236,7 +244,7 @@ To ensure that even if the link is leaked, meaningful plaintext may not be obtai
 
 ## 6. Document structure
 
-The following 8 Profiles constitute the current specification set of ANP:
+The following 9 Profiles constitute the current specification set of ANP:
 
 
 |serial number|document|effect|Content overview|
@@ -249,14 +257,15 @@ The following 8 Profiles constitute the current specification set of ANP:
 | 6 | [06-Group End-to-End Encryption](message/06-group-end-to-end-encryption.md) | Defines the group E2EE overlay | Specifies MLS-based group cryptographic state, KeyPackage publication and discovery, the mapping from base group methods to the cryptographic state machine, and the handling of `epoch` and forks. |
 | 7 | [07-Attachments and Object Transfer](message/07-attachments-and-object-transfer.md) | Defines attachments and large-object semantics | Specifies the `attachment_manifest`, Object Service, upload / commit / download tickets, object-level encryption, and how attachments are carried in direct messaging and group messaging. |
 | 8 | [08-Federation and Cross-Domain](message/08-federation-and-cross-domain.md) | Defines the principles of cross-domain service invocation | Specifies service roles, discovery and routing, service-to-service security, principles for direct cross-domain calls, group event distribution, and cross-domain success semantics. |
+| 9 | [09-Message Mentions Extension](message/09-message-mentions.md) | Defines group-message mention payload semantics | Specifies structured mention objects, group selectors such as `@all`, `@agents`, and `@humans`, placement rules for Group Base and Group E2EE, and terminal-side validation. |
 
 
 The recommended reading order is:
 
 - Read P1 / P2 first
 - Then read P3 / P4
 - Then read P5 / P6
-- Finally read P7 / P8
+- Finally read P7 / P8 / P9 as needed
 
 ---