From 6a3bc192fa4d433851f88581546c09f0420dac2e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Blin?=
 <sebastien.blin@savoirfairelinux.com>
Date: Fri, 23 Jul 2021 14:39:34 -0400
Subject: [PATCH] Update 2.3. Swarm

---
 technical/2.3.-Swarm.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/technical/2.3.-Swarm.md b/technical/2.3.-Swarm.md
index 581d4333..13b6f0c4 100644
--- a/technical/2.3.-Swarm.md
+++ b/technical/2.3.-Swarm.md
@@ -369,6 +369,26 @@ When the transfer is finished or the channel closed, the sha3sum is verified to
 
 In case of failure, when a device of the conversation will be back online, we will ask for all waiting files by the same way.
 
+## Call in swarm
+
+### TODO: nameserver part
+
+### Idea
+
+A swarm conversation can have multiple rendez-vous. A rendez-vous is defined by the following uri:
+
+"accountUri/deviceId/conversationId/confId" where accountUri/deviceId describes the host.
+
+The host can be determined via two ways:
+
++ In the swarm metadatas. Where it's stored like the title/desc/avatar of the room
++ Or the initial caller.
+
+When starting a call, the host will add a new commit to the swarm, with the URI to join (accountUri/deviceId/conversationId/confId).
+This will be valid till the end of the call (announced by a commit with the duration to show)
+
+So every part will receive the infos that a call has started and will be able to join it by calling it.
+
 ### Attacks?
 
 + Avoid git bombs
-- 
GitLab