-
|
How does a SLIM node obtain group information for message distribution? Which protocol field is the group information stored in, and is it in plaintext? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hello @perhon In SLIM, groups are identified by a unique name. To join a group, an application must be invited either by a moderator (an application responsible for creating and updating the group) or through the control plane. Once added to a group, the application subscribes to the group name to receive all messages exchanged within that group. When a message is sent to a group, the destination name in the message is set to the group name. This ensures that all participants in the group receive the message. The group name is the only information required in the message to deliver it to all group participants. The destination field in the message is in plaintext, meaning it is not encrypted with the MLS protocol that SLIM uses for end-to-end encryption. This is necessary so that each SLIM node can read the message destination name and make forwarding decisions. However, if the connection between nodes is encrypted (for example, using TLS), the group name and the entire SLIM header are encrypted in the transmission between nodes. You can find more info about groups in the SLIM doc: https://docs.agntcy.org/messaging/slim-group/ |
Beta Was this translation helpful? Give feedback.
-
|
@micpapal bingo！ thank you. |
Beta Was this translation helpful? Give feedback.
Hello @perhon
In SLIM, groups are identified by a unique name. To join a group, an application must be invited either by a moderator (an application responsible for creating and updating the group) or through the control plane. Once added to a group, the application subscribes to the group name to receive all messages exchanged within that group.
When a message is sent to a group, the destination name in the message is set to the group name. This ensures that all participants in the group receive the message. The group name is the only information required in the message to deliver it to all group participants.
The destination field in the message is in plaintext, meaning it is not encryp…