commit d8a5834bb59faf1af1be3e454ccf6eb31c1d527e
parent 9ef5404060fca428bd16556908f23794ebd5d742
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Mon, 11 Nov 2024 15:14:40 +0100
Correct rst paragraph
Diffstat:
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/developers/apis/cong.rst b/developers/apis/cong.rst
@@ -147,8 +147,8 @@ The initiator selection remains unchanged from the above protocol.
-First Message (RTT=0):
-======================
+First Message (RTT=0)
+"""""""""""""""""""""
``I`` sends to ``R`` the following message:
@@ -213,7 +213,7 @@ and encrypt the certificate giving us the ``EncryptedInitiatorCert``.
Second Message (RTT=0.5)
-========================
+""""""""""""""""""""""""
``R`` the receives:
@@ -273,7 +273,7 @@ First ``R`` processes the message received from ``I``:
Third Message (RTT=1.5)
-=======================
+"""""""""""""""""""""""
``I`` receives:
@@ -319,7 +319,7 @@ First ``I`` processes the message received from ``R``:
Confirmation (RTT=1.5)
-======================
+""""""""""""""""""""""
``R`` receives ``IteratorFinished`` and computes:
@@ -332,13 +332,13 @@ Confirmation (RTT=1.5)
At this point we have a secure channel and application payload can be en/decrypted using **IATS** and **RATS**, respectively.
Rekey / Service Status change
-=============================
+"""""""""""""""""""""""""""""
TODO
Edge Cases
-==========
+""""""""""
* The Initiator/Receiver selection logic may require a timed fallback: The designates Initiator may never initiate (NAT, already has sufficient connections, learns about receiver later than receiver about initiator etc.)
* This may result in edge cases where the Initiator initiates a handshake and the Receiver also initiates a handshake at the same time switching roles.
@@ -346,7 +346,7 @@ Edge Cases
Glossary
-========
+""""""""
* **IATS**: Initiator Application Traffic Secret Key
* **RATS**: Receiver Application Traffic Secret Key
