1.4 Relationship to Other Protocols
The RRAS Management Protocol relies on RPC [MS-RPCE] as a transport. It is used to remotely manage RRAS server implementations.
This protocol uses RPC over named pipes as specified in section 2.1. The support for the RPC protocol sequence using named pipes is as specified in the [MS-RPCE] section 2.1.1.2.
This protocol uses DCOM [MS-DCOM] as specified in section 2.
The registry values that the RRASM client uses for configurations are handled using the [MS-RRP] protocol. Any RRAS server implementation can use these registry settings to initialize the RRAS server configuration.
The client-side Remote Access Service (RAS) is a point-to-point or point-to-site service. It is not to be confused with this RRASM protocol, which is a site-to-site server-side router management protocol. Some of the functions in the RAS API are supported only on network servers, and other functions are supported only on network clients. See legacy information in [MSDOCS-RA-API].