The Session object's State moves to Ready. The Session object can be used by protocols to create connections to the peer. Handling the Accept Header The following sequence defines the required actions following the activation of the session: The server MUST listen on transports according to information that was exchanged with the client in earlier steps of the protocol. The client MUST attempt to connect to the server on all the transports that the server is listening on. The server chooses the best connection and accepts it. On connection establishment, the client MUST send an Accept Header (section ) to the server. On receipt of the Accept Header, the server MUST validate the SessionID from the Accept Header by comparing it to the ReplyChannelID that it received from the client in the Session Activation message (section ). If the IDs match, the server MUST send the Accept Header back to the client. If the IDs do not match, the server MUST abort the connection. The client MUST validate the Accept Header received from the server by comparing it to the Accept Header it sent before. If the Accept Headers the negotiation is complete; otherwise, the client MUST abort the connection. Timer Events The following timer events are associated with the timers defined by this protocol (section ). SessionProtocolTimer: If this timer fires when the associated Session object (section ) State is WaitingForAck or WaitingForTransmit, the object transitions to the Terminated state. This Session object is not usable by higher-level protocols. If this timer fires when the Session object State is Ready, the timer is ignored. OOBConnectorProtocolTimer: If this timer fires when the associated OOB Connector object (section ) State is WaitingForAck or WaitingForTransmit, the object State transitions to Incomplete. If this timer fires when the OOB Connector object State is any other value, the timer is ignored. OOBConnectorKeepAliveTimer: If this timer fires before the associated OOB Connector object State transitions out of Incomplete, the reference logged at initialization SHOULD be released. If there are no other references to the object, the object SHOULD be destroyed. SessionFactoryKeepAliveTimer: An independent timer for each Session Factory object (section ), which is started when a Session Factory object is created. If it fires before a client takes ownership of the object, the Session Factory object SHOULD be deleted. Other Local Events None.
The Session object's State moves to Ready. The Session object can be used by protocols to create connections to the peer. Handling the Accept Header The following sequence defines the required actions following the activation of the session: The server MUST listen on transports according to information that was exchanged with the client in earlier steps of the protocol. The client MUST attempt to connect to the server on all the transports that the server is listening on. The server chooses the best connection and accepts it. On connection establishment, the client MUST send an Accept Header (section ) to the server. On receipt of the Accept Header, the server MUST validate the SessionID from the Accept Header by comparing it to the ReplyChannelID that it received from the client in the Session Activation message (section ). If the IDs match, the server MUST send the Accept Header back to the client. If the IDs do not match, the server MUST abort the connection. The client MUST validate the Accept Header received from the server by comparing it to the Accept Header it sent before. If the Accept Headers the negotiation is complete; otherwise, the client MUST abort the connection. Timer Events The following timer events are associated with the timers defined by this protocol (section ). SessionProtocolTimer: If this timer fires when the associated Session object (section ) State is WaitingForAck or WaitingForTransmit, the object transitions to the Terminated state. This Session object is not usable by higher-level protocols. If this timer fires when the Session object State is Ready, the timer is ignored. OOBConnectorProtocolTimer: If this timer fires when the associated OOB Connector object (section ) State is WaitingForAck or WaitingForTransmit, the object State transitions to Incomplete. If this timer fires when the OOB Connector object State is any other value, the timer is ignored. OOBConnectorKeepAliveTimer: If this timer fires before the associated OOB Connector object State transitions out of Incomplete, the reference logged at initialization SHOULD be released. If there are no other references to the object, the object SHOULD be destroyed. SessionFactoryKeepAliveTimer: An independent timer for each Session Factory object (section ), which is started when a Session Factory object is created. If it fires before a client takes ownership of the object, the Session Factory object SHOULD be deleted. Other Local Events None.
%5BMS-NFPB%5D-171201.docx