2.1 Transport
All remote procedure call (RPC) protocols use RPC dynamic endpoints (2) and well-known endpoints (2), as specified in [C706].
The Exchange Server NSPI Protocol uses the following RPC protocol sequences:
The protocol allows a server to be configured to use a specific port for RPC over TCP. The mechanism for configuring a server to use a specific port is not constrained by the Exchange Server NSPI Protocol. The mechanism for a client to discover this configured TCP port is not constrained by the Exchange Server NSPI Protocol.
For the network protocol sequence RPC over HTTPS, this protocol MUST use the well-known endpoint 6004. For RPC over TCP, this protocol can use RPC dynamic endpoints, as defined in Part 4 of [C706].
This protocol MUST use the UUID F5CC5A18-4264-101A-8C59-08002B2F8426. The protocol MUST use the RPC version number 56.0.
The protocol uses the underlying RPC protocol to retrieve the identity of the client that made the method call, as specified in [MS-RPCE]. The server MAY use this identity to perform access checks, as described in section 5 of this document.
The server MAY enforce limits on the maximum RPC packet size that it will accept.