The routing and remote access service (RRAS) server management (RRASM) protocol enables remote management (configuration and monitoring) of an RRAS implementation. The RRAS implementation here refers to the components that can be configured to provide the following functionality:
Remote access service
The RRASM protocol is a client/server protocol based on remote procedure call (RPC). It comprises RPC methods that enable the remote management of an RRAS implementation.
This document also specifies the registry information that can be used to specify the overall RRAS configuration. These registry settings can be managed remotely using the [MS-RRP] protocol. Additionally, for site-to-site connectivity, the settings to be used to connect to a remote site are specified in the form of a phonebook file. This document also specifies the format of the phonebook file used by RRAS server.
As a part of remote management of RRAS implementation, a management application should use the RPC methods to manage the RRAS implementation actively (while RRAS is running). When RRAS is not active, the configurations should be managed through the registry information. The management application can use the phonebook file format to specify the connection configuration to be used for site-to-site connections.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. Sections 1.5 and 1.9 are also normative but cannot contain those terms. All other sections and examples in this specification are informative.