Browse Prior Art Database

Dynamic Host Configuration Protocol (RFC1541)

IP.com Disclosure Number: IPCOM000002373D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 32 page(s) / 91K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Droms: AUTHOR

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior of BOOTP relay agents [7, 23], and DHCP participants can interoperate with BOOTP participants [9]. Due to some errors introduced into RFC 1531 in the editorial process, this memo is reissued as RFC 1541.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group R. Droms

Request for Comments: 1541 Bucknell University

Obsoletes: 1531 October 1993

Category: Standards Track

Dynamic Host Configuration Protocol

Status of this memo

This RFC specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" for the standardization state and status

of this protocol. Distribution of this memo is unlimited.

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework

for passing configuration information to hosts on a TCP/IP network.

DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the

capability of automatic allocation of reusable network addresses and

additional configuration options [19]. DHCP captures the behavior of

BOOTP relay agents [7, 23], and DHCP participants can interoperate

with BOOTP participants [9]. Due to some errors introduced into RFC

1531 in the editorial process, this memo is reissued as RFC 1541.

Table of Contents

1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1 Related Work. . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Problem definition and issues . . . . . . . . . . . . . . . . 4

1.3 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 5

1.4 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.5 Design goals. . . . . . . . . . . . . . . . . . . . . . . . . 6

2. Protocol Summary . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 Configuration parameters repository . . . . . . . . . . . . . 10

2.2 Dynamic allocation of network addresses . . . . . . . . . . . 11

3. The Client-Server Protocol . . . . . . . . . . . . . . . . . . 11

3.1 Client-server interaction - allocating a network address. . . 12

3.2 Client-server interaction - reusing a previously allocated

network address . . . . . . . . . . . . . . . . . . . . . . . 17

3.3 Interpretation and representation of time values. . . . . . . 19

3.4 Host parameters in DHCP . . . . . . . . . . . . . . . . . . . 19

3.5 Use of DHCP in clients with multiple interfaces . . . . . . . 20

3.6 When clients should use DHCP. . . . . . . . . . . . . . . . . 20

4. Specification of the DHCP client-server protocol . . . . . . . 21

4.1 Constructing and sending DHCP messages. . . . . . . . . . . . 21

4.2 DHCP server administrative controls . . . . . . . . . . . . . 23

4.3 DHCP server behavior....