commit d761e0bf8d031c59a01df5e677810d5f78540db2
parent ef8ceb591e61522018922b56bab058486efacfdd
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 29 Aug 2023 09:01:57 +0200
minor clarification tng comm
Diffstat:
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/developers/transport-ng/transport-ng.rst b/developers/transport-ng/transport-ng.rst
@@ -216,8 +216,12 @@ TRANSPORT may ask a communicator to try to connect to another address.
TRANSPORT will only ask for connections where the address matches the
communicator's address prefix that was provided when the connection was
established. Communicators should then attempt to establish a
-connection. No response is provided to TRANSPORT service on failure. The
-TRANSPORT service has to ask the communicator explicitly to retry.
+connection.
+It is under the discretion of the communicator whether to honor this request.
+Reasons for not honoring such a request may be that an existing connection exists
+or resource limitations.
+No response is provided to TRANSPORT service on failure.
+The TRANSPORT service has to ask the communicator explicitly to retry.
If a communicator succeeds in establishing an outgoing connection for
transmission, or if a communicator receives an incoming bi-directional
@@ -293,5 +297,7 @@ FIXME: Handshake wire format? KX, Flow.
QUIC communicator
^^^^^^^^^^^^^^^^^
-
+The QUIC communicator runs over a bi-directional UDP connection.
+TLS layer with self-signed certificates (binding/signed with peer ID?).
+Single, bi-directional stream?
FIXME: Handshake wire format? KX, Flow.
