3.1.5.6 DPSP_MSG_KEYEXCHANGEREPLY

  • Article

When a DirectPlay 4 client receives a DPSP_MSG_KEYEXCHANGEREPLY message (section 2.2.35), the DirectPlay 4 client MUST remember the SessionKey contained in the message as Session.SessionKey. It MUST then format a DPSP_MSG_ADDFORWARDREQUEST message (section 2.2.11) with the PlayerID field set to the system player ID. The client MUST then start the reliable API timer and wait for a DPSP_MSG_SUPERENUMPLAYERSREPLY message (section 2.2.53). If no reply is received before the reliable API timer fires, then the client MUST return this information to the higher-level entity.