chore: rename file

Signed-off-by: Luca Muscariello <lumuscar@cisco.com>

Author: muscariello

.github/CODEOWNERS

@@ -1 +1 @@
-**/ @agntcy/agp-maintainers
+**/ @agntcy/slim-maintainers

README.md

@@ -3,7 +3,7 @@
 This repo contains sources of the technical specification of the agent
 gateway protocol.
 The sources in markdown format are compiled in HTML and txt and published
-in https://spec.agp.agntcy.org.
+in https://spec.slim.agntcy.org.
 
 This is work in progress and the reference implementation is available
-in the repository https://github.com/agntcy/agp
+in the repository https://github.com/agntcy/slim

draft-agntcy-slim.md

@@ -2,11 +2,11 @@
 ###
 # Description of Agent Gateway Protocol
 ###
-title: "Agent Gateway Protocol"
-abbrev: "agent-gw"
+title: "Secure Interactive Low-Latency Interactive Messaging (SLIM)"
+abbrev: "agent-slim"
 category: info
 
-docname: draft-agntcy-agp-latest
+docname: draft-agntcy-slim-latest
 submissiontype: independent
 number:
 date:
@@ -23,8 +23,8 @@ venue:
   group: WG
   type: Working Group
   mail: discussion@agntcy.org
-  github: agntcy/agp
-  latest: https://spec.agp.agntcy.org
+  github: agntcy/slim
+  latest: https://spec.slim.agntcy.org
 
 author:
 
@@ -45,10 +45,11 @@ informative:
 
 --- abstract
 
-This document specifies the Agent Gateway Protocol (AGP), a protocol designed to
-support real-time interactive AI applications at scale. AGP extends gRPC with
-publish-subscribe capabilities to enable efficient many-to-many communication
-patterns between AI agents. The protocol provides mechanisms for connection
+This document specifies the Secure Low-Latency Interactive RealTime Messaging
+(SLIM), a protocol designed to support real-time interactive AI applications at
+scale. SLIM leverates gRPC and add publish-subscribe capabilities to enable
+efficient many-to-many communication patterns between AI agentic applications
+(AI models, tools and data). The protocol provides mechanisms for connection
 management, stream multiplexing, and flow control while maintaining
 compatibility with existing gRPC deployments.
 
@@ -62,8 +63,8 @@ compatibility with existing gRPC deployments.
 
 
 As AI systems become more sophisticated and interconnected, there is a growing need
-for protocols that can support real-time interactive applications at scale. The Agent
-Gateway Protocol (AGP) addresses this need by:
+for protocols that can support real-time interactive applications at scale. SLIM 
+addresses this need by:
 
 * Extending gRPC with publish-subscribe patterns
 * Supporting bidirectional streaming between agents
@@ -72,7 +73,7 @@ Gateway Protocol (AGP) addresses this need by:
 
 ## Protocol Overview
 
-AGP builds on gRPC's core features while adding:
+SLIM builds on gRPC's core features while adding:
 
 * Native support for pub/sub messaging patterns
 * Enhanced stream multiplexing capabilities
@@ -86,7 +87,7 @@ AGP builds on gRPC's core features while adding:
          +-------------------+
          |     Application   |
          +-------------------+
-         |   AGP Services    |
+         |   SLIM Services    |
          +-------------------+
          |     Pub/Sub       |
          +-------------------+
@@ -97,18 +98,22 @@ AGP builds on gRPC's core features while adding:
 
 ## Core Components
 
-* Gateway Nodes: Handle routing and message distribution
+* Messaging Nodes: Handle routing and message distribution
 * Topics: Named channels for pub/sub communication
 * Streams: Bidirectional communication channels
 * Services: Application-specific RPC definitions
 
-### Gateway Nodes
+### Meassging Nodes
 
-Gateway Nodes are essential components of the Agent Gateway Protocol (AGP) architecture. They handle routing and message distribution between agents and manage the communication infrastructure. Gateway Nodes are composed of two main tables: the connection table and the subscription table.
+Nodes are essential components of the SLIM architecture.
+They handle routing and message distribution between agents and manage the
+communication infrastructure. Meassaging Nodes are composed of two main tables: the
+connection table and the subscription table.
 
 #### Connection Table
 
-The connection table maintains interfaces with neighboring nodes and local applications. It is responsible for:
+The connection table maintains interfaces with neighboring nodes and local
+applications. It is responsible for:
 
 * Establishing and managing connections with other Gateway Nodes
 * Maintaining active connections with local applications
@@ -117,16 +122,21 @@ The connection table maintains interfaces with neighboring nodes and local appli
 The connection table entries include:
 
 * Node ID: Unique identifier for the neighboring node or local application
-* Connection Status: Current status of the connection (e.g., active, inactive, error)
-* Connection Parameters: Details such as IP address, port, and security credentials
+* Connection Status: Current status of the connection (e.g., active, inactive,
+error)
+* Connection Parameters: Details such as IP address, port, and security
+credentials
 
 #### Subscription Table
 
-The subscription table is used to map topic subscriptions to neighboring nodes. It manages the distribution of messages based on topic subscriptions and ensures efficient routing of pub/sub messages. The subscription table entries include:
+The subscription table is used to map topic subscriptions to neighboring nodes.
+It manages the distribution of messages based on topic subscriptions and ensures
+efficient routing of pub/sub messages. The subscription table entries include:
 
 * Topic: The name of the topic to which the subscription applies
 * Subscriber Node IDs: List of node IDs that have subscribed to the topic
-* Subscription Status: Current status of the subscription (e.g., active, inactive)
+* Subscription Status: Current status of the subscription (e.g., active,
+inactive)
 
 The subscription table is responsible for:
 
@@ -135,17 +145,19 @@ The subscription table is responsible for:
 * Handling subscription updates, additions, and removals
 * Ensuring efficient and reliable message delivery
 
-By maintaining these tables, Gateway Nodes facilitate seamless communication and message distribution in the AGP network, enabling real-time interactive AI applications at scale.
+By maintaining these tables, Meassaging Nodes facilitate seamless communication and
+message distribution in a SLIM network, enabling real-time interactive AI
+applications at scale.
 
 # Security Considerations
 
 
-The Agent Gateway Protocol (AGP) relies on the Messaging Layer Security (MLS) protocol
+SLIM relies on the Messaging Layer Security (MLS) protocol
 to provide end-to-end security for group communications between agents.
 
 ## MLS Integration
 
-AGP uses MLS for the following security properties:
+SLI uses MLS for the following security properties:
 
 * End-to-end encryption for all agent communications
 * Forward secrecy and post-compromise security
@@ -183,7 +195,7 @@ Implementations MUST:
 
 ## Privacy Considerations
 
-AGP with MLS provides:
+SLIM with MLS provides:
 
 * Metadata protection
 * Group membership privacy
@@ -197,4 +209,4 @@ Implementations MUST NOT:
 * Use non-MLS encryption schemes
 * Support downgrades to less secure modes
 * Allow plaintext communication
-* Skip credential verification
+* Skip credential verification