[OTR-dev] OTRv3 instance tag and session switching

[Ian Goldberg]

On Wed, Dec 11, 2013 at 04:49:59PM +0200, M. D. wrote:
>  
>  >Error Messages and Query Messages aren't handled by ConnContexts.  If
>  >they cause Alice to try to start a new session, new sessions will start
>  >with a Commit Message with a receiver instance 0, so that any instance
>  >of Bob may respond.  In libotr, this is implemented via a "master
>  >context" that remembers (for v3) just the secrets used to construct the
>  >Commit Message.  But this implementation detail is not part of the spec;
>  >you can implement it however you like.
> 
> Okay, things are much more clear now! Thank you very much!
> 
> I have just one more question: do every ConnContext maintain its own
> Message_State and Policy? It seems to me that things become much more
> complicated if the 'master context' policy and message state are not
> in sync with its slave's conn contexts. Am I right?

Different child contexts can definitely be in different message states.
For example, Alice is talking to Bob1 and Bob2, and Bob1 ends the
private conversation.  Alice is still talking privately to Bob2.

   - Ian