draft-ietf-dhc-dhcpv6-loadb-01.txt   draft-ietf-dhc-dhcpv6-loadb-02.txt 
Internet Engineering Task Force B. Volz Internet Engineering Task Force B. Volz
INTERNET DRAFT Ericsson INTERNET DRAFT Ericsson
DHC Working Group June 2002 DHC Working Group August 2002
Expires: December 18, 2002 Expires: February 1, 2003
Load Balancing for DHCPv6 Load Balancing for DHCPv6
draft-ietf-dhc-dhcpv6-loadb-01.txt draft-ietf-dhc-dhcpv6-loadb-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 18, 2002. This Internet-Draft will expire on February 1, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This document specifies a load balancing algorithm for use with This document specifies a load balancing algorithm for use with
DHCPv6. Load balancing enables multiple cooperating DHCPv6 servers DHCPv6. Load balancing enables multiple cooperating DHCPv6 servers
to decide which one should service a client, without exchanging to decide which one should service a client, without exchanging
skipping to change at page 4, line 4 skipping to change at page 4, line 4
process the message as per [2]. process the message as per [2].
3. If the Client Identifier option's DUID is within the server's 3. If the Client Identifier option's DUID is within the server's
hash bucket assignment, process as per [2]. hash bucket assignment, process as per [2].
4. If the Elapsed Time option is present in the message and its 4. If the Elapsed Time option is present in the message and its
value exceeds the configured threshold, process as per [2]. value exceeds the configured threshold, process as per [2].
5. Otherwise, do not process the message because load balancing 5. Otherwise, do not process the message because load balancing
dictates that another server should be processing the message. dictates that another server should be processing the message.
Note: For CONFIRM messages (which do not include a Server Identifier
option), a server MAY forgo the load balancing algorithm and respond
to all clients.
The hash bucket assignments for each server must be configured and The hash bucket assignments for each server must be configured and
care must be taken to assign each hash bucket to at least one server. care must be taken to assign each hash bucket to at least one server.
How the hash buckets are configured in servers is outside the scope How the hash buckets are configured in servers is outside the scope
of this document. of this document.
If a single hash bucket is assigned to multiple servers, the logic a If a single hash bucket is assigned to multiple servers, the logic a
client uses to select a server applies (just as if there were client uses to select a server applies (just as if there were
multiple servers for clients without load balancing). For example, multiple servers for clients without load balancing). For example,
each server can be configured with a different server preference each server can be configured with a different server preference
 End of changes. 

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