draft-ietf-rserpool-policies-04.txt   draft-ietf-rserpool-policies-05.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: September 6, 2007 University of Duisburg-Essen Expires: January 10, 2008 University of Duisburg-Essen
March 5, 2007 July 9, 2007
Reliable Server Pooling Policies Reliable Server Pooling Policies
draft-ietf-rserpool-policies-04.txt draft-ietf-rserpool-policies-05.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 September 6, 2007. This Internet-Draft will expire on January 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). 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.
skipping to change at page 3, line 11 skipping to change at page 3, line 11
4.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 10 4.3.2. ENRP Server Considerations . . . . . . . . . . . . . . 10
4.3.3. Pool User Considerations . . . . . . . . . . . . . . . 11 4.3.3. Pool User Considerations . . . . . . . . . . . . . . . 11
4.3.4. Pool Member Selection Policy Parameter . . . . . . . . 11 4.3.4. Pool Member Selection Policy Parameter . . . . . . . . 11
4.4. Randomized Least Used Policy . . . . . . . . . . . . . . . 11 4.4. Randomized Least Used Policy . . . . . . . . . . . . . . . 11
4.4.1. Description . . . . . . . . . . . . . . . . . . . . . 11 4.4.1. Description . . . . . . . . . . . . . . . . . . . . . 11
4.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 11 4.4.2. ENRP Server Considerations . . . . . . . . . . . . . . 11
4.4.3. Pool User Considerations . . . . . . . . . . . . . . . 12 4.4.3. Pool User Considerations . . . . . . . . . . . . . . . 12
4.4.4. Pool Member Selection Policy Parameter . . . . . . . . 12 4.4.4. Pool Member Selection Policy Parameter . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.1. A New Table for RSerPool Policy Types . . . . . . . . . . 12
7. Reference Implementation . . . . . . . . . . . . . . . . . . . 13 7. Reference Implementation . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Introduction 1. Introduction
The protocols defined in ENRP [5], ASAP [4] and Parameters [3] The protocols defined in ENRP [6], ASAP [5] and Parameters [4]
support a variety of server policies. Some of the policies use support a variety of server policies. Some of the policies use
dynamic load information of the pool elements and others do not. dynamic load information of the pool elements and others do not.
Therefore, we classify them as adaptive and non-adaptive. The Therefore, we classify them as adaptive and non-adaptive. The
selection of the pool user is performed by two different entities. selection of the pool user is performed by two different entities.
Some of the consequences for policies which are not stateless are Some of the consequences for policies which are not stateless are
described in Performance [11]. described in Performance [12].
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. Terminology and Definitions 2. Terminology and Definitions
2.1. Load 2.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
skipping to change at page 8, line 32 skipping to change at page 8, line 32
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.
3.5.4. Pool Member Selection Policy Parameter 3.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 = 0x6 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0xa | (reserved) | | Policy Type = 0x00000005 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Reserved: 24 bits, SHOULD be set to 0.
o Priority: 32 bits, unsigned int. Larger numbers mean higher o Priority: 32 bits, unsigned int. Larger numbers mean higher
priorities. priorities.
4. Adaptive Policies 4. Adaptive Policies
4.1. Least Used Policy 4.1. Least Used Policy
4.1.1. Description 4.1.1. Description
The Least Used (LU) policy uses load information provided by the pool The Least Used (LU) policy uses load information provided by the pool
skipping to change at page 12, line 26 skipping to change at page 12, line 26
| Policy Type = 0x40000004 | | Policy Type = 0x40000004 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load | | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
5. Security Considerations 5. 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 [7]. The server policy descriptions in this
document do not add any other threats. document do not add any other threats.
6. IANA Considerations 6. IANA Considerations
The IANA keeps a list of Policy Types which are 4 byte values. The [NOTE to RFC-Editor:
format of the policy type value is defined as follows: "RFCXXXX" is to be replaced by the RFC number you assign this
document.
]
This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an
RSerPool specific page.
6.1. A New Table for RSerPool Policy Types
RSerPool Policy Types which are 4 byte values have to be maintained
by IANA. The format of the policy type value is defined as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X|A| Policy Number | |X|A| Policy Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o X: If set to 1, the policy is user-defined and not standardized. o X: If set to 1, the policy is user-defined and not standardized.
All standards policies reserved by the IETF use X=0. All standards policies reserved by the IETF use X=0.
o A: If set to 1, the policy is adaptive. Otherwise, it is non- o A: If set to 1, the policy is adaptive. Otherwise, it is non-
adaptive. adaptive.
o Policy Number: The actual number of the policy. o Policy Number: The actual number of the policy.
The Policy Type values used in this document are: Nine initial Policy Types should be assigned and maintained in a new
table "RSerPool Policy Types":
Value Policy Value Policy Reference
----- --------- ----- --------- ---------
0x00000000 (reserved by IETF) 0x00000000 (reserved by IETF) RFCXXXX
0x00000001 Round Robin 0x00000001 Round Robin RFCXXXX
0x00000002 Weighted Round Robin 0x00000002 Weighted Round Robin RFCXXXX
0x00000003 Random 0x00000003 Random RFCXXXX
0x00000004 Weighted Random 0x00000004 Weighted Random RFCXXXX
0x00000005 Active/Passive 0x00000005 Priority RFCXXXX
0x00000006 (reserved by IETF) 0x00000006 (reserved by IETF) RFCXXXX
... ...
0x3fffffff (reserved by IETF) 0x3fffffff (reserved by IETF) RFCXXXX
0x40000000 (reserved by IETF) 0x40000000 (reserved by IETF) RFCXXXX
0x40000001 Least Used 0x40000001 Least Used RFCXXXX
0x40000002 Least Used with Degradation 0x40000002 Least Used with Degradation RFCXXXX
0x40000003 Priority Least Used 0x40000003 Priority Least Used RFCXXXX
0x40000004 Randomized Least Used 0x40000004 Randomized Least Used RFCXXXX
0x40000005 (reserved by IETF) 0x40000005 (reserved by IETF) RFCXXXX
... ...
0x7fffffff (reserved by IETF) 0x7fffffff (reserved by IETF) RFCXXXX
0x80000000 (user-defined, non-standard policy) 0x80000000 (user-defined, non-standard policy) RFCXXXX
... ...
0xffffffff (user-defined, non-standard policy) 0xffffffff (user-defined, non-standard policy) RFCXXXX
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
unique and use the appropiate upper bits. The "Specification
Required" policy of RFC2434 [3] MUST be applied.
7. Reference Implementation 7. 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 [8].
8. References 8. References
8.1. Normative References 8.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Bradner, S., "Intellectual Property Rights in IETF Technology", [2] Bradner, S., "Intellectual Property Rights in IETF Technology",
RFC 3668, February 2004. RFC 3668, February 2004.
[3] Stewart, R., "Aggregate Server Access Protocol (ASAP) and [3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[4] Stewart, R., "Aggregate Server Access Protocol (ASAP) and
Endpoint Handlespace Redundancy Protocol (ENRP) Parameters", Endpoint Handlespace Redundancy Protocol (ENRP) Parameters",
draft-ietf-rserpool-common-param-11 (work in progress), draft-ietf-rserpool-common-param-11 (work in progress),
October 2006. October 2006.
[4] Stewart, R., "Aggregate Server Access Protocol (ASAP)", [5] Stewart, R., "Aggregate Server Access Protocol (ASAP)",
draft-ietf-rserpool-asap-15 (work in progress), January 2007. draft-ietf-rserpool-asap-15 (work in progress), January 2007.
[5] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)", [6] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)",
draft-ietf-rserpool-enrp-15 (work in progress), January 2007. draft-ietf-rserpool-enrp-15 (work in progress), January 2007.
[6] Stillman, M., "Threats Introduced by Rserpool and Requirements [7] Stillman, M., "Threats Introduced by Rserpool and Requirements
for Security in response to Threats", for Security in response to Threats",
draft-ietf-rserpool-threats-06 (work in progress), draft-ietf-rserpool-threats-06 (work in progress),
November 2006. November 2006.
8.2. Informative References 8.2. Informative References
[7] Dreibholz, T., "Thomas Dreibholz's RSerPool Page", [8] Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/. URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/.
[8] Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable [9] Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable
Server Pooling Systems", Proceedings of the 30th IEEE Local Server Pooling Systems", Proceedings of the 30th IEEE Local
Computer Networks Conference, November 2005. Computer Networks Conference, November 2005.
[9] Dreibholz, T. and E. Rathgeb, "The Performance of Reliable [10] Dreibholz, T. and E. Rathgeb, "The Performance of Reliable
Server Pooling Systems in Different Server Capacity Scenarios", Server Pooling Systems in Different Server Capacity Scenarios",
Proceedings of the IEEE TENCON, November 2005. Proceedings of the IEEE TENCON, November 2005.
[10] Dreibholz, T. and E. Rathgeb, "Implementing the Reliable Server [11] Dreibholz, T. and E. Rathgeb, "Implementing the Reliable Server
Pooling Framework", Proceedings of the 8th IEEE International Pooling Framework", Proceedings of the 8th IEEE International
Conference on Telecommunications, June 2005. Conference on Telecommunications, June 2005.
[11] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution [12] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution
Performance of the Reliable Server Pooling Framework", Performance of the Reliable Server Pooling Framework",
Proceedings of the 4th IEEE International Conference on Proceedings of the 4th IEEE International Conference on
Networking, April 2005. 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
 End of changes. 30 change blocks. 
45 lines changed or deleted 65 lines changed or added

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