lsd0012

commit 8f676c695b5c5169b3d0770599f2b9c22de1e55d
parent 5ebf138c555d68bb64421fd02d36f15a39f07aea
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon, 11 Nov 2024 22:52:31 +0100

typos

Diffstat:
M
draft-schanzen-cake.xml
 | 
10
+---------

1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/draft-schanzen-cake.xml b/draft-schanzen-cake.xml
@@ -129,15 +129,7 @@
       <t>
         We use the notation and terminology of <xref target="RFC9180"/> throughout
         this document.
-        In addition, we define:
       </t>
-      <dl>
-        <dt>coinFlip()</dt>
-        <dd>
-          A helper function that returns "heads" or "tails". Each result is
-          returned with a likelihood of 50%.
-        </dd>
-      </dl>
     </section>
     <section anchor="handshake" numbered="true" toc="default">
       <name>Handshake protocol</name>
@@ -145,7 +137,7 @@
         This protocol is heavily inspired by <xref target="KEMTLS"/>.
       </t>
       <t>
-        We assume that the peers have semi-static (as opposed to ephemeral) key pairs. Let (pk<sub>A/<sub>,sk<sub>A</sub>) be the key pair of peer PID</sub>A</sub> and (pk<sub>B</sub>,sk<sub>B</sub>) the key pair of peer PID<sub>B</sub>.
+        We assume that the peers have semi-static (as opposed to ephemeral) key pairs. Let (pk<sub>A</sub>,sk<sub>A</sub>) be the key pair of peer PID<sub>A</sub> and (pk<sub>B</sub>,sk<sub>B</sub>) the key pair of peer PID<sub>B</sub>.
       </t>
       <t>
         For any secure handshake protocol, we have to dermine an initiator and a receiver in the protocol. We use <tt>GNUNET_CRYPTO_hash_cmp</tt> to determine which peer is the receiver R and which peer the initiator I: