Partager via

3.1.5.1.1 Sending of MCS Disconnect Provider Ultimatum PDU

  • Article

The structure and fields of the MCS Disconnect Provider Ultimatum PDU are specified in section 2.2.2.3.

The tpktHeader field is initialized as specified 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 Disconnect Provider Ultimatum PDU (embedded within the mcsDPum field) is specified in [T125] section 7, part 4. Only the rn-provider-initiated (1) or rn-user-requested (3) reason codes MUST be used in the reason field.

  • In the case of a user-initiated client-side disconnection (section 1.3.1.4.1), the reason code set by the client MUST be rn-user-requested (3).

  • In the case of a user-initiated server-side disconnection (section 1.3.1.4.2), the reason code set by the server MUST be rn-user-requested (3).

  • In the case of an administrator-initiated server-side disconnection (section 1.3.1.4.3), the reason code set by the server MUST be rn-provider-initiated (1).

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.

Once the MCS Disconnect Provider Ultimatum PDU has been sent, the network connection MUST be closed.