draft-ietf-rserpool-policies-01.txt   draft-ietf-rserpool-policies-02.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
Expires: December 14, 2005 T. Dreibholz Expires: August 6, 2006 T. Dreibholz
University of Duisburg-Essen University of Duisburg-Essen
June 12, 2005 February 2, 2006
Reliable Server Pooling Policies Reliable Server Pooling Policies
draft-ietf-rserpool-policies-01.txt draft-ietf-rserpool-policies-02.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 December 14, 2005. This Internet-Draft will expire on August 6, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
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 name Pooling including considerations for implementing them at name
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 3, line 9 skipping to change at page 3, line 9
4.4 Randomized Least Used Policy . . . . . . . . . . . . . . . 10 4.4 Randomized Least Used Policy . . . . . . . . . . . . . . . 10
4.4.1 Description . . . . . . . . . . . . . . . . . . . . . 10 4.4.1 Description . . . . . . . . . . . . . . . . . . . . . 10
4.4.2 Name Server Considerations . . . . . . . . . . . . . . 11 4.4.2 Name Server Considerations . . . . . . . . . . . . . . 11
4.4.3 Pool User Considerations . . . . . . . . . . . . . . . 11 4.4.3 Pool User Considerations . . . . . . . . . . . . . . . 11
4.4.4 Pool Member Selection Policy Parameter . . . . . . . . 11 4.4.4 Pool Member Selection Policy Parameter . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1 Normative References . . . . . . . . . . . . . . . . . . . 12 7.1 Normative References . . . . . . . . . . . . . . . . . . . 12
7.2 Informative References . . . . . . . . . . . . . . . . . . 12 7.2 Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . 14
1. Introduction 1. Introduction
The protocols defined in ENRP [5], ASAP [4] and Parameters [3] The protocols defined in ENRP [5], ASAP [4] and Parameters [3]
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 [7]. described in Performance [11].
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
name servers and the pool users to implement each server policy. name 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 5, line 41 skipping to change at page 5, line 41
beginning again until the information is out of date. beginning again until the information is out of date.
3.1.4 Pool Member Selection Policy Parameter 3.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 = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x1 | (reserved) | | Policy=0x1 | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Reserved: 24 bits, SHOULD be set to 0. o Reserved: 24 bits, SHOULD be set to 0.
3.2 Weighted Round Robin Policy 3.2 Weighted Round Robin Policy
3.2.1 Description 3.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 28 skipping to change at page 6, line 28
The pool user SHOULD follow the same rules as for RR. The pool user SHOULD follow the same rules as for RR.
3.2.4 Pool Member Selection Policy Parameter 3.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 = 0x8 | | Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x2 | Weight | | Policy=0x2 | Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Weight: Weight constant for the WRR process. o Weight: Weight constant for the WRR process.
3.3 Random Policy 3.3 Random Policy
3.3.1 Description 3.3.1 Description
The Random (RAND) policy is a very simple stateless policy. The Random (RAND) policy is a very simple stateless policy.
3.3.2 Name Server Considerations 3.3.2 Name Server Considerations
skipping to change at page 7, line 13 skipping to change at page 7, line 13
received from the name server. received from the name server.
3.3.4 Pool Member Selection Policy Parameter 3.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 = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x3 | (reserved) | | Policy=0x3 | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Reserved: 24 bits, SHOULD be set to 0. o Reserved: 24 bits, SHOULD be set to 0.
3.4 Weighted Random Policy 3.4 Weighted Random Policy
3.4.1 Description 3.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
to WRAND having all weights set to 1. to WRAND having all weights set to 1.
skipping to change at page 7, line 47 skipping to change at page 7, line 47
received from the name server. received from the name server.
3.4.4 Pool Member Selection Policy Parameter 3.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 = 0x8 | | Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x4 | Weight | | Policy=0x4 | Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Weight: Weight constant for the WRAND process. o Weight: Weight constant for the WRAND process.
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
elements to select the lowest-loaded pool elements within the pool. elements to select the lowest-loaded pool elements within the pool.
skipping to change at page 8, line 41 skipping to change at page 8, line 41
have a sufficient amount of feasible backup entries available. have a sufficient amount of feasible backup entries available.
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 = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x5 | Load | | Policy=0x5 | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
4.2 Least Used with Degradation Policy 4.2 Least Used with Degradation Policy
4.2.1 Description 4.2.1 Description
The Least Used with Degradation (LUD) policy extends the LU policy by The Least Used with Degradation (LUD) policy extends the LU policy by
a load degradation value describing the pool element's load increment a load degradation value describing the pool element's load increment
when a new service association is accepted. when a new service association is accepted.
skipping to change at page 9, line 29 skipping to change at page 9, line 29
See LU policy. See LU policy.
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 = 0x6 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x6 | Load | | Policy=0x6 | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (reserved) | Load Degradation | | (reserved) | Load Degradation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Load: Current load of the pool element. o Load: Current load of the pool element.
o Reserved: 8 bits, SHOULD be set to 0. o Reserved: 8 bits, SHOULD be set to 0.
o Load Degradation: Load Degradation constant of the pool element. o Load Degradation: Load Degradation constant of the pool element.
4.3 Priority Least Used Policy 4.3 Priority Least Used Policy
4.3.1 Description 4.3.1 Description
The Priority Least Used (PLU) policy uses load information provided The Priority Least Used (PLU) policy uses load information provided
skipping to change at page 10, line 33 skipping to change at page 10, line 33
have a sufficient amount of feasible backup entries available. have a sufficient amount of feasible backup entries available.
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 = 0xc | | Param Type = 0x6 | Length = 0xc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x7 | Load | | Policy=0x7 | Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (reserved) | Load Degradation | | (reserved) | 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.
4.4 Randomized Least Used Policy 4.4 Randomized Least Used Policy
4.4.1 Description 4.4.1 Description
The Randomized Least Used (RLU) policy combines LU and WRAND. That The Randomized Least Used (RLU) policy combines LU and WRAND. That
is, the pool element entries are selected randomly; the probability is, the pool element entries are selected randomly; the probability
skipping to change at page 11, line 22 skipping to change at page 11, line 22
See WRAND policy. See WRAND policy.
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 = 0x7 | Length = 0x8 | | Param Type = 0x7 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x9 | Load | | Policy=0x9 | 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 [6]. 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
skipping to change at page 12, line 13 skipping to change at page 12, line 13
7. References 7. References
7.1 Normative References 7.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., Xie, Q., and M. Tuexen, "Aggregate Server Access [3] Stewart, R., "Aggregate Server Access Protocol (ASAP) and
Protocol (ASAP) and Endpoint Name Resolution (ENRP) Endpoint Handlespace Redundancy Protocol (ENRP) Parameters",
Parameters", draft-ietf-rserpool-common-param-08 (work in draft-ietf-rserpool-common-param-09 (work in progress), I-D
progress), February 2005. Status active, IETF Datatracker State AD is watching, Intended
Status None, Responsible AD Jon Peterson, July 2005.
[4] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate [4] Stewart, R., "Aggregate Server Access Protocol (ASAP)",
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-11 draft-ietf-rserpool-asap-12 (work in progress), I-D
(work in progress), February 2005. Status active, IETF Datatracker State AD is watching, Intended
Status None, Responsible AD Jon Peterson, July 2005.
[5] Xie, Q., Stewart, R., and M. Stillman, "Enpoint Name Resolution [5] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)",
Protocol (ENRP)", draft-ietf-rserpool-enrp-11 (work in draft-ietf-rserpool-enrp-12 (work in progress), I-D
progress), February 2005. Status active, IETF Datatracker State AD is watching, Intended
Status None, Responsible AD Jon Peterson, July 2005.
[6] Stillman, M., "Threats Introduced by Rserpool and Requirements [6] Stillman, M., "Threats Introduced by Rserpool and Requirements
for Security in response to Threats", for Security in response to Threats",
draft-ietf-rserpool-threats-04 (work in progress), January 2005. draft-ietf-rserpool-threats-05 (work in progress), I-D
Status iesg, IETF Datatracker State IESG Evaluation :: Point
Raised - writeup needed, Intended Status Informational,
Responsible AD Jon Peterson, July 2005.
7.2 Informative References 7.2 Informative References
[7] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution [7] Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
Performance of the Reliable Server Pooling Framework", Submitted URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/.
to Globecom 2004.
[8] Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable
Server Pooling Systems", Proceedings of the 30th IEEE Local
Computer Networks Conference, November 2005.
[9] Dreibholz, T. and E. Rathgeb, "The Performance of Reliable
Server Pooling Systems in Different Server Capacity Scenarios",
Proceedings of the IEEE TENCON, November 2005.
[10] Dreibholz, T. and E. Rathgeb, "Implementing the Reliable Server
Pooling Framework", Proceedings of the 8th IEEE International
Conference on Telecommunications, June 2005.
[11] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution
Performance of the Reliable Server Pooling Framework",
Proceedings of the 4th IEEE International 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 14, line 41 skipping to change at page 14, line 41
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 AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 23 change blocks. 
32 lines changed or deleted 54 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/