Browse Prior Art Database

Requirements for Reliable Server Pooling (RFC3237)

IP.com Disclosure Number: IPCOM000006704D
Original Publication Date: 2002-Jan-01
Included in the Prior Art Database: 2002-Jan-24
Document File: 11 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Tuexen: AUTHOR [+7]

Abstract

This document defines a basic set of requirements for reliable server pooling.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 21% of the total text.

Network Working Group                                          M. Tuexen

Request for Comments: 3237                                    Siemens AG

Category: Informational                                           Q. Xie

                                                                Motorola

                                                              R. Stewart

                                                                M. Shore

                                                                   Cisco

                                                                  L. Ong

                                                                   Ciena

                                                             J. Loughney

                                                             M. Stillman

                                                                   Nokia

                                                            January 2002

                Requirements for Reliable Server Pooling

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document defines a basic set of requirements for reliable server

   pooling.

   The goal of Reliable Server Pooling (RSerPool) is to develop an

   architecture and protocols for the management and operation of server

   pools supporting highly reliable applications, and for client access

   mechanisms to a server pool.

1.  Introduction

1.1.  Overview

   The Internet is always on.  Many users expect services to be always

   available; many businesses depend upon connectivity 24 hours a day, 7

   days a week, 365 days a year.  In order to fulfill this level of

   performance, many proprietary solutions and operating system

   dependent solutions have been developed to provide highly reliable

   and highly available servers.

Tuexen, et al.               Informational                      [Page 1]

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                      [Page 2]

RFC 3237        Requirements for Reliable Server Pooling    January 2002

      RSerPoo...