Value Meaning 0x00010000 — 0x00010004 Any protocol version number between 1.0 and 1.4 implements the base features. 0x00010005 Protocol version number 1.5 implements the base features, and adds support for coalescence. Note The coalescence feature is not used by the base implementation of the DirectPlay DXDiag Usage Protocol. 0x00010006 Protocol version number 1.6 implements the base features, supports coalescence, and adds support for signing. Note The signing feature is not used by the base implementation of the DirectPlay DXDiag Usage Protocol. dwSessID (4 bytes): A 32-bit integer session identifier. The value MUST be set to the value of dwSessID specified in the TRANS_COMMAND_CONNECT packet; otherwise, the packet SHOULD be ignored. tTimestamp (4 bytes): A 32-bit integer that provides the sender's computer system tick count. The value of the tTimestamp field SHOULD be ignored, but MAY be used to estimate the differences in local tick counts between a sender and receiver. TRANS_COMMAND_SACK The TRANS_COMMAND_SACK packet is used to acknowledge outstanding packets. Packet ACK is typically bundled in all user data packets using the bSeq and bNRcv fields found in the . However, the TRANS_COMMAND_SACK packet is used in the following scenarios: A dedicated ACK is requested (that is, when the PACKET_COMMAND_POLL bit in the bCommand header field is set). No user data remains for further bundled acknowledgments. The elapses. 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 bCommand bExtOpCode bFlags bRetry bNSeq bNRcv wPadding tTimestamp dwSACKMask1 (optional) dwSACKMask2 (optional) dwSendMask1 (optional) dwSendMask2 (optional) bCommand (1 byte): An 8-bit integer that provides the command code for the message. This field MUST be set to one of the following values.
Value Meaning 0x00010000 — 0x00010004 Any protocol version number between 1.0 and 1.4 implements the base features. 0x00010005 Protocol version number 1.5 implements the base features, and adds support for coalescence. Note The coalescence feature is not used by the base implementation of the DirectPlay DXDiag Usage Protocol. 0x00010006 Protocol version number 1.6 implements the base features, supports coalescence, and adds support for signing. Note The signing feature is not used by the base implementation of the DirectPlay DXDiag Usage Protocol. dwSessID (4 bytes): A 32-bit integer session identifier. The value MUST be set to the value of dwSessID specified in the TRANS_COMMAND_CONNECT packet; otherwise, the packet SHOULD be ignored. tTimestamp (4 bytes): A 32-bit integer that provides the sender's computer system tick count. The value of the tTimestamp field SHOULD be ignored, but MAY be used to estimate the differences in local tick counts between a sender and receiver. TRANS_COMMAND_SACK The TRANS_COMMAND_SACK packet is used to acknowledge outstanding packets. Packet ACK is typically bundled in all user data packets using the bSeq and bNRcv fields found in the . However, the TRANS_COMMAND_SACK packet is used in the following scenarios: A dedicated ACK is requested (that is, when the PACKET_COMMAND_POLL bit in the bCommand header field is set). No user data remains for further bundled acknowledgments. The elapses. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 bCommand bExtOpCode bFlags bRetry bNSeq bNRcv wPadding tTimestamp dwSACKMask1 (optional) dwSACKMask2 (optional) dwSendMask1 (optional) dwSendMask2 (optional) bCommand (1 byte): An 8-bit integer that provides the command code for the message. This field MUST be set to one of the following values.