@@ -348,7 +348,9 @@ contact `~worwel-sipnum` but does not know the IP address and port at which
348`~worwel-sipnum` resides. Both planets live under `~zod`, which knows both of
348`~worwel-sipnum` resides. Both planets live under `~zod`, which knows both of
349their IP and port numbers by virtue of being the galaxy that both live under.
349their IP and port numbers by virtue of being the galaxy that both live under.
351+To prepare, `~bacbel-tagfeb` forms a Diffie-Hellman symmetric key with their own
352+private key and the public key of `~worwel-sipnum`, obtained via Jael. Then
351−So `~bacbel-tagfeb` sends a packet addressed to `~worwel-sipnum` to `~zod`.
353+`~bacbel-tagfeb` sends a packet addressed to `~worwel-sipnum` to `~zod`.
353The packet has the following format:
355The packet has the following format:
354 - The standard Ames header described in [header](#header), where the checksum
356 - The standard Ames header described in [header](#header), where the checksum
@@ -361,8 +363,7 @@ followed by the payload.
361 - The payload of this packet will be the `+jam` of `[origin content]`. `origin`
363 - The payload of this packet will be the `+jam` of `[origin content]`. `origin`
362for this initial packet will be `~`, which implies that the packet is
364for this initial packet will be `~`, which implies that the packet is
363originating from the sender. `content` is the `+jam` of the message, encrypted
365originating from the sender. `content` is the `+jam` of the message, encrypted
364−using a Diffie-Hellman symmetric key obtained with the private key of
366+using the Diffie-Hellman symmetric key that was previously computed.
365−`~bacbel-tagfeb` and the public key of `~worwel-sipnum`.
367`~zod` receives the packet and reads the body. It sees that it is not the
368`~zod` receives the packet and reads the body. It sees that it is not the
368intended recipient of the packet, and so gets ready to forward it to
369intended recipient of the packet, and so gets ready to forward it to