idnits 2.17.1 draft-ietf-dhc-loadb-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3074 5 Title: DHC Load Balancing Algorithm 6 Author(s): B. Volz, S. Gonczi, T. Lemon, R. Stevens 7 Status: Standards Track 8 Date: February 2001 9 Mailbox: bernie.volz@ericsson.com, 10 steve.gonczi@networkengines.com, 11 ted.lemon@nominum.com, robs@join.com 12 Pages: 10 13 Characters: 19374 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-dhc-loadb-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3074.txt 20 This document proposes a method of algorithmic load balancing. It 21 enables multiple, cooperating servers to decide which one should 22 service a client, without exchanging any information beyond initial 23 configuration. 25 The server selection is based on the servers hashing client Media 26 Access Control (MAC) addresses when multiple Dynamic Host 27 Configuration Protocol (DHCP) servers are available to service DHCP 28 clients. The proposed technique provides for efficient server 29 selection when multiple DHCP servers offer services on a network 30 without requiring any changes to existing DHCP clients. The same 31 method is proposed to select the target server of a forwarding agent 32 such as a Bootstrap Protocol (BOOTP) relay. 34 This document is a product of the Dynamic Host Configuration Working 35 Group of the IETF. 37 This is now a Proposed Standard Protocol. 39 This document specifies an Internet standards track protocol for 40 the Internet community, and requests discussion and suggestions 41 for improvements. Please refer to the current edition of the 42 "Internet Official Protocol Standards" (STD 1) for the 43 standardization state and status of this protocol. Distribution 44 of this memo is unlimited. 46 This announcement is sent to the IETF list and the RFC-DIST list. 47 Requests to be added to or deleted from the IETF distribution list 48 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 49 added to or deleted from the RFC-DIST distribution list should 50 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 52 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 53 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 54 help: ways_to_get_rfcs. For example: 56 To: rfc-info@RFC-EDITOR.ORG 57 Subject: getting rfcs 59 help: ways_to_get_rfcs 61 Requests for special distribution should be addressed to either the 62 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 63 specifically noted otherwise on the RFC itself, all RFCs are for 64 unlimited distribution.echo 65 Submissions for Requests for Comments should be sent to 66 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 67 Authors, for further information.