Endpoint Handlespace Redundancy Protocol (ENRP)
RFC 5353

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 21

Network Working Group                                             Q. Xie
Request for Comments: 5353                                    R. Stewart
Category: Experimental                                The Resource Group
                                                             M. Stillman
                                                                   Nokia
                                                               M. Tuexen
                                      Muenster Univ. of Applied Sciences
                                                            A. Silverton
                                                  Sun Microsystems, Inc.
                                                          September 2008

            Endpoint Handlespace Redundancy Protocol (ENRP)

Status of This Memo

   This memo defines an Experimental Protocol for the Internet
   community.  It does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

Abstract

   The Endpoint Handlespace Redundancy Protocol (ENRP) is designed to
   work in conjunction with the Aggregate Server Access Protocol (ASAP)
   to accomplish the functionality of the Reliable Server Pooling
   (RSerPool) requirements and architecture.  Within the operational
   scope of RSerPool, ENRP defines the procedures and message formats of
   a distributed, fault-tolerant registry service for storing,
   bookkeeping, retrieving, and distributing pool operation and
   membership information.

Table of Contents

   1. Introduction ....................................................3
      1.1. Definitions ................................................3
      1.2. Conventions ................................................4
   2. ENRP Message Definitions ........................................4
      2.1. ENRP_PRESENCE Message ......................................5
      2.2. ENRP_HANDLE_TABLE_REQUEST Message ..........................6
      2.3. ENRP_HANDLE_TABLE_RESPONSE Message .........................7
      2.4. ENRP_HANDLE_UPDATE Message .................................9
      2.5. ENRP_LIST_REQUEST Message .................................10
      2.6. ENRP_LIST_RESPONSE Message ................................11
      2.7. ENRP_INIT_TAKEOVER Message ................................12
      2.8. ENRP_INIT_TAKEOVER_ACK Message ............................13
      2.9. ENRP_TAKEOVER_SERVER Message ..............................14
      2.10. ENRP_ERROR Message .......................................15

Xie, et al.                   Experimental                      [Page 1]
RFC 5353            Endpoint Handlespace Redundancy       September 2008

   3. ENRP Operation Procedures ......................................15
      3.1. Methods for Communicating amongst ENRP Servers ............16
      3.2. ENRP Server Initialization ................................16
           3.2.1. Generate a Server Identifier .......................16
           3.2.2. Acquire Peer Server List ...........................17
                  3.2.2.1. Finding the Mentor Server .................17
                  3.2.2.2. Request Complete Server List from
                           Mentor Peer ...............................17
           3.2.3. Download ENRP Handlespace Data from Mentor Peer ....18
      3.3. Server Handlespace Update .................................20
           3.3.1. Announcing Additions or Updates of PE ..............20
           3.3.2. Announcing Removal of PE ...........................21
      3.4. Maintaining Peer List and Monitoring Peer Status ..........22
           3.4.1. Discovering New Peer ...............................22
           3.4.2. Server Sending Heartbeat ...........................22
           3.4.3. Detecting Peer Server Failure ......................23
      3.5. Taking Over a Failed Peer Server ..........................23
           3.5.1. Initiating Server Take-over Arbitration ............23
           3.5.2. Takeover Target Peer Server ........................24
      3.6. Handlespace Data Auditing and Re-synchronization ..........25
           3.6.1. Auditing Procedures ................................25
           3.6.2. PE Checksum Calculation Algorithm ..................26
           3.6.3. Re-Synchronization Procedures ......................27
      3.7. Handling Unrecognized Messages or Unrecognized
           Parameters ................................................28
   4. Variables and Thresholds .......................................28
      4.1. Variables .................................................28
      4.2. Thresholds ................................................28
   5. IANA Considerations ............................................28
      5.1. A New Table for ENRP Message Types ........................29
      5.2. A New Table for Update Action Types .......................29