gnunet-handbook

commit da1da92d2de5d4144e46019179c405ea9a33d694
parent bf4837a9b3f3e5e9baa96ce6272c6c378867d227
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Fri, 14 Jul 2023 18:52:51 +0200

add other comms

Diffstat:
M
developers/subsystems/transport-ng/transport-ng.rst
 | 
13
++++++++++++-

1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/developers/subsystems/transport-ng/transport-ng.rst b/developers/subsystems/transport-ng/transport-ng.rst
@@ -255,7 +255,6 @@ message are up to the communicators which use them. TRANSPORT may fail
 transmitting backchannel messages, and TRANSPORT will not attempt to
 retransmit them.
 
-
 UDP communicator
 ^^^^^^^^^^^^^^^^
 
@@ -284,3 +283,15 @@ stamp, its peer ID, and the target peerID and send this data as well as the sign
 in one of the first packets.
 Receivers should keep track (persist) of the monotonic time stamps for each
 peer ID to reject possible replay attacks.
+
+FIXME: Handshake wire format? KX, Flow.
+
+TCP communicator
+^^^^^^^^^^^^^^^^
+
+FIXME: Handshake wire format? KX, Flow.
+
+QUIC communicator
+^^^^^^^^^^^^^^^^^
+
+FIXME: Handshake wire format? KX, Flow.