This denomination has been dropped in order to avoid confusion with the Domain Name System (DNS).
It is explicitly not a goal of RSerPool to manage the global Internet's pools within a single handlespace.
That is, PHs do not have any hierarchy in contrast to the Domain Name System with its top-level and sub-domains.
PRs have to be redundant in order to avoid a PR to become a Single Point of Failure (SPoF).
Due to handlespace synchronization by ENRP, PRs of an operation scope are functionally equal.
Using the Aggregate Server Access Protocol (ASAP), a PE can add itself to a pool or remove it from by requesting a registration or deregistration from an arbitrary PR of the operation scope.
If the PE fails to answer within a certain timeout, it is assumed to be dead and immediately removed from the handlespace.
Using an appropriate selection policy, it is e.g. possible to equally distribute the request load onto the pool's PEs.
To make it possible for RSerPool components to configure automatically, PRs can announce themselves via UDP over IP multicast.
The advantage of using IP multicast instead of broadcast is that this mechanism will also work over routers (e.g. LANs inter-connected via a VPN) and the announces will — for the case of e.g. a switched Ethernet — only be heard and processed by stations actually interested in this information.