You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pid="section-note.1-1">This note is to be removed before publishing as an RFC.<ahref="#section-note.1-1" class="pilcrow">¶</a></p>
1112
1114
<pid="section-note.1-2">
1113
-
The latest revision of this draft can be found at <span><ahref="https://spec.agp.agntcy.org">https://spec.agp.agntcy.org</a></span>.
1114
-
Status information for this document may be found at <span><ahref="https://datatracker.ietf.org/doc/draft-agntcy-agp/">https://datatracker.ietf.org/doc/draft-agntcy-agp/</a></span>.<ahref="#section-note.1-2" class="pilcrow">¶</a></p>
1115
+
The latest revision of this draft can be found at <span><ahref="https://spec.slim.agntcy.org">https://spec.slim.agntcy.org</a></span>.
1116
+
Status information for this document may be found at <span><ahref="https://datatracker.ietf.org/doc/draft-agntcy-slim/">https://datatracker.ietf.org/doc/draft-agntcy-slim/</a></span>.<ahref="#section-note.1-2" class="pilcrow">¶</a></p>
1115
1117
<pid="section-note.1-3">
1116
1118
Discussion of this document takes place on the
1117
1119
WG Working Group mailing list (<span><ahref="mailto:discussion@agntcy.org">mailto:discussion@agntcy.org</a></span>).<ahref="#section-note.1-3" class="pilcrow">¶</a></p>
1118
1120
<pid="section-note.1-4">Source for this draft and an issue tracker can be found at
<pid="section-3.2.1-1">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.<ahref="#section-3.2.1-1" class="pilcrow">¶</a></p>
1336
+
<pid="section-3.2.1-1">Nodes are essential components of the SLIM architecture.
1337
+
They handle routing and message distribution between agents and manage the
1338
+
communication infrastructure. Meassaging Nodes are composed of two main tables: the
1339
+
connection table and the subscription table.<ahref="#section-3.2.1-1" class="pilcrow">¶</a></p>
<pid="section-3.2.1.1-1">The connection table maintains interfaces with neighboring nodes and local applications. It is responsible for:<ahref="#section-3.2.1.1-1" class="pilcrow">¶</a></p>
1345
+
<pid="section-3.2.1.1-1">The connection table maintains interfaces with neighboring nodes and local
1346
+
applications. It is responsible for:<ahref="#section-3.2.1.1-1" class="pilcrow">¶</a></p>
1341
1347
<ulclass="normal">
1342
1348
<liclass="normal" id="section-3.2.1.1-2.1">
1343
1349
<pid="section-3.2.1.1-2.1.1">Establishing and managing connections with other Gateway Nodes<ahref="#section-3.2.1.1-2.1.1" class="pilcrow">¶</a></p>
<pid="section-3.2.1.1-4.1.1">Node ID: Unique identifier for the neighboring node or local application<ahref="#section-3.2.1.1-4.1.1" class="pilcrow">¶</a></p>
1356
1362
</li>
1357
1363
<liclass="normal" id="section-3.2.1.1-4.2">
1358
-
<pid="section-3.2.1.1-4.2.1">Connection Status: Current status of the connection (e.g., active, inactive, error)<ahref="#section-3.2.1.1-4.2.1" class="pilcrow">¶</a></p>
1364
+
<pid="section-3.2.1.1-4.2.1">Connection Status: Current status of the connection (e.g., active, inactive,
<pid="section-3.2.1.1-4.3.1">Connection Parameters: Details such as IP address, port, and security credentials<ahref="#section-3.2.1.1-4.3.1" class="pilcrow">¶</a></p>
1368
+
<pid="section-3.2.1.1-4.3.1">Connection Parameters: Details such as IP address, port, and security
<pid="section-3.2.1.2-1">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:<ahref="#section-3.2.1.2-1" class="pilcrow">¶</a></p>
1379
+
<pid="section-3.2.1.2-1">The subscription table is used to map topic subscriptions to neighboring nodes.
1380
+
It manages the distribution of messages based on topic subscriptions and ensures
1381
+
efficient routing of pub/sub messages. The subscription table entries include:<ahref="#section-3.2.1.2-1" class="pilcrow">¶</a></p>
1372
1382
<ulclass="normal">
1373
1383
<liclass="normal" id="section-3.2.1.2-2.1">
1374
1384
<pid="section-3.2.1.2-2.1.1">Topic: The name of the topic to which the subscription applies<ahref="#section-3.2.1.2-2.1.1" class="pilcrow">¶</a></p>
<pid="section-3.2.1.2-2.2.1">Subscriber Node IDs: List of node IDs that have subscribed to the topic<ahref="#section-3.2.1.2-2.2.1" class="pilcrow">¶</a></p>
1378
1388
</li>
1379
1389
<liclass="normal" id="section-3.2.1.2-2.3">
1380
-
<pid="section-3.2.1.2-2.3.1">Subscription Status: Current status of the subscription (e.g., active, inactive)<ahref="#section-3.2.1.2-2.3.1" class="pilcrow">¶</a></p>
1390
+
<pid="section-3.2.1.2-2.3.1">Subscription Status: Current status of the subscription (e.g., active,
<pid="section-3.2.1.2-4.4.1">Ensuring efficient and reliable message delivery<ahref="#section-3.2.1.2-4.4.1" class="pilcrow">¶</a></p>
1396
1407
</li>
1397
1408
</ul>
1398
-
<pid="section-3.2.1.2-5">By maintaining these tables, Gateway Nodes facilitate seamless communication and message distribution in the AGP network, enabling real-time interactive AI applications at scale.<ahref="#section-3.2.1.2-5" class="pilcrow">¶</a></p>
1409
+
<pid="section-3.2.1.2-5">By maintaining these tables, Meassaging Nodes facilitate seamless communication and
1410
+
message distribution in a SLIM network, enabling real-time interactive AI
1411
+
applications at scale.<ahref="#section-3.2.1.2-5" class="pilcrow">¶</a></p>
0 commit comments