| process is called a referral. |
A replica that refers all update operations to | |
| A server can hold any number of |
A replica that contains a master copy of directory information | |
| and can be updated. A server can hold any number of |
| |
relative distinguished name | See RDN. |
replica | A database that participates in replication. |
Replication configuration where replica servers, either hub or | |
| consumer servers, pull directory data from supplier servers. |
| This method is available only for legacy replication. |
replication | Act of copying directory trees or subtrees from supplier servers |
| to replica servers. |
replication agreement | Set of configuration parameters that are stored on the supplier |
| server and identify the databases to replicate, the replica |
| servers to which the data is pushed, the times during which |
| replication can occur, the DN and credentials used by the |
| supplier to bind to the consumer, and how the connection is |
| secured. |
RFC | Request for Comments. Procedures or standards documents |
| submitted to the Internet community. People can send |
| comments on the technologies before they become accepted |
| standards. |
role | An entry grouping mechanism. Each role has members, which |
| are the entries that possess the role. |
Attributes that appear on an entry because it possesses a | |
| particular role within an associated CoS template. |
root | The most privileged user available on Unix machines. The root |
| user has complete access privileges to all files on the machine. |
root suffix | The parent of one or more sub suffixes. A directory tree can |
| contain more than one root suffix. |
S
SASL | An authentication framework for clients as they attempt to bind |
| to a directory. Also Simple Authentication and Security Layer . |
133