3 Protocol Details
There are three components to the RRAS management - the RPC interfaces, the phonebook file settings, and the registry settings.
The RPC interfaces enable remote management of the RRAS runtime. It comprises two RPC interfaces – DIMSVC and RASRPC.
The phonebook file specifies the site-to-site connection settings and RRASM validates the phonebook entries used as a part of RRASM RPC methods using the phonebook file. The phonebook entries (specified through the RPC methods) are valid if there are corresponding phonebook entry sections that have the same name. The phonebook file format is described in section 2.2.2.
The registry settings specify the RRAS configuration. RRAS initializes its runtime configuration using the registry settings described in section 2.2.3. Subsequently the RRASM RPC interfaces provide the remote management of these runtime configuration settings. RRAS is responsible for updating the configuration changes back to the registry store. RRAS initializes the RRASM RPC interfaces as given in section 188.8.131.52 and 184.108.40.206. RRAS server passes the value of two of the registry keys that impacts RRASM protocol behavior as a part of this initialization as defined in section 3.1.6. RRASM stores these values in the ADM variables as defined in section 3.1.1. The other registry settings do not impact the RRASM protocol behavior and only impact the configuration used by RRAS. Both RRASM and RRAS reside on the same server. That portion of the server which implements the management semantics, which the RRASM protocol remotely makes available remotely, is referred to as the RRAS server or RRAS implementation.