draft-ietf-rserpool-policies-07.txt   draft-ietf-rserpool-policies-08.txt 
Network Working Group M. Tuexen Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Applied Sciences Internet-Draft Muenster Univ. of Applied Sciences
Intended status: Experimental T. Dreibholz Intended status: Experimental T. Dreibholz
Expires: May 12, 2008 University of Duisburg-Essen Expires: September 11, 2008 University of Duisburg-Essen
November 9, 2007 March 10, 2008
Reliable Server Pooling Policies Reliable Server Pooling Policies
draft-ietf-rserpool-policies-07.txt draft-ietf-rserpool-policies-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 12, 2008. This Internet-Draft will expire on September 11, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes server pool policies for Reliable Server This document describes server pool policies for Reliable Server
Pooling including considerations for implementing them at ENRP Pooling including considerations for implementing them at ENRP
servers and pool users. servers and pool users.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
skipping to change at page 2, line 23 skipping to change at page 2, line 23
4.1. Round Robin Policy . . . . . . . . . . . . . . . . . . . . 5 4.1. Round Robin Policy . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Description . . . . . . . . . . . . . . . . . . . . . 5 4.1.1. Description . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. ENRP Server Considerations . . . . . . . . . . . . . . 5 4.1.2. ENRP Server Considerations . . . . . . . . . . . . . . 5
4.1.3. Pool User Considerations . . . . . . . . . . . . . . . 5 4.1.3. Pool User Considerations . . . . . . . . . . . . . . . 5
4.1.4. Pool Member Selection Policy Parameter . . . . . . . . 5 4.1.4. Pool Member Selection Policy Parameter . . . . . . . . 5
4.2. Weighted Round Robin Policy . . . . . . . . . . . . . . . 6 4.2. Weighted Round Robin Policy . . . . . . . . . . . . . . . 6
4.2.1. Description . . . . . . . . . . . . . . . . . . . . . 6 4.2.1. Description . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. ENRP Server Considerations . . . . . . . . . . . . . . 6 4.2.2. ENRP Server Considerations . . . . . . . . . . . . . . 6
4.2.3. Pool User Considerations . . . . . . . . . . . . . . . 6 4.2.3. Pool User Considerations . . . . . . . . . . . . . . . 6
4.2.4. Pool Member Selection Policy Parameter . . . . . . . . 6 4.2.4. Pool Member Selection Policy Parameter . . . . . . . . 6
4.3. Random Policy . . . . . . . . . . . . . . . . . . . . . . 6 4.3. Random Policy . . . . . . . . . . . . . . . . . . . . . . 7
4.3.1. Description . . . . . . . . . . . . . . . . . . . . . 6 4.3.1. Description . . . . . . . . . . . . . . . . . . . . . 7
4.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 6 4.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 7
4.3.3. Pool User Considerations . . . . . . . . . . . . . . . 7 4.3.3. Pool User Considerations . . . . . . . . . . . . . . . 7
4.3.4. Pool Member Selection Policy Parameter . . . . . . . . 7 4.3.4. Pool Member Selection Policy Parameter . . . . . . . . 7
4.4. Weighted Random Policy . . . . . . . . . . . . . . . . . . 7 4.4. Weighted Random Policy . . . . . . . . . . . . . . . . . . 7
4.4.1. Description . . . . . . . . . . . . . . . . . . . . . 7 4.4.1. Description . . . . . . . . . . . . . . . . . . . . . 7
4.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 7 4.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 7
4.4.3. Pool User Considerations . . . . . . . . . . . . . . . 7 4.4.3. Pool User Considerations . . . . . . . . . . . . . . . 8
4.4.4. Pool Member Selection Policy Parameter . . . . . . . . 7 4.4.4. Pool Member Selection Policy Parameter . . . . . . . . 8
4.5. Priority Policy . . . . . . . . . . . . . . . . . . . . . 8 4.5. Priority Policy . . . . . . . . . . . . . . . . . . . . . 8
4.5.1. Description . . . . . . . . . . . . . . . . . . . . . 8 4.5.1. Description . . . . . . . . . . . . . . . . . . . . . 8
4.5.2. ENRP Server Considerations . . . . . . . . . . . . . . 8 4.5.2. ENRP Server Considerations . . . . . . . . . . . . . . 8
4.5.3. Pool Element Considerations . . . . . . . . . . . . . 8 4.5.3. Pool Element Considerations . . . . . . . . . . . . . 8
4.5.4. Pool Member Selection Policy Parameter . . . . . . . . 8 4.5.4. Pool Member Selection Policy Parameter . . . . . . . . 8
5. Adaptive Policies . . . . . . . . . . . . . . . . . . . . . . 9 5. Adaptive Policies . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Least Used Policy . . . . . . . . . . . . . . . . . . . . 9 5.1. Least Used Policy . . . . . . . . . . . . . . . . . . . . 9
5.1.1. Description . . . . . . . . . . . . . . . . . . . . . 9 5.1.1. Description . . . . . . . . . . . . . . . . . . . . . 9
5.1.2. ENRP Server Considerations . . . . . . . . . . . . . . 9 5.1.2. ENRP Server Considerations . . . . . . . . . . . . . . 9
5.1.3. Pool User Considerations . . . . . . . . . . . . . . . 9 5.1.3. Pool User Considerations . . . . . . . . . . . . . . . 9
5.1.4. Pool Member Selection Policy Parameter . . . . . . . . 9 5.1.4. Pool Member Selection Policy Parameter . . . . . . . . 9
5.2. Least Used with Degradation Policy . . . . . . . . . . . . 9 5.2. Least Used with Degradation Policy . . . . . . . . . . . . 10
5.2.1. Description . . . . . . . . . . . . . . . . . . . . . 9 5.2.1. Description . . . . . . . . . . . . . . . . . . . . . 10
5.2.2. ENRP Server Considerations . . . . . . . . . . . . . . 10 5.2.2. ENRP Server Considerations . . . . . . . . . . . . . . 10
5.2.3. Pool User Considerations . . . . . . . . . . . . . . . 10 5.2.3. Pool User Considerations . . . . . . . . . . . . . . . 10
5.2.4. Pool Member Selection Policy Parameter . . . . . . . . 10 5.2.4. Pool Member Selection Policy Parameter . . . . . . . . 10
5.3. Priority Least Used Policy . . . . . . . . . . . . . . . . 10 5.3. Priority Least Used Policy . . . . . . . . . . . . . . . . 11
5.3.1. Description . . . . . . . . . . . . . . . . . . . . . 10 5.3.1. Description . . . . . . . . . . . . . . . . . . . . . 11
5.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 11 5.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 11
5.3.3. Pool User Considerations . . . . . . . . . . . . . . . 11 5.3.3. Pool User Considerations . . . . . . . . . . . . . . . 11
5.3.4. Pool Member Selection Policy Parameter . . . . . . . . 11 5.3.4. Pool Member Selection Policy Parameter . . . . . . . . 11
5.4. Randomized Least Used Policy . . . . . . . . . . . . . . . 11 5.4. Randomized Least Used Policy . . . . . . . . . . . . . . . 12
5.4.1. Description . . . . . . . . . . . . . . . . . . . . . 11 5.4.1. Description . . . . . . . . . . . . . . . . . . . . . 12
5.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 12 5.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 12
5.4.3. Pool User Considerations . . . . . . . . . . . . . . . 12 5.4.3. Pool User Considerations . . . . . . . . . . . . . . . 12
5.4.4. Pool Member Selection Policy Parameter . . . . . . . . 12 5.4.4. Pool Member Selection Policy Parameter . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7.1. A New Table for RSerPool Policy Types . . . . . . . . . . 13 7.1. A New Table for RSerPool Policy Types . . . . . . . . . . 13
8. Reference Implementation . . . . . . . . . . . . . . . . . . . 14 8. Reference Implementation . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . . . 17
1. Introduction 1. Introduction
The protocols defined in ENRP [5], ASAP [4] and Parameters [3] The protocols defined in ENRP [I-D.ietf-rserpool-enrp], ASAP
support a variety of server policies. Some of the policies use [I-D.ietf-rserpool-asap] and Parameters
dynamic load information of the pool elements and others do not. [I-D.ietf-rserpool-common-param] support a variety of server
Therefore, we classify them as adaptive and non-adaptive. The policies. Some of the policies use dynamic load information of the
selection of the pool user is performed by two different entities. pool elements and others do not. Therefore, we classify them as
Some of the consequences for policies which are not stateless are adaptive and non-adaptive. The selection of the pool user is
described in Performance [10]. performed by two different entities. Some of the consequences for
policies which are not stateless are described in Performance
[ICN2005].
Therefore this document describes not only packet formats but also Therefore this document describes not only packet formats but also
gives a detailed description of the procedures to be followed at the gives a detailed description of the procedures to be followed at the
ENRP servers and the pool users to implement each server policy. ENRP servers and the pool users to implement each server policy.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [1]. document are to be interpreted as described in RFC2119 [RFC2119].
3. Terminology and Definitions 3. Terminology and Definitions
3.1. Load 3.1. Load
The term load is a value specifying how much a pool element's The term load is a value specifying how much a pool element's
resources are currently utilized. 0x00000000 states, that the pool resources are currently utilized. 0x00000000 states, that the pool
element is not utilized (0%), 0xffffffff states that it is fully element is not utilized (0%), 0xffffffff states that it is fully
utilized (100%). Defining what utilization means is application- utilized (100%). Defining what utilization means is application-
dependent and out of the scope of RSerPool. However, it is required dependent and out of the scope of RSerPool. However, it is required
skipping to change at page 5, line 43 skipping to change at page 6, line 4
the pool users start with the same element. the pool users start with the same element.
4.1.3. Pool User Considerations 4.1.3. Pool User Considerations
A pool user SHOULD use the list of pool elements returned by the ENRP A pool user SHOULD use the list of pool elements returned by the ENRP
server in a round robin fashion, starting with the first. If all server in a round robin fashion, starting with the first. If all
elements of the list have been used it should start from the elements of the list have been used it should start from the
beginning again until the information is out of date. beginning again until the information is out of date.
4.1.4. Pool Member Selection Policy Parameter 4.1.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 | | Param Type = 0x8 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x00000001 | | Policy Type = 0x00000001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.2. Weighted Round Robin Policy 4.2. Weighted Round Robin Policy
4.2.1. Description 4.2.1. Description
The Weighted Round Robin (WRR) policy is a generalization of the RR The Weighted Round Robin (WRR) policy is a generalization of the RR
policy. If all weights are 1 then WRR is just RR. policy. If all weights are 1 then WRR is just RR.
skipping to change at page 6, line 32 skipping to change at page 6, line 39
4.2.3. Pool User Considerations 4.2.3. Pool User Considerations
The pool user SHOULD follow the same rules as for RR. The pool user SHOULD follow the same rules as for RR.
4.2.4. Pool Member Selection Policy Parameter 4.2.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0xc | | Param Type = 0x8 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x00000002 | | Policy Type = 0x00000002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight | | Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Weight: Weight constant for the WRR process. o Weight: Weight constant for the WRR process.
4.3. Random Policy 4.3. Random Policy
skipping to change at page 7, line 16 skipping to change at page 7, line 28
Each time the pool user must select one pool element it does this by Each time the pool user must select one pool element it does this by
randomly selecting one element from the list of pool elements randomly selecting one element from the list of pool elements
received from the ENRP server. received from the ENRP server.
4.3.4. Pool Member Selection Policy Parameter 4.3.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 | | Param Type = 0x8 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x00000003 | | Policy Type = 0x00000003 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.4. Weighted Random Policy 4.4. Weighted Random Policy
4.4.1. Description 4.4.1. Description
The Weighted Random (WRAND) policy is a generalization of the RAND The Weighted Random (WRAND) policy is a generalization of the RAND
policy, adding a weight for each pool element entry. RAND is equal policy, adding a weight for each pool element entry. RAND is equal
skipping to change at page 8, line 4 skipping to change at page 8, line 12
selecting a pool element should be the ratio of the weight of that selecting a pool element should be the ratio of the weight of that
pool element to the sum of weights. pool element to the sum of weights.
4.4.3. Pool User Considerations 4.4.3. Pool User Considerations
Each time the pool user must select one pool element it does this by Each time the pool user must select one pool element it does this by
randomly selecting one element from the list of pool elements randomly selecting one element from the list of pool elements
received from the ENRP server. received from the ENRP server.
4.4.4. Pool Member Selection Policy Parameter 4.4.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0xc | | Param Type = 0x8 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x00000004 | | Policy Type = 0x00000004 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight | | Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Weight: Weight constant for the WRAND process. o Weight: Weight constant for the WRAND process.
4.5. Priority Policy 4.5. Priority Policy
skipping to change at page 8, line 36 skipping to change at page 9, line 4
priorities. They MUST be reported in decreasing order. If multiple priorities. They MUST be reported in decreasing order. If multiple
pool elements have the same priority, they may be listed in any pool elements have the same priority, they may be listed in any
order. order.
4.5.3. Pool Element Considerations 4.5.3. Pool Element Considerations
The pool user MUST select the active pool element with the highest The pool user MUST select the active pool element with the highest
priority. priority.
4.5.4. Pool Member Selection Policy Parameter 4.5.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0xc | | Param Type = 0x8 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x00000005 | | Policy Type = 0x00000005 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Priority: 32 bits, unsigned int. Larger numbers mean higher o Priority: 32 bits, unsigned int. Larger numbers mean higher
priorities. priorities.
5. Adaptive Policies 5. Adaptive Policies
skipping to change at page 9, line 33 skipping to change at page 10, line 4
5.1.3. Pool User Considerations 5.1.3. Pool User Considerations
The pool user should try to use the pool elements returned from the The pool user should try to use the pool elements returned from the
list in the order returned by the ENRP server. A subsequent call for list in the order returned by the ENRP server. A subsequent call for
handle resolution may result in the same list. Thereofore, it is handle resolution may result in the same list. Thereofore, it is
RECOMMENDED for a pool user to request multiple entries in order to RECOMMENDED for a pool user to request multiple entries in order to
have a sufficient amount of feasible backup entries available. have a sufficient amount of feasible backup entries available.
5.1.4. Pool Member Selection Policy Parameter 5.1.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0xc | | Param Type = 0x8 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x40000001 | | Policy Type = 0x40000001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load | | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
5.2. Least Used with Degradation Policy 5.2. Least Used with Degradation Policy
skipping to change at page 10, line 26 skipping to change at page 10, line 44
5.2.3. Pool User Considerations 5.2.3. Pool User Considerations
See LU policy. See LU policy.
5.2.4. Pool Member Selection Policy Parameter 5.2.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x10 | | Param Type = 0x8 | Length = 0x10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x40000002 | | Policy Type = 0x40000002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load | | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load Degradation | | Load Degradation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
o Load Degradation: Load Degradation constant of the pool element. o Load Degradation: Load Degradation constant of the pool element.
skipping to change at page 11, line 27 skipping to change at page 12, line 4
5.3.3. Pool User Considerations 5.3.3. Pool User Considerations
The pool user should try to use the pool elements returned from the The pool user should try to use the pool elements returned from the
list in the order returned by the ENRP server. A subsequent call for list in the order returned by the ENRP server. A subsequent call for
handle resolution may result in the same list. Therefore, it is handle resolution may result in the same list. Therefore, it is
RECOMMENDED for a pool user to request multiple entries in order to RECOMMENDED for a pool user to request multiple entries in order to
have a sufficient amount of feasible backup entries available. have a sufficient amount of feasible backup entries available.
5.3.4. Pool Member Selection Policy Parameter 5.3.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x10 | | Param Type = 0x8 | Length = 0x10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x40000003 | | Policy Type = 0x40000003 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load | | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load Degradation | | Load Degradation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
o Load Degradation: Load Degradation constant of the pool element. o Load Degradation: Load Degradation constant of the pool element.
skipping to change at page 12, line 20 skipping to change at page 12, line 43
5.4.3. Pool User Considerations 5.4.3. Pool User Considerations
See WRAND policy. See WRAND policy.
5.4.4. Pool Member Selection Policy Parameter 5.4.4. Pool Member Selection Policy Parameter
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x7 | Length = 0xc | | Param Type = 0x8 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type = 0x40000004 | | Policy Type = 0x40000004 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load | | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
6. Security Considerations 6. Security Considerations
The security threats regarding RSerPool have been analyzed in The security threats regarding RSerPool have been analyzed in
RSerPool threats [6]. The server policy descriptions in this RSerPool threats [I-D.ietf-rserpool-threats]. The server policy
document do not add any other threats. descriptions in this document do not add any other threats.
7. IANA Considerations 7. IANA Considerations
[NOTE to RFC-Editor: [NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this "RFCXXXX" is to be replaced by the RFC number you assign this
document. document.
] ]
This document (RFCXXX) is the reference for all registrations This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an described in this section. All registrations need to be listed on an
skipping to change at page 14, line 4 skipping to change at page 14, line 33
... ...
0x7fffffff (reserved by IETF) RFCXXXX 0x7fffffff (reserved by IETF) RFCXXXX
0x80000000 (private use, non-standard policy) RFCXXXX 0x80000000 (private use, non-standard policy) RFCXXXX
... ...
0xffffffff (private use, non-standard policy) RFCXXXX 0xffffffff (private use, non-standard policy) RFCXXXX
For registering at IANA an RSerPool Policy Type in this table a For registering at IANA an RSerPool Policy Type in this table a
request has to be made to assign such a number. This number must be request has to be made to assign such a number. This number must be
unique and use the appropiate upper bits. The "Specification unique and use the appropiate upper bits. The "Specification
Required" policy of RFC2434 [2] MUST be applied. Required" policy of RFC2434 [RFC2434] MUST be applied.
The Policy Type space from 0x80000000 to 0xffffffff is designated for The Policy Type space from 0x80000000 to 0xffffffff is designated for
private use. private use.
8. Reference Implementation 8. Reference Implementation
The reference implementation of RSerPool and the policies described The reference implementation of RSerPool and the policies described
in this document is available at [7]. in this document is available at [RSerPoolPage].
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[3] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate [I-D.ietf-rserpool-common-param]
Server Access Protocol (ASAP) and Endpoint Handlespace Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
Redundancy Protocol (ENRP) Parameters", "Aggregate Server Access Protocol (ASAP) and Endpoint
draft-ietf-rserpool-common-param-13 (work in progress), Handlespace Redundancy Protocol (ENRP) Parameters",
September 2007. draft-ietf-rserpool-common-param-15 (work in progress),
December 2007.
[4] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate [I-D.ietf-rserpool-asap]
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-17 Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
(work in progress), September 2007. "Aggregate Server Access Protocol (ASAP)",
draft-ietf-rserpool-asap-18 (work in progress),
November 2007.
[5] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. [I-D.ietf-rserpool-enrp]
Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)", Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
draft-ietf-rserpool-enrp-17 (work in progress), September 2007. Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-18 (work in progress),
November 2007.
[6] Stillman, M., Gopal, R., Guttman, E., Holdrege, M., and S. [I-D.ietf-rserpool-threats]
Sengodan, "Threats Introduced by RSerPool and Requirements for Stillman, M., Gopal, R., Guttman, E., Holdrege, M., and S.
Security in Response to Threats", Sengodan, "Threats Introduced by RSerPool and Requirements
for Security in Response to Threats",
draft-ietf-rserpool-threats-09 (work in progress), draft-ietf-rserpool-threats-09 (work in progress),
October 2007. October 2007.
9.2. Informative References 9.2. Informative References
[7] Dreibholz, T., "Thomas Dreibholz's RSerPool Page", [RSerPoolPage]
URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/. Dreibholz, T., "Thomas Dreibholz's RSerPool Page", URL:
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/.
[8] Dreibholz, T., "Reliable Server Pooling -- Evaluation, [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation,
Optimization and Extension of a Novel IETF Architecture", Ph.D. Optimization and Extension of a Novel IETF Architecture",
Thesis University of Duisburg-Essen, Faculty of Economics, Ph.D. Thesis University of Duisburg-Essen, Faculty of
Institute for Computer Science and Business Information Economics, Institute for Computer Science and Business
Systems, URL: http://duepublico.uni-duisburg-essen.de/servlets/ Information Systems, URL: http://
DerivateServlet/Derivate-16326/Dre2006-final.pdf, March 2007. duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/
Derivate-16326/Dre2006-final.pdf, March 2007.
[9] Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of
Server Pooling Systems", Proceedings of the 30th IEEE Local Reliable Server Pooling Systems", Proceedings of the 30th
Computer Networks Conference, November 2005. IEEE Local Computer Networks Conference, November 2005.
[10] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution [ICN2005] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load
Performance of the Reliable Server Pooling Framework", Distribution Performance of the Reliable Server Pooling
Proceedings of the 4th IEEE International Conference on Framework", Proceedings of the 4th IEEE International
Networking, April 2005. Conference on Networking, April 2005.
Authors' Addresses Authors' Addresses
Michael Tuexen Michael Tuexen
Muenster University of Applied Sciences Muenster University of Applied Sciences
Stegerwaldstrasse 39 Stegerwaldstrasse 39
48565 Steinfurt 48565 Steinfurt
Germany Germany
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
skipping to change at page 16, line 7 skipping to change at page 17, line 7
45326 Essen, Nordrhein-Westfalen 45326 Essen, Nordrhein-Westfalen
Germany Germany
Phone: +49 201 183-7637 Phone: +49 201 183-7637
Fax: +49 201 183-7673 Fax: +49 201 183-7673
Email: dreibh@exp-math.uni-essen.de Email: dreibh@exp-math.uni-essen.de
URI: http://www.exp-math.uni-essen.de/~dreibh/ URI: http://www.exp-math.uni-essen.de/~dreibh/
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 16, line 44 skipping to change at line 691
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 42 change blocks. 
84 lines changed or deleted 86 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/