--- type: Agentic Web Standard title: "Natural Language Interaction Protocol (NLIP)" description: "Can this agent or service exchange natural-language, multi-modal messages using a shared, vendor-neutral envelope instead of a bespoke API?" resource: "https://ecma-international.org/publications-and-standards/standards/ecma-430/" tags: ["coordinate", "document-format", "industry-body", "agent-to-agent-messaging", "describe-agent-capabilities"] status: stable generated: { by: agenticweb-builder/1.0, at: 2026-10-30T00:00:00Z } verified: { by: process:agenticweb-engine, at: 2026-10-29T00:00:00Z } stale_after: 2026-11-28T00:00:00Z sources: - id: ref-1 resource: "https://ecma-international.org/publications-and-standards/standards/ecma-430/" title: "Ecma International, ECMA-430 Natural Language Interaction Protocol (NLIP), 1st edition, standard page, checked 2026-10-29: \"ECMA-430 Natural Language Interaction Protocol (NLIP) 1st edition, December 2025\" \"This Standard defines the specifications of Natural Language Interaction Protocol (NLIP), which is an application-level communication protocol defined between AI Agents or between a human and an AI agent.\" \"ISO/IEC number DIS 26637\"" last_modified: 2025-12-10T00:00:00Z - id: ref-2 resource: "https://ecma-international.org/wp-content/uploads/ECMA-430_1st_edition_december_2025.pdf" title: "Ecma International, ECMA-430 1st edition, December 2025 (PDF), checked 2026-10-29: \"This Ecma Standard was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025.\" \"Each message exchanged via NLIP is primarily represented as a JSON message. Each message consists of a first submessage and an optional list of other submessages.\" \"The format field is required. It is used to specify the format in which the contents field is represented.\" \"The subformat field is required. It is used to specify the subcategory of representation within the format.\" \"The content field is required. It includes the actual content being sent between the client and the server.\" \"The value of 'control' is reserved and indicates a message that is used to negotiate control parameters.\"" last_modified: 2025-12-10T00:00:00Z - id: ref-3 resource: "https://ecma-international.org/publications-and-standards/standards/ecma-431/" title: "Ecma International, ECMA-431 standard page, checked 2026-10-29: \"Binding of the Natural Language Interaction Protocol (NLIP) over HTTP/HTTPS\" \"ISO/IEC number DIS 26638\"" last_modified: 2025-12-10T00:00:00Z - id: ref-4 resource: "https://ecma-international.org/wp-content/uploads/ECMA-431_1st_edition_december_2025.pdf" title: "Ecma International, ECMA-431 1st edition, December 2025 (PDF), checked 2026-10-29: \"port/nlip. The end-point shall support accepting an NLIP message using the POST command of HTTP.\" \"The end-point should use either HTTP/1.1 or HTTP/2 as the base transfer protocol, Implementations may use HTTP/3 in validated use cases.\"" last_modified: 2025-12-10T00:00:00Z - id: ref-5 resource: "https://ecma-international.org/publications-and-standards/standards/ecma-432/" title: "Ecma International, ECMA-432 standard page, checked 2026-10-29: \"This specification defines how the Natural Language Interaction Protocol (NLIP) shall be implemented over the WebSocket protocol using CBOR (Concise Binary Object Representation, RFC 8949) for compact and efficient multimodal communication.\" \"It also describes a fallback to UTF-8 encoded JSON text frames for compatibility.\" \"ISO/IEC number DIS 26639\"" last_modified: 2025-12-10T00:00:00Z - id: ref-6 resource: "https://ecma-international.org/publications-and-standards/standards/ecma-433/" title: "Ecma International, ECMA-433 standard page, checked 2026-10-29: \"This Standard defines how the Natural Language Interaction Protocol (NLIP) should be implemented over the base transfer protocol of AMQP.\" \"ISO/IEC number DIS 26640\"" last_modified: 2025-12-10T00:00:00Z - id: ref-7 resource: "https://ecma-international.org/publications-and-standards/standards/ecma-434/" title: "Ecma International, ECMA-434 standard page, checked 2026-10-29: \"This Standard establishes the Agent Security Profiles for NLIP as a standalone Ecma Standard.\" \"Conformance to this Standard is mandatory for any implementation claiming NLIP conformance.\" \"ISO/IEC number DIS 26641\"" last_modified: 2025-12-10T00:00:00Z - id: ref-8 resource: "https://ecma-international.org/wp-content/uploads/ECMA-434_1st_edition_december_2025.pdf" title: "Ecma International, ECMA-434 1st edition, December 2025 (PDF), checked 2026-10-29: \"While Profile 1 is mandatory to be NLIP- compliant, specific applications can further choose to implement either Profile 2 or Profile 3, or a subset of SCOs in them, based on specific security assurance needs and threats in their development and deployment environments.\" \"This agent security profile is recommended for service providers.\"" last_modified: 2025-12-10T00:00:00Z - id: ref-9 resource: "https://ecma-international.org/publications-and-standards/technical-reports/ecma-tr-113/" title: "Ecma International, ECMA TR/113 technical report page, checked 2026-10-29: \"ECMA TR/113 Explanatory guide to the Natural Language Interaction Protocol (NLIP) 1st edition, December 2025\" \"This is an informative document and does not define a standard.\"" last_modified: 2025-12-10T00:00:00Z - id: ref-10 resource: "https://ecma-international.org/wp-content/uploads/ECMA_TR-113_1st_edition_december_2025.pdf" title: "Ecma International, ECMA TR/113 1st edition, December 2025 (PDF), checked 2026-10-29: \"This Ecma Technical Report was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025.\"" last_modified: 2025-12-10T00:00:00Z - id: ref-11 resource: "https://ecma-international.org/news/ecma-international-approves-new-standards-12/" title: "Ecma International, Ecma International approves new standards, 2025-12-11, checked 2026-10-29: \"The 130th General Assembly held in Geneva on 10 December 2025 approved the following documents:\" \"ECMA-430 1st edition – Natural Language Interaction Protocol (NLIP)\" \"ECMA TR/113 1st edition – Explanatory guide to the Natural Language Interaction Protocol (NLIP)\"" last_modified: 2025-12-11T00:00:00Z - id: ref-12 resource: "https://ecma-international.org/news/ecma-international-approves-nlip-standards-suite-for-universal-ai-agent-communication/" title: "Ecma International, Ecma International approves NLIP standards suite for universal AI agent communication, 2025-12-17, checked 2026-10-29: \"Ecma International published on 10 December 2025 five new standards and one technical report defining the Natural Language Interaction Protocol (NLIP).\" \"ECMA-431: Binding of NLIP over HTTP/HTTPS makes NLIP accessible to existing web infrastructure by defining standardized endpoints with support for HTTP/1.1, HTTP/2, and HTTP/3.\" \"Open-source reference implementations can be found on GitHub\"" last_modified: 2025-12-17T00:00:00Z - id: ref-13 resource: "https://ecma-international.org/news/call-for-participation-on-natural-language-interaction-protocol-for-communication-with-ai-agents-standardization/" title: "Ecma International, call for participation on NLIP, 2025-05-15, checked 2026-10-29: \"The development of this protocol began in March 2024 through a collaborative initiative within the Enterprise Neurosystems Group (ENG), an open-source consortium. This effort led to the formation of TC56 within Ecma International in December 2024.\" \"On 1 May 2025, TC56 approved the first draft specification of the NLIP protocol\"" last_modified: 2025-05-15T00:00:00Z - id: ref-14 resource: "https://ecma-international.org/news/call-for-participation-and-comments-on-revised-nlip-specification-and-new-websocket-binding/" title: "Ecma International, call for participation on the revised NLIP specification and WebSocket binding, 2025-07-17, checked 2026-10-29: \"The publication of a second draft of the NLIP core specification The release of the first draft binding of NLIP over WebSocket\"" last_modified: 2025-07-17T00:00:00Z - id: ref-15 resource: "https://ecma-international.org/technical-committees/tc56/" title: "Ecma International, TC56 committee page, checked 2026-10-29: \"The TC specifies a common protocol, framework and interfaces for interactions between AI agents using natural language while supporting multiple modalities.\" \"TC56 operates under the Royalty-Free Patent Policy\" \"Chair: Dinesh Verma (IBM) Vice-Chair: Elisa Bertino (Purdue University) Secretaries: Patrick Luthi (Ecma International) and Luyi Xing (University of Illinois)\"" last_modified: 2026-10-29T00:00:00Z - id: ref-16 resource: "https://arxiv.org/abs/2609.04135" title: "arXiv:2609.04135 abstract page, checked 2026-10-29: \"[Submitted on 3 Sep 2026]\" \"Comments: Accepted by ACM AI Summit 2026\"" last_modified: 2026-09-03T00:00:00Z - id: ref-17 resource: "https://arxiv.org/pdf/2609.04135" title: "L. Xing, R. O. Topaloglu, R. Sinha, A. Ratnaparkhi and others, The Natural Language Interaction Protocol and Standard for AI Agents, arXiv:2609.04135 (PDF), checked 2026-10-29: \"NLIP started in June 2024 as a technical working group within the Enterprise NeuroSystem Group (ENG).\" \"In October 2024, the initial version of the protocol was defined, and a decision to convert the specification to a formal standard was made.\" \"The members who officially joined Ecma TC56 to define the official standards included IBM,\" \"University at Buffalo, Fordham University, Chicago State University, Marist University, and City University of New York.\" \"NLIP was used by the two intelligent agents to communicate with each other.\" \"These results suggest that NLIP may be well suited for frequent, lightweight, latency- sensitive interactions, while A2A-style task abstractions are better suited for long-running or governance-intensive workflows and can be carried over, integrated with, or bridged through NLIP.\" \"A commercial use case was demonstrated by IBM at the 2025 Telecommunications Management Forum (TMF)\"" last_modified: 2026-09-03T00:00:00Z - id: ref-18 resource: "https://www.enterpriseneurosystem.org/nlip" title: "Enterprise Neurosystem, NLIP project page (undated), checked 2026-10-29: \"Dr. Dinesh Verma (IBM Research and Enterprise Neurosystem CTO) proposed a universal chatbot for all consumer mobile applications.\" \"he initiated an Enterprise Neurosystem community project: NLIP.\" \"Backers now include Cisco, Hewlett Packard, Hitachi, IBM, Microsoft and Red Hat, alongside multiple academic institutions.\"" last_modified: 2026-10-29T00:00:00Z - id: ref-19 resource: "https://api.github.com/orgs/nlip-project" title: "GitHub API, nlip-project organization record (UTC), checked 2026-10-29: \"\"created_at\": \"2024-09-20T14:09:13Z\"\" \"\"blog\": \"https://nlip-project.org\"\"" last_modified: 2024-09-20T00:00:00Z - id: ref-20 resource: "https://api.github.com/orgs/nlip-project/repos?per_page=100" title: "GitHub API, nlip-project repositories (UTC), checked 2026-10-29: \"\"full_name\": \"nlip-project/nlip_server\"\" \"\"full_name\": \"nlip-project/nlip_sdk\"\" \"\"full_name\": \"nlip-project/nlip_soln\"\"" last_modified: 2026-10-29T00:00:00Z - id: ref-21 resource: "https://raw.githubusercontent.com/nlip-project/.github/main/profile/README.md" title: "nlip-project organization profile README, checked 2026-10-29: \"is the official organization working space for [Ecma TC56 NLIP]\"" last_modified: 2026-10-29T00:00:00Z - id: ref-22 resource: "https://raw.githubusercontent.com/nlip-project/nlip_spec/main/README.md" title: "nlip-project/nlip_spec, README.md, checked 2026-10-29: \"The following documents are the official standards and technical report approved by Ecma International on 10 December 2025, developed by Ecma TC56 NLIP.\"" last_modified: 2026-10-29T00:00:00Z - id: ref-23 resource: "https://raw.githubusercontent.com/nlip-project/nlip_server/main/README.md" title: "nlip-project/nlip_server, README.md, checked 2026-10-29: \"This repository contains one component of the various python repositories for NLIP Proof of Concept implementation.\"" last_modified: 2026-10-29T00:00:00Z - id: ref-24 resource: "https://raw.githubusercontent.com/nlip-project/ecma_draft/main/README.md" title: "nlip-project/ecma_draft, README.md, checked 2026-10-29: \"This repo contains early DRAFT documents for NLIP and are considered out of date.\"" last_modified: 2026-10-29T00:00:00Z - id: ref-25 resource: "https://pypi.org/pypi/nlip-sdk/json" title: "PyPI JSON API, nlip_sdk (upload times UTC), checked 2026-10-29: \"\"name\":\"nlip_sdk\"\" \"\"version\":\"0.1.3\"\" \"\"upload_time\":\"2026-06-24T12:58:51\"\" \"\"upload_time\":\"2024-11-13T12:20:47\"\"" last_modified: 2026-06-24T00:00:00Z - id: ref-26 resource: "https://pypi.org/pypi/nlip-server/json" title: "PyPI JSON API, nlip-server (upload times UTC), checked 2026-10-29: \"\"name\":\"nlip-server\"\" \"\"upload_time\":\"2026-06-24T12:57:31\"\"" last_modified: 2026-06-24T00:00:00Z - id: ref-27 resource: "https://pypi.org/pypi/nlip/json" title: "PyPI JSON API, nlip (yanked), checked 2026-10-29: \"\"yanked_reason\":\"Published other packages as nlip-sdk and nlip-server\"\"" last_modified: 2026-10-29T00:00:00Z - id: ref-28 resource: "https://api.github.com/repos/ag2ai/ag2/pulls/2468" title: "GitHub API, ag2ai/ag2 pull request 2468 (UTC), checked 2026-10-29: \"\"title\": \"feat: add NLIP integration\"\" \"\"merged_at\": \"2026-04-08T16:00:26Z\"\"" last_modified: 2026-04-08T00:00:00Z - id: ref-29 resource: "https://api.github.com/repos/ag2ai/ag2/pulls/3024" title: "GitHub API, ag2ai/ag2 pull request 3024 (UTC), checked 2026-10-29: \"\"title\": \"feat: add NLIP integration for beta\"\" \"\"merged_at\": \"2026-06-30T19:19:45Z\"\"" last_modified: 2026-06-30T00:00:00Z - id: ref-30 resource: "https://the-ai-alliance.github.io/enterprise-MCP/getting-to-know-mcp/nlip/" title: "Tom Sheffler, NLIP, Agents, and Protocols, AI Alliance, Getting to Know MCP, 2025-10-21, checked 2026-10-29: \"NLIP focuses only on the transfer of conversations and provides guidelines for its secure use with agents.\" \"Editor's Note: Tom is a member of the NLIP project. NLIP complements MCP, as well as other protocols, in many ways\"" last_modified: 2025-10-21T00:00:00Z - id: ref-31 resource: "https://siebelschool.illinois.edu/news/luyi-xing-nsf-grant-ecma" title: "Rudy San Miguel, Siebel School of Computing and Data Science, University of Illinois, Xing receives NSF grant and sets AI Agent Ecosystems ISO standard, 2026-09-25, checked 2026-10-29: \"Xing and his team are building on the Natural Language Interaction Protocol (NLIP) for communication with and between AI agents, for which Xing has held a leadership role with Ecma International and which will soon become an official ISO standard.\" \"In June 2026, University of Illinois Urbana-Champaign was approved as a not-for-profit member\"" last_modified: 2026-09-25T00:00:00Z - id: ref-32 resource: "https://www.hpcwire.com/aiwire/2026/10/01/illinois-researcher-receives-nsf-grant-and-sets-ai-agent-ecosystems-iso-standard/" title: "AIwire (HPCwire), republication of the Illinois story, 2026-10-01, checked 2026-10-29: \"received a $1.5 million National Science Foundation (NSF) Safe-OSE grant to advance security for AI Agent Ecosystems.\"" last_modified: 2026-10-01T00:00:00Z --- # Natural Language Interaction Protocol (NLIP) Natural Language Interaction Protocol (NLIP) is an agentic-web standard (document format) at step 6, Coordinate, governed by Ecma International Technical Committee 56. TC56 operates under the Royalty-Free Patent Policy; its status is "Approved and published by Ecma in December 2025. The 130th General Assembly held in Geneva on 10 December 2025 approved the following documents: ECMA-430 1st edition – Natural Language Interaction Protocol … ECMA TR/113 1st edition – Explanatory guide to the Natural Language Interaction Protocol". It answers: "Can this agent or service exchange natural-language, multi-modal messages using a shared, vendor-neutral envelope instead of a bespoke API?" Implementation status is multi-implementation (nlip-project Python reference implementation), last verified 2026-10-29. # Overview NLIP defines one envelope for messages between AI agents, and between people and AI agents, so that any compliant client or agent can exchange text, structured data and binary content such as images or audio with any other [^ref-1][^ref-2]. It began as a community project of the Enterprise Neurosystem group, led by IBM's Dinesh Verma, and moved into a dedicated Ecma technical committee, which he chairs [^ref-13][^ref-18][^ref-15]. Ecma's General Assembly approved the core standard, three transport bindings, a security standard and an explanatory report together, and they are free to download [^ref-11][^ref-12]. The same texts carry ISO/IEC draft numbers, and ISO publication is still pending [^ref-1][^ref-31]. Reference software comes from the project itself, and one outside agent framework, formerly called AutoGen, has merged support [^ref-20][^ref-28][^ref-17]. ### How it works * **Message.** "Each message exchanged via NLIP is primarily represented as a JSON message. Each message consists of a first submessage and an optional list of other submessages." In the first submessage: "The format field is required. It is used to specify the format in which the contents field is represented." "The subformat field is required. It is used to specify the subcategory of representation within the format." "The content field is required. It includes the actual content being sent between the client and the server." [^ref-2]. * **Control messages.** "The value of 'control' is reserved and indicates a message that is used to negotiate control parameters." [^ref-2]. * **HTTP/HTTPS (ECMA-431).** "The end-point should use either HTTP/1.1 or HTTP/2 as the base transfer protocol, Implementations may use HTTP/3 in validated use cases." [^ref-4]. Ecma's announcement summarises this as "ECMA-431: Binding of NLIP over HTTP/HTTPS makes NLIP accessible to existing web infrastructure by defining standardized endpoints with support for HTTP/1.1, HTTP/2, and HTTP/3." [^ref-12]. * **WebSocket (ECMA-432).** "This specification defines how the Natural Language Interaction Protocol (NLIP) shall be implemented over the WebSocket protocol using CBOR (Concise Binary Object Representation, RFC 8949) for compact and efficient multimodal communication." "It also describes a fallback to UTF-8 encoded JSON text frames for compatibility." [^ref-5]. * **AMQP (ECMA-433).** "This Standard defines how the Natural Language Interaction Protocol (NLIP) should be implemented over the base transfer protocol of AMQP." [^ref-6]. * **Security (ECMA-434).** "This Standard establishes the Agent Security Profiles for NLIP as a standalone Ecma Standard." "Conformance to this Standard is mandatory for any implementation claiming NLIP conformance." [^ref-7]. "While Profile 1 is mandatory to be NLIP- compliant, specific applications can further choose to implement either Profile 2 or Profile 3, or a subset of SCOs in them, based on specific security assurance needs and threats in their development and deployment environments." Profile 3: "This agent security profile is recommended for service providers." [^ref-8]. * **Explanatory guide (TR/113).** "This is an informative document and does not define a standard." [^ref-9]. "This Ecma Technical Report was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025." [^ref-10]. * **Path to the standard.** "On 1 May 2025, TC56 approved the first draft specification of the NLIP protocol" [^ref-13]. In July 2025 Ecma announced "The publication of a second draft of the NLIP core specification The release of the first draft binding of NLIP over WebSocket" [^ref-14]. # Examples ```http POST https://{endpoint}/nlip/ # parse: A 200 response whose JSON body is (or contains) an NLIP message: an object with a first sub-message carrying format/subformat/content fields (e.g. {"format":"text","subformat":"english","content":"..."}), per the ECMA-430 envelope and the ECMA-431 HTTP/HTTPS binding # on absent: A non-2xx response, a connection refusal, or a body that does not parse as an NLIP envelope means the origin does not run an NLIP endpoint at that address; NLIP has no well-known discovery path, so absence at a guessed path is not conclusive proof the origin lacks NLIP support ``` # Knowledge Graph * **Lifecycle Step**: [6 Coordinate](/category/coordinate/index.md) * **Pairs with**: [Agent2Agent Protocol (A2A)](/okf/protocols/a2a.md), [Model Context Protocol](/okf/protocols/mcp.md), [Agent Network Protocol](/okf/protocols/anp.md), [Agent Communication Protocol](/okf/protocols/agent-communication-protocol.md), [Agent Connect Protocol](/okf/protocols/agent-connect-protocol.md), [Secure Low-Latency Interactive Messaging (SLIM)](/okf/protocols/slim.md) * **Compared in**: [Agent2Agent Protocol (A2A) vs Natural Language Interaction Protocol (NLIP)](/compare/a2a-vs-nlip/index.md) [^ref-1]: Ecma International, ECMA-430 Natural Language Interaction Protocol (NLIP), 1st edition, standard page, checked 2026-10-29: "ECMA-430 Natural Language Interaction Protocol (NLIP) 1st edition, December 2025" "This Standard defines the specifications of Natural Language Interaction Protocol (NLIP), which is an application-level communication protocol defined between AI Agents or between a human and an AI agent." "ISO/IEC number DIS 26637" (https://ecma-international.org/publications-and-standards/standards/ecma-430/) [^ref-2]: Ecma International, ECMA-430 1st edition, December 2025 (PDF), checked 2026-10-29: "This Ecma Standard was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025." "Each message exchanged via NLIP is primarily represented as a JSON message. Each message consists of a first submessage and an optional list of other submessages." "The format field is required. It is used to specify the format in which the contents field is represented." "The subformat field is required. It is used to specify the subcategory of representation within the format." "The content field is required. It includes the actual content being sent between the client and the server." "The value of 'control' is reserved and indicates a message that is used to negotiate control parameters." (https://ecma-international.org/wp-content/uploads/ECMA-430_1st_edition_december_2025.pdf) [^ref-3]: Ecma International, ECMA-431 standard page, checked 2026-10-29: "Binding of the Natural Language Interaction Protocol (NLIP) over HTTP/HTTPS" "ISO/IEC number DIS 26638" (https://ecma-international.org/publications-and-standards/standards/ecma-431/) [^ref-4]: Ecma International, ECMA-431 1st edition, December 2025 (PDF), checked 2026-10-29: "port/nlip. The end-point shall support accepting an NLIP message using the POST command of HTTP." "The end-point should use either HTTP/1.1 or HTTP/2 as the base transfer protocol, Implementations may use HTTP/3 in validated use cases." (https://ecma-international.org/wp-content/uploads/ECMA-431_1st_edition_december_2025.pdf) [^ref-5]: Ecma International, ECMA-432 standard page, checked 2026-10-29: "This specification defines how the Natural Language Interaction Protocol (NLIP) shall be implemented over the WebSocket protocol using CBOR (Concise Binary Object Representation, RFC 8949) for compact and efficient multimodal communication." "It also describes a fallback to UTF-8 encoded JSON text frames for compatibility." "ISO/IEC number DIS 26639" (https://ecma-international.org/publications-and-standards/standards/ecma-432/) [^ref-6]: Ecma International, ECMA-433 standard page, checked 2026-10-29: "This Standard defines how the Natural Language Interaction Protocol (NLIP) should be implemented over the base transfer protocol of AMQP." "ISO/IEC number DIS 26640" (https://ecma-international.org/publications-and-standards/standards/ecma-433/) [^ref-7]: Ecma International, ECMA-434 standard page, checked 2026-10-29: "This Standard establishes the Agent Security Profiles for NLIP as a standalone Ecma Standard." "Conformance to this Standard is mandatory for any implementation claiming NLIP conformance." "ISO/IEC number DIS 26641" (https://ecma-international.org/publications-and-standards/standards/ecma-434/) [^ref-8]: Ecma International, ECMA-434 1st edition, December 2025 (PDF), checked 2026-10-29: "While Profile 1 is mandatory to be NLIP- compliant, specific applications can further choose to implement either Profile 2 or Profile 3, or a subset of SCOs in them, based on specific security assurance needs and threats in their development and deployment environments." "This agent security profile is recommended for service providers." (https://ecma-international.org/wp-content/uploads/ECMA-434_1st_edition_december_2025.pdf) [^ref-9]: Ecma International, ECMA TR/113 technical report page, checked 2026-10-29: "ECMA TR/113 Explanatory guide to the Natural Language Interaction Protocol (NLIP) 1st edition, December 2025" "This is an informative document and does not define a standard." (https://ecma-international.org/publications-and-standards/technical-reports/ecma-tr-113/) [^ref-10]: Ecma International, ECMA TR/113 1st edition, December 2025 (PDF), checked 2026-10-29: "This Ecma Technical Report was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025." (https://ecma-international.org/wp-content/uploads/ECMA_TR-113_1st_edition_december_2025.pdf) [^ref-11]: Ecma International, Ecma International approves new standards, 2025-12-11, checked 2026-10-29: "The 130th General Assembly held in Geneva on 10 December 2025 approved the following documents:" "ECMA-430 1st edition – Natural Language Interaction Protocol (NLIP)" "ECMA TR/113 1st edition – Explanatory guide to the Natural Language Interaction Protocol (NLIP)" (https://ecma-international.org/news/ecma-international-approves-new-standards-12/) [^ref-12]: Ecma International, Ecma International approves NLIP standards suite for universal AI agent communication, 2025-12-17, checked 2026-10-29: "Ecma International published on 10 December 2025 five new standards and one technical report defining the Natural Language Interaction Protocol (NLIP)." "ECMA-431: Binding of NLIP over HTTP/HTTPS makes NLIP accessible to existing web infrastructure by defining standardized endpoints with support for HTTP/1.1, HTTP/2, and HTTP/3." "Open-source reference implementations can be found on GitHub" (https://ecma-international.org/news/ecma-international-approves-nlip-standards-suite-for-universal-ai-agent-communication/) [^ref-13]: Ecma International, call for participation on NLIP, 2025-05-15, checked 2026-10-29: "The development of this protocol began in March 2024 through a collaborative initiative within the Enterprise Neurosystems Group (ENG), an open-source consortium. This effort led to the formation of TC56 within Ecma International in December 2024." "On 1 May 2025, TC56 approved the first draft specification of the NLIP protocol" (https://ecma-international.org/news/call-for-participation-on-natural-language-interaction-protocol-for-communication-with-ai-agents-standardization/) [^ref-14]: Ecma International, call for participation on the revised NLIP specification and WebSocket binding, 2025-07-17, checked 2026-10-29: "The publication of a second draft of the NLIP core specification The release of the first draft binding of NLIP over WebSocket" (https://ecma-international.org/news/call-for-participation-and-comments-on-revised-nlip-specification-and-new-websocket-binding/) [^ref-15]: Ecma International, TC56 committee page, checked 2026-10-29: "The TC specifies a common protocol, framework and interfaces for interactions between AI agents using natural language while supporting multiple modalities." "TC56 operates under the Royalty-Free Patent Policy" "Chair: Dinesh Verma (IBM) Vice-Chair: Elisa Bertino (Purdue University) Secretaries: Patrick Luthi (Ecma International) and Luyi Xing (University of Illinois)" (https://ecma-international.org/technical-committees/tc56/) [^ref-16]: arXiv:2609.04135 abstract page, checked 2026-10-29: "[Submitted on 3 Sep 2026]" "Comments: Accepted by ACM AI Summit 2026" (https://arxiv.org/abs/2609.04135) [^ref-17]: L. Xing, R. O. Topaloglu, R. Sinha, A. Ratnaparkhi and others, The Natural Language Interaction Protocol and Standard for AI Agents, arXiv:2609.04135 (PDF), checked 2026-10-29: "NLIP started in June 2024 as a technical working group within the Enterprise NeuroSystem Group (ENG)." "In October 2024, the initial version of the protocol was defined, and a decision to convert the specification to a formal standard was made." "The members who officially joined Ecma TC56 to define the official standards included IBM," "University at Buffalo, Fordham University, Chicago State University, Marist University, and City University of New York." "NLIP was used by the two intelligent agents to communicate with each other." "These results suggest that NLIP may be well suited for frequent, lightweight, latency- sensitive interactions, while A2A-style task abstractions are better suited for long-running or governance-intensive workflows and can be carried over, integrated with, or bridged through NLIP." "A commercial use case was demonstrated by IBM at the 2025 Telecommunications Management Forum (TMF)" (https://arxiv.org/pdf/2609.04135) [^ref-18]: Enterprise Neurosystem, NLIP project page (undated), checked 2026-10-29: "Dr. Dinesh Verma (IBM Research and Enterprise Neurosystem CTO) proposed a universal chatbot for all consumer mobile applications." "he initiated an Enterprise Neurosystem community project: NLIP." "Backers now include Cisco, Hewlett Packard, Hitachi, IBM, Microsoft and Red Hat, alongside multiple academic institutions." (https://www.enterpriseneurosystem.org/nlip) [^ref-19]: GitHub API, nlip-project organization record (UTC), checked 2026-10-29: ""created_at": "2024-09-20T14:09:13Z"" ""blog": "https://nlip-project.org"" (https://api.github.com/orgs/nlip-project) [^ref-20]: GitHub API, nlip-project repositories (UTC), checked 2026-10-29: ""full_name": "nlip-project/nlip_server"" ""full_name": "nlip-project/nlip_sdk"" ""full_name": "nlip-project/nlip_soln"" (https://api.github.com/orgs/nlip-project/repos?per_page=100) [^ref-21]: nlip-project organization profile README, checked 2026-10-29: "is the official organization working space for [Ecma TC56 NLIP]" (https://raw.githubusercontent.com/nlip-project/.github/main/profile/README.md) [^ref-22]: nlip-project/nlip_spec, README.md, checked 2026-10-29: "The following documents are the official standards and technical report approved by Ecma International on 10 December 2025, developed by Ecma TC56 NLIP." (https://raw.githubusercontent.com/nlip-project/nlip_spec/main/README.md) [^ref-23]: nlip-project/nlip_server, README.md, checked 2026-10-29: "This repository contains one component of the various python repositories for NLIP Proof of Concept implementation." (https://raw.githubusercontent.com/nlip-project/nlip_server/main/README.md) [^ref-24]: nlip-project/ecma_draft, README.md, checked 2026-10-29: "This repo contains early DRAFT documents for NLIP and are considered out of date." (https://raw.githubusercontent.com/nlip-project/ecma_draft/main/README.md) [^ref-25]: PyPI JSON API, nlip_sdk (upload times UTC), checked 2026-10-29: ""name":"nlip_sdk"" ""version":"0.1.3"" ""upload_time":"2026-06-24T12:58:51"" ""upload_time":"2024-11-13T12:20:47"" (https://pypi.org/pypi/nlip-sdk/json) [^ref-26]: PyPI JSON API, nlip-server (upload times UTC), checked 2026-10-29: ""name":"nlip-server"" ""upload_time":"2026-06-24T12:57:31"" (https://pypi.org/pypi/nlip-server/json) [^ref-27]: PyPI JSON API, nlip (yanked), checked 2026-10-29: ""yanked_reason":"Published other packages as nlip-sdk and nlip-server"" (https://pypi.org/pypi/nlip/json) [^ref-28]: GitHub API, ag2ai/ag2 pull request 2468 (UTC), checked 2026-10-29: ""title": "feat: add NLIP integration"" ""merged_at": "2026-04-08T16:00:26Z"" (https://api.github.com/repos/ag2ai/ag2/pulls/2468) [^ref-29]: GitHub API, ag2ai/ag2 pull request 3024 (UTC), checked 2026-10-29: ""title": "feat: add NLIP integration for beta"" ""merged_at": "2026-06-30T19:19:45Z"" (https://api.github.com/repos/ag2ai/ag2/pulls/3024) [^ref-30]: Tom Sheffler, NLIP, Agents, and Protocols, AI Alliance, Getting to Know MCP, 2025-10-21, checked 2026-10-29: "NLIP focuses only on the transfer of conversations and provides guidelines for its secure use with agents." "Editor's Note: Tom is a member of the NLIP project. NLIP complements MCP, as well as other protocols, in many ways" (https://the-ai-alliance.github.io/enterprise-MCP/getting-to-know-mcp/nlip/) [^ref-31]: Rudy San Miguel, Siebel School of Computing and Data Science, University of Illinois, Xing receives NSF grant and sets AI Agent Ecosystems ISO standard, 2026-09-25, checked 2026-10-29: "Xing and his team are building on the Natural Language Interaction Protocol (NLIP) for communication with and between AI agents, for which Xing has held a leadership role with Ecma International and which will soon become an official ISO standard." "In June 2026, University of Illinois Urbana-Champaign was approved as a not-for-profit member" (https://siebelschool.illinois.edu/news/luyi-xing-nsf-grant-ecma) [^ref-32]: AIwire (HPCwire), republication of the Illinois story, 2026-10-01, checked 2026-10-29: "received a $1.5 million National Science Foundation (NSF) Safe-OSE grant to advance security for AI Agent Ecosystems." (https://www.hpcwire.com/aiwire/2026/10/01/illinois-researcher-receives-nsf-grant-and-sets-ai-agent-ecosystems-iso-standard/)