-
Notifications
You must be signed in to change notification settings - Fork 0
Conversations
Two parties may establish a long-running conversation with dedicated rolling keys that are used for symmetric encryption of the messages that are exchanged. Each party has its own key, and each party maintains a synchronized copy of the other party's key in order to decrypt incoming messages.
Two packets are required to establish a conversation. In a conversation between parties A and B, party A could begin the conversation by sending a START-CONVO packet along with its contribution of key material and a CONVERSATION-ID unique to the two parties. Party B, upon receipt and verification of A's packet, would send an ACCEPT-CONVO packet along with B's contribution of key material.
More than one conversation can be in play simultaneously between two parties. Each conversation is identified by a CONVERSATION-ID that is specified in the envelope.
Either party may end the conversation by sending an END-CONVO packet. Conversations should be closed automatically if they have been idle for more than 30 minutes.