18.104.22.168 Sending the RopBackoff ROP Response
When the server determines that a ROP request is required to be delayed, the server MUST either respond with a RopBackoffROP response (section 22.214.171.124) or fail the ExDoRpcExt2 method, as specified in [MS-OXCRPC] section 126.96.36.199, or the Execute request type,<23> as specified in [MS-OXCMAPIHTTP] section 188.8.131.52.
If the server version, as defined in [MS-OXCRPC] section 184.108.40.206.3.2. is greater than 08.00.0525.0 and the client version, as defined in [MS-OXCRPC] section 220.127.116.11.3.2, is greater than 12.0.4228.0, the server SHOULD substitute a RopBackoff ROP response in place of the response for the delayed ROP request. If either the client or the server is an earlier version, then the server MUST instead fail either the ExDoRpcExt2 method by raising the RPC_S_SERVER_TOO_BUSY exception, as specified in [MS-OXCRPC], or the Execute request type with an HTTP status code of 200, a value of 0 (success) in the X-ResponseCode header, and a value of 0x000006BB in the StatusCode field of the Execute request type failure response body, as specified in [MS-OXCMAPIHTTP].
If ROPs are specified in a RopBackoff ROP response, all subsequent ROP requests SHOULD NOT be processed.