Changes
/* VIII.10 (n+1)sec Message Handling */
If the message has a session id of a session that the user is part of, then message handling is governed by the finite state machine table described below. Otherwise, the messages should be handled as follows:
=====Joiner=====
In current (n+1)sec implementation, this state is implemented as:
* Messages without session id (including JOIN_REQUEST):The Joiner, user in "JOINIG" state will ignores all messages without session id.
* If the message has a session id corresponding to a session that which the joiner already has not constructed (and is in process of joining, i.e. is not DEAD), then - the session FSM joiner will deal with the message.react as follows:
** ''Participant Info'': *** If the message has joiner is mentioned in the participant list, the joiner construct a session id which with that list.*** If the joiner has is not constructed - mentioned in the plist, the joiner will react as follows:ignore the message (*** Should the joiner begins a session by appending itself to the list?).
** ''Participant InfoSession Confirmation'': ** If the The joiner is mentioned in will mark all sessions as DEAD and wait for the new participant list, the joiner construct a session with that list.** If the joiner is not mentioned in the plist, the joiner ignore the message (*** Should the should joiner begins send a session by appending itself to the listnew join request?).
=====Confirmed Participant=====
