RFC 3237 (rfc3237) - Page 2 of 10

Requirements for Reliable Server Pooling

RFC 3237        Requirements for Reliable Server Pooling    January 2002


   This document defines requirements for an architecture and protocols
   enabling pooling of servers to support high reliability and
   availability for applications.

   The range of applications that can benefit from reliable server
   pooling includes both mobile and real-time applications.  Reliable
   server pooling mechanisms will be designed to support functionality
   for flexible pooling such as registration and deregistration, and
   load balancing of traffic across the server pool.  Mechanisms will
   need to balance the needs of scalability, overhead traffic and
   response time to changes in pool status, as discussed below.

1.2.  Terminology

   This document uses the following terms:

      Operation scope:
         The part of the network visible to pool users by a specific
         instance of the reliable server pooling protocols.

      Pool (or server pool):
         A collection of servers providing the same application
         functionality.

      Pool handle (or pool name):
         A logical pointer to a pool.  Each server pool will be
         identifiable in the operation scope of the system by a unique
         pool handle or "name".

      Pool element:
         A server entity having registered to a pool.

      Pool user:
         A server pool user.

      Pool element handle (or endpoint handle):
         A logical pointer to a particular pool element in a pool,
         consisting of the name of the pool and one or more destination
         transport addresses for the pool element.

      Name space:
         A cohesive structure of pool names and relations that may be
         queried by an internal or external agent.

      Name server:
         Entity which is responsible for managing and maintaining the
         name space within the RSerPool operation scope.




Tuexen, et al.               Informational