3.3.5.3.9 Sending MCS Channel Join Confirm PDU(s)
The structure and fields of the MCS Channel Join Confirm PDU are described in section 2.2.1.9.
The tpktHeader field is initialized as described in [T123] section 8, while the x224Data field (which contains an X.224 Class 0 Data TPDU) is initialized as specified in [X224] section 13.7.
The MCS Channel Join Confirm PDU (embedded within the mcsCJcf field) is described in [T125] section 7, parts 6 and 10. The result field MUST be set to rt-successful (0) if the MCS channel ID in the corresponding MCS Channel Join Request PDU (section 3.3.5.3.8) was successfully joined. If an error occurred during the join (for example, too many channels, no such MCS channel ID, or a memory allocation error), the server MUST set the result field to rt-unspecified-failure (14). The remaining fields MUST be initialized as follows (these fields are essentially copied over from the MCS Channel Join Request PDU).
|
Channel Join Confirm field |
Value |
|---|---|
|
initiator |
The initiator value which was sent in the corresponding MCS Channel Join Request PDU. |
|
requested |
The MCS channel ID which was sent in the corresponding MCS Channel Join Request PDU. |
|
channelId |
The MCS channel ID which was sent in the corresponding MCS Channel Join Request PDU. |
The optional channelId field MUST be included in the MCS Channel Join Confirm PDU sent to the client.
If Enhanced RDP Security (section 5.4) is in effect, the External Security Protocol (section 5.4.5) MUST be used to encrypt the entire PDU and generate a verification digest before the PDU is transmitted over the wire.