Share via


2.2.3.6 RPC

An RPC technical specification defines a method-based protocol, which uses a formal syntax with calls and return codes, and in which a protocol client initiates all communication and a protocol server responds to the protocol client. RPC specifies request/response protocols, in which all arguments come directly from the higher layer, and all return codes, output parameters, and exceptions are passed unmodified.

Some RPC specifications specify protocols that use the Distributed Component Object Model (DCOM) as their transport, which uses the TCP/IP RPC protocol sequence. Such protocols can use the DCOM security and authentication framework and interface activation.

RPC specifications use Interface Definition Language (IDL) to specify the syntax of protocol methods and marshaling of protocol data. Such interface definitions can be compiled by using the Microsoft Interface Definition Language (MIDL) compiler with command-line parameters, as follows: "midl /target NT60 /nologo". To avoid duplicating the definitions of common data types, RPC protocol IDL sections can contain one or more import directives for IDL data from other technical specifications, including the following:

RPC specifications can contain the following types of normative information, where applicable.

RPC specifications include the following normative reference:

For DCOM-based RPC protocols, the following normative reference is included: