Takeover Suggestion Flag for the ENRP Handle Update Message
draft-dreibholz-rserpool-enrp-takeover-18

Document Type Active Internet-Draft (individual)
Last updated 2017-08-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       T. Dreibholz
Internet-Draft                                Simula Research Laboratory
Intended status: Experimental                                    X. Zhou
Expires: February 7, 2018                              Hainan University
                                                         August 06, 2017

      Takeover Suggestion Flag for the ENRP Handle Update Message
             draft-dreibholz-rserpool-enrp-takeover-18.txt

Abstract

   This document describes the Takeover Suggestion Flag for the
   ENRP_HANDLE_UPDATE message of the ENRP protocol.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 7, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dreibholz & Zhou        Expires February 7, 2018                [Page 1]
Internet-Draft          Takeover Suggestion Flag             August 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Takeover Suggestion Flag  . . . . . . . . . . . . . . . . . .   3
     2.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Reference Implementation  . . . . . . . . . . . . . . . . . .   4
   4.  Testbed Platform  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Reliable Server Pooling as described in [RFC5351] defines protocols
   for providing highly available services.  The management component
   used for pool administration is denoted as ENRP Server or Pool
   Registrar (PR).  Since a single ENRP server constitutes a single
   point of failure, there must be multiple ENRP servers.  Servers,
   denoted as Pool Elements (PE), use an arbitrary ENRP server for
   registration into the pool.  The chosen ENRP server becomes the Home
   ENRP Server, also denoted as Home PR (PR-H), of the PE.  It is
   responsible for making the PE identity known to the other ENRP
   servers (by using ENRP_HANDLE_UPDATE messages) and also to monitor
   the PE health (by using keep-alive messages).

   As shown in [AINA2009], the following scenario leads to unbalanced
   ENRP server workload: consider a set of multiple ENRP servers with
   one subset being unreliable (for example, their network connection
   has problems) and some reliable ENRP servers.  After a while, the
   reliable ENRP server will get the home ENRP server role for almost
   all of the PEs, which results in high workload for this ENRP server.
   Since the home ENRP server role is more computation-intensive (as
   shown by [IJHIT2008]), this leads to highly unbalanced workload for
   large RSerPool setups.  This unbalanced workload remains, even when
   the unreliable ENRP servers become reliable again (for example, when
   the network problems have been solved).

1.1.  Scope

   The Takeover Suggestion Flag defined in this draft defines a flag for
Show full document text