Revision Summary Date Revision History Revision Class Comments 3/30/2012 1.0 New Released new document. 7/12/2012 2.0 Updated and revised the technical content. 10/25/2012 2.1 Minor Clarified the meaning of the technical content. 1/31/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Updated and revised the technical content. 11/14/2013 4.0 Major Updated and revised the technical content. 2/13/2014 5.0 Major Updated and revised the technical content. 5/15/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 6.0 Significantly changed the technical content.
9/24/2015 6.1 Minor Clarified the meaning of the technical content. 10/16/2015 6.1 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 6.2 Clarified the meaning of the technical content.
Configures the RPC runtime to perform a strict data consistency at target level 5.0. section 2.1 LSAD In the Microsoft implementation, uses IDL "[range]" attributes to limit the size of requests that will be accepted by the directory service. [MS-LSAD] sections 6 and 7 In the Microsoft implementation, configures the RPC runtime to perform a strict NDR data consistency at target level 5.0. [MS-LSAD] section 7 Configures the RPC runtime to enforce Maximum Server Input Data Size. [MS-LSAD] section 2.2.1 LSAT In the Microsoft implementation, uses IDL "[range]" attributes to limit the size of requests that will be accepted by the directory service. [MS-LSAT] sections 6 and 7 In the Microsoft implementation, configures the RPC runtime to perform a strict NDR data consistency check at target level 5.0. [MS-LSAT] section 7 WS-Transfer * * ADCAP * * Implementations can provide mechanisms to limit the operations that can be performed or the size of the response.<6>
attachment to an SMTP mail message, is sent to DC2. DC2 receives the request. The SMTP service on DC2 receives the mail message from DC1 and gives the frame to the SRPL extension. The SRPL extension performs message processing operations ([MS-SRPL] section 3.3.5) and then passes the BLOB to the DRS engine, which processes the request. DC2 sends the SMTP response as follows. After it processes the request, the DRS engine on DC2 generates another DRS BLOB, which contains the response. The SRPL extension performs the higher-layer triggered operation and then passes the response to the SMTP service. The SMTP service sends the message to DC1 as an attachment to an SMTP mail message. DC1 receives the response. The SMTP service on DC1 receives the mail message and gives the frame to the SRPL extension. The SRPL extension performs message processing and passes the BLOB to the DRS engine, which processes the response. Example 23: Cross-Domain Move This example demonstrates the use case in section , Cross-Domain Move - Client Application. It is explained in section 4.1.15.4.
Index A 112 27 22 32 C 103 180 107 30 22 D Dependencies 30 30 E 29 104 Examples 125 113 113 Extensibility 177 177 103 30 F 22 G 10 I 177 108 19 32 5 M 177 O Overview 27 22 P 178 R 19 Requirements 107 104 32 S 108 29 30 30 104 27 33 T 27 180 U 33 V Versioning 177 103 177