gnunet-handbook

commit 559ef9bc97a1672bfe64cf3c0515f4c4bc471fb0
parent 51c3bc6a6092f6842958c8832d3617d497bcb6f3
Author: Julius Bünger <buenger@mytum.de>
Date:   Tue, 12 Mar 2024 17:18:58 +0100

cong: start section for details on pid construction

Diffstat:
M
developers/apis/cong.rst
 | 
17
++++++++++++++---

1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/developers/apis/cong.rst b/developers/apis/cong.rst
@@ -221,11 +221,22 @@ peer id. The change requires messenger to account for peer id changes.
 Details on how
 ^^^^^^^^^^^^^^
 
+Peer ids will be generated from the set of a peer's current addresses. Once a
+peer obtains the same set of addresses it shall be using the same peer id. To
+achieve this behavior, the current string representation of addresses is
+sorted, the sorted representation hashed and the peer id generated from the
+hash.
+.. TODO details?
+
+Once a peer id changes, all communication via open channels shall immediately
+cease. To signal this, the mq is to be used.
+.. TODO details?
+
 ..
    - adress bundle (transport communicators implement decision?)
-   - how adresses are generated:
-  	 - sort, hash, derive peer id from hash
-   - signaling functionality (signal pid change to higher layers)
+   - I vaguely remember the talk of 'insignificant' address changes (within
+     local network or such), that don't require a new peer id, but forgot the
+     specifics.
 
 
 .. _Open-questions: