Difference between revisions of "Np1sec/concurrent join"

(First version)
 
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=Proposal for concurrent join=
 
=Proposal for concurrent join=
  
−
With having session key confirmation one can have following protocol to handle concurrent join.
+
One can have the following protocol to handle concurrent join.
  
−
Each session can have 5 status: {current, potentially next, next, admissible, inadmissible}.
+
Each occupant can mark each session with one of the '''5 statuses: {current, in-limbo, dead}'''
 +
'''current''': User messages are being encrypted and decrypted in the current session. The join request will be processed by this session.
 +
'''in-limbo''': A session which is receiving shares and confirmations, this session can potentially become the next session if it receives session confirmation from all users.
 +
'''dead''': The session is abandoned and not going to become the current session.
  
−
==Session picking protocol for current occupant of the current session==
+
The protocol joins one user at a time but is greedy and non-blocking in respect to several concurrent joiners and eventually results in joins of all new users (as long as current users in the session cooperate with the join process). The global order of messages is essential for the protocol to succeed, which is a transport assumption for <math>n+1sec</math> protocol.
−
Suppose user <math>U_i</math> is in Session <math>S</math>. When new user <math>Unew_j</math> send a join request, user <math>U_i</math> start an admissible session <math>S_j</math>  with the list of authenticated participant in the room (not users in the session).
+
  
−
If <math>m</math> users are joining that session concurrently, there are <math>S_1,...,S_m</math> admissible which are receiving shares and authentication messages.
+
==Session picking protocol for new user joining the room==
 +
New user starts a join process by sending <math>(U_{joiner}, y_{joiner})</math>. In respose, it receives messages of the format
  
−
Suppose <math>S_j</math> receives the mutual authentication of all new users in admissible session <math>S_j</math> that will become the potentially next session of <math>U_i</math>. <math>U_i</math> then sends the combined list of (authenticated) participants in <math>S_j</math>, <math>(U_1,y_1,...,Unew_m,ynew_m,...)</math> to the room intending for new users not in the list to see and to authenticate to, and to old user to signal its potentially next session. It tags <math>S_1,...,S_m</math> as inadmissible sessions.
+
<math> sid, (U_1,y_1,...,U_{joiner},y_{joiner},...), kc_{i}, z_{i}</math>
  
−
When <math>U_i</math> receives all shares of potentially next session <math>S_j</math> and the authenticated list from all users from current session, they tag the session as next and send the session key confirmation of <math>S_j</math>. The session will not be tagged as inadmissible in case of new authenticated list, it just make new admissible session.
+
From each user <math>i</math>. The joiner makes a session for each <math>sid</math> which contains them as a participant, the user initiates a session and gathers shares. When a session receives all shares, it computes the session key and becomes the current session. All other sessions can remain in limbo or get discarded based on the memory capacity of the implementation and security requirement.
  
−
If user U_i receives another authenticated list from another <math>S_j'</math> then it tag <math>S_j</math> inadmissible as well and start an admissible session with <math>plist_{S_j'} \cup plist_{S_j}</math> as new admissible session waiting for authentication from new users.
+
==Session picking protocol for current occupant of the current session==
 +
Suppose user <math>U_i</math> is in Session <math>S</math>. When a new user <math>U_j</math> sends a join request, the user <math>U_i</math> starts a session in limbo <math>S_j</math> with the list of users in the current session plus the joining user. As part of initiation of each session <math>S_j</math> the current user sends a message of type:
  
−
If it receives key confirmation from all <math>U_l</math> in <math>(U_1,...,Unew_m,..)</math> then it will make <math>S_j</math> as current session and send messages to this session.
+
<math> sid, (U_1,y_1,...,U_{joiner},y_{joiner},...), kc_{i}, z_{i}</math>
  
−
==Session picking protocol for new user joining the room==
 
−
When a joining user Unew_l receives a list of potential users which is not including them, it authenticate to U_i's which new user has not yet authenticated to, and compute new share for the new share list. When they have all shares and authentication for plist_j then they send the key confirmation and wait for all of key confirmation.
 
  
−
When they receive confirmation from every user in plist_j. They make it current session and start chatting.
+
If <math>m</math> users are joining that session concurrently, there are <math>S_1,...,S_m</math> sessions in-limbo which are receiving shares and authentication messages.  
 +
 
 +
If <math>U_l</math>, currently in the session, signals to leave the room, a new session <math>S_l</math> is created. Furthermore, each session <math>S_j</math> in-limbo which has <math>U_l</math> as participants, results in the creation of new session <math>S_{j'}</math> with user <math>U_l</math> omitted and <math>S_j</math> is marked as dead.  
  
−
admissible -> {inadmissible, potentially next}
+
The user <math>U_i</math> sends the shares and authentication token necessary for each session. The first session which receives all confirmations will become the main session, and the joiner user of that session becomes the current session. All other <math>S_j</math> result in new sessions <math>S_{j''}</math> to which <math>U_{joiner}</math> is added. Previous active (current) session of the room becomes in-limbo.
−
potentially next ->{inadmissible, next}
+
−
next->{current}
+
  
−
current and inadmissible will be eventually discarded.
+
in-limbo -> {in-limbo, dead, current}
 +
current -> in-limbo

Latest revision as of 16:33, 13 March 2015

Proposal for concurrent join

One can have the following protocol to handle concurrent join.

Each occupant can mark each session with one of the 5 statuses: {current, in-limbo, dead} current: User messages are being encrypted and decrypted in the current session. The join request will be processed by this session. in-limbo: A session which is receiving shares and confirmations, this session can potentially become the next session if it receives session confirmation from all users. dead: The session is abandoned and not going to become the current session.

The protocol joins one user at a time but is greedy and non-blocking in respect to several concurrent joiners and eventually results in joins of all new users (as long as current users in the session cooperate with the join process). The global order of messages is essential for the protocol to succeed, which is a transport assumption for n+1sec protocol.

Session picking protocol for new user joining the room

New user starts a join process by sending (U_{{joiner}},y_{{joiner}}). In respose, it receives messages of the format

sid,(U_{1},y_{1},...,U_{{joiner}},y_{{joiner}},...),kc_{{i}},z_{{i}}

From each user i. The joiner makes a session for each sid which contains them as a participant, the user initiates a session and gathers shares. When a session receives all shares, it computes the session key and becomes the current session. All other sessions can remain in limbo or get discarded based on the memory capacity of the implementation and security requirement.

Session picking protocol for current occupant of the current session

Suppose user U_{i} is in Session S. When a new user U_{j} sends a join request, the user U_{i} starts a session in limbo S_{j} with the list of users in the current session plus the joining user. As part of initiation of each session S_{j} the current user sends a message of type:

sid,(U_{1},y_{1},...,U_{{joiner}},y_{{joiner}},...),kc_{{i}},z_{{i}}


If m users are joining that session concurrently, there are S_{1},...,S_{m} sessions in-limbo which are receiving shares and authentication messages.

If U_{l}, currently in the session, signals to leave the room, a new session S_{l} is created. Furthermore, each session S_{j} in-limbo which has U_{l} as participants, results in the creation of new session S_{{j'}} with user U_{l} omitted and S_{j} is marked as dead.

The user U_{i} sends the shares and authentication token necessary for each session. The first session which receives all confirmations will become the main session, and the joiner user of that session becomes the current session. All other S_{j} result in new sessions S_{{j''}} to which U_{{joiner}} is added. Previous active (current) session of the room becomes in-limbo.

in-limbo -> {in-limbo, dead, current} current -> in-limbo

Retrieved from "https://learn.equalit.ie/mw/index.php?title=Np1sec/concurrent_join&oldid=2953"