From b7ca90ef95b19c4d4744e97fb1bacbc72319523c Mon Sep 17 00:00:00 2001 From: zzz Date: Thu, 19 Sep 2019 14:58:43 +0000 Subject: [PATCH] prop 144 updates part 2 --- .../144-ecies-x25519-aead-ratchet.rst | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst b/i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst index ba350047..7bec7504 100644 --- a/i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst +++ b/i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst @@ -1217,7 +1217,6 @@ Optional blocks can have multiple I2NP blocks, but only a single padding block. If present, the padding block must be the final block. -KDF for Payload Section Encrypted Contents KDF for Ephemeral Key Section Encrypted Contents ```````````````````````````````````````````````` @@ -1281,12 +1280,23 @@ KDF for Ephemeral Key Section Encrypted Contents {% endhighlight %} + +KDF for Payload Section Encrypted Contents +`````````````````````````````````````````` + +TODO basically like the first Existing Session message, +post-split. + +.. raw:: html + + {% highlight lang='text' %} +TODO + +{% endhighlight %} + Notes ----- -Bob must include the matching session ID in the reply Ephemeral Key Section for Alice to -properly decrypt and bind the reply inbound session with the original outbound session. - Multiple NSR messages may be sent in reply, each with unique ephemeral keys, depending on the size of the response. Alice and Bob are required to use new ephemeral keys for every NS and NSR message.