Added more details about design of announcer tasks.

1 files changed, 29 insertions, 0 deletions

diff --git a/conn-notes.txt b/conn-notes.txt
index a072afec..c1bbed00 100644
--- a/conn-notes.txt
+++ b/conn-notes.txt
@@ -42,6 +42,35 @@ while (account is active):
                                 (AwaitingHandshake)
                         send handshake
 
+Plan: Suppose our user key is OrjBG.GyWuQhGc1pb0KssgmYAocohFh35Vx8mREC9Nu and we have
+a contact with user key DdhbLjiwaV0GAiGKgesNPbvj2TbhrBHEWEEc5icfvQN.  The following AnnounceKeys
+will be scheduled:
+
+        toxid:OrjBG.GyWuQhGc1pb0KssgmYAocohFh35Vx8mREC9Nu
+
+                This task searches for our own user key, and publishes itself
+                at rendezvous nodes.
+
+        dhtkey:DdhbLjiwaV0GAiGKgesNPbvj2TbhrBHEWEEc5icfvQN
+
+                This task searches for our contact's user key and uses the
+                rendezvous nodes that it finds in order to share our dhtkey
+                with our contact.
+
+
+        connect:DdhbLjiwaV0GAiGKgesNPbvj2TbhrBHEWEEc5icfvQN
+
+                Depending on whether or not the ip/port is "fresh", this task
+                has two modes only one of which is active at a time:
+
+                (1) (stale) Search for our contact's dhtkey (nodeid) in order
+                to discover his ip address and port.
+
+                (2) (fresh) Send handshakes to our friend every 5 seconds.
+
+The toxid:* task will be scheduled as long as you are online.  The dhtkey:* and
+connect:* will only be scheduled when there is no active "netcrypto" session
+link with your contact.
 
 On inbound
 ----------